On 9/18/16 9:32 PM, Charles wrote: > On 09/18/2016 06:00 AM, Carl Eugen Hoyos wrote: >> 2016-09-18 6:16 GMT+02:00 Charles <lin...@orion15.org>: >> >>> Think there is an issue >>> Version 2.6.8 from linuxtech repo is working >>> Version 3.1.3 from ffmpeg is not >> >> Which commit introduced the regression? >> >> Carl Eugen > > Sorry, don't know, I am not an ffmpeg developer, I just use the libs. > My current application is broken because I can not receive (demux) RTP > stream. Well, Git bisect makes it easy enough to locate the issue, reducing the number of rebuilds significantly. It will start in the middle of a range you specify, and you will determine if the resulting commit compiles to broken code or not by building and testing, then reporting back to Git whether the build is working or broken. It will jump halfway forward or backward from your last commit, depending on working or broken, until you find the exact commit that broke it.
If you cannot test it, perhaps you can share your test streams (privately) with me and I can bisect it for you, assuming it breaks for me at all. > > Thanks > cco > > > _______________________________________________ > Libav-user mailing list > Libavfirstname.lastname@example.org > http://ffmpeg.org/mailman/listinfo/libav-user
Description: OpenPGP digital signature
_______________________________________________ Libav-user mailing list Libavemail@example.com http://ffmpeg.org/mailman/listinfo/libav-user