Forums > Max For Live

Strange bug using live.remote on EQ8


newtfish
August 4, 2013 | 11:27 am

Hi,

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.

Cheers

N


Stephane Morisse
August 4, 2013 | 11:37 am

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 ?


newtfish
August 4, 2013 | 1:55 pm

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?


newtfish
August 5, 2013 | 11:20 am

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?

Viewing 4 posts - 1 through 4 (of 4 total)