News for hackers. Stuff that matters.
Re:Google wants to take on Dolby with new open media formats by monocasa on Thursday September 22, 2022 @02:26PM (#32942747)
If the open solution doesn't take off in favor of the proprietary solution, then you're in essentially the same end state as if there was no open solution in the first place.
Re:Google wants to take on Dolby with new open media formats by scarface74 on Thursday September 22, 2022 @02:32PM (#32942813)
Not after you’ve already encoded your audio to support it. From history we know that Google isn’t going to do the leg work it takes to make the standard ubiquitous.
Re:Google wants to take on Dolby with new open media formats by monocasa on Thursday September 22, 2022 @02:42PM (#32942938)
Why would you only encode your media in a format that none of your customers have support for in the first place?

Additionally, being an open standard, you can probably rely on ffmpeg supporting it. This allows you to transcode into something that your proprietary encoder will support for ingest if it comes to that.

Re:Google wants to take on Dolby with new open media formats by scarface74 on Thursday September 22, 2022 @02:45PM (#32942995)
Yes because transcoding audio couldn’t possibly lead to lesser quality.
Re:Google wants to take on Dolby with new open media formats by monocasa on Thursday September 22, 2022 @03:05PM (#32943262)
Neither of these (HDR10+/DV, open spatial audio/Atmos) are due to compression, so yeah, kind of. They're both metadata schemes on top of other, pluggable compression schemes. So yeah, I wouldn't expect a conversion to necessarily end up with a loss of quality.

This is also ignoring the first sentence: your whole supposition is based on a scenario where you as the content producer for some reason encoded in a format that your customers don't have, and don't have the masters for some reason. Which is basically absurd for anything that would need dynamic HDR or spatial audio.