Track numbers not updating in MPC (FIXED)

[Tod]

This has been happening for quite a while now and it's rather random.

How exactly it's happening I'm not sure, as I'm working along and adding tracks in the TCP which are above the tracks in the MPC, the MPC track numbers do not always update.

It happened to me today and I was going to take a screenshot of it, but before I took the shot, I changed themes and it fixed itself.

Sometimes all I have to do is edit a track name and it will fix itself. Sometimes not.

The main thing that bugs me is when I'm routing something, especially in the routing or group matrix, it gets a little confusing.

Something else that came up today in the routing matrix. A track ended up being routed to itself. Checking the routing on the track itself shows that it is not routed to itself. I tried various things, even closing Reaper and rebooting but it still shows that it's routed to itself in the Routing Matrix.

Look at track 23 "Sub Strings".



I know the routing thing with the MTC track number not updating is going to happen again fairly soon, and next time I'll try get a picture right away.

[Tod]

I knew it wouldn't take long. As you can see, Track manager shows them correctly, tracks 6, 7, & 8. However, they are 4, 5, & 6 in the MPC.

[EpicSounds]

Master track options - Auto Arrange Tracks in Mixer [checked]

[Tod]

Originally Posted by EpicSounds

Master track options - Auto Arrange Tracks in Mixer [checked]

Heh heh, so there's an option for this? I should-a figured!

Thanks EpicSounds, but indeed mine is checked, so that's not it.

[4x4uk]

Hi Tod

I think epicsounds is actually saying you should uncheck that if its checked.

[EpicSounds]

Originally Posted by 4x4uk

Hi Tod

I think epicsounds is actually saying you should uncheck that if its checked.

no indeed it should be checked. No other ideas for this 'bug'

[Tod]

Okay, I think I may have narrowed it down, it could be happening when I duplicate tracks.

I'm going to test this a little more today.

[Tod]

Yep, I can get it to happen every time by duplicating tracks in the TCP.

I had 7 tracks in the TCP and 3 in the MPC. Then I duplicated Track-7 and Track-5. You can see the outcome.

[Dstruct]

Confirmed (5.201 x64).

FIXED (5.21pre7)

[EpicSounds]

can't reproduce here on 5.20 osx

[ivansc]

At the risk of sounding flippant, exactly what did you expect to happen when you actually \**duplicate**/ a track?

I see what is happening as logical behaviour. Sorry.
You told reaper to duplicate something, so it did.
A case of do what I want not what I say.

[EpicSounds]

Originally Posted by ivansc

At the risk of sounding flippant, exactly what did you expect to happen when you actually \**duplicate**/ a track?

I see what is happening as logical behaviour. Sorry.
You told reaper to duplicate something, so it did.
A case of do what I want not what I say.

The track numbers are wrong. compare track names with numbers in that image

[Tod]

Okay, I checked it on 4 versions.

v5.15/x64
v5.18/x64
v5.20/x64
v5.11pre3/x64

It's the same with all of them.

I loaded 5 tracks into the TCP and 2 tracks into the MCP.

I duplicated Track 5 first, then track 3, and the MCP tracks did not update.

[EpicSounds]

Originally Posted by Tod

Okay, I checked it on 4 versions.

v5.15/x64
v5.18/x64
v5.20/x64
v5.11pre3/x64

It's the same with all of them.

any of them clean portable installs?

[Tod]

Originally Posted by EpicSounds

any of them clean portable installs?

Hi Jon, they are all portable installs, however they weren't clean.

However I do have one that is totally clean, v5.20rc6, and the only thing I did is put my license in it, otherwise it's completely fresh. Same thing happens there too.

So you can't reproduce this? Following the directions I showed above, this is what I did.

I loaded 5 tracks into the TCP and 2 tracks into the MCP.

I duplicated Track 5 first, then track 3, and the MCP tracks did not update.

Now the exact order probably doesn't have to be that way, I've just been trying to follow the same procedure.

[Justin]

Duplicated the issue with track numbers not updating in the mixer when duplicating an earlier track, thanks! Fixing.

Any idea how to reproduce that routing matrix drawing bug?

[Justin]

Originally Posted by Tod

Something else that came up today in the routing matrix. A track ended up being routed to itself. Checking the routing on the track itself shows that it is not routed to itself. I tried various things, even closing Reaper and rebooting but it still shows that it's routed to itself in the Routing Matrix.

Ooh send me the .RPP please!

[Tod]

Okay, here you go Justin, thanks.

http://stash-new.reaper.fm/27722/04%...er%20crash.zip

[ivansc]

Originally Posted by EpicSounds

The track numbers are wrong. compare track names with numbers in that image

Suppose it comes down to your interpretation of "wrong".

Sorry - I just felt argumentative last night I guess...

But it will be interesting to see what Justin makes of this.
I can of course understand the desired behaviour, but it sorta comes down to the difference semantically between "copy" and "duplicate" I suppose.
Glad I dont have to code this stuff.

[Dstruct]

Originally Posted by Tod

Okay, here you go Justin, thanks.

http://stash-new.reaper.fm/27722/04%...er%20crash.zip

Confirmed (5.201).


FIXED (5.21pre7)

[Tod]

Originally Posted by Dstruct

Confirmed (5.201).

Thanks Dstruct.

Originally Posted by ivansc

Suppose it comes down to your interpretation of "wrong".

Sorry - I just felt argumentative last night I guess...

But it will be interesting to see what Justin makes of this.
I can of course understand the desired behaviour, but it sorta comes down to the difference semantically between "copy" and "duplicate" I suppose.
Glad I dont have to code this stuff.

Yeah, it's really not a big deal until you open one of the matrixes looking for a track number, because the they all have the correct numbering. When you have a large project, it can get a little confusing.

[Justin]

Originally Posted by Tod

Okay, here you go Justin, thanks.

http://stash-new.reaper.fm/27722/04%...er%20crash.zip

Heh what is the "after crash" you mention?

This project has an invalid send (sending from the track to itself), which we can easily filter on read, just curious how it got there...

[Tod]

Originally Posted by Justin

Heh what is the "after crash" you mention?

This project has an invalid send (sending from the track to itself), which we can easily filter on read, just curious how it got there...

Yeah, heh heh, I do get the occasional crash, mostly when I've got Kontakt open.

I don't have a clue how the invalid send got there, or how long it was like that before I noticed it. It just suddenly showed up, or I should say, I noticed it while I was assigning tracks. It caught my attention because I didn't think that was possible.

Thanks Justin.

[Tod]

Well It looks like it's not just using "Duplicate", I just used "SWS: Insert Track above selected tracks", and the tracks in the MCP did not update.

I thought I should mention it.

[Justin]

Originally Posted by Tod

Yeah, heh heh, I do get the occasional crash, mostly when I've got Kontakt open.

Right, but how do you have an "after-crash" rpp?

[Tod]

Originally Posted by Justin

Right, but how do you have an "after-crash" rpp?

That's just a little note to myself that the project crashed on me and I reopened it with an autosave backup.

My next save wont have that.