Re: [Cin] Solus is working on adding Cinelerra -- email being resent
"John" > My Cinelerra-GG Solus package is almost ready, but there is a blocker. > Video effects that use vaapi don't work and in terminal I get: > PluginFVClient::process_buffer() F_denoise_vaapi > err: Operacja niedozwolona (that means "operation not allowed" in > english). > > Today's GIT checkin has the plugin.opts file updated to comment out F_denoise_vaapi, deinterlace, procamp, scale, and sharpness. Thank you for discovering this and letting us know. P.S. I forgot to ask about this "Second is just a suggestion. If you do make install -j# (# means number of cores) build will fail" but will do so soon. gg/Phyllis -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] French translation update
About the French translation update from Olivier. It has been checked into the Git repository. @Pierre - there is a Mint18 build if you would like to check it out at: https://www.cinelerra-gg.org/download/testing/cinelerra-5.1-mint18-x86_64-static.txz and as usual it contains a bunch of other changes to include some masking fixes (later I will update BT #2) 2. edited po/xlat.sh and added "--from-code utf-8" to the xgettext line > The above has been corrected xlat.sh as you provided and checked into GIT just now. > > 4. ran: msgmerge -U po/fr.po po/cin.po > I have updated the documentation here locally in the manual Translations chapter to recommend your method as being a lot simpler to follow. And I will update the cinelerra-gg website also because being a lot less complicated may result in more language translations. Thanks for all of your help. gg/Phyllis -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] LV2_blacklist.txt & Debian packaging improvements contributions
Olivier: Now that things as settled around, and now that I'm good with the > website French translation, I'm taking back the packaging of Cin-GG for > my audio-linux debian-based distribution (and maybe later, a potential > inclusion into Debian mainstream, but... one step after another). > When you do get this packaged with audio-linux LibraZiK, it would be good to add this to cinelerra-gg.org same as AV Linux and Bodhi Linux. > > Doing that, I found a bunch of LV2 plugins which are avoided Cin to be > launched and then, which needs to be added to the LV2_blacklist.txt file > (after I did that locally, Cin is launching fine). Those following lines > are the culprits: > > file:///usr/lib/lv2/MonoEffect.ingen/MonoEffect.ttl > file:///usr/lib/lv2/MonoInstrument.ingen/MonoInstrument.ttl > file:///usr/lib/lv2/StereoEffect.ingen/StereoEffect.ttl > file:///usr/lib/lv2/StereoInstrument.ingen/StereoInstrument.ttl > http://example.org/raffo > http://www.wodgod.com/newtonator/1.0 > https://sami.boukortt.com/plugins/intersect#Intersect > https://sami.boukortt.com/plugins/intersect#SymmetricDifference > https://sami.boukortt.com/plugins/intersect#Upmix The latest GIT checkin a few minutes ago, includes the updated lv2_blacklist.txt with the first 4 lines BUT I could not test it. You already did so it should be fine. HOWEVER, I do not understand the last 5 URL lines. None of them worked for me and I am confused as to why they were included. > > Also, please, find attached an improved version for the > ./blds/debian/control file which contains those improvements/changes: > At the end of the month, GG is really pressed for time doing all of the distros. He is not very good at Debian system packaging/maintenance -- we work on Fedora. Today he is trying to jam in some changes that got put off while working on the update of OpenGL. We will save your "control" file and work on looking more carefully at your suggested improvements. He did take the time to evaluate it, found the duplicate libraries that your control file pointed out and the libusb missing one and alphabetized all of the dependencies to make it easier to find a specific one. The reason for not listing them one per line despite the fact that it is more human-readable is that just like cpu-s, memory, and disks, the *screen is a resource* -- most people do not think of that as such, but when you are working with several windows on several program routines simultaneously, you need space. So he really needs to see fewer lines to get to the one he needs to see. Also, time is a big factor and when he does all of the monthly builds, he uses *xen* and he has to edit a bunch of individual files before starting to get the builds to work and wants to quickly find the lines he has to modify in each. Their are some real experts on package control for all of the distros -- in the commercial world where he used to work, there was a "builder" who took care of all of this type of stuff. We are using bare bones / old stuff just to manage. Maybe some day, a Cinelerra builder will show up and take care of all of this! > > -- why is inkscape needed for building ? It sounds like a mistake at a > first glance. > There is a plugin called SVG for Inkscape so that is why it is needed. > -- why is e2fsprogs needed ? > We did not find the exact reason -- i think it is for mount bluray - I will see if I can find out for sure but at any rate he does not want to take it out until we are sure. > -- same for linux-firmware, why is that needed for building ? The main reason for this is supposed to be OpenGL + the TV tuner _ hardware. I will look at this again too since you say it is not even in the Debian repository anymore. > - The "Standards-Version" number is currently defined to "5.1.20190430". > It is not supposed to be the program version number (which is defined in > the debian/changelog file), but a number matching a Debian standard. If > you're OK with that, I would set it up to 3.9.8 which is the standard > for Debian Stretch (current stable - Debian 9) and which will work as > well for the next stable (Buster - Debian 10). > Every month when gg does a build for Debian, it errors out UNLESS he change the Standards-Version in the control file -- so we are surprised that he could put this at 3.9.8 and it would work, month after month. Again, this may be because of xen. Also, this is why he leaves this line at the beginning of the file -- to make it easy to find to change it. Thanks for all of your input. If I find out anything more, I will let you know. gg/Phyllis -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] French translation update
Le 2019-05-28 03:14, Phyllis Smith a écrit : Olivier, concerning the following: Note that to do this (attached) translation, I did those steps: 1. extracted the tarball 2. edited po/xlat.sh and added "--from-code utf-8" to the xgettext line (see [1] below) 3. ran: po/xlat.sh > po/cin.po (my understanding is that this command updated the general "cin.po" catalog) 4. ran: msgmerge -U po/fr.po po/cin.po (my understanding is that this command updated the French "fr.po" translation file from the general "cin.po" catalog) 5. translates the po/fr.po It would be great if the knowledgeable people (ping the usual suspects here: Phyllis & GG!) could tell me if this workflow is fine. The workflow is fine! We were unaware of "msgmerge" but now that I know, I will add this to the documentation because it might be a lot easier to follow. Thanks, GG/Phyllis That sounds like a good idea. Cheers, Olivier -- Site web : https://librazik.tuxfamily.org/ Donation : https://liberapay.com/LibraZiK/ Diaspora : https://framasphere.org/people/8c184af0c9450134f6682a053625 Mastodon : https://mastodon.xyz/@LibraZiK -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] CinGG manual to Latex
Hi einhander. Add chapter 8. The glossary odt has many entries and long descriptions (good work Phyllis!). Can you make a separate file to include as you do with chapters, instead of searching for words in the text and entering the relevant entry just below? And if you can do so, you can enter multiple entries and only last give the command MakeIndex and then compile the pdf? or you have to do away with for single entry added? -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] CinGG manual to Latex
The glossary is checked in as part of the Appendix so it can be removed from there and made into a separate section for a Latex Glossary. I do not recommend starting from scratch because the goal was to only put in words necessary for specific Cinelerra clarification. Do you have an odt from the glossary or does it have to start from scratch? > -- > > -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] CinGG manual to Latex
Hi Andrea, On page 91 (105) of the pdf, the wrapfigure narrows the text for 3-4 consecutive pages, instead of returning to normal width after the figure. Is there anything I can do? I can't. The fix is in my repo. It's wrapfigure feature, it create box in lists environments and not always correctly. The best that I can do is manually close environment and start it again with proper numeration. In case of description environment it's really easy. I don't know any other ways to correct that behavior. -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Re: [Cin] CinGG manual to Latex
@einhander On page 91 (105) of the pdf, the wrapfigure narrows the text for 3-4 consecutive pages, instead of returning to normal width after the figure. Is there anything I can do? I can't. @Phyllis Do you have an odt from the glossary or does it have to start from scratch? -- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
