[FFmpeg-user] flame about confusing command line options.

As a note, I just had to get this off my chest, and I'll only say this once. Some of FFmpeg's command line syntax is *confusing* and *super confusing* for beginners. For instance this: ffmpeg -r 30 -i input_file specifies a framerate *override* for the input, however if you specify it for the

Re: [FFmpeg-user] flame about confusing command line options.

Roger Pack gmail.com> writes: > ffmpeg -i input -f rawvideo -f nut output.nut > > Using (or being able to use) "-f" > typically using two "-f" s would be an override. > But in this case it isn't. In fact, its using > "-f" to specify two entirely different aspects of > the output file. I

Re: [FFmpeg-user] ffmpeg makes some sources darker

Jim Worrall wrote: Strange, unless there is something in the pngs that causes a different viewer to produce different output. I looked again (display from ancient imagemagic) and can't see any difference - psnr/ssim agree. The pngs are not the same md5sum wise OK - you’re definitely getting

Re: [FFmpeg-user] Need help; willing to pay

Matthew Adams matthewadams.me> writes: > goo.gl/Bb6tQW Which player plays this file at the correct speed? Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Re: [FFmpeg-user] Ingest of SMPTE-377M

>But my question was if there is a receiver >that plays the eac3 spdif file you uploaded: So the specific file that I posted here: https://www.dropbox.com/s/tec7al5bcmihwey/sample.eac3.337.wav?dl=0 Works fine in my configuration, which is: File playing in AJA Control Room, which generates an SDI

Re: [FFmpeg-user] flame about confusing command line options.

Am 05.01.2016 um 16:32 schrieb Paul B Mahol: On 1/5/16, Reindl Harald wrote: Am 05.01.2016 um 16:21 schrieb Michael Koch: For example, Harald Reindl just wrote: "and when you specify something twice the right one wins" Is this already in the FFmpeg documentation?

Re: [FFmpeg-user] ffmpeg makes some sources darker

> On 2016 Jan 5, at 8:38 AM, Andy Furniss wrote: > > Should be that, the png is a different issue/feature - I don't know > what's correct or not. I guess you saw my other post that showed the > gamma difference. Whether you see it or not is going to be down to the >

Re: [FFmpeg-user] Need help; willing to pay

Wow thanks Carl. Two questions. 1. Is 1.65s consistent on both ends of the video & in both videos? 2. If so, can cut (on both ends), transcode & merge be scripted with bash & ffmpeg? On Tue, Jan 5, 2016 at 10:32 AM, Another Sillyname < anothersn...@googlemail.com> wrote: > It's at 1.65

Re: [FFmpeg-user] flame about confusing command line options.

> thinking one can develop a GUI which is usable and supports all of the >  >features of ffmpeg or even a large part of them is naive Well, possibly, but the problem is that the CLI doesn't do a very good job of it either. Inasmuch as CLI discoverability is effectively zero, it doesn't do any 

Re: [FFmpeg-user] flame about confusing command line options.

Am 05.01.2016 um 17:00 schrieb Phil Rhodes: thinking one can develop a GUI which is usable and supports all of the > features of ffmpeg or even a large part of them is naive Well, possibly, but the problem is that the CLI doesn't do a very good job of it either. Inasmuch as CLI

Re: [FFmpeg-user] Need help; willing to pay

It's at 1.65 seconds it goes into 'slo mo' mode, but there's no change in framerate reported by either ffmpeg or mplayer and 'proper' speed would appear to need it to be run at about 220 fps after 1.65 seconds. Bit weird. Can't see an immediate way to do this without manual cut, transcode and

Re: [FFmpeg-user] ffmpeg makes some sources darker

> I’m not really looking for perfection, just don’t want the transcodes to be > darker on any device. > > So my testing has shown, for both libx264 and libx265, the problem is > solved (meaning the pngs come out with the same luminosity, which > is good enough for me) either of two ways, using

Re: [FFmpeg-user] Need help; willing to pay

Only d/loaded one...am away from machine now. Are you running IOS on your desktop machine? On 5 January 2016 at 17:09, Matthew Adams wrote: > Wow thanks Carl. Two questions. > > 1. Is 1.65s consistent on both ends of the video & in both videos? > 2. If so, can cut (on

Re: [FFmpeg-user] flame about confusing command line options.

I think in general a lot of problems with commandline software in general exist when the software begins to exceed the ability of a commandline to act as a workable UI. Naturally there are reasons to provide serialised instructions to a piece of software, but in many cases that isn't really

Re: [FFmpeg-user] flame about confusing command line options.

Am 05.01.2016 um 16:03 schrieb Michael Koch: What part of this mailing list thread is not documented in your opinion? For example, Harald Reindl just wrote: "and when you specify something twice the right one wins" Is this already in the FFmpeg documentation? that's common sense

Re: [FFmpeg-user] flame about confusing command line options.

On 1/5/16, Reindl Harald wrote: > > > Am 05.01.2016 um 16:21 schrieb Michael Koch: For example, Harald Reindl just wrote: "and when you specify something twice the right one wins" Is this already in the FFmpeg documentation? >>> >>> that's common sense

Re: [FFmpeg-user] flame about confusing command line options.

On Tue, Jan 05, 2016 at 07:04:11 -0700, Roger Pack wrote: > As a note, I just had to get this off my chest, and I'll only say this > once. Some of FFmpeg's command line syntax is *confusing* and *super > confusing* for beginners. That may be the case. :-) Feel free to suggest improvements to

