[FFmpeg-user] Sony FX3 timecode (or the lack of it...)

2024-04-29 Thread Bouke / edit 'B
This cam writes Mp4 without a QuickTime timecode track, but it does write 
’something’ that ’should’ be (about) correct. (It’s a known issue it’s off by 
one or two frames when slaved.)

ffprobe -v error -print_format json -show_format -show_streams 
/Users/bouke/Downloads/Sony\ FX3/PRIVATE/M4ROOT/CLIP/20240227_C6917.MP4 
Partial return:

{
"index": 2,
"codec_type": "data",
"codec_tag_string": "rtmd",
"codec_tag": "0x646d7472",
"id": "0x3",
"r_frame_rate": "0/0",
"avg_frame_rate": "0/0",
"time_base": "1/3",
"start_pts": 0,
"start_time": "0.00",
"duration_ts": 1261260,
"duration": "42.042000",
"bit_rate": "4664775",
"nb_frames": "1260",
"disposition": {
"default": 1,
"dub": 0,
"original": 0,
"comment": 0,
"lyrics": 0,
"karaoke": 0,
"forced": 0,
"hearing_impaired": 0,
"visual_impaired": 0,
"clean_effects": 0,
"attached_pic": 0,
"timed_thumbnails": 0,
"captions": 0,
"descriptions": 0,
"metadata": 0,
"dependent": 0,
"still_image": 0
},
"tags": {
"creation_time": "2024-02-27T10:22:27.00Z",
"language": "und",
"handler_name": "Timed Metadata Media Handler",
"timecode": "05:37:06:19"
}
}



Now, where is this TC stored? I cannot find it using a HEX editor.
And, more important, FCP, Avid MC and Resolve interpret the “timecode” as Drop 
frame, where there is no indication of that in FFmpeg / FFprobe.
Can anyone shed a light on this?


thx,

Bouke
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Hyper fast gone in Gyan's binaries

2024-04-09 Thread Bouke / edit 'B


> On 9 Apr 2024, at 13:45, Gyan Doshi  wrote:
> 
> 
> 
> On 2024-04-09 02:46 pm, Bouke / edit 'B wrote:
>> For my work I try an install of FFmpeg by running it without any params.
>> 
>> It used to be that the return would include ‘Hyper fast’.
>> However, the current binaries from Gyan do not include that, but state 
>> ‘Universal media encoder’.
> 
> That description was changed in 86e8439994d86b33f9b22ad64c4a31a559f05aac
>> 
>> What would be a good, future proof way of testing if FFmpeg is indeed 
>> installed / running properly?
> 
> Try
> 
>  ffmpeg -f lavfi -i nullsrc -t 0.1 -v 0 -progress pipe:1 -f null - | grep end
> 
> If grep returns nothing, then something went wrong.

Hi Gyan, 
Thanks.
But what to youse for FFprobe / FFlay?

Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


[FFmpeg-user] Hyper fast gone in Gyan's binaries

2024-04-09 Thread Bouke / edit 'B
For my work I try an install of FFmpeg by running it without any params.

It used to be that the return would include ‘Hyper fast’.
However, the current binaries from Gyan do not include that, but state 
‘Universal media encoder’.

What would be a good, future proof way of testing if FFmpeg is indeed installed 
/ running properly?


Bouke



___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] ffplay - no delay between playbacks when looping

2024-03-26 Thread Bouke / edit 'B
 
> On 26 Mar 2024, at 09:57, computermaster360  
> wrote:
> 
> I want to loop a short wav sample, which is an 8-bar melody:
> 
>ffplay -loop 0 sample.wav
> 
> There is a small, but perceptible delay between individual playbacks
> of the sample, which throws the melody off. Is there a way to make the
> playback completely continuous with no delay?

Not tested, but I would try to do the loop in FFmpeg and pipe to FFplay.
This way FFplay will get just samples, bypassing whatever happens on restart 
playback of the file.

Bouke


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Wave channel split is very slow

2024-02-24 Thread Bouke / Videotoolshed
On 24 Feb 2024, at 12:37, Paul B Mahol  wrote:
> 
> On Sat, Feb 24, 2024 at 11:33 AM Bouke / Videotoolshed <
> bo...@videotoolshed.com> wrote:
> 
>> Trying to split a 64 channel 48Khz 24 bits Wave file.
>> That is VERY slow.
>> 
>> ffmpeg -i /Volumes/Data/magweg/64channel.wav -filter_complex
>> "[0]pan=mono|c0=c0[tr0]" -c:a pcm_s24le -map "[tr0]"
>> /Volumes/Data/magweg/64_test/out_1.wav
>> 
>> Runs at about 15x
>> 
>> But if I do all 64 in one pass, it slows down to about 0.7x
>> 
>> I don’t get it. DiskIO should not be a factor, and there is no math
>> involved. (Granted, the ppm_s24le might involve math, but that should be
>> simple.)
>> 
>> Is this a bug?
>> (Same happens vice versa, going from multiple non-interleaved to one big
>> interleaved Wave.)
>> 
>> Bouke
>> 
> 
> For demuxing case, use -max_size 400 as input option for wav demuxer,

Hi Paul,

Yup, that helps. It now runs 64 channels at about 16x, that is about 20 times 
faster than before!

> order of this option matters.

Where have I heard this before :-) (I won’t go there, no worries.)


> Issue is if single packets have small number of stored samples it hurts
> performance with ffmpeg utility, recently situation got even worse with
> threading work.
I trust you, but I don’t do C
> I raised concerns and reported it to authorities multiple times without
> results, but got responses that is not relevant but very minor problem.

This IS a serious problem, same as stripping audio only from video has become 
dog slow.
FFmbc used to be able to do that (with -c:a copy) at the speed of drive, FFmpeg 
nowadays seems to read the entire file, including video.
> 
> Dunno what command you use for reverse direction so can not help you on
> that one.

My filter compex is HUGE, it splits all inputs to mono, pads / merges / etc. 
(I’m doing auto sequence style.)
But for now, I’ve got something more to toy with.

Thanks,
Bouke

Better command line (way simplified) that indeed runs faster:
/Applications/ffmpeg -max_size 400 -i 
/Volumes/Data/magweg/64_test/64chans.wav -max_size 400 -filter_complex 
"[0]pan=mono|c0=c0[tr0];[0]pan=mono|c0=c1[tr1];[0]pan=mono|c0=c2[tr2];[0]pan=mono|c0=c3[tr3];[0]pan=mono|c0=c4[tr4];[0]pan=mono|c0=c5[tr5];[0]pan=mono|c0=c6[tr6];[0]pan=mono|c0=c7[tr7];[0]pan=mono|c0=c8[tr8];[0]pan=mono|c0=c9[tr9];[0]pan=mono|c0=c10[tr10];[0]pan=mono|c0=c11[tr11];[0]pan=mono|c0=c12[tr12];[0]pan=mono|c0=c13[tr13];[0]pan=mono|c0=c14[tr14];[0]pan=mono|c0=c15[tr15];[0]pan=mono|c0=c16[tr16];[0]pan=mono|c0=c17[tr17];[0]pan=mono|c0=c18[tr18];[0]pan=mono|c0=c19[tr19];[0]pan=mono|c0=c20[tr20];[0]pan=mono|c0=c21[tr21];[0]pan=mono|c0=c22[tr22];[0]pan=mono|c0=c23[tr23];[0]pan=mono|c0=c24[tr24];[0]pan=mono|c0=c25[tr25];[0]pan=mono|c0=c26[tr26];[0]pan=mono|c0=c27[tr27];[0]pan=mono|c0=c28[tr28];[0]pan=mono|c0=c29[tr29];[0]pan=mono|c0=c30[tr30];[0]pan=mono|c0=c31[tr31];[0]pan=mono|c0=c32[tr32];[0]pan=mono|c0=c33[tr33];[0]pan=mono|c0=c34[tr34];[0]pan=mono|c0=c35[tr35];[0]pan=mono|c0=c36[tr36];[0]pan=mono|c0=c37[tr37];[0]pan=mono|c0=c38[tr38];[0]pan=mono|c0=c39[tr39];[0]pan=mono|c0=c40[tr40];[0]pan=mono|c0=c41[tr41];[0]pan=mono|c0=c42[tr42];[0]pan=mono|c0=c43[tr43];[0]pan=mono|c0=c44[tr44];[0]pan=mono|c0=c45[tr45];[0]pan=mono|c0=c46[tr46];[0]pan=mono|c0=c47[tr47];[0]pan=mono|c0=c48[tr48];[0]pan=mono|c0=c49[tr49];[0]pan=mono|c0=c50[tr50];[0]pan=mono|c0=c51[tr51];[0]pan=mono|c0=c52[tr52];[0]pan=mono|c0=c53[tr53];[0]pan=mono|c0=c54[tr54];[0]pan=mono|c0=c55[tr55];[0]pan=mono|c0=c56[tr56];[0]pan=mono|c0=c57[tr57];[0]pan=mono|c0=c58[tr58];[0]pan=mono|c0=c59[tr59];[0]pan=mono|c0=c60[tr60];[0]pan=mono|c0=c61[tr61];[0]pan=mono|c0=c62[tr62];[0]pan=mono|c0=c63[tr63]"
 -map_metadata -1 -c:a pcm_s24le -map "[tr0]" 
/Volumes/Data/magweg/64_test/speed_1.wav -y -map_metadata -1 -c:a pcm_s24le 
-map "[tr1]" /Volumes/Data/magweg/64_test/speed_2.wav -y -map_metadata -1 -c:a 
pcm_s24le -map "[tr2]" /Volumes/Data/magweg/64_test/speed_3.wav -y 
-map_metadata -1 -c:a pcm_s24le -map "[tr3]" 
/Volumes/Data/magweg/64_test/speed_4.wav -y -map_metadata -1 -c:a pcm_s24le 
-map "[tr4]" /Volumes/Data/magweg/64_test/speed_5.wav -y -map_metadata -1 -c:a 
pcm_s24le -map "[tr5]" /Volumes/Data/magweg/64_test/speed_6.wav -y 
-map_metadata -1 -c:a pcm_s24le -map "[tr6]" 
/Volumes/Data/magweg/64_test/speed_7.wav -y -map_metadata -1 -c:a pcm_s24le 
-map "[tr7]" /Volumes/Data/magweg/64_test/speed_8.wav -y -map_metadata -1 -c:a 
pcm_s24le -map "[tr8]" /Volumes/Data/magweg/64_test/speed_9.wav -y 
-map_metadata -1 -c:a pcm_s24le -map "[tr9]" 
/Volumes/Data/magweg/64_test/speed_10.wav -y -map_metadata -1 -c:a pcm_s24le 
-map "[tr10]" /Volumes/Data/magweg/64_test/speed_11.wav -y -map

[FFmpeg-user] Wave channel split is very slow

2024-02-24 Thread Bouke / Videotoolshed
Trying to split a 64 channel 48Khz 24 bits Wave file.
That is VERY slow.

ffmpeg -i /Volumes/Data/magweg/64channel.wav -filter_complex 
"[0]pan=mono|c0=c0[tr0]" -c:a pcm_s24le -map "[tr0]" 
/Volumes/Data/magweg/64_test/out_1.wav

Runs at about 15x

But if I do all 64 in one pass, it slows down to about 0.7x

I don’t get it. DiskIO should not be a factor, and there is no math involved. 
(Granted, the ppm_s24le might involve math, but that should be simple.)

Is this a bug? 
(Same happens vice versa, going from multiple non-interleaved to one big 
interleaved Wave.)

Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Packet corrupt on cut, notice on concat

2024-02-19 Thread Bouke / Videotoolshed

> On 19 Feb 2024, at 19:23, Reindl Harald  wrote:
> 
> 
> 
> Am 19.02.24 um 19:20 schrieb Bouke / edit 'B:
>> My most sincere apologies to the list.
>> I have a mental condition that forces me to indulge in these kind of 
>> discussions, while it is clearly pointless.
>> Sorry for the waste of bandwidth / your attention.
>> I’ll make a message rule filtering out the OP.
> 
> given our off-list "conversation" started by you your mental conditions need 
> much more than filter out a single invidual

You are totally right, as you always are.
And you have such a nice way of bringing your point across, as you always make 
an effort to be friendly, and help people.

Now I’m stepping out of this.

Bouke



___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Packet corrupt on cut, notice on concat

2024-02-19 Thread Bouke / edit 'B
> 
> On 19 Feb 2024, at 19:14, Mark Filipak  wrote:
> 
> On 19/02/2024 13.11, Bouke / edit 'B wrote:
>>> On 19 Feb 2024, at 19:04, Mark Filipak  wrote:
>>> 
>>> On 19/02/2024 12.59, Bouke / edit 'B wrote:
>>>>> 
>>>>> On 19 Feb 2024, at 18:47, Mark Filipak  wrote:
>>>>> 
>>>>>  I'm not writing a book.
>>>>> That's something someone made up.
>>>> Yes, the ’someone' was you. Search the archives.
>>> 
>>> No, that was not me. You may have misunderstood. I was/am writing 
>>> documentation, not a book.
>> My bad, my apologies if you are indeed correct. Please dive into the 
>> archives.
>>> Kindly stop harassing me.
>> IIRC, you wrote not so long ago that you post not more than 6 entries a year 
>> to this list.
>> What should I think about you?
> 
> I think you might conclude that something has changed.

My most sincere apologies to the list.
I have a mental condition that forces me to indulge in these kind of 
discussions, while it is clearly pointless.

Sorry for the waste of bandwidth / your attention.
I’ll make a message rule filtering out the OP.

Bouke


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Packet corrupt on cut, notice on concat

2024-02-19 Thread Bouke / edit 'B


> On 19 Feb 2024, at 19:04, Mark Filipak  wrote:
> 
> On 19/02/2024 12.59, Bouke / edit 'B wrote:
>>> 
>>> On 19 Feb 2024, at 18:47, Mark Filipak  wrote:
>>> 
>>>  I'm not writing a book.
>>> That's something someone made up.
>> Yes, the ’someone' was you. Search the archives.
> 
> No, that was not me. You may have misunderstood. I was/am writing 
> documentation, not a book.

My bad, my apologies if you are indeed correct. Please dive into the archives.

> Kindly stop harassing me.

IIRC, you wrote not so long ago that you post not more than 6 entries a year to 
this list.
What should I think about you?



___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Packet corrupt on cut, notice on concat

2024-02-19 Thread Bouke / edit 'B
> 
> On 19 Feb 2024, at 18:47, Mark Filipak  wrote:
> 
>  I'm not writing a book.
> That's something someone made up.

Yes, the ’someone' was you. Search the archives.




___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] FFmpeg Architecture (was: Codec copy with -ss before -i and after -i is not documented)

2024-02-12 Thread Bouke / Videotoolshed
Even though I used the word "or" in my post, the use of any of the 
architectural techniques can be mixed.

On the subject of you being a troll, you wrote that you posted no more than 6 
posts a year.

That turns out to be ‘a day’

Go away, or at least shut up.


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Why are these different?

2024-02-11 Thread Bouke / Videotoolshed
So do you, so why ask the question?
Now go away!


> On 11 Feb 2024, at 19:05, Mark Filipak  wrote:
> 
> On 11/02/2024 13.00, Bouke / Videotoolshed wrote:
>> Stop trolling.
>> Read in on the subject. You want to write a FFmpeg manual?
>> Go away, don’t spam the rest of us.
>>> On 11 Feb 2024, at 18:47, Mark Filipak  wrote:
>>> 
>>> Command 1:
>>> ffmpeg -ss 10 -copyts -i this.m2ts -map 0 -c copy -sn -dn -muxdelay 0 
>>> that.m2ts
>>> Command 2:
>>> ffmpeg -copyts -i this.m2ts -map 0 -ss 10 -c copy -sn -dn -muxdelay 0 
>>> that.m2ts
>>> 
>>> Let's ignore all the errors both make. And let's ignore the individual 
>>> errors that they make individually.
>>> 
>>> Should Command 1 and Command 2 make the same outputs? "Yes" or "No"?
> 
> You don't know the answer, do you Bouke?
> 
> 
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Why are these different?

2024-02-11 Thread Bouke / Videotoolshed
Stop trolling.
Read in on the subject. You want to write a FFmpeg manual?
Go away, don’t spam the rest of us.

> On 11 Feb 2024, at 18:47, Mark Filipak  wrote:
> 
> Command 1:
> ffmpeg -ss 10 -copyts -i this.m2ts -map 0 -c copy -sn -dn -muxdelay 0 
> that.m2ts
> Command 2:
> ffmpeg -copyts -i this.m2ts -map 0 -ss 10 -c copy -sn -dn -muxdelay 0 
> that.m2ts
> 
> Let's ignore all the errors both make. And let's ignore the individual errors 
> that they make individually.
> 
> Should Command 1 and Command 2 make the same outputs? "Yes" or "No"?
> 
> I'm not trying to be rude. I'm simply trying to get a definitive answer to a 
> question that goes to the heart of what ffmpeg is and does.
> 
> Regards,
> Mark.
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] The Guild

2024-02-01 Thread Bouke / edit 'B
>  I'd pay $25/month to belong.

I pay 25 bucks for each troll head.

(Or 50 per ball, makes for more fun)

Bouke 

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] '-t' versus '-to'

2024-01-14 Thread Bouke / edit 'B

> On 14 Jan 2024, at 21:22, Carl Zwanzig  wrote:
> 
> On 1/13/2024 10:26 PM, Mark Filipak wrote:
>> For example:
>> -ss 20.061708 -to 5570.815250
>> would be
>> -frametrim 481..134046
>> meaning frame 481 thru frame 134046.
> 
> Although IME it much more common to specify the frame number after a dot* but 
> ffmpeg doesn't seem to do that. (There may be North American vs Europe vs 
> Asiatic regional conventions on this.)
> 
> *hh:mm:ss.ff, or occasionally hh:mm:ss:ff, but the latter is ambiguous if 
> either hh or ff are omitted
> 
> Perhaps some day I'll look at the command arg time parser to see what 
> assumptions are made and where they're documented.

