Did The Default MIDI Input Selection Change In 2017.01 ?

Author
Post
Essentials Only Full Version
AdamGrossmanLG
Max Output Level: -62 dBFS
  • Total Posts : 1436
  • Joined: 2014/07/13 03:40:34
  • Status: offline
2017/02/19 18:03:02 (permalink)

Did The Default MIDI Input Selection Change In 2017.01 ?

so now when I insert a softsynth, it's input by default is "Omni", not my keyboard controller.  So now I am getting EVERY synth with MIDI-Out information playing onto new softsynths I insert into my project.
 
 
#1

7 Replies Related Threads
    AdamGrossmanLG
    Max Output Level: -62 dBFS
    • Total Posts : 1436
    • Joined: 2014/07/13 03:40:34
    • Status: offline
    Re: Did The Default MIDI Input Selection Change In 2017.01 ? 2017/02/21 10:22:58 (permalink)
    bumpedy bump
    #2
    EddieLotter
    Max Output Level: -89 dBFS
    • Total Posts : 98
    • Joined: 2012/01/05 20:08:18
    • Location: West Hollywood, CA
    • Status: offline
    Re: Did The Default MIDI Input Selection Change In 2017.01 ? 2017/02/21 10:54:46 (permalink)
    This is how it has always behaved for me.

    Cheers
    Eddie
    #3
    AdamGrossmanLG
    Max Output Level: -62 dBFS
    • Total Posts : 1436
    • Joined: 2014/07/13 03:40:34
    • Status: offline
    Re: Did The Default MIDI Input Selection Change In 2017.01 ? 2017/02/21 10:57:30 (permalink)
    it used to default to my MIDI controller only.
    #4
    tenfoot
    Max Output Level: -53.5 dBFS
    • Total Posts : 2186
    • Joined: 2015/01/22 18:12:07
    • Location: Qld, Australia
    • Status: offline
    Re: Did The Default MIDI Input Selection Change In 2017.01 ? 2017/02/21 11:28:01 (permalink)
    It has only ever defaulted to my designated controller if I use a project or track template, otherwise defaults to omni (though it was labelled "none") .

    Bruce.
     
    Sonar Platinum 2017-09, Studio One 3.5.3, Win 10 x64, Quad core i7, RME Fireface, Behringer X32 Producer, Behringer X32 Rack, Presonus Faderport, Lemure Software Controller (Android), Enttec DMXIS VST lighting controller, Xtempo POK.
    #5
    Cactus Music
    Max Output Level: 0 dBFS
    • Total Posts : 8424
    • Joined: 2004/02/09 21:34:04
    • Status: offline
    Re: Did The Default MIDI Input Selection Change In 2017.01 ? 2017/02/21 11:58:18 (permalink)
    Same for me. It's always reverts to my MIDI ports because they are at the top of the list in MIDI devices.
    Try moving your controller to the top of the list. Maybe this changed but this is how it used to work. 

    Johnny V  
    Cakelab  
    Focusrite 6i61st - Tascam us1641. 
    3 Desktops and 3 Laptops W7 and W10
     http://www.cactusmusic.ca/
     
     
    #6
    tenfoot
    Max Output Level: -53.5 dBFS
    • Total Posts : 2186
    • Joined: 2015/01/22 18:12:07
    • Location: Qld, Australia
    • Status: offline
    Re: Did The Default MIDI Input Selection Change In 2017.01 ? 2017/02/21 12:42:03 (permalink)
    From memory only midi outputs can be re-ordered under preferences. Midi input order can be changed in the ttseq.ini file.

    Bruce.
     
    Sonar Platinum 2017-09, Studio One 3.5.3, Win 10 x64, Quad core i7, RME Fireface, Behringer X32 Producer, Behringer X32 Rack, Presonus Faderport, Lemure Software Controller (Android), Enttec DMXIS VST lighting controller, Xtempo POK.
    #7
    Musicman762
    Max Output Level: -90 dBFS
    • Total Posts : 44
    • Joined: 2015/03/06 15:35:08
    • Status: offline
    Re: Did The Default MIDI Input Selection Change In 2017.01 ? 2017/03/02 05:44:38 (permalink)
    I believe if you go to the Edits/MIDI Instruments in Preferences, you can pre-assign your Controller to Default, as well as configure the Output Port.  This particular Midi Preference is in serious need of updating though as it hasn't changed in probably 14 years.  The instrument definitions are old.  However, I believe the Default setting does not need to be configured, just assigned...
    #8
    Jump to:
    © 2024 APG vNext Commercial Version 5.1