Markers Pointing To Previous Marker In DP 11.2? RESOLVED

[primeevolutionary]

This may have been going on for a while, but, in DP 11.2, when I'm following along in a sequence, the Markers window's pointer is always pointing to one marker behind where the counter is set.

If I have markers at measure 1, 5 and 9, the pointer is not appearing anywhere if the counter is on measure 1, pointing to measure 1 when the counter is on measure 5 and pointing to measure 5 when the counter is on measure 9.

Is anyone else experiencing this issue, or, do I have something set wrong? I can't imagine there's setting to always point one marker back.

[James Steele]

I just checked and not happening here. Although, I do notice that the pointer will not advance until you actually reach the next measure where there is a marker.

For example I was playing back and had a marker on mm 13 and mm 21. When playback reaches mm 13 marker pointer jumps to the associated marker... then stays there until playback reaches mm 21, then jumps there. If I hit stop and then location to mm 20 (using "." 20 "enter" on numeric keypad, the pointer in the marker window will jump back to the marker for mm 13, even though playback wiper is at mm 20. So pointer is always on the most recent marker.

Again... sorry to be redundant. May not have anything to do with that. Did you also check you chunk start time? Maybe there's an offset affecting it?

[primeevolutionary]

Thanks, James!

Chunk start looks normal.

The marker will switch to the new marker once the counter is passed the new marker, but, not at the marker. That's not how it always worked though. Also, this seems to be happening on all projects, even new ones.

My measure 5 marker will change to point to that marker at 005|1|001, but, not 005|1|000. It used to change right on the measure.

[James Steele]

Hmmm... that's strange. I just tested this and located to measure 21, and marker window pointer jumped to the correct marker at 21|1|000 not 21|1|001 so I'm at a loss as to why it's happening for you. See attached QT movie to verify this.

Marker Window.mov

(513.68 KiB) Downloaded 108 times

[primeevolutionary]

Darn for me, but, thank you, James! I hope you're feeling better.

[James Steele]

Darn for me, but, thank you, James! I hope you're feeling better.

A lot... thanks! I wonder if it's project specific? Does it happen with other projects? It's very odd that it would be off by one tick. Definitely a head scratcher.

[primeevolutionary]

I thought it was happening on all projects, but, I just tried it on one that was created in 11.2 and it's not happening on that one.

[James Steele]

I thought it was happening on all projects, but, I just tried it on one that was created in 11.2 and it's not happening on that one.

Ahhh... you know it's funny. I've had situations similar to that where something weird is going on and it turns out to be a particular project file that must have somehow gotten corrupted and a few bytes flipped or something. I wonder if you used "Load..." to load that chunk into a new project created in DP 11.2 if the issue will go away for that particular project (chunk, actually)?

[primeevolutionary]

It's possible. It's a very old project. It's not a big deal as the pointer isn't even something I look at often. I just found it weird.

I appreciate you spending some time on it.

[James Steele]

It's possible. It's a very old project. It's not a big deal as the pointer isn't even something I look at often. I just found it weird.

I appreciate you spending some time on it.

Oh it's no biggie. It's a Saturday and I'm still just kind of taking it easy after my appendectomy. I just happened to be at my DAW computer when I read this so it was easy for me to look into it. I have to say, I'm loving this Mac Studio. It took some doing to get this studio modernization I'm currently in the midst of going. Had to sell one of my higher end guitars to get the Mac Studio, but no regrets. Apple Silicon is a real game changer.

I'll mark this RESOLVED, if that's cool with you.

[primeevolutionary]

I'm glad you're loving it. I'm a little jealous. My previous Mac was starting to do a bunch of weird things and I had to buy my M1 Macmini before the Mac Studio was available, however, I am loving my Macmini. This was the first time I did a clean install and feels nice to be so streamlined.

Anyway, the thread really is resolved and you helped me resolve it.

Your idea to check the Chunk/Sequence Start gave me an idea. I started comparing a bunch of projects. So, it wasn't the Chunk/Sequence Start, but, the Memory Start that was the issue. Why was it happening on some projects and not others? It was happening on any projects where I had a pickup bar into measure 1.

This is my theory/composition background getting in my way. My OCD likes to see measure 1 at 0:00:00.00, but, in engineering terms, 0:00:00.00 would be wherever the start of the recording is. I guess this happens to me all the time, because I'll usually add a tenth of a second to the beginning of all mixes and masters as well.

Thanks for helping me troubleshoot it.

[James Steele]

I'm glad you're loving it. I'm a little jealous. My previous Mac was starting to do a bunch of weird things and I had to buy my M1 Macmini before the Mac Studio was available, however, I am loving my Macmini. This was the first time I did a clean install and feels nice to be so streamlined.

Hey those M1 Mac Minis are great! I probably could have done okay with one of those, but I figured I'd sell some stuff and go for it. Either way, that mini still runs circles around the old Intel cheesegraters!

Thanks for helping me troubleshoot it.

No worries. This DAW systems we all put together have so many interacting parts that all sorts of strangeness can creep in. Glad the mystery seems somewhat solved.