Re: [FFmpeg-user] How to resolve conflicting errors in copying stream

2017-02-20 Thread Carl Eugen Hoyos
2017-02-20 12:03 GMT+01:00 Sub Phil : > Because: "This is deprecated and will STOP WORKING in the future. Fix > your code to set the timestamps properly" > > And I haven't found how to fix it. The fix has to be made by the ffmpeg developers, not the users. Please do not break mail threads, Carl

Re: [FFmpeg-user] How to resolve conflicting errors in copying stream

2017-02-20 Thread Sub Phil
>* Executing *>* ffmpeg -y -i VTS_01_2.VOB -c copy -t 50 VTS_01_2_CUT.VOB *>>* Leads to this warning *>* Timestamps are unset in a packet for stream 0. This is deprecated *>* and will STOP WORKING in the future. Fix your code to set the *>* timestamps properly * This warning should have no relevanc

Re: [FFmpeg-user] How to resolve conflicting errors in copying stream ??

2017-02-16 Thread Carl Eugen Hoyos
2017-02-15 10:05 GMT+01:00 Sub Phil : > Executing > ffmpeg -y -i VTS_01_2.VOB -c copy -t 50 VTS_01_2_CUT.VOB > > Leads to this warning > Timestamps are unset in a packet for stream 0. This is deprecated > and will STOP WORKING in the future. Fix your code to set the > timestamps properly This warn

[FFmpeg-user] How to resolve conflicting errors in copying stream ??

2017-02-15 Thread Sub Phil
Hi, Executing ffmpeg -y -i VTS_01_2.VOB -c copy -t 50 VTS_01_2_CUT.VOB Leads to this warning Timestamps are unset in a packet for stream 0. This is deprecated and will STOP WORKING in the future. Fix your code to set the timestamps properly PROBLEM: how to lossless copy? Now, if I try ffmpeg -y