eac3to - audio conversion tool

[hubblec4]

There are more differences. Eac3to will not really work with UHD-BD at the moment.
https://forum.doom9.org/showthread.p...85#post1810285

[colpoz]

Is there any way to extract only the subtitles flagged as forced instead of the entire track??

Example if the English track contains "1000 normal and 50 forced captions" I want to extract only the 50 forced ones.

Is it possible using only eac3to command line?

[LigH]

Probably not (at least I see no option mentioned in its help output). The purpose of eac3to is mainly to handle audio. You may need a tool specialized in handling subtitles instead.

[stax76]

Originally Posted by colpoz

Is there any way to extract only the subtitles flagged as forced instead of the entire track??

Example if the English track contains "1000 normal and 50 forced captions" I want to extract only the 50 forced ones.

Is it possible using only eac3to command line?

As far as I know such disks are extremely rare, what's the name of the title? Tools you can try are BDSup2Sub(++) and Subtitle Edit.

[Q-the-STORM]

Originally Posted by stax76

As far as I know such disks are extremely rare, what's the name of the title? Tools you can try are BDSup2Sub(++) and Subtitle Edit.

I've encountered a lot of those, it's not that rare... you can extract them with BDSub2Sub... just drop the file in there, navigate to "File" -> "Save/Export" -> tick "Export only Forced" -> click on "save"...

If you prefer working in CLI, use --forced-only

[stax76]

Originally Posted by Q-the-STORM

I've encountered a lot of those, it's not that rare... you can extract them with BDSub2Sub... just drop the file in there, navigate to "File" -> "Save/Export" -> tick "Export only Forced" -> click on "save"

Can you name same titles, I'm always looking to improve my sample collection.

[von Suppé]

Take into account that forced subtitles can be flagged as "forced" in a total subtitle stream,
but they can also be muxed / authored as a separate stream.

[stax76]

I'm interested in titles that have it flagged as forced, ideally with spoken dialog and small file size.

[nevcairiel]

Most of the Avatar Blu-ray releases use flagged forced frames for alien dialog, sometimes even with normal frames active at the same time, which is a good test if the separation works properly.

[stax76]

It's a bit long, at least the price is low.

[nevcairiel]

Blu-rays are the only sources of commercial PGS subtitles, what do you expect?

[stax76]

Probably unrealistic to find but something smaller like 100 min, 30 GB and decent movie I've not already seen.

[Q-the-STORM]

I don't remember which ones, it's not like I wrote it down... Definitely a few seasons of True Blood have them (not all, some have separate forced subs), same goes for Game of Thrones...

[thomaz909]

When i use "-normalize" it creates wav files only to get the maxiumum gain value of the source.
Isn't it possible to just read the gain value of the source instead of doing a complete decode to wav (some ac3 640 sources result in very huge 64 bit float wavs)?

[LigH]

Gain values in headers are no guarantee to avoid an integer overflow or a suboptimal volume.

[Boulder]

A good option would be to output the first pass to NUL if normalization is forced by the user.

[tebasuna51]

Maybe, but with a wav file the second pass don't need re-decode source.

[thomaz909]

isn't encoding the bottleneck in the whole process?

i would really love to have an option to -normalize "onthefly".
ssd wear, small ramdisks.
~107mins ac3 640 produced a 14gb 64bit wav 5.1 file, only to get the 4-5 digit db value.

[Asmodian]

Originally Posted by tebasuna51

Maybe, but with a wav file the second pass don't need re-decode source.

Or even worse, re-extract if from the BD!

Originally Posted by thomaz909

isn't encoding the bottleneck in the whole process?

i would really love to have an option to -normalize "onthefly".
ssd wear, small ramdisks.
~107mins ac3 640 produced a 14gb 64bit wav 5.1 file, only to get the 4-5 digit db value.

To do normalizing well you need to read the entire file before writing anything. Maybe it could be cached in memory (assuming there is enough free memory) or recompressed to flac for the intermediate file, to reduce IO, but true on the fly normalizing is a bad idea.

[sneaker_ger]

Originally Posted by Asmodian

To do normalizing well you need to read the entire file before writing anything.

But you don't need to store the decoded data of the first pass. Only store the peak volume. That's just one value that gets updated when you find a new peak. O(1).