Re: [CinCV TNG] Fw: Need for CV Cinelerra documentation Manu…

Top Page
Attachments:
Message as email
+ (text/plain)
+ signature.asc (application/pgp-signature)
Delete this message
Author: Miroslav Rovis
Date:  
To: Good Guy
Subject: Re: [CinCV TNG] Fw: Need for CV Cinelerra documentation Manual updates (mostly in the area of "effects" with some new features)
I'll carefully apply your instructions below.

Let me just answer the query of yours about my schedule:
I plan to go to sleep tonight when I (nearly) fall dead tired, making a
comprimise btwn desire to se this done, and the need to get up in the
morning not too tired... ;-)

I will likely get up at around 6 a.m. but it could be even earlier, and
can see if there's any mail from you.

I go to Mass at 7:30 a.m. and am back soon after 8 a.m. and can be
available for more testing again.

Will let you know if this try was successful. Going to try it now.

Just one note below...
On 160426-14:54-0600, Good Guy wrote:
> >
> > python < ./bccmdl.py > bcxfer.C
> > g++ `cat x86_64/c_flags` -c condition.C -o x86_64/condition.o
> > g++ `cat x86_64/c_flags` -c errorbox.C -o x86_64/errorbox.o
> > g++ `cat x86_64/c_flags` -c filesystem.C -o x86_64/filesystem.o
> >   File "<stdin>", line 498
> >     print "%svoid %sxfer_%s_to_%s" % (pfx, cls, fr_cmdl[3:], to_cmdl[3:]),
> >                                  ^
> > SyntaxError: invalid syntax
> > Makefile:121: recipe for target 'bcxfer.C' failed
> > make[2]: *** [bcxfer.C] Error 1
> > make[2]: *** Waiting for unfinished jobs....
> > filesystem.C: In constructor ‘FileSystem::FileSystem()’:
> > filesystem.C:123:38: warning: ignoring return value of ‘char*
> > getcwd(char*, size_t)’, declared with attribute warn_unused_result
> > [-Wunused-result]
> >   (void)getcwd(current_dir, BCTEXTLEN);
> >                                       ^