Re: [FFmpeg-user] flame about confusing command line options.

Am 05.01.2016 um 15:43 schrieb Phil Rhodes: I think in general a lot of problems with commandline software in general exist when the software begins to exceed the ability of a commandline to act as a workable UI. Naturally there are reasons to provide serialised instructions to a piece of

Re: [FFmpeg-user] flame about confusing command line options.

Am 05.01.2016 um 16:21 schrieb Michael Koch: For example, Harald Reindl just wrote: "and when you specify something twice the right one wins" Is this already in the FFmpeg documentation? that's common sense for you, but not for a beginner well, then i ask the question different

Re: [FFmpeg-user] flame about confusing command line options.

Michael Koch t-online.de> writes: > For many questions, it might be better not to answer > them here. Instead, please add the answers to the > documentation and then just post a link. What part of this mailing list thread is not documented in your opinion? Carl Eugen

[FFmpeg-user] Need help; willing to pay

Hi, I'm a software developer myself, but just don't have the time to fix a problem that I'm having. I grabbed some videos recorded by Coach's Eye on iOS from my phone, and they seem to use variable bitrates within the video. A sample video file (.mov format) is available via my Google Drive

Re: [FFmpeg-user] flame about confusing command line options.

As mentioned, documentation improvements are *always* welcome. I agree with Roger that for a beginner FFmpeg's documentation leaves many questions unanswered. It would be great to have more details and especially more examples in the documentation. Many questions are answered in this user

Re: [FFmpeg-user] flame about confusing command line options.

For example, Harald Reindl just wrote: "and when you specify something twice the right one wins" Is this already in the FFmpeg documentation? that's common sense for you, but not for a beginner. Michael ___ ffmpeg-user mailing list

Re: [FFmpeg-user] ffmpeg makes some sources darker