Don’t feed the trolls.

Bouke


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Towards better trims & concatenations

2024-01-08 Thread Bouke / Videotoolshed

> For clarity, I wasn't accusing you of lying and it certainly wasn't my
> intention to imply that; my apologies if it sounded that way!

Don’t feed the trolls


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] sntsc

2023-12-26 Thread Bouke / edit 'B



> On 26 Dec 2023, at 21:13, Mark Filipak  wrote:

How about stopping trolling if you know it all?

The ‘imdb’ in your mail address makes you an even bigger jerk.

Bouke



___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] FFmpeg default processing(invisible processing)

2023-12-20 Thread Bouke / Videotoolshed


> On 19 Dec 2023, at 17:24, Erik Dobberkau  wrote:
> 
>> 
>> @Shuto: I'm sure you've noticed already that you will want to adjust the
>> frame rate (option "-r"). But I'm not sure if that does also require an
>> adjustment of the -bufsize .
>> 
> 
> @Bouke: and it works without explicitly specifying a GOP size of 12 (for
> 50Hz  15 for 60-ish Hz) and a b-frame interval of 2 ?

Hi Eric,
Yup, this is the output of my (commercial) SpotXML app.
https://www.videotoolshed.com/product/spotxml/ 
<https://www.videotoolshed.com/product/spotxml/>

Broadcasters over here have a Baton, an it eats the files.
(This particular one would be rejected cause having a non 5 sec multiple 
duration, and of course the volume change is very strange, resolution change 
probably not needed, I took the first stupid clip I found…)


Bouke

videotoolshed.com
Van Oldenbarneveltstraat 33
6512 AS Nijmegen, the Netherlands
+31 6 21817248
If you want to send me large files, please use:
https://videotoolshed.wetransfer.com/


> Erik
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] FFmpeg default processing(invisible processing)

2023-12-19 Thread Bouke / edit 'B



> On 19 Dec 2023, at 17:16, Erik Dobberkau  wrote:
> 
>> 
>> Trust me, this command (besides audio parsing, depending on sources) has
>> made thousands of broadcast compliant files over here, where XDCAM is also
>> mandatory.
>> 
> 
> Does that mean the issue mentioned here:
> https://www.mail-archive.com/ffmpeg-user@ffmpeg.org/msg26313.html 
> <https://www.mail-archive.com/ffmpeg-user@ffmpeg.org/msg26313.html> (and
> its follow-up messages) is not an issue anymore?

No clue, only thing I know is that the stupid broadcasters over here accept 
files created as I showed
Bouke
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] FFmpeg default processing(invisible processing)

2023-12-19 Thread Bouke / edit 'B
Top posting, as my mail client does now allow for decent parsing, and I’m fed 
up with that.

My command to create ‘’proper” XDcam HD 50Mb, as required by the broadcasters 
here.
Read between the filenames, it does work.

/Applications/ffmpeg -hide_banner -threads 0 -i /Users/bouke/yadda.mov -f lavfi 
-i anullsrc=channel_layout=mono:sample_rate=48000 -map 0:0 -map 0:1 -map 0:1 
-map 1:0 -map 1:0 -map 1:0 -map 1:0 -map 1:0 -map 1:0 -c:a pcm_s24le -ar 48000 
-map_channel 0.1.0:0.1 -c:a pcm_s24le -ar 48000 -map_channel 0.1.1:0.2 -c:a 
pcm_s24le -map_channel 1.0.0:0.3 -c:a pcm_s24le -map_channel 1.0.0:0.4 -c:a 
pcm_s24le -map_channel 1.0.0:0.5 -c:a pcm_s24le -map_channel 1.0.0:0.6 -c:a 
pcm_s24le -map_channel 1.0.0:0.7 -c:a pcm_s24le -map_channel 1.0.0:0.8 -af 
volume=-11.4dB -vf setfield=tff,scale=1920x1080:flags=lanczos -r 25 -flags 
+ilme+ildct -top 1 -c:v mpeg2video -b:v 5k -maxrate 5k -bufsize 3835k 
-minrate 5k -pix_fmt yuv422p -profile:v 0 -level:v 2 -t 26 -timecode 
00:00:00:00 /Volumes/Data/magweg/Mars_Mars-Delight_26_1_19-12-2023_HD.mxf -y 

 Trust me, this command (besides audio parsing, depending on sources) has made 
thousands of broadcast compliant files over here, where XDCAM is also mandatory.

Bouke 

> On 19 Dec 2023, at 06:56, 大石脩斗  wrote:
> 
> I'm trying to use ffmpeg to generate an MXF file that can be played on an
> XDCAM XDS-PD2000.
> Please tell me what default processing is performed in ffmpeg when no
> options are entered.
> 
> [background]
> Sony's check tool outputs an error saying "MXF metadata contains
> non-standard values".
> The data output by the editing machine is OK with the check tool,
> The data generated with ffmpeg will be rejected by the check tool.
> The metadata looks the same for both.
> Please let me know if you are processing anything other than the meta
> information that is being output
> 
> 【Data output by editing machine」
> aftertext.txt
> 
> 【Data output by ffmpeg】
> testffmpeg.txt
> commondlie
> ffmpeg.exe -i input\base.MXF -c:v mpeg2video -r 29.97 -pix_fmt yuv422p
> -aspect 16:9 -flags +ildct+ilme -b:v 5000 -minrate 5000 -maxrate
> 5000 -bufsize 17825792 -bf 2 -metadata creation_time=now -video_format
> component -g 15 -timecode 00:59:45:00 -ac 1 -map 0:0 -map 0:1 -map 0:1 -map
> 0:1 -map 0:1 -map 0:1 -map 0:1 -map 0:1 -map 0:1 -c:a pcm_s24le -ar 48000
> -f mxf -y output/output_test.mxf
> 
> Shuto
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] ffmpeg and use of the ildct flag in progressive encoding

2023-12-17 Thread Bouke / Videotoolshed

> On 17 Dec 2023, at 20:44, Nik Armstrong  wrote:
> 
> On 2023-12-16 15:01, Erik Dobberkau wrote:
>> The ildct flag appears only to be making the output file "think" it is
>>> interlaced, when it is, in fact, progressive. It does not seem to be doing
>>> anything to change the footage (quality-wise and it's still progressive).
>>> Since someone other than myself set the flag on this command, I am trying
>>> to figure out what effect, if any, taking it off will do to the output.
>> IIRC, it only has an effect when you are creating an interlaced output
>> using -top 1, (and from here on I‘m guessing) it might instruct the encoder
>> or an automatically inserted filter to apply the DCT in a different fashion
>> compared to a progressive input.
>> But again, that’s a guess which may (also) be outdated, since I last did
>> these kinds of transcodes quite a while ago.
>> Good luck.
>> ___
>> ffmpeg-user mailing list
>> ffmpeg-user@ffmpeg.org
>> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>> To unsubscribe, visit link above, or email
>> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
> Thanks Erik. Much appreciated.

Mind you:
Sometimes it’s wanted / needed to have all files ’the same’.
If that is interlaced, it’s interlaced. Codec should say ‘interlaced’, no 
matter the actual content.

For Avid media, that might (depending on the version of MC) be important for a 
‘fast import’, or omitting adapters you don’t want / need.

In broadcast, over here interlaced is mandatory, even if the content is 
progressive.

So no, it’s NOT complicated, and no, it’s NOT outdated.

Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] why reducing the resolution a percentage doesn't reduce the video the same proportion?

2023-03-14 Thread Bouke / edit 'B

> On 14 Mar 2023, at 14:03, Natalia Molinero Mingorance 
>  wrote:
> 
> what do you mean by " Why is the output size important if you use -preset
> ultrafast?  “

That will mean quick and dirty encoding, at the cost of a higher bitrate.
-preset slow will make the file significant smaller, at the cost of more 
processing time / cpu use.
(And thus energy use, but if you stream too large files a gazillion times, you 
might want to invest in high quality encoding instead of quick ’n dirty.)
It’s a ‘would you like to be bitten by the cat or by the dog’ situation.

Bouke



___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] why reducing the resolution a percentage doesn't reduce the video the same proportion?

2023-03-14 Thread Bouke / edit 'B
On 14 Mar 2023, at 13:07, Phil Rhodes via ffmpeg-user  
wrote:
> 
> Also, it depends what you mean by 50% of the resolution. If your original 
> video is 100x100 pixels and you reduce it to 50x50, then you have half the 
> resolution, but you only have one quarter the pixels.

But, the image will still have a tree, a house and a dog.
>From what I have understood, the resolution in terms of pixels does not 
>compute to output file size (Unless you work uncompressed of course.)

> P
>On Tuesday, 14 March 2023 at 09:37:36 GMT, Natalia Molinero Mingorance 
> mailto:eng.nataliamolin...@gmail.com>> wrote: 
>  
> 
> I'm using this command:
> 
> -y -r -i $inVideoUri -movflags faststart -c:v libx265 -s
> $videoResolution -c:a copy -preset ultrafast  $outPutUri

/// 
> some headers or metadata added during the process but I would like to know
> how to estimate the final video size.

Why is the output size important if you use -preset ultrafast?

Bouke


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


[FFmpeg-user] Directshow capture and irregular timing of output to StdErr

2023-03-11 Thread Bouke / Videotoolshed
Trying to build a metering tool that displays (almost) RT values.
On Mac, all works fine with AVfoundation, but on Win with Directshow I have an 
issue:

C:\Users\Bouke>ffmpeg.exe -nostats -f dshow -ar 48000 -i audio="Line (Steinberg 
CI2)" -filter_complex "ebur128=peak=true" -f null -

Now, this works fine, BUT, the output to stderr is at very irregular intervals.
Output is as expected lines like:
[Parsed_ebur128_0 @ 01915fe77a40] t: 0.199979   TARGET:-23 LUFSM:-120.7 
S:-120.7 I: -70.0 LUFS   LRA:   0.0 LU  FTPK: -55.5 -71.0 dBFS  TPK: 
-55.2 -69.8 dBFS
[Parsed_ebur128_0 @ 01915fe77a40] t: 0.299979   TARGET:-23 LUFSM:-120.7 
S:-120.7 I: -70.0 LUFS   LRA:   0.0 LU  FTPK: -56.2 -72.7 dBFS  TPK: 
-55.2 -69.8 dBFS

Now, sometimes one line is outputted (as expected) but most of the times it’s 2 
up to 4 lines at the same time.
That does not make for a pretty visual show if I parse it ‘as fast as possible’

I could buffer the output and do my display stuff for each line with my own 
interval / if buffer line length >= 4 or alike, but that would introduce half a 
second delay, and that does not compute well in my brain when I have to ride 
the faders…

Is there anything I can do to have FFmpeg spit out each line ‘as soon as it is 
available’?
(I’m starting FFmpeg from Python, listening to StdOut / StdErr.)

Below the full command, what you cannot see is the irregularity in when the 
lines arrive….

Thx,

Bouke


C:\Users\Bouke>ffmpeg.exe -nostats -f dshow -ar 48000 -i audio="Line (Steinberg 
CI2)" -filter_complex "ebur128=peak=true" -f null -

ffmpeg version 6.0-full_build-www.gyan.dev Copyright (c) 2000-2023 the FFmpeg 
developers
  built with gcc 12.2.0 (Rev10, Built by MSYS2 project)
  configuration: --enable-gpl --enable-version3 --enable-static 
--disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv 
--enable-gnutls --enable-libxml2 --enable-gmp --enable-bzlib --enable-lzma 
--enable-libsnappy --enable-zlib --enable-librist --enable-libsrt 
--enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray 
--enable-libcaca --enable-sdl2 --enable-libaribb24 --enable-libdav1d 
--enable-libdavs2 --enable-libuavs3d --enable-libzvbi --enable-librav1e 
--enable-libsvtav1 --enable-libwebp --enable-libx264 --enable-libx265 
--enable-libxavs2 --enable-libxvid --enable-libaom --enable-libjxl 
--enable-libopenjpeg --enable-libvpx --enable-mediafoundation --enable-libass 
--enable-frei0r --enable-libfreetype --enable-libfribidi --enable-liblensfun 
--enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf 
--enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec 
--enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libvpl 
--enable-libshaderc --enable-vulkan --enable-libplacebo --enable-opencl 
--enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt 
--enable-libopencore-amrwb --enable-libmp3lame --enable-libshine 
--enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libilbc 
--enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex 
--enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite 
--enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint
  libavutil  58.  2.100 / 58.  2.100
  libavcodec 60.  3.100 / 60.  3.100
  libavformat60.  3.100 / 60.  3.100
  libavdevice60.  1.100 / 60.  1.100
  libavfilter 9.  3.100 /  9.  3.100
  libswscale  7.  1.100 /  7.  1.100
  libswresample   4. 10.100 /  4. 10.100
  libpostproc57.  1.100 / 57.  1.100
Guessed Channel Layout for Input Stream #0.0 : stereo
Input #0, dshow, from 'audio=Line (Steinberg CI2)':
  Duration: N/A, start: 2052080.982000, bitrate: 1536 kb/s
  Stream #0:0: Audio: pcm_s16le, 48000 Hz, 2 channels, s16, 1536 kb/s
[Parsed_ebur128_0 @ 0191617889c0] Summary:

  Integrated loudness:
I: -70.0 LUFS
Threshold:   0.0 LUFS

  Loudness range:
LRA: 0.0 LU
Threshold:   0.0 LUFS
LRA low: 0.0 LUFS
LRA high:0.0 LUFS

  True peak:
Peak:   -inf dBFS
Stream mapping:
  Stream #0:0 (pcm_s16le) -> ebur128:default
  ebur128:out0 -> Stream #0:0 (pcm_s16le)
Press [q] to stop, [?] for help
[Parsed_ebur128_0 @ 01915fe77a40] t: 0.0999792  TARGET:-23 LUFSM:-120.7 
S:-120.7 I: -70.0 LUFS   LRA:   0.0 LU  FTPK: -55.2 -69.8 dBFS  TPK: 
-55.2 -69.8 dBFS
Output #0, null, to 'pipe:':
  Metadata:
encoder : Lavf60.3.100
  Stream #0:0: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s
Metadata:
  encoder : Lavc60.3.100 pcm_s16le
[Parsed_ebur128_0 @ 01915fe77a40] t: 0.199979   TARGET:-23 LUFSM:-120.7 
S:-120.7 I: -70.0 LUFS   LRA:   0.0 LU  FTPK: -55.5 -71.0 dBFS  TPK: 
-55.2 -69.8 dBFS
[Parsed_ebur128_0 @ 01915fe77a40] t: 0.299979   TARGET:-23 LUFSM:-120.7 
S:-120.7 I: -70.0 LUFS   LRA:   0.0 LU  FTPK: -56

Re: [FFmpeg-user] ebuR128 display of live source

2023-03-03 Thread Bouke / Videotoolshed
> 
> On 1 Mar 2023, at 11:53, Bouke / Videotoolshed  
> wrote:
> 
> Hi,
> Trying to get a visualisation of my levels during record / stream.
> This works fine for file based material:
> 
> ffplay -f lavfi -i 
> "amovie=/Users/bouke/Downloads/test.wav,ebur128=video=1:meter=18:target=-16 
> [out0][out1]"
> 
> But I would like to have a live source (I’m on Mac, AVfoundation I guess.)


Tried the following:

ffplay -f lavfi -i 
"amovie='\:2':f=avfoundation,ebur128=video=1:meter=18:target=-16 [out0][out1]”

Closer, but still no cigar:
It does not throw an error, but nothing is shown, as if input is not fed to the 
ebur128 filter

 
ffplay version git-2021-03-31-b3e9a84 Copyright (c) 2003-2021 the FFmpeg 
developers
  built with Apple clang version 12.0.0 (clang-1200.0.32.29)
  configuration: --enable-videotoolbox --enable-nonfree --enable-gpl 
--enable-lv2 --enable-openssl --enable-libsvtav1 --enable-libx264 
--enable-libx265 --enable-libvpx --enable-libxvid --enable-libvidstab 
--enable-libaom --enable-libopencore_amrnb --enable-libopencore_amrwb 
--enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libtheora 
--enable-libfdk-aac --enable-libwebp --enable-libsrt --disable-debug 
--disable-doc --disable-shared --enable-pthreads --enable-static --enable-small 
--enable-version3 --enable-libfreetype --enable-libfontconfig --enable-decklink 
--extra-cflags='-I/Users/bouke/ffmpeg-build-script/workspace/include 
-I/Users/bouke/ffmpeg-build-script/include' --extra-ldexeflags= 
--extra-ldflags='-L/Users/bouke/ffmpeg-build-script/workspace/lib 
-L/Users/bouke/ffmpeg-build-script/include' --extra-libs='-ldl -lpthread -lm 
-lz' --pkgconfigdir=/Users/bouke/ffmpeg-build-script/workspace/lib/pkgconfig 
--pkg-config-flags=--static --prefix=/Users/bouke/ffmpeg-build-script/workspace
  libavutil  56. 63.101 / 56. 63.101
  libavcodec 58.117.101 / 58.117.101
  libavformat58. 65.101 / 58. 65.101
  libavdevice58. 11.103 / 58. 11.103
  libavfilter 7. 96.100 /  7. 96.100
  libswscale  5.  8.100 /  5.  8.100
  libswresample   3.  8.100 /  3.  8.100
  libpostproc55.  8.100 / 55.  8.100
nan:  0.000 fd=   0 aq=0KB vq=0KB sq=0B f=0/0   
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


[FFmpeg-user] ebuR128 display of live source

