Strange "routing" problem moving from X3

Author
Post
Essentials Only Full Version
timboalogo
Max Output Level: -89 dBFS
  • Total Posts : 54
  • Joined: 2004/12/29 08:45:15
  • Status: offline
2018/04/11 18:54:06 (permalink)

Strange "routing" problem moving from X3

In X3, I was able to start Sonar without my Advance 49 turned on. If I decided to record, I'd turn it on and receive a "do you want to load" message. There is no such message in CB.
 
Additionally, if I open a project without the Advance on, all the midi tracks inputs are lost. When I turn on the midi controller, the tracks do not update themselves and I have to manually reroute all the inputs, and I've seen it where I've had to reroute the audio outputs.
 
Has anyone else come across this or is there something I'm missing?
 
Thanks,
Timbo
#1

4 Replies Related Threads
    Cactus Music
    Max Output Level: 0 dBFS
    • Total Posts : 8424
    • Joined: 2004/02/09 21:34:04
    • Status: offline
    Re: Strange "routing" problem moving from X3 2018/04/11 18:59:27 (permalink)
    It is actually up to the midi driver for that device how smoothly these things work. Example, My Roland controller can be turned on after Sonar is running and I get that "do you wish to connect" message. 
    My Akai Keyboard does not and I have to close Sonar and re open every time. Same computer. 
    So while using the Akai I always try and make sure it is on before I open Sonar. Simple. 

    Johnny V  
    Cakelab  
    Focusrite 6i61st - Tascam us1641. 
    3 Desktops and 3 Laptops W7 and W10
     http://www.cactusmusic.ca/
     
     
    #2
    azslow3
    Max Output Level: -42.5 dBFS
    • Total Posts : 3297
    • Joined: 2012/06/22 19:27:51
    • Location: Germany
    • Status: offline
    Re: Strange "routing" problem moving from X3 2018/04/11 20:56:05 (permalink)
    They have tried to improve MIDI detection in some update (if I remember correctly, during 2017 updates). But they have just made it worse.
     
    Even in case it asks, I have not seen Sonar changes input settings in already opened project.
     
    I have thought that all is "natural" and comes from drivers. Till I first was surprised other DAW has no problem with that and later by programming MIDI communications myself.

    Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro
    GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB
    RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc.
    www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
    #3
    timboalogo
    Max Output Level: -89 dBFS
    • Total Posts : 54
    • Joined: 2004/12/29 08:45:15
    • Status: offline
    Re: Strange "routing" problem moving from X3 2018/04/11 21:08:57 (permalink)
    Thanks guys. Funny thing is that it asked in X3 and doesn't anymore.
     
    Learning curve!
    #4
    timboalogo
    Max Output Level: -89 dBFS
    • Total Posts : 54
    • Joined: 2004/12/29 08:45:15
    • Status: offline
    Re: Strange "routing" problem moving from X3 2018/04/22 18:56:10 (permalink)
    Sorry to resurrect this, but it happened again and I realized I'd forgotten to tell you that not only are all the midi inputs messed up, but each midi output is moved -1 up the list of midi/audio tracks. So I've got the drums playing the bass and the piano playing the drums etc. Sounds cool, but required 10 minutes of swearing and rerouting ... this never happened in x3.
    #5
    Jump to:
    © 2024 APG vNext Commercial Version 5.1