2020-02-28, 04:03 PM
AP can't handle AC3 properly anymore.
About 3 or 4 major revisions ago it had an internal encoder and decoder for AC3 built in. They worked out a license with Dolby that for every copy sold. Dolby would be paid a certain amount in royalties. When they switched to the 99% cloud, their accounting of what qualified as a copy sold got "creative". Dolby realized they were being cheated and came calling. Rather than pay any further future amounts they remove the encoder/decoder all together.
The reasoning was that Windows has an internal AC-3 encoder/decoder. So Adobe would just use that. Problem with that is that was only Windows 10. If you were on 7 at the time (like me) you were out of luck. Well turns out that the W10 AC-3 doesn't work well at all with AP. It can read AC-3 fine in AP and Audition but has a real problem generating accurate info for AC-3 files in export. Basically, the problems you described Croweyes. So if you are doing any audio work in AP you almost always have to use LPCM. I decode the 5.1 into 6 wavs, import that into AP, edit it and literally export each wav separately/individually and combine them back in another program.
A simpler way is not to use AP at all for editing. Take the AC-3 convert it into PCM 2.0 to act as a sync track, make your edits, export that and then do the real 5.1 changes in something like Audition, using that 2.0 as a guide.
(And as for Adobe, don't get me started on them removing MKV support)
About 3 or 4 major revisions ago it had an internal encoder and decoder for AC3 built in. They worked out a license with Dolby that for every copy sold. Dolby would be paid a certain amount in royalties. When they switched to the 99% cloud, their accounting of what qualified as a copy sold got "creative". Dolby realized they were being cheated and came calling. Rather than pay any further future amounts they remove the encoder/decoder all together.
The reasoning was that Windows has an internal AC-3 encoder/decoder. So Adobe would just use that. Problem with that is that was only Windows 10. If you were on 7 at the time (like me) you were out of luck. Well turns out that the W10 AC-3 doesn't work well at all with AP. It can read AC-3 fine in AP and Audition but has a real problem generating accurate info for AC-3 files in export. Basically, the problems you described Croweyes. So if you are doing any audio work in AP you almost always have to use LPCM. I decode the 5.1 into 6 wavs, import that into AP, edit it and literally export each wav separately/individually and combine them back in another program.
A simpler way is not to use AP at all for editing. Take the AC-3 convert it into PCM 2.0 to act as a sync track, make your edits, export that and then do the real 5.1 changes in something like Audition, using that 2.0 as a guide.
(And as for Adobe, don't get me started on them removing MKV support)
