I'm attempting to sync Resolume's midi clock to Maschine but I'm not having much luck. I've got the midi communication set up but the Resolume bpm skips about all over the place. Maybe I'm expecting too much from it - havent used it much before. I am also sending midi messages from Maschine to trigg...

Dead basic issue here - can anyone replicate: I have a 1 bar midi loop in Live with just one note in, triggering a clip in Resolume. If I set the clip in Resolume to piano mode and make the note in the midi clip a whole bar long, it becomes quite unreliable. Anyone else seeing this? I'm using a macb...

Can you try sending Resolume 3 values greater than 1, eg 1.02 1.02 1.8

I think this causes a crash.

Thanks for looking anyway - I've realized the strange results were because you need to send a bang to the OpenSoundControl object to send your message.

Not sure about the crash yet but I'll get there or at least somehwere in the end!

I actually tried using the resolume.dispatcher maxforlive device which I got from the website somewhere. Having quite strange results though - sending my osc data doesn't seem to work until I stop or start live's transport. Then the messages get through. I'm sure its user error but I just don't get ...

I've attached the patch but its in a very early state!

To try it unzip the file, open the text file and paste into an empty m4l audio effect device. You need the OSC external.

I managed to crash Resolume by sending OSC values for in/out/position points for a clip.

I was editing a m4l patch and probably sent it some non sensical values but thought you'd want to know.

Where's the best place to report bugs?

I can't export from Ableton Live using DXV. I'm getting crashes - I attach some kind of crash report.

I'm using leopard 10.5 + Quicktime 7.6.2 + Ableton 8.1.5

Any ideas?

Sending the values isn't the problem!

Its detecting the file path of a clip to display the waveform.

Hence the thread......

No not FFT, just in/out and cue points