Re: [Cin] New release update
I did some builds with the new version; I compiled with/without “--enable-libsvtav1” and with/without the “multibit” patch. All OK. Before a start I integrated the contextHelp. The following 2 errors appeared: Gtk-Message: 13:59:05.609: Failed to load module "window-decorations-gtk-module" Gtk-Message: 13:59:05.609: Failed to load module "colorreload-gtk-module" Considering that I use KDE and everything works fine, I would say this is normal. Appimage also works fine, including rendering with av1_svt. Thank you, Phyllis. PS: I have to change the elevator bulb, but I don't feel like it... ; ) -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Changes in manual
> Note to Andrea, is this a correct change that I made? Previously it had been > "cin -d 10650 cin -d 10651" on the same line. Yes, it is correct. Thanks. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] AOM SVT-AV1 2.1 Released
Dav1d (decoder) is also promising, at least for cpu's that take advantage of AVX: https://code.videolan.org/videolan/dav1d/-/releases/1.4.2 -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] Changes in manual
I changed the render farm section according to chapolin's suggestions, see if it's okay. https://www.cinelerra-gg.org/forum/help-video/how-to-do-for-a-fast-rendering/#post-2797 Rendering.tar.gz Description: application/gzip -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 soon to be released
All OK, for me. Thanks you. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Chromakey improvements checked in to GIT
To add the explanation of the new keys and equalize the presentation
to what was done for ChromaKey-HSV, I updated the manual for the
ChromaKey plugin. You just need to replace the entry in Latex.
\subsection{Chroma Key}%
\label{sub:chroma_key}
\index{chroma key}
This effect erases pixels which match the selected color. They are replaced
with black if there is no alpha channel and transparency if there is an alpha
channel. In this case, you create a matte in the alpha channel, which is not
visible to us. The selection of color model is important to determine the
behavior (figure~\ref{fig:chroma-key}).
\begin{figure}[htpb]
\centering
\includegraphics[width=0.5\linewidth]{chroma-key.png}
\caption{Chroma Key control window}
\label{fig:chroma-key}
\end{figure}
Chroma key uses either the lightness or the hue to determine what is erased.
\textit{Use value} singles out only the lightness to determine transparency
(Luma Key).
\textit{Color section}
Select a key color to erase using the \textit{Color} button. Alternatively a
color can be picked directly from the output frame by first using the
\textit{color picker} in the compositor window and then selecting the
\textit{Use color picker} button. This sets the chroma key color to the current
color picker color.
Be aware that the output of the chroma key is fed back to the compositor, so
selecting a color again from the compositor will use the output of the chroma
key effect. The chroma key should be disabled when selecting colors with the
color picker.
\textit{Key parameters section}
If the lightness or hue is within a certain \textit{threshold} it is erased.
Increasing the threshold determines the range of colors to be erased. It is not
a simple on/off switch; it'a a range color. As the color approaches the edge of
the threshold, it gradually gets erased if the \textit{slope} is high or is
rapidly erased if the slope is low. The slope as defined here is the number of
extra values flanking the threshold required to go from opaque to transparent.
The \textit{Default} button returns Threshold to the value $10.0$; Slope to the
value $0.0$; and Color to black ($#ff00$). The \textit{Reset} button and
the \textit{reset} icons next to the sliders always return to the value $0.0$.
Before the sliders are the \textit{input boxes} so that the precise numerical
values can be written.
Normally threshold is very low when using a high slope. The two parameters tend
to be exclusive because slope fills in extra threshold. The slope tries to
soften the edges of the chroma key but it does not work well for compressed
sources. A popular softening technique is to use a maximum slope and chain a
blur effect below the chroma key effect to blur just the alpha.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Chromakey improvements checked in to GIT
I tried to start CinGG (ffmpeg7) in wayland. During startup I get this error:
BC_DisplayInfo::gl_fb_config failed
Error I don't have in Xorg. However, everything works normally. I've
tried both X11 and X11-OpenGL driver, but I don't notice any
difference.
As a test I put in the chroma-key plugin and observed a strange
behavior: now the threshold works from the value 40 instead of a value
just above 0. Even going back into Xorg the same behavior remains. Why
did it work correctly for me the first time and from the second test
onwards the threshold seems to shift from 0 to 40? Anyway it is not
important, I will do more tests but it is probably due to some mistake
of mine.
Instead, an important thing that I had noticed even before trying
wayland, but forgot to report in the previous email is that the
“Default” button returns the threshold to 10, as required. In
contrast, the “Reset” button on the slider brings it back to 0. This
difference can also be seen in chromakey.C :
ChromaKeyConfig::ChromaKeyConfig()
{
reset(RESET_DEFAULT_SETTINGS);
}
void ChromaKeyConfig::reset(int clear)
{
switch(clear) {
case RESET_ALL :
red = 0.0;
green = 0.0;
blue = 0.0;
threshold = 0.0;
use_value = 0;
slope = 0.0;
break;
case RESET_RGB :
red = 0.0;
green = 0.0;
blue = 0.0;
break;
case RESET_SLOPE :
slope = 0.0;
break;
case RESET_THRESHOLD :
threshold = 0.0;
break;
case RESET_DEFAULT_SETTINGS :
default:
red = 0.0;
green = 0.0;
blue = 0.0;
threshold = 10.0;
use_value = 0;
slope = 0.0;
break;
}
}
I think in each line that threshold appears the value should be raised to 10.0.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Chromakey improvements checked in to GIT
I compiled with ffmpeg 7 and patched for multi-bit. I also did a 12-bit rendering with x265. All OK. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Cinelerra-HV 9 is out!
> ... I believe that Andrea uses it frequently also with no new reported issues. Since you provided the patches I have always used CinGG compiled with ffmpeg 7. I have not found any problems. I have done rendering, background rendering and batch rendering without any problems. I have not done render farms. I have tried a few plugins both native and ffmpeg without problems. I have tried X11 and OpenGL-X11 without problems. Older or older projects give no problems. What tests should I do further? -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Audio Offset Finder
In the DaVinci Resolve manual (starting on page 425) the way they use for sync is explained. This might be a cue on how to do it in CinGG, but I don't actually know how to do it. It's not just a matter of not knowing how to write code: I don't even intuit how to do it at the idea level, at the design stage. https://documents.blackmagicdesign.com/UserManuals/DaVinci_Resolve_18_Reference_Manual.pdf -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Audio Offset Finder
> What you describe below, why not approach this from an EDL perspective? > Don't materialise it into new content just as 'clips'? And here I'm already getting lost. Do you mean that you can do everything inside CinGG? I don't know how to program, and my (stupid) attempts are nothing more than looking for some project to use together with others in a very simple script. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Audio Offset Finder
> So it builds a linear timeline?
No, just duplicate sources but with the external audio embedded and
synchronized. A little like the transcode function that asks you to
hide the original media leaving only the newly transcoded.
1- collect the files into one folder (video files with internal audio
+ external audio). Duplicate they. Calculate the length of each file
by timecode. If the external audio is not unique, concatenate and
insert blanks to maintain timecode linearity. [?]
2- Synchronize the files with the external audio track (your choice of
timecode {or waveform}). [?; you consider the external audio track to
be the "master," you synchronize the other media with reference to its
timecode. Or you take advantage of CinGG's code for "Align
Timecodes".]
3- Duplicate and trim the external audio track so that there are
coincidental chunks with every files. [?; you assign each media a
timecode based on that of the master and trim on copies of the master
for each media; ffmpeg -ss, -t, map]
4- Associate the external audio chunks with the relative files. [ffmpeg map]
5- Delete the internal audio tracks leaving only the external one. [ffmpeg map]
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Audio Offset Finder
> I don't even want to do things manually, if I have a choice ;) I have tried several times to create a script for ffmpeg that would automate the A/V sync, but I do not have the skills. See: https://www.cinelerra-gg.org/bugtracker/view.php?id=448 > So you mean that you would have an extern audio recorder, and just drop > in replace the audio from the camera? I have an old Tascam DR40, great but no timecode... > What do you mean with this? I mean a button like your "sync up" button, put in the Resources window to act on the sources. > What is post-editing in your opinion? Colour-grading, lower two thirds? Yes, Color Correction and Compositing. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Audio Offset Finder
Some time ago there was talk about OpenTimelineIO, but I can no longer find the reference. What I was thinking of, was to use Audio Offset Finder to see the gap between files and then manually impose a timecode on each asset via the appropriate "set timecode" button. At this point you can use your "sync up" (i.e., "Align Timecodes") button whenever you want. Regarding the ease of losing sync on the timeline and then having to redo it again and again, I seem to remember that it was not possible to lock audio and video together because it meant creating a new type of "A/V" track while CinGG only has "A" and "V". In contrast to what you said, in my opinion, what all open NLEs on linux lack is synchronization in pre-editing, that is, in the Resources window, working even on dozens and dozens of sources. What is also missing is the ability to automatically replace, in each source, the embedded audio track with an external audio track. But always in pre-editing, not on the timeline. In my opinion, the operations of pre-editing should be present in an NLE, while post-editing may be missing. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] Audio Offset Finder
A nice command-line tool that reads the offset between two audio tracks, thus allowing them to be manually synchronized. Unfortunately it is made with Python, but I was wondering if it is possible to import it into "i" shell commands, so as to provide sync information of the various assets. It has the Apache license. https://github.com/bbc/audio-offset-finder -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ChromakeyHSV menu much improved
With the new, beautiful, configuration window, we need to change the image in the manual. chroma-key-hsv.tar.gz Description: application/gzip -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Add to the manual
I would prefer tò remove the references tò Compositore, It serms tò me that It leads tò more confusione. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Add to the manual
I'm sorry Phyllis but I explained the Compositor thing wrong. I meant that a fourth item, that is, using the tools in the Compositing window during editing, could affect the result of the render file. Instead it does not: all operations in the Compositor window do not affect the render, only the three items that are listed have influence. I had put a sentence inside the "timeline" item because it is in the Compositor that we see the timeline and we might be led to think that these tools are also influential. But the Compositor only serves as a display for the timeline. It may be best to remove the Compositor part. Sorry for the confusion I created. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ChromakeyHSV menu much improved
> P.S. Someone indicated that ChromakeyHSV had some kind of bug, but I was > wondering if Andrea ever found out exactly what that was? since it looks OK > to me. > Great job; thank you! One problem with the plugin can be seen in the following video: https://streamable.com/yyze7y In practice, "Min Saturation" behaves like "Saturation Offset" when in fact it should behave as in the following figure: https://postimg.cc/HjZDcvr2 (Min Sat should form a new smaller wedge [dotted line], instead it creates an arc without more spike, which is the right behavior of Sat Offset). However, I always hope that we will be able to integrate Adam's new plugin, which is a great evolution of ours and works very well. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] Forum registration with HotMail
A problem with registration via HotMail was posted on the forum. https://www.cinelerra-gg.org/forum/announcements-and-updates/registration-mail-and-hotmail/#post-2756 Can anyone who has server knowledge or has HotMail give some useful pointers? -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] Add to the manual
I wrote a short introduction for chapter 7 of the manual, the one with the rendering options. I am not sure it is necessary so I am attaching, in addition to the latex version, a txt version. Judge whether it should be included. In this case it should be put at the beginning, as the first paragraph. rendering_intro.tar.gz Description: application/gzip -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] vaapi vs appimage, kdenlive way
I put the patch for vaapi, but I don't notice any change in decoding. There are no warnings in the terminal but the GPU does not affect the decoding. I used CinGG compiled, not the appimage. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Problem with the compile
With the new mjpegtools 2.2.1 the compile happens without errors. Thanks Andrew, you are always helpful. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Problem with the compile
> sounds like upgraded gcc started to misunderstand some old code? what version > of gcc you have? gcc 14.1.1+r1+g43b730b9134-2 The fact that it has all those numbers indicates that it is a particular version, perhaps not yet stable. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] vaapi vs appimage, kdenlive way
Since I don't quite understand what to do, is it possible to have a patch to compile? PS: is it possible to do something similar with vulkan? -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] Change description in av1_svt.webm preset
I changed the description present in the av1_svt.webm preset. The previous one referred to the av1.webm codec. av1_svt.mkv Description: video/matroska -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] small changes in Manual
OT I think there is a problem with server moderation of IgorV. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] Fwd: [cinelerra-cv-team] About copy-pasting from CV Manual to CGG Manual
-- Forwarded message - Da: Igor Vladimirsky Date: mar 30 apr 2024 alle ore 20:20 Subject: [cinelerra-cv-team] About copy-pasting from CV Manual to CGG Manual To: Each of my messages to the Cin-GG ML is moderated. This is why I have opened this thread here and restoring the chronology --- 28.04.2023 Andrea Paz wrote the msg to the CinGG ML. https://lists.cinelerra-gg.org/pipermail/cin/2024-April/008211.html Quote: I have updated the plugins chapter, based on IgorV's updates for the manual of Cinelerra-CV. (See: https://github.com/cinelerra-cv-team/cinelerra-cv/commits/master/doc) Check that they fit. My answer to the CinGG ML was: > Do marketers of the Cin-GG Community discourage linking to sources? I want to remind them of something. The CV manual was mostly copied (many years ago) from the HV-manual & the Alex's cv-wiki. The content of the CGG manual was mostly copied from HV/CV-manuals and Features5.1 and paraphrased (in some places)/reordered for pseudo-originality & better understanding/usability (however, you did not solve the problems of the previous manuals). + you described well the new functions made by William Morrow aka GoodGuy (but not all as far as I remember). The content was copied from hv-cv_mans to cgg-man without providing links to hv-cv_sources and contributors. The CGG-manual contains only this: Information contained in this manual is a description of the CINELERRA-GG program usage and was obtained from various sources to include different communication channels, emails, common knowledge, and write-ups as new features were added In CV: This manual originates from "Secrets of Cinelerra", an excellent primer written by Adam WILLIAMS from HEROINE VIRTUAL LTD. In 2003 Alex FERRER created a Wiki based on that manual and added many screenshots and topic descriptions. The CV-manual contains a list of its contributors. So, - I provided a description of how chromakey-hsv works not for the CGG-manual, but for the CV-manual. Therefore you have to indicate the source. - Marketers of your community should finally make an effort on themselves and indicate the main sources of origin of the contents of the CinGG-manual. Good luck. As expected, the msg above did not pass moderation in the GG-ML and was banned. However, I see some progressive changes here https://git.cinelerra-gg.org/git/?p=goodguy/cin-manual-latex.git;a=shortlog BTW, The traditional tendency (in CinGG) to not indicate sources of origin and assign the original name of the program to the fork was evident many years ago. ----- 30.04.2023 Andrea Paz wrote the msg to the CinGG ML. https://lists.cinelerra-gg.org/pipermail/cin/2024-April/008221.html QUOTE: @igor_ubuntu (Igor Vladimirsky) See if the changes made to the manual sound good to you. https://git.cinelerra-gg.org/git/?p=goodguy/cin-manual-latex.git;a=commitdiff;h=8da3ca92772da956388bb055696a8b564bd1212f If that doesn't work for you, try writing something yourself (plain text is fine) and then put it here in the thread so it can be integrated into the manual. If, on the other hand, what you are asking for is that every sentenceI take from your manual report the author, then I apologize for what I have done so far. I thought that having asked your permission and then mentioning you on the mailing list (complete with a link) was enough. From now on, I will not resume sentences written by others to avoid these problems. -- - My answer (here, in the freelist): Andrea Paz, you know that my messages are moderated. Therefore, your proposal to write something to the gg-ml sounds like a mockery. If you carefully read the original of my message, you can see that there is no requirement in it quote:"that every sentence I take from your manual report the author". I talk about chromakey and about indicating the main sources of origin of your manual.. However, for the future: Texts written by me for my blog/yt-channel and transferred to the cv manual 1 - may only be copied to cgg-man with my permission. 2 - you may copy them only after indicating that this text was written by .. and was copied by you from cv-man to gg-man 3 - the copied text must have a direct link (to the original) in the text, and not somewhere at the bottom of the page. I have no desire to improve (neither directly nor indirectly) cgg-manual and I do not want to be an anonymous hero. I don't really hate cgg, but marketing I just can't stand. You can, of course, copy other text from cv-man without any conditions (it is under GPL). We all use open sources, in particular the mailing list archive. Phyllis finally indicated the sources of the cgg manual. It's enough. Until today, I have not taken the text from your manual. But if
Re: [Cin] small changes in Manual
@igor_ubuntu (Igor Vladimirsky) See if the changes made to the manual sound good to you. https://git.cinelerra-gg.org/git/?p=goodguy/cin-manual-latex.git;a=commitdiff;h=8da3ca92772da956388bb055696a8b564bd1212f If that doesn't work for you, try writing something yourself (plain text is fine) and then put it here in the thread so it can be integrated into the manual. If, on the other hand, what you are asking for is that every sentence I take from your manual report the author, then I apologize for what I have done so far. I thought that having asked your permission and then mentioning you on the mailing list (complete with a link) was enough. From now on, I will not resume sentences written by others to avoid these problems. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] OT: when you try to record dolphin, but result is mostly radio interference
More than Ubuntu Studio I recommend AV Linux from "our" Glen. And more than Audacity I recommend Ardour... (but even better: GarageBand, it is MacOS native) -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] small changes in Manual
I agree on all points. Il mar 30 apr 2024, 00:16 Phyllis Smith ha scritto: > Andrea, thank you for locating these improvements. My commentary below is > not meant to be too picky, just suggestions that you can ignore. If you > agree with my suggestions, no need to resend Plugins.tex because I will > just make the changes accordingly. These are the result of my doing "Check > that they fit", but I have not reviewed it all yet. > > 1) "The following effects support OpenGL acceleration:" - I am not sure > that it is important to list these as either the person wants to use the > plugin or they do not so they probably do not care if it uses OpenGL. I > would leave this out unless you think it is really important. And the list > is missing several per the search I did which may not be 100% correct to > include: > >> colorspace/colorspace.C:#ifdef HAVE_GL >> downsample/downsample.C:#ifdef HAVE_GL >> flash/flash.C:#ifdef HAVE_GL >> lens/lens.C:#ifdef HAVE_GL >> mirror/mirror.C:#ifdef HAVE_GL >> motion51/motion51.C:#ifdef HAVE_GL >> rumbler/rumbler.C:#ifdef HAVE_GL >> scaleratio/scaleratio.C:#ifdef HAVE_GL >> swapchannels/swapchannels.C:#ifdef HAVE_GL >> zoomblur/zoomblur.C:#ifdef HAVE_GL >> zoom/zoom.C:#ifdef HAVE_GL >> > > 2) The added line "The contents of the Mask track can be processed further > (blur, color correction, further masking) after the plugin." would go > better on the end after "animated Mask in one track and then to transfer > the Alpha channel to another target track" because that is where Mask is > being talked about. > > 3) Since ChromaKey implementation has varied so much and CinGG's version > has a problem, I am not sure if this is correct in our case: "It uses the > same algorithm as the Gimp selection tools. It works best with computer > generated graphics." Anyway to test this and verify in a case where it > does work? > > On Mon, Apr 29, 2024 at 5:36 AM Andrea paz via Cin < > cin@lists.cinelerra-gg.org> wrote: > >> I have updated the plugins chapter, based on IgorV's updates for the >> manual of >> Cinelerra-CV. (See: >> https://github.com/cinelerra-cv-team/cinelerra-cv/commits/master/doc) >> Check that they fit. >> -- >> Cin mailing list >> Cin@lists.cinelerra-gg.org >> https://lists.cinelerra-gg.org/mailman/listinfo/cin >> > -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] HTML manual
OK for me. Thanks. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] av1 hw decoding
Your patch doesn't seem to work: the message still appears that 'libdav1d does not support vaap'i. You can't see any load on the GPU. It is the same starting CinGG with “CIN_HW_DEV=vaapi” than without. I have tried various appimages: - kdenlive has the option for GPU disabled (I think I need to install motif). - Openshot doesn't start because it requires glibc 2.35 while I have 2.39. - Shotcut works: GPU = 10-30%; CPU = 10-30%. However, it indicates that it is using libdav1d for the decoding and I don't understand why it works. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] av1 hw decoding
I am responding here because the title is more appropriate than in the other thread. > you can simply comment out line "remap_video_decoder libaom-av1=libdav1d" in ffmpeg/decode.opts Yes, hardware decoding with libaom works. There are no messages on the terminal. The GPU is only 8-21% busy but the CPU is only 2-6% busy. However, if scrolling there are still freezes and artifacts; the performance seems to me similar to dav1d and so I don't think it is convenient to use libaom. Note: again, until I deleted .bcast5, and started from 0, was left with working libdav1d instead of libaom. If you have other ideas/tests for me to do, please let me know. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] HTML manual
Trying to open the html manual directly from the website, I no longer get to the cover and context menu, but I get to our repository list files. See video: https://streamable.com/o4dryf This has been happening for a couple of weeks. I don't know if it's my fault and the endless ad-blockers I use in my Firefox... -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] amdgpu_top
> Interesting, so av1 does not decode in hw in our case ... something to
> investigate, but I have no relevant hardware ...
It seems that Dav1d is developed by VLC together with ffmpeg. They say
it is software only
and does not uses any GPU acceleration:
https://www.videolan.org/projects/dav1d.html
It would be to try with Nvidia hardware to confirm.
It can use AVX2 in decoding, though. Do you have to enable this option
or is it by
default?
https://code.videolan.org/videolan/dav1d
It seems that dav1d is not a very up-to-date project; if I wanted to
compare with
libaom I just need to disable "-enable-libdav1d" in configure?
> hm, ah, second error! Was it 10bit hevc by the way?
Yes, it is a file 10-bit:
"pix yuv420p10le"; Color Space: bt2020nc; Color range: TV (mpeg).
Has anything changed between CinGG with ffmpeg6 and 7, since with
appimage I have no
problems
loading ("second error").
[PS:
Following the manual, I tried to start CinGG(ffmpeg7) with:
CIN_HW_DEV=vaapi ./cin
Now loading works without errors and playback works with a certain
percentage of GPU
acceleration (8-20%). If you try scrolling, however, there are
continuous freezes and
artifacts. But there are no messages and errors in the terminal.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] amdgpu_top
I use system monitor from KDE. I tried loading into CinGG an 8k video; 60 fps; AV1 (supported by vaapi) and mkv. I ran the playback, but I do not detect GPU utilization. The GPU load varies from 0 to 10%, but these are normal variations that are repeated even with GPU at rest. The CPU has a load of about 30%. With the appimage I have: GPU = Same values. CPU = about 60%. Confirmation is the terminal message: "Decoder libdav1d does not support device type vaapi." I also tried vdpau (which for AMD GPU is a wrapper that leads to vaapi) and the result is the same: "Decoder libdav1d does not support device type vdpau." I tried a second video: 4k; 60 fps; HEVC; mp4. The video does not load and I have numerous errors like: "file: /home/paz/video_editing/free_video/Life Untouched 4K Demo.mp4 int FFVideoConvert::convert_picture_vframe(VFrame*, AVFrame*, AVFrame*): Error retrieving data from GPU to CPU" With appimage I have no loading errors, but still the GPU is not engaged: "file:/home/paz/video_editing/free_video/Life Untouched 4K Demo.mp4 err: Operation not permitted Failed HW device create. dev:vaapi err: Input/output error HW device init failed, using SW decode." Finally using mpv from the command line (set to vaapi): $ mpv 'Life Untouched 4K Demo.mp4' GPU = 30-60% CPU = 0-2% -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 soon to be released
> I assume attached tar archive then only about TEST1 ? ? In test 1 I used a VP8/mov source without audio [4-3_3-2.mov] combined with an mp3/wav audio and in addition the render result [igor_test3.webm]: VP9/webm with audio Vorbis (webm.webm preset). [I didn't notice that the wav audio was mp3, maybe I need to use PCM audio?] In test 2 I used Big Buck Bunny_sunflower in h264/mp4 version with mp3 audio. In both tests I simply loaded (in test 1, the project and in test 2, the file) with the “replace current project” option and then did a little playback/scrolling. The messages shown are everything that appeared between starting and closing CinGG (I just removed the normal start/end messages that CinGG has). The problems with vaapi are probably due to the combination of AMD, mesa, amdgpu and rocm, since every time they are updated the behavior always changes and new problems always arise... However in CinGG/ffmpeg7 it seems that vaapi is working (test 2 [bbb_sunflower_1080p_30fps_normal.mp4]: no line “HW device init failed, using SW decode"). In test 1 you have errors with vaapi with VP8 [4-3_3-2.mov], which I believe is not supported. But there are no errors with VP9 [igor_test3.webm], which certainly supports vaapi. > I wonder if plain system ffmpeg still works for hw decoding? In Arch I still have ffmpeg 6.1.1. I have tried transcoding from mp4 to mp4, via decoding and encoding in vaapi, but I don't understand if decoding in vaapi works, while encoding works (https://trac.ffmpeg.org/wiki/Hardware/VAAPI): $ ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format vaapi -i mixkit-worried-and-sad-woman-outdoors-8739.mp4 -c:v h264_vaapi -b:v 2M -maxrate 2M output.mp4 [...] Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'mixkit-worried-and-sad-woman-outdoors-8739.mp4': Metadata: major_brand : M4V minor_version : 1 compatible_brands: isomavc1mp42 creation_time : 2020-06-21T18:53:40.00Z Duration: 00:00:15.00, start: 0.00, bitrate: 24801 kb/s Stream #0:0[0x1](und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], 24798 kb/s, 24 fps, 24 tbr, 24k tbn (default) Metadata: creation_time : 2020-06-21T18:53:40.00Z handler_name: ETI ISO Video Media Handler vendor_id : [0][0][0][0] encoder : Elemental H.264 Stream mapping: Stream #0:0 -> #0:0 (h264 (native) -> h264 (h264_vaapi)) Press [q] to stop, [?] for help [h264_vaapi @ 0x571d363508c0] Driver does not support some wanted packed headers (wanted 0xd, found 0x1). Output #0, mp4, to 'output.mp4': Metadata: major_brand : M4V minor_version : 1 compatible_brands: isomavc1mp42 encoder : Lavf60.16.100 Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), vaapi(tv, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 2000 kb/s, 24 fps, 12288 tbn (default) Metadata: creation_time : 2020-06-21T18:53:40.00Z handler_name: ETI ISO Video Media Handler vendor_id : [0][0][0][0] encoder : Lavc60.31.102 h264_vaapi [out#0/mp4 @ 0x571d3632dc80] video:3649kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.064330% frame= 360 fps=196 q=-0.0 Lsize=3652kB time=00:00:14.95 bitrate=1999.9kbits/s speed=8.14x -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 soon to be released
> hm, so hw decoding of vp9 does not work? Only on this version or on previous > ffmpeg 6.1 based cingg too? TEST 1 I directly loaded the project containing both the sources and the render (VP9). The two CinGGs are configured similarly, decoding with vaapi. TEST2 Second test regarding decoding in hardware with vaapi. I loaded directly into timeline a media with h264 codec and mp4 format to make sure vaapi is supported. Playback and scrolling does not produce any messages on the terminal. NOTE: Audio with PulseAudio does not work. The following message is shown: AudioPulse::open_output 110: failed server=(null) Invalid argument I don't understand why, on other occasions it works. This is true for both appimage and compiled. test.tar.gz Description: application/gzip -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 soon to be released
> well, this is even with my latest patch? Sorry for the late response. Below is what is written in the terminal from loading the media in timeline, then the render and finally the subsequent loading of the render to timeline: file:/home/paz/test/4-3_3-2.mov err: Invalid argument Render::render_single: Session finished. ** rendered 1019 frames in 50.335 secs, 20.244 fps FFMPEG::open_decoder: some stream times estimated: /home/paz/igor_test3.webm audio0 pad 8 -143 (151) audio0 pad 0 -143 (143) FFMPEG::open_decoder: some stream times estimated: /home/paz/igor_test3.webm FFStream::decode: avcodec_send_packet failed. file:/home/paz/test/4-3_3-2.mov err: Invalid argument FFStream::decode: failed HW device init failed, using SW decode. file:/home/paz/test/4-3_3-2.mov err: Invalid argument FFMPEG::open_decoder: some stream times estimated: /home/paz/igor_test3.webm FFMPEG::open_decoder: some stream times estimated: /home/paz/igor_test3.webm > Also, you can try to run cin via qemu-x86_64 user level emulator with > different -cpu parameters, may be bug surface only on specific cpus . I have the latest Ubuntu on qemu, but I don't quite understand what I need to do. What parameters of the processor should I use? > Anyway, I thought there still a lot to test (hw decoding, hw rendering, > renderfarm, background render, proxies, various profiles) so we better not to > rush release this month ... I agree about postponing the version with ffmpeg7. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 soon to be released
Trying to repeat Igor's test, with CinGG compiled with ffmpeg7, I find the render audio clean and without scratches. I remember that I use Arch, which has all updated drivers and libraries. On the terminal I read: file:/home/paz/igor_test.webm err: Invalid data found when processing input FFStream::decode: failed FFMPEG::open_decoder: some stream times estimated: /home/paz/igor_test.webm FFMPEG::open_decoder: some stream times estimated: /home/paz/igor_test.webm -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] trying to fix libopus for 5.1 sound
I don't understand how the channel map works. Anyway I post you the image showing on the left the sources and on the right a render: https://postimg.cc/Bj9GrFyc -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] trying to fix libopus for 5.1 sound
> But then can you try ffmpeg 7 with and without patch just in case it only > affects ffmpeg 7.0? Still the same result. General Complete name: opus_test_ffmpeg7_no_patch.webm Format : WebM Format version : Version 4 File size: 5.51 MiB Duration : 2 min 31 s Overall bit rate : 306 kb/s Writing application : Lavf61.1.100 Writing library : Lavf61.1.100 Audio ID : 1 Format : Opus Codec ID : A_OPUS Duration : 2 min 31 s Channel(s) : 6 channels Channel layout : L R C Lb Rb LFE Sampling rate: 48.0 kHz Bit depth: 32 bits Compression mode : Lossy Language : Italian Default : No Forced : No -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] trying to fix libopus for 5.1 sound
Same result with a cut made by me. I got the various files from: https://samples.mplayerhq.hu/A-codecs/AC3/ Broadway-5.1-48khz-448kbit.ac3 Canyon-5.1-48khz-448kbit.ac3 monsters_inc_2.0_192.ac3 TomorrowNeverDies-2.1-48khz-192kbit.ac3 There are no video tracks, I only rendered the audio. General Complete name: opus_test_ac3_2_no_patch.webm Format : WebM Format version : Version 4 File size: 5.51 MiB Duration : 2 min 31 s Overall bit rate : 306 kb/s Writing application : Lavf60.16.100 Writing library : Lavf60.16.100 Audio ID : 1 Format : Opus Codec ID : A_OPUS Duration : 2 min 31 s Channel(s) : 6 channels Channel layout : L R C Lb Rb LFE Sampling rate: 48.0 kHz Bit depth: 32 bits Compression mode : Lossy Language : Italian Default : No Forced : No General Complete name: opus_test_ac3_2.webm Format : WebM Format version : Version 4 File size: 5.86 MiB Duration : 2 min 31 s Overall bit rate : 325 kb/s Writing application : Lavf61.1.100 Writing library : Lavf61.1.100 Audio ID : 1 Format : Opus Codec ID : A_OPUS Duration : 2 min 31 s Channel(s) : 6 channels Channel layout : L R C Lb Rb LFE Sampling rate: 48.0 kHz Bit depth: 32 bits Compression mode : Lossy Language : Italian Default : No Forced : No -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] trying to fix libopus for 5.1 sound
> Can you also post output of mediainfo for both cases? Here it is. NO PATCH: General Complete name: opus_test_no_patch.webm Format : WebM Format version : Version 4 File size: 12.1 MiB Duration : 3 min 7 s Overall bit rate : 541 kb/s Writing application : Lavf61.1.100 Writing library : Lavf61.1.100 Video ID : 1 Format : AV1 Format/Info : AOMedia Video 1 Format profile : Main@L3.0 Codec ID : V_AV1 Duration : 3 min 7 s Width: 720 pixels Height : 576 pixels Display aspect ratio : 4:3 Frame rate mode : Variable Color space : YUV Chroma subsampling : 4:2:0 Bit depth: 8 bits Default : No Forced : No Color range : Full Matrix coefficients : BT.709 Audio ID : 2 Format : Opus Codec ID : A_OPUS Duration : 3 min 7 s Channel(s) : 6 channels Channel layout : L R C Lb Rb LFE Sampling rate: 48.0 kHz Bit depth: 32 bits Compression mode : Lossy Language : Italian Default : No Forced : No PATCH: General Complete name: opus_test_patch.webm Format : WebM Format version : Version 4 File size: 13.4 MiB Duration : 3 min 7 s Overall bit rate : 600 kb/s Writing application : Lavf61.1.100 Writing library : Lavf61.1.100 Video ID : 1 Format : AV1 Format/Info : AOMedia Video 1 Format profile : Main@L3.0 Codec ID : V_AV1 Duration : 3 min 7 s Width: 720 pixels Height : 576 pixels Display aspect ratio : 4:3 Frame rate mode : Variable Color space : YUV Chroma subsampling : 4:2:0 Bit depth: 8 bits Default : No Forced : No Color range : Full Matrix coefficients : BT.709 Audio ID : 2 Format : Opus Codec ID : A_OPUS Duration : 3 min 7 s Channel(s) : 6 channels Channel layout : L R C Lb Rb LFE Sampling rate: 48.0 kHz Bit depth: 32 bits Compression mode : Lossy Language : Italian Default : No Forced : No -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] trying to fix libopus for 5.1 sound
Test with CinGG-20240229-x86_64-multibit.AppImage (no patch): https://streamable.com/r4r150 test with compile version with ffmpeg7 and patch: https://streamable.com/rd9sz0 With only 4 audio channels: [libopus @ 0x75d44803b100] Invalid channel layout 4.0 for specified mapping family -1. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] trying to fix libopus for 5.1 sound
I cannot find "matrixbench_highdivx_ac3.avi". Can you provide it? NOTE: could the problems stem from the AVI format, which is old and limited? -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] AgingTV plugin issue
OK, with a very clear image I can see the dark spots. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] May be I fixed vorbis for webm/mkv with ffmpeg 7/6
Yes, I also remember the noisy audio. I don't remember the details well. However, with your patch everything is OK, even with flac (which, I seem to remember, suffered from the same problem; only opus worked fine). In my tests I always try to use the default profiles. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] AgingTV plugin issue
AgingTv seems to work fine for me. The settings are maintained. The slider at 0 gives no effect and increasing it works well. The check button works well. Two of my notes: 1- Grain is too pronounced. In my opinion there should be a slider for "Grain" as well so that it can be modulated. 2- I didn't quite understand the effect of "Dust"; what does it do? -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] May be I fixed vorbis for webm/mkv with ffmpeg 7/6
I don't remember the Vorbis problem very well. I ran renders of: Ogg/Vorbis; ffmpeg/Ogg (vorbis); ffmpeg/Ogg (flac); ffmpeg/webm (vorbis); ffmpeg/mkv (vorbis) and ffmpeg/mkv (flac). In all cases the sound was clean and correct. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ChomaKey's old bug
You are right. You can't see it by applying Title to the same track as the purple background, but by putting Title in an empty upper track the problem is still there. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ChomaKey's old bug
> Can you try attached patch ? It seems to me that the patch works. I used Camille's original video where you can see the title fade from black to transparent and finally to white as it should be. I superimposed my own title on top of it ( on top) where instead the fade always remains white. The demonstration video is here: https://streamable.com/cqg3u2 I recommend advancing frame by frame. Thank you, Andrew -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 soon to be released
I am not the best one to evaluate sound, since I am deaf in one ear, which precludes me from sound spatiality. For me, comparison between Andrew's patches and without patches is simple. In the second case only a strong pulsating signal can be heard. In the first case you can hear well, including differences due to varying plugin parameters (but in hearing small differences I am not reliable). -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 soon to be released
The crash was my fault. With a new compilation all the f_audio plugins I tried work. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 soon to be released
The ffmpeg audio plugins still do not work. Even deleting .bcast5 they still do not work. Now, however, the Pulse Audio driver is working. I then tried a new compilation with git clone but I can't install the 005- patch anymore and the compilation crashes. I don't know if the crash is related to ffmpeg or vulkan decode. If needed I can post the cin5.log. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 soon to be released
As usual, I get a little confused about patches and how to put them on top of others. Can you clarify for me which patches to put and how to put them? -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ChromaKey's old bug
I also find ChrmaKeyHSV's window too narrow. I like IgorB's proposal very much. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 soon to be released
@Andrew Randrianasulu Complete failure with ffmpeg audio filters. One premise, setting the audio driver to "pulse" the audio does not work. Setting it to "alsa" works normally. I do not have Pulseaudio in my system, but Pipewire takes pulse signals as if it were there. In ffmpeg6 I do not have this problem. None of the ffmpeg filters I have tried work. The typical error is as follows: PluginFAClient::activate: F_adynamicequalizer failed err: Option not found PluginFAClient::process_buffer() F_adynamicequalizer err: Operation not permitted The old CinGG with ffmpeg 6 works normally. LV2 and native filters work fine, of course. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Minor improvments to the manual
Sorry. The right Word Is anamorphic. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 soon to be released
I am continuing to use the version compiled with ffmpeg7 and have found no bugs or other problems. Even the efficiency of playback and some rendering are comparable with the previous version. All OK, for me. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] Minor improvments to the manual
I am reading the Cin-CV manual with IgorV's updates. (https://github.com/cinelerra-cv-team/cinelerra-cv/commits/master/doc). Based on these I have made the first minor adjustments to Windows.tex. Later I will post some major updates in the other chapters. Windows.tar.gz Description: application/gzip -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 api changes
Sometimes I think it is my old projects or even not my own that cause some problems. For example to test ChromaKeyHSV I created my own project, but I also used two projects of IgorV. I could never see precise cause and effect though, so I'm not sure. Regarding AC3, there is a commit in Adam's repository about decoding AC3, but I don't think it is related. Anyway, the link is this one: https://github.com/heroineworshiper/hvirtual/commit/3124ad744154eae8e48bdeff00d81d11613dc9a4 -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 api changes
I also tried several appimages and always AlphaOffset did not work. After deleting ".bcast5" instead the slider works in both appimage and compiled CinGG. So I would say it's all OK, it is definitely not a ffmpeg 7 problem. I would say it is my problem that I often do the tests without renewing .bcast5 first. Sorry. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 api changes
In CinGG compiled with ffmpeg7 I find "strange" behavior that I do not encounter with appimage (which has ffmpeg6). Using a greenscreen image, as the top track and any media as the background track, we need to apply the ChromaKey HSV plugin. We can see that the "Alpha Offset" slider does not produce any change. It does not work. If we repeat the same test with appimage, the slider works normally. Can you verify if this is also the case for you or does it depend on me or my system? I have also tried other plugins that use the alpha channel, and also patchbay overlays, but everything works fine. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 api changes
Yes, "bd.m2ts" was created and it works. It is always my stupidity that I did not realize that CinGG always terminates automatically, at the end of bd-render, if there is no burner and db-disk. I apologize, as always. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Latex problem
Hi, I simply commented out that line and now everything works fine. Is it possible to remove it permanently? I couldn't find any \substitutefont entries in the code, so there are no substitutions to be made with \DeclareFontFamilySubstitution. Am I wrong? -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] Latex problem
I updated the latex manual with a "git pull" and now it no longer
produces the pdf for me. I get the error:
packages.tex Error 10: File `substitutefont.sty' not found. \usepackage
In packages.tex I have, from line 9 to line 15:
9 \usepackage{substitutefont} % so we can use fonts other than those
specified in babel
10 \usepackage[english]{babel} % default language for document
11 % Cyrillic - if it is used, no Small Caps are available:
12 %\usepackage[scaled=0.925]{XCharter} % Подключение русифицированных
13% шрифтов XCharter "Connection
14% of Russified XCharter Fonts"
15 \usepackage[bitstream-charter]{mathdesign} % Согласование
Do you have any idea what could have happened? Lately I have had
updates to both texlive and TexStudio, which I use to work on the
manual.
I found this link:
https://ctan.org/pkg/substitutefont?lang=en
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Audio/video sync with "Audio Offset"
As usual, I got it wrong... "This is not for syncing audio and video on the timeline. This is for calibrating and configuring the operation of the program and audio driver." (IgorV) However, it remains important to know and I hope you find it interesting. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 api changes
I made a new compilation with Andrew's 5 patches and putting in /src the tarball of ffmpeg 7 plus patches3, patch 4 and patchD. All OK. The BD render still does not create the video, even with a media with only 2 audio tracks. I think it is my fault that I have never done BD/DVD and don't know how to do it -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] Audio/video sync with "Audio Offset"
The manual entry "Audio Offset," which was taken from Adam's manual, "Secrets of Cinelerra," provides an excellent method for synchronizing a video track with an audio track. It has been a long time since I read it and I want to bring it to your attention again: https://cinelerra-gg.org/download/CinelerraGG_Manual/Audio_Out_section.html There is also a video tutorial by Adam: https://www.youtube.com/watch?v=n0evGSOpwbY=PLv6Mn7I6pSmWivUKTvf_CzqHjnlKt5zCS=10 -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ChomaKey's old bug
Yes, thank you. I read the manual on the new ChromaKey hsv. As for the compilation, I am not very good at it. Some time ago I had tried CinCV just because it was present in Arch's AUR. CinHV I tried to install it unsuccessfully and have not tried again. CinCVE I have never tried PS: Your article is very clear and comprehensive. Adam is always in too much of a hurry and takes many things for granted. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ChomaKey's old bug
I tried taking the ChromaKeyHSV binary of CinHV and substituting it for that of CinGG. However, the program crashes at startup. I guess that's not the way to do it :) -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 api changes
Compilation with all the patches went well. I loaded a m2ts file with many audio channels and tried (from root) to do a BD render. I left all settings at default. At the end of the render I got a crash (no dump). In the terminal I have these lines: FFMPEG::open_decoder: some stream times estimated: /home/paz/video_editing/free_video/Amaze.m2ts Render::render_single: Session finished. ** rendered 1033 frames in 14.711 secs, 70.220 fps ++ dirname /home/paz/test/bd_20240407-202044/bd.sh + sdir=/home/paz/test/bd_20240407-202044 ++ cd /home/paz/test/bd_20240407-202044 ++ pwd + dir=/home/paz/test/bd_20240407-202044 + PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/opt/rocm/bin:/home/paz/cinelerra5/cinelerra-5.1/bin + mkdir -p /home/paz/test/bd_20240407-202044/udfs ++ du -cb /home/paz/test/bd_20240407-202044/bd.m2ts ++ tail -1 ++ sed -e 's/[ ].*//' + sz=53477376 + blks=30208 + rm -f /home/paz/test/bd_20240407-202044/bd.udfs + '[' -f /home/paz/test/bd_20240407-202044/bd.meta ']' + mkudffs -b 2048 /home/paz/test/bd_20240407-202044/bd.udfs 30208 filename=/home/paz/test/bd_20240407-202044/bd.udfs label=LinuxUDF uuid=6612e44ea433917e blocksize=2048 blocks=30208 udfrev=2.01 start=0, blocks=16, type=ERASE start=16, blocks=4, type=VRS start=20, blocks=76, type=ERASE start=96, blocks=16, type=MVDS start=112, blocks=16, type=ERASE start=128, blocks=4, type=LVID start=132, blocks=124, type=ERASE start=256, blocks=1, type=ANCHOR start=257, blocks=29688, type=PSPACE start=29945, blocks=6, type=ERASE start=29951, blocks=1, type=ANCHOR start=29952, blocks=96, type=ERASE start=30048, blocks=16, type=RVDS start=30064, blocks=143, type=ERASE start=30207, blocks=1, type=ANCHOR + mount -t udf -o loop /home/paz/test/bd_20240407-202044/bd.udfs /home/paz/test/bd_20240407-202044/udfs + bdwrite /home/paz/test/bd_20240407-202044/udfs /home/paz/test/bd_20240407-202044/bd.m2ts + umount /home/paz/test/bd_20240407-202044/udfs + echo To burn bluray, load writable media and run: To burn bluray, load writable media and run: + echo for WORM: growisofs -dvd-compat -Z /dev/bd=/home/paz/test/bd_20240407-202044/bd.udfs for WORM: growisofs -dvd-compat -Z /dev/bd=/home/paz/test/bd_20240407-202044/bd.udfs + echo for RW: dd if=/home/paz/test/bd_20240407-202044/bd.udfs of=/dev/bd bs=2048000 for RW: dd if=/home/paz/test/bd_20240407-202044/bd.udfs of=/dev/bd bs=2048000 + kill 197321 Terminato -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 api changes
>> I tried to cp thirdparty/src/ffmpeg-6.1.patch10 as ffmpeg-7.0.patch10 and >> compilation currently progressed beyond this error. Success! Thank you very much, Andrew. I saw that in this edition there are few filters. In CinGG there is only "tiltandshift" filter; it does not give error but it does not work. In the terminal I have only the message: "resource temporarily unavaible" Of the other filters, there is no trace. These are: aap qrencode quirc fsync showinfo bitstream dnn > Ah, even if most patches apart from 3, 4 and D still apply encoding is busted > :/ I have tried three encodings and they work normally (h265-Hi; DNxHR-HQX and AV1.svt). -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 api changes
> you mean > echo "system_libs += -L/usr/pkg/lib/ffmpeg6" > echo "CFLAGS += -I/usr/pkg/include/ffmpeg6" > ? > those are for NetBSD > Yes, I meant those. didn't know they were for BSD. In the log it talks about a cuda error; maybe it tries to activate even on my system that doesn't have cuda? -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] ffmpeg 7.0 api changes
How to compile CinGG with ffmpeg7? Should I remove ffmpeg5.1 and ffmpeg6.1 and all their patches and then add the tarball of ffmpeg7 plus your new patch? -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] ChomaKey's old bug
In an exchange of mails Igor Vladimirsky pointed out to me that the old bug reported by Camille: https://lists.cinelerra-gg.org/pipermail/cin/2021-March/003149.html and: https://www.cinelerra-gg.org/bugtracker/view.php?id=559 Has been fixed by Adam in CinHV. The patch with the fix is at: https://github.com/heroineworshiper/hvirtual/commit/9080ca3fc952edce68fcabb6d7460dda7c75da79 Andrew, do you think it is possible to implement the patch in CinGG? -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] The Lady
I agree. I only reported the new because it was curious, not because I wanted to replace the images from the manual. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] The Lady
Curious news: https://arstechnica.com/information-technology/2024/03/playboy-image-from-1972-gets-ban-from-ieee-computer-journals/ We used the Lady in the OpenCV filter section of the manual. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] BlueBanana and alpha slider
In other emails, Igor Vladimirsky identified the commit after which the alpha slider is no longer functional: https://git.cinelerra-gg.org/git/?p=goodguy/history.git;a=commit;h=259e435484d99cf6517290f530ac2d9d0d86cd16 If anyone can figure out where the problem lies, they are welcome. Perhaps in bluebanacolor.c, the line: float a = 1.f - *S*F; Which became: float a = *S*F; ? -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] Vectras VM
This looks more interesting than termux, but I guess it takes Android tablets with better hardware: https://vectras.netlify.app/ -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] Question from the forum
An interesting question from the forum: https://www.cinelerra-gg.org/forum/everything-else/how-to-automate-the-cutting-of-a-project-by-timecode/#post-2700 Do you think it is possible to build a script that teaches how to make automatic cuts in CinGG? -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] Youtube
A quick note to say that CinGG's Youtube channel has reached 500 subscribers. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] removing letter boxing while preserving aspect
I have added the tip to the manual; see if it is okay. I also attach a
txt file for those who want to correct or improve the tip.
To be put at the end of section 3.2:
A tip on how to eliminate Letterbox/Pillarbox black bands in the Set
Format window can be found here: \nameref{sub:remove_letterbox}.
To be put at the end of section 19.7.11:
\subsection{How to remove letterbox/pillarbox bands}%
\label{sub:remove_letterbox}
To remove the horizontal black bands of the letterbox or the vertical
black bands of the pillarbox we need to change the \textit{size} and
\textit{aspect ratio} of the source by cropping.
For example, if we want to remove the letterbox from a $4:3$ frame to
leave only the content with aspect ratio $3:2$, we can act on the
project format by doing the following steps:
\begin{enumerate}
\item Check the size of the base W of the original frame in pixels;
\texttt{Resource} window $\rightarrow$ \texttt{RMB} on Asset
$\rightarrow$ \texttt{Info} $\rightarrow$ \texttt{Detail}; e.g. W =
768 px
\item Obtain the height of the figure in $3:2$, i.e., without the
black bands; H can be obtained from the formula:
$\frac{3}{2} = \frac{W}{H}$ \quad from which $H = \frac{768 \times
2}{3}$; \qquad e.g., H = 512 px
\item Note that $W \times H = 768 \times 512$ is just the crop we
are looking for to switch from $4:3$ frame to $3:2$ frame without
letterbox
\item Open \textit{Set Format} window: \texttt{Settings
$\rightarrow$ Format}
\item Change $H = 512$ and set \textit{Display Aspect Ratio} to
$3:2$; press \texttt{Apply} and \texttt{OK}. Note that we leave W
unchanged, since the frame width does not change.
\item If needed, act on the \textit{Camera} tool to get the
desired viewport.
\end{enumerate}
\paragraph{Note:} in complex situations, with multiple sources of
different sizes, it may be appropriate to premise an additional step
to the second: change the size of the track on the Timeline via
\texttt{RMB $\rightarrow$ Resize track}.
In this way we crop the track to match it to the project format that
we will change in the next step. This way we avoid possible unwanted
distortions.
In the case of the pillarbox, we will leave H unchanged while
calculating the new value of W. The formula $\frac{x}{y} =
\frac{W}{H}$ is valid for any aspect ratio ($4:3; 16:9; 2.35:1$; etc)
How to remove letterbox/pillarbox bands
To remove the horizontal black bands of the letterbox or the vertical black
bands of the pillarbox we need to change the size and aspect ratio of the
source by cropping.
For example, if we want to remove the letterbox from a 4:3 frame to leave only
the content with aspect ratio 3:2, we can act on the project format by doing
the following steps:
1- Check the size of the base W of the original frame in pixels; e.g., W = 768
px
2- Obtain the height of the figure in 3:2, i.e., without the black bands; H can
be obtained from the formula 3/2 = W/H, from which H = (768 x 2)/3; e.g., H =
512 px
3- Note that WxH = 768 x 512 is just the crop we are looking for to switch from
4:3 frame to 3:2 frame without letterbox
4- Open Set Format window: Settings --> Format
5- Change H to 512 and set Display Aspect Ratio to 3:2; press Apply and OK.
Note that we leave W unchanged, since the frame width does not change.
6- If needed, act on the Camera tool to get the desired viewport.
Note: in complex situations, with multiple sources of different sizes, it may
be appropriate to premise an additional step to the second: change the size of
the track on the timeline via RMB --> Resize track.
In this way we crop the track to match it to the project format that we will
change in the next step. This way we avoid possible unwanted distortions.
In the case of the pillarbox, we will leave H unchanged while calculating the
new value of W. The formula x/y = W/H is valid for any aspect ratio (4:3; 16:9;
2.35:1; etc)
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] New Opus audio codec
AVX2 and Machine Learning in the new release of Opus audio codec: https://opus-codec.org/ -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] removing letter boxing while preserving aspect
Actually in the case of my png image, the "Resize track" step is not necessary, but it is always better to have the project format the same as the track format in Timeline, especially if you are using multiple clips. Note: "Set Format" and "Resize track" cause a crop, which is necessary in your case, but we often want to avoid it by using the "Scale" plugin instead of "Resize track." @IgorBeg can you please indicate your method? (I plan to make an addition to the manual). -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] removing letter boxing while preserving aspect
I think the work can also be done in CinGG. When you have distortions it is because the format of the project does not match the format of the track on the timeline or the format of the asset; in our case the track is considered. I created in inkscape an image with a 4:3 format and the dimensions of 768x576. Inside I drew a rectangle that coincides with the 3:2 format with dimensions 768x512. I attach this image. If we change the DAR (aspect ratio) from 4:3 to 3:2 we get a distorted image. So we must first adjust the track on the timeline to the new dimensions and then conform the project (size 768x512 and DAR to 3:2) in the window Settings --> Format. Now that format and track size match we have our crop without distortion. Note: the first step of scaling to the 768x512 size should not be done on the asset (via plugin or the Resize found in RMB --> Info), because this keeps the DAR at 4:3. We must scale by acting on the track in the timeline, via RMB --> Resize track... The steps I took are as follows: 1- I upload the image 4-3_3-2.png 2- upload image to timeline 3- RMB on the track on the Timeline and I choose Resize track 4- I set the value 768 (unchanged) and 512 (new). Note that the ratio of sides remains 1:1. I click OK. 5- I see the deformed track because it conflicts with the project format (which matches the asset format) 6- I open the Set Format window (Setting --> Format) 7- Set H = 512 8- Set Display Aspect Ratio a 3:2 9- I click Apply and then click OK. 10- In the compositor you can see the crop of the asset that exactly shows the 768x512 format at 3:2 11- By making a render this remains in the new format, that is, of the desired 3:2 crop. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Fwd: Chromakey + blur testcase from IgorV
I tried to update the text of Blur plugin in the manual. See if it is
okay (to be added at the end):
Problems may arise, with old projects or with
Cinelerra-CV/Cinelerra-HV projects, regarding the parameter
\textit{alpha determines radius}. However, to avoid problems, it was
hidden in the GUI's plugin. For compatibility reasons and for future
development it has been left in the code.
The parameter about \textit{alpha determines radius} is
\texttt{A\_KEY}. \texttt{A\_KEY} can be 0 or 1. When we press the
\texttt{Reset} button in the Blur plugin window the values are:
\texttt{Radius=5}; \texttt{Horizontal= Vertical= A= R= G= B= 1};
\texttt{A\_KEY= 0}.
Old projects may have saved that parameter (A\_KEY) to 1 so, in the
special cases, is needed some workarounds to put it to 0.
\begin{enumerate}
\item Open the file project (\texttt{.xml}) in a text editor and
change the A\_KEY value of the BLUR from 1 to 0. It can be useful to
change ALL these value using \textit{Find and replace...} tool.
\item In \CGG{} program, open the project. Click on the cog icon
(\textit{Preset edit}) of the Blur effect bar and the \textit{Keyframe
parameters} window is open. There, you can see the A\_KEY parameter
and change it: select the \texttt{A\_KEY} parameter and in the
\texttt{Edit value} change it from 1 to 0,... and press \texttt{OK}
button.
\end{enumerate}
> Not even sure if it makes sense to do release this month? On the other hand
> not even sure if we will able to fix more than one problem in next 30 days ...
I would bring out a new appimage because DeJay needed the appimage
with Color 3 Way working...
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Fwd: Chromakey + blur testcase from IgorV
NB: Completely agree with Andrew's conclusion about apes! (quote from "planet of the apes" trilogy?) -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Fwd: Chromakey + blur testcase from IgorV
To me the story was even more odd. When I uploaded IgorV's project, it was completely out of whack. I tried various settings with the same result. When I did the reset the situation improved but the horizontal slider still did not work. Using values other than 0 brought the background to black as well as the masked part (the green flag). Using just the Vertical slider on the other hand worked fine. I also tried the LinearBlur plugin by setting it to horizontal and everything worked fine. After IgorBeghetto's email I reset it again and now everything is fine, even the horizontal slider. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Fwd: Chromakey + blur testcase from IgorV
You are right: CinGG is very feature rich and can also use the ffmpeg plugins. Plus I also tested the other native blur plugins (linera blur, radial blur, etc) and they all work normally with Chroma Key (HSV). It is the only Blur plugin that interacts with Chroma Key giving problems. PS: I don't understand the problems with Chroma Key (HSV); for the little I have tested it, it works fine for me (without Blur plugin). What precisely should I be testing? -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Fwd: Chromakey + blur testcase from IgorV
What is the problem with Chroma Key (HSV)? I can't find the original discussion. It seems to me that CinGG has problems when dealing with the alpha channel, so in overlays, Keys, etc. See also here (without taking offense at the jibes he throws toward CinGG users): https://linuxvideoediting.blogspot.com/2022/09/transparent-text-effect-with-Cinelerra-part2.html IgorV sees the following problems in CinGG (comparing with CV and HV): 1- Color rendering 2- Overlays 3- Conversion between color models (Adam has made updates, but states that Cin will always have problems with YUV(A) and recommends using only RGBA-FLOAT) 4- Blur -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Fwd: Chromakey + blur testcase from IgorV
Igor Vladimirsky also made a good video tutorial on how Chroma key (HSV) plugin works: https://www.youtube.com/watch?v=QATi9J6Q8uw -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Ghosts from the shell!
> Thanks for the link. I tried to change the text in the manual, see if > that's okay. > > I also changed the paragraph in Color 3 Way plugin about HDR. > I didn't change the HDR entries of the overlays and Histogram; > Phyllis, tell me if I should remove them from there as well. @Phyllis Smith If you don't want to use the whole chapters I attached, the change in Keyframes.tex is in the "Compositor keyframes" section, and in Plugins.tex is the last paragraph of Color 3 Way. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] DAR, PAR and SAR, again
A curiosity: looking at the commit on git (https://git.cinelerra-gg.org/git/?p=goodguy/cin-manual-latex.git;a=commitdiff;h=fb7369e6b5f670d1b1ebaffa08f3c2e4bb053a61) we find "\r" at each end of the line. Is this due to the fact that I use texstudio? This has never happened before... -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] Patch HDR for Color3way
>> Just now, in comparing the results with the alternative views in the manual, >> the PorterDuff matches what I see. You are right. I had forgotten how PorteDuff works. Sorry. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
[Cin] Patch HDR for Color3way
>From this forum thread: https://www.cinelerra-gg.org/forum/help-video/problem-with-colour3way/ After the patch to make Color3way work in float, even with values above the range (0 - 1.0f), this problem occurs: "If I move the Shadows Value slider to the left, by the time it reaches 0.006 the image is almost totally black, which makes it totally useless." and: "I confirm the problem. The color wheel also behaves the same way, while the saturation slider works normally. Midtone and Highlight work normally." The applicated HDR patches can be seen here: https://git.cinelerra-gg.org/git/?p=goodguy/cinelerra.git;a=commitdiff;h=3cdcd29150341dd26a8c61772f8473ab20a85fdd I've tried a few builds/tests. The patches for Overlays and for Histogram plugin seem to work normally. Only the patch for Color3way causes a problem. This problem occurs only for shadows, which is strange because the patch only alters the white boundary and leaves the black boundary unchanged. I tried to read the plugin code but I am not able to understand the problem. Does anyone understand anything about it? For now you could exclude the Color3way patch but put the other two back in. PS: Using the overlays in the patchbay seems to me that the PorterDuff do not work. This does not depend on the patch because I have the same behavior even with the old appimages without the patch... -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] rusticl and DaVinch Resolve (round N)
Impossible with AMD graphics! :-) -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] rusticl and DaVinch Resolve (round N)
It seems that with the latest kernel 6.7.3 the problems with my AMD graphics card are solved. Now DVR works with both ROCm and Rusticl (just use "RUSTICL_ENABLE=radeonsi"). The performance between the two OpenCLs seems similar to me. In contrast, for those using Blender, rusticl is not implemented and ROCm-Hip must be used. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
