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 specify

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

2023-12-20 Thread Erik Dobberkau
> I understand that RDD-9 is necessary, but even after reading the article, I > don't know where RDD-9 is. > RDD 9 is Sony's Registered Disclosure Document for the XDCAM file format [1]. You can download the document from IEEExplore [2] if you have an account (e.g. via a SMPTE membership, probably

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

2023-12-19 Thread 大石脩斗
@Eril Thank you for answering I understand that RDD-9 is necessary, but even after reading the article, I don't know where RDD-9 is. I couldn't fix it myself. Please tell me more details. 2023年12月20日(水) 1:16 Erik Dobberkau : > > > > Trust me, this command (besides audio parsing, depending on s

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

2023-12-19 Thread 大石脩斗
@ Bouke Thank you for answering. It didn't work. I tried referring to your command, but the situation did not change. Please let me know if there are any other improvements. Also, it seems that the -map_channel option will be removed. If you know an alternative pan filter command, please let me kn

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

2023-12-19 Thread Nicolas Gaullier
>> 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://w

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-a

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

2023-12-19 Thread Erik Dobberkau
> > @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-fram

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

2023-12-19 Thread Erik Dobberkau
> > 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 (and its follow-up m

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 lav

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

2023-12-18 Thread 大石脩斗
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