Carl Eugen Hoyos wrote: Andy Furniss gmail.com> writes: I think it's because the master is flagged as rec709 but the yuv and I guess hevc aren't. While this is at least likely (sorry for my original comment, I don't know what I looked at), the source code seems to disagree: colour_primaries

Re: [FFmpeg-user] flame about confusing command line options.

What part of this mailing list thread is not documented in your opinion? For example, Harald Reindl just wrote: "and when you specify something twice the right one wins" Is this already in the FFmpeg documentation? Michael ___ ffmpeg-user mailing

Re: [FFmpeg-user] Ingest of SMPTE-377M

Hi Carl, I am unable to recreate the results you are describing here. Starting with the sample.ac3 file I posted a copy of earlier: https://www.dropbox.com/s/ripe53oci6wz7t6/sample.ac3?dl=0 Packaging it with smpte 337M: ffmpeg -i sample.ac3 -acodec ac3 -f spdif sample.ac3.spdif Gives this

Re: [FFmpeg-user] flame about confusing command line options.

well, then i ask the question different "--width=600 --width=300" - what would you expect? before I saw your answer, it was unclear to me if it's 300 or 600. Michael ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org

Re: [FFmpeg-user] ffmpeg makes some sources darker

Jim Worrall wrote: I’m not really looking for perfection, just don’t want the transcodes to be darker on any device. So my testing has shown, for both libx264 and libx265, the problem is solved (meaning the pngs come out with the same luminosity, which is good enough for me) either of two ways,

Re: [FFmpeg-user] Need help; willing to pay

No, I'm not running iOS on my desktop. It's a MacBook Pro w/El Capitan. I pulled the files off of the iPhone using iExplorer, a nice little tool to get at the iOS filesystem. On Tue, Jan 5, 2016 at 11:14 AM, Another Sillyname < anothersn...@googlemail.com> wrote: > Only d/loaded one...am away

Re: [FFmpeg-user] Need help; willing to pay

Here is a link to zipped copies of originals placed on my dropbox account. I zipped them in order to reduce the likelihood that they're changed by the file hosting service. https://www.dropbox.com/s/31civbxpe1utote/2016-01-02%2C%20Tour%20Warm%20Up.zip?dl=0 On Tue, Jan 5, 2016 at 2:08 PM,

Re: [FFmpeg-user] flame about confusing command line options.

Am 05.01.2016 um 15:04 schrieb Roger Pack: As a note, I just had to get this off my chest, and I'll only say this once. Some of FFmpeg's command line syntax is *confusing* and *super confusing* for beginners. For instance this: ffmpeg -r 30 -i input_file specifies a framerate *override*

Re: [FFmpeg-user] Need help; willing to pay

On Tue, Jan 05, 2016 at 13:30:07 -0600, Matthew Adams wrote: > I pulled the files off of the iPhone using iExplorer, a nice little tool to > get at the iOS filesystem. Hmm. Something tells me this isn't the raw video as it comes from your device, but it was manipulated by Google (Drive) after

Re: [FFmpeg-user] ffmpeg makes some sources darker

> > Ouch, did the new file show as 709 with > > ffmpeg -i newfile.mkv > > I can't reproduce this one myself x265-params seems to work. > If for some reason the newfile didn't get flagged as 709 then it could be > possible to get brighter with different colours in a scene. Yes. The ORIGINAL

Re: [FFmpeg-user] ffmpeg makes some sources darker

> Yes, that's probably it. > > Maybe you could try below to see if the original shows 709 - > > ffmpeg -analyzeduration 100M -probesize 100M -i original.m2ts > > FWIW I just noticed another issue - using pass 1 and pass 2 via ffmpeg > doesn't work for libx265. > > It does work if you use it

Re: [FFmpeg-user] Need help; willing to pay

u intend to play it on. > > > > If the quality is too low for you you can always get higher bitrates > > with eg. -crf 20. > > > > FWIW testing the master direct mpv by default does a good job playing it > > on my PC. > > > > ___ > > ffmpeg-user mailin

Re: [FFmpeg-user] Can FFmpeg fetch a title from a DVD?

Thank you for all the suggestions. I want to stick to open-source if possible, on principle. I tried MPlayer, but I got an error; libdvdread complained that it couldn't open the file with libdvdcss. Not sure why. It seemed to open the DVD OK, because it told me the correct number of titles on

Re: [FFmpeg-user] Can FFmpeg fetch a title from a DVD?

On Tue, Jan 5, 2016 at 5:59 PM, Nicholas Robbins wrote: > You might also want to take a look at makemkv (makemkv.com) Second the nomination of MakeMKV. Not free, but it has a linux version that you can "compile" and install. In my experience, MakeMKV is the

Re: [FFmpeg-user] Need help; willing to pay

er mailing list > ffmpeg-user@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-user Tested on the windows 10 side of my laptop with the command: "C:\Users\Steve\Desktop\ffmpeg-20160105-git-68eb208-win64-static\bin>ffmpeg -i C:\Users\Steve\Desktop\Jan22016-150PM-b6cs7

Re: [FFmpeg-user] Can FFmpeg fetch a title from a DVD?

You would try Free DVD ripper at http://www.free-star.org/free-dvd-ripper-freeware.html At 2016-01-06 10:42:13, "Steve Boyer" wrote: >On Tue, Jan 5, 2016 at 5:59 PM, Nicholas Robbins > wrote: >> You might also want to

Re: [FFmpeg-user] Need help; willing to pay

; I suppose it depends on what you intend to play it on. >> > >> > If the quality is too low for you you can always get higher bitrates >> > with eg. -crf 20. >> > >> > FWIW testing the master direct mpv by default does a good job playing it >> > on m

Re: [FFmpeg-user] ffmpeg makes some sources darker

> On 2016 Jan 5, at 3:13 PM, Jim Worrall wrote: > >> Currently I just get an empty ffmpeg2pass-0.log and pass 1 is as slow as >> pass 2. As expected he result is worse as well. >> > Uh-oh, I thought that’s what was supposed to happen (except for the worse > result

Re: [FFmpeg-user] Need help; willing to pay

Matthew Adams matthewadams.me> writes: > https://www.dropbox.com/s/31civbxpe1utote/2016-01-02%2C%20Tour%20Warm%20Up.zip These videos can be decoded with FFmpeg, you just have to define what you want to do with them. Please do not top-post here, Carl Eugen

[FFmpeg-user] Can FFmpeg fetch a title from a DVD?

Can anyone tell me if there's a command to fetch a title (this is DVD-speak for a 'track') from a DVD file structure? I have a DVD structure in a VIDEO_TS folder, and I want to fetch title #7 from it, and convert it to something. This requires FFmpeg to be aware of the DVD menu structure, and

Re: [FFmpeg-user] flame about confusing command line options.

Reindl Harald thelounge.net> writes: > when you specify something twice the right one wins I fear it's not that easy: It is actually undefined behaviour to specify an option twice (that is not supposed to be specified more than once), so for example ticket #4184. Carl Eugen

Re: [FFmpeg-user] Need help; willing to pay

On Tue, Jan 05, 2016 at 14:51:46 -0600, Matthew Adams wrote: > > https://www.dropbox.com/s/31civbxpe1utote/2016-01-02%2C%20Tour%20Warm%20Up.zip?dl=0 Ah, those are indeed different. They are true VFR. > Don't forget that these videos were created by Coach's Eye > for

Re: [FFmpeg-user] ffmpeg makes some sources darker

Jim Worrall wrote: Yes, that's probably it. Maybe you could try below to see if the original shows 709 - ffmpeg -analyzeduration 100M -probesize 100M -i original.m2ts FWIW I just noticed another issue - using pass 1 and pass 2 via ffmpeg doesn't work for libx265. It does work if you use it

Re: [FFmpeg-user] Need help; willing to pay

Matthew Adams wrote: On Tue, Jan 5, 2016 at 3:07 PM, Moritz Barsnick wrote: Anyway, it should be possible to convert those to something sane. As Carl Eugen mentions: What's your goal? My goal is to convert these videos a fixed, relatively standard (30 fps? 60 fps?) frame

Re: [FFmpeg-user] ffmpeg makes some sources darker

> On 2016 Jan 5, at 5:17 PM, Andy Furniss wrote: > I snipped some other "evidence" in my last post. > > If you want to check outputs between the two ways look at the last > lines of the larger block of x265 [info]. > > with ffmpeg the last 2 lines of both pass 1 and 2 are

Re: [FFmpeg-user] ffmpeg makes some sources darker

Jim Worrall wrote: On 2016 Jan 5, at 5:17 PM, Andy Furniss wrote: I snipped some other "evidence" in my last post. If you want to check outputs between the two ways look at the last lines of the larger block of x265 [info]. with ffmpeg the last 2 lines of both pass 1

Re: [FFmpeg-user] ffmpeg makes some sources darker

> On 2016 Jan 5, at 6:06 PM, Andy Furniss wrote: > I would double check your command line(s) - if they seem OK paste it/them > along with the full output(s). > You are so right. I had pass=1 twice (I’m going to hide under a rock now). Now I get: x265 [info]: tools: rd=2

[FFmpeg-user] ffplay and increasing delay (latency)

Hello, I'm using ffplay to play an RTMP stream from the nginx/rtmp server. The stream from the microphone is being captured with ffmpeg as follows: ffmpeg -fflags nobuffer -re -f alsa -i hw:0,0 -c:a nellymoser \ -ar 11025 -ab 8k -ac 1 -f flv rtmp://192.168.88.244/live/1 Next, I have

Re: [FFmpeg-user] ffmpeg makes some sources darker

Jim Worrall wrote: On 2016 Jan 5, at 4:28 PM, Andy Furniss wrote: Jim Worrall wrote: On 2016 Jan 5, at 3:13 PM, Jim Worrall wrote: Currently I just get an empty ffmpeg2pass-0.log and pass 1 is as slow as pass 2. As expected he result is worse

Re: [FFmpeg-user] ffmpeg makes some sources darker

Jim Worrall wrote: Ouch, did the new file show as 709 with ffmpeg -i newfile.mkv I can't reproduce this one myself x265-params seems to work. If for some reason the newfile didn't get flagged as 709 then it could be possible to get brighter with different colours in a scene. Yes. The

Re: [FFmpeg-user] Need help; willing to pay

Don't forget that these videos were created by Coach's Eye for iOS. I don't know anything about their internals WRT recording videos. On Tue, Jan 5, 2016 at 2:50 PM, Matthew Adams wrote: > Here is a link to zipped copies of originals placed

Re: [FFmpeg-user] ffmpeg makes some sources darker

> On 2016 Jan 5, at 4:28 PM, Andy Furniss wrote: > > Jim Worrall wrote: >> >>> On 2016 Jan 5, at 3:13 PM, Jim Worrall >>> wrote: >>> Currently I just get an empty ffmpeg2pass-0.log and pass 1 is as slow as pass 2. As expected he result is

Re: [FFmpeg-user] Can FFmpeg fetch a title from a DVD?

> On Tuesday, January 5, 2016 4:25 PM, Matt Zagrabelny > wrote: > > On Tue, Jan 5, 2016 at 3:20 PM, Andy Civil wrote: >> Can anyone tell me if there's a command to fetch a title (this is > DVD-speak >> for a 'track') from a DVD file structure? I have

Re: [FFmpeg-user] ffmpeg makes some sources darker

Jim Worrall wrote: On 2016 Jan 5, at 3:13 PM, Jim Worrall wrote: Currently I just get an empty ffmpeg2pass-0.log and pass 1 is as slow as pass 2. As expected he result is worse as well. Uh-oh, I thought that’s what was supposed to happen (except for the worse result