On Fri, 30 Jul 2004 14:27:55 -0700 Russell Hanaghan <hanaghan@xxxxxxxxxxxx> wrote: > On Fri, 2004-07-30 at 14:03, Andrew Dahlin wrote: > > On Fri, 30 Jul 2004 12:23:06 -0700 > > Russell Hanaghan <hanaghan@xxxxxxxxxxxx> wrote: > > > > > Have a question... > > > > > > I'm trying to move ever towards eliminating Winblows. I have to come up > > > with a *bullet proof* method of running a solid midi seq alongside the > > > Delta for my fx and live audio processing. > > > > > > None of the midi apps out there seem to work very well with softsynths > > > used for the GM instrument set. Fluidsynth, etc has it's issues and so > > > on. I don't own any hardware modules and don't want to if I dont have > > > to. I have been using Roland Virtual sound canvas, Yamaha sy-xg, > > > wingroove, Edirol Hypercanvas, etc on Win XP with Sonar for this > > > function and it works well. > > > > > > I'm wondering, how might I run a SBlive next to the Delta and not have > > > them conflict. I guess I would have to run the SBlive in the OSS layer? > > > Then suffer from realtime issues again? Point being in previous > > > experimentation, the SBlive with a sound font loaded, at least behaves > > > more like an actual piece of hardware...It might play a little nicer > > > with Muse or Rosegarden... > > > > > > R~ > > > > > > > > > i have my onboard sound card (ens1371) running at the same time as my audiophile card. both are using alsa and i run jack ontop of my audiophile. it's pretty easy to do and i'm not sure why more people don't do it. > > > > --Andrew > > So the second card just has access direct to the alsa drivers but does > not affect Jack's operation at all on the other? > > R~~ > i've never noticed any problems with jack. basically, alsa runs on top of both cards. i tell jack to use card 0 (my audiophile) and it does happily. i still have card 1 available, so when i want to output to that, i tell the program to output to that one. kinda looks like this: jack -> alsa's ice1712 driver -> card 0 alsa'a ens1371 driver -> card 1 (just wrote that out to point out that the alsa driver has access to the card, not the other way around. technicalities/sorry if i mis-understood ;)
