Vertical dotted line showing up on my clip

[Digitalsound84]

I see a vertical dotted line on one of my clips.  I don't know why it's there.  I have a photo of it.  The cursor is near this dotted line in the photo.  You can see it on Track 3.

[SteveG_AudioMasters_]

I've had a very close look, on a 20" monitor and I can't see a vertical dotted line anywhere on track 3 - or anywhere else, come to that. No, I am not blind. Can anybody else see it?

[emmrecs]

Actually, yes I can see it!  (On a 23" monitor).

I've seen something similar before, but can't remember when and why!  I think you can safely ignore it??

[SteveG_AudioMasters_]

I used the screen magifier to enlarge it 300% and I still can't see any vertical dotted line. This may well be something to do with the way the image is displayed on different monitors, for all I know. But whatever it may or may not be, it can certainly be ignored!

[emmrecs]

I think this is what the OP is referring to:

[SteveG_AudioMasters_]

Ah, I can see it now - doesn't quite qualify for my definition of  'near', but never mind. If it shows in Waveform view as well, then it's possibly an unwanted artifact in the .pkf file. You can test this hypothesis by deleting the track's .pkf file and letting Audition re-create it. If it's still there - well, I'll be a little surprised...

[Spamhunter]

Isn't this a marker in the audio file? Open the audio file & check.

[SteveG_AudioMasters_]

No, markers don't show like that. There's nothing on the timeline to indicate a timeline marker, and a marker transfered from Waveform view would have an identifier with it - and no dotted line:

[Spamhunter]

I just created one on an audio file within a multitrack session. The one difference is that it has a marker tag on it. (Audition 23.5, build 23.5.0.48)

[SteveG_AudioMasters_]

After a bit of investigating, it would appear that not all systems display dotted lines - which is a bit weird. I think that this is probably down to individual video driver differences.

[Spamhunter]

Ah, I was thinking that must be the case but thought it might be between different versions/builds.