1 (edited by guix 2024-05-29 21:13:40)

Topic: Why you can't map a Fader for an Output in a single address in OSC?

Why you can't map a Fader for an Output in a single address in OSC?

Seems this is not possible. If only the implementation would address objects in a more logical way, Something like:
/Input/AN1/Fader
/Software/AES/PFL
/Output/ADAT8/Meter
/Output/ADAT8/Mute
/Output/Main/Mono
/Snapshots/Mix/1
/DUREcorder/stop
/Groups/Mute/1

Is this not possible to implement?

Re: Why you can't map a Fader for an Output in a single address in OSC?

has been discussed already in multiple threads.

Why you can't map a Fader for an Output in a single address in OSC?

You can do this already.

Look here and the following posts:
https://forum.rme-audio.de/viewtopic.ph … 41#p218141

“Do It For Her”
My Gear: Bontempi Magic light Keyboard

Re: Why you can't map a Fader for an Output in a single address in OSC?

Well not in single commands...
You always need multiple commands for things to work and that is the down side.
i mean how many commands you need to move a fade  to 0 db? should be one :- )

Re: Why you can't map a Fader for an Output in a single address in OSC?

i mean how many commands you need to move a fade  to 0 db? should be one :- )

Is exactly… one.

Read carefully!

https://forum.rme-audio.de/viewtopic.ph … 99#p218199

“Do It For Her”
My Gear: Bontempi Magic light Keyboard