hello,
This happens in all versions, I think.
I have a PCI soundcard + onboard soundcard. On startup, the system will
allocate randomly which card becomes /dev/dsp and which becomes /dev/dsp1.
This causes problems with Jack not starting because the device locked into
jack's config is no-longer the intended one.
Also,in 1.3.7 I have seen my Edirol midi keyboard controller (ID'd as "PCR")
become the output device for jack ! (Jack did not start unsuprisingly)
Now I know what is happening, the random and mysterious "jack won't start"
messages make sense.
Same problem occurs with /dev/*midi* allocations. This causes problems
where the /dev/*midi* device is hard-coded in the config , such as with a
synth called beatrix.
I've read this is UDEV behaviour by design and can be overcome by
hard-mapping device hardware ID's to specific /dev/ nodes.
Can anyone confirm that udev is the cause and the solution?
May be worth writing this up in the FAQ? I'll document the udev changes I
have to make.
s~
_________________________________________________________________
Like the way Microsoft Office Outlook works? Youll love Windows Live
Hotmail.
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_outlook_0507
_______________________________________________
64studio-devel mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-devel
