PS: Did I read something about Dolby Encoding Engine being used via CLI? I think that would speed things up when automating via scripting even if you need to split 5.1 tracks to 6 wav files. I'll try 5.1 when I have time (If I have time) I think I still hear something different somewhere but couldn't pinpoint it well enough so I might be simply wrong.įfmpg's Ac3 is apparently transparent but I think I could find something to focus on if I took more time to test. Pro-Ec3 is basically transparent to me here. Pro-Ac3 is almost transparent to me but I still can tell it apart if I focus on very specific sounds. Pro-Ec3 still have a slight edge over pro-Ac3 Pro-Ec3 has a slight edge over pro-Ac3, though. I just did a quick test using your samples and encoding your wav to Ac3 so I can compare with current ffmpeg version, the one I used for my own tests. There is a plugin for Sound Forge, it can take floating point input, but seems to work only with stereo. They either require split channels, encode only one file at a time, or read from directshow with random delay and limited maximum file size, or the GUI is bloated and awkward, may require mapping of input channels. Tools with the Dolby encoder are frustrating to use. But the reason for that is mainly my worn ears. I struggle to hear a significant difference with normal music, apart from artificial killer samples with sharp impulses such as "Everything Is Green" where ffmpeg is more smeared. Audio size is easy to handle relative to video, with modern internet connections or storage.ĮC3 has slightly more bandwidth than AC3 at the same bitrate. I would prefer AC-3 for maximum compatibility with 2 or 6 channels. 5.1 music at 256 kbit/s is unlistenable with ffmpeg. The Dolby encoder degrades more gracefully at extremely low bitrates than ffmpeg. I would like to have a Dolby Encoder to test.
0 Comments
Leave a Reply. |