Pro Tools bugs

Selection Memory Locations with Absolute Reference Remain Relative When Session Start Timecode Changes

When changing the session start time in the Session Setup window, Pro Tools seems to erringly override Selection memory locations that have Absolute time references and treats them as relative instead (a bug).

 

To reproduce:

 

1) Make a PT session with at least one track and one region

2) Create a Selection memory location with an Absolute time reference (not Bar | Beat). Note the timecode.

3) Open Session Setup window, and change the session start time to a time that is earlier than it currently is.

4) A dialog will appear asking if you want to "Maintain Relative Position" or "Maintain Timecode."

 

- "Maintain Relative Position" WILL work as expected.

- "Maintain Timecode" will NOT work as expected. It won't retain the timecode of the Absolute Selection, but cause it to be offset relatively (the same effect as if you had chosen "Maintain Relative Position."

 

Here are my observations:

 

SCENARIO 1

---> Session with no contents (no regions)

---> One marker, absolute reference

---> One marker, bar | beat reference

---> One selection, absolute reference

---> One selection, bar | beat reference

- Change session start time. Dialog will NOT appear asking to maintain relative position or maintain timecode.

- RESULT:

---> All four markers/selections remain at their timecode locations as expected.

 

SCENARIO 2: (see attached screenshot)

---> Session with contents (at least one region on a track)

---> One marker, bar | beat reference

---> One marker, absolute reference

---> One selection, bar | beat reference

---> One selection, absolute reference

- Change session start time. Dialog WILL appear asking to maintain relative position or maintain timecode.

- Select "Maintain Timecode"

- RESULT:

---> Marker, bar | beat reference - stays at timecode as expected

---> Marker, absolute reference - stays at timecode as expected

---> Selection, bar | beat reference - stays at timecode as expected

---> Selection, absolute reference - remains relative, NOT as expected

 

 

I included Scenario 1 to demonstrate why Scenario 2 is in fact a bug.

Tags

Idea No. 215

Attachments

- [ Show all ]