# Can no longer Copy Transitions To Track \> PQ

**URL:** <https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509>\
**Category:** Flame Questions\
**Tags:** timeline, hdr\
**Created:** [April 23, 2024, 4:48pm UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509 "2024-04-23T16:48:23Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![cicero](https://avatars.discourse-cdn.com/v4/letter/c/ecae2f/32.png) [@cicero](https://forum.logik.tv/u/cicero)\
**Post date:** [April 23, 2024, 4:48pm UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/1 "2024-04-23T16:48:23Z")

</div>

Flame timeline has HDR graded media on V1.1. Then an SDR trim xml has been imported from Baselight onto timeline, with auto-generated PQ track immediately under the so-called “HDR” (xml) track.

In 2023 we were able to Copy Transitions To Track (from V1.1) \> PQ track, to blade up that PQ track before rendering. This was very useful for various reasons…

Now in Flame 2024.2.1 the option is no longer there, in the exposed list of tracks to copy to. All the others are there as options. Is this by design? Can’t think why it would have been disabled.  
Thanks!  
@fredwarren @Slabrie

---

<div class="post-metadata">

**Author:** ![tylerf](https://avatars.discourse-cdn.com/v4/letter/t/8491ac/32.png) [@tylerf](https://forum.logik.tv/u/tylerf)\
**Post date:** [April 23, 2024, 5:10pm UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/2 "2024-04-23T17:10:33Z")

</div>

I belive they (Autodesk) removed the ability to add transitions to HDR and PQ tracks. This was in one of their release notes somewhere.

Not sure if that answers your question?

---

<div class="post-metadata">

**Author:** ![Slabrie](https://avatars.discourse-cdn.com/v4/letter/s/7cd45c/32.png) [@Slabrie](https://forum.logik.tv/u/Slabrie)\
**Post date:** [April 23, 2024, 5:48pm UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/3 "2024-04-23T17:48:34Z")

</div>

Tylerf is right: we have removed the ability to add FX and transitions to these tracks since we got many users confused by that. Cicero, could you explain the use case to add dissolve on the HDR and the PQ track?

---

<div class="post-metadata">

**Author:** ![cicero](https://avatars.discourse-cdn.com/v4/letter/c/ecae2f/32.png) [@cicero](https://forum.logik.tv/u/cicero)\
**Post date:** [April 23, 2024, 5:59pm UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/4 "2024-04-23T17:59:44Z")

</div>

Thanks both. Yes I had totally missed that, but just found it in ‘ **2024.1 Additional enhancements** ’:  
**HDR Workflow** : You’re no longer allowed to add a Transition or Timeline FX to the HDR or PQ tracks of a sequence.

We don’t want to copy transitions (dissolves etc) to PQ track - that would be mad! Just the cuts. Our work is longform and we want to render that PQ track before a client session. If we make changes under the PQ track, often the whole layer will become unrendered, not just the changed frames. If it has already been chopped up, then only the changed shots will need to be re-rendered on the PQ layer.

Looks like you can still manually add cuts to the PQ layer, which is obviously time-consuming but what we’ll have to do I guess. Seems odd still to allow cuts to be added one by one, but not copied wholesale from another track.

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [April 23, 2024, 6:22pm UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/5 "2024-04-23T18:22:12Z")

</div>

There’s still an Old Skool way: Copy the track with the transitions to a new layer and duplicate media. Unlink media for that track. Put a copy of the PQ track in a reel by itself. Conform the track with no media pointing to the PQ track reel as the conform source.

I’ve never done HDR, so I don’t now if this is possible with a PQ track, and I “remembered” the method off the top of my head, but it should work.

The ability to do this with one or two clicks was a great improvement when it came out.

---

<div class="post-metadata">

**Author:** ![cicero](https://avatars.discourse-cdn.com/v4/letter/c/ecae2f/32.png) [@cicero](https://forum.logik.tv/u/cicero)\
**Post date:** [April 23, 2024, 6:26pm UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/6 "2024-04-23T18:26:34Z")

</div>

Thanks Tim but I don’t think that’ll work. The PQ track contains no media, it’s effectively a Colour Management TLFX on gap/filler, so can’t be linked to like media can.

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [April 23, 2024, 6:53pm UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/7 "2024-04-23T18:53:18Z")

</div>

Ah. Sorry. Interesting how the PQ becomes completely unrendered when with normal gap effect tracks only the portion over the changes become unrendered. For what it’s worth, I don’t experience that with a CM gap fx.

---

<div class="post-metadata">

**Author:** ![Robg](https://avatars.discourse-cdn.com/v4/letter/r/a698b9/32.png) [@Robg](https://forum.logik.tv/u/Robg)\
**Post date:** [April 23, 2024, 8:21pm UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/8 "2024-04-23T20:21:04Z")

</div>

> [@cicero](#):
>
> …he whole layer will become unrendered, not just the changed frames. If it has already been chopped up, then only the changed shots will need to be re-rendered on the PQ layer.Looks like you can still manually add cuts to the PQ layer, which is obviously time-consuming but what we’ll have to do I guess. Seems odd still to allow cuts to be added one by one, but not copied wholesale from another track.

Just wondering what your purpose of rendering the PQ layer is? Would caching your grade and then blowing after the client session still give you the same confidence? Alternately adding a CC layer above the PQ and do a Copy Transitions to Track on that and rendering?

---

<div class="post-metadata">

**Author:** ![Slabrie](https://avatars.discourse-cdn.com/v4/letter/s/7cd45c/32.png) [@Slabrie](https://forum.logik.tv/u/Slabrie)\
**Post date:** [April 24, 2024, 9:36am UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/9 "2024-04-24T09:36:56Z")

</div>

> [@cicero](#):
>
> …he whole layer will become unrendered, not just the changed frames. If it has already been chopped up, then only the changed shots will need to be re-rendered on the PQ layer.Looks like you can still manually add cuts to the PQ layer, which is obviously time-consuming but what we’ll have to do I guess. Seems odd still to allow cuts to be added one by one, but not copied wholesale from another track.

Hello Cicero!  
Ok now I better understand the use case. You should not have to render the PQ track. Have you seen playback issue when the PQ track was not rendered?

---

<div class="post-metadata">

**Author:** ![cicero](https://avatars.discourse-cdn.com/v4/letter/c/ecae2f/32.png) [@cicero](https://forum.logik.tv/u/cicero)\
**Post date:** [April 24, 2024, 10:50am UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/10 "2024-04-24T10:50:18Z")

</div>

@ytf I’ve just done a test and the behaviour was the same as yours, it only needed to re-render the frames changed below. But we have seen this in the past and in any case, if you have a 60min timeline with a single slug of CM across the PQ track, it takes maybe a couple of minutes to realise that it only needs to re-render a few seconds of changes. If the layer already had edits, it knows instantly what needs re-rendering. It does this for any FX which span a long timeline, not just PQ CM.

---

<div class="post-metadata">

**Author:** ![cicero](https://avatars.discourse-cdn.com/v4/letter/c/ecae2f/32.png) [@cicero](https://forum.logik.tv/u/cicero)\
**Post date:** [April 24, 2024, 10:50am UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/11 "2024-04-24T10:50:52Z")

</div>

@Robg @Slabrie I never start a client session without all TLFX being rendered. All our work is longform in UHD using EXRs off central storage. Even if media is cached I won’t trust it to play back an hour of timeline with any unrendered FX, without dropping frames.

---

<div class="post-metadata">

**Author:** ![Robg](https://avatars.discourse-cdn.com/v4/letter/r/a698b9/32.png) [@Robg](https://forum.logik.tv/u/Robg)\
**Post date:** [April 24, 2024, 11:16am UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/12 "2024-04-24T11:16:44Z")

</div>

That’s fair enough, I don’t render a cm or hdr layer as I just don’t have the time to let the machine do that. I’ve very rarely had an issue with that especially if what’s beneath is cached as well.

---

<div class="post-metadata">

**Author:** ![Slabrie](https://avatars.discourse-cdn.com/v4/letter/s/7cd45c/32.png) [@Slabrie](https://forum.logik.tv/u/Slabrie)\
**Post date:** [April 24, 2024, 12:50pm UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/13 "2024-04-24T12:50:30Z")

</div>

@cicero we will see what could be done to solve your issue and we will keep you updated.

---

<div class="post-metadata">

**Author:** ![cicero](https://avatars.discourse-cdn.com/v4/letter/c/ecae2f/32.png) [@cicero](https://forum.logik.tv/u/cicero)\
**Post date:** [April 25, 2024, 10:39am UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/14 "2024-04-25T10:39:27Z")

</div>

Thanks Stéphane! Have submitted an improvement request and linked to this thread:  
[FI-03245](https://feedback.autodesk.com/project/feedback/view.html?cap=5afe6c84-5cb3-447a-b36c-cbd7f0688f84&uf=b6158f64-c34c-4397-98ee-39f30d6db983&nextsteps=1&nextstepsf=8fbadb72-c1b4-44ad-b55e-888e3fdc17e4&nextstepsuf=b6158f64-c34c-4397-98ee-39f30d6db983)

---

<div class="post-metadata">

**Author:** ![Slabrie](https://avatars.discourse-cdn.com/v4/letter/s/7cd45c/32.png) [@Slabrie](https://forum.logik.tv/u/Slabrie)\
**Post date:** [April 25, 2024, 12:12pm UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/15 "2024-04-25T12:12:18Z")

</div>

Thanks a lot!

---

<div class="post-metadata">

**Author:** ![Slabrie](https://avatars.discourse-cdn.com/v4/letter/s/7cd45c/32.png) [@Slabrie](https://forum.logik.tv/u/Slabrie)\
**Post date:** [April 29, 2024, 10:32am UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/16 "2024-04-29T10:32:11Z")

</div>

The ability to copy cut transitions to track will come back in an upcoming service pack. Thanks for reporting the issue and sorry for any inconvenience.

---

<div class="post-metadata">

**Author:** ![cicero](https://avatars.discourse-cdn.com/v4/letter/c/ecae2f/32.png) [@cicero](https://forum.logik.tv/u/cicero)\
**Post date:** [April 29, 2024, 1:16pm UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/17 "2024-04-29T13:16:07Z")

</div>

Amazing, thanks Stéphane!

---

<div class="post-metadata">

**Author:** ![fredwarren](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/fredwarren/32/158_2.png) [@fredwarren](https://forum.logik.tv/u/fredwarren)\
**Post date:** [May 23, 2024, 3:04pm UTC](https://forum.logik.tv/t/can-no-longer-copy-transitions-to-track-pq/10509/18 "2024-05-23T15:04:24Z")

</div>

The functionality has been brought back in the 2025.0.1 version.
