Strange bug using live.remote on EQ8

Aug 4, 2013 at 11:27am

Strange bug using live.remote on EQ8


This is a really strange problem, where I am using live.remote to change the “Filter Type” on the first EQ8 band. When I select a new filter type, and then group the EQ8, the filter type resets itself to a low pass. Here’s the patch.

– Pasted Max Patch, click to expand. –

I really dont understand why it’s doing this and would be really grateful for some guidance.

What’s even more strange is that I can see it creates and undo step when it resets the filter type, so something in the patch must be affecting it.



Aug 4, 2013 at 11:37am

First, without trying it in Live, I would say that you could use a live.object rather than the M4L.api.DeviceParameterRemote abstraction to do this. Concerning your bug, there may be an initialization like a [loadbang] when you group the device ?

Aug 4, 2013 at 1:55pm

Yes, it seems that for what Im trying to do, live.object might should work better (since the parameter changes im making are moving quite fast and I hear live.object uses less cpu). However, it does not. I have a bunch of parameters mapped and theyre moving quite fast, but it’s really locking up my patch now. Any idea why this might happen?

Aug 5, 2013 at 11:20am

Now I have started to use live.object, however, it is adding things to the undo queue. Is there any way around this, to stop this happening?


You must be logged in to reply to this topic.