Agreed. The best way to visualize this is to open the Environment and you will see what Logic is actually doing (CMD+0). There you will see all of your Instrument track laid out in the order they were created. That's the important part Logic assigns instrument tracks based on when they were created, not track order because track order is not tied to the instrument itself. So when you move a track you are moving something that points to Instrument 2 for example not Instrument 2 itself. This is done that way because you can have multiple tracks point to the same instrument, or you can even change the instrument the track is pointing to. So the track you see in the arranger and mixer is just a reference to Instrument 2. The Environment does give you direct access to the instrument tracks though, but moving them around still won't re-assign instrument numbers because like I said its based on the order the instrument was created not position in the mixer.beely wrote: Mon Nov 07, 2022 10:50 pmIt's a reference to the audio object used, not the track number. Those are very different concepts in Logic. If you want to understand why, in Logic you can have eg fifteen different tracks, all with the same audio object assigned to them. Every track has an environment object assigned to it which tells Logic what type of track it is (MIDI or audio) and where to route the track contents.AsgardBS wrote: Mon Nov 07, 2022 5:33 pm I know that "inst 2" equal to the underhood reference to when it was created, but its really anoying they made it that way. They should allow reorganizing it to keep it clean, and not be stuck with old reference number... Should be able to have that number in sync with the actual track #... my OCD kick in hard.
So no, Logic shouldn't change the name or reference of the environment object that's been assigned to a given track when you change the order of tracks in the arrange page.
How to survive Logic Mixer
-
- KVRian
- 1404 posts since 17 Oct, 2018
Studio One // Bitwig // Logic Pro // Ableton // Reason // FLStudio // MPC // Force // Maschine
-
- KVRist
- 44 posts since 20 Oct, 2020
I agree with your two issues. Same for me, and I haven’t found a “simple solution”. All published solutions don’t 100% work for me. You’d think it would be easier. Maybe in the next update…