> >
>
> this fragment is from the first build error in the log.
>
> It occurs in the guicast llbrary build, which is part of cinelerra proper.
> This script is a "code generator", which outputs a program which are
> the colormodel transfer functions. All that said, the args of the the
> "print"
> are strings, and this is an example of pasting it into a python2.7
> interpreter:
>
> [root@telluride Downloads]# python2.7
> Python 2.7.11 (default, Mar 31 2016, 20:46:51)
> [GCC 5.3.1 20151207 (Red Hat 5.3.1-2)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> print "%svoid %sxfer_%s_to_%s" % ("arg1 ", "arg2 ", "arg3 ", "arg4"),
> arg1 void arg2 xfer_arg3 _to_arg4
>
> which operates without errors.
> and now, this is what happens when you use python3:
> [root@telluride Downloads]# python3
> Python 3.4.3 (default, Mar 31 2016, 20:42:37)
> [GCC 5.3.1 20151207 (Red Hat 5.3.1-2)] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> print "%svoid %sxfer_%s_to_%s" % ("arg1 ", "arg2 ", "arg3 ", "arg4"),
>   File "<stdin>", line 1
>     print "%svoid %sxfer_%s_to_%s" % ("arg1 ", "arg2 ", "arg3 ", "arg4"),
>                                  ^
> SyntaxError: invalid syntax

>
> which looks just like the error message. So, here is another attempt
> at making sure that python2.7 is used.
>
> cd cinelerra5/cinelerra-5.1
> echo "EXTRA_LIBS += -lva" >> global_config
> sed -e '1,1c#!/usr/bin/python2.7' -i guicast/bccmdl.py
> sed -e '/^bcxfer.C:/,+1s/python/python2.7/' -i guicast/Makefile
> ./configure shared
> make >& log
>
> This patch should look like:
> [root@telluride guicast]# diff Makefile
> /mnt0/cinelerra5/cinelerra-5.1/guicast/Makefile
> 121c121
> <       python2.7 < ./bccmdl.py > bcxfer.C
> ---
> >       python < ./bccmdl.py > bcxfer.C

>
> You should use both seds.
> Pretty sure this is the first big problem. It does not mean it is the
> last, but it is
> in the path. Stay in touch, and let me know what your schedule may be so I
> can try to plan.
>
> gg
>
>


See this:

> On Sun, Apr 10, 2016 at 1:32 PM, Terje J. Hanssen <terje@???
> > wrote:
>


You seem to have replied to wrong email. But the content of your mail
(barring the quoting of the wrong mail) is clear and workable.

Going to work now.

> >
> > Den 10. april 2016 19:29, skrev Good Guy:
> >
> >>
> >>     For batch rendering (3) Blu-ray or DVD a video bit-rate 8 Mb(ps?)
> >>     is documented to the current default.
> >>     I tried (not batch) DVD render wth bit-rate '0' and got a much
> >>     lower video bit-rate of 1.49 Mbps.
> >>     When I set 8 Mbps video bit-ray for blu-ray and dvd I got that.

> >>
> >>
> >> the 'target' bitrate is calculated based on a formula from the DVD code.
> >> it divides the media size (in bits)
> >> by the video time (in seconds) to find the bitrate that will "just fit".
> >> This could create a weird bitrate if the
> >> media is large, and the video time is small, so the target bitrate is
> >> limited to 8Mb/s. That is the bitrate
> >> shown as the initial bitrate when the render menu is created. The same
> >> method is used for DVD and BD.
> >> Probably, you got the bitrate default calculation from libavcodec in
> >> ffmpeg.
> >>
> >
> > The source file I loaded was a small dv clip:
> >
> > du -sm dv68*
> >
> > 377    dv68.dv
> > 82    dv68_vbr6Mbps_yuva-8.dvd
> > 20    dv68_BD_default_yuva-8.m2ts
> > 118    dv68_BD_vbr8mbbs_yuva-8.m2ts
> > 4    dv68_h264_default.mp4
> > 7    dv68_h264_vbr400kbs.mp4
> > 4    dv68_h265_default.mp4
> > 7    dv68_h265_vbr400kbs.mp4
> > 489    dv68_yuv422p10_rgbfloat.pro

> >
> > ffprobe  dv68.dv
> > [dv @ 0xc8dd40] Estimating duration from bitrate, this may be inaccurate
> > Input #0, dv, from 'dv68.dv':
> >   Metadata:
> >     timecode        : 00:00:00:00
> >   Duration: 00:01:49.76, start: 0.000000, bitrate: 28800 kb/s
> >     Stream #0:0: Video: dvvideo, yuv420p, 720x576 [SAR 16:15 DAR 4:3],
> > 28800 kb/s, 25 fps, 25 tbr, 25 tbn, 25 tbc
> >     Stream #0:1: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s

> >
> >
> >>     I wondered also a bit about the dvd render video options: s
> >>     720x480 and r 30000/1001 and Format frame rates DVD 29.97 (1) ?
> >>     When I loaded a PAL DV file 720x576 @ 25 fps (8-bit yuv 4:2:0), I
> >>     also got these settings automatic in Set Format (except the color
> >>     model), somehting I verified with ffprobe on the result.

> >>
> >>
> >> The CV guys use a default format guess for the choice between ntsc and
> >> pal based on your timezone.
> >> Pretty clever. Sadly, the dvd/bd render setup does not currently
> >> incorporate this kind of factoring. I will
> >> look at trying to see if that could be done.
> >>
> >
> > Yes, the latter seems smart.
> >
> > While 1920×1080 @ 23.976p (16:9) is one of the supported HD video formats
> > for BD in both PAL and NTSC regions, it seems there are differentces for SD
> > BD video formats as follows: 720×576 @ 50i and 720×480 @ 59.94i
> > https://en.wikipedia.org/wiki/Blu-ray#Video
> >
> > and for DVD (SD): PAL DVDs are encoded at 25fps, while NTSC DVDs are
> > encoded at 30fps according to
> > https://trac.handbrake.fr/wiki/FramerateGuide#Being-my-Pal-is-NoTSoCool
> >
> >
> > Would it also be possible to also clarify (guide) when to use
> > File > Rendering > dvd (or m2ts) and Settings > Format
> > vs
> > File > DVD-render (or BD-render) and possibly Settings > Format
> > Different purposes? (I seems for me the latter set up a disc structure,
> > while the first render media classes )
> >
> >     To sum up:
> >>     When a PAL or NTSC source file is loaded, is it possible to get
> >>     the corresponding parameters set as default (automatic) where
> >>     relevant in both

> >>
> >>
> >> Ok, are you asking for the encode data rate to match the decode "probe"
> >> data rate??
> >> This is sort of harder than you may think. The cinelerra timeline is
> >> divided up into tracks and edits.
> >> There may be a lot of choices for where to get a guess. Which one is the
> >> good one?
> >> Maybe the first edit of the first track? It is just an initial target
> >> guess, so anything is probably ok
> >> to be the criteria, but it would be nice to make it reasonable. Then,
> >> there is the question of what
> >> to do if you have previously changed the initial target guess. Yours
> >> again? When do you change it?
> >>
> >
> >
> > Yeah, I loaded just one single file for testing. And yes, I see it can be
> > a problem when there are different media formats to mix.
> >
> >
> > Terje J. H
> >
> >
> >
> >
> >>
> >>
> >> On Sun, Apr 10, 2016 at 9:04 AM, Terje J. Hanssen <
> >> terje@??? <mailto:terje@nordland-teknikk.no>> wrote:
> >>
> >>     Goodguy and Phyllis,

> >>
> >>     Features5.pdf
> >>     Nice to see the screenshots, just what I wanted :)
> >>     When I have finished my hw-upgrade I can possibly help with more
> >>     screenshots from my rendering tests, as I expect they will go much
> >>     faster. For daily use I'm the happy the Cin5.1 gui is a mix of
> >>     local language/English, but for screenshot documentation i have to
> >>     find an easy way to switch everything to plain English.

