Slight Problem with FruityLoops (3.5)

Riggar · Post by **Riggar** » Sat Sep 21, 2002 8:49 am

Using FruityLoops (v 3.5) running 'stand alone' as a midi driver into pulsar to fire of one or two synths for basic beat etc. Problem is when I want to 'adust' something in Pulsar .... fruity stops ?

why is this ? and is there a solution.

its a bit like wanting to 'play in the background' setting a la Cubase

cheers for your thoughts

Riggar

marcuspocus · Post by **marcuspocus** » Sat Sep 21, 2002 11:27 am

Yes, same thing exist in fruity, go in the audio panel, and uncheck the 'Auto Close Devices' just beside your choice of drivers.