“Create new track with next channel” assigns random channel

[paulcristo]

When I use the “Create new track with next channel” command on a MIDI track, Logic assigns a random channel to the new track and sometimes a completely different MIDI device to the new track. Depending on Logic’s mood, it might assign the channels in descending order from channel 16, skipping channels along the way. It rarely will assign the actual next channel to the new track.  
I’m wondering if this is a known issue and if there’s a way to fix it. 

Edited February 28, 2023 by paulcristo

[polanoid]

Can't reproduce that, not even in your Logic version (10.4.8). We need more information it seems. Maybe post an example project in which this happens? 

[David Nahmani]

It works as expected here too. Can you share your Logic file and give instructions on how to reproduce? 

[paulcristo]

14 minutes ago, David Nahmani said:

It works as expected here too. Can you share your Logic file and give instructions on how to reproduce? 

I neglected to update my new computer and Logic version, which I fixed.

I'm loading an instrument track with Vienna Ensemble Pro AU3 and cabling a Multi-Instrument to it with all the channels enabled. When I assign the first MIDI track to that Multi-Instrument and try to create subsequent MIDI tracks, this is where the problem lies. 

Thanks for the help.

 

 

 

 

Logic Template 3.0.zip

[polanoid]

12 minutes ago, paulcristo said:

I'm loading an instrument track with Vienna Ensemble Pro AU3 and cabling a Multi-Instrument to it with all the channels enabled. When I assign the first MIDI track to that Multi-Instrument and try to create subsequent MIDI tracks, this is where the problem lies.

OK I can reproduce the issue now (even after flattening the too deeply nested track stacks).

[polanoid]

Seems to happen as soon as the song contains at least two multi instruments  sorry that wasn't it... can't reproduce now

Edited February 28, 2023 by polanoid

[David Nahmani]

I did some testing and apparently this happens (in a new project) when you don't activate (make assignable) the channels in order. 

[paulcristo]

1 minute ago, David Nahmani said:

I did some testing and apparently this happens (in a new project) when you don't activate (make assignable) the channels in order. 

I can confirm this on my end. I'm not sure if I should consider this working as expected or if this is some kind of obscure bug. 

Thank you for figuring that out so quickly.

[David Nahmani]

2 minutes ago, paulcristo said:

Thank you for figuring that out so quickly.

You're welcome. 

Oops: you had a double post, seems like you deleted one while I deleted the other, now they're both gone. 😞

[paulcristo]

29 minutes ago, polanoid said:

OK I can reproduce the issue now (even after flattening the too deeply nested track stacks).

What's wrong with a few stack layers? 😁

[polanoid]

15 minutes ago, paulcristo said:

What's wrong with a few stack layers? 😁

Logic doesn't officially support it so you might run into problems when using that "feature"

[polanoid]

Seems like the naming of the single instruments in the Multi Instrument is important as well (if they were renamed them like you did in your project). In that case Logic seems to use the alphabetical order (which makes no sense and should be reported as a bug). Try in attached project 😉.instrument names test.logicx.zip

[paulcristo]

17 minutes ago, polanoid said:

Seems like the naming of the single instruments in the Multi Instrument is important as well (if they were renamed them like you did in your project). In that case Logic seems to use the alphabetical order (which makes no sense and should be reported as a bug). Try in attached project 😉.instrument names test.logicx.zip

Ah! I see what you mean. It appears Logic is prioritizing the naming of the tracks over the actual mechanics of how the Logic actually works. 

Thanks for looking into this. Now I have to figure how to word a bug report so it makes sense. 

[polanoid]

10 minutes ago, paulcristo said:

It appears Logic is prioritizing the naming of the tracks

In fact you are actually not renaming the track, but the environment object used by the track (in my example project there isn't even a track for the Multi Instrument sub channels, the name is stored in the sub channel itself). If you create more than 16 tracks using the "create with next channel" function, you will see that Logic sometimes creates a track using some other MIDI object from the environment (like e.g. "Input Notes") if it fits into the alphabetical order 😉 

Edited February 28, 2023 by polanoid

[polanoid]

13 minutes ago, paulcristo said:

Now I have to figure how to word a bug report so it makes sense.

How about "New Track with Next Channel" uses alphabetical order of environment object names instead of MIDI channel when creating a new track for a Multi Instrument sub channel?

[David Nahmani]

Ok Apple is now aware of this bug and it should get fixed shortly. 🙂 

[fuzzfilth]

17 hours ago, polanoid said:

"New Track with Next Channel" uses alphabetical order of environment object names instead of MIDI channel when creating a new track for a Multi Instrument sub channel

Let's hope Apple actually go ahead an fix it, rather than tacking a checkbox to its left and call it a feature:

[David Nahmani]

They could call it "New Track with Next Channel only when channels were created in ascending order and their alphabetical name order matches the channel ascending order (as in the original Notator/Creator beta)."

[paulcristo]

On 2/28/2023 at 8:34 AM, polanoid said:

Logic doesn't officially support it so you might run into problems when using that "feature"

I don't understand how a feature can be deliberately implemented but not supported.

[polanoid]

23 minutes ago, paulcristo said:

deliberately implemented

It isn't

[paulcristo]

12 minutes ago, polanoid said:

It isn't

But it can't be a programmatic anomaly that nested track stacks just happen to work because you couldn't always do that. They wrote the program to do that, so how can it not be supported?