> >>
> >>     Detailss on the FFMpeg icon:
> >>     Looks like the FFMpeg icon is displayed differently in the various
> >>     distros/environments/themes (?)  I'm quite happy with the clear
> >>     icon I see on my openSUSE Leap 42.1 as attached: Red 'FF' text on
> >>     a green 'V' (checked) on a yellow/white square background, or Red
> >>     'FF' on a green triangle background when unchecked. No 'reddish'
> >>     or 'blackish' here(?)

> >>
> >>     Rendering default presets and Set format:
> >>     As a first time, quick&easy trial, it will be fine if just
> >>     selecting a media class and nothing else (compression, bit-rate
> >>     etc) will result in useful, acceptable results from defaults.

> >>
> >>     What gives i.e the 'default video bit-rate', is it when the
> >>     bit-rate is '0' first time or selected '0' ?
> >>     One 'problem' for the 'default' looks to be that the previous
> >>     selected bit-rate is remembered and is automatic set next time.

> >>
> >>     On the other hand, the Set Format menu seems to get the right
> >>     values according to the loaded file, except the color model that
> >>     is is not remembered but go back to the default RGB-8 Bit.

> >>
> >>     My previous test with ffprobe on rendered .mp4 (x264/x265
> >>     encoding) showed that 'default 0' bit-rate give video bit-rate of
> >>     only 125-130 kbs that is all too low which results in unuseful bad
> >>     quality. I think required a video bit-rate 500-600 kbs or more is
> >>     neccessary to be useful for the web.

> >>
> >>     For batch rendering (3) Blu-ray or DVD a video bit-rate 8 Mb(ps?)
> >>     is documented to the current default.
> >>     I tried (not batch) DVD render wth bit-rate '0' and got a much
> >>     lower video bit-rate of 1.49 Mbps.
> >>     When I set 8 Mbps video bit-ray for blu-ray and dvd I got that.

> >>
> >>     I wondered also a bit about the dvd render video options: s
> >>     720x480 and r 30000/1001 and Format frame rates DVD 29.97 (1) ?
> >>     When I loaded a PAL DV file 720x576 @ 25 fps (8-bit yuv 4:2:0), I
> >>     also got these settings automatic in Set Format (except the color
> >>     model), somehting I verified with ffprobe on the result.

> >>
> >>     Rgds,
> >>     Terje J. H

> >>
> >>
> >>     Den 10. april 2016 03:01, skrev Good Guy:

> >>
> >>         Terje

> >>
> >>         Your discussion caused me to do some exploring, and I
> >>         discovered a bug.  bummer.  It did not affect much, but it is
> >>         in part of the decision process used here.  When you open
> >>         media for reading, if it is "replace current project" and is a
> >>         single asset file, in 5.1 it causes "select_asset" to operate
> >>         on the asset.  This in turn calls "get_best_colormodel", and
> >>         that is where the bug is.  The determination of best
> >>         colormodel for decoding seems to depend on which video
> >>         graphics driver you have set in your playback preferences.
> >>  So, if you like opengl, it goes for yuv888 but if you use X11
> >>         it uses rgb.  It seems to select based on how your media is to
> >>         be displayed.

