Resolume Forum

I'm getting a lot of crashes when I run FL Studio and Res3 at the same time. I get crashing with even simple test projects nothing to complex, though there are often very fast midi signals running from FL to Res3. It's Res3 that crashes first, then that in turn seems to bomb FL (Which is a very stable app) I don't know what's causing it, both programs run fine on their own, it may be midi yoke if this is the case then I'm really very worried as I have a lot of midi linking to do.

I'm praying it's my specs, perhaps either my graphics card or sound card isn't up to the multi tasking, but I can't see how to test this out so I can't tell for sure.

This is happening on a Vaio, but I've experienced similar problems with a better machine, at a guess I'd say it might be midi yoke that's somehow fouling things up.

Specs on this laptop are.'

Intel core two duo 1.83 GHZ

NVIDIA GeForce Go 7600

2 gig of Ram.

Make sure you don't have a MIDI feedback loop.

Whatever port FL is using to send info to Res 3, make sure it is set only as a MIDI output in FL. Disable input from that port in FL.

If you want to be absolutely sure, have FL and Res 3 using different MIDI ports, and use the MIDI OX routing control to send MIDI from one to the other.

That's a really good point.

I've been having midi assignment problems for month's now. I'll un assign a midi yoke port, then the next time I open the midi settings page it's re assigned itself, this happens with both FL and Res3 and they often Bomb when un selecting ports, I'd say %50 of the time.

Reconfiguring the ports, just doesn't seem to work, what ever changes I make, just reverse them selves as soon as I close the midi options windows. I've tried saving con fig files, but still nothing.

I'm going to have to re install them all, it's the only answer, then I'll route in future with midi ox.

Yeah it was feedback, uninstantiated midiyoke and replaced it with Mapple, works fine now. Thanks.