Sonar X3 saving MIDI channels problem

Author
pbajon
Max Output Level: -90 dBFS
  • Total Posts : 13
  • Joined: 2010/07/28 09:54:51
  • Status: offline
2014/04/19 19:54:47 (permalink)

Sonar X3 saving MIDI channels problem

Hi guys. I don't know if any of you have encountered this problem but in the past, when I was using earlier versions of Sonar Producer this particular problem has never existed. I have one song that I use 4 MIDI controllers with. The project features 17 tracks all together out of which 4 tracks are being played LIVE using those 4 MIDI controllers. All the MIDI Devices are listed and checked within the Preferences section of the Sonar X3. Each MIDI controller transmits on MIDI Channel 1. So, the setup looks like this:
 
Track 10 - Kurzweil PC3x - MIDI Channel 1
Track 11 - Novation Supernova II - MIDI Channel 1
Track 12 - Roland GAIA - MIDI CHannel 1
Track 13 - Akai MPK 49 - MIDI CHannel 1
 
When all is set and done I do test overall performance and all is well. No problems. I save the song "Save As" (typical Sonar project file format). I close the Sonar X3.
 
Next day I turn on my PC, connect all the MIDI controllers, and start the Sonar X3. I open the saved project, and ........ all the MIDI channels assignments to my MIDI controllers are totally messed up. Upon the examination I get something like this (or variation of it):
 
Track 10 - Kurzweil PC3x - MIDI Channel 2
Track 11 - Kurzweil PC3x - MIDI Channel 4
Track 12 - Roland GAIA - MIDI Channel 2
Track 13 - Akai MPK 49 - MIDI Channel 1
 
Do you guys have any idea why is this happening? It seems like Sonar X3 does not properly save the MIDI Channel assignments. It's weird. I have NEVER experienced anything like this. If I won't be able to fix this then I cannot go on the stage with a LIVE performance because I cannot rely on proper MIDI Channels (and controllers) assignments. Thanks in advance for all of your help. 
#1

5 Replies Related Threads

    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: Sonar X3 saving MIDI channels problem 2014/04/20 02:18:39 (permalink)
    I could see ports getting spontaneously reassigned when USB devices get enumerated differently by Windows, but I've never seen input channel assignments change to a different specific channel (maybe from channel 1 on a specific port to All Inputs - Omni, but not to 2 or 4). In any case, I strongly recommend that you have all USB-connected controllers already connected and powered up before you boot your PC to help prevent issues like this. If you're in the habit of connecting them after the fact, I'm surprised you haven't encountered issues before now.

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #2
    Splat
    Max Output Level: 0 dBFS
    • Total Posts : 8672
    • Joined: 2010/12/29 15:28:29
    • Location: Mars.
    • Status: offline
    Re: Sonar X3 saving MIDI channels problem 2014/04/24 11:03:15 (permalink)

    Sell by date at 9000 posts. Do not feed.
    @48/24 & 128 buffers latency is 367 with offset of 38.

    Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.4,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),4 x Seagate ST31500341AS (mirrored),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5.Maschine Studio+Komplete 9 Ultimate+Kontrol Z1.Addictive Keys,Izotope Nectar elements,Overloud Bundle,Geist.Acronis True Image 2014.
    #3
    robert_e_bone
    Moderator
    • Total Posts : 8968
    • Joined: 2007/12/26 22:09:28
    • Location: Palatine, IL
    • Status: offline
    Re: Sonar X3 saving MIDI channels problem 2014/04/24 11:18:01 (permalink)
    Whenever I plug midi devices into the back of my computer, using USB connectors, after I finish I create a text file that lists what devices are connected to which port on the back panel of the computer.
     
    That way, when I move my gear for a gig or for whatever, I always know what has to get plugged into which port.
     
    Some of my older stuff used to want me to install drivers again, after plugging into a wrong port, so that's why I started doing the text file.
     
    Other than moving gear, I always have everything connected.
     
    Bob Bone
     

    Wisdom is a giant accumulation of "DOH!"
     
    Sonar: Platinum (x64), X3 (x64) 
    Audio Interfaces: AudioBox 1818VSL, Steinberg UR-22
    Computers: 1) i7-2600 k, 32 GB RAM, Windows 8.1 Pro x64 & 2) AMD A-10 7850 32 GB RAM Windows 10 Pro x64
    Soft Synths: NI Komplete 8 Ultimate, Arturia V Collection, many others
    MIDI Controllers: M-Audio Axiom Pro 61, Keystation 88es
    Settings: 24-Bit, Sample Rate 48k, ASIO Buffer Size 128, Total Round Trip Latency 9.7 ms  
    #4
    dougalex
    Max Output Level: -86 dBFS
    • Total Posts : 244
    • Joined: 2003/11/18 14:22:24
    • Status: offline
    Re: Sonar X3 saving MIDI channels problem 2014/04/24 16:48:33 (permalink)
    Windows assigns numbers to ports as the devices get connected.
    If you boot computer with the devices connected, the devices can get assigned port numbers in any random order, and you have no control over the port number assignments and Sonar can only guess what device goes to what track input. Some programs (like Brainspawn Forte) have an option to let you just fix the port mapping manually, (regardless of how Windows assigned port numbers), but Sonar lacks this feature.
     
    I solved the problem in Sonar by this method:
     
    I always boot computer with no midi devices connected (including sound card because it often has a midi driver). Then I plug in the midi devices in SAME order, to same ports. (Pausing to make sure a device is recognized before plugging in next device). I use 4 USB midi controllers connected to a USB hub, and I plug in the hub first (making sure nothing is connected to hub), then connect midi devices to the hub (same port, same order). This method works every time.
     
    One you determined the order and then fixed up the track midi inputs (for the last time ) in Sonar, then from then on, if you forgot to disconnect everything before boot up (and the Sonar Midi inputs are messed up), DO NOT TRY TO FIX THE MIDI INPUTS IN SONAR (you are just chasing your tail). Just make sure you disconnect everything reboot and do correct orderly boot up and connections.
     
    By trial and error I found the "connection order" that nicely puts the topmost keyboard at beginning of the picklist in Sonar. (Because I found it annoying if the list was not in "top to bottom" order).
     
     
     
    #5
    pbajon
    Max Output Level: -90 dBFS
    • Total Posts : 13
    • Joined: 2010/07/28 09:54:51
    • Status: offline
    Re: Sonar X3 saving MIDI channels problem 2014/05/01 13:34:55 (permalink)
    Hi guys,
     
    Many thanks for all of your input. A truly valuable info indeed, but I have decided to ditch the separate USB connections, and hook up all of my synths to my MIDISport 8x8 Midi patchbay interface. When I did that, all the Midi port assignment problems have disapeared. There is only 8 Midi channels available and four of my synths use 4 Midi Ins and Outs from that Midi patchbay. It doesn't matter when I turn on any particular synth. It's always connected to one of the Midi Ins of the MidiSport 8x8. The key to have a success is to turn on the MidiSport 8x8 Midi patchbay BEFORE turning on the PC. After starting Sonar, the DAW automatically detects the MIDI Sport 8x8 and corresponding assigned channels, and it doesn't re-assign the different channels to different synths. Everything is locked.
     
    So, I think I'm gonna use this particular setup (8 channels IN and 8 channels  OUT of MIDISport 8x8 midi interface) since it works for me, but it is definitely worth saving all of the above info from you guys, just in case the future might require to use several USB Midi INs and OUTs.
     
    Thanks again for trying to help.
    #6
    Jump to:
    © 2025 APG vNext Commercial Version 5.1