> >>
> >>         For encoding, the internal colormodels the codec supports are
> >>         the salient parameters.  Since that all depends on just
> >>         exactly what you are going to be doing, it depends on the
> >>         future, not the past like in the decoder instance.  While
> >>         there may be some work that can be done to make preset encoder
> >>         files which only specify the desirable format combinations,
> >>         that may or may not be your intent.  I recommend that you be
> >>         the judge of good and evil.

> >>
> >>         Phyllis took your suggestion, and has added some screenshots
> >>         to the 5.1 features documentation.  Thanks for the help.

> >>
> >>         gg

> >>
> >>         On Fri, Apr 8, 2016 at 8:48 AM, Terje J. Hanssen
> >>         <terje@??? <mailto:terje@nordland-teknikk.no>
> >>         <mailto:terje@nordland-teknikk.no

> >>
> >>         <mailto:terje@nordland-teknikk.no>>> wrote:

> >>
> >>             Phyllis,

> >>
> >>             Thanks a lot for your work with the documentation.

> >>
> >>             I have not reached to read everything yet, and because it
> >>         now may
> >>             take some time before I will be ready to test DVD&BD-R
> >>         authoring
> >>             and burning (I'm faced with my hardware upgrade), I want
> >>         to post
> >>             some some construvtive comments and questions first:

> >>
> >>             The Cinelerra-CV manual is a combined 'all-in-one' Getting
> >>             started-User, Admin and Reference guide  in one.

> >>
> >>             As time permit I will suggest to add screen shots as visual
> >>             examples/selections of each menu discussed to complement the
> >>             document text.
> >>             My experience since command line Unix only, is that graphical
> >>             images, menus and gui are especially appreciated and user
> >>             attractive, independent of OS platforms and applications.
> >>         This of
> >>             course doesn't prevent more experienced users to combine
> >>         the best
> >>             out of preferred gui and cli tools as their 'best practice'.

> >>
> >>             That is more like these:
> >>         https://cinelerra-cv.org/docs/cinelerra_cv_manual_en.html#SEC62

> >>
> >>             So some questions to the menus, presets and possible
> >>         combinations:

> >>
> >>             *Settings > Format* (Shift-F) menu | *Color model*:

> >>
> >>               * RGB-8 Bit
> >>               * RGBA-8 Bit
> >>               * RGB-FLOAT
> >>               * RGBA-FLOAT
> >>               * YUV-8 Bit
> >>               * *YUVA-8 Bit*

> >>
> >>             It looks like Cinelerra 5.1 uses RGB-8 Bit default color
> >>         model,
> >>             while in CinelerraCV 2.2 and later the color model is set to
> >>             *YUVA-8 bit.*
> >>             Most compressed media is in YUV and this derivate allows
> >>         video to
> >>             be processed fast with the least color degradation
> >>         according to
> >>             the manual.

> >>
> >>             If there is nothing that prohibit it, it looks reasonabel if
> >>             Cinelerra 5.1 also get *YUVA-8 bit *as the default color
> >>         model?

> >>
> >>
> >>             *File > Render* (Shift-R) menu:

> >>
> >>             File Format: *FFMPEG* dropdown menu and *Video
> >>         Compression* Preset
> >>             contains

> >>
> >>               * mp4
> >>                       + h264.mp4
> >>                       + h265.mp4
> >>               * pro
> >>                       + med422p10
> >>               * m2ts
> >>                       + bluray.m2ts
> >>               * mkv
> >>                       + u2b.mkv
> >>               * mpeg
> >>                       + mpeg.mpeg
> >>               * qt
> >>                       + mp4.qt
> >>                       + and many more
> >>               * mp3
> >>                      +

> >>
> >>               * dvd
> >>                       + dvd.dvd

> >>
> >>
> >>             It would be fine to get clarified *which* of the above
> >>             combinations of *FFMPEG Video compression* and *Color
> >>         models* that

> >>
> >>             is valid and actual?

> >>
> >>             i.e 'Pro' and/or 'YUV-FLOAT/YUVA-FLOAT' has been told me
> >>         by GG are
> >>             to be used in combination.
> >>             What happends and what is the result of Pro using 10-bit
> >>         x264/x265
> >>             libs and FLOAT which is 32 Bit color-depth?

> >>
> >>             Possibly this Adobe Premiere Pro document can be used as a
> >>             reference here

> >>
> >> http://blogs.adobe.com/VideoRoad/2010/06/understanding_color_processing.html
> >>
> >>
> >>             Terje J. H

> >>
> >>
> >>             Den 07. april 2016 22:42, skrev Phyllis Smith:

> >>
> >>                 Terje:

> >>
> >>                 In response to your words below:

> >>
> >>                 "So to what you mentioned first and somehwat related
> >>             to ffmpeg;
> >>                 that is making Blu-ray Video disk and DVD (Digital
> >>             Video) disks.
> >>                 I hope you also may find time to these actual parts
> >>             next.  And to
> >>                 use this opportunity to remind GG about my request and
> >>             suggestion
> >>                 to extend the ffmpeg options with the 'high422p'
> >>             profile for h264
> >>                 and h265 rendering ;)"

