On Sunday, May 15, 2022, Andrea paz wrote:
> > just add this line (-DWITH_JASPER=OFF) without '+' to your opencv_build
> file in cinegg src root...?
>
> I tried adding the line with jasper in opencv_build and then compiling
> CinGG. The result is the same: the OpenCV plugins are not present.
On Sunday, May 15, 2022, Andrea paz wrote:
> > do you have jasper3 or jasper2 lib on your system?
> I have jasper2 on my system.
> > Have you tried my modification for opencv_build disabling jasper support
> there?
> Sorry, I didn't understand how to do it!
>
just add this line
> do you have jasper3 or jasper2 lib on your system?
I have jasper2 on my system.
> Have you tried my modification for opencv_build disabling jasper support
> there?
Sorry, I didn't understand how to do it!
--
Cin mailing list
Cin@lists.cinelerra-gg.org
On Sunday, May 15, 2022, Andrea paz wrote:
> The past week and next week I will not have much time; I apologize.
>
this is ok, have (good) life!
I tried to compile CinGG and everything is OK.
> I tried to compile with OpenCV taken from CinGG's git
>
The past week and next week I will not have much time; I apologize.
I tried to compile CinGG and everything is OK.
I tried to compile with OpenCV taken from CinGG's git
(--with-opencv=sta,tar=
http://cinelerra-gg.org/download/opencv/opencv-20200306.tgz) and, although
the build gives no errors, the
Checked into GIT netbsd patch and bld from:
0031-Patches-for-attempting-to-make-netbsd-i386-compile.patch
Initially I panicked when I did a grep for 'diff' but today I figured it
out as all of the diffs where located in the patch so I was relieved.
Later if Andrew makes changes, probably should
On Saturday, May 14, 2022, Phyllis Smith wrote:
> Checked into GIT, the ffmpeg versioning mods - this is a very useful
> feature for using one version of ffmpeg but being able to test the upcoming
> version. Also, mods for allowing for OpenEXR version 3.
>
so, current git should be mostly
Checked into GIT, the ffmpeg versioning mods - this is a very useful
feature for using one version of ffmpeg but being able to test the upcoming
version. Also, mods for allowing for OpenEXR version 3. Patches now
included are:
0025-Make-cin-compile-with-ffmpeg-5-unconditionally.patch
On Wednesday, May 11, 2022, Andrew Randrianasulu
wrote:
>
>
> On Wednesday, May 11, 2022, Phyllis Smith wrote:
>
>> Checked into GIT, LV2 building changes + 4 additional to Calf LV2 plugins
>> that I discovered while testing. They did not cause CinGG to crash EXCEPT
>> when using the Calf LV2
On Wednesday, May 11, 2022, Phyllis Smith wrote:
> Status of other 18 patches from the Megapile:
>
> *Bluray Truehd:*
> 0002-Improve-truehd-decoder-encoder-from-ffmpeg.git.patch -- *not quite
> working; setting aside*
> *Netbsd Compile;*
>
Status of other 18 patches from the Megapile:
*Bluray Truehd:*
0002-Improve-truehd-decoder-encoder-from-ffmpeg.git.patch -- *not quite
working; setting aside*
*Netbsd Compile;*
0031-Patches-for-attempting-to-make-netbsd-i386-compile.patch -- *25+
files/have to study*
*Ffmpeg Versioning:*
On Wednesday, May 11, 2022, Phyllis Smith wrote:
> Checked into GIT, LV2 building changes + 4 additional to Calf LV2 plugins
> that I discovered while testing. They did not cause CinGG to crash EXCEPT
> when using the Calf LV2 plugins with an AppImage.When using from a
> self-build, they
Checked into GIT, LV2 building changes + 4 additional to Calf LV2 plugins
that I discovered while testing. They did not cause CinGG to crash EXCEPT
when using the Calf LV2 plugins with an AppImage.When using from a
self-build, they did not show up in Audio Effects but reported the error
Checked into GIT even more from the Megapile:
0027-Hopefully-fixed-dynamic-liba52.patch
0029-Hopefully-fix-dyn-liba52-on-termux.patch
0032-video4linux2-and-DVB-support-currently-depend-on-lib.patch
0033-Try-to-abort-earlier-if-xinerama-xfixes-support-not-.patch
On Saturday, May 7, 2022, Phyllis Smith wrote:
> \0/ \0/ (me and Buddy waving wow)
> Checked into GIT the following (thank you Andrew for these many fixes;
> please check cinelerra/Makefile to make sure no mistakes)
>
> 0010-filegif-addition-of-nearly-all-quntize.c-from-giflib.patch
>
>
well,
\0/ \0/ (me and Buddy waving wow)
Checked into GIT the following (thank you Andrew for these many fixes;
please check cinelerra/Makefile to make sure no mistakes)
0010-filegif-addition-of-nearly-all-quntize.c-from-giflib.patch
0018-pkg-config-based-dynamic-openexr-link-fix-for-freebs.patch
On Saturday, May 7, 2022, Phyllis Smith wrote:
> Andrew,
> I do not understand what WANT_CIN_3RDPARTY is
>
>
variable telling buildsystem we want to build/link with libraries in
thirdparty folder (our default)
>
>
>
> and consequently do not know whether adding patch:
>
Andrew,
I do not understand what WANT_CIN_3RDPARTY is and consequently do not know
whether adding patch:
0024-Add-android-only-hacked-Dynamic-makefile-libs.patch (along with
0018)
for additional LIBS will affect other people who ae doing their own
builds. What I am concerned about is in bold
On Friday, May 6, 2022, Phyllis Smith wrote:
> Andrew
>
>> \0/
>>>
>> What does the above symbol mean?
>
hands up/waving as in 'wow, very cool' (found on irc long time ago)
>
>>> thanks, will test on tablet just now
>>>
>>
>> hm, I think dynamic blds need to disable libdpx for now...
>>
>
Andrew
> \0/
>>
> What does the above symbol mean?
>
>> thanks, will test on tablet just now
>>
>
> hm, I think dynamic blds need to disable libdpx for now...
>
There are more patches to termux that I have NOT put in from the Megapile,
so not sure how well the build will work ?
--
Cin
On Friday, May 6, 2022, Andrew Randrianasulu
wrote:
>
>
> On Friday, May 6, 2022, Phyllis Smith wrote:
>
>> Checked into GIT from the current Megapile_12, the following:
>>
>> 0020-update-blds-bsd.bld-for-freebsd-13.patch
>> 0021-Attempt-at-adding-freebsd-detect-in-plugins-Makefile.patch
>>
On Friday, May 6, 2022, Phyllis Smith wrote:
> Checked into GIT from the current Megapile_12, the following:
>
> 0020-update-blds-bsd.bld-for-freebsd-13.patch
> 0021-Attempt-at-adding-freebsd-detect-in-plugins-Makefile.patch
> 0022-Attempt-at-freebsd-netbsd-detection-in-cinelerra-Mak.patch +
>
Checked into GIT from the current Megapile_12, the following:
0020-update-blds-bsd.bld-for-freebsd-13.patch
0021-Attempt-at-adding-freebsd-detect-in-plugins-Makefile.patch
0022-Attempt-at-freebsd-netbsd-detection-in-cinelerra-Mak.patch +
+
thanks!
On Wednesday, May 4, 2022, Phyllis Smith wrote:
> Checked into GIT from the current Megapile, the following:
>
> 0004-mem-and-resource-leaks-in-indexfile-indextate-cppche.patch
> 0005-cppcheck-in-cursor.C.patch
> 0006-cppcheck-in-resourcepixmap.C.patch
>
Checked into GIT from the current Megapile, the following:
0004-mem-and-resource-leaks-in-indexfile-indextate-cppche.patch
0005-cppcheck-in-cursor.C.patch
0006-cppcheck-in-resourcepixmap.C.patch
0007-Add-objrem-target-for-thirdparty-Makefile-removes-on.patch
On Tuesday, May 3, 2022, Phyllis Smith wrote:
> Andrew,
> Using the last email fix suggestion (and ignoring the previous to that
> email suggestion), bdwrite no longer crashes but there is an error message:
>
> + mount -t udf -o loop /tmp/bd_20220502-191150/bd.udfs
> /tmp/bd_20220502-191150/udfs
Andrew,
Using the last email fix suggestion (and ignoring the previous to that
email suggestion), bdwrite no longer crashes but there is an error message:
+ mount -t udf -o loop /tmp/bd_20220502-191150/bd.udfs
/tmp/bd_20220502-191150/udfs
+ bdwrite /tmp/bd_20220502-191150/udfs
actually, after making one more test it seems I can avoid fatal error (in
exchange for non-fatal error) by changing bdwrite like this
$ cat bdwrite_truehd/0001-Workaround-for-pure-truehd.patch
>From 218966843cd1537e0d0fea80aba1e1717efaaae3 Mon Sep 17 00:00:00 2001
From: Andrew Randrianasulu
does this patch fix 0ch issue without breaking other cases?
$ git diff bdwrite.C
diff --git a/cinelerra-5.1/cinelerra/bdwrite.C
b/cinelerra-5.1/cinelerra/bdwrite.C
index 1017c169..cebee789 100644
--- a/cinelerra-5.1/cinelerra/bdwrite.C
+++ b/cinelerra-5.1/cinelerra/bdwrite.C
@@ -2639,6 +2639,8 @@
On Monday, May 2, 2022, Phyllis Smith wrote:
> Andrew, what other software has to be installed to get Truehd to work?
> Andrea does not get the error I do so there must be something additional
> that has to be installed. We need to know for documentation.
>
i tried with tsmuxer, but I guess
Andrew, what other software has to be installed to get Truehd to work?
Andrea does not get the error I do so there must be something additional
that has to be installed. We need to know for documentation.
On Mon, May 2, 2022 at 12:42 PM Andrew Randrianasulu <
randrianas...@gmail.com> wrote:
>
I added to megapile_12 the patch 0001-.
I uncommented the line with "truehd" in bdcreate.C
I built CinGG without problems.
I started CinGG from root.
In BD Render the profile "truehd" appeared. The render progresses up
to 100% then there is a crash. At the terminal I have:
well, this is not exactly what we hoped for.. in this case.
sorry TWO issues going on
1) tsmuxer choke on ffmpeg's lpcm as encoded without ONE MORE PATCH..
2) truehd encoder in ffmoeg may trip bdwrite...
for truehd encoder you need to either uncomment line in bdcreate.C {with
truehd profile,
> can you confirm it contain trueHD audio (run mediainfo)?
ffprobe:
Stream #0:1[0x1100](ita): Audio: pcm_bluray ([128][0][0][0] / 0x0080),
48000 Hz, stereo, s16, 1536 kb/s
mediainfo:
Audio
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
On Monday, May 2, 2022, Andrea paz wrote:
> @Phyllis Smith
> Here what I get after installing udftools (which contains mkudffs):
>
> Render::render_single: Session finished.
> ** rendered 917 frames in 14.627 secs, 62.692 fps
> ++ dirname /tmp/bd_20220502-192458/bd.sh
> +
@Phyllis Smith
Here what I get after installing udftools (which contains mkudffs):
Render::render_single: Session finished.
** rendered 917 frames in 14.627 secs, 62.692 fps
++ dirname /tmp/bd_20220502-192458/bd.sh
+ sdir=/tmp/bd_20220502-192458
++ cd /tmp/bd_20220502-192458
++ pwd
+
On Monday, May 2, 2022, Andrea paz via Cin
wrote:
> @andrew
> I didn't quite understand your truehd audio example. I took 2 pcm s16
> files I loaded them in CinGG and burned them as truehd: I have no
> errors and the rendering I loaded it again in CinGG with no errors. I
> don't think this is
I think depend on distro mkudffs can be only visible/usable by root...
at least on Slackware it wokjs this way...
On Monday, May 2, 2022, Phyllis Smith via Cin
wrote:
> Andrea, you will have to install 'mkudffs' if you don't mind. I looked on
> the internet, and it appears to be available for
On Monday, May 2, 2022, Andrea paz via Cin
wrote:
> @andrew
> I didn't quite understand your truehd audio example. I took 2 pcm s16
> files I loaded them in CinGG and burned them as truehd: I have no
> errors and the rendering I loaded it again in CinGG with no errors. I
> don't think this is
Andrea, you will have to install 'mkudffs' if you don't mind. I looked on
the internet, and it appears to be available for Arch.
Following Phyllis' instructions (BD render) I render up to 100% and
> then I have these errors (from root):
>
>
> + mkudffs -b 2048 /tmp/bd_20220502-182538/bd.udfs
Andrea -- Oops, you do have to be "root" unless you do the workaround as
described in the manual but this is just a simple one time test to see if
you have the same problem that I do.
On Mon, May 2, 2022 at 9:36 AM Phyllis Smith
wrote:
> *Andrea,* since you have the megapatches all in, could
*Andrea,* since you have the megapatches all in, could you run the binary
and test "truehd"? These are the steps:
load file
File-> BD Render
Profile - use down arrow to choose *Truehd* and take rest of defaults
Ignore Warning about root because you do not need to actually create
On Monday, May 2, 2022, Phyllis Smith wrote:
> We can NOT make LV2 a requirement because the plugins are too unreliable -
> just like we can not make OpenCV a requirement.
> When patching the LV2 patches from the pile - which is the following:
>0052-Defend-against-missed-lv2-headers.patch
>
We can NOT make LV2 a requirement because the plugins are too unreliable -
just like we can not make OpenCV a requirement.
When patching the LV2 patches from the pile - which is the following:
0052-Defend-against-missed-lv2-headers.patch
0056-Attempt-at-fixing-lv2-detection.patch
On Monday, May 2, 2022, Andrea paz wrote:
> Tried the build with megapatch_12. Everything OK: it compiles without
> errors.
> I enclose cin5_ffmpeg4.log. There are many "warning+error" concerning
> Latex and the html manual and many "warning" concerning c++. I don't
> know if they are important
45 matches
Mail list logo
