On Saturday 02 February 2008 16:04:37 Arnold Krille wrote: > Hi, > > Am Samstag, 2. Februar 2008 schrieb Hartmut Noack: > > verymeta@xxxxxxxxxx schrieb: > > > $ jackd -d freebob > > > without the Solo plugged in, Jack won't start. > > You want jack to use the device and wonder that jack wont start when the > device is not there??? I think that what he was getting at is that he was using this as a test that the device was at least being seen because the messages were different depending on whether the card was attached or not when trying to start jack. > > > > But if the Solo is > > > plugged in Jack will start, and I get the messages: > > > JACK compiled with System V SHM support. > > > loading driver .. > > > SSE2 detected > > > Freebob using Firewire port 0, node -1 > > > libiec61883 warning: Established connection on channel 0. > > > You may need to manually set the channel on the receiving node. > > > libiec61883 warning: Established connection on channel 1. > > > You may need to manually set the channel on the receiving node. > > These messages are not directly from freebob but from some library-level > below. And they mean nothing, at least nothing freebob is concerned about. > > > > Also, I don't know if this is meaningful in any way, but when I open > > > qjackctl and go to setup, the 'input device', 'output device', 'input > > > channels', and 'output channels' drop-down boxes are greyed out. > > > > the greyed out options do not apply to the freebob backend, if there is > > something to set, freebob does it. > > The same applies to the other backends jack has: QJackCtl shows the boxes > only if the backend supports the options... > > Arnold all the best, drew _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
