A small problem I encountered with the latest beta (2.17.9):
Recent versions issue a warning when you use a 6 channel audio setup - I therefore changed my default to 8 channels (even if I usually use only 6 channel sound).
When I create a VF to this kind of OV and use the automatic naming, "HI-VI" is added to the name - even if channels 7 and 8 are empty.
This does not happen for the OV, so I suppose it's a glitch and should not happen?!
Naming problem when using 8 audio channels
-
- Posts: 3
- Joined: Fri Jul 21, 2023 12:06 pm
-
- Site Admin
- Posts: 2548
- Joined: Thu Nov 14, 2013 2:53 pm
Re: Naming problem when using 8 audio channels
Sounds like a bug indeed. I added a note in the tracker.
-
- Posts: 9
- Joined: Wed Jan 10, 2024 9:54 am
Re: Naming problem when using 8 audio channels
Yeah it's great carl because I'm facing same issue.
Thanks.
Thanks.
-
- Posts: 2804
- Joined: Tue Apr 15, 2014 9:11 pm
- Location: Germany
Re: Naming problem when using 8 audio channels
I guess HI/VI-N should only turn up in the Auto-ISDCF name and metadata fields when these channels are assigned in the audio matrix.
Aside from that - the warning is no reason to not use a 6ch configuration. This warning is only targeted towards potential workflow issues with external service companies when your DCP is being worked on there for added value. 6ch DCPs play on all servers and in all TMS environments. E.g. 'Oppenheimer' was all 6ch, trailers as well as main feature.
Aside from that - the warning is no reason to not use a 6ch configuration. This warning is only targeted towards potential workflow issues with external service companies when your DCP is being worked on there for added value. 6ch DCPs play on all servers and in all TMS environments. E.g. 'Oppenheimer' was all 6ch, trailers as well as main feature.
-
- Posts: 9
- Joined: Wed Jan 10, 2024 9:54 am
Re: Naming problem when using 8 audio channels
It's good to know that you've added a note in the tracker. Looking forward to a fix for this glitch.