| milk | might Patchage ever support connecting ALSA MIDI to JACK MIDI, or is the solution simply to use a2e? | 02:45 |
|---|---|---|
| drobilla | or the jack drivers that do it, or whatever, yes | 02:47 |
| drobilla | I feel pretty strongly that patchage should stick to just connecting things | 02:47 |
| drobilla | However if sufficient metadata was available to make it possible, automagically merging the "same" ports would be nice. | 02:48 |
| drobilla | I think it kinda sorta is somewhere maybe, but not sure, and not exposed by the jack metadata API universally in any case | 02:49 |
| drobilla | It's all kind of a mess :/ | 02:49 |
| milk | Catia allows for that, though I can understand separation of concerns. | 02:49 |
| milk | hehe | 02:49 |
| drobilla | I think -X alsa_midi is not the recommmended way for jack1. Not sure about 2. | 02:50 |
| drobilla | Yeah, some older stuff did too. I'm too lazy to figure out how, what can I say? :) | 02:52 |
| milk | i'd stick with JACK MIDI, but midi_capture_N is confusing :) | 02:52 |
| milk | fair enough :) | 02:52 |
| drobilla | Since anything that exposes aseq ports to jack, well, exposes them, it seems like not a great use of effort | 02:52 |
| drobilla | Oh, yes, on that I very much agree. The names situation needs sorting out. | 02:53 |
| drobilla | The metadata API is without question IMO the way to do this among many other things to make the general jack experience much nicer and automagic, but jack2 being a straggler on that one is holding it back currently | 02:53 |
| milk | fwiw, i just created a github issue for it | 03:41 |
| drobilla | I don't really pay attention to github issues, for the record, but okay | 04:16 |
| milk | ah, for jack2 ;) | 05:30 |
| milk | i'm loving ingen, now rethinking my while workflow | 05:31 |
| milk | er, whole | 05:34 |
| drobilla | awesome | 05:50 |
| milk | is there any way to panic kill/reset an instrument? sometimes when midi stops and/or is disconnect the instrument doesn't shut up. turning off processing quietens it, but turning on and it returns. it seems i have to delete it then readd it? | 06:56 |
| drobilla | No | 15:19 |
| drobilla | I suppose that would be a good idea, though a reliable panic in something like Ingen would be tricky. Countless ways the controls in a patch could simply be set in a way that's always audible if running at all | 15:20 |
| drobilla | or you mean one particular instrument plugin is stuck, so just a MIDI panic send would do? | 15:20 |
| drobilla | (all notes off and so on) | 15:20 |
| milk | ah, cc 120 does indeed shut it up, sorted :) | 20:35 |
| milk | or should that be 123 | 21:01 |
| milk | weird, trying different synths, a midi note to cc 120 or 123 stops sounds from casynth, but i can't then play the same notes again, they just click, while other notes do work. this adds up.. | 21:02 |
| drobilla | A 'reinstantiate plugin' option in Ingen would be nice | 21:17 |
| drobilla | Bugs will always happen. I've found myself wanting one a few times, but it doesn't fit so nicely into the protocol. I'll figure something out | 21:17 |
| milk | is the Carla rack gui known to work in Ingen? i'm seeking to see if the pizmidi vst plugins can work via that, and a gui box comes up for the Carla rack but is never filled with the interface. | 22:06 |
| milk | the note thing just seems to be casynth, the midi2cc123 stops hanging notes fine with zyn | 22:11 |
| drobilla | No idea | 22:14 |
| milk | fair dos | 22:17 |
Generated by irclog2html.py 2.13.0 by Marius Gedminas - find it at mg.pov.lt!