2023-03-01 Thread Bouke / Videotoolshed
Hi,
Trying to get a visualisation of my levels during record / stream.
This works fine for file based material:

ffplay -f lavfi -i 
"amovie=/Users/bouke/Downloads/test.wav,ebur128=video=1:meter=18:target=-16 
[out0][out1]"

But I would like to have a live source (I’m on Mac, AVfoundation I guess.)

How to do that?


Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Multiline subtitles without thin dark line

2023-02-15 Thread Bouke / Videotoolshed
Hi Steinar,
>> 
> 
> I know it's due to overlapping boxes. I cannot find anything in the ASS
> specs. or the subtitles filter to alter the line spacing. I would be very
> happy if your confidence could point me to the right setting ;-)

I would if I could, but sorry, that’s beyond my capability. 
For reasons like this, I render my own subtitles as PNG (with metadata), google 
’subbits subtitler’, that’s my work. (And yes, it allows for a box :-)

Then I create a catlist, and overlay, if a burn-in is needed.
Yes, that was quite some work, but I’m a control freak.

> Anyway, overlapping boxes is (to my knowledge) handled by the filter so in
> my opinion it should be addressed there. Cause I don't believe anyone
> needing this style wants the result created by these overlapping
> transparent boxes. Like this dude:
> https://stackoverflow.com/questions/72093116/ffmpeg-subtitles-background-issue-when-multiple-lines-using-srt-format

I hope someone else can help, I can’t…

> Of course suggesting another style is not a solution.

I know, I just gave my opinion on how things “should” look. I come from a 
country where EVERYTHING is subtitled, and I’ve worked (as a pro in movies / 
tv) with subs for over 20 years.

Bouke



___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Multiline subtitles without thin dark line

2023-02-15 Thread Bouke / Videotoolshed

> On 15 Feb 2023, at 13:21, Steinar Apalnes  wrote:
> 
> Hi,
> 
> I want to create subtitles with multiple text lines using BorderStyle=3 in
> order to have the background color adapt to the length of each line. The
> problem is that I get a thin dark line between every text line.

You do not have a stupid black line, you have overlapping boxes so the alpha 
will double.
Increase line spacing and it ’should’ be fine. (I did not try, but I’m pretty 
confident.)
And for my taste, just outline is enough, boxes are ugly and came from stupid 
CC / TeleText.

Bouke


> Is there a
> way to avoid this so that all background areas appear uniform and
> transparent?
> Using BorderStyle=4 is not an option, nor is using a solid black background.
> 
> ffmpeg -f lavfi -i mandelbrot=size=1280x720 -filter_complex
> "subtitles=sub.srt:force_style='Alignment=0,OutlineColour=,BorderStyle=3'"
> -c:v rawvideo -f nut - | ffplay -
> 
> Thanks
> -steinar
> 
> [image: sub.jpg]
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Any way to estimate moov_size in mov/mp4?

2023-02-10 Thread Bouke / Videotoolshed

> On 10 Feb 2023, at 11:40, Stefan Oltmanns  wrote:
> 
> Hello,
> 
> ffmpeg allows to set a reserved space for the moov at the beginning of
> the file using the "-moov_size" option.
> This will waste some space, but prevent the (in some cases very
> time-consuming) second pass of "-movflags faststart" if you want to have
> the moov atom at the beginning of the file.
> 
> If the reserved space is too small the moov atom gets written at the end
> from my testing (the documentation seems to be wrong here, it states
> muxing will fail, or why could the produced mov file still be played?).
> 
> Is there any way to properly estimate the moov size? In my use case it
> should be rather simple: PCM audio, DNXHD codec (all-I frames, almost
> CBR), known number of frames.
> As the produced files are very big anyway I don't mind wasting a few MB
> by overestimating.

I don’t get it.
Faststart is for internet / network playing only, when the entire file is not 
yet available.
If movflags faststart is needed, it should be darn fast as your files ’should’ 
be fairly small, as they are intended for (relative) low bandwith.
There is NO penalty for having the MOOV atom at the end if a file is local, as 
parsing all atoms will not take longer than a few secs if the file is local.
Having said that:
Checking the size of the moov atom is relative simple, use ‘any’ atom parser, 
or render the same file for 1 frame with a scale as small as you can get, with 
highly compressed sound and use the entire file size for the MOOV atom size 
(plus a bit).

Hth,

Bouke



___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Noticeable transitions between audio chunks

2023-02-07 Thread Bouke / edit 'B
Oh wait...
> 
>> then I get raw PCM of each chunk and replace some parts of PCM with sine
>> wave data (adding beeps) and then I transform that PCM chunks to mp3 chunks
>> and write those to stream. The final process of concating audio parts is *NOT
>> *performed by ffmpeg, I just write data chunks to the destination stream.

Are you trying to concat mp3 chunks? That seems like a bad idea,
Concat the raw PCM, then convert that to mp3

bouke


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Noticeable transitions between audio chunks

2023-02-07 Thread Bouke / edit 'B

> On 7 Feb 2023, at 11:05, Alexander Bieliaev via ffmpeg-user 
>  wrote:
> 
> I am processing audio chunks programmatically by using the ffmpeg library
> for C#. First I divide the input audio of .wav format into chunks of 1
> minute each (I can't process the whole audio for specific reasons), then
> prepend it's header to each chunk so it can be recognized and processed,

I don’t get it. If you speak C, and you have uncompressed Wave input, is as 
simple as opening the file, find the DATA riff and copy out X bytes (depending 
on the bit depth / sample rate)


> then I get raw PCM of each chunk and replace some parts of PCM with sine
> wave data (adding beeps) and then I transform that PCM chunks to mp3 chunks
> and write those to stream. The final process of concating audio parts is *NOT
> *performed by ffmpeg, I just write data chunks to the destination stream. I
> am facing the problem that there are noticeable transitions between 1
> minute chunks in result audio(clicks/silence/change of volume/shifting).
> How can I smooth out the start/end of each chunk so when I'm putting them
> together there are no noticeable transitions?

From experience I know that the size of -f segment for Wave does NOT result in 
a sample accurate amount of data, not sure if that is what you are facing. 
(Should not matter if there is a pure concat of the data.)
It ’should’ be seamless.

So, if I can  do this kind of stuff in pure python, why find the cause and not 
do it yourself in C?

Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


[FFmpeg-user] I love the smell of assholes in the morning

2023-02-04 Thread Bouke / edit 'B
Bonus points if you get the reference.

I also like the smell in the afternoon, and evening, and night.
(Hunting targets.)

IOW:

SHUT UP
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Create a black box over top of the video for a set duration at a set time.

2022-12-31 Thread Bouke / edit 'B
On 31 Dec 2022, at 10:41, Michael Koch  wrote:
> 
> Am 31.12.2022 um 10:31 schrieb Bouke / Videotoolshed:
>> On 31 Dec 2022, at 04:53, Gyan Doshi  wrote:
>>> On 2022-12-31 08:15 am, David Niklas wrote:
>>>> Sorry for taking so long to reply.
>>>> It is not working. Terminal output below.
>>>> 
>>>> % ffmpeg -i Ducksinarow.mp4 -filter_complex 
>>>> "[0:0]drawbox=color=black:t=fill=enable='between(t,1.0,2.0)'" -c:a copy 
>>>> -c:v libvpx ducks.mp4
>>> There should be a colon after fill, not =
>>> 
>>> drawbox=color=black:t=fill:enable='between(t,1.0,2.0)'
>> And for your next question that might come up (since you want to do multiple 
>> filters, I do too and just got bitten):
>> There is a limitation on Windows that won’t accept long arguments.
> 
> Do you have an example? I have used command lines _much_ longer than the 
> above example, and never found a limitation.
> 
> Michael

The limitation is 8091 chars, and afaik only exists on Windows. (Mac is fine, I 
don’t know about Linux, but I suspect it will be no issue there too.)
My latest issue had a line of more than 64000 chars, example from 
filter_complex (that caused the huge length) below.

Bouke

map 0:0 -filter_complex 
[0:0]drawtext=enable='between(t,0.0302083334,75.180166)':timecode='00\:49\:29\:11':fontfile='/Volumes/Data/PycharmProjects/LTC_convert/src/main/resources/base/courbd.ttf':r=25:x=(w-text_w)/2:y=h-th:
 
y=h-(2*lh):fontsize=54.0:fontcolor=white:borderw=2.7:bordercolor=#101010@0.8,drawtext=enable='between(t,75.190167,75.780166)':text='--
 NO LTC 
!':fontfile='/Volumes/Data/PycharmProjects/LTC_convert/src/main/resources/base/courbd.ttf':x=(w-text_w)/2:y=h-th:
 
y=h-(2*lh):fontsize=54.0:fontcolor=white:borderw=2.7:bordercolor=#101010@0.8,drawtext=enable='between(t,75.790166,299.980125)':timecode='00\:47\:41\:21':fontfile='/Volumes/Data/PycharmProjects/LTC_convert/src/main/resources/base/courbd.ttf':r=25:x=(w-text_w)/2:y=h-th:
 
y=h-(2*lh):fontsize=54.0:fontcolor=white:borderw=2.7:bordercolor=#101010@0.8,drawtext=enable='between(t,300.030041667,822.939770833)':timecode='00\:47\:41\:21':fontfile='/Volumes/Data/PycharmProjects/LTC_convert/src/main/resources/base/courbd.ttf':r=25:x=(w-text_w)/2:y=h-th:
 
y=h-(2*lh):fontsize=54.0:fontcolor=white:borderw=2.7:bordercolor=#101010@0.8,drawtext=enable='between(t,822.949770833,1138.661916667)':text='--
 NO LTC 
!':fontfile='/Volumes/Data/PycharmProjects/LTC_convert/src/main/resources/base/courbd.ttf':x=(w-text_w)/2:y=h-th:
 y=h-(2*lh):fontsize=54.0:fontcolor=white:borderw=2.7:bordercolor=#101010@0.8, 
and so on….
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Create a black box over top of the video for a set duration at a set time.

2022-12-31 Thread Bouke / Videotoolshed
On 31 Dec 2022, at 04:53, Gyan Doshi  wrote:
> 
> On 2022-12-31 08:15 am, David Niklas wrote:
>> Sorry for taking so long to reply.
>> It is not working. Terminal output below.
>> 
>> % ffmpeg -i Ducksinarow.mp4 -filter_complex 
>> "[0:0]drawbox=color=black:t=fill=enable='between(t,1.0,2.0)'" -c:a copy -c:v 
>> libvpx ducks.mp4
> 
> There should be a colon after fill, not =
> 
> drawbox=color=black:t=fill:enable='between(t,1.0,2.0)'

And for your next question that might come up (since you want to do multiple 
filters, I do too and just got bitten):
There is a limitation on Windows that won’t accept long arguments.
In that case, save the filter_complex string to a file, then, instead of 
filter_complex you can use filter_complex_script with the filename as argument.

Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Create a black box over top of the video for a set duration at a set time.

2022-12-24 Thread Bouke / Videotoolshed
On 23 Dec 2022, at 22:55, David Niklas  wrote:
> 
> Hello,
> What I'd like to achieve is sort of like censoring, but with a black box.
> 
> I can find plenty of examples of how to add a black box to a video, but
> the problem is it is always either the whole video, or only at the
> beginning/end, that the examples add black boxes


Try filter_complex "[0:0]youfilter=enable='between(t,1.0,2.0)’”

Hth
Bouke

> to. I cannot seem to
> figure out how to set the start and end timestamp.
> 
> Thanks,
> David
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Changing scan type (progressive<->interlaced) without reencoding.

2022-12-05 Thread Bouke (Edit 'B)
It’s no problem at all.
Btw, it’s very common to store progressive as interlaced, as broadcast still 
requires interlaced material, no matter how it is shot.

From memory, just do a -c copy and you’ll end up with the source in a 
progressive container.

Bouke


> On 05 Dec 2022, at 11:56, Steinar Apalnes  wrote:
> 
> Hi,
> 
> As the title says, is this at all possible? My concern is mostly with mpeg2
> and h264 that have content of one type but encoded/marked as another. Most
> notably content that has progressive video but stored interlaced. So I'm
> probably talking about a bit stream filter here because just setting the
> "field_order", "top" etc. flags when rewrapping does nothing.But I have not
> found anything in the official docs that suggest this is currently possible
> so it would be nice if some of you developers could shed some light on this.
> 
> Thanks,
> Steinar Apalnes
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Ubuntu 22.04 audio capture issue

2022-11-30 Thread Bouke / Videotoolshed


> On 30 Nov 2022, at 17:17, Carl Zwanzig  wrote:
> 
> Doubtful, IME.

I enjoyed it, even showed some to my GF. 

Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] How to reduce interlace artifacts while trancoding to mp4

2022-11-12 Thread Bouke / Videotoolshed

> On 12 Nov 2022, at 01:46, Ulf Zibis  wrote:
> 
> Hi,
> 
> I have transcoded a avi video to mp4 for compressing by factor 8. Now I see 
> interlace artifacts. E.g. the eagle in the back window of the bus or the 
> fence in the background.
> Additionally I would like to reduce the noise for even better compression. 
> Any hint for a good filter?
> 
> Refer:
> http://jugkoeln.de/Videos/2012-01-03_21.46.40_6.29GB_15.avi
> http://jugkoeln.de/Videos/2012-01-03_21.46.40_6.29GB_15.mp4

Hi Ulf,
This is normal DV interlaced video. Open the .avi with VLC and turn OFF 
de-interlace, you’ll see how gorgeous the motion was on an old fashioned 
interlace aware screen.

So, you need to de-interlace the filter.
While you’re at it, you should crop a little, as SD is an over scanned format. 
And, you have non-square pixels that you have to accommodate for, so set aspect 
to 4:3 (in this case), or scale to a 4:3 ratio.

Hth,

Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] ffserver

2022-11-10 Thread Bouke / Videotoolshed

> On 10 Nov 2022, at 14:22, david stephen  wrote:
> 
> ffserver is not someone that speciality in audio/video. u just need to

Well David,

I have no clue what this is about, but with you write ‘u’ instead of ‘you’, you 
have lost all my respect.
Not signing your post with your name tops it off.

Bouke


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Wrong TC read with doubled Framenumber read out when input is 50p

2022-11-06 Thread Bouke (Edit 'B)

> On 06 Nov 2022, at 21:35, Björn Büchel via ffmpeg-user 
>  wrote:
> 
> Hi Bouke, 
> Thanks for the reply. You are right, that makes no sense. But this is what I 
> found out. 
> I checked the TC with Avid Media Composer as well as with Resolve and 
> Premiere. 
> In all three Apps the TC is identical. 
> Björn 

Hi Björn,
Did you try QTchange as well? (If not, please do, the free demo will do just 
fine.)
https://www.videotoolshed.com/handcrafted-timecode-tools/qtchange/

It’s partly based on FFmpeg, so it ‘should’ give the same results. 
There are a couple of thousend end users, including some major broadcasters / 
studios, and I have not have any complaint like you describe…

So, this is strange.

Bouke



> 
> —-
> 
> Björn Büchel
> Am Hüpplingsgraben 5
> 42799 Leichlingen
> 0152 / 051 051 00
> bjoernbuec...@me.com
> 
> 
>> Am 06.11.2022 um 11:10 schrieb Bouke / Videotoolshed 
>> :
>> 
>> 
>>> 
>>> On 6 Nov 2022, at 08:42, Björn Büchel via ffmpeg-user 
>>>  wrote:
>>> 
>>> Hi, when I pass a 50p h264 or h265 Video to "ffmpeg -i" without any further 
>>> code the console shows the "TC In" of the Video. But the Frame coloumn of 
>>> the File is doubled so the output has the wrong TC. 
>>> e.g. 
>>> orginial File TC: 10:00:00:05
>>> ffmpeg -i shows: 10:00:00:10
>>> 
>>> or e.g. 
>>> orginial File TC: 10:00:00:45
>>> ffmpeg -i shows: 10:00:01:40
>>> 
>>> Is this a known issue or does anyone have a workaround?
>> 
>> This I’ve never seen. I know that the TC is written as frames in Mov, Mp4 
>> and MXF, so you need the frame rate to convert to HH MM SS FF
>> This sometimes goes wrong, so different apps calculate different TC values, 
>> but that is always the entire number doubled / halved.
>> In your case only the frames are doubled, this makes no sense, a frames to 
>> tc routine will not use a different FPS for hours / minutes / seconds and 
>> frames.
>> 
>> When you say ‘original File TC’, what makes you so sure that is indeed 
>> correct? What software tells you that? Did you try other apps? (Resolve / 
>> Premiere / Avid / Quicktime player / whatever you have.)
>> 
>> Bouke
>> 
>> 
>>> I would appreciate your help. 
>>> Björn
>>> ___
>>> ffmpeg-user mailing list
>>> ffmpeg-user@ffmpeg.org
>>> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>>> 
>>> To unsubscribe, visit link above, or email
>>> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>> 
>> ___
>> ffmpeg-user mailing list
>> ffmpeg-user@ffmpeg.org
>> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>> 
>> To unsubscribe, visit link above, or email
>> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Wrong TC read with doubled Framenumber read out when input is 50p

2022-11-06 Thread Bouke / Videotoolshed

> 
> On 6 Nov 2022, at 08:42, Björn Büchel via ffmpeg-user 
>  wrote:
> 
> Hi, when I pass a 50p h264 or h265 Video to "ffmpeg -i" without any further 
> code the console shows the "TC In" of the Video. But the Frame coloumn of the 
> File is doubled so the output has the wrong TC. 
> e.g. 
> orginial File TC: 10:00:00:05 
> ffmpeg -i shows: 10:00:00:10
> 
> or e.g. 
> orginial File TC: 10:00:00:45 
> ffmpeg -i shows: 10:00:01:40
> 
> Is this a known issue or does anyone have a workaround?

This I’ve never seen. I know that the TC is written as frames in Mov, Mp4 and 
MXF, so you need the frame rate to convert to HH MM SS FF
This sometimes goes wrong, so different apps calculate different TC values, but 
that is always the entire number doubled / halved.
In your case only the frames are doubled, this makes no sense, a frames to tc 
routine will not use a different FPS for hours / minutes / seconds and frames.

When you say ‘original File TC’, what makes you so sure that is indeed correct? 
What software tells you that? Did you try other apps? (Resolve / Premiere / 
Avid / Quicktime player / whatever you have.)

Bouke


> I would appreciate your help. 
> Björn
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] 16:9 to 2.35:1 and true HD 7.1 to DTS

