OSC Crash

[gavspav]

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?

[Tschoepler]

Could you upload the patch as well?
By doing so I could check if the problem is present on the PC side as well.

best,
jake

[gavspav]

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.

[Joris]

Thanks for the find Gavspav, and thanks for the testing Tschoepler.

Overall posting on the forum is a good way to report a general bug. If you think the problem is specific to your machine, you can use the Feedback option in the preferences to send us your logfile. If you want a quick response you can of course always mail us at support[at]resolume[dot[com].

Joris

[gavspav]

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 it at the moment.

[Tschoepler]

I don't have M4L just plain MAX. But nonetheless I was able to have a look at the patch and the message that get's send out seems to be right: /layer1/clip1/audio/position/values
In my case the three values were all set 0.224116 but it didn't crash Resolume. You could try to record what is going through the OpenSoundControl and check the lines when Resolume crashes. Sorry I couldn't help in more detail.

[gavspav]

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!

[gavspav]

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

I think this causes a crash.

[Tschoepler]

nope it doesn't. just sets both in and out points to the very end of the clip.