[FFmpeg-user] I am getting error while download.

2018-02-19 Thread swades
Hello Respected's i m new here. & also new user of ffmpeg. i was able to record or capture through m3u8. But now i am getting Error *[https @ 005c2ea0] HTTP error 404 Not Found. * Screenshot_31.jpg please resolve my

Re: [FFmpeg-user] I am getting error while download.

2018-02-19 Thread Reindl Harald
Am 20.02.2018 um 02:50 schrieb swades: Hello Respected's i m new here. & also new user of ffmpeg. i was able to record or capture through m3u8. But now i am getting Error *[https @ 005c2ea0] HTTP error 404 Not Found "404 Not Found" is a pretty clear response from the webserver you

Re: [FFmpeg-user] I am getting error while download.

2018-02-19 Thread swades
Hello Respected please don't mind. i think others are able to download where from i got error message. -- Sent from: http://www.ffmpeg-archive.org/ ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user To

Re: [FFmpeg-user] FFMPEG convert MXF OP-1b to DNxHD error getting stream index 385942017

2018-02-19 Thread Marton Balint
On Mon, 19 Feb 2018, Hannes Kuehn wrote: Hi, my question regarding the problem is basicly the same as in this mail https://ffmpeg.org/pipermail/ffmpeg-user/2017-March/035541.html but there was no solution yet. We need to convert MXF OP-1b to DNxHD so that our Avid Media Composer will be

[FFmpeg-user] FFMPEG convert MXF OP-1b to DNxHD error getting stream index 385942017

2018-02-19 Thread Hannes Kuehn
Hi, my question regarding the problem is basicly the same as in this mail https://ffmpeg.org/pipermail/ffmpeg-user/2017-March/035541.html but there was no solution yet. We need to convert MXF OP-1b to DNxHD so that our Avid Media Composer will be able to handle the files. Media info and

Re: [FFmpeg-user] FFMPEG convert MXF OP-1b to DNxHD error getting stream index 385942017

2018-02-19 Thread Carl Eugen Hoyos
2018-02-19 19:33 GMT+01:00 Marton Balint : > > On Mon, 19 Feb 2018, Hannes Kuehn wrote: >> my question regarding the problem is basicly the same as in this mail >> https://ffmpeg.org/pipermail/ffmpeg-user/2017-March/035541.html >> >> but there was no solution yet. >> >> We need to