From the original SynthMaker forum (2004–2014), with its members’ names and dates.
sunsynth ·
If u try 2 remotely control an App which gives/sends back it's actual status like:
value of a knob and when this knob is of course also draggable in the main app - u have a prob... it's a Midi loop 😮
Any ideas like delayed send or/and Midi buffer 2 prevent these??? I think a different MidiCC only isn't the solution?! 😉
Any thoughts?
cheers, SUNsynth
philter5 ·
hey walther, i think you have to explain some more what you exactly need. perhaps i can help you. or is this what youre looking for?
sunsynth ·
Thanks Phil,
maybe it's the local Midi Yoke Devices (forgot 2 mention i use that 'virtual' driver) 😮 If i have the spare time i will upload a diagram/screen of my actual biggest project ever 😉
Walter
philter5 ·
sunsynth wrote: Thanks Phil,
maybe it's the local Midi Yoke Devices (forgot 2 mention i use that 'virtual' driver) 😮 If i have the spare time i will upload a diagram/screen of my actual biggest project ever 😉 Walter
IF you have 2 or more MIDI Inputs/Outputs on your local midi device(s), then try to avoid using Virtual MIDI Rounting; better ( and CPU lighter) :just take a MIDI cable and hook it up from MIDI Out 1 to MIDI in 2 . This way you can be sure it´s not the virtual midi routing that brings problems and you save CPU 😉
rl ·
hmm... you could build some additional logic in.
some ideas: - on midi receive, only set the knob, but don't send midi from the knob - have a midi-through switch to control that behavior - only send midi when dragging/changing the knob from the UI and/or preset changes -..and the external app should also have an option to not send back midi data
sunsynth ·
@Phil: IF you have 2 or more MIDI Inputs/Outputs on your local midi device(s), then try to avoid using Virtual MIDI Rounting; better ( and CPU lighter) :just take a MIDI cable and hook it up from MIDI Out 1 to MIDI in 2 . This way you can be sure it´s not the virtual midi routing that brings problems and you save CPU
nope...I have 2 make it easy 4 the 'dummy' user 😉 *** @rl: very good thoughts 😀
some ideas: - on midi receive, only set the knob, but don't send midi from the knob - have a midi-through switch to control that behavior
i have realized that for 50% i think... 😮 will look at it again
- only send midi when dragging/changing the knob from the UI and/or preset changes
...already implemented
-..and the external app should also have an option to not send back midi data
not possible because third party one
Cheers guys... will report later Walter
sunsynth ·
After rearranging the chaos i found this working 4 me:
(Only ONE Master knob was the bad boy...)
philter5 ·
sunsynth wrote: After rearranging the chaos i found this working 4 me:
(Only ONE Master knob was the bad boy...)
thx for this. when i said use the midi cable instead of a virtual loopback device i was only talking about the testing, to be sure it isn´t the virtual device that brings problems...
btw: what the hell is that boolean primitive next to the drag inpurt? i´ve never seen this before 😕
sunsynth ·
Hi Phil,
it's THE de-bouncer from infuzion
not really needed here i think now - a fragment of the old chaos version...
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker