e-vee

While working with the Vbap Doppler audio effect in Ableton, I want to get the the values from the x-axis, y-axis and radius and store them in three separate coll objects in the following format:

"[index number] [current_song_time] [value]"

 Setting the Id cannot be triggered by notifications. You will need to defer your response."

 forum post but it didn't solve the problem. From the subpatch "debug", it was clear that my method of storing in [coll] does work.

message

button

comment

prepend

number

join

counter

coll

deferlow

toggle

gate

change

metro

inlet

flonum

outlet

live.path

live.observer

loadbang

live.object

route

unpack

loadmess

While working with the Vbap Doppler audio effect in Ableton, I want to get the the values from the x-axis, y-axis and radius and store them in three separate coll objects in the following format:
"[index number] [current_song_time] [value]"

I get the error: "live.observer: Setting the Id cannot be triggered by notifications. You will need to defer your response."
I read about it in this forum post but it didn't solve the problem. From the subpatch "debug", it was clear that my method of storing in [coll] does work.

Is there anyone willing to help me?


Dear Maxers,
While working with the Vbap Doppler audio effect in Ableton, I want to get the the values from the x-axis, y-axis and radius an

live-observer-values-to-coll-defer-error

Strange, but that worked :) Thanks! Could you maybe explain why this method works and mine didn't?

Apparently, a patch can only observe one parameter/object at the time? Only the right [coll] gets filled during Ableton playback.

The patch i posted was just to point to mistakes :

1- using too many live.objects to form one id for one live observer

2- avoid using live objects when possible, like taking play position from plugsync~

instead of get current_song_time, triggered from 3 sources

3- metro 100 banging property value makes no sense, 

when either object it observes changes, or it's value, and not otherwise

sending it repeatedly property value produces nothing.

If you want to speed limit parameter capturing, then use speedlimit, 

if it is for creating some kind of automation, bang current output value of live observer at certain interval and capture either only if value changed or allways,

There is no limit of observing only 1 parameter

have look at this one, capturing at set interval and adding only changed values to coll :

fom initial patch you posted it is not actually clear how you want values to be captured

The patch i posted was just to point to mistakes :

1- using too many live.objects to form one id for one live observer

2- avoid using live objects when possible, like taking play position from plugsync~
instead of get current_song_time, triggered from 3 sources


3- metro 100 banging  property value makes no sense, live.observer outputs something
when either object it observes changes, or it's value, and not otherwise
sending it repeatedly property value produces nothing.
If you want to speed limit parameter capturing, then use speedlimit, 
if it is for creating some kind of automation, bang current output value of live observer at certain interval and capture either only if value changed or allways,
by inserting change object or not

4- that complicated trigger,  join - etc 
and so on
There is no limit of observing only 1 parameter
have look at this one, capturing at set interval and adding only changed values to coll :


fom initial patch you posted it is not actually clear how you want values to be captured
---
P.S.
maybe you could use this

Thanks so much! This patch is exactly what I meant.

1. Ok, damn, that last patch you send me does the job so much more efficient 🙈

2. I didn't know about plugsynth~, that's indeed what I needed.

Thanks for the effort of explaining, it taught me a lot :)

Thanks so much! This patch is exactly what I meant. 

live.observer values to coll, defer error