View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000310 | eac3to | bug | public | 2015-06-11 16:00 | 2015-11-01 16:15 |
Reporter | tebasuna51 | Assigned To | madshi | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Summary | 0000310: Use ffmpeg like external encoder | ||||
Description | To use ffmpeg like external encoder I make some test: 1) eac3to input stdout.wav | ffmpeg -i - -c:a ac3 -b:a 640k wav.ac3 - eac3to send to stdout a wav header with RIFF_length and data_length near to 4 GB, and finish without errors. - ffmpeg seems work fine with short audios, thats means than do a implicit -ignorelength with piped data. - Of course with data > 4 GB ffmpeg cut the encode and finish with a file short than input. 2) eac3to input stdout.w64 | ffmpeg -i - -c:a ac3 -b:a 640k w64.ac3 - eac3to send to stdout a w64 header with riff_length and data_length near to 4 GB, and finish with this ERROR, with any input length: Writing W64... Creating file "stdout.w64"... The W64 writer couldn't seek to the header. <ERROR> Aborted at file position 1886250. <ERROR> - ffmpeg work until the eac3to crash, but output a encode short than input and a error like: [pcm_s24le @ 0000000002d19700] Invalid PCM packet, data has size 8 but at least a size of 18 was expected Error while decoding stream #0:0: Invalid data found when processing input 3) I test ffmpeg piping a w64 file with riff_length and data_length greater than file length and work fine. Then we can use stdout.w64 with two simple changes, I think, in eac3to: a) Don't crash with: The W64 writer couldn't seek to the header. <ERROR> Like don't crash when use stdout.wav b) Put a higer value in fields riff_length and data_length of w64 header. Maybe 1 Tera is enough. | ||||
Tags | No tags attached. | ||||
eac3to Version | 3.29 | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2015-06-11 16:00 | tebasuna51 | New Issue | |
2015-11-01 16:15 | madshi | Note Added: 0001229 | |
2015-11-01 16:15 | madshi | Status | new => closed |
2015-11-01 16:15 | madshi | Assigned To | => madshi |
2015-11-01 16:15 | madshi | Resolution | open => fixed |