2022-11-04 Thread Bouke / Videotoolshed

> On 3 Nov 2022, at 22:55, Carl Eugen Hoyos  wrote:
> 
> Am Do., 3. Nov. 2022 um 20:18 Uhr schrieb Bartosz Trzebuchowski
> :
> 
>> 1. How can I convert 16:9 movies to 2.35:1? My projector can’t
>> scale down and 16:9 movies run outside my 2.35:1 canvas at
>> the top and the bottom. I need to black out top and bottom so
>> only 2.35:1 is visible.
> 
> Use the crop filter:
> https://ffmpeg.org/ffmpeg-filters.html#crop
> 
> Carl Eugen
> ___

Definitely not crop, that will remove part of the image.
Instead, pillarbox it, using the pad filter, if needed in combo with scale.

https://ffmpeg.org/ffmpeg-filters.html#pad

Bouke
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] encode to RAW video

2022-10-24 Thread Bouke / edit 'B


> On 24 Oct 2022, at 14:29, Naveen.B  wrote:
> 
>> 
>> 
>> On 24 Oct 2022, at 12:52, Naveen.B  wrote:
>>> 
>>> Hello Team,
>>> 
>>> I have managed to convert raw Images files to .mp4 video,
>>> I need to encode to a RAW video instead, could you please let me know the
>>> command for this?
>>> 
>>> RAW Image file is,
>>> resolution - 1600x1300
>>> fps-30
>>> bit depth-16bit
>>> 
>> 
>> Do not specify a video codec, or set -c:v rawhide, set your frame rate /
>> resolution / bit depth params and use .raw as extension.
>> 
>> I tried as you suggested, I get the below error,
> 
> C:\Naveen\projects\DMS\software\ffmpeg_full\ffmpeg\bin>ffmpeg -pixel_format
> gray10le -s 1600x1300 -r 30 -i CapturedImage-%03d.raw -c:v rawhide -crf 1
> raw_video.raw

Rawhide?
WTF?
Rawvideo does not carry a pix format afaik.


> ffmpeg version 2022-06-20-git-56419428a8-full_build-www.gyan.dev Copyright
> (c) 2000-2022 the FFmpeg developers
>  built with gcc 11.3.0 (Rev1, Built by MSYS2 project)
>  configuration: --enable-gpl --enable-version3 --enable-static
> --disable-w32threads --disable-autodetect --enable-fontconfig
> --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-bzlib
> --enable-lzma --enable-libsnappy --enable-zlib --enable-librist
> --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth
> --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libdav1d
> --enable-libdavs2 --enable-libuavs3d --enable-libzvbi --enable-librav1e
> --enable-libsvtav1 --enable-libwebp --enable-libx264 --enable-libx265
> --enable-libxavs2 --enable-libxvid --enable-libaom --enable-libjxl
> --enable-libopenjpeg --enable-libvpx --enable-mediafoundation
> --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi
> --enable-liblensfun --enable-libvidstab --enable-libvmaf --enable-libzimg
> --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec
> --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2
> --enable-libmfx --enable-libshaderc --enable-vulkan --enable-libplacebo
> --enable-opencl --enable-libcdio --enable-libgme --enable-libmodplug
> --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame
> --enable-libshine --enable-libtheora --enable-libtwolame
> --enable-libvo-amrwbenc --enable-libilbc --enable-libgsm
> --enable-libopencore-amrnb --enable-libopus --enable-libspeex
> --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite
> --enable-libmysofa --enable-librubberband --enable-libsoxr
> --enable-chromaprint
>  libavutil  57. 27.100 / 57. 27.100
>  libavcodec 59. 33.100 / 59. 33.100
>  libavformat59. 25.100 / 59. 25.100
>  libavdevice59.  6.100 / 59.  6.100
>  libavfilter 8. 41.100 /  8. 41.100
>  libswscale  6.  6.100 /  6.  6.100
>  libswresample   4.  6.100 /  4.  6.100
>  libpostproc56.  5.100 / 56.  5.100
> Input #0, image2, from 'CapturedImage-%03d.raw':
>  Duration: 00:00:01.20, start: 0.00, bitrate: N/A
>  Stream #0:0: Video: rawvideo (Y1[0][10] / 0xA003159), gray10le,
> 1600x1300, 25 fps, 25 tbr, 25 tbn
> [NULL @ 023c862e6740] Unable to find a suitable output format for
> 'raw_video.raw'
> raw_video.raw: Invalid argument
> 
> C:\Naveen\projects\DMS\software\ffmpeg_full\ffmpeg\bin>
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] encode to RAW video

2022-10-24 Thread Bouke / Videotoolshed



> On 24 Oct 2022, at 12:52, Naveen.B  wrote:
> 
> Hello Team,
> 
> I have managed to convert raw Images files to .mp4 video,
> I need to encode to a RAW video instead, could you please let me know the
> command for this?
> 
> RAW Image file is,
> resolution - 1600x1300
> fps-30
> bit depth-16bit
> 

Do not specify a video codec, or set -c:v rawhide, set your frame rate / 
resolution / bit depth params and use .raw as extension.

Bouke


> Thanks and Regards,
> Naveen B.
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Raw video conversion

2022-07-08 Thread Bouke / Videotoolshed
WTF,
 I did NOT, I repeat, NOT write the message below.
And my mail has not been hacked, so what is going on?

Bouke

> On 8 Jul 2022, at 12:17, Bouke / Videotoolshed  
> wrote:
> 
> Please provide full command and console output, and do NOT top post here!
>> 
>> I have a raw video file captured from the monochrome camera, I need to
>> convert the raw video file to visualise it in .avi or .mp4.
>> I tried this command, but this did not worked out to me,
>> ffmpeg -f rawvideo -pixel_format yuv420p -video_size 1600x1300 -framerate
>> 30 -i raw_video.raw raw_video.avi
>> 
>> Could anyone help me on how to do conversion from raw file to .avi or -mp4
>> file?
> 
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Raw video conversion

2022-07-08 Thread Bouke / Videotoolshed
Please provide full command and console output, and do NOT top post here!
> 
> I have a raw video file captured from the monochrome camera, I need to
> convert the raw video file to visualise it in .avi or .mp4.
> I tried this command, but this did not worked out to me,
> ffmpeg -f rawvideo -pixel_format yuv420p -video_size 1600x1300 -framerate
> 30 -i raw_video.raw raw_video.avi
> 
> Could anyone help me on how to do conversion from raw file to .avi or -mp4
> file?

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] How come after update, it takes so longer, many more process

2022-07-08 Thread Bouke / Videotoolshed


> On 8 Jul 2022, at 04:23, Budi  wrote:
> 
> $ ffmpeg -i "b.mp4" -to 0:2:20  a.mp4
> 
> 
> used to do it nicely done in few seconds

FFmpeg -i "b.mp4" -to 0:2:20  -c: copy a.mp4
Mind the codec copy.

If you omit that, FFmpeg will transcode, resulting in speed and quality loss.

Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Make white of photo transparant

2022-06-29 Thread Bouke / edit 'B
Beledig me niet, lijk met niet in lijn met je princiepes / de Heer, iig siert 
het niemand.

Bouke / edit 'B

videotoolshed.com
Van Oldenbarneveltstraat 33
6512 AS Nijmegen, the Netherlands
+31 6 21817248
If you want to send me large files, please use:
https://videotoolshed.wetransfer.com/

> On 29 Jun 2022, at 13:45, Cecil Westerhof via ffmpeg-user 
>  wrote:
> 
> Bouke / Videotoolshed  writes:
> 
>> Pff, make it an option.
> 
> You probably would tell a homeless person that is hungry and cold:
> just put on clothes and eat something.
> (Without providing him anything.)
> 
> -- 
> Cecil Westerhof
> Senior Software Engineer
> LinkedIn: http://www.linkedin.com/in/cecilwesterhof
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Make white of photo transparant

2022-06-29 Thread Bouke / Videotoolshed
Pff, make it an option. 
Finding someone who knows this stuff is less work than this shit, including the 
top post flaming.


Boukee use:
https://videotoolshed.wetransfer.com/

> On 29 Jun 2022, at 13:19, Cecil Westerhof via ffmpeg-user 
>  wrote:
> 
> Bouke / Videotoolshed  <mailto:bo...@videotoolshed.com>> writes:
> 
>>> On 29 Jun 2022, at 12:54, Cecil Westerhof via ffmpeg-user 
>>>  wrote:
>>> 
>>> Bouke / Videotoolshed  writes:
>>> 
>>>> No, sorry. But, hire an editor / designer to do this for you,
>>>> results will be better / less pain.
>>>> If you want to have it done for free, be my guest, but don’t ask my
>>>> help, do not expect any half decent results.
>>> 
>>> I am doing it for a school (musical) , so I cannot spend money on it.
>> 
>> What do you want me to say? What is your point?
> 
> You tell me to hire an editor/designer. I explain why that is not an
> option.
> 
> -- 
> Cecil Westerhof
> Senior Software Engineer
> LinkedIn: http://www.linkedin.com/in/cecilwesterhof 
> <http://www.linkedin.com/in/cecilwesterhof>
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org <mailto:ffmpeg-user@ffmpeg.org>
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user 
> <https://ffmpeg.org/mailman/listinfo/ffmpeg-user>
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org <mailto:ffmpeg-user-requ...@ffmpeg.org> with 
> subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Make white of photo transparant

2022-06-29 Thread Bouke / Videotoolshed


> On 29 Jun 2022, at 12:54, Cecil Westerhof via ffmpeg-user 
>  wrote:
> 
> Bouke / Videotoolshed  writes:
> 
>> No, sorry. But, hire an editor / designer to do this for you,
>> results will be better / less pain.
>> If you want to have it done for free, be my guest, but don’t ask my
>> help, do not expect any half decent results.
> 
> I am doing it for a school (musical) , so I cannot spend money on it.

What do you want me to say? What is your point?


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Make white of photo transparant

2022-06-29 Thread Bouke / Videotoolshed

>> doing, and IMHO, FFmpeg is not the tool for this.
> 
> A long time ago I tried to work with GUI programs, but I found them to
> bothersome. 

Any half decent video editor / designer works with a GUI, WYSIWYG has been 
invented for a reason.
Doing this without feedback only works in lab circumstances, and I think less 
than 0.01 % of the FFmpeg users have that situation.

>> (But someone recently mentioned a GUI for filters, that might help you big 
>> time on this one.)
> 
> Do you remember the GUI?


No, sorry. But, hire an editor / designer to do this for you, results will be 
better / less pain.
If you want to have it done for free, be my guest, but don’t ask my help, do 
not expect any half decent results.


Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Make white of photo transparant

2022-06-29 Thread Bouke / Videotoolshed
On 29 Jun 2022, at 01:48, Cecil Westerhof via ffmpeg-user 
 wrote:
> 
> 
> The background of the photo is white. Would it be possible to make
> that transparent? (So where there is white, I do not see white, but
> the video.)

This is called Luma (or Luminance) key.

Yes, it is possible, yes, it will be ugly unless you know what you are doing, 
and IMHO, FFmpeg is not the tool for this.
(But someone recently mentioned a GUI for filters, that might help you big time 
on this one.)

Bouke



___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Get the file size in advance when encoding from one another format

2022-06-14 Thread Bouke (Edit 'B)

> 
> Please help me do this; How do I get the file size in advance if I encode
> any media format to another format so that I can set the Header
> Content-Length in the header. What is the formula for this? I'm new to
> FFMpeg.

Didn’t you already get flamed on this very subject not very long ago?

Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Large Sized output files recieved while encoding the audio

2022-04-20 Thread Bouke / edit 'B

> On 20 Apr 2022, at 19:50, Shubham Tiwari  wrote:
> 
> I think you are not reading the message properly.
 
I think I do.

> If you notice, the size
> of the file i am passing is 2 mb, the return file size is 176 mb. Does 88
> times increase seem reasonable to you?

Yes, as far as it goes for your command line, this is to be expected, and 
totally comprehensive.

> I want the file to be in approximately similar quality and file size should
> go at max 2 to 3 times. In this case upto 6 mb file size is fine.

State what you want, do you want to trim (cut out parts), just to forward it to 
other people?
So, what do you want, what are you after?
> 
> I am doing this because we have a redaction logic to be executed on
> approximately 1 million audio files per day.  And all these calls are
> stored in aws s3. so storing multiple files of size 176 mb doesn't seem to
> be a good idea.

Again, what are you after? If you need ’some’ kind of computer logic / 
analysis, uncompressed Wave / PCM CAN be faster / more efficient than 
compressing it.
In that case, file size does not matter if it’s local, it’s just math on what 
is cheaper / more efficient.

BUT, since you don’t give any clue what / who has to process the output of your 
work, trust me, hire a specialist to drag this out of you.

I’m trying to help you, but for that, you need to provide more input.

Bouke / edit 'B

videotoolshed.com
Van Oldenbarneveltstraat 33
6512 AS Nijmegen, the Netherlands
+31 6 21817248
If you want to send me large files, please use:
https://videotoolshed.wetransfer.com/


> 
> Concerning my lack of knowledge, I read the documentation page multiple
> times but couldn't find something that gives me the right information.  In
> the end I reached out here. Concerning my lack of knowledge, probably some
> help would be better instead of passing remarks.
> 
> On Wed, Apr 20, 2022 at 11:07 PM Bouke / Videotoolshed <
> bo...@videotoolshed.com> wrote:


Bouke / edit 'B

videotoolshed.com
Van Oldenbarneveltstraat 33
6512 AS Nijmegen, the Netherlands
+31 6 21817248
If you want to send me large files, please use:
https://videotoolshed.wetransfer.com/

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Large Sized output files recieved while encoding the audio

2022-04-20 Thread Bouke / edit 'B



> On 20 Apr 2022, at 19:50, Shubham Tiwari  wrote:
> 
> 1 million audio files per day.

Hire a specialist. Now. Immediately. Pay him / her well. Do NOT hesitate. Do 
NOT think, just do it. Right now.
It WILL pay off.
Did I mention you DO NOT HAVE time to waste?


Bouke / edit 'B

videotoolshed.com
Van Oldenbarneveltstraat 33
6512 AS Nijmegen, the Netherlands
+31 6 21817248
If you want to send me large files, please use:
https://videotoolshed.wetransfer.com/ <https://videotoolshed.wetransfer.com/>




___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Large Sized output files recieved while encoding the audio

2022-04-20 Thread Bouke / Videotoolshed

> On 20 Apr 2022, at 19:30, Shubham Tiwari  wrote:
> 
> Please accept my apology for putting a large size msg. I appreciate all the
> help received.
> 
> I have another example with similar behavior. The exact commands used are
> below. The detailed output is attached in this email.
> 
> *command 1*: ffmpeg -i call.wav -af
> "volume=enable='between(t,0,1)':volume=0" output.wav
> *behaviour: *executed within a second, input file size 2.1 mb, output file
> size 176 mb
> 
> *command 2*: ffmpeg -i call.wav -af
> "volume=enable='between(t,0,1)':volume=0" output.mp3
> *behaviour: *executed time approx 40 seconds, input file size 2.1 mb,
> output file size 15 mb

You do not specify what kind of output file size you want, so yes, it will be 
‘as it is’.
Having a .wav extension on your input DOES NOT mean your input is uncompressed 
Wave PCM. (Wave Can be compressed, in your case, you have OGG compression with 
a .wav extension.)

What do you expect / why are you doing this? The quality of your file will NOT 
get better, nor will the file size get significant down if you process it.

Concerning your lack of knowledge, the only thing you can accomplish is making 
things worse.

Bouke


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Large Sized output files recieved while encoding the audio

2022-04-20 Thread Bouke / edit 'B
Hi Shubham,
When I copy your mail below (not done on this list, mind you!), it’s exactly as 
long as it was before. What do you expect?
Bouke



> On 20 Apr 2022, at 15:01, Shubham Tiwari  wrote:
> 
> Hi,
> 
> When I run ffmpeg command on a wav file, the received output file is of
> large size as compared to the original file. The command and the output are
> below,
> 
> *FFMPEG command*
> 
> % ~/Downloads/audio/ffmpeg -i call-redacted.wav output.wav
> 
> ffmpeg version 4.4.1-tessus  https://evermeet.cx/ffmpeg/  Copyright (c)
> 2000-2021 the FFmpeg developers
> 
>  built with Apple clang version 11.0.0 (clang-1100.0.33.17)
> 
>  configuration: --cc=/usr/bin/clang --prefix=/opt/ffmpeg
> --extra-version=tessus --enable-avisynth --enable-fontconfig --enable-gpl
> --enable-libaom --enable-libass --enable-libbluray --enable-libdav1d
> --enable-libfreetype --enable-libgsm --enable-libmodplug
> --enable-libmp3lame --enable-libmysofa --enable-libopencore-amrnb
> --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg
> --enable-libopus --enable-librubberband --enable-libshine
> --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora
> --enable-libtwolame --enable-libvidstab --enable-libvmaf
> --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwebp
> --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid
> --enable-libzimg --enable-libzmq --enable-libzvbi --enable-version3
> --pkg-config-flags=--static --disable-ffplay
> 
>  libavutil  56. 70.100 / 56. 70.100
> 
>  libavcodec 58.134.100 / 58.134.100
> 
>  libavformat58. 76.100 / 58. 76.100
> 
>  libavdevice58. 13.100 / 58. 13.100
> 
>  libavfilter 7.110.100 /  7.110.100
> 
>  libswscale  5.  9.100 /  5.  9.100
> 
>  libswresample   3.  9.100 /  3.  9.100
> 
>  libpostproc55.  9.100 / 55.  9.100
> 
> Input #0, mp3, from 'call-redacted.wav':
> 
>  Metadata:
> 
>encoder : Lavf58.45.100
> 
>  Duration: 00:13:06.38, start: 0.138125, bitrate: 64 kb/s
> 
>  Stream #0:0: Audio: mp3, 8000 Hz, stereo, fltp, 64 kb/s
> 
> Stream mapping:
> 
>  Stream #0:0 -> #0:0 (mp3 (mp3float) -> pcm_s16le (native))
> 
> Press [q] to stop, [?] for help
> 
> Output #0, wav, to 'output.wav':
> 
>  Metadata:
> 
>ISFT: Lavf58.76.100
> 
>  Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 8000 Hz, stereo,
> s16, 256 kb/s
> 
>Metadata:
> 
>  encoder : Lavc58.134.100 pcm_s16le
> 
> size=   24569kB time=00:13:06.17 bitrate= 256.0kbits/s speed=2.97e+03x
> 
> video:0kB audio:24569kB subtitle:0kB other streams:0kB global headers:0kB
> muxing overhead: 0.000310
> 
> 
> *Input and output file sizes*
> 
> du -sh call-redacted.wav
> 
> 6.5M call-redacted.wav
> 
> du -sh output.wav
> 
> 24M output.wav
> 
> 
> Alternatively, when I run the same command but change the output
> file's extension to mp3, the correct sized file is returned. But the time
> taken (6 seconds) in this case is quite higher than the previous case(less
> than 1 second). The command and output is below,
> 
> 
> 
> ~/Downloads/audio/ffmpeg -i call-redacted.wav output.mp3
> 
> ffmpeg version 4.4.1-tessus  https://evermeet.cx/ffmpeg/  Copyright (c)
> 2000-2021 the FFmpeg developers
> 
>  built with Apple clang version 11.0.0 (clang-1100.0.33.17)
> 
>  configuration: --cc=/usr/bin/clang --prefix=/opt/ffmpeg
> --extra-version=tessus --enable-avisynth --enable-fontconfig --enable-gpl
> --enable-libaom --enable-libass --enable-libbluray --enable-libdav1d
> --enable-libfreetype --enable-libgsm --enable-libmodplug
> --enable-libmp3lame --enable-libmysofa --enable-libopencore-amrnb
> --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg
> --enable-libopus --enable-librubberband --enable-libshine
> --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora
> --enable-libtwolame --enable-libvidstab --enable-libvmaf
> --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwebp
> --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid
> --enable-libzimg --enable-libzmq --enable-libzvbi --enable-version3
> --pkg-config-flags=--static --disable-ffplay
> 
>  libavutil  56. 70.100 / 56. 70.100
> 
>  libavcodec 58.134.100 / 58.134.100
> 
>  libavformat58. 76.100 / 58. 76.100
> 
>  libavdevice58. 13.100 / 58. 13.100
> 
>  libavfilter 7.110.100 /  7.110.100
> 
>  libswscale  5.  9.100 /  5.  9.100
> 
>  libswresample   3.  9.100 /  3.  9.100
> 
>  libpostproc55.  9.100 / 55.  9.100
> 
> Input #0, mp3, from 'call-redacted

Re: [FFmpeg-user] Fluorescent White Balance Video Filters

2022-04-19 Thread Bouke / edit 'B
On 19 Apr 2022, at 20:44, Jim DeLaHunt  wrote:
> 
> Not that the FFmpeg tool is stupid overall — it is quite capable and useful 
> in many ways. But there are aspects of the tool, and its documentation, and 
> its contributors' behaviour, and the project culture, which are indeed quite 
> stupid.

Hear hear!

Now, IMHO, audio mapping in FFmpeg is plain stupid. FFMBC’s approach what so 
much easier / better.
(On top of that, ripping just sound from an AV file with FFMBC was WAY faster, 
as FFMBC was able to ignore the video data, where FFmpeg seems to feel a need 
to plough trough it.)

Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Fluorescent White Balance Video Filters

2022-04-19 Thread Bouke / edit 'B

> On 19 Apr 2022, at 21:00, Carl Zwanzig  wrote:
> 
> On 4/19/2022 11:52 AM, Bouke / edit 'B wrote:
>>> How would you do that when there are only parameters for R and B?
> 
>> AFAIK, YUV = R-Y B-Y, so it’s just math.
>> Doing corrections in RGB is simpler for a mortal,
> 
> and in analog :)
> 
> What I'm getting at is there are no green terms on that filter's controls so 
> I don't see a way to directly adjust green (my point). This makes sense for a 
> filter that's trying to correct what we call white balance- like a 
> three-legged stool, you only ever have to adjust two legs to make the top 
> level.
> 
Could be I’m missing the point, but cutting / extending two legs of a three 
legged chair will close to NEVER make the desired height.
But yes, it will level it if needed, to stick to the reference.

