• SONAR
  • MIDI Issue - Input Selection Being Ignored (p.3)
2015/05/14 02:53:09
brundlefly
This only happens if you have "Aways Echo Current MIDI Track" enabled in preferences. This causes the input of new MIDI tracks to default to "Omni" which is the same as AllInputsOmni. If you don't have Always Echo enabled, new track inputs will default to None so you'll be starting from the correct state in the first place.
 
 
 
 
2015/05/14 03:09:20
AdamGrossmanLG
brundlefly
This only happens if you have "Aways Echo Current MIDI Track" enabled in preferences. This causes the input of new MIDI tracks to default to "Omni" which is the same as AllInputsOmni. If you don't have Always Echo enabled, new track inputs will default to None so you'll be starting from the correct state in the first place.
 
 
 
 


but i want to be able to have that option on!   :)
2015/05/14 10:33:04
brundlefly
So did Silktone's Toggle-Input-to-None-and-Back workaround solve your problem?
 
I'm finding that even with Always Echo enabled (i.e. starting with Input = Omni on a new track) and then setting the input to <Controller> - Omni or <Controller> - <MatchingChannel>, I only get the false confidence recording clip outline; no notes show in the clip while recording, and nothing is actually recorded or echoed to the synth. I don't have to toggle the Input to prevent actual recording.
 
I don't have multiple MIDI interfaces connected to my DAW at the moment, but I have in the past so there are entries for them in TTSSEQ.INI. Maybe that's all it takes to make the problem go away...?
 
I'll try to look into this more later.
2015/05/14 10:34:31
AdamGrossmanLG
i will test it later and confirm my findings :)
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account