Re: [Cin] UPD: Re: DNxHR presets
В сообщении от Thursday 12 November 2020 23:53:40 MatN via Cin написал(а): > On Thu, 12 Nov 2020 21:41:20 +0100 (CET), MatN via Cin wrote: > > >On Wed, 11 Nov 2020 23:47:17 +0100, Andrea paz via Cin wrote: > > > >>I think you need to copy Andrew's presets to ".../bin/ffmpeg/video" > >>after compilation. At least that's what I do. If you want to do it > >>before compiling then you have to copy the presets to > >>".../ffmpeg/video", which is in the main directory, without entering > >>"/bin". But I don't understand the code at all, sorry. > >>In this way DNxHR.mov. are also displayed. To me only the 420 appears > >>without other options. Since the 420 is not supported by DNxHR then > >>the render fails. For Andrew it works fine. > > > >@Andrea, > > > >Ok, got it. The .mov files need to be in the cinelerra5.1/ffmpeg/video > >directory, and the "make install" copies that ffmpeg directory to the bin > >directory (a "make clean" removes that and some other subdirectories of bin). > > > >Now if in the render window I choose file format ffmpeg.mov, then open the > >video options, I get the 7 extra options DnxHR options in the 'compression" > >dropdown. I presume you get this far too? > >Then if I select e.g. DNxHR_HQ, the Pixels dropdown has extra entries like > >yuv422p . Do you get this? > > I can render a file with DNxHR_HQ pixel yuv422p fine, but it expands > enormously. The source Jellyfish .MP4 file was 35 MB, the .mov file 787 Mb. > VLC's codec info on that file shows indeed dnxhr yuv422p . > > So what is the advantage of these DNxHR formats? According to this: https://www.mainconcept.com/fileadmin/user_upload/datasheets/DNxHD-DNxHR_SDK_DATASHEET.pdf The MainConcept VC-3 SDK Packages for Avid DNxHD and Avid DNxHR are software-only solutions which enable application developers to integrate with production tools like Avid Media Composer and Avid Interplay storage solutions or cameras which store media in either of these formats. Avid DNxHD and DNxHR are based on the SMPTE 2019-2006 (VC-3) specification. - so, basically standard codec for exchange with Big Boys (AVID, etc) Better to be put on fast storage. Try to play it back/forward, framestep, fastforward, and randomly hit various places on relatively long timeline, notice if there any difference in responsiveness with h264. > > MatN > > > > -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] UPD: Re: DNxHR presets
The advantage of using mezzanine codecs (also called Intermediate codecs) is that it preserves all the information in the original file throughout the editing process. In addition, they are uncompressed codecs and therefore not stressful for the CPU. They are indispensable for high level works of Color Correction; denoise; mask and Chroma Key, where the compression artifacts do not allow good results. For only editing they are not necessary, and in fact proxies are often used. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] UPD: Re: DNxHR presets
No, I only have yuv420 available (which you shouldn't even have). So it's my problem, since it works normally for you and Andrew. @Andrew You can propose to integrate your presets for the next release. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] UPD: Re: DNxHR presets
On Thu, 12 Nov 2020 21:41:20 +0100 (CET), MatN via Cin wrote: >On Wed, 11 Nov 2020 23:47:17 +0100, Andrea paz via Cin wrote: > >>I think you need to copy Andrew's presets to ".../bin/ffmpeg/video" >>after compilation. At least that's what I do. If you want to do it >>before compiling then you have to copy the presets to >>".../ffmpeg/video", which is in the main directory, without entering >>"/bin". But I don't understand the code at all, sorry. >>In this way DNxHR.mov. are also displayed. To me only the 420 appears >>without other options. Since the 420 is not supported by DNxHR then >>the render fails. For Andrew it works fine. > >@Andrea, > >Ok, got it. The .mov files need to be in the cinelerra5.1/ffmpeg/video >directory, and the "make install" copies that ffmpeg directory to the bin >directory (a "make clean" removes that and some other subdirectories of bin). > >Now if in the render window I choose file format ffmpeg.mov, then open the >video options, I get the 7 extra options DnxHR options in the 'compression" >dropdown. I presume you get this far too? >Then if I select e.g. DNxHR_HQ, the Pixels dropdown has extra entries like >yuv422p . Do you get this? I can render a file with DNxHR_HQ pixel yuv422p fine, but it expands enormously. The source Jellyfish .MP4 file was 35 MB, the .mov file 787 Mb. VLC's codec info on that file shows indeed dnxhr yuv422p . So what is the advantage of these DNxHR formats? MatN -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] UPD: Re: DNxHR presets
On Wed, 11 Nov 2020 23:47:17 +0100, Andrea paz via Cin wrote: >I think you need to copy Andrew's presets to ".../bin/ffmpeg/video" >after compilation. At least that's what I do. If you want to do it >before compiling then you have to copy the presets to >".../ffmpeg/video", which is in the main directory, without entering >"/bin". But I don't understand the code at all, sorry. >In this way DNxHR.mov. are also displayed. To me only the 420 appears >without other options. Since the 420 is not supported by DNxHR then >the render fails. For Andrew it works fine. @Andrea, Ok, got it. The .mov files need to be in the cinelerra5.1/ffmpeg/video directory, and the "make install" copies that ffmpeg directory to the bin directory (a "make clean" removes that and some other subdirectories of bin). Now if in the render window I choose file format ffmpeg.mov, then open the video options, I get the 7 extra options DnxHR options in the 'compression" dropdown. I presume you get this far too? Then if I select e.g. DNxHR_HQ, the Pixels dropdown has extra entries like yuv422p . Do you get this? MatN -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] UPD: Re: DNxHR presets
I think you need to copy Andrew's presets to ".../bin/ffmpeg/video" after compilation. At least that's what I do. If you want to do it before compiling then you have to copy the presets to ".../ffmpeg/video", which is in the main directory, without entering "/bin". But I don't understand the code at all, sorry. In this way DNxHR.mov. are also displayed. To me only the 420 appears without other options. Since the 420 is not supported by DNxHR then the render fails. For Andrew it works fine. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] UPD: Re: DNxHR presets
On Wed, 11 Nov 2020 15:03:46 +0100, Andrea paz via Cin wrote: >> >> May be some pathes are too long? >> Where exactly you put those profile files? >> > >/home/paz/cinelerra5/cinelerra-5.1/bin/ffmpeg/video/DNxHR_444.mov > >about 70 characters. > >@MatN >can you try to put Andrew's presets in your CinGG to see if they work for you? >The path should be: > >/home/USER/cinelerra5/cinelerra-5.1/bin/ffmpeg/video/ I'm not sure what the exact procedure is. I did: - fresh pull from git. - "sudo ./bld.sh" to make sure it builds ok, then "sudo make clean" - move Andrew's .mov files in the cinelerra-5.1/bin/ffmpeg/video/ directory. - As sudo I did ./autogen.sh ./configure --with-single-user make 2>&1 | tee log make install - in the bin directory, /cin. load a jellyfish h264 mp4 file - Render menu, select file format ffmpeg.mov, then clicked the tool for video presets. There I see compression mov.mov, and for pixels only the option yuv420 . I guess I should see more pixel options? Or what? MatN -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] UPD: Re: DNxHR presets
В сообщении от Wednesday 11 November 2020 17:03:46 Andrea paz via Cin
написал(а):
> >
> > May be some pathes are too long?
> > Where exactly you put those profile files?
> >
>
> /home/paz/cinelerra5/cinelerra-5.1/bin/ffmpeg/video/DNxHR_444.mov
>
> about 70 characters.
Just compiled Cin with just one switch:
./configure --with-single-use
it worked with some local hacks (/usr/X11R7 for X libs, disabling swscale
integration in x264 snapshot)
I can load my profile to
/dev/shm/cinelerra/cinelerra-5.1$ ls bin/ffmpeg/video/
DNxHR_HQX.mov
and it show up correctly and let me render.
Does your build enable vdpau/vaapi? As far as I can see those options loaded in
https://git.cinelerra-gg.org/git/?p=goodguy/cinelerra.git;a=blob;f=cinelerra-5.1/cinelerra/ffmpeg.C;h=97b6698acbb2ffc342f93049dbd54537d0a39235;hb=HEAD
2081
2082 void FFMPEG::scan_video_options(Asset *asset, EDL *edl)
2083 {
2084 char cin_pix_fmt[BCSTRLEN];
2085 int cin_fmt = AV_PIX_FMT_NONE;
2086 const char *options = asset->ff_video_options;
2087 if( !get_ff_option("cin_pix_fmt", options, cin_pix_fmt) )
2088 cin_fmt = (int)av_get_pix_fmt(cin_pix_fmt);
2089 if( cin_fmt < 0 ) {
2090 char video_codec[BCSTRLEN]; video_codec[0] = 0;
2091 AVCodec *av_codec = !get_codec(video_codec, "video",
asset->vcodec) ?
2092 avcodec_find_encoder_by_name(video_codec) : 0;
2093 if( av_codec && av_codec->pix_fmts ) {
2094 if( 0 && edl ) { // frequently picks a bad answer
2095 int color_model =
edl->session->color_model;
2096 int max_bits =
BC_CModels::calculate_pixelsize(color_model) * 8;
2097 max_bits /=
BC_CModels::components(color_model);
2098 cin_fmt =
avcodec_find_best_pix_fmt_of_list(av_codec->pix_fmts,
2099 (BC_CModels::is_yuv(color_model) ?
2100 (max_bits > 8 ?
AV_PIX_FMT_AYUV64LE : AV_PIX_FMT_YUV444P) :
2101 (max_bits > 8 ?
AV_PIX_FMT_RGB48LE : AV_PIX_FMT_RGB24)), 0, 0);
2102 }
2103 else
2104 cin_fmt = av_codec->pix_fmts[0];
2105 }
2106 }
2107 if( cin_fmt < 0 ) cin_fmt = AV_PIX_FMT_YUV420P;
search for 'cin_pix_fmt'
so for some reason it fails to find best format via
avcodec_find_best_pix_fmt_of_list ?
Also, I tried with default RGBA-8 colormodel . may be it fails with
YUV/RGBA-float?
no, seems to work too
You can try and add printf("doing X \n"); in this function and see that branch
it takes :} and also print out exact value of cin_fmt
printf("cin_fmt= %i \n", cin_fmt);
something like this ...
>
> @MatN
> can you try to put Andrew's presets in your CinGG to see if they work for you?
> The path should be:
>
> /home/USER/cinelerra5/cinelerra-5.1/bin/ffmpeg/video/
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] UPD: Re: DNxHR presets
> > May be some pathes are too long? > Where exactly you put those profile files? > /home/paz/cinelerra5/cinelerra-5.1/bin/ffmpeg/video/DNxHR_444.mov about 70 characters. @MatN can you try to put Andrew's presets in your CinGG to see if they work for you? The path should be: /home/USER/cinelerra5/cinelerra-5.1/bin/ffmpeg/video/ -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] UPD: Re: DNxHR presets
В сообщении от Wednesday 11 November 2020 13:28:21 Andrea paz via Cin написал(а): > 1- I compiled from root, but the result doesn't change: your presets > don't work in my CinGG; it only offers the yuv420p option which, not > being supported, produces error. > > 2- I compiled from root with the ./build.sh provided by GG but the > result is the same as point 1- > > 3- I compiled with ffmpeg-git --> compile error yeah, I removed bigger patch (it basically adds fixes for blu-ray creation - I have no such device): mv thirdparty/src/ffmpeg.git.patch2 thirdparty/src/_ffmpeg.git.patch2 this way it really not picked up by build. > > The trouble is that I compile with the copy and paste, without knowing > what I do. > The steps I use are: > > $ git clone --depth 1 > "git://git.cinelerra-gg.org/goodguy/cinelerra.git" cinelerra5 > > $ cd /home/paz/cinelerra5/cinelerra-5.1 > > $ ./autogen.sh > > $ ./configure --without-oss --with-single-user --with-booby > --with-opencv=sta,tar=http://cinelerra-gg.org/download/opencv/opencv-20200306.tgz Most bigger difference is "--with-single-user", as far as I can see... I do system-build May be some pathes are too long? Where exactly you put those profile files? /home/paz/cinelerra5/cinelerra-5.1/bin something ? I'll try --single-user somemoment later. > > $ make 2>&1 | tee /tmp/cin5.log && make install > > All this without being Root. > > Do you think I'm wrong? Should I try your ./configure? (but most of > the strings I don't understand them!) -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] UPD: Re: DNxHR presets
Hi Andrea, I always do "sudo ./bld.sh" in the cinelerra5.1 directory. And before a rebuild, "sudo make clean". I have not looked at what would be required to build it as normal user. MatN On Wed, 11 Nov 2020 11:28:21 +0100, Andrea paz via Cin wrote: >1- I compiled from root, but the result doesn't change: your presets >don't work in my CinGG; it only offers the yuv420p option which, not >being supported, produces error. > >2- I compiled from root with the ./build.sh provided by GG but the >result is the same as point 1- > >3- I compiled with ffmpeg-git --> compile error > >The trouble is that I compile with the copy and paste, without knowing >what I do. >The steps I use are: > >$ git clone --depth 1 >"git://git.cinelerra-gg.org/goodguy/cinelerra.git" cinelerra5 > >$ cd /home/paz/cinelerra5/cinelerra-5.1 > >$ ./autogen.sh > >$ ./configure --without-oss --with-single-user --with-booby >--with-opencv=sta,tar=http://cinelerra-gg.org/download/opencv/opencv-20200306.tgz > >$ make 2>&1 | tee /tmp/cin5.log && make install > >All this without being Root. > >Do you think I'm wrong? Should I try your ./configure? (but most of >the strings I don't understand them!) >-- >Cin mailing list >Cin@lists.cinelerra-gg.org >https://lists.cinelerra-gg.org/mailman/listinfo/cin > -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] UPD: Re: DNxHR presets
1- I compiled from root, but the result doesn't change: your presets don't work in my CinGG; it only offers the yuv420p option which, not being supported, produces error. 2- I compiled from root with the ./build.sh provided by GG but the result is the same as point 1- 3- I compiled with ffmpeg-git --> compile error The trouble is that I compile with the copy and paste, without knowing what I do. The steps I use are: $ git clone --depth 1 "git://git.cinelerra-gg.org/goodguy/cinelerra.git" cinelerra5 $ cd /home/paz/cinelerra5/cinelerra-5.1 $ ./autogen.sh $ ./configure --without-oss --with-single-user --with-booby --with-opencv=sta,tar=http://cinelerra-gg.org/download/opencv/opencv-20200306.tgz $ make 2>&1 | tee /tmp/cin5.log && make install All this without being Root. Do you think I'm wrong? Should I try your ./configure? (but most of the strings I don't understand them!) -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] UPD: Re: DNxHR presets
В сообщении от Wednesday 11 November 2020 00:35:34 Andrea paz via Cin
написал(а):
> > I also tested _lb and _sq presets.
> >
> > They also seems to accept only yuv422p
> >
> > Should I add some remark all those are for using with progressive video?
> > (in file itself, so user will see it in window, othervise reason why it
> > fails to render may be hidden, if user start Cin from menu)
>
> I do not know if it is right to continue this discussion. I think GG
> would like it!
>
> Yes, it is, HQ; SQ and LB are only 8-bit. 444 e HQX are 10-bit (in ffmpeg).
> See:
> https://avid.secure.force.com/pkb/articles/en_US/white_paper/DNxHR-Codec-Bandwidth-Specifications
> (second table).
>
> Good idea to add info on bit-depth and interlacing.
>
> My test:
> timeline 1920x1080; h264 and png, 20sec (612 frames).
>
> Your presets:
> LB; SQ; HQ; HQX and 444: the only pixel formats is yuv420p (not
> supported) --> Error rendering data.
>
> My preset:
> 444_yuv: render 13 sec; size 1.0 GB; Color space RGB (mediainfo)
> 444_gbr:18 sec; 1.0 GB; yuv""
> HQX_422_10: 10 sec: 536 MB; yuv""
> HQ_422_8: 07 sec; 535 MB; yuv""
> SQ_422_8: 07 sec; 354 MB; yuv""
> LB_422_8: 07 sec; 110 MB; yuv""
>
> Those shown are the only pixel formats that work for each preset.
> I don't know why my CinGG behaves wrong. I build it from git (not root).
Hm, probably build (configure) switches
EXTRA_LIBS=" -lOpenCL -ldav1d -lxvidcore -lass -lbluray -lsnappy" \
FFMPEG_EXTRA_CFG=" --enable-opencl --enable-frei0r --enable-libdav1d
--enable-libxvid --enable-libass --enable-libbluray --enable-libsnappy" \
CFLAGS="$SLKCFLAGS -D__STDC_CONSTANT_MACROS" \
CXXFLAGS="$SLKCFLAGS -D__STDC_CONSTANT_MACROS" \
LDFLAGS="-L/usr/X11R7/lib -ldl -L/usr/lib${LIBDIRSUFFIX}" \
./configure \
--prefix=/usr \
--with-git-ffmpeg=https://git.ffmpeg.org/ffmpeg.git \
--with-opencv=sta,tar=https://cinelerra-gg.org/download/opencv/opencv-20200306.tgz
\
--sysconfdir=/etc \
--localstatedir=/var \
--libdir=/usr/lib${LIBDIRSUFFIX} \
--with-ladspa-build \
--with-opus \
--with-nv \
--enable-opus \
--with-jobs=4 \
--with-booby \
--with-commercial \
--build=$ARCH-slackware-linux
on 32-bit userspace .
This is worrying - profiles working for me doesn't work for you :/
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] UPD: Re: DNxHR presets
> I also tested _lb and _sq presets. > > They also seems to accept only yuv422p > > Should I add some remark all those are for using with progressive video? > (in file itself, so user will see it in window, othervise reason why it fails > to render may be hidden, if user start Cin from menu) I do not know if it is right to continue this discussion. I think GG would like it! Yes, it is, HQ; SQ and LB are only 8-bit. 444 e HQX are 10-bit (in ffmpeg). See: https://avid.secure.force.com/pkb/articles/en_US/white_paper/DNxHR-Codec-Bandwidth-Specifications (second table). Good idea to add info on bit-depth and interlacing. My test: timeline 1920x1080; h264 and png, 20sec (612 frames). Your presets: LB; SQ; HQ; HQX and 444: the only pixel formats is yuv420p (not supported) --> Error rendering data. My preset: 444_yuv: render 13 sec; size 1.0 GB; Color space RGB (mediainfo) 444_gbr:18 sec; 1.0 GB; yuv"" HQX_422_10: 10 sec: 536 MB; yuv"" HQ_422_8: 07 sec; 535 MB; yuv"" SQ_422_8: 07 sec; 354 MB; yuv"" LB_422_8: 07 sec; 110 MB; yuv"" Those shown are the only pixel formats that work for each preset. I don't know why my CinGG behaves wrong. I build it from git (not root). -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] UPD: Re: DNxHR presets
I also tested _lb and _sq presets. They also seems to accept only yuv422p Should I add some remark all those are for using with progressive video? (in file itself, so user will see it in window, othervise reason why it fails to render may be hidden, if user start Cin from menu) -- Пересланное сообщение -- Тема: Re: [Cin] DNxHR presets Дата: Понедельник 09 ноября 2020 Отправитель: Andrew Randrianasulu Получатель: cin@lists.cinelerra-gg.org I tried to modify those presets so they show/select right pixel format, but for some reason file path: /dev/shm/DNxHR-yuv422-8bit.mov 435864233 bytes info: format: mov,mp4,m4a,3gp,3g2,mj2 1 video stream vid0 (0), id 0x63: video1 dnxhd 1920x1080 30.00 pix yuv422p is basically same size as file path: /dev/shm/DNxHR-yuv422.mov 435864233 bytes info: format: mov,mp4,m4a,3gp,3g2,mj2 1 video stream vid0 (0), id 0x63: video1 dnxhd 1920x1080 30.00 pix yuv422p10le color space:bt709/ range:tv 472+0 frms 15.73 secs 0:00:15.73 (both play fast/realtime on my machine, as opposed to DNxHR_444) --- DNxHR_LB.mov Description: Binary data DNxHR_SQ.mov Description: Binary data -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
