Replies: 4 comments 1 reply
-
|
DME uses broken up executables on newer versions instead of DEE. However DEE is still being developed (https://professionalsupport.dolby.com/s/article/Dolby-Encoding-Engine-v6-0-is-out?language=en_US). DeeZy utilizes the JSON interface so it should be in good shape for future releases. Untested but DeeZy should work with DEE v6.0 and beyond. From my understanding there is no benefit in upgrading at the moment either. |
Beta Was this translation helpful? Give feedback.
-
|
Have a look here. ;) Perhaps you can start playing new version of DEE inside DME too. |
Beta Was this translation helpful? Give feedback.
-
|
I think DME encoder support for all the split up binaries really isn't in the scope and provides little benefit over DEE. This would require split logic to execute tasks different ways based on what executable is available and it's not trivial ATM. DeeZy should support DEE v6+ with no problem thanks to me building it out to utilize the JSON interface, but I would need to test that and ATM I don't have access to the DEE v6. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for my bad english. What I meant is to start adding support to the new DEE executables, that are separated and not a single one anymore: You can find them in the repo I linked in my previous post. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Do you plan to add Dolby Media Encoder 3.7.0 support?
DEE.EXEisn't present anymore, inside the.\resources\deeyou can findand as far as I know, the DME doesn't even have the usual xml interface that DEE is based on.
Beta Was this translation helpful? Give feedback.
All reactions