ffmpeg 7.0.1 and Windows 7

[oniiz86]

I haven't changed ffmpeg defaults but if that is a desired change and simple to implement I would consider it.

@autodidact Thanks for the consideration, it would be greatly appreciated if you could implement this easily in the Windows 7 builds, the original eac3to developer madshi had disabled DRC in his custom FFmpeg build, the concern is about preserving the original dynamic range there is some old discussion about it here https://ffmpeg.org/pipermail/ffmpeg-devel/2015-March/170771.html

[geextah_2]

Does someone know how to use the apple aac_at in high efficiency 2 (aac_he_v2)

here it sais https://trac.ffmpeg.org/wiki/Encode/AAC#aac_at
Note: -profile option only accepts numeric values for aac_at encoder, e.g. 4 works as aac_he and 28 as aac_he_v2. (​https://trac.ffmpeg.org/ticket/9574).

so "-profile:a 4" (aac_he) is working but "-profile:a 28" (aac_he_v2) just crashes

[cholla]

I just tested with the version of ffmpeg I have
The -profile:a 28 fails with a bunch of errors.
I'm using the last 32-bit versions autodidact posted.

It is possible that a later version of audiotoolbox Encoder might be able to do this.
It probably would tale a later version of Windows than my Windows 7 32-bit.
Probably a 64-bit version of ffmpeg,audiotoolbox Encoder,& Windows could .

[geextah_2]

This is crashing on latest ffmpeg 8.1.1 from this post https://forum.videohelp.com/threads/414767-ffmpeg-7-0-1-and-Windows-7/page3#post2781425
Im on Win 10 64bit, and also the latest audiotoolbox files from https://github.com/AnimMouse/QTFiles

[autodidact]

I think with aac_at the aac_he_v2 profile may only work directly on MacOS. On Windows we use the
audiotoolboxwrapper which is based on qaac and that only supports aac_he.

QAAC only does LC and HEv1. It can use some of the audiotoolkit filters while it works.

Source:https://wiki.hydrogenaudio.org/index.php?title=Apple_AAC

[geextah_2]

Oh okay, thats a bit weird but thanks for the information

[manolito]

I have no idea if this ETA information is directly taken from the console or if it is recalculated by the GUI. Whatever, it works fine under FFmpeg 7.x, and it fails under FFmpeg 8.x.

Hi autodidact,

after some research I do know that the ETA calculation in the dmMediaConverter output screen does not get its ETA information directly from the FFmpeg console output. Instead it calculates the ETA data itself from the console output. And since the console output is different between FFmpeg 7 and 8, the ETA display will also be different.

Which means that I need to approach Marius Dalacu and ask him if and how dmMediaEncoder could be updated to spit out correct ETA values both for FFmpeg 7.x and FFmpeg 8.x ...


Cheers
manolito