You are here

Add new comment

Awesome helpful software, Thanks!
but... I am writing to ask for help clearing up my confusion about the difference in functionality between the Patchbay window that opens when you click the patchbay button, and the Connect button that opens the Connections window. When would one use patchbay versus connect to set up the desired connections? It seems to this newbie like they do almost the same thing but somewhat differently, and maybe the patchbay can persistently saved, but not so apparently for the connections. There is some inner logic clearly working to decide what items get displayed in the dropdown lists of both windows but I can't figure it out. I am also confused about what's an input and what's an output.

For example: I have a Yamaha WX5 wind controller. I want to hook it up to send MIDI in to my Creative Soundblaster card (which has a MIDI cable plugged into the joystick port with a split output cable for MIDI in and MIDI out, with an Ubuntu jaunty computer running jackd compiled for alsa. I have also got fluidsynth running, with two virtual synthesizer instances set up inside. I want to be able to play the MIDI controller, to a) cause the MIDI data to go to one or the other of the two Qsynths (and be able to easily change which Qsynth in performance) and b) send output to be played by the Soundblaster's audio out to my external speakers. Simultaneously I want c) the same MIDI data routed out the Soundblaster's MIDI-out port so I can send it to an external Yamaha TX7 synthesizer also.

So how do I use the interfaces for the patchbay and the connect windows to specifiy what connects to what to make the connections, what will be persistent if I save the patchbay as a file, and what is performance-changeable and non-persistent?
Again, thanks so much for your great work! I appreciate any lore for newbies you can give me, to facilitate my actually having a solid grip on things.
-Dave Britton