Sebastián Cordovés

On 12/29/2022 at 2:06 AM, SirWillyDS12 said:

Kevin made a very good point here...

 

I use MidiQuest VST with my keyboards and I have to disable the midi input to route them to MidiQuest... (Forbidden Windows driver sharing...) Then use a third party midi loop back driver to interface with Cakewalk... So if Cakewalk would always enable all midi devices that would be a nightmare...

But I 100% agree that Cakewalk should remember disconnected devices and not re-assign the next available driver when a device is not present... This can also be a real pain when I open a project without one of my keyboards on...

I think moonbooter means that the ports are always active in the preferences, not always selected in the preferences.

I'm trying toCakewlak solves the MIDI Port problems for a long time.

Check this thread, there is some tips there than can help in your sitution:

22 hours ago, moonbooter said:

I am dealing with this problem for over 20 years and so far there is no satisfying solution. I also have over 35 different Midi-devices in my setup and cakewalk rotates ports from time to time. BUT: I think the more important problem is, that Cakewalk deactivates MIDI ports on his own. So, if You reopen a project and the device is NOT manually re-activated in the MIDI settings, THEN the ports will be exchanged (not before). So this problem will NOT take affect when You activate all necessary ports BEFORE loading a project. So far my experiences. Other DAWs activate always all available MIDI ports at startup. They have only the option to deactive selected ports so that VST plugins can directly speak to a connected hardware synthesizer.

My wish: Please let Cakewalk always activate ALL available MIDI-ports automatically.

AND: The problem, Sebastián described, takes also effect on the Midi-in presets. So I personally have to re-select my masterkeyboards and midi controllers every time I start Cakewalk with different connected hardware (midi ports).

I reported this problem to Cakewalk support 6 months ago, after a month I received a mail asking if the problem was solved in the last upgrade, I explained everything again, and they told me that will pass the problem to the technical support (I don't know who was answering my report, I thought that technical issues were managed by technical support).
Anyway, I didn't had any news since that...

 

22 hours ago, sjoens said:

If you have many MIDI devices, why not use a MIDI interface? I think they are (over priced but) still available.

Just because I don't want... the problem is Cakewalk, it should work with modern hardware. Other DAWs and MIDI software works properly (I tried Ableton Live, Reaper, several synth editors, etc, all of them remembers the MIDI port configuration).

But the multi-pot interface is USB?
Because I think the problem is related to that (I used to have a parallel multi-pot MIDI interface and did not have the problem), but with USB, ports get mixed all the time, even if it is a multi port one. I have 2 Korg synths that have 2 ports each, and the order of those ports are mixed even if it is the only synth I'm using.
But, I think for you, making ttsq.ini read only should work as you have only one USB device connected all time.

The problem happens with MIDI ports of USB devices.

If you don't have all the devices you used in the project or template turned on, Cawalk just shift all port assignmets.

Even if you turn all the devices on, sometimes Cakewalk just mix all the inputs and outputs. For this particular case somebody told me that setting ttsq.ini to read only after stting things up will keep the order of the ports, and it works to some extent, but if you have one device turned off, everything gets messed up again.

Check my original post (and the steps for make ttsq.ini read only):

Hi, I have a topic about MIDI input ports being messed, for almost a year... Some months ago I contacted Cakewalk support and exchanged a few mails with them but I haven't much news about it.

May be you can contact them to make some pressure

OK, I wrote a note directly to Cakewalk support, lets see what they say....

Hi all,

I come back to ask if this problem can be solved.

Setting ttseq.ini to read only is not very helpful. It makes Cakewalk sets the ports in the correct order, but only  helps when I turn on all the synths, because as soon as I have one turned off the MIDI routing becomes a mess... (as I explained in the first post).

I know this can be solved because I have several other MIDI software that works properly and remembers the MIDI port assignments.

I don't know if it is a more direct way to make a feature request (or should I call it bug report?) to Cakewalk/Bandlab.

On 10/2/2021 at 2:40 AM, Kevin Perry said:

There's a bit of a hack that I think works (I've run into the same with my control surface, which I rarely turn on):

- Turn everything on
- Run Cakewalk and set up the MIDI ports as you want them to be set up
- Close Cakewalk
- Open Windows Explorer and navigate to %APPDATA%\Cakewalk\Cakewalk Core
- Find ttseq.ini, and right click on it, and choose Properties
- Tick Read-Only and click OK

Of course, if you want to make changes to your MIDI setup, you'll have to un-Read-Only it, then start at the first step here again.

Thank you Kevin, I will try that.
If it works it will do my life a lot easier

Hi:

I'm a long time Cakewalk user. In the past I used to have a multi port MIDI interface (now obsolete) and connect all my synths there.

Now I don't have that MIDI interface anymore and, as most modern synths have USB MIDI, I connect all my synths directly to the computer.

The problem is that not always want to use all my synth, sometimes I just turn on a single one and Cakewalk just mess all MIDI port selection on the MIDI tracks. The MIDI data (notes, etc) is sent to the wrong synths. I have to set the MIDI port for every MIDI track every time.
Even if  I turn on all my synths, sometimes Cakewalk  change the order of MIDI ports and again I have to set the MIDI port for every MIDI track.

Same happens when sending MIDI clock to my drum machine, after opening a saved project the MIDI ports are in a different order and the MIDI clock is sent to a different port so my drum machine doesn't start.

Also if I have set an instrument definition for a MIDI port, I lost that assignment...

So, please make Cakewalk remember the MIDI port settings. If I have a MIDI track and the MIDI port output is set to a MIDI port named SynthX (all my MIDI ports have the name of the synth), next time I open the project that track should be assigned to the MIDI port SynthX, and if that MIDI port is not available (not connected), should be routed to a dummy MIDI port, not to other MIDI port, if I want to route that MIDI data to another MIDI port I will do it myself manually (letting Cakewalk choose a random MIDI port doesn't help).

Thank you!