HDV formats patch
For cinelerra/defaultformats.h I de-capitalized "I" in presets, but I'm not sure about overall aesthetics of "P" vs "p" or how I added "(HDV)" to some presets (because I think those 720p presets can be used outside of HDV material?) Terje, can you try to pull cinGG sources from git, apply my patch (git apply PATCH from source tree) and build with "--with-single-user", so there will be no danger to your Cin isntallation and see if patch actually gives workable settings for your real footage? From dialogs it seems Aspect Ratio at the bottom of format window IS Screen/Display aspect ration, and W/H ratio is about non-square pixels. But I wonder how it supposed to work for rendering back into HDV? If your pipeline set to 1440x1080, and you encode just with special flag set - all movements and graphics and text and masked effects you added must be somewhat scaled horizontally up and down? (because if Compositor shows 1920x1080 image, and you draw nice square with Sketcher there - how those pixels will be drawn on top of project size sized frame? Or you must have special overlay track set to 1920x1080 where you draw, and then just let Cin mix two?) NOTE: I don't think this will adds autodetect-on-load but at least having correct profiles somewhere might be 0.2 step in this direction.
Den 12.11.2020 13:57, skrev Andrew Randrianasulu:
For cinelerra/defaultformats.h
I de-capitalized "I" in presets, but I'm not sure about overall aesthetics of "P" vs "p" or how I added "(HDV)" to some presets (because I think those 720p presets can be used outside of HDV material?)
Terje, can you try to pull cinGG sources from git, apply my patch (git apply PATCH from source tree) and build with "--with-single-user", so there will be no danger to your Cin isntallation and see if patch actually gives workable settings for your real footage?
Here I reach my limit : Though I've worked with civil engineering, I'm not familiar with building, compiling and patching computer software :) Actually, almost five years ago, GG guided me step by step by email to compile my first Cin5.0 on openSUSE 42.1. Since then I've just installed pre-build rpm packages, included the current Cin-GG 5.1 on Leap 15.2. So to do it now, I will need the detailed command procedure, step by step again ;)
From dialogs it seems Aspect Ratio at the bottom of format window IS Screen/Display aspect ration, and W/H ratio is about non-square pixels.
But I wonder how it supposed to work for rendering back into HDV? If your pipeline set to 1440x1080, and you encode just with special flag set - all movements and graphics and text and masked effects you added must be somewhat scaled horizontally up and down? (because if Compositor shows 1920x1080 image, and you draw nice square with Sketcher there - how those pixels will be drawn on top of project size sized frame? Or you must have special overlay track set to 1920x1080 where you draw, and then just let Cin mix two?)
NOTE: I don't think this will adds autodetect-on-load but at least having correct profiles somewhere might be 0.2 step in this direction.
However, via a previous mail thread with url to a small hdv video clip, this file can be downloaded and tested: CinCV TNG] Setting up a Project https://lists.cinelerra-cv.org/pipermail/cinelerra/2016q4/005613.html http://mvd.homevideo.free.fr/films_HDV/20081103140154.m2t ============ mediainfo provides a longer detailed list, but here is a short list using ffprobe 20081103140154.m2t ............. Input #0, mpegts, from '20081103140154.m2t': Duration: 00:00:13.44, start: 1042.400000, bitrate: 26598 kb/s Program 100 Stream #0:0[0x810]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709, top first), 1440x1080 [SAR 4:3 DAR 16:9], 25000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc Stream #0:1[0x814]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 384 kb/s ============ I loaded this hdv file 20081103140154.m2t in my current Cin-GG, and noticed the Set Format window with Canvas size=1440x1080, W.Ratio=1, H.Ratio=1, Aspect Ratio= 4:3, Interlace mode=Bottom field first Attached screen shot below The video image aspect ratio seems be 4:3 in the compositor and player windows. Shouldn't Cin-GG with "FFmpeg First" button enabled, detect and set the same parameters like ffprobe detect above? In the past, Cin-CV did not auto-detect aspect ratio, and only applied Format aspect ratio on the output, not on the individual input files. https://cinelerra.skolelinux.narkive.com/kkJef8tW/cincvs-compositor-stretchi... ============= Terje J. H
MediaInfo rather indicates that this file is of type Top field first. Pierre Le 20-11-12 à 23 h 05, Terje J. Hanssen via Cin a écrit :
I loaded this hdv file 20081103140154.m2t in my current Cin-GG, and noticed the Set Format window with Canvas size=1440x1080, W.Ratio=1, H.Ratio=1, Aspect Ratio= 4:3, Interlace mode=Bottom field first Attached screen shot below
Den 13.11.2020 05:35, skrev Pierre autourduglobe via Cin:
MediaInfo rather indicates that this file is of type Top field first.
Pierre
Le 20-11-12 à 23 h 05, Terje J. Hanssen via Cin a écrit :
I loaded this hdv file 20081103140154.m2t in my current Cin-GG, and noticed the Set Format window with Canvas size=1440x1080, W.Ratio=1, H.Ratio=1, Aspect Ratio= 4:3, Interlace mode=Bottom field first Attached screen shot below
Thank you, of course my typo: ffprobe ... Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709, top first) Terje J. H
Den 13.11.2020 05:35, skrev Pierre autourduglobe via Cin:
MediaInfo rather indicates that this file is of type Top field first.
Pierre
Le 20-11-12 à 23 h 05, Terje J. Hanssen via Cin a écrit :
I loaded this hdv file 20081103140154.m2t in my current Cin-GG, and noticed the Set Format window with Canvas size=1440x1080, W.Ratio=1, H.Ratio=1, Aspect Ratio= 4:3, Interlace mode=Bottom field first Attached screen shot below
Pierre, Thank you - of course my typo again: "top first" ffprobe ... Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709, top first) Terje J. H
Den 13.11.2020 10:14, skrev Terje J. Hanssen:
Den 13.11.2020 05:35, skrev Pierre autourduglobe via Cin:
MediaInfo rather indicates that this file is of type Top field first.
Pierre
Le 20-11-12 à 23 h 05, Terje J. Hanssen via Cin a écrit :
I loaded this hdv file 20081103140154.m2t in my current Cin-GG, and noticed the Set Format window with Canvas size=1440x1080, W.Ratio=1, H.Ratio=1, Aspect Ratio= 4:3, Interlace mode=Bottom field first Attached screen shot below
Pierre, Thank you - of course my typo again: "top first"
ffprobe ... Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709, top first)
Terje J. H
That was not my typo anyway :) What I really repeated above, except the left-out Framerate=25, were the "auto-detected parameters" inside the Set Format window after loading the hdv file (the attached screen shot). According to ffprobe, the auto-detection should instead correspond to 1440x1080 [SAR 4:3 DAR 16:9], 25 fps, top first, ============ The "Preset 1080i" in the Set Format window differs with Framerate=29.9700, Canvas size=1920x1080, W.Ratio=1.333, H.Ratio=1.0000, Aspect Ratio= 16:9, Interlace mode=Bottom field first Obviously the 1080i Preset Framerate=29.97 is for NTSC Interlace mode Bottom field is wrong The Canvas Width=1920 seems to be for FHD (HDV=1440)? If W.Ratio=1.3333 seems to be HDV (not for FHD)? Terje J. H
В сообщении от Friday 13 November 2020 07:05:19 вы написали:
Den 12.11.2020 13:57, skrev Andrew Randrianasulu:
For cinelerra/defaultformats.h
I de-capitalized "I" in presets, but I'm not sure about overall aesthetics of "P" vs "p" or how I added "(HDV)" to some presets (because I think those 720p presets can be used outside of HDV material?)
Terje, can you try to pull cinGG sources from git, apply my patch (git apply PATCH from source tree) and build with "--with-single-user", so there will be no danger to your Cin isntallation and see if patch actually gives workable settings for your real footage?
Here I reach my limit : Though I've worked with civil engineering, I'm not familiar with building, compiling and patching computer software :) Actually, almost five years ago, GG guided me step by step by email to compile my first Cin5.0 on openSUSE 42.1. Since then I've just installed pre-build rpm packages, included the current Cin-GG 5.1 on Leap 15.2.
So to do it now, I will need the detailed command procedure, step by step again ;)
:} there is big script in cinelerra/cinelerra-5.1/blds/bld_prepare.sh I'll copy-paste part of it so you can copy/paste it into terminal (konsole, xterm ..) and execute as root (or use gui for isntalling all those packages, but I think it will be more time consuming): zypper -n install nasm gcc gcc-c++ zlib-devel texinfo libpng16-devel \ freeglut-devel libXv-devel alsa-devel libbz2-devel ncurses-devel \ libXinerama-devel freetype-devel libXft-devel giflib-devel ctags \ bitstream-vera-fonts xorg-x11-fonts-core xorg-x11-fonts dejavu-fonts \ openexr-devel libavc1394-devel festival-devel libjpeg8-devel libdv-devel \ libdvdnav-devel libdvdread-devel libiec61883-devel libuuid-devel \ ilmbase-devel fftw3-devel libsndfile-devel libtheora-devel flac-devel \ libtiff-devel inkscape cmake patch libnuma-devel lzma-devel udftools git \ yasm autoconf automake rpm-build libjbig-devel libvdpau-devel libva-devel \ gtk2-devel libusb-1_0-devel libpulse-devel libtool python after this you should have 'git' command available. as user: create some dir, I usually create src/ in my home and then add software-specific dirs there. You can use your GUI filemanager for this task or in terminal: $ mkdir src $ cd src $ mkdir cin5 $ cd cin5 "$" indicates user-level shell, as opposed to root shell ending with "#" now git clone git://git.cinelerra-gg.org/goodguy/cinelerra.git you can add --depth 1 if you want only last commit and not whole tree with history. But I hope you have anough hdd space. my build takes 2692M without OpenCV plugins. when this step finished you must have cinelerra tree cloned. Go to cinelerra-5.1 (should be alongside CineRmt, you can use 'ls' to look around - it prints list of files and directories) using 'cd' comman (cd stands for 'change directory') apply my patch: git apply DEFAULT_FORMATS-2.patch if you saved it under this name. This psecific form looks for file in current dir, so place it there, or use git apply /path/to/some/place/DEFAULT_FORMATS-2.patch hopefully this step shouldn't give you errors. and from there execute ./autogen.sh when this finishes correctly run ./configure --with-single-user autogen script calls various autotools to generate configure script, you can look (with mcedit/nano/kate) into each script but configure will be rather large. I hope there will be no need to mess with them. now you should see summary of things configure found on your system. If it looks ok then just type make and look at all those lines scrolling past :} (you may use this trick with tee and log file redirection, but I just watch lines scroll) if everything finishes without error - then run make install (as user) . It will give you 'bin' directory inside source tree to run ./cin from
From dialogs it seems Aspect Ratio at the bottom of format window IS Screen/Display aspect ration, and W/H ratio is about non-square pixels.
But I wonder how it supposed to work for rendering back into HDV? If your pipeline set to 1440x1080, and you encode just with special flag set - all movements and graphics and text and masked effects you added must be somewhat scaled horizontally up and down? (because if Compositor shows 1920x1080 image, and you draw nice square with Sketcher there - how those pixels will be drawn on top of project size sized frame? Or you must have special overlay track set to 1920x1080 where you draw, and then just let Cin mix two?)
NOTE: I don't think this will adds autodetect-on-load but at least having correct profiles somewhere might be 0.2 step in this direction.
However, via a previous mail thread with url to a small hdv video clip, this file can be downloaded and tested: CinCV TNG] Setting up a Project https://lists.cinelerra-cv.org/pipermail/cinelerra/2016q4/005613.html http://mvd.homevideo.free.fr/films_HDV/20081103140154.m2t
============
mediainfo provides a longer detailed list, but here is a short list using
ffprobe 20081103140154.m2t ............. Input #0, mpegts, from '20081103140154.m2t': Duration: 00:00:13.44, start: 1042.400000, bitrate: 26598 kb/s Program 100 Stream #0:0[0x810]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709, top first), 1440x1080 [SAR 4:3 DAR 16:9], 25000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc Stream #0:1[0x814]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 384 kb/s
============
I loaded this hdv file 20081103140154.m2t in my current Cin-GG, and noticed the Set Format window with Canvas size=1440x1080, W.Ratio=1, H.Ratio=1, Aspect Ratio= 4:3, Interlace mode=Bottom field first Attached screen shot below
The video image aspect ratio seems be 4:3 in the compositor and player windows. Shouldn't Cin-GG with "FFmpeg First" button enabled, detect and set the same parameters like ffprobe detect above?
I think it should, probably bug or something not wired up yet ....
In the past, Cin-CV did not auto-detect aspect ratio, and only applied Format aspect ratio on the output, not on the individual input files. https://cinelerra.skolelinux.narkive.com/kkJef8tW/cincvs-compositor-stretchi...
=============
Terje J. H
Den 13.11.2020 09:40, skrev Andrew Randrianasulu:
В сообщении от Friday 13 November 2020 07:05:19 вы написали:
Den 12.11.2020 13:57, skrev Andrew Randrianasulu:
For cinelerra/defaultformats.h
I de-capitalized "I" in presets, but I'm not sure about overall aesthetics of "P" vs "p" or how I added "(HDV)" to some presets (because I think those 720p presets can be used outside of HDV material?)
Terje, can you try to pull cinGG sources from git, apply my patch (git apply PATCH from source tree) and build with "--with-single-user", so there will be no danger to your Cin isntallation and see if patch actually gives workable settings for your real footage? Here I reach my limit : Though I've worked with civil engineering, I'm not familiar with building, compiling and patching computer software :) Actually, almost five years ago, GG guided me step by step by email to compile my first Cin5.0 on openSUSE 42.1. Since then I've just installed pre-build rpm packages, included the current Cin-GG 5.1 on Leap 15.2.
So to do it now, I will need the detailed command procedure, step by step again ;) :}
there is big script in cinelerra/cinelerra-5.1/blds/bld_prepare.sh
I'll copy-paste part of it so you can copy/paste it into terminal (konsole, xterm ..) and execute as root (or use gui for isntalling all those packages, but I think it will be more time consuming):
zypper -n install nasm gcc gcc-c++ zlib-devel texinfo libpng16-devel \ freeglut-devel libXv-devel alsa-devel libbz2-devel ncurses-devel \ libXinerama-devel freetype-devel libXft-devel giflib-devel ctags \ bitstream-vera-fonts xorg-x11-fonts-core xorg-x11-fonts dejavu-fonts \ openexr-devel libavc1394-devel festival-devel libjpeg8-devel libdv-devel \ libdvdnav-devel libdvdread-devel libiec61883-devel libuuid-devel \ ilmbase-devel fftw3-devel libsndfile-devel libtheora-devel flac-devel \ libtiff-devel inkscape cmake patch libnuma-devel lzma-devel udftools git \ yasm autoconf automake rpm-build libjbig-devel libvdpau-devel libva-devel \ gtk2-devel libusb-1_0-devel libpulse-devel libtool python
after this you should have 'git' command available.
I got the following output: ============== Retrieving repository 'multimedia:apps' metadata ...................................................................................................[done] Building repository 'multimedia:apps' cache ........................................................................................................[done] Retrieving repository 'Packman Repository' metadata ................................................................................................[done] Building repository 'Packman Repository' cache .....................................................................................................[done] Retrieving repository 'Hovedpakkebrønn for oppdateringer' metadata .................................................................................[done] Building repository 'Hovedpakkebrønn for oppdateringer' cache ......................................................................................[done] Retrieving repository 'Hovedpakkebrønn for oppdateringer' metadata .................................................................................[done] Building repository 'Hovedpakkebrønn for oppdateringer' cache ......................................................................................[done] Loading repository data... Reading installed packages... 'gcc' is already installed. No update candidate for 'gcc-7-lp152.4.114.x86_64'. The highest available version is already installed. 'zlib-devel' is already installed. No update candidate for 'zlib-devel-1.2.11-lp152.8.6.1.x86_64'. The highest available version is already installed. 'python' is already installed. There is an update candidate for 'python' from vendor 'obs://build.opensuse.org/home:deltafox', while the current vendor is 'openSUSE'. Use 'zypper install python-2.7.18-lp152.177.1.x86_64' to install this candidate. 'dejavu-fonts' is already installed. No update candidate for 'dejavu-fonts-2.37-lp152.3.2.noarch'. The highest available version is already installed. 'xorg-x11-fonts' is already installed. No update candidate for 'xorg-x11-fonts-7.6-lp152.7.3.1.noarch'. The highest available version is already installed. 'xorg-x11-fonts-core' is already installed. No update candidate for 'xorg-x11-fonts-core-7.6-lp152.7.3.1.noarch'. The highest available version is already installed. 'lzma-devel' not found in package names. Trying capabilities. Resolving package dependencies... 5 Problems: Problem: alsa-devel-1.2.4-lp152.338.3.x86_64 requires libasound2 = 1.2.4, but this requirement cannot be provided Problem: fftw3-devel-3.3.8-lp152.104.2.x86_64 requires libfftw3-3 = 3.3.8-lp152.104.2, but this requirement cannot be provided Problem: flac-devel-1.3.3-lp152.231.4.x86_64 requires libFLAC8 = 1.3.3, but this requirement cannot be provided Problem: libpng16-devel-1.6.37-lp152.126.3.x86_64 requires libpng16-16 = 1.6.37, but this requirement cannot be provided Problem: giflib-devel-5.2.1-lp152.121.3.x86_64 requires libgif7 = 5.2.1, but this requirement cannot be provided Problem: alsa-devel-1.2.4-lp152.338.3.x86_64 requires libasound2 = 1.2.4, but this requirement cannot be provided not installable providers: libasound2-1.2.4-lp152.338.3.x86_64[https-download.opensuse.org-6b55971e] Solution 1: install libasound2-1.2.4-lp152.338.3.x86_64 (with vendor change) openSUSE --> obs://build.opensuse.org/multimedia Solution 2: do not install alsa-devel-1.2.4-lp152.338.3.x86_64 Solution 3: break alsa-devel-1.2.4-lp152.338.3.x86_64 by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): c =========== 1 or 2 ? Terje J. H
as user:
create some dir, I usually create src/ in my home and then add software-specific dirs there.
You can use your GUI filemanager for this task or in terminal:
$ mkdir src $ cd src $ mkdir cin5 $ cd cin5
"$" indicates user-level shell, as opposed to root shell ending with "#"
now git clone git://git.cinelerra-gg.org/goodguy/cinelerra.git
you can add --depth 1 if you want only last commit and not whole tree with history. But I hope you have anough hdd space.
my build takes 2692M without OpenCV plugins.
when this step finished you must have cinelerra tree cloned. Go to cinelerra-5.1 (should be alongside CineRmt, you can use 'ls' to look around - it prints list of files and directories) using 'cd' comman (cd stands for 'change directory')
apply my patch: git apply DEFAULT_FORMATS-2.patch if you saved it under this name. This psecific form looks for file in current dir, so place it there, or use
git apply /path/to/some/place/DEFAULT_FORMATS-2.patch
hopefully this step shouldn't give you errors.
and from there execute ./autogen.sh
when this finishes correctly run
./configure --with-single-user
autogen script calls various autotools to generate configure script, you can look (with mcedit/nano/kate) into each script but configure will be rather large. I hope there will be no need to mess with them.
now you should see summary of things configure found on your system. If it looks ok then just type make and look at all those lines scrolling past :} (you may use this trick with tee and log file redirection, but I just watch lines scroll)
if everything finishes without error - then run make install (as user) . It will give you 'bin' directory inside source tree to run ./cin from
From dialogs it seems Aspect Ratio at the bottom of format window IS Screen/Display aspect ration, and W/H ratio is about non-square pixels.
But I wonder how it supposed to work for rendering back into HDV? If your pipeline set to 1440x1080, and you encode just with special flag set - all movements and graphics and text and masked effects you added must be somewhat scaled horizontally up and down? (because if Compositor shows 1920x1080 image, and you draw nice square with Sketcher there - how those pixels will be drawn on top of project size sized frame? Or you must have special overlay track set to 1920x1080 where you draw, and then just let Cin mix two?)
NOTE: I don't think this will adds autodetect-on-load but at least having correct profiles somewhere might be 0.2 step in this direction. However, via a previous mail thread with url to a small hdv video clip, this file can be downloaded and tested: CinCV TNG] Setting up a Project https://lists.cinelerra-cv.org/pipermail/cinelerra/2016q4/005613.html http://mvd.homevideo.free.fr/films_HDV/20081103140154.m2t
============
mediainfo provides a longer detailed list, but here is a short list using
ffprobe 20081103140154.m2t ............. Input #0, mpegts, from '20081103140154.m2t': Duration: 00:00:13.44, start: 1042.400000, bitrate: 26598 kb/s Program 100 Stream #0:0[0x810]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv, bt709, top first), 1440x1080 [SAR 4:3 DAR 16:9], 25000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc Stream #0:1[0x814]: Audio: mp2 ([3][0][0][0] / 0x0003), 48000 Hz, stereo, s16p, 384 kb/s
============
I loaded this hdv file 20081103140154.m2t in my current Cin-GG, and noticed the Set Format window with Canvas size=1440x1080, W.Ratio=1, H.Ratio=1, Aspect Ratio= 4:3, Interlace mode=Bottom field first Attached screen shot below
The video image aspect ratio seems be 4:3 in the compositor and player windows. Shouldn't Cin-GG with "FFmpeg First" button enabled, detect and set the same parameters like ffprobe detect above? I think it should, probably bug or something not wired up yet ....
In the past, Cin-CV did not auto-detect aspect ratio, and only applied Format aspect ratio on the output, not on the individual input files. https://cinelerra.skolelinux.narkive.com/kkJef8tW/cincvs-compositor-stretchi...
=============
Terje J. H
В сообщении от Friday 13 November 2020 19:03:24 вы написали:
Den 13.11.2020 09:40, skrev Andrew Randrianasulu:
В сообщении от Friday 13 November 2020 07:05:19 вы написали:
Den 12.11.2020 13:57, skrev Andrew Randrianasulu:
For cinelerra/defaultformats.h
I de-capitalized "I" in presets, but I'm not sure about overall aesthetics of "P" vs "p" or how I added "(HDV)" to some presets (because I think those 720p presets can be used outside of HDV material?)
Terje, can you try to pull cinGG sources from git, apply my patch (git apply PATCH from source tree) and build with "--with-single-user", so there will be no danger to your Cin isntallation and see if patch actually gives workable settings for your real footage? Here I reach my limit : Though I've worked with civil engineering, I'm not familiar with building, compiling and patching computer software :) Actually, almost five years ago, GG guided me step by step by email to compile my first Cin5.0 on openSUSE 42.1. Since then I've just installed pre-build rpm packages, included the current Cin-GG 5.1 on Leap 15.2.
So to do it now, I will need the detailed command procedure, step by step again ;) :}
there is big script in cinelerra/cinelerra-5.1/blds/bld_prepare.sh
I'll copy-paste part of it so you can copy/paste it into terminal (konsole, xterm ..) and execute as root (or use gui for isntalling all those packages, but I think it will be more time consuming):
zypper -n install nasm gcc gcc-c++ zlib-devel texinfo libpng16-devel \ freeglut-devel libXv-devel alsa-devel libbz2-devel ncurses-devel \ libXinerama-devel freetype-devel libXft-devel giflib-devel ctags \ bitstream-vera-fonts xorg-x11-fonts-core xorg-x11-fonts dejavu-fonts \ openexr-devel libavc1394-devel festival-devel libjpeg8-devel libdv-devel \ libdvdnav-devel libdvdread-devel libiec61883-devel libuuid-devel \ ilmbase-devel fftw3-devel libsndfile-devel libtheora-devel flac-devel \ libtiff-devel inkscape cmake patch libnuma-devel lzma-devel udftools git \ yasm autoconf automake rpm-build libjbig-devel libvdpau-devel libva-devel \ gtk2-devel libusb-1_0-devel libpulse-devel libtool python
after this you should have 'git' command available.
I got the following output:
==============
Retrieving repository 'multimedia:apps' metadata ...................................................................................................[done] Building repository 'multimedia:apps' cache ........................................................................................................[done] Retrieving repository 'Packman Repository' metadata ................................................................................................[done] Building repository 'Packman Repository' cache .....................................................................................................[done] Retrieving repository 'Hovedpakkebrønn for oppdateringer' metadata .................................................................................[done] Building repository 'Hovedpakkebrønn for oppdateringer' cache ......................................................................................[done] Retrieving repository 'Hovedpakkebrønn for oppdateringer' metadata .................................................................................[done] Building repository 'Hovedpakkebrønn for oppdateringer' cache ......................................................................................[done] Loading repository data... Reading installed packages... 'gcc' is already installed. No update candidate for 'gcc-7-lp152.4.114.x86_64'. The highest available version is already installed. 'zlib-devel' is already installed. No update candidate for 'zlib-devel-1.2.11-lp152.8.6.1.x86_64'. The highest available version is already installed. 'python' is already installed. There is an update candidate for 'python' from vendor 'obs://build.opensuse.org/home:deltafox', while the current vendor is 'openSUSE'. Use 'zypper install python-2.7.18-lp152.177.1.x86_64' to install this candidate. 'dejavu-fonts' is already installed. No update candidate for 'dejavu-fonts-2.37-lp152.3.2.noarch'. The highest available version is already installed. 'xorg-x11-fonts' is already installed. No update candidate for 'xorg-x11-fonts-7.6-lp152.7.3.1.noarch'. The highest available version is already installed. 'xorg-x11-fonts-core' is already installed. No update candidate for 'xorg-x11-fonts-core-7.6-lp152.7.3.1.noarch'. The highest available version is already installed. 'lzma-devel' not found in package names. Trying capabilities. Resolving package dependencies... 5 Problems: Problem: alsa-devel-1.2.4-lp152.338.3.x86_64 requires libasound2 = 1.2.4, but this requirement cannot be provided Problem: fftw3-devel-3.3.8-lp152.104.2.x86_64 requires libfftw3-3 = 3.3.8-lp152.104.2, but this requirement cannot be provided Problem: flac-devel-1.3.3-lp152.231.4.x86_64 requires libFLAC8 = 1.3.3, but this requirement cannot be provided Problem: libpng16-devel-1.6.37-lp152.126.3.x86_64 requires libpng16-16 = 1.6.37, but this requirement cannot be provided Problem: giflib-devel-5.2.1-lp152.121.3.x86_64 requires libgif7 = 5.2.1, but this requirement cannot be provided
Problem: alsa-devel-1.2.4-lp152.338.3.x86_64 requires libasound2 = 1.2.4, but this requirement cannot be provided not installable providers: libasound2-1.2.4-lp152.338.3.x86_64[https-download.opensuse.org-6b55971e] Solution 1: install libasound2-1.2.4-lp152.338.3.x86_64 (with vendor change) openSUSE --> obs://build.opensuse.org/multimedia Solution 2: do not install alsa-devel-1.2.4-lp152.338.3.x86_64 Solution 3: break alsa-devel-1.2.4-lp152.338.3.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): c
===========
1 or 2 ?
Terje J. H
One, I think ..or "3" because not installing it will lead to no ALSA i/o (nowadays there is pulseaudio in CinGG , but I'm not sure how well it work)
Den 13.11.2020 17:27, skrev Andrew Randrianasulu:
В сообщении от Friday 13 November 2020 19:03:24 вы написали:
Den 13.11.2020 09:40, skrev Andrew Randrianasulu:
В сообщении от Friday 13 November 2020 07:05:19 вы написали:
Den 12.11.2020 13:57, skrev Andrew Randrianasulu:
For cinelerra/defaultformats.h
I de-capitalized "I" in presets, but I'm not sure about overall aesthetics of "P" vs "p" or how I added "(HDV)" to some presets (because I think those 720p presets can be used outside of HDV material?)
Terje, can you try to pull cinGG sources from git, apply my patch (git apply PATCH from source tree) and build with "--with-single-user", so there will be no danger to your Cin isntallation and see if patch actually gives workable settings for your real footage? Here I reach my limit : Though I've worked with civil engineering, I'm not familiar with building, compiling and patching computer software :) Actually, almost five years ago, GG guided me step by step by email to compile my first Cin5.0 on openSUSE 42.1. Since then I've just installed pre-build rpm packages, included the current Cin-GG 5.1 on Leap 15.2.
So to do it now, I will need the detailed command procedure, step by step again ;) :}
there is big script in cinelerra/cinelerra-5.1/blds/bld_prepare.sh
I'll copy-paste part of it so you can copy/paste it into terminal (konsole, xterm ..) and execute as root (or use gui for isntalling all those packages, but I think it will be more time consuming):
zypper -n install nasm gcc gcc-c++ zlib-devel texinfo libpng16-devel \ freeglut-devel libXv-devel alsa-devel libbz2-devel ncurses-devel \ libXinerama-devel freetype-devel libXft-devel giflib-devel ctags \ bitstream-vera-fonts xorg-x11-fonts-core xorg-x11-fonts dejavu-fonts \ openexr-devel libavc1394-devel festival-devel libjpeg8-devel libdv-devel \ libdvdnav-devel libdvdread-devel libiec61883-devel libuuid-devel \ ilmbase-devel fftw3-devel libsndfile-devel libtheora-devel flac-devel \ libtiff-devel inkscape cmake patch libnuma-devel lzma-devel udftools git \ yasm autoconf automake rpm-build libjbig-devel libvdpau-devel libva-devel \ gtk2-devel libusb-1_0-devel libpulse-devel libtool python
after this you should have 'git' command available. I got the following output:
==============
Retrieving repository 'multimedia:apps' metadata ...................................................................................................[done] Building repository 'multimedia:apps' cache ........................................................................................................[done] Retrieving repository 'Packman Repository' metadata ................................................................................................[done] Building repository 'Packman Repository' cache .....................................................................................................[done] Retrieving repository 'Hovedpakkebrønn for oppdateringer' metadata .................................................................................[done] Building repository 'Hovedpakkebrønn for oppdateringer' cache ......................................................................................[done] Retrieving repository 'Hovedpakkebrønn for oppdateringer' metadata .................................................................................[done] Building repository 'Hovedpakkebrønn for oppdateringer' cache ......................................................................................[done] Loading repository data... Reading installed packages... 'gcc' is already installed. No update candidate for 'gcc-7-lp152.4.114.x86_64'. The highest available version is already installed. 'zlib-devel' is already installed. No update candidate for 'zlib-devel-1.2.11-lp152.8.6.1.x86_64'. The highest available version is already installed. 'python' is already installed. There is an update candidate for 'python' from vendor 'obs://build.opensuse.org/home:deltafox', while the current vendor is 'openSUSE'. Use 'zypper install python-2.7.18-lp152.177.1.x86_64' to install this candidate. 'dejavu-fonts' is already installed. No update candidate for 'dejavu-fonts-2.37-lp152.3.2.noarch'. The highest available version is already installed. 'xorg-x11-fonts' is already installed. No update candidate for 'xorg-x11-fonts-7.6-lp152.7.3.1.noarch'. The highest available version is already installed. 'xorg-x11-fonts-core' is already installed. No update candidate for 'xorg-x11-fonts-core-7.6-lp152.7.3.1.noarch'. The highest available version is already installed. 'lzma-devel' not found in package names. Trying capabilities. Resolving package dependencies... 5 Problems: Problem: alsa-devel-1.2.4-lp152.338.3.x86_64 requires libasound2 = 1.2.4, but this requirement cannot be provided Problem: fftw3-devel-3.3.8-lp152.104.2.x86_64 requires libfftw3-3 = 3.3.8-lp152.104.2, but this requirement cannot be provided Problem: flac-devel-1.3.3-lp152.231.4.x86_64 requires libFLAC8 = 1.3.3, but this requirement cannot be provided Problem: libpng16-devel-1.6.37-lp152.126.3.x86_64 requires libpng16-16 = 1.6.37, but this requirement cannot be provided Problem: giflib-devel-5.2.1-lp152.121.3.x86_64 requires libgif7 = 5.2.1, but this requirement cannot be provided
Problem: alsa-devel-1.2.4-lp152.338.3.x86_64 requires libasound2 = 1.2.4, but this requirement cannot be provided not installable providers: libasound2-1.2.4-lp152.338.3.x86_64[https-download.opensuse.org-6b55971e] Solution 1: install libasound2-1.2.4-lp152.338.3.x86_64 (with vendor change) openSUSE --> obs://build.opensuse.org/multimedia Solution 2: do not install alsa-devel-1.2.4-lp152.338.3.x86_64 Solution 3: break alsa-devel-1.2.4-lp152.338.3.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): c
===========
1 or 2 ?
Terje J. H
One, I think ..or "3" because not installing it will lead to no ALSA i/o (nowadays there is pulseaudio in CinGG , but I'm not sure how well it work) =============
Andrew, There was something above that put a 'c' and 'cr' at the end, and exited to the prompt as shown above. I had to install several packages Solution 1 from the open build service obs://....... before the build script ran through and installed 2321 packages. Now I'm here : terje@alfa:~/src/cin5> terje@alfa:~/src/cin5> du -sh 546M . terje@alfa:~/src/cin5> Could you add the command "to pull cinGG sources from git, apply my patch" (git apply PATCH from source tree) and build with "--with-single-user", so there will be no danger to your Cin isntallation and see if patch actually gives workable settings for your real footage? ========= Terje J. H
Den 13.11.2020 20:32, skrev Terje J. Hanssen:
Den 13.11.2020 17:27, skrev Andrew Randrianasulu:
В сообщении от Friday 13 November 2020 19:03:24 вы написали:
Den 13.11.2020 09:40, skrev Andrew Randrianasulu:
В сообщении от Friday 13 November 2020 07:05:19 вы написали:
Den 12.11.2020 13:57, skrev Andrew Randrianasulu:
For cinelerra/defaultformats.h
I de-capitalized "I" in presets, but I'm not sure about overall aesthetics of "P" vs "p" or how I added "(HDV)" to some presets (because I think those 720p presets can be used outside of HDV material?)
Terje, can you try to pull cinGG sources from git, apply my patch (git apply PATCH from source tree) and build with "--with-single-user", so there will be no danger to your Cin isntallation and see if patch actually gives workable settings for your real footage? Here I reach my limit : Though I've worked with civil engineering, I'm not familiar with building, compiling and patching computer software :) Actually, almost five years ago, GG guided me step by step by email to compile my first Cin5.0 on openSUSE 42.1. Since then I've just installed pre-build rpm packages, included the current Cin-GG 5.1 on Leap 15.2.
So to do it now, I will need the detailed command procedure, step by step again ;) :}
there is big script in cinelerra/cinelerra-5.1/blds/bld_prepare.sh
I'll copy-paste part of it so you can copy/paste it into terminal (konsole, xterm ..) and execute as root (or use gui for isntalling all those packages, but I think it will be more time consuming):
zypper -n install nasm gcc gcc-c++ zlib-devel texinfo libpng16-devel \ freeglut-devel libXv-devel alsa-devel libbz2-devel ncurses-devel \ libXinerama-devel freetype-devel libXft-devel giflib-devel ctags \ bitstream-vera-fonts xorg-x11-fonts-core xorg-x11-fonts dejavu-fonts \ openexr-devel libavc1394-devel festival-devel libjpeg8-devel libdv-devel \ libdvdnav-devel libdvdread-devel libiec61883-devel libuuid-devel \ ilmbase-devel fftw3-devel libsndfile-devel libtheora-devel flac-devel \ libtiff-devel inkscape cmake patch libnuma-devel lzma-devel udftools git \ yasm autoconf automake rpm-build libjbig-devel libvdpau-devel libva-devel \ gtk2-devel libusb-1_0-devel libpulse-devel libtool python
after this you should have 'git' command available. I got the following output:
==============
Retrieving repository 'multimedia:apps' metadata ...................................................................................................[done]
Building repository 'multimedia:apps' cache ........................................................................................................[done]
Retrieving repository 'Packman Repository' metadata ................................................................................................[done]
Building repository 'Packman Repository' cache .....................................................................................................[done]
Retrieving repository 'Hovedpakkebrønn for oppdateringer' metadata .................................................................................[done]
Building repository 'Hovedpakkebrønn for oppdateringer' cache ......................................................................................[done]
Retrieving repository 'Hovedpakkebrønn for oppdateringer' metadata .................................................................................[done]
Building repository 'Hovedpakkebrønn for oppdateringer' cache ......................................................................................[done]
Loading repository data... Reading installed packages... 'gcc' is already installed. No update candidate for 'gcc-7-lp152.4.114.x86_64'. The highest available version is already installed. 'zlib-devel' is already installed. No update candidate for 'zlib-devel-1.2.11-lp152.8.6.1.x86_64'. The highest available version is already installed. 'python' is already installed. There is an update candidate for 'python' from vendor 'obs://build.opensuse.org/home:deltafox', while the current vendor is 'openSUSE'. Use 'zypper install python-2.7.18-lp152.177.1.x86_64' to install this candidate. 'dejavu-fonts' is already installed. No update candidate for 'dejavu-fonts-2.37-lp152.3.2.noarch'. The highest available version is already installed. 'xorg-x11-fonts' is already installed. No update candidate for 'xorg-x11-fonts-7.6-lp152.7.3.1.noarch'. The highest available version is already installed. 'xorg-x11-fonts-core' is already installed. No update candidate for 'xorg-x11-fonts-core-7.6-lp152.7.3.1.noarch'. The highest available version is already installed. 'lzma-devel' not found in package names. Trying capabilities. Resolving package dependencies... 5 Problems: Problem: alsa-devel-1.2.4-lp152.338.3.x86_64 requires libasound2 = 1.2.4, but this requirement cannot be provided Problem: fftw3-devel-3.3.8-lp152.104.2.x86_64 requires libfftw3-3 = 3.3.8-lp152.104.2, but this requirement cannot be provided Problem: flac-devel-1.3.3-lp152.231.4.x86_64 requires libFLAC8 = 1.3.3, but this requirement cannot be provided Problem: libpng16-devel-1.6.37-lp152.126.3.x86_64 requires libpng16-16 = 1.6.37, but this requirement cannot be provided Problem: giflib-devel-5.2.1-lp152.121.3.x86_64 requires libgif7 = 5.2.1, but this requirement cannot be provided
Problem: alsa-devel-1.2.4-lp152.338.3.x86_64 requires libasound2 = 1.2.4, but this requirement cannot be provided not installable providers: libasound2-1.2.4-lp152.338.3.x86_64[https-download.opensuse.org-6b55971e]
Solution 1: install libasound2-1.2.4-lp152.338.3.x86_64 (with vendor change) openSUSE --> obs://build.opensuse.org/multimedia Solution 2: do not install alsa-devel-1.2.4-lp152.338.3.x86_64 Solution 3: break alsa-devel-1.2.4-lp152.338.3.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): c
===========
1 or 2 ?
Terje J. H
One, I think ..or "3" because not installing it will lead to no ALSA i/o (nowadays there is pulseaudio in CinGG , but I'm not sure how well it work) =============
Andrew,
There was something above that put a 'c' and 'cr' at the end, and exited to the prompt as shown above. I had to install several packages Solution 1 from the open build service obs://....... before the build script ran through and installed 2321 packages.
Now I'm here :
terje@alfa:~/src/cin5> terje@alfa:~/src/cin5> du -sh 546M . terje@alfa:~/src/cin5>
Could you add the command "to pull cinGG sources from git, apply my patch"
(git apply PATCH from source tree) and build with "--with-single-user", so there will be no danger to your Cin isntallation and see if patch actually gives workable settings for your real footage?
=========
Terje J. H
....including download the patch
В сообщении от Friday 13 November 2020 22:39:24 Terje J. Hanssen написал(а): [skip]
Andrew,
There was something above that put a 'c' and 'cr' at the end, and exited to the prompt as shown above. I had to install several packages Solution 1 from the open build service obs://....... before the build script ran through and installed 2321 packages.
Now I'm here :
terje@alfa:~/src/cin5> terje@alfa:~/src/cin5> du -sh 546M . terje@alfa:~/src/cin5>
Could you add the command "to pull cinGG sources from git, apply my patch"
(git apply PATCH from source tree) and build with "--with-single-user", so there will be no danger to your Cin isntallation and see if patch actually gives workable settings for your real footage?
in theory if you already have 546M of it - sources must be ok .... I usually attach patch to email, so you can check now your email client/web interface shows attachments, and download it from there... Yes, I can't see it via web interface to mail archive. I put some patches in web folder: https://cloud.mail.ru/public/2ceA/4exRtrswu double-click on patch name and then hit Скачать
=========
Terje J. H
....including download the patch
Den 13.11.2020 21:02, skrev Andrew Randrianasulu:
В сообщении от Friday 13 November 2020 22:39:24 Terje J. Hanssen написал(а): [skip]
Now I'm here :
terje@alfa:~/src/cin5> terje@alfa:~/src/cin5> du -sh 546M . terje@alfa:~/src/cin5>
Could you add the command "to pull cinGG sources from git, apply my patch"
(git apply PATCH from source tree) and build with "--with-single-user", so there will be no danger to your Cin isntallation and see if patch actually gives workable settings for your real footage? in theory if you already have 546M of it - sources must be ok ....
I usually attach patch to email, so you can check now your email client/web interface shows attachments, and download it from there...
Yes, I can't see it via web interface to mail archive.
I put some patches in web folder:
https://cloud.mail.ru/public/2ceA/4exRtrswu
double-click on patch name and then hit Скачать
Yup, thank you - that worked :) Tested Cin-GG and loaded the hdv m2t file; ./cin Cinelerra Infinity - built: Nov 13 2020 22:08:49 git://git.cinelerra-gg.org/goodguy/cinelerra.git (c) 2006-2019 Heroine Virtual Ltd. by Adam Williams 2007-2020 mods for Cinelerra-GG by W.P.Morrow aka goodguy Cinelerra is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. There is absolutely no warranty for Cinelerra. FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t [W][000017893.443208][remote-node.c:632 client_node_port_use_buffers()] Failed to mlock memory 0x7fd337f04000 32832: This is not a problem but for best performance, consider increasing RLIMIT_MEMLOCK FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t Session time: 0:19:47 Cpu time: user: 0:00:07.198 sys: 0:00:02.003 =============== Attach two compressed screen shots: hdv-m2t_Cin-GG_4x3.jpg shows the Format default preset and the new selected 1080i/25 preset (would next suggest to change the upper "P"s to lower case "p") Not sure about the W.Ratio=1 and H.Ratio=1, as the Cin Viewer still playback the hdv video image with Aspect 4x3 ? hdv-m2t_VLC_16x9.jpg Playback the same hdv m2t file in VLC with its Codec info. Playback the video with correct aspect 16x9 ================= Terje J. H
В сообщении от Saturday 14 November 2020 01:14:24 вы написали:
Den 13.11.2020 21:02, skrev Andrew Randrianasulu:
В сообщении от Friday 13 November 2020 22:39:24 Terje J. Hanssen написал(а): [skip]
Now I'm here :
terje@alfa:~/src/cin5> terje@alfa:~/src/cin5> du -sh 546M . terje@alfa:~/src/cin5>
Could you add the command "to pull cinGG sources from git, apply my patch"
(git apply PATCH from source tree) and build with "--with-single-user", so there will be no danger to your Cin isntallation and see if patch actually gives workable settings for your real footage? in theory if you already have 546M of it - sources must be ok ....
I usually attach patch to email, so you can check now your email client/web interface shows attachments, and download it from there...
Yes, I can't see it via web interface to mail archive.
I put some patches in web folder:
https://cloud.mail.ru/public/2ceA/4exRtrswu
double-click on patch name and then hit Скачать
Yup, thank you - that worked :)
Tested Cin-GG and loaded the hdv m2t file;
./cin Cinelerra Infinity - built: Nov 13 2020 22:08:49 git://git.cinelerra-gg.org/goodguy/cinelerra.git (c) 2006-2019 Heroine Virtual Ltd. by Adam Williams 2007-2020 mods for Cinelerra-GG by W.P.Morrow aka goodguy Cinelerra is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. There is absolutely no warranty for Cinelerra.
FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t [W][000017893.443208][remote-node.c:632 client_node_port_use_buffers()] Failed to mlock memory 0x7fd337f04000 32832: This is not a problem but for best performance, consider increasing RLIMIT_MEMLOCK FFMPEG::open_decoder: some stream times estimated: /data/video/Diverse/20081103140154.m2t Session time: 0:19:47 Cpu time: user: 0:00:07.198 sys: 0:00:02.003 ===============
Attach two compressed screen shots:
hdv-m2t_Cin-GG_4x3.jpg shows the Format default preset and the new selected 1080i/25 preset (would next suggest to change the upper "P"s to lower case "p") Not sure about the W.Ratio=1 and H.Ratio=1, as the Cin Viewer still playback the hdv video image with Aspect 4x3 ?
Not sure too, those fields tend to change their value wildly as I select various presets. Did you load video with default 'create new resources only' strategy, or with 'replace current project'? 'Replace' indeed not autodetect Display Aspect Ratio. Try with 'Create reources only' and then drag your video into tracks on timeline... (after you set Project preset correctly). Or just select correct profile in Format after loading - it should set things correctly. I tried rendering it into h264 with correct profile - and output file comes as Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, smpte170m/unknown/unknown), 1440x1080 [SAR 4:3 DAR 16:9], 5239 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default) plays as VO: [vdpau] 1440x1080 => 1920x1080 Planar YV12 [fs] Also, when I tried to set project preferences to something else (like, preset Internet - 320x240x15 fps) and load your file - there was black screen in Compositor with Video output driver X11-OpenGL. It showed some image with X11/X11-xv ..
hdv-m2t_VLC_16x9.jpg Playback the same hdv m2t file in VLC with its Codec info. Playback the video with correct aspect 16x9 =================
Terje J. H
I updated patches at https://cloud.mail.ru/public/2ceA/4exRtrswu now if you apply DEFAULT_FORMATS-2.patch to clean source tree you should get lowercase "p/i" in presets. You can undo patch with 'cat patch.patch | patch -R -p1' It will be useful if you also test interlace_aspect_autodetect-2.patch I hope it will work for mixed-type files in same project. PS: I solved my little black screen problem - just missed dri3_disable patch for this build :}
Den 14.11.2020 08:37, skrev Andrew Randrianasulu:
I updated patches at https://cloud.mail.ru/public/2ceA/4exRtrswu
now if you apply DEFAULT_FORMATS-2.patch to clean source tree you should get lowercase "p/i" in presets.
You can undo patch with 'cat patch.patch | patch -R -p1'
It will be useful if you also test interlace_aspect_autodetect-2.patch I hope it will work for mixed-type files in same project.
PS: I solved my little black screen problem - just missed dri3_disable patch for this build :}
I saved the updated and new patches in terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> ls -1 *.patch DEFAULT_FORMATS-2.patch interlace_aspect_autodetect-2.patch and then tried to apply the first updated patch: terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> git apply DEFAULT_FORMATS-2.patch error: patch failed: cinelerra-5.1/cinelerra/defaultformats.h:39 error: cinelerra-5.1/cinelerra/defaultformats.h: patch does not apply Is it neccessary to undo the original DEFAULT_FORMATS-2.patch first? ---------- Terje J. H
В сообщении от Saturday 14 November 2020 19:43:54 Terje J. Hanssen написал(а):
Den 14.11.2020 08:37, skrev Andrew Randrianasulu:
I updated patches at https://cloud.mail.ru/public/2ceA/4exRtrswu
now if you apply DEFAULT_FORMATS-2.patch to clean source tree you should get lowercase "p/i" in presets.
You can undo patch with 'cat patch.patch | patch -R -p1'
It will be useful if you also test interlace_aspect_autodetect-2.patch I hope it will work for mixed-type files in same project.
PS: I solved my little black screen problem - just missed dri3_disable patch for this build :}
I saved the updated and new patches in
terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> ls -1 *.patch DEFAULT_FORMATS-2.patch interlace_aspect_autodetect-2.patch
and then tried to apply the first updated patch:
terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> git apply DEFAULT_FORMATS-2.patch error: patch failed: cinelerra-5.1/cinelerra/defaultformats.h:39 error: cinelerra-5.1/cinelerra/defaultformats.h: patch does not apply
Is it neccessary to undo the original DEFAULT_FORMATS-2.patch first?
Sadly, yes.
----------
Terje J. H
Den 14.11.2020 20:25, skrev Andrew Randrianasulu:
В сообщении от Saturday 14 November 2020 19:43:54 Terje J. Hanssen написал(а):
Den 14.11.2020 08:37, skrev Andrew Randrianasulu:
I updated patches at https://cloud.mail.ru/public/2ceA/4exRtrswu
now if you apply DEFAULT_FORMATS-2.patch to clean source tree you should get lowercase "p/i" in presets.
You can undo patch with 'cat patch.patch | patch -R -p1'
It will be useful if you also test interlace_aspect_autodetect-2.patch I hope it will work for mixed-type files in same project.
PS: I solved my little black screen problem - just missed dri3_disable patch for this build :}
I saved the updated and new patches in
terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> ls -1 *.patch DEFAULT_FORMATS-2.patch interlace_aspect_autodetect-2.patch
and then tried to apply the first updated patch:
terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> git apply DEFAULT_FORMATS-2.patch error: patch failed: cinelerra-5.1/cinelerra/defaultformats.h:39 error: cinelerra-5.1/cinelerra/defaultformats.h: patch does not apply
Is it neccessary to undo the original DEFAULT_FORMATS-2.patch first? Sadly, yes.
Sorry, I try to understand what to do with the mentioned undo patch command cat patch.patch | patch -R -p1 What I have saved are terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> ls -1 DEFAULT* DEFAULT_FORMATS-2.patch DEFAULT_FORMATS-2.patch_old where the first one listed is the new patch, the latter is the renamed, already installed version (I did rename it to keep it without overwriting of the new patch with the same name and version) Before doing anything wrong, what should the undo command line be? Possibly I have to rename the new patch first, DEFAULT_FORMATS-2.patch_new and keep the old as DEFAULT_FORMATS-2.patch before running the undo command? Terje J. H
В сообщении от Saturday 14 November 2020 23:52:32 Terje J. Hanssen написал(а):
Den 14.11.2020 20:25, skrev Andrew Randrianasulu:
В сообщении от Saturday 14 November 2020 19:43:54 Terje J. Hanssen написал(а):
Den 14.11.2020 08:37, skrev Andrew Randrianasulu:
I updated patches at https://cloud.mail.ru/public/2ceA/4exRtrswu
now if you apply DEFAULT_FORMATS-2.patch to clean source tree you should get lowercase "p/i" in presets.
You can undo patch with 'cat patch.patch | patch -R -p1'
It will be useful if you also test interlace_aspect_autodetect-2.patch I hope it will work for mixed-type files in same project.
PS: I solved my little black screen problem - just missed dri3_disable patch for this build :}
I saved the updated and new patches in
terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> ls -1 *.patch DEFAULT_FORMATS-2.patch interlace_aspect_autodetect-2.patch
and then tried to apply the first updated patch:
terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> git apply DEFAULT_FORMATS-2.patch error: patch failed: cinelerra-5.1/cinelerra/defaultformats.h:39 error: cinelerra-5.1/cinelerra/defaultformats.h: patch does not apply
Is it neccessary to undo the original DEFAULT_FORMATS-2.patch first? Sadly, yes.
Sorry, I try to understand what to do with the mentioned undo patch command
cat patch.patch | patch -R -p1
What I have saved are
terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> ls -1 DEFAULT* DEFAULT_FORMATS-2.patch DEFAULT_FORMATS-2.patch_old
where the first one listed is the new patch, the latter is the renamed, already installed version (I did rename it to keep it without overwriting of the new patch with the same name and version)
Before doing anything wrong, what should the undo command line be? Possibly I have to rename the new patch first, DEFAULT_FORMATS-2.patch_new and keep the old as DEFAULT_FORMATS-2.patch before running the undo command?
I think exact patch name is not important, as long as you remember old vs new. In my case I reverted patch like this guest@slax:/dev/shm/cinelerra$ cat ~/botva/src/cinelerra-git/cin-5/DEFAULT_FORMATS-2.patch | patch -R -p1 patching file cinelerra-5.1/cinelerra/defaultformats.h guest@slax:/dev/shm/cinelerra$ when I did it wrong (from wrong point in tree) it complained like this: guest@slax:/dev/shm/cinelerra$ cat ~/botva/src/cinelerra-git/cin-5/DEFAULT_FORMATS-2.patch | patch -R -p0 can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff --git a/cinelerra-5.1/cinelerra/defaultformats.h b/cinelerra-5.1/cinelerra/defaultformats.h |index 61bd2165..b963decd 100644 |--- a/cinelerra-5.1/cinelerra/defaultformats.h |+++ b/cinelerra-5.1/cinelerra/defaultformats.h -------------------------- File to patch: ^C I ctrl-c (interrupted) it. with git you probbaly can say 'git clean -fdx' and then 'git reset --hard' but this will wipe out anything from your working tree (not in git index), so use with extreme caution .... https://git-scm.com/docs/git-clean/2.23.0
Terje J. H
Den 14.11.2020 22:56, skrev Andrew Randrianasulu:
В сообщении от Saturday 14 November 2020 23:52:32 Terje J. Hanssen написал(а):
Den 14.11.2020 20:25, skrev Andrew Randrianasulu:
В сообщении от Saturday 14 November 2020 19:43:54 Terje J. Hanssen написал(а):
Den 14.11.2020 08:37, skrev Andrew Randrianasulu:
I updated patches at https://cloud.mail.ru/public/2ceA/4exRtrswu
now if you apply DEFAULT_FORMATS-2.patch to clean source tree you should get lowercase "p/i" in presets.
You can undo patch with 'cat patch.patch | patch -R -p1'
It will be useful if you also test interlace_aspect_autodetect-2.patch I hope it will work for mixed-type files in same project.
PS: I solved my little black screen problem - just missed dri3_disable patch for this build :}
I saved the updated and new patches in
terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> ls -1 *.patch DEFAULT_FORMATS-2.patch interlace_aspect_autodetect-2.patch
and then tried to apply the first updated patch:
terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> git apply DEFAULT_FORMATS-2.patch error: patch failed: cinelerra-5.1/cinelerra/defaultformats.h:39 error: cinelerra-5.1/cinelerra/defaultformats.h: patch does not apply
Is it neccessary to undo the original DEFAULT_FORMATS-2.patch first? Sadly, yes.
Sorry, I try to understand what to do with the mentioned undo patch command
cat patch.patch | patch -R -p1
What I have saved are
terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> ls -1 DEFAULT* DEFAULT_FORMATS-2.patch DEFAULT_FORMATS-2.patch_old
where the first one listed is the new patch, the latter is the renamed, already installed version (I did rename it to keep it without overwriting of the new patch with the same name and version)
Before doing anything wrong, what should the undo command line be? Possibly I have to rename the new patch first, DEFAULT_FORMATS-2.patch_new and keep the old as DEFAULT_FORMATS-2.patch before running the undo command? I think exact patch name is not important, as long as you remember old vs new.
In my case I reverted patch like this
guest@slax:/dev/shm/cinelerra$ cat ~/botva/src/cinelerra-git/cin-5/DEFAULT_FORMATS-2.patch | patch -R -p1 patching file cinelerra-5.1/cinelerra/defaultformats.h guest@slax:/dev/shm/cinelerra$
when I did it wrong (from wrong point in tree) it complained like this:
guest@slax:/dev/shm/cinelerra$ cat ~/botva/src/cinelerra-git/cin-5/DEFAULT_FORMATS-2.patch | patch -R -p0 can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff --git a/cinelerra-5.1/cinelerra/defaultformats.h b/cinelerra-5.1/cinelerra/defaultformats.h |index 61bd2165..b963decd 100644 |--- a/cinelerra-5.1/cinelerra/defaultformats.h |+++ b/cinelerra-5.1/cinelerra/defaultformats.h -------------------------- File to patch: ^C
I ctrl-c (interrupted) it.
with git you probbaly can say 'git clean -fdx' and then 'git reset --hard' but this will wipe out anything from your working tree (not in git index), so use with extreme caution ....
First I got the same complaint as above. Possibly I had moved the patches on level down to /src/cin5/cinelerra/cinelerra-5.1 after patching. Moved it up one level again and tried to undo the old and apply the new. This time undo and apply seemed to work, and configured again (... should I configure ?). But after starting ./cin again, the Format Preset menu did still show uppercase "P". Could you possibly have a look in my attached file, Patching_term_output, in case there is something wrong? The initial commands were just to verify that the patch version names were correct according to content. (if "2" in DEFAULT_FORMATS-2.patch is version number, shouldn't the latter had version "3" ?) Or is it possible to search for if the new patch really has applied changes in the source tree? Terje
В сообщении от Sunday 15 November 2020 02:53:28 Terje J. Hanssen написал(а):
Den 14.11.2020 22:56, skrev Andrew Randrianasulu:
В сообщении от Saturday 14 November 2020 23:52:32 Terje J. Hanssen написал(а):
Den 14.11.2020 20:25, skrev Andrew Randrianasulu:
В сообщении от Saturday 14 November 2020 19:43:54 Terje J. Hanssen написал(а):
Den 14.11.2020 08:37, skrev Andrew Randrianasulu:
I updated patches at https://cloud.mail.ru/public/2ceA/4exRtrswu
now if you apply DEFAULT_FORMATS-2.patch to clean source tree you should get lowercase "p/i" in presets.
You can undo patch with 'cat patch.patch | patch -R -p1'
It will be useful if you also test interlace_aspect_autodetect-2.patch I hope it will work for mixed-type files in same project.
PS: I solved my little black screen problem - just missed dri3_disable patch for this build :}
I saved the updated and new patches in
terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> ls -1 *.patch DEFAULT_FORMATS-2.patch interlace_aspect_autodetect-2.patch
and then tried to apply the first updated patch:
terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> git apply DEFAULT_FORMATS-2.patch error: patch failed: cinelerra-5.1/cinelerra/defaultformats.h:39 error: cinelerra-5.1/cinelerra/defaultformats.h: patch does not apply
Is it neccessary to undo the original DEFAULT_FORMATS-2.patch first? Sadly, yes.
Sorry, I try to understand what to do with the mentioned undo patch command
cat patch.patch | patch -R -p1
What I have saved are
terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> ls -1 DEFAULT* DEFAULT_FORMATS-2.patch DEFAULT_FORMATS-2.patch_old
where the first one listed is the new patch, the latter is the renamed, already installed version (I did rename it to keep it without overwriting of the new patch with the same name and version)
Before doing anything wrong, what should the undo command line be? Possibly I have to rename the new patch first, DEFAULT_FORMATS-2.patch_new and keep the old as DEFAULT_FORMATS-2.patch before running the undo command? I think exact patch name is not important, as long as you remember old vs new.
In my case I reverted patch like this
guest@slax:/dev/shm/cinelerra$ cat ~/botva/src/cinelerra-git/cin-5/DEFAULT_FORMATS-2.patch | patch -R -p1 patching file cinelerra-5.1/cinelerra/defaultformats.h guest@slax:/dev/shm/cinelerra$
when I did it wrong (from wrong point in tree) it complained like this:
guest@slax:/dev/shm/cinelerra$ cat ~/botva/src/cinelerra-git/cin-5/DEFAULT_FORMATS-2.patch | patch -R -p0 can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff --git a/cinelerra-5.1/cinelerra/defaultformats.h b/cinelerra-5.1/cinelerra/defaultformats.h |index 61bd2165..b963decd 100644 |--- a/cinelerra-5.1/cinelerra/defaultformats.h |+++ b/cinelerra-5.1/cinelerra/defaultformats.h -------------------------- File to patch: ^C
I ctrl-c (interrupted) it.
with git you probbaly can say 'git clean -fdx' and then 'git reset --hard' but this will wipe out anything from your working tree (not in git index), so use with extreme caution ....
First I got the same complaint as above. Possibly I had moved the patches on level down to /src/cin5/cinelerra/cinelerra-5.1 after patching. Moved it up one level again and tried to undo the old and apply the new.
This time undo and apply seemed to work, and configured again (... should I configure ?).
I think 'git apply -v' is more useful - it will tell you if it skipped patch (did this for me few times) I also think you forgot 'make'. Depend on specific files you changed 'make' may rebuild them, or I was forced to do this in cinelerra: guest@slax:/dev/shm/cinelerra/cinelerra-5.1/cinelerra$ setarch i686 make clean && make -j 5 'setarch i686' because I build x86 program on system running x86_64 kernel, you can omit this. You can run cin from there. I found it slightly easier for console-based editing to just 'mcedit file', rerun this 'make clean /make' route, and launch ../bin/cin Of course I think multi-document editor (like kate from KDE) is better because you can have few files open at once, but it seems I slip back to old DOS habits often ....
But after starting ./cin again, the Format Preset menu did still show uppercase "P".
Could you possibly have a look in my attached file, Patching_term_output, in case there is something wrong?
The initial commands were just to verify that the patch version names were correct according to content. (if "2" in DEFAULT_FORMATS-2.patch is version number, shouldn't the latter had version "3" ?)
Yes, it should, but I decided to just owerwrite old version - there was no change in logic, hopefully, just cosmetics.
Or is it possible to search for if the new patch really has applied changes in the source tree?
You can look into this file cinelerra-5.1/cinelerra/defaultformats.h with your favourite editor...
Terje
Den 15.11.2020 04:13, skrev Andrew Randrianasulu:
В сообщении от Sunday 15 November 2020 02:53:28 Terje J. Hanssen написал(а):
Den 14.11.2020 22:56, skrev Andrew Randrianasulu:
В сообщении от Saturday 14 November 2020 23:52:32 Terje J. Hanssen написал(а):
Den 14.11.2020 20:25, skrev Andrew Randrianasulu:
В сообщении от Saturday 14 November 2020 19:43:54 Terje J. Hanssen написал(а):
Den 14.11.2020 08:37, skrev Andrew Randrianasulu: > I updated patches at https://cloud.mail.ru/public/2ceA/4exRtrswu > > now if you apply DEFAULT_FORMATS-2.patch to clean source tree you should get lowercase "p/i" in presets. > > You can undo patch with 'cat patch.patch | patch -R -p1' > > It will be useful if you also test interlace_aspect_autodetect-2.patch > I hope it will work for mixed-type files in same project. > > PS: I solved my little black screen problem - just missed dri3_disable patch for this build :} > I saved the updated and new patches in
terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> ls -1 *.patch DEFAULT_FORMATS-2.patch interlace_aspect_autodetect-2.patch
and then tried to apply the first updated patch:
terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> git apply DEFAULT_FORMATS-2.patch error: patch failed: cinelerra-5.1/cinelerra/defaultformats.h:39 error: cinelerra-5.1/cinelerra/defaultformats.h: patch does not apply
Is it neccessary to undo the original DEFAULT_FORMATS-2.patch first? Sadly, yes.
Sorry, I try to understand what to do with the mentioned undo patch command
cat patch.patch | patch -R -p1
What I have saved are
terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1> ls -1 DEFAULT* DEFAULT_FORMATS-2.patch DEFAULT_FORMATS-2.patch_old
where the first one listed is the new patch, the latter is the renamed, already installed version (I did rename it to keep it without overwriting of the new patch with the same name and version)
Before doing anything wrong, what should the undo command line be? Possibly I have to rename the new patch first, DEFAULT_FORMATS-2.patch_new and keep the old as DEFAULT_FORMATS-2.patch before running the undo command? I think exact patch name is not important, as long as you remember old vs new.
In my case I reverted patch like this
guest@slax:/dev/shm/cinelerra$ cat ~/botva/src/cinelerra-git/cin-5/DEFAULT_FORMATS-2.patch | patch -R -p1 patching file cinelerra-5.1/cinelerra/defaultformats.h guest@slax:/dev/shm/cinelerra$
when I did it wrong (from wrong point in tree) it complained like this:
guest@slax:/dev/shm/cinelerra$ cat ~/botva/src/cinelerra-git/cin-5/DEFAULT_FORMATS-2.patch | patch -R -p0 can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff --git a/cinelerra-5.1/cinelerra/defaultformats.h b/cinelerra-5.1/cinelerra/defaultformats.h |index 61bd2165..b963decd 100644 |--- a/cinelerra-5.1/cinelerra/defaultformats.h |+++ b/cinelerra-5.1/cinelerra/defaultformats.h -------------------------- File to patch: ^C
I ctrl-c (interrupted) it.
with git you probbaly can say 'git clean -fdx' and then 'git reset --hard' but this will wipe out anything from your working tree (not in git index), so use with extreme caution ....
First I got the same complaint as above. Possibly I had moved the patches on level down to /src/cin5/cinelerra/cinelerra-5.1 after patching. Moved it up one level again and tried to undo the old and apply the new.
This time undo and apply seemed to work, and configured again (... should I configure ?). I think 'git apply -v' is more useful - it will tell you if it skipped patch (did this for me few times)
I also think you forgot 'make'. Depend on specific files you changed 'make' may rebuild them, or I was forced to do this in cinelerra:
guest@slax:/dev/shm/cinelerra/cinelerra-5.1/cinelerra$ setarch i686 make clean && make -j 5
'setarch i686' because I build x86 program on system running x86_64 kernel, you can omit this.
You can run cin from there. I found it slightly easier for console-based editing to just 'mcedit file', rerun this 'make clean /make' route, and launch
../bin/cin
Of course I think multi-document editor (like kate from KDE) is better because you can have few files open at once, but it seems I slip back to old DOS habits often ....
Sorry, I'm stuck; obviously I have managed to get something wrong, but what? It seems the patch should be applied, but the Format menu still shows me uppercase "P" Attach two new terminal outputs.: * Patching_term_output_2 * Patching_term_output_3 make clean && make -j 5 was possible to run in case _2 but not for _3. In the latter case _3 I also tried 'make install' without success.
But after starting ./cin again, the Format Preset menu did still show uppercase "P".
Could you possibly have a look in my attached file, Patching_term_output, in case there is something wrong?
The initial commands were just to verify that the patch version names were correct according to content. (if "2" in DEFAULT_FORMATS-2.patch is version number, shouldn't the latter had version "3" ?) Yes, it should, but I decided to just owerwrite old version - there was no change in logic, hopefully, just cosmetics.
Or is it possible to search for if the new patch really has applied changes in the source tree? You can look into this file cinelerra-5.1/cinelerra/defaultformats.h
with your favourite editor...
Tested it with grep 1080p cinelerra-5.1/cinelerra/defaultformats.h which was hit
Terje
Sorry, I'm stuck; obviously I have managed to get something wrong, but what?
It seems the patch should be applied, but the Format menu still shows me uppercase "P"
Attach two new terminal outputs.:
* Patching_term_output_2 * Patching_term_output_3
It seems in both cases you run cin from your system installation, because it says: Cinelerra Infinity - built: Oct 31 2020 10:49:15 try full autogen/configure/make/make install route... it should say something like this guest@slax:/dev/shm/cinelerra/cinelerra-5.1/cinelerra$ ../bin/cin Cinelerra Infinity - built: Nov 15 2020 06:34:23 those leading dots in './program' and '../path/program' actually quite important if you want to launch specific instance. do not strip them
make clean && make -j 5 was possible to run in case _2 but not for _3.
In the latter case _3 I also tried 'make install' without success.
But after starting ./cin again, the Format Preset menu did still show uppercase "P".
Could you possibly have a look in my attached file, Patching_term_output, in case there is something wrong?
The initial commands were just to verify that the patch version names were correct according to content. (if "2" in DEFAULT_FORMATS-2.patch is version number, shouldn't the latter had version "3" ?) Yes, it should, but I decided to just owerwrite old version - there was no change in logic, hopefully, just cosmetics.
Or is it possible to search for if the new patch really has applied changes in the source tree? You can look into this file cinelerra-5.1/cinelerra/defaultformats.h
with your favourite editor...
Tested it with grep 1080p cinelerra-5.1/cinelerra/defaultformats.h which was hit
Terje
Den 15.11.2020 15:29, skrev Andrew Randrianasulu:
Sorry, I'm stuck; obviously I have managed to get something wrong, but what?
It seems the patch should be applied, but the Format menu still shows me uppercase "P"
Attach two new terminal outputs.:
* Patching_term_output_2 * Patching_term_output_3
It seems in both cases you run cin from your system installation, because it says:
Cinelerra Infinity - built: Oct 31 2020 10:49:15
try full autogen/configure/make/make install route...
it should say something like this
guest@slax:/dev/shm/cinelerra/cinelerra-5.1/cinelerra$ ../bin/cin Cinelerra Infinity - built: Nov 15 2020 06:34:23
those leading dots in './program' and '../path/program' actually quite important if you want to launch specific instance. do not strip them
Thanks, you're right. How could I oversee the new path today 😅 I just enterted the path to the actual cin, and the Format Preset was ok with 'p'. terje@alfa:~> cd /home/terje/src/cin5/cinelerra/cinelerra-5.1/bin terje@alfa:~/src/cin5/cinelerra/cinelerra-5.1/bin> ./cin Cinelerra Infinity - built: Nov 15 2020 11:56:16 git://git.cinelerra-gg.org/goodguy/cinelerra.git Now I have also created a specific 'Cin-GG_Build' app launcher with Alacarte and put it on the Gnome program menu and the handy favorite panel. For later on, will it possibly be ok to 'undo' and 'git apply' several patches first, before a single, final autogen/configure/make/make install route... ? --------------- Terje J. H
participants (3)
-
Andrew Randrianasulu -
Pierre autourduglobe -
Terje J. Hanssen