> >>
> >>                 The 5.1 Features5 PDF manual has been updated to
> >>             include making
> >>                 DVDs and is in the standard CV http "five"
> >>             subdirectory. Also,
> >>                 made some corrections in previous areas to include a
> >>             complete
> >>                 example of modifying ffmpeg options files based on the
> >>             ProRes
> >>                 422p stuff Good Guy had you test the other day. (BTW he is
> >>                 including those files, and the "pro" option, he sent
> >>             in the next
> >>                 Cinelerra 5.1 deliverable and is building new binaries
> >>             for the
> >>                 different distros now so should be at
> >>             https://cinelerra-cv.org/five today or tomorrow).

> >>
> >>                 The section in the manual for creating DVDs seems
> >>             verbose, but it
> >>                 is really quite simple that even I can do it! Keep in
> >>             mind that
> >>                 it has only ever been used on a Fedora linux system,
> >>             with a
> >>                 specific brand of blu-ray writer, and the last live
> >>             usage was
> >>                 about 4 months ago with a lot of code having been modified
> >>                 since.  However, the actual media was tested on
> >>             several players.     In other words, please report any
> >>             problems, confusing
> >>                 documentation, and also if it worked correctly for
> >>             you!  And you
> >>                 might want to use rewritable media at first.

> >>
> >>                 No need to reply until you have a chance to read
> >>             Features5.pdf
> >>                 and try making a blu-ray.  ... Phyllis

> >>
> >>
> >>
> >>
> >>                 _______________________________________________
> >>                 Cinelerra mailing list
> >>             Cinelerra@???
> >>             <mailto:Cinelerra@lists.cinelerra-cv.org>
> >>                 <mailto:Cinelerra@lists.cinelerra-cv.org
> >>             <mailto:Cinelerra@lists.cinelerra-cv.org>>

> >>
> >> http://lists.cinelerra-cv.org/cgi-bin/mailman/listinfo/cinelerra
> >>
> >>
> >>
> >>             _______________________________________________
> >>             Cinelerra mailing list
> >>         Cinelerra@???
> >>         <mailto:Cinelerra@lists.cinelerra-cv.org>
> >>             <mailto:Cinelerra@lists.cinelerra-cv.org
> >>         <mailto:Cinelerra@lists.cinelerra-cv.org>>
> >>         http://lists.cinelerra-cv.org/cgi-bin/mailman/listinfo/cinelerra

> >>
> >>
> >>
> >>
> >>         _______________________________________________
> >>         Cinelerra mailing list
> >>         Cinelerra@???
> >>         <mailto:Cinelerra@lists.cinelerra-cv.org>
> >>         http://lists.cinelerra-cv.org/cgi-bin/mailman/listinfo/cinelerra

> >>
> >>
> >>
> >>     _______________________________________________
> >>     Cinelerra mailing list
> >>     Cinelerra@???
> >>     <mailto:Cinelerra@lists.cinelerra-cv.org>
> >>     http://lists.cinelerra-cv.org/cgi-bin/mailman/listinfo/cinelerra

> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> Cinelerra mailing list
> >> Cinelerra@???
> >> http://lists.cinelerra-cv.org/cgi-bin/mailman/listinfo/cinelerra
> >>
> >
> > _______________________________________________
> > Cinelerra mailing list
> > Cinelerra@???
> > http://lists.cinelerra-cv.org/cgi-bin/mailman/listinfo/cinelerra
> >


--
Miroslav Rovis
Zagreb, Croatia
http://www.CroatiaFidelis.hr