M4L using poly~: deferlow isn't working
I'm trying to take the total tracks in Live, and update a poly~ object which contains track parameters (volume, panning, etc) for each track which I can then set from my hardware controller.
My patch is working, but when I add or delete tracks in Live, it sends the typical error: "Setting the Id cannot be triggered by notifications. You will need to defer your response." from the objects and observers in the poly~. I've tried using deferlow objects in various places in the patch (i.e.: between path and object), but the error keeps coming up in the Max window; obviously the patch is open in Max for this to be shown.
I think the issues might be coming from the poly~ object which contains the track setting/observing object errors.
Can anyone take a look at my patch and see what the issue is?
Anyone?
I guess you need deferlow within the subpatchers 'p trk_VOL_set' etc.
When I put a deferlow between live.path and live.observer/live.object, it stills gives the "setting the id" error.
Moving, duplicating, or deleting tracks all throw the error message when the M4L patch is open in Max.
The timing is screwed when the patch is open to edit, ignore the errors that occur unless you see them when the device is running in Live....
Cheers
D
"ignore the errors that occur unless you see them when the device is running in Live…."
If I do that, the patch stops working correctly because the errors mess up the IDs getting sent to the tracks.
After a bit more searching, I think it might be related to "unchecking the ‘Use persistent Mapping’ option" in the inspector of live.observer and live.object. Appears to be working after a short amount of testing.