<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Thanks again for the clarification!<div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">And about „wrong mailing list“, any recommendations for the correct one?<br class="">ffmpeg-devel?<br class=""></blockquote><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">No questions should ever be sent there, but if you have a question</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">concerning the ffmpeg command line tool (your email indicated</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">this), then ffmpeg-user is the right mailing list.</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""></div></blockquote></div><br class=""></div><div class="">Well, not really. In my original email I was (somewhat reluctantly, because maybe I wouldn’t even be capable) </div><div class="">offering to work on the source code and try improving that issue, that’s why I thought it might be relevant to ffmpeg-devel. </div><div class=""><br class=""></div><div class="">But indeed it had a question-part, but that question was more about the mp2-format, not so much about ffmpeg usage </div><div class="">(already assuming that with different ffmpeg-usage I cannot do anything about it), </div><div class="">and that’s why I eventually posted it here, on libav-user. </div><div class="">However, it seems that in the meantime I found a workaround that removes my need to look into the source code…</div><div class=""><br class=""></div><div class="">Instead of using the original command which has 4 seconds of delay:</div><div class=""><br class=""></div><div class="">ffmpeg -ss 4:0:0 -i bigfile.mp2 test.mp3</div><div class=""><br class=""></div><div class="">I’m now using the following combination of dd (on Linux, in order to cut a portion of a file) and ffmpeg without noticable delay:</div><div class=""><br class=""></div><div class="">dd ibs=1152 skip=600000 count=200 if=bigfile.mp2 | ffmpeg -i pipe:0 test.mp3</div><div class=""><br class=""></div><div class="">In my example file, my frames have a constant frame size of 1152 bytes with a duration of 24ms. So I skip 600000 blocks of 24ms which correspond to 4 hours.</div><div class="">This command starts transcoding without any noticable delay!</div><div class=""><br class=""></div><div class="">I actually think that this kind of information could be interesting for ffmpeg-devel. Or should I file something on bug-tracker?</div></body></html>