Please don't top-post on this list. On Wed, 2010-10-27 at 11:19 +0200, Ján Kolár wrote: > > Dňa 26. 10. 2010 16:32, Tomas Härdin wrote / napísal(a): > >> On Tue, 2010-10-26 at 16:20 +0200, Ján Kolár wrote: > >>> When generating mpeg-ts stream using ffmpeg, I have observed, that > PCR > >>> marks are spaced too far apart one from another. Typical PCR > period is > >>> about 60 - 70 ms which is a way too much. Another problem is that > this > >>> value considerable varies at some moments. Especially on dynamic > scenes > >>> I have seen extraordinarily big PCR periods ranging to several > hundreds > >>> of milliseconds. Because of this I have disordered timing in > output > >>> module which sends created stream to network QAM modulator > >>> (http://www.dektec.com/Products/IP/DTE-3114/). My output buffer > can > >>> accomodate max. 250 ms block of data. I have suspicion that this > is a > >>> ffmpeg bug, but not sure. Has this happened to someone? > >>> > >>> Jan > >> I posted a couple of patches related to PCR generation a few weeks > ago. > >> They have not been OK'd to commit yet though. Do try them out since > >> feedback on them would be good. > >> > >> The following thread deals with PCR jitter and accuracy > improvement: > >> > >> > https://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2010-September/097856.html > >> > >> > >> The latest version of that patch is at: > >> > http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2010-October/098479.html > >> > >> > >> > >> This thread deals with forcing PCR to be written more often, at the > cost > >> of some overhead. It is probably closer to what you want: > >> > >> > https://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2010-October/098484.html > >> > >> > >> /Tomas > >> > Dňa 27. 10. 2010 11:15, Ján Kolár wrote / napísal(a): > > How can I apply changes you sent to my source code? I downloaded > > ffmpeg trunk from svn, successfully compiled. Now trying implement > > changes from > > > http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2010-October/098479.html > > > > I am using following command: > > "D:\Install\_Programming\GIT>git apply > > --directory=C:\msys\1.0\home\ffmpeg patch2.diff" (patch2.diff is > > renamed attachment.bin) > > > > Getting following errors: > > patch2.diff:9: trailing whitespace. > > #define PCR_TIME_BASE 27000000 > > patch2.diff:10: trailing whitespace. > > > > patch2.diff:19: trailing whitespace. > > int64_t first_pcr; > > patch2.diff:37: trailing whitespace. > > ts->first_pcr = av_rescale(s->max_delay, PCR_TIME_BASE, > > AV_TIME_BASE); > > patch2.diff:45: trailing whitespace. > > static int64_t get_pcr(const MpegTSWrite *ts, ByteIOContext *pb) > > error: patch failed: C:\msys\1.0\home > \ffmpeg/libavformat/mpegtsenc.c:27 > > error: C:\msys\1.0\home\ffmpeg/libavformat/mpegtsenc.c: patch does > not > > apply > > > > Nevertheless changes were applied and compilation was successfull. > Just > don't understand what does this error message mean.
Uhm, if patching failed then the changes obviously weren't applied. Double-check with svn diff. Since the patches are a few weeks old, try applying them to revision 25366 (that's where they are in my local git tree). You could also apply them using patch, like "patch -p1 < foo.patch". It should leave failed hunks in the files with the usual "<<<" lines, so you can/must correct the conflicts. /Tomas
signature.asc
Description: This is a digitally signed message part
_______________________________________________ libav-user mailing list [email protected] https://lists.mplayerhq.hu/mailman/listinfo/libav-user