I'm missing out on the ‘analog’ reference. AFAIK, YUV is still in use in 
(digital) codecs.
And it’s hard to grasp if you do color correction, and are used to fancy tools 
like Resolve. (That used to be a 100.000+ tool not so long ago.)

Bouke



___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Fluorescent White Balance Video Filters

2022-04-19 Thread Bouke / edit 'B


> On 19 Apr 2022, at 20:41, Carl Zwanzig  wrote:
> 
> On 4/19/2022 11:37 AM, Paul B Mahol wrote:
>> colorcorrect filter operates in YUV colorspace and not RGB colorspace
>> So green tint can be adjusted with it.
> 
> How would you do that when there are only parameters for R and B?
> 
> z!

AFAIK, YUV = R-Y B-Y, so it’s just math.
Doing corrections in RGB is simpler for a mortal, but should / could result 
exactly the same. Now, let someone write something to convert the matrix to 
support RGB.

Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] DNxHD / DNxHR conversions for Avid

2022-04-13 Thread Bouke / Videotoolshed
On 12 Apr 2022, at 21:24, Paul B Mahol  wrote:
> 
>> do cause an error on the Avid side if you drop them directly in an Avid
>> MediaFiles/MXF folder

If you want to use the MXF/xxx folders, you need special wrapped Avid MXF.
The BBC has made a tool for that, https://sourceforge.net/p/bmxlib/home/Home/ 
<https://sourceforge.net/p/bmxlib/home/Home/>

If you have a recent version of Avid MC, you can use normal Op1 MXF, but those 
have to go to
Avid MediaFiles/UME/xxx

Both can work, I’ve done it before.


Hth,
Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Loudnorm or ebu?

2022-04-12 Thread Bouke / Videotoolshed
Learn to live with it, as well as the flaming for top posting, as I’m about to 
receive.
(Or not, if I tell I actually like it to be spanked by nerds.(

Bouke


> On 12 Apr 2022, at 19:02, CMG DiGiTaL  wrote:
> 
> I have noticed, from the harsh and uneducated answers, that the
> distinguished
> Mr. Paul B Mahol, must have serious social relationship problems...
> ...poor man, must be a very lonely person!
> 
> 
> 
> Em ter., 12 de abr. de 2022 às 07:54, Reindl Harald 
> escreveu:
> 
>> 
>> 
>> Am 12.04.22 um 12:29 schrieb Paul B Mahol:
>>>> it's a *users list* if you haven't realized it
>>> 
>>> The tool is not provided by ffmpeg if you have not yet realized it by now
>> 
>> and who gives a shit?
>> it's a users list
>> 
>> just because a few morons on this list pretends wrappers are not
>> supported means nothing on a users-list
>> ___
>> ffmpeg-user mailing list
>> ffmpeg-user@ffmpeg.org
>> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>> 
>> To unsubscribe, visit link above, or email
>> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>> 
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] linear loudnorm

2022-02-27 Thread Bouke / edit 'B


>> 
>> I'm trying to nomalize an audio file with FFmpeg. I'm using the loudnorm
>> filter. The source loudness is -23 LUFS and I want to make it -17 LUFS.
>> As far as I know, loudnorm has 2 modes of normalizing audio: linear and


>> 2. Encode the audio with:
>> 
>> ffmpeg -i input.wav -filter:a
>> loudnorm=I=-17:TP=-1:LRA=9:measured_I=-22.72:measured_TP=-2.67:measured_LRA=6.10:measured_thresh=-33.31:offset=-0.05:linear=true:print_format=summary

Why not just add 6 dB to the input?

That ’should’ do the trick just fine imho. (As one LU should correspond with 1 
dB)


Bouke


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Video Notation, A Video Lingua Franca

2022-02-09 Thread Bouke / edit 'B


> On 9 Feb 2022, at 18:32, Mark Filipak  wrote:
> 
> Hello, All,

Bye Mark.go away!
Now. No time to waste. Unsub / close your internet account / kill yourself / 
hire someone to do that for you, I don’t care, just, stop.

Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Please advise

2021-12-30 Thread Bouke / edit 'B


> On 30 Dec 2021, at 15:16, Reindl Harald  wrote:
> 
> 
> 
> Am 30.12.21 um 15:05 schrieb Bouke / edit 'B:
>>> On 30 Dec 2021, at 14:58, Reindl Harald  wrote:
>>> 
>>> it's amazing that you
>> Hey Harald,
>> Are you allright? You almost sound polite!
> 
> no, not if you read the whole sentence

I did, you wrote:
"it's amazing that you managed to subscribe but not to understand a ML”
I fail to see a good insult in that line.

> i forgot to mention that "New post" is a idiotic subject for any email no 
> matter in what context

I agree, but since these are your words, I could not care less.

> 
>> Is everything well? Should someone call a doctor / inform the authorities?
> 
> mind your own business

I AM. My business is (sometimes) to make this world a better place.
You are trying to do the same thing, in the most irritating offensive annoying 
way I’ve ever encountered.
(Not that I disagree about the stupidity in this thread, but that’s beside the 
point.)

Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Please advise

2021-12-30 Thread Bouke / edit 'B



> On 30 Dec 2021, at 14:58, Reindl Harald  wrote:
> 
> it's amazing that you 

Hey Harald,
Are you allright? You almost sound polite!
Is everything well? Should someone call a doctor / inform the authorities?

Bouke


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] ffmpeg create wrong time information

2021-12-22 Thread Bouke / Videotoolshed



> On 21 Dec 2021, at 19:37, Cecil Westerhof via ffmpeg-user 
>  wrote:
> 
> Cecil Westerhof via ffmpeg-user  writes:
> 
> After some experiments I solved it by putting -ss and -to behind -i
> and not forgetting to alter the between values.
> But this takes about a third more time.
> Is there be a better solution?
> 
> I am now using:
>ffmpeg -y \
>-i input.mp4  \
>-ss 00:26:05  \
>-to 00:44:04  \
>-vf "
> drawbox=enable='between(t, 1565, 1566.6)':
>color = black :
>w = in_w  :
>h = in_h  :
>thickness = fill
>" \
>-acodec copy  \
>-vcodec libx264   \
>-crf 23   \
>-preset veryfast  \
>output.mkv

I think you are inserting black, not overlaying (blanking) the video. Try -vf 
overlay.
With -ss before input, it will do a faster search, you might have to do a bit 
of math on the enable= range, but that will become very obvious with a small 
test.

Bouke
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Concatenating video cuts - audio gets out of sync...

2021-12-17 Thread Bouke (Edit 'B)

> On 17 Dec 2021, at 11:08, Bo Berglund  wrote:
> 
> Can I keep the copy for video but re-encode for audio?
> Some ffmpeg command suggestion?

-c:v copy -c:a ‘something’, but no clue if it will help you…

Bouke
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] How to change recording datetime of WAV files

2021-09-15 Thread Bouke



> On 15 Sep 2021, at 09:19, Felix E. Klee  wrote:
> 
> I tried now to change the creation time, but this actually removes it:
> 
>$ ffprobe ZOOM0004.WAV
>[…]
>  Metadata:
>encoded_by  : ZOOM Field Recorder F1
>date: 2021-09-13
>creation_time   : 19:21:33
>time_reference  : 3345264000
>coding_history  : A=PCM,F=48000,W=24,M=stereo,T=ZOOM Field
>  Recorder F1


why would you want to change the creation time if you have a bwf timestamp?
That ’should’ be locked to other equipment and is the most important metadata, 
any post software will use that instead of file creation time.


Bouke

>[…]
>$ ffmpeg -i ZOOM0004.WAV -metadata creation_time="03:17:33" OUT.WAV
>[…]
>$ ffprobe OUT.WAV
>[…]
>  Metadata:
>date: 2021-09-13
>encoder : Lavf58.76.100
>encoded_by  : ZOOM Field Recorder F1
>[…]
> 
> What’s wrong?
> 
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


[FFmpeg-user] Does recording stops without encoding the buffer?

2021-09-09 Thread Bouke
Trying to record two streams with something like this:

ffmpeg -hide_banner -thread_queue_size "35012" -f "decklink" -queue_size 
"1073741824" -raw_format "auto" -format_code "Hp25" -channels "2" 
-timecode_format "rp188ltc" -video_input "sdi" -audio_input "embedded" 
-audio_depth "16" -i "bm mini Two" -timecode "09:13:28:04" -metadata:s:v:0 
"reel_name=Reelname" -filter_complex "[0:v]split=2[out1][out2]" -map "[out1]" 
-map "0:a" -c:a "pcm_s16le" -c:v "prores" -profile:v "0" -vendor "ap10" 
-pix_fmt "yuv422p10le" "/Volumes/Data/09-09-2021/669.mov" -map "[out2]" -c:v 
"libx264" -preset "ultrafast" -g "30" -pix_fmt "yuv422p" -tune "zerolatency" 
-aspect "16:9" -f "tee" -map "0:v" "[f=mpegts]udp://127.0.0.1:1230" 

Stop recording by sending 'q' to both instances (at about the same time)
Now, sometimes one of the recordings is way shorter than the other, and does 
not hold all video as expected.
My guess (I don't have access to the machine it's running on now) is that the 
buffer isn't processed after the 'q' is received.

Could this be the case? If so, any workaround? 

(Besides looking at the amount of frames encoded and wait until it matches the 
time user pressed 'stop record'.)

thx
Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] ITU-R BS.1770-1 (Netflix) audio measurement, just hack it...

2021-08-12 Thread Bouke


> On 11 Aug 2021, at 12:18, Bouke  wrote:
> 
>> 
>> On 11 Aug 2021, at 09:01, Carl Eugen Hoyos  wrote:
>> 
>> 
>> 
>>> Am 10.08.2021 um 11:03 schrieb Bouke :
>>> 
>>> I'm using the R128 functionality now, but Netflix wants sound to be Dolby 
>>> dialogue-gated measured.
>> 
>>> Seems that the needed Dolby code is free now.
>> 
>> Very generally, this was unlikely, after following the links you provided, 
>> it’s not correct.
>> („free“ has more than one meaning, on a mailing list that deals with open 
>> source software, the interpretation „no money needed“ is not relevant.)
> 
> Hi Carl Eugen,
> Sorry, my bad, I should have seen that one coming.
> 
> Nevertheless, I can see some possibilities:
> Redo / reverse engineer the dialog gating with ’some’ filter, and implement 
> 1770-1.
> It does not need to be exact the same as Dolby wants, as Netflix allows for 
> +/- 2 LU. (And that’s a lot I woud think.)
> 
> Another option perhaps could be that I pay someone for a custom version that 
> I can distribute. (In which case I need to do the Dolby dance.)


Thinking of it, for Netflix delivery, there also have to be stems.
So a silence detection of the dialogue stem should provide data for timeline 
measuring.
It won’t be exactly the same, but I bet it will get very close.

Bouke

> 
> What do you think?
> 
> Bouke
> 
> 
>> 
>> Carl Eugen
>> ___
>> ffmpeg-user mailing list
>> ffmpeg-user@ffmpeg.org <mailto:ffmpeg-user@ffmpeg.org>
>> https://ffmpeg.org/mailman/listinfo/ffmpeg-user 
>> <https://ffmpeg.org/mailman/listinfo/ffmpeg-user>
>> 
>> To unsubscribe, visit link above, or email
>> ffmpeg-user-requ...@ffmpeg.org <mailto:ffmpeg-user-requ...@ffmpeg.org> with 
>> subject "unsubscribe".
> 
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org <mailto:ffmpeg-user@ffmpeg.org>
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user 
> <https://ffmpeg.org/mailman/listinfo/ffmpeg-user>
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org <mailto:ffmpeg-user-requ...@ffmpeg.org> with 
> subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] ITU-R BS.1770-1 (Netflix) audio measurement

2021-08-11 Thread Bouke

> On 11 Aug 2021, at 09:01, Carl Eugen Hoyos  wrote:
> 
> 
> 
>> Am 10.08.2021 um 11:03 schrieb Bouke :
>> 
>> I'm using the R128 functionality now, but Netflix wants sound to be Dolby 
>> dialogue-gated measured.
> 
>> Seems that the needed Dolby code is free now.
> 
> Very generally, this was unlikely, after following the links you provided, 
> it’s not correct.
> („free“ has more than one meaning, on a mailing list that deals with open 
> source software, the interpretation „no money needed“ is not relevant.)

Hi Carl Eugen,
Sorry, my bad, I should have seen that one coming.

