Page 1 of 1
Problem with 5.1 sound when copying a timeline

Posted:
Wed Jun 23, 2021 2:39 pm
by Alexander Gietz
Hi,
I am having a 50fps timeline with 5.1 sound ... everything running smoothly.
Now I need a 25fps delivery of the same video. So I make a new timeline with 25fps and just drag the complete 50fps timeline into the new one. Works perfect when the original is a stereo timeline, but with 5.1 sound I just get an empty 5.1 track on the 25fps timeline. Inspector file format says it's: Adaptive 6
Any suggestions?
Best
Alex
Re: Problem with 5.1 sound when copying a timeline

Posted:
Wed Jun 23, 2021 3:42 pm
by Reynaud Venter
Is this behaviour only with a nested Timeline rather than placing the source media within a new Timeline?
Re: Problem with 5.1 sound when copying a timeline

Posted:
Wed Jun 23, 2021 6:06 pm
by Alexander Gietz
Yes, it's only when it's nested. I think its unnecessary to copy all timeline items, when you can get the same effect with a nested timeline. And ... it works wonderfully in Stereo, but won't with 5.1 ?¿?
Re: Problem with 5.1 sound when copying a timeline

Posted:
Thu Jun 24, 2021 8:12 am
by Reynaud Venter
Any improvement manually changing the Embedded Timeline's Audio Channel Configuration via Clip Attributes from Adaptive 6 to SMPTE 5.1?
Alternatively:
Edit menu > Decompose Compound Clips On Edit
Clip contextual menu > Decompose in Place
Re: Problem with 5.1 sound when copying a timeline

Posted:
Thu Jun 24, 2021 10:12 am
by Alexander Gietz
Reynaud Venter wrote:Any improvement manually changing the Embedded Timeline's Audio Channel Configuration via Clip Attributes from Adaptive 6 to SMPTE 5.1?
Alternatively:
Edit menu > Decompose Compound Clips On Edit
Clip contextual menu > Decompose in Place
Both give unfortunately no result. There is also no waveform to see in the audio-clip. I only see 6 empty channels. When I'm doing it in Stereo, I see the waveforms from both channels.
Re: Problem with 5.1 sound when copying a timeline

Posted:
Thu Jul 01, 2021 8:26 am
by Alexander Gietz
Unfortunately 17.2.2 did not fix this issue
