[sdiy] MIDI CC with Pots

rburnett at richieburnett.co.uk rburnett at richieburnett.co.uk
Mon Oct 6 17:17:54 CEST 2014


Hi Paul,

The synth doesn't send out the CC again.  The synth processes the 
control change due to it's internal local connection between the control 
that was turned and the synth engine, and sends out a CC so that the 
tweak can be recorded, but the sequencer then re-transmits this CC 
message back out of its MIDI out port so that it ends up arriving back 
at the synth via it's MIDI IN port to possibly get processed again.  
This is the situation I was discussing.  And whether "local off" at the 
synth or dissabling thru functionality at the sequencer were the 
preferred way to deal with this?  Or indeed whether people even worry 
about it?

-Richie,


On 2014-10-06 16:06, Paul Maddox wrote:
> Richie,
> 
>> On a related note, how are people dealing with the MIDI loop problem 
>> these days when tweaking real-time controllers and recording to their 
>> sequencer?
>> 
>> To use Paul's example of a bassline playing over 2 bars and someone 
>> tweaking the "filter cutoff" control on a synth...  This manipulation 
>> of the control will change the filter setting directly inside the 
>> synth, but will also result in CC messages being sent out the synth's 
>> MIDI OUT port to the sequencer for recording.  The sequencer then 
>> feeds these CC messages back out it's MIDI OUT port and they arrive 
>> back at the synth's MIDI IN port, where they presumably get acted on 
>> and set the filter cutoff frequency inside the synth again!
> errr, why?
> 
> Sorry, most synths I know when they receive a CC don't send it "out"
> again, only to the 'thru' port.
> 
> Paul
> _______________________________________________
> Synth-diy mailing list
> Synth-diy at dropmix.xs4all.nl
> http://dropmix.xs4all.nl/mailman/listinfo/synth-diy



More information about the Synth-diy mailing list