Nevertheless, I can see some possibilities:
Redo / reverse engineer the dialog gating with ’some’ filter, and implement 
1770-1.
It does not need to be exact the same as Dolby wants, as Netflix allows for +/- 
2 LU. (And that’s a lot I woud think.)

Another option perhaps could be that I pay someone for a custom version that I 
can distribute. (In which case I need to do the Dolby dance.)

What do you think?

Bouke


> 
> Carl Eugen
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


[FFmpeg-user] ITU-R BS.1770-1 (Netflix) audio measurement

2021-08-10 Thread Bouke
I'm using the R128 functionality now, but Netflix wants sound to be Dolby 
dialogue-gated measured.
Seems that the needed Dolby code is free now.

More reading here:
https://www.pro-tools-expert.com/home-page/2018/8/23/has-netflix-turned-the-clock-back-10-years-or-is-their-new-loudness-delivery-spec-a-stroke-of-genius

Some work seems to be done already:
https://github.com/reaper-oss/sws/issues/1046 
<https://github.com/reaper-oss/sws/issues/1046>


Is it possible to implement this in FFmpeg? Can I sponsor / hire a developer?

Thx,

Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


[FFmpeg-user] FFmpeg capture, mkvtimestamp_v2, vsync 0 and timecode don't play nice

2021-05-24 Thread Bouke
Trying to capture and modify the TC in-file afterwards.
I've found a nice way to store the timestamps from the capture.
(https://stackoverflow.com/questions/53391150/ffmpeg-obtain-the-system-time-corresponding-to-each-frame-present-in-a-video)

This works fine using this line:

ffmpeg -hide_banner -f "decklink" -queue_size "1073741824" -raw_format "auto" 
-format_code "Hi50" -video_input "sdi" -i "bm mini One" -filter_complex 
"settb=1/1000,setpts=RTCTIME/1000-15000,mpdecimate,split[out][ts];[out]setpts=N/25/TB[out]"
 -map "[out]" -c:a "copy" -c:v "prores" -profile:v "1" -vendor "ap10" -pix_fmt 
"yuv422p10le" "/Volumes/Data/tst1.mov" -map "[ts]" -f mkvtimestamp_v2 
"/Volumes/Data/time.txt" -vsync 0

But, when I add -timecode "00:00:00:00" (to force a TC atom in the output), 
horrible things happen.

ffmpeg -f "decklink" -queue_size "1073741824" -raw_format "auto" -format_code 
"Hi50" -video_input "sdi" -i "bm mini One" -filter_complex 
"settb=1/1000,setpts=RTCTIME/1000-15000,mpdecimate,split[out][ts];[out]setpts=N/25/TB[out]"
 -map "[out]" -timecode "00:01:00:00" -c:a "copy" -c:v "prores" -profile:v "1" 
-vendor "ap10" -pix_fmt "yuv422p10le" "/Volumes/Data/tst1.mov" -map "[ts]" -f 
mkvtimestamp_v2 "/Volumes/Data/time.txt" -vsync 0

The timecode does not run at the video speed, skips a frame or two here and 
there, and the image freezes after a random amount of time (between 10 seconds 
and a minute or so).

How come the timecode can mess up stuff that much? From what I understand it's 
just a couple of atoms in the moov atom, and a reference where the actual TC 
value (as frames) is stored in the mdat.

I highly suspect the -vsync 0 to also work on the video. If I omit that, the 
video is fine, the TC is fine, but there is no metadata output, just the # 
timecode format v2

The alternative to this dance is to use -timestamp_align, but I also want to 
use non-decklink audio, and I can’t get that in sync. (Using -ss for sound is 
not accurate.)
 
Bouke

Output from the terminal: (non-working file)

bouke@Boukes-iMac ~ %  ffmpeg -f "decklink" -queue_size "1073741824" 
-raw_format "auto" -format_code "Hi50" -video_input "sdi" -i "bm mini One" 
-filter_complex 
"settb=1/1000,setpts=RTCTIME/1000-15000,mpdecimate,split[out][ts];[out]setpts=N/25/TB[out]"
 -map "[out]" -timecode "00:01:00:00" -c:a "copy" -c:v "prores" -profile:v "1" 
-vendor "ap10" -pix_fmt "yuv422p10le" "/Volumes/Data/tst1.mov" -map "[ts]"  -f 
mkvtimestamp_v2 "/Volumes/Data/time.txt" -vsync 0
ffmpeg version git-2021-03-31-b3e9a84 Copyright (c) 2000-2021 the FFmpeg 
developers
  built with Apple clang version 12.0.0 (clang-1200.0.32.29)
  configuration: --enable-videotoolbox --enable-nonfree --enable-gpl 
--enable-lv2 --enable-openssl --enable-libsvtav1 --enable-libx264 
--enable-libx265 --enable-libvpx --enable-libxvid --enable-libvidstab 
--enable-libaom --enable-libopencore_amrnb --enable-libopencore_amrwb 
--enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libtheora 
--enable-libfdk-aac --enable-libwebp --enable-libsrt --disable-debug 
--disable-doc --disable-shared --enable-pthreads --enable-static --enable-small 
--enable-version3 --enable-libfreetype --enable-libfontconfig --enable-decklink 
--extra-cflags='-I/Users/bouke/ffmpeg-build-script/workspace/include 
-I/Users/bouke/ffmpeg-build-script/include' --extra-ldexeflags= 
--extra-ldflags='-L/Users/bouke/ffmpeg-build-script/workspace/lib 
-L/Users/bouke/ffmpeg-build-script/include' --extra-libs='-ldl -lpthread -lm 
-lz' --pkgconfigdir=/Users/bouke/ffmpeg-build-script/workspace/lib/pkgconfig 
--pkg-config-flags=--static --prefix=/Users/bouke/ffmpeg-build-script/workspace
  libavutil  56. 63.101 / 56. 63.101
  libavcodec 58.117.101 / 58.117.101
  libavformat58. 65.101 / 58. 65.101
  libavdevice58. 11.103 / 58. 11.103
  libavfilter 7. 96.100 /  7. 96.100
  libswscale  5.  8.100 /  5.  8.100
  libswresample   3.  8.100 /  3.  8.100
  libpostproc55.  8.100 / 55.  8.100
[decklink @ 0x7fc41a808200] Found Decklink mode 1920 x 1080 with rate 25.00(i)
[decklink @ 0x7fc41a808200] Frame received (#1) - No input signal detected - 
Frames dropped 1
Guessed Channel Layout for Input Stream #0.0 : stereo
Input #0, decklink, from 'bm mini One':
  Duration: N/A, start: 0.00, bitrate: 830976 kb/s
Stream #0:0: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s
Stream #0:1: Video: rawvideo (UYVY / 0x59565955), uyvy422(top first), 

Re: [FFmpeg-user] Python / Qprocess misfires commands. SOLVED

2021-05-19 Thread Bouke

> On 18 May 2021, at 16:28, Moritz Barsnick  wrote:
> 
> Hmm. Your attached reports indicate that there were more log messages.
> I wonder where they went…

I found it.
They went into the smelly lava / tar pit deep under Cupertino, sent there by 
’Security & Privacy’.
This specific demon ’should’ ask if it’s OK to use the microphone, but it does 
not.

Curses! Two days lost on something I should have known.

Thanks for all the suggestions!

Bouke



___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Python / Qprocess misfires commands.

2021-05-18 Thread Bouke

> On 18 May 2021, at 09:33, Moritz Barsnick  wrote:
> 
> On Mon, May 17, 2021 at 09:19:46 +0200, Bouke wrote:
>>> You will have to show/look at the console output of both commands.
>>> (It's there for a reason, and most likely says what the issue is.)
>> 
>> I know, but there was ’nothing’ on stdErr / stdOut.
> 
> Then you're capturing your output incorrectly.

Nah, this was an apology for an earlier message where I ment ’nothing except 
the banner'

> 
>> It turns out that FFmpeg crashes, nothing wrong with the command line.
>> QProcess sees an error, and either QProcess terminates FFmpeg (I don’t think 
>> so) or FFmpeg crashes by itself.
> 
> If QProcess terminates it unconditionally, there's nothing we can do(?).

I understand, but now it’s the blame game, what happens where / when / why?

> If ffmpeg crashes, that's bad. You would have to convince your system
> to create a core dump, and would have to look at a backtrace. (Or run
> ffmpeg within gdb.)

Eeh, I’m a simple scripter, not a coder, no clue how to do that...

> 
>> in Python:
>> cmd = "bash"
>> args = ["-c", "/Applications/ffmpeg -loglevel trace -report -f avfoundation 
>> -i :0 /Volumes/Data/test.mov"]
> 
> Do you need to run it in bash? Can you not set cmd to "ffmpeg" and
> properly pass the arguments?

Normally I do that, especially as that saves tons of headaches on escaping 
stuff.
But this was a suggestion from the QT forum, hoping it would provide a bit more 
insight.
https://forum.qt.io/topic/126674/escaping-colon-in-command-line-argument/8 
<https://forum.qt.io/topic/126674/escaping-colon-in-command-line-argument/8>

Trust me, it makes no difference if I use separate args or run it as bash.

Bouke


> 
> Regards,
> Moritz
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


[FFmpeg-user] XDcam MXF wrong field order

2021-05-18 Thread Bouke

Trying to make broadcast compliant (XDcam style) MXF files, but those fail on 
wrong field order, if the source is progressive.
This used to work fine. (ffmpeg version 3.2.2 has no issues with this, and has 
done literally thousands of good / compliant files)

FFmpeg always reports "top coded first (swapped))", and MediaInfo says:
Scan order   : Bottom Field First

If I swap out -top 1 for -field_order tt it does not help at all.

Now, it ’should’ not be an issue, except that Baton / pre baton scripts bitch 
about it, and the files get rejected.


Bouke

Stripped down line: (To indicate the problem, this will not make a compliant 
file, I know.)

/Applications/ffmpeg -i /Volumes/Data/17-05-2021_14-34-56_1.mov -c:v mpeg2video 
-b:v 5k -maxrate 5k -bufsize 3835k -minrate 5k -r 25 -flags 
+ilme+ildct -top 1 -pix_fmt yuv422p -profile:v 0 -level:v 2 -t 1 
/Volumes/Data/interlacetest.mxf -y 

ffmpeg version 4.4-tessus  https://evermeet.cx/ffmpeg/  Copyright (c) 2000-2021 
the FFmpeg developers
  built with Apple clang version 11.0.0 (clang-1100.0.33.17)
  configuration: --cc=/usr/bin/clang --prefix=/opt/ffmpeg 
--extra-version=tessus --enable-avisynth --enable-fontconfig --enable-gpl 
--enable-libaom --enable-libass --enable-libbluray --enable-libdav1d 
--enable-libfreetype --enable-libgsm --enable-libmodplug --enable-libmp3lame 
--enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb 
--enable-libopenh264 --enable-libopenjpeg --enable-libopus 
--enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr 
--enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab 
--enable-libvmaf --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx 
--enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs 
--enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi 
--enable-version3 --pkg-config-flags=--static --disable-ffplay
  libavutil  56. 70.100 / 56. 70.100
  libavcodec 58.134.100 / 58.134.100
  libavformat58. 76.100 / 58. 76.100
  libavdevice58. 13.100 / 58. 13.100
  libavfilter 7.110.100 /  7.110.100
  libswscale  5.  9.100 /  5.  9.100
  libswresample   3.  9.100 /  3.  9.100
  libpostproc55.  9.100 / 55.  9.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 
'/Volumes/Data/17-05-2021_14-34-56_1.mov':
  Metadata:
major_brand : qt  
minor_version   : 512
compatible_brands: qt  
encoder : Lavf58.65.101
  Duration: 00:00:15.20, start: 0.00, bitrate: 276385 kb/s
  Stream #0:0: Video: prores (HQ) (apch / 0x68637061), yuv422p10le(tv, top 
coded first (swapped)), 1920x1080, 274850 kb/s, 25 fps, 25 tbr, 12800 tbn, 
12800 tbc (default)
Metadata:
  handler_name: VideoHandler
  vendor_id   : FFMP
  encoder : Lavc58.117.101 prores
  timecode: 12:34:59:00
  Stream #0:1: Audio: pcm_s16le (sowt / 0x74776F73), 48000 Hz, stereo, s16, 
1536 kb/s (default)
Metadata:
  handler_name: SoundHandler
  vendor_id   : [0][0][0][0]
  Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s
Metadata:
  handler_name: TimeCodeHandler
  timecode: 12:34:59:00
Stream mapping:
  Stream #0:0 -> #0:0 (prores (native) -> mpeg2video (native))
  Stream #0:1 -> #0:1 (pcm_s16le (native) -> pcm_s16le (native))
Press [q] to stop, [?] for help
Output #0, mxf, to '/Volumes/Data/interlacetest.mxf':
  Metadata:
major_brand : qt  
minor_version   : 512
compatible_brands: qt  
encoder : Lavf58.76.100
  Stream #0:0: Video: mpeg2video (4:2:2), yuv422p(tv, progressive), 1920x1080, 
q=2-31, 5 kb/s, 25 fps, 25 tbn (default)
Metadata:
  handler_name: VideoHandler
  vendor_id   : FFMP
  timecode: 12:34:59:00
  encoder : Lavc58.134.100 mpeg2video
Side data:
  cpb: bitrate max/min/avg: 5000/5000/5000 buffer size: 3835000 
vbv_delay: N/A
  Stream #0:1: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s (default)
Metadata:
  handler_name: SoundHandler
  vendor_id   : [0][0][0][0]
  encoder : Lavc58.134.100 pcm_s16le
frame=1 fps=0.0 q=0.0 size=   0kB time=00:00:00.16 bitrate=   
0.0kbits/sframe=   24 fps=0.0 q=2.0 size=5632kB time=00:00:00.96 
bitrate=48059.7kbits/frame=   25 fps=0.0 q=1.6 Lsize=6216kB 
time=00:00:00.96 bitrate=53043.7kbits/s speed=1.79x
video:5986kB audio:188kB subtitle:0kB other streams:0kB global headers:0kB 
muxing overhead: 0.681476%
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Python / Qprocess misfires commands.

2021-05-17 Thread Bouke

> On 16 May 2021, at 15:46, Moritz Barsnick  wrote:
> 
> On Fri, May 14, 2021 at 13:16:41 +0200, Bouke wrote:
>> Using Python to fire FFmpeg
>> cmd = ‘ffmpeg’
>> args = [‘-f’, ‘avfoundation’, ‘-i’, ‘:0’]
>> 
>> with a QProcess, this returns exit code 6, exitstatus 1
>> 
>> 
>> ffmpeg -f avfoundation -i :0 in a Terminal works.
>> (At least one output file….)
> 
> You will have to show/look at the console output of both commands.
> (It's there for a reason, and most likely says what the issue is.)


Hi Moritz,
I know, but there was ’nothing’ on stdErr / stdOut.
It turns out that FFmpeg crashes, nothing wrong with the command line.
QProcess sees an error, and either QProcess terminates FFmpeg (I don’t think 
so) or FFmpeg crashes by itself.
Strange thing is, the EXACT same line works from the terminal.

I’m pretty sure that it’s not something in my code. I’ve ran a gazillion 
decklink captures. Trouble starts when I want to use avfoundation.

in Python:
cmd = "bash"
args = ["-c", "/Applications/ffmpeg -loglevel trace -report -f avfoundation -i 
:0 /Volumes/Data/test.mov"]

self.proc = QProcess(self._main)
self.proc.finished.connect(self.renderdone)
self.proc.errorOccurred.connect(self.erroroccured)
self.proc.start(cmd, args)
print("cmd is now", self.proc.arguments())
self.proc.readyReadStandardOutput.connect(lambda: 
self.readStdOutput(self.proc))
self.proc.readyReadStandardError.connect(lambda: 
self.readStdErr(self.proc))

Attachments don’t seem to work for me, so I copy / paste the reports below, 
first the failing one from Python, then the working one from the terminal.

Anything else I can do to figure out why the same line does not work fired from 
Python?

ffmpeg started on 2021-05-17 at 08:40:32
Report written to "ffmpeg-20210517-084032.log"
Log level: 56
Command line:
ffmpeg -loglevel trace -report -f avfoundation -i :0 /Volumes/Data/test.mov
ffmpeg version git-2021-03-31-b3e9a84 Copyright (c) 2000-2021 the FFmpeg 
developers
  built with Apple clang version 12.0.0 (clang-1200.0.32.29)
  configuration: --enable-videotoolbox --enable-nonfree --enable-gpl 
--enable-lv2 --enable-openssl --enable-libsvtav1 --enable-libx264 
--enable-libx265 --enable-libvpx --enable-libxvid --enable-libvidstab 
--enable-libaom --enable-libopencore_amrnb --enable-libopencore_amrwb 
--enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libtheora 
--enable-libfdk-aac --enable-libwebp --enable-libsrt --disable-debug 
--disable-doc --disable-shared --enable-pthreads --enable-static --enable-small 
--enable-version3 --enable-libfreetype --enable-libfontconfig --enable-decklink 
--extra-cflags='-I/Users/bouke/ffmpeg-build-script/workspace/include 
-I/Users/bouke/ffmpeg-build-script/include' --extra-ldexeflags= 
--extra-ldflags='-L/Users/bouke/ffmpeg-build-script/workspace/lib 
-L/Users/bouke/ffmpeg-build-script/include' --extra-libs='-ldl -lpthread -lm 
-lz' --pkgconfigdir=/Users/bouke/ffmpeg-build-script/workspace/lib/pkgconfig 
--pkg-config-flags=--static --prefix=/Users/bouke/ffmpeg-build-script/workspace
  libavutil  56. 63.101 / 56. 63.101
  libavcodec 58.117.101 / 58.117.101
  libavformat58. 65.101 / 58. 65.101
  libavdevice58. 11.103 / 58. 11.103
  libavfilter 7. 96.100 /  7. 96.100
  libswscale  5.  8.100 /  5.  8.100
  libswresample   3.  8.100 /  3.  8.100
  libpostproc55.  8.100 / 55.  8.100
Splitting the commandline.
Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) 
with argument 'trace'.
Reading option '-report' ... matched as option 'report' (generate a report) 
with argument '1'.
Reading option '-f' ... matched as option 'f' (force format) with argument 
'avfoundation'.
Reading option '-i' ... matched as input url with argument ':0'.
Reading option '/Volumes/Data/test.mov' ... matched as output url.
Finished splitting the commandline.
Parsing a group of options: global .
Applying option loglevel (set logging level) with argument trace.
Applying option report (generate a report) with argument 1.
Successfully parsed a group of options.
Parsing a group of options: input url :0.
Applying option f (force format) with argument avfoundation.
Successfully parsed a group of options.
Opening an input file: :0.
[avfoundation @ 0x7f905080ee00] audio device 'Built-in Microphone' opened


##

The Terminal version:

ffmpeg started on 2021-05-17 at 08:41:36
Report written to "ffmpeg-20210517-084136.log"
Log level: 56
Command line:
ffmpeg -loglevel trace -report -f avfoundation -i :0 /Volumes/Data/test.mov
ffmpeg version git-2021-03-31-b3e9a84 Copyright (c) 2000-2021 the FFmpeg 
developers
  built with Apple clang version 12.0.0 (clang-1200.0.32.29)
  configuration: --enable-videotoolbox --enable-nonfree --enabl

[FFmpeg-user] Python / Qprocess misfires commands.

2021-05-14 Thread Bouke
Using Python to fire FFmpeg
cmd = ‘ffmpeg’
args = [‘-f’, ‘avfoundation’, ‘-i’, ‘:0’]

with a QProcess, this returns exit code 6, exitstatus 1


ffmpeg -f avfoundation -i :0 in a Terminal works.
(At least one output file….)


Bouke


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


[FFmpeg-user] FFplay turkey

2021-05-13 Thread Bouke
When I run FFplay, and scale the window to something like 320x180, AND drag the 
top to something smaller than 150:

On doubleclick, fullscreen
Next doubleclick, window scales back, but vertical position is now at the 
bottom of the screen.
When the small window is lower than 150 all is as expected. If the window is 
bigger (no clue how big it must be), it also does not happen.

This does not happen when I use the fullscreen button, and doubleclick to get 
back to ’normal’

Happens on OSX / catalina, have not tested other OS’s


Bouke


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Failed / strange build script, now with log / script files in link

2021-05-11 Thread Bouke

> On 11 May 2021, at 14:59, Moritz Barsnick  wrote:
> 
> On Tue, May 11, 2021 at 09:50:14 +0200, Bouke wrote:
>> Logfiles and script is here:
>> Download link
>> https://we.tl/t-UB5Ynvv8DE <https://we.tl/t-UB5Ynvv8DE>
>> 
>> (Original script comes from 
>> https://github.com/markus-perl/ffmpeg-build-script 
>> <https://github.com/markus-perl/ffmpeg-build-script> )
> 
> You can't report your issue there, because you modified the script,
> correct?

Hi Moritz,
I can report the issue here, I did :-)

> I don't see a drawtext/fontconfig feature request there
> either. (I do see your Decklink one.)

Eeh, don’t you see:
CONFIGURE_OPTIONS+=("--enable-libfontconfig")
CONFIGURE_OPTIONS+=("--enable-libfreetype")

> Anyway, regarding fontconfig:
> 
>> test_pkg_config libfontconfig fontconfig fontconfig/fontconfig.h FcInit
>> pkg-config --exists --print-errors fontconfig
>> Package fontconfig was not found in the pkg-config search path.
>> Perhaps you should add the directory containing `fontconfig.pc'
>> to the PKG_CONFIG_PATH environment variable
>> No package 'fontconfig' found
>> ERROR: fontconfig not found using pkg-config
> 
> Does your machine have actually fontconfig.pc?
> On Linux, I would do
> $ locate fontconfig.pc
> I assume MacOS has a similar function. (Note that the database for
> locate is updated in large intervals, it won't find anything I
> installed today.)

It seems to be there...
MacBook-Pro:ffmpeg-build-script bouke$ locate fontconfig.pc
/System/Volumes/Update/mnt1/Users/bouke/ffmpeg-build-script/packages/pkg-config-0.29.2/check/gtk/fontconfig.pc
/Users/bouke/ffmpeg-build-script/packages/pkg-config-0.29.2/check/gtk/fontconfig.pc

However, I don’t really need libfontconfig it seems. (I don’t need font 
substitudion, this is for a very specific project for just a couple om machines.
Leaving —enable-libfontconfig out let me build on the machine that failed 
before.


> And regarding static/dynamic:
>> MacBook-Pro:~ bouke$ /Users/bouke/Desktop/ffplay ; exit;
>> dyld: Library not loaded: /usr/local/opt/fontconfig/lib/libfontconfig.1.dylib
>>  Referenced from: /Users/bouke/Desktop/ffplay
>>  Reason: image not found
> 
> I have no idea why the compiler would link against a dynamic library
> which isn't there. On Linux, I would know how to check the compile-time
> and run-time linkers, but not here remotely.
> 
> And regarding static vs. dynamic: Is a static libfontconfig available
> at all? Does the system provide static libraries? (I sort of doubt it.)

I have no clue… But the dowloads from evermeet.cx <http://evermeet.cx/> / 
gyan.dev always work, so it ’should’ be possible.

On ‘clean’ machines I still get:
dyld: Library not loaded: /usr/local/opt/freetype/lib/libfreetype.6.dylib

But at least I have a bit hope my client is able to run the script.

thx,
Bouke

> 
> Cheers,
> Moritz
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Failed / strange build script, now with log / script files in link

2021-05-11 Thread Bouke

> On 11 May 2021, at 11:29, Reindl Harald  wrote:
> 
> 
> 
> Am 11.05.21 um 09:50 schrieb Bouke:
>>> from the Compilation guide it is suggestred that macOS comes with freetype 
>>> installed.
>>> freetype-config on the ‘good’ machine works,
>>> but on the non-working machine:
>>> -bash: freetype-config: command not found
>>> 
>>> So, two problems:
>>> 1) not fully static
>>> 2) not able to build on ’some’ machines
>>> 
>>> What am I missing?
>>> Logfiles and script are attached
>>> 
>>> Bouke
>>> 
>> Logfiles and script is here:
>> Download link
>> https://we.tl/t-UB5Ynvv8DE <https://we.tl/t-UB5Ynvv8DE>
>> (Original script comes from 
>> https://github.com/markus-perl/ffmpeg-build-script 
>> <https://github.com/markus-perl/ffmpeg-build-script> )
> 
> besides that i won't use Apple or such a sript

Hi Harald,
Always a pleasure to read your kind comments.
You might be an experienced coder, I’m not. I’m a video editor trying to make 
peoples life easier.

> can't you read or what did you not understand in **only Linux** in context of 
> "1) not fully static"


What was unclear to you about me stating that I am trying to alter the script?
Besides, from what I read is that for Linux you have an OPTION to do full 
static, where on OSX its ALWAYS full static.
(And that seems to be the case, except for the mentioned issues.)

So, what do I need to do more then to add —enalble-libfontconfig 
—enable-libfreetype?


Bouke

> 
> https://github.com/markus-perl/ffmpeg-build-script 
> <https://github.com/markus-perl/ffmpeg-build-script>
> Usage
> 
> Usage: build-ffmpeg [OPTIONS]
> Options:
>  -h, --help Display usage information
>  --version  Display version information
>  -b, --buildStarts the build process
>  --enable-gpl-and-non-free  Enable non-free codecs  - 
> https://ffmpeg.org/legal.html <https://ffmpeg.org/legal.html>
>  -c, --cleanup  Remove all working dirs
>  --full-static  Complete static build of ffmpeg (eg. glibc, 
> pthreads etc...) **only Linux**
> Note: Because of the NSS (Name Service 
> Switch), glibc does not recommend static
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org <mailto:ffmpeg-user@ffmpeg.org>
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user 
> <https://ffmpeg.org/mailman/listinfo/ffmpeg-user>
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org <mailto:ffmpeg-user-requ...@ffmpeg.org> with 
> subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Failed / strange build script, now with log / script files in link

2021-05-11 Thread Bouke

> On 10 May 2021, at 10:47, Bouke  wrote:
> 
> Hi all,
> I’ve downloaded a FFMpeg build script and altered it to my liking
> (Added Decklink support / drawtext)
> 
> running the script as ./build-ffmpeg -b --enable-gpl-and-non-free
> 
> Now it does build on a Catalina system, but fails on a Big Sur.
> The succesfull build however has dependencies  where everything should be 
> static.
> 
> MacBook-Pro:~ bouke$ /Users/bouke/Desktop/ffplay ; exit;
> dyld: Library not loaded: /usr/local/opt/fontconfig/lib/libfontconfig.1.dylib
>  Referenced from: /Users/bouke/Desktop/ffplay
>  Reason: image not found
> 
> 
> The failed builds seems to fail on 
> Library not loaded: /usr/local/opt/fontconfig/lib/libfontconfig.1.dylib
> 
> from the Compilation guide it is suggestred that macOS comes with freetype 
> installed.
> freetype-config on the ‘good’ machine works, 
> but on the non-working machine:
> -bash: freetype-config: command not found
> 
> 
> So, two problems:
> 1) not fully static
> 2) not able to build on ’some’ machines
> 
> What am I missing?
> Logfiles and script are attached
> 
> Bouke
> 

Logfiles and script is here:
Download link 
https://we.tl/t-UB5Ynvv8DE <https://we.tl/t-UB5Ynvv8DE>

(Original script comes from https://github.com/markus-perl/ffmpeg-build-script 
<https://github.com/markus-perl/ffmpeg-build-script> )


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Failed / strange build script

2021-05-10 Thread Bouke


> On 10 May 2021, at 16:31, Moritz Barsnick  wrote:
> 
> 
> No, they are not.

How does one attach a file here?

I’m pretty sure I did attach the stuff…

Bouke
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


[FFmpeg-user] Failed / strange build script

2021-05-10 Thread Bouke
Hi all,
I’ve downloaded a FFMpeg build script and altered it to my liking
(Added Decklink support / drawtext)

running the script as ./build-ffmpeg -b --enable-gpl-and-non-free

Now it does build on a Catalina system, but fails on a Big Sur.
The succesfull build however has dependencies  where everything should be 
static.

MacBook-Pro:~ bouke$ /Users/bouke/Desktop/ffplay ; exit;
dyld: Library not loaded: /usr/local/opt/fontconfig/lib/libfontconfig.1.dylib
  Referenced from: /Users/bouke/Desktop/ffplay
  Reason: image not found


The failed builds seems to fail on 
Library not loaded: /usr/local/opt/fontconfig/lib/libfontconfig.1.dylib

from the Compilation guide it is suggestred that macOS comes with freetype 
installed.
freetype-config on the ‘good’ machine works, 
but on the non-working machine:
-bash: freetype-config: command not found


So, two problems:
1) not fully static
2) not able to build on ’some’ machines

What am I missing?
Logfiles and script are attached

Bouke

www.VideoToolShed.com
van Oldenbarneveltstraat 33
6512 AS  Nijmegen
+31 6 21817248
To send files, go here:
https://videotoolshed.wetransfer.com/
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Decklink timestamp_align, what should it do?

2021-05-03 Thread Bouke

> On 2 May 2021, at 18:58, Marton Balint  wrote:
> 
> 
> 
> On Sun, 2 May 2021, Bouke wrote:
> 
>> 
>> 
>>> On 2 May 2021, at 13:22, Bouke  wrote:
>>> Setting a timestamp_align of 6 seconds results in a start delay of just 6 
>>> seconds…
>> 
>> 
>> Oops, I ment, Setting a timestamp_align of TEN seconds results in a start 
>> delay of just 6 seconds…
> 
> Well of course, since it waits only until system clock reaches a 10 second 
> boundary - :00 :10 :20 :30 :40 or :50.
> 
> Maybe I should have wrote this: it waits till
> UNIX_TIMESTAMP() modulo timestamp_align becomes 0.
> where unix timestamp is numer of seconds since 1970.
> 
> Hope it finally makes sense now.

YES!

My Python (pseudso) code now:
_add = 1 - (time.time() % 1)
_tc += add
args extend([‘-timestamp_align’, ‘1'])
args.extend([‘-timecode’, tc])

THANKS!

Bouke

> 
> Regards,
> Marton
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Decklink timestamp_align, what should it do?

2021-05-02 Thread Bouke


> On 2 May 2021, at 13:22, Bouke  wrote:
> 
> Setting a timestamp_align of 6 seconds results in a start delay of just 6 
> seconds…


Oops, I ment, 
Setting a timestamp_align of TEN seconds results in a start delay of just 6 
seconds…
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Decklink timestamp_align, what should it do?

2021-05-02 Thread Bouke

> On 2 May 2021, at 13:10, Nicolas George  wrote:
> 
> Bouke (12021-05-02):
>> Ok, but what is ' UTC modulo’ ?
> 
> An incomplete formula. Like "UTC minus": UTC minus... what? UTC
> modulo... "UTC modulo timestamp_align", as a whole.


Well yes, I do know a little math.

BUT, it does not work.
Setting a timestamp_align of 6 seconds results in a start delay of just 6 
seconds…
I’ll continue testing, but for the concept:

What I need is to compensate for the time it takes FFmpeg to start.
So, what I really need is:
’start capture if time > x seconds since epoch’ (or something like 
that.)

Otherwise, what’s the use? What am I missing here?

Thx,
Bouke



> 
> Then read:
> 
> https://en.wikipedia.org/wiki/Modulo
> 
> Regards,
> 
> -- 
>  Nicolas George
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Decklink timestamp_align, what should it do?

2021-05-02 Thread Bouke

> On 2 May 2021, at 11:02, Marton Balint  wrote:
> 
> 
> 
> On Sun, 2 May 2021, Bouke wrote:
> 
>> From the manual:
>> 'timestamp_align
>> Capture start time alignment in seconds. If set to nonzero, input frames are 
>> dropped till the system timestamp aligns with configured value
>> 
>> Ok, when I put -timestamp_align in my command, it  does wait ‘a bit’ before 
>> starting capture.
>> That’s what I’m after, but i have no clue how long it waits. It’s not a 
>> ‘wait X seconds’ for sure.
> 
> It waits until UTC modulo timestamp_align becomes 0. So for 60 it waits until 
> a full minute boundary is reached.

Ok, but what is ' UTC modulo’ ?
If i enter 0, it starts capturing immediately, higher values do give ‘a’ delay, 
but it’s not predictable at all.
(It’s off by a random value, up to 30% difference from what I expect…)

Bouke


> 
> Regards,
> Marton
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


[FFmpeg-user] Decklink timestamp_align, what should it do?

2021-05-02 Thread Bouke
From the manual:
'timestamp_align
Capture start time alignment in seconds. If set to nonzero, input frames are 
dropped till the system timestamp aligns with configured value

Ok, when I put -timestamp_align in my command, it  does wait ‘a bit’ before 
starting capture.
That’s what I’m after, but i have no clue how long it waits. It’s not a ‘wait X 
seconds’ for sure.

So my question, what is 'the system timestamp’? How do I get it so I can enter 
the correct value?

thx

Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Media Express vs FFmpeg CPU use

2021-04-30 Thread Bouke

> On 29 Apr 2021, at 08:37, Carl Zwanzig  wrote:
> 
> On 4/28/2021 11:15 PM, Bouke wrote:
>>> Can you capture into something else and then transcode?
>> Nah, the whole idea is to be done as fast as possible, so not to transcode…
> 
> You _have_ to encode (not transcode), the SDI input is raw uncompressed 
> frames ("rawvideo (UYVY / 0x59565955)"); capturing them takes no time at all, 
> just a lot of storage space if you write to disk.

Sorry, my bad, I’ve used transcode as if it were encode...

> 
> This may be a simple case that one encoder is better than another.

Yes, definitly!
I just want to do ‘all’ in one pass.

Bouke

> 
> z!
> ___

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Media Express vs FFmpeg CPU use

2021-04-29 Thread Bouke

> On 28 Apr 2021, at 21:27, Carl Zwanzig  wrote:
> 
> On 4/28/2021 3:03 AM, Bouke wrote:
>> Trying to capture decklink input to ProRes.
>> FFmpeg is VERY cpu hungry (230 % on my sytem in the example below, 
>> increasing when upping the quality of Prores)
>> Media Express / VTEncoderXPCservice use just half the CPU.
> 
> My assumption is that the BMD code is simply more optimized for the tasks 
> it's doing, and probably using a licensed encoder. Otherwise, are all the 
> parameters the same between tests?

I ’think’ so, but even when not, what could I do to make FFmpeg less CPU hungry?

> I was looking specifically at pix_fmt (might need to move that earlier in the 
> cmd line). (I'd experiment myself with this but have a production on Saturday 
> and a lot to do before that.)

Tried it, does not make any difference. Strangely, today’s test used 158% where 
yesterday it was 230%. Machine has not been restarted…

> 
>> (Eventually I want to do multiple streams on a single machine.)
> 
> Do you need prores output?

Client request, I would choose MpegII...

> Can you capture into something else and then transcode?

Nah, the whole idea is to be done as fast as possible, so not to transcode…

Thanks!

Bouke

> 
> Later,
> 
> z!
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


[FFmpeg-user] Media Express vs FFmpeg CPU use

2021-04-28 Thread Bouke
Trying to capture decklink input to ProRes.
FFmpeg is VERY cpu hungry (230 % on my sytem in the example below, increasing 
when upping the quality of Prores)
Media Express / VTEncoderXPCservice use just half the CPU.

Is there a way to speed up FFmpeg in a similar way?
(Eventually I want to do multiple streams on a single machine.)

Bouke

bouke@Boukes-iMac ~ % /Applications/ffmpeg -hide_banner -f decklink -raw_format 
auto -format_code Hi50 -channels 2 -timecode_format rp188vitc -video_input sdi 
-audio_input embedded -audio_depth 16 -threads 0 -rtbufsize 1024000k -i 
"UltraStudio Mini Recorder" -c:v prores -profile:v 1 -vendor ap10 -pix_fmt 
yuv422p10le -c:a copy /Volumes/Data/test.mov -y 
[decklink @ 0x7fe924019200] Found Decklink mode 1920 x 1080 with rate 25.00(i)
Guessed Channel Layout for Input Stream #0.0 : stereo
Input #0, decklink, from 'UltraStudio Mini Recorder':
  Duration: N/A, start: 0.00, bitrate: 830976 kb/s
Stream #0:0: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s
Stream #0:1: Video: rawvideo (UYVY / 0x59565955), uyvy422(top first), 
1920x1080, 829440 kb/s, 25 tbr, 1000k tbn, 1000k tbc
Metadata:
  timecode: 21:59:13:11
Stream mapping:
  Stream #0:1 -> #0:0 (rawvideo (native) -> prores (native))
  Stream #0:0 -> #0:1 (copy)
Press [q] to stop, [?] for help
Output #0, mov, to '/Volumes/Data/test.mov':
  Metadata:
encoder : Lavf58.65.101
Stream #0:0: Video: prores (apcs / 0x73637061), yuv422p10le(tv, top coded 
first (swapped)), 1920x1080, q=2-31, 200 kb/s, 0.04 fps, 12800 tbn
Metadata:
  timecode: 21:59:13:11
  encoder : Lavc58.117.101 prores
Stream #0:1: Audio: pcm_s16le (sowt / 0x74776F73), 48000 Hz, stereo, s16, 
1536 kb/s
frame=1 fps=0.0 q=0.0 size=   0kB time=00:00:00.00 bitrate=N/A 
speed=N/Aframe=   15 fps=0.0 q=-0.0 size=4096kB time=00:00:00.56 
bitrate=59919.2kbitsframe=   28 fps= 27 q=-0.0 size=9216kB time=00:00:01.08 
bitrate=69905.4kbitsframe=   41 fps= 26 q=-0.0 size=   14336kB time=00:00:01.60 
bitrate=73400.5kbitsframe=   54 fps= 26 q=-0.0 size=   19200kB time=00:00:02.12 
bitrate=74191.8kbitsframe=   67 fps= 26 q=-0.0 size=   24320kB time=00:00:02.64 
bitrate=75465.8kbitsframe=   80 fps= 26 q=-0.0 size=   29440kB time=00:00:03.16 
bitrate=76320.5kbitsframe=   93 fps= 26 q=-0.0 size=   34304kB time=00:00:03.68 
bitrate=76363.8kbitsframe=  106 fps= 26 q=-0.0 size=   39424kB time=00:00:04.20 
bitrate=76895.6kbitsframe=  119 fps= 25 q=-0.0 size=   44544kB time=00:00:04.72 
bitrate=77310.3kbitsframe=  132 fps= 25 q=-0.0 size=   49664kB time=00:00:05.24 
bitrate=77642.7kbitsframe=  145 fps= 25 q=-0.0 size=   54528kB time=00:00:05.76 
bitrate=77551.0kbitsframe=  158 fps= 25 q=-0.0 size=   596
 48kB time=00:00:06.28 bitrate=77808.4kbitsframe=  164 fps= 25 q=-0.0 Lsize=   
63700kB time=00:00:06.52 bitrate=80034.4kbits/s speed=0.998x
video:62474kB audio:1222kB subtitle:0kB other streams:0kB global headers:0kB 
muxing overhead: 0.005828%

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] drawtext timecode from metadata

2021-04-24 Thread Bouke
Hmm,
I’m pretty sure I saw a reply from Gyan, stating ’not possible, how are you 
capturing, i’ll look into something’

few seconds later that was gone. (Or I really need to up my medicine…)

Anyways, I’m dong a BM capture, with TC coming in embedded over SDI.
(I must admit I have not yet tested it with BM capture, just with a local file.

The TC as metadata in a Qt atom works just fine.

Bouke


> On 24 Apr 2021, at 13:26, Bouke  wrote:
> 
> trying to capture and burn in TC at the same time.
> Burn in TC works if I specify the start TC, but I can’t probe and then 
> record, as that takes time so the TC will be off.
> So I’m hoping to set the drawtext filter on the fly, I tried:
> drawtext=timecode=%{metadata\\\:timecode}:
> 
> -filter_complex 
> "[0:0]drawtext=timecode=%{metadata\\\:timecode}:fontfile='/Volumes/Data/fonts/courbd.ttf':r=25:x=(w-tw)
>  - (w * 0.02): y=h-(2*lh):fontsize=54.0:fontcolor=white” 
> 
> This does not work, gives me:
> [Parsed_drawtext_0 @ 0x7ff9fbe0cb40] Unable to parse timecode, syntax: 
> hh:mm:ss[:;.]ff
> 
> Is there a way to do this?
> 
> thx,
> Bouke
> 
> 
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


[FFmpeg-user] drawtext timecode from metadata

2021-04-24 Thread Bouke
trying to capture and burn in TC at the same time.
Burn in TC works if I specify the start TC, but I can’t probe and then record, 
as that takes time so the TC will be off.
So I’m hoping to set the drawtext filter on the fly, I tried:
drawtext=timecode=%{metadata\\\:timecode}:

-filter_complex 
"[0:0]drawtext=timecode=%{metadata\\\:timecode}:fontfile='/Volumes/Data/fonts/courbd.ttf':r=25:x=(w-tw)
 - (w * 0.02): y=h-(2*lh):fontsize=54.0:fontcolor=white” 

This does not work, gives me:
[Parsed_drawtext_0 @ 0x7ff9fbe0cb40] Unable to parse timecode, syntax: 
hh:mm:ss[:;.]ff

Is there a way to do this?

thx,
Bouke


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


Re: [FFmpeg-user] Local latency with FFplay

2021-04-23 Thread Bouke

> On 22 Apr 2021, at 18:05, Carl Zwanzig  wrote:
> 
> On 4/22/2021 12:43 AM, Bouke wrote:
>> Trying to view a stream while recording. (That 'sorta kinda' works with a
>> tee and udp streaming, but has a horrible delay.)
>> Ideal would be to keep FFplay open, and start / stop FFmpeg for
>> recording, or just viewing the incoming signal.
> The BMD recorder app does a rather good job of that

You mean Media Express? Yes, that has just a little latency, but is too limited 
for my purpose.

> 
>> This results in a latency of 6 seconds (Ok, no local file, but with it
>> and a tee it’s the same)
> Have you tried
> different encodings?

Yes, but that’s no issue, the encoding is fast enough

> tee-ing raw frames into both a viewer and a separate encoder?

How would I go about that? And, how should that help ’not’ filling the buffer 
that FFplay reads out, introducing the latency?

> IIRC the ffmpeg decklink code has a few frames of latency, but not more than 
> that. OTOH, how many does the x264 encoder have?
Very little, that’s not the issue

> (I'll assume the encoder can keep up with the incoming frames.) At least for 
> the viewing part, you shouldn't use -any- encoding since those same frames 
> will then have to be decoded for display. (If you're using ffplay to monitor 
> the recording -after- encoding, they you have to live with the encoder's 
> latency.)

Just cursed and googled more, -fflags nobuffer solves it!

Thanks for putting me on the right track

Bouke


> Later,
> 
> z!
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


[FFmpeg-user] Local latency with FFplay

2021-04-22 Thread Bouke
Trying to view a stream while recording. (That 'sorta kinda' works with a tee 
and udp streaming, but has a horrible delay.)
eg:
I start FFplay:
ffplay udp://127.0.0.1:1230 -x 320 -y 240 -left 100 -top 100 -alwaysontop

Then:
ffmpeg -f decklink -i UltraStudio Mini Recorder -raw_format auto -format_code 
Hi50 -channels 2 -timecode_format none -video_input sdi -audio_input embedded 
-audio_depth 16 -vcodec libx264 -preset ultrafast -pix_fmt yuv422p -tune 
zerolatency -an -s 320x180 -aspect 16:9 -map 0:v -f flv udp://127.0.0.1:1230 

This results in a latency of 6 seconds (Ok, no local file, but with it and a 
tee it’s the same)

So, back to the drawing board and trying something simple, piping directly from 
FFmpeg to FFplay.
ffmpeg -i yadda - | ffplay -
this takes 2 up to 6 seconds before the FFplay window is shown (Depending on 
the phase of the moon divided by the temperature or something, I am clueless 
why there is a difference), and the video is still horrible delayed (app by the 
same time as it took FFplay to start / show the video). If I add a -ss 2 to 
FFplay, there is just a couple frames delay, but the startup time of FFplay is 
doubled.
Funny enough, without -ss 2 the video could be 6 seconds late, with -ss 2 it's 
very close. (good enough for rock 'n roll, except for the 12 seconds start 
time...)


Any pointers?
Ideal would be to keep FFplay open, and start / stop FFmpeg for recording, or 
just viewing the incoming signal. 

thx,
Bouke



bouke@Boukes-iMac ~ % /usr/local/bin/ffmpeg -f decklink -i "UltraStudio Mini 
Recorder" -format_code Hi50 -raw_format auto -s 320x180 -aspect 16:9  -map 0:v 
-an -vcodec libx264 -preset ultrafast -f flv - | /usr/local/bin/ffplay -
 
ffplay version git-2021-03-31-b3e9a84 Copyright (c) 2003-2021 the FFmpeg 
developers
  built with Apple clang version 12.0.0 (clang-1200.0.32.29)
  configuration: --enable-videotoolbox --enable-nonfree --enable-gpl 
--enable-lv2 --enable-openssl --enable-libsvtav1 --enable-libx264 
--enable-libx265 --enable-libvpx --enable-libxvid --enable-libvidstab 
--enable-libaom --enable-libopencore_amrnb --enable-libopencore_amrwb 
--enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libtheora 
--enable-libfdk-aac --enable-libwebp --enable-libsrt --disable-debug 
--disable-doc --disable-shared --enable-pthreads --enable-static --enable-small 
--enable-version3 --enable-decklink 
--extra-cflags='-I/Users/bouke/ffmpeg-build-script/workspace/include 
-I/Users/bouke/ffmpeg-build-script/include' --extra-ldexeflags= 
--extra-ldflags='-L/Users/bouke/ffmpeg-build-script/workspace/lib 
-L/Users/bouke/ffmpeg-build-script/include' --extra-libs='-ldl -lpthread -lm 
-lz' --pkgconfigdir=/Users/bouke/ffmpeg-build-script/workspace/lib/pkgconfig 
--pkg-config-flags=--static --prefix=/Users/bouke/ffmpeg-build-script/workspace
ffmpeg version git-2021-03-31-b3e9a84 Copyright (c) 2000-2021 the FFmpeg 
developers
  built with Apple clang version 12.0.0 (clang-1200.0.32.29)
  configuration: --enable-videotoolbox --enable-nonfree --enable-gpl 
--enable-lv2 --enable-openssl --enable-libsvtav1 --enable-libx264 
--enable-libx265 --enable-libvpx --enable-libxvid --enable-libvidstab 
--enable-libaom --enable-libopencore_amrnb --enable-libopencore_amrwb 
--enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libtheora 
--enable-libfdk-aac --enable-libwebp --enable-libsrt --disable-debug 
--disable-doc --disable-shared --enable-pthreads --enable-static --enable-small 
--enable-version3 --enable-decklink 
--extra-cflags='-I/Users/bouke/ffmpeg-build-script/workspace/include 
-I/Users/bouke/ffmpeg-build-script/include' --extra-ldexeflags= 
--extra-ldflags='-L/Users/bouke/ffmpeg-build-script/workspace/lib 
-L/Users/bouke/ffmpeg-build-script/include' --extra-libs='-ldl -lpthread -lm 
-lz' --pkgconfigdir=/Users/bouke/ffmpeg-build-script/workspace/lib/pkgconfig 
--pkg-config-flags=--static --prefix=/Users/bouke/ffmpeg-build-script/workspace
  libavutil  56. 63.101 / 56. 63.101
  libavutil  56. 63.101 / 56. 63.101
  libavcodec 58.117.101 / 58.117.101
  libavformat58. 65.101 / 58. 65.101
  libavcodec 58.117.101 / 58.117.101
  libavdevice58. 11.103 / 58. 11.103
  libavformat58. 65.101 / 58. 65.101
  libavfilter 7. 96.100 /  7. 96.100
  libavdevice58. 11.103 / 58. 11.103
  libswscale  5.  8.100 /  5.  8.100
  libavfilter 7. 96.100 /  7. 96.100
  libswresample   3.  8.100 /  3.  8.100
  libswscale  5.  8.100 /  5.  8.100
  libpostproc55.  8.100 / 55.  8.100
  libswresample   3.  8.100 /  3.  8.100
  libpostproc55.  8.100 / 55.  8.100
[decklink @ 0x7f87ec80f000] Autodetected the input mode
[decklink @ 0x7f87ec80f000] Found Decklink mode 1920 x 1080 with rate 25.00(i)
Guessed Channel Layout for Input Stream #0.0 : stereo0B f=0/0   
Input #0, decklink, from 'UltraStudio Mini Recorder':
  Duration: N/A, start: 0.00, bitrate: 830976 kb/s
Stream #0:0: Audio: pcm_s16le, 48000 Hz, stereo,

[FFmpeg-user] OT, Noise, am I'm loosing it? (rant)

2021-02-04 Thread Bouke
Recently watched ‘Win it all’ on Netflix.
(Ok, you can flame me for bad taste, but that would be beside the point.)

Now, in this flick, a ‘Netflix original’, noise on close to every interior shot 
is beyond reasonable.
Now, Netflix has very high demands on delivery.
How could this happen? Why did Netflix accept this? (And this is far from the 
only noisy shot I see in modern movies nowadays….)
This movie was shot some 5 years ago. Even back then there were cams that could 
shoot with candle light if needed, without excessive noise!

I guess this is due to shooting LUT by someone who is totally clueless. (Note, 
my guess is that even without additional lighting the shots ‘could’ have turned 
out with way less noise.)
Having said that, I have never ever seen a LUT shot that turned out better than 
shooting decent in the first place, but my editorial work has productions with 
a total budget of 300K max.
I know there is a place in this world where shooting LUT can indeed help, my 
guess is that those events are 0.1 % of the cases where LUT is in fact used.

If the noise would be an artistic decision I could understand it, but that 
seems not the case IMHO. Nor was it out of need. (I have some experience, I 
have restored old movies, where the only available stock needed to be 
overcranked, there is a valid reason.)

What I do know that the added data for compression for Netflix will burn half a 
rain forrest, consuming way more energy / cost than having had the set lighted 
properly, or, again, pick a decent camera and do NOT shoot lut, or do it 
properly at least.

What am I missing, or am I right and should some people get their butts kicked?


Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] co64 atom in QT / Mp4, and compatibility with Premiere _ FIXED

2021-02-01 Thread Bouke


> On 31 Jan 2021, at 13:06, Bouke  wrote:
> 
> This is not an FFmpeg question perse, but I hope someone knows more about 
> atoms than I do.
> 
> Similar to the previous thread, I am modifiying clips ‘in place / 
> destructive’. (For .Mp4 / .mov files)
> 
> For that I re-write or re-order the moov atom to needs.
> That all seems to work fine, if files are < 4 gig.
> On larger files, when I want to change TC, I add an mdat atom with the TC 
> converted to frame number.
> In the TC track (That I rip from a dummy FFmpeg short transcode), I change 
> the pointer in the TC tracks stco atom to the newly added mdat location.
> So far so good.
> 
> Now, when the new mdat pos goes over 4 gig, I add an co64 atom so I have 8 
> bytes to set it, and I  change the whole shebang to reflect the new length of 
> all atoms in the structure.
> This also ‘sorta kinda’ works, as QT player displays the correct TC.
> 
> BUT, Adobe Premiere does NOT like this, it gives me another TC that I can’t 
> place for the life of me…
> If I omit the co64 atom and find ‘some’ spot (either inside an mdat atom or 
> not), it works, but it seems Premiere totally ignores the co64 info.

For the archives:
Fixed. trouble was that Premiere / Resolve expect the co64 atom INSTEAD of 
stco, rather than after to overwrite previous value.

Bouke

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-user] co64 atom in QT / Mp4, and compatibility with Premiere

2021-01-31 Thread Bouke
This is not an FFmpeg question perse, but I hope someone knows more about atoms 
than I do.

Similar to the previous thread, I am modifiying clips ‘in place / destructive’. 
(For .Mp4 / .mov files)

For that I re-write or re-order the moov atom to needs.
That all seems to work fine, if files are < 4 gig.
On larger files, when I want to change TC, I add an mdat atom with the TC 
converted to frame number.
In the TC track (That I rip from a dummy FFmpeg short transcode), I change the 
pointer in the TC tracks stco atom to the newly added mdat location.
So far so good.

Now, when the new mdat pos goes over 4 gig, I add an co64 atom so I have 8 
bytes to set it, and I  change the whole shebang to reflect the new length of 
all atoms in the structure.
This also ‘sorta kinda’ works, as QT player displays the correct TC.

BUT, Adobe Premiere does NOT like this, it gives me another TC that I can’t 
place for the life of me…
If I omit the co64 atom and find ‘some’ spot (either inside an mdat atom or 
not), it works, but it seems Premiere totally ignores the co64 info.

Can anyone shed a light on this?


Thx,

Bouke
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

  1   2   >