Hi all!
I installed texlive for Slackware and additional fonts (on another partition
due to its size, mounted with -obind), and Kile 1.9.3 (KDE3 TeX editor).
Now when I try to compile documentation I get:
/usr/share/texmf-dist/tex/latex/mathdesign/mdsffont.def:0: Font shape
declaration has
Hi, Andrew!
Indeed, very strange error. But you can bypass it by comment
out renewcommand{\rmdefault}{mdbch}\rmfamily string. Although latex will
use the default CM font.
That texlive version you use? Can it be possible to update it?
--
Best regards,
Andrey
вс, 20 сент. 2020 г., 18:57 Andrew
The overfull warning is a just info, that latex cant fit line into its
borders. Its can be skipped if that line looks ok.
The reference and labels warnings are important, it's indicates that some
references are undefined, or labels used more than one time.
The pdf looks the same
Hi Andrea,
Do you installed only TexStudio, or TexStudio+TexLive?
To get whole structure of Cin Manual for local use you should:
1.Go to the main repo of manual https://github.com/einhander/cin-manual-latex
and grab the latest version.
1a. If you have git installed you can open terminal in
Hi!
On 190902-08:09-0600, Phyllis Smith wrote:
> I believe (and Andrey/Andrea can confirm) that the source for the LaTex
No, they wouldn't be able to confirm, as you forgot to stick the cinelerra-gg
list email in the To: header, but replied to me only. :) . That is now
corrected.
> ma
trol of output format.
> To produce a good pdf from Asciidoc, you have to fine tune the standard latex
> template and entire document,
This is past. Asciidoctor-pdf produces beautiful pdf from scratch.
No need to convert into docbook or latex anymore.
> because Asciidoc and other LMLs use
into html and into other formats.
Syntax IMHO is a mater of taste.
The disadvantages of LML is a continuation of it advantages,
LML has a lack of control of output format.
To produce a good pdf from Asciidoc, you have to fine tune the standard latex
template and entire document,
because Asciidoc
HTML, so you can export it and also
import it into LaTex, some hand changes to LaTex would still be necessary.
2. Changes could then always be done very quickly online and several
people could also work on the manual, because the individual web pages
could be maintained independently of each
В сообщении от Sunday 20 September 2020 21:10:05 Андрей Спицын via Cin
написал(а):
> The overfull warning is a just info, that latex cant fit line into its
> borders. Its can be skipped if that line looks ok.
> The reference and labels warnings are important, it's indicates that som
nd do the tests. I saw that in Texstudio, in the menu "idefix", there
is the entry "convert to Latex"; does it serve to convert a document
(of libreoffice for example) in latex? Or is it better to rewrite
everything from scratch? Can I make a copy paste of the sentences from
Libr
> PS: where are the doc sources? With the program sources I do not see
> anything like in /doc, perhaps in another repo?
The files in odt are in git:
https://git.cinelerra-gg.org/git/?p=goodguy/documentation.git;a=summary
But as we use them to make the manual in latex, they are chang
It would be great if the manual could be translated from wordpress. I
have no problems with Latex, it is by far the best software for all
kinds of publications. But it is more useful to do it from worpress
because it allows to have the text in English and automatically
available to be
I added a News post to the cinelerra-gg.org website that now points to the
newly converted LaTeX version PDF manual. As before with the odt version,
it is pointed to under Download, Documentation, User Manual.
The News post says it all except the most important parts:
!! *Andrey* (Einhander
> Thanks to IgorB for how-to, Andrea for Latex formatting, and Andrew for
> proofreading. Made a few corrections based on feedback and checked into GIT.
> (Andrea, note I have added a new section to Manual, Authors and
> Contributors, so you may want to checkout all from
connection
Everything up-to-date
other error message:
To https://github.com/Andrea-Paz/cin-manual-latex
! [rejected]master -> master (fetch first)
error: failed to push some refs to
'https://github.com/Andrea-Paz/cin-manual-latex'
suggerimento: Updates were rejected becau
long.
I prefer a semantic line wrap by sentences.
But it's up to user to do a line brake or not.
Novice LaTeX users prefer not to use linewrap.
For a Git usage I prefer use Diff by words.
пн, 1 июл. 2019 г., 19:08 Andrea paz :
> @Olaf.
> Every month I write an email containing LaTeX an
, 2023 at 9:48 AM Andrea paz
wrote:
> > Thanks to IgorB for how-to, Andrea for Latex formatting, and Andrew for
> proofreading. Made a few corrections based on feedback and checked into
> GIT. (Andrea, note I have added a new section to Manual, Authors and
> Contributors, so
@Olaf.
Every month I write an email containing LaTeX and Manual in the title
to continue the discussion and translation work with einhander. I
installed the whole package, plus the Greek and Russian languages. Of
course I also installed an editor, that is TexStudio.
It would be nice if you could
> glossary would be nice.
LaTeX has special package for glossary creation.
Texstudio should be reconfigured to use that package. I will add an
example, and instruction for texstudio.
>
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Hi, Andrey.
Olaf has proposed changes to the structure of the Latex manual. Since
he is not a member of the mailing list, I enclose his attachments here
too.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 04.11.2022 09:30, skrev Andrea paz:
@Terje
can you provide the changes to the manual so that I or Phyllis can
bring them into Latex? You can edit or rewrite anything you want! If
you use latex you can edit the manual directly and then provide
Phyllis with the entire chapter with the
hink that Latex is really a good language to write
> docs apart from math books. ...
I mean that now there are better laguages that permits to write docs in
> ...
> One of my favourite is asciidoc.
>
I see that asciidoc is text format. That for me, personally, is the number
1 reason f
Andrey wrote:
But if you create a vector image it's best to export it as vector PDF
file.
I agree with you. I don't know nothing about LatTex and I thought that
LaTex was not able to digest the pdf format. Sorry.
Thanks!
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists
> It's OK if I'll paste it in mail message, not in repo?
Yeah, all right. All the examples and writings that you put in the old
emails I kept them for study.
I'll try the latex script first, and only for the data.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://list
e future we can do something
> similar. For now, we are stopping at a simple collection of pdfs (but
> we are now close to the end of the manual in LaTeX).
Right, lets first finish what you have. If you are close to finish it,
that is the most sensible thing to do. For the future, I'm h
Hi, Andrey
There is a problem with TOC:
"Contents, page ix. Numbers above 10.6.9 run into the text after them.
It's a Latex setting somewhere, we had this elsewhere before."
I do not know how to solve it, can you do something?
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://
erre
On 20-01-15 00 h 07, Phyllis Smith wrote:
I added a News post to the cinelerra-gg.org <http://cinelerra-gg.org>
website that now points to the newly converted LaTeX version PDF
manual. As before with the odt version, it is pointed to under
Download, Documentation, User Manual.
T
@Terje
can you provide the changes to the manual so that I or Phyllis can
bring them into Latex? You can edit or rewrite anything you want! If
you use latex you can edit the manual directly and then provide
Phyllis with the entire chapter with the changes.
--
Cin mailing list
Cin@lists.cinelerra
I'm sorry: the link:
https://www.cinelerra-gg.org/bugtracker/view.php?id=77#c2466
Il giorno lun 18 nov 2019 alle ore 09:32 Andrea paz
ha scritto:
>
> Hi, Andrey.
> Olaf has proposed changes to the structure of the Latex manual. Since
> he is not a member of the mailing li
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
(was 13.4.7 in the .odt version).
That is the beauty of Latex that it keeps track of all of this stuff.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Thanks again to Andrea. I had to make a single change as my Latex got an
error on: ($#ff00$). I had to remove the 2 $ to solve it.
> 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
> ChromaK
Hi,
@Phyllis. I think it is best not to waste time converting all images
into high quality png. It's a job you can do as you convert chapters
to Latex.
@einhander. I have finished chapter 4 of the manual (3, in the
conversion to Latex). Now how to submit it to your review? I'm not
fam
e done, but sometimes it lacks the space to let an
> image enter its section and the same page. This is the case of fig.
> 10.8 and 16.2, which I cannot fix.
> Latex works like this: we can give indications of where we want an
> image, but then it takes care of finding the best layout.
Hi,
I have added chapters 12 and 13. I have taken the initiative of
splitting the original chapter 13 into two new chapters (12 and 13,
precisely), because I consider them huge and autonomous.
Phyllis, if you prefer a single chapter, with Latex it is very simple
and fast to reunite them.
In the
Thanks!
Sergio
El 18/11/2019 a las 10:36, Andrea paz escribió:
I'm sorry: the link:
https://www.cinelerra-gg.org/bugtracker/view.php?id=77#c2466
Il giorno lun 18 nov 2019 alle ore 09:32 Andrea paz
ha scritto:
Hi, Andrey.
Olaf has proposed changes to the structure of the Latex manual.
Andrea:
>
> @Phyllis
> I'd need the last revision of chapter 4 to try and create it in Latex.
> The .odt file, I mean. Is that possible?
>
> The one that matches the manual that the users see is checked into the git
documentation as file: attributes.odt
https://www.
Thank you Andrea!
Mon, Nov 18, 2019 at 02:36:35PM +0100, Andrea paz написал:
I'm sorry: the link:
https://www.cinelerra-gg.org/bugtracker/view.php?id=77#c2466
Il giorno lun 18 nov 2019 alle ore 09:32 Andrea paz
ha scritto:
Hi, Andrey.
Olaf has proposed changes to the structure of the
On 190831-15:50-0600, Phyllis Smith wrote:
[...]
> https://www.cinelerra-gg.org/download/
> In addition the complete releasenotes.pdf are in that directory.
> And now, presenting the Work-In-Progress (WIP) LaTex manual, which is
> incomplete but which includes the new Masking op
On Mon, 16 Jan 2023, Andrea paz via Cin wrote:
> to contribute to the manual I was thinking of not transposing the new
> additions into Latex right away. I propose to post the contributions
> to the mailing list in odt so that any user can propose, read and edit
> them. LibreOffice
Hi Igor,
Please export them as a vector PDF images.
Latex can handle pdf with ease.
It's also decrease whole file size.
ср, 25 сент. 2019 г., 15:56 Igor BEGHETTO :
> Hi!
> @Phyllis and @Andea_paz
> About Pipeline images for the manual I have done that, if you want.
> Two PNG
> Andrea,
> Latex problem in Auxiliaryprograms.tex that I tried several ways to fix. If
> you have any idea how to fix this, please do so.
Sorry Phyllis, I don't think I understand the problem. I tried
manually copying the script into a file (jpeglist.sh) and it works
without
ommand \DeclareFontFamilySubstitution
added to the LATEX kernel in its 2020-02 release (cf. ltnews31).
>Existing documents can be updated by removing \usepackage{substitutefont}
and replacing all instances of \substitutefont with
\DeclareFontFamilySubstitution.
Best regards,
Andrey
пн, 8 апр. 2024 г. в 17:3
at 2:42 AM Andrea paz
wrote:
> GG's response to Glenn in the forum seems
> (
> https://www.cinelerra-gg.org/forum/help-video/hotkey-to-deselect-all-groups/#post-698
> )
> so clear and interesting to me that I propose to include it in the
> latex manual:
>
>
The little addendum for Andrew. You can setup the github repo for manual
clone the cinelerra's git and bound it to sharelatex.com.
The sharelatex provides full functional latex editor for web browser.
The only limitation on free account I found for myself is compile time.
But you can e
f the manual on sections that I have
not yet seen in the
Master GIT at:
https://github.com/einhander/cin-manual-latex/tree/master/parts
so that I do not generate extra work in the LaTex creation (let me know if
I am wrong).
There is a lot there!! and eventually I hope to learn it all but keepin
next page. So I think it's ok.
As far as I can understand the typography rules that empty space on page
must be filled by text or figures. LaTeX tries it's best to follow this
rule.
Sat, Sep 19, 2020 at 09:38:13PM +0200, Andrea paz via Cin написал:
The problem is when there is no p
Hi, Andrey.
Phyllis put an Index to the CinGG manual in Latex (see git). But I
can't get it to work in TexStudio. I put the following line in
Configure --> Commands --> Makeindex:
makeindex -s nomencl.ist -o CinelerraGG_Manual.nls CinelerraGG_Manual.nlo
but if I try to build i
we will
> have to replace all the images. I propose to postpone this work until
> after the completion of the manual.
> What do you think? I'm fine with any solution.
>
My opinion is that I would like to see the manual completely converted to
Latex before re-doing any images. I
the initiative of
> splitting the original chapter 13 into two new chapters (12 and 13,
> precisely), because I consider them huge and autonomous.
> Phyllis, if you prefer a single chapter, with Latex it is very simple
> and fast to reunite them.
> In the DVD/BD chapter there are thre
Commented it out in common/packages.tex, ran latex build (not up to date
install like Andrea), and checked into GIT so not lost. Thank you both
...Phyllis
On Mon, Apr 8, 2024 at 11:04 AM Андрей Спицын via Cin <
cin@lists.cinelerra-gg.org> wrote:
>
> I think that it should be comme
On Monday, December 13, 2021, Andrea paz
wrote:
> > Andrea,
> > Latex problem in Auxiliaryprograms.tex that I tried several ways to
> fix. If you have any idea how to fix this, please do so.
>
> Sorry Phyllis, I don't think I understand the problem. I tried
> manua
Hi, Andrey.
In the TOC of the Latex manual the spacing between number and
subsection name was set to 3.6em and everything worked fine. See image
4.2em.png
Now, all of a sudden, it has become too small and the 6-digit numbers
overlap the beginning of the name. See image 3.6em.png
I solved it by
file common/settings.tex line 5
from \geometry{right=2.0cm} to \geometry{right=3.0cm}
If you want to change chapter style go to line 31 and change
\chapterstyle{madsen} to something else.
Some chapter styles are shown in
http://mirrors.ctan.org/info/latex-samples/MemoirChapStyles/MemoirChapStyles.pdf
Andrea,
The table looks really good! Later today, gg will replace the current
CinelerraGG_manual_WIP.pdf on the website with your latest. You are
getting really close to full LaTex conversion -- I can hardly wait to get
my hands on it. Thanks, gg/Phyllis
On Tue, Oct 29, 2019 at 8:54 AM Andrea
with Tex/LaTeX files.
po4a has a few seperate commands:
po4a-gettextize, convert an original file (and its translation) to a PO file
po4a-normalize, normalize a documentation file by parsing it in po4a, and
writing it back
po4a-translate, convert a PO file back to documentation format
po4a
(where it is located), but always within
the same section, as Andrew prefers; or to let Latex fill the blank
space with the next section and put the image at the beginning of the
next page. I've let Latex do it so far, but if others prefer Andrew's
idea, it's not difficult to fix
I made changes in windows.tex to eliminate the second TODO present in
the Latex code.
I also made other changes and small additions. See if they are okay.
The third TODO refers to the creation of a real table from a list. We
can see this list in the attached figure.
I don't know how to mak
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 f
there should be no size problem. But better to hear Sam's opinion
as well.
As for the danger of leaving a thread open without getting to Latex,
it is true: it is a real danger.
@Georgy
I have never used Lyx but I see that it still relies on texlive. I was
just thinking about the possibility
o ambitious?
>
It does sound like a lot of work and it would certainly be worthwhile. BUT
I think we need to wait until it is fully converted to LaTex (Andrea/Andrey
are getting pretty close as far as I know). And I have many additions to
make for new features that have been added recentl
Hi,
@Andrea
Thank you for your kind words. Let's start from your last question.
There a several ways to do that.
1. Use Writer2Latex. In debian it in libreoffice-writer2latex package.
Create table in Writer, select it, then go to Export... click the
Selection checkbox and select LaT
Thanks to IgorB for how-to, Andrea for Latex formatting, and Andrew for
proofreading. Made a few corrections based on feedback and checked into
GIT. (Andrea, note I have added a new section to Manual, Authors and
Contributors, so you may want to checkout all from GIT because
Hi,
@ einhander
I'm progressing slowly with chapter 9 (plugins.odt) [Cursed is he who
stretched it out ;-)]. I have the problem of the big tables of
Libreoffice Writer to import in latex (in Sketcher and Titler
sections). How should this be done? I have not found any information
about
Add glossary.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
I'm sorry, my fault. It' ok now.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
On Thu, 10 Feb 2022 mni...@zap.a2000.nl wrote:
> > 1) As the manual is absolutely architecture-independent, nothing is
> > against building it under some most convenient platform (that, for
> > example, where all the necessary latex/html tools are
> > installed/configured)
It works perfectly; thank you very much.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
at 5:55 AM Andrea paz via Cin <
cin@lists.cinelerra-gg.org> wrote:
> Hi, Andrey.
> Phyllis put an Index to the CinGG manual in Latex (see git). But I
> can't get it to work in TexStudio. I put the following line in
> Configure --> Commands --> Make
л:
Hi, Andrey
There is a problem with TOC:
"Contents, page ix. Numbers above 10.6.9 run into the text after them.
It's a Latex setting somewhere, we had this elsewhere before."
I do not know how to solve it, can you do something?
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https:/
Yes, it plays. Thank you. No problem with "mathtext.sty" now.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Hi people,
I am a lurker in this ml, I am sorry, I also am not really a cinelerra
user but I do like _very much_ the project, the spirit, the people.
To cut through the chase I want to contribute somehow with a suggestion.
Here is my 2 cents: I see you talk about Latex because you seem to use it
OK, let's go with the 4.2em. Thank you.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Add chapter 16.
Pdf at:
https://www.dropbox.com/s/0js49r47s0qu621/CinelerraGG_Manual.pdf?dl=0
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
You forgot about a fourth person: Phyllis!
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
I forgot window.tex.
Windows.tar.gz
Description: application/gzip
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
I forgot: I added the section on VHS capture at the end of chapter 12.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
located), but always within
> the same section, as Andrew prefers; or to let Latex fill the blank
> space with the next section and put the image at the beginning of the
> next page. I've let Latex do it so far, but if others prefer Andrew's
> idea, it's not difficult to
I forgot to attach Plugins.tex where I had made some changes.
Plugins.tar.gz
Description: application/gzip
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Add glossary.
Good job! I've made small changes in chapter 8 (approx. 1 line) and pushed into
my repo.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
feature in product and want to keep old stable
version. Good how-to about branches in git located at:
https://nvie.com/posts/a-successful-git-branching-model/
So in short to transfer my changes into your repository, you have to crate pull
requests in your
repository, a select base repository An
- 1) I think we settled on the style of the pdf awhile back as a
group discussion and all styles have merit,
and 2) I do not pay any attention to errors that LaTex generates unless it
actually stops because I do not even know what they mean anyway and do not
really plan on learning LaTex due to lack
Since I will be making new AppImages tomorrow, I wanted to make sure the
HTML and PDF manuals contained the information on the SGE 2 new plugins.
Not only was the work SGE did on the code huge, so was the documentation.
Luckily Andrea was willing to put it in Latex format. I changed some
wording
2. Register at github.com and add your public key (id_rsa.pub) in that
page https://github.com/settings/keys
3. Fork my repo (https://github.com/einhander/cin-manual-latex) by
clicking "Fork" button.
4. Clone your own fork of repo to a local folder ( git clone
g...@github.com:YOUR_NAME
When this text has passed the last revision, let me know that I will
put it in latex in the manual.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Hi Andrey!
Okay. I thought You wanted the PNGs file for the illustrations.
Here the PDFs.
@Phyllis
Thanks!
compositing_pipeline-masks.pdf
Description: Adobe PDF document
compositing_pipeline-01.pdf
Description: Adobe PDF document
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.c
is to move the large sections to
"x.1-9.y" range of TOC if it is applicable.
Best regards,
Andrey
сб, 23 янв. 2021 г. в 11:45, Andrea paz via Cin :
> Hi, Andrey.
> In the TOC of the Latex manual the spacing between number and
> subsection name was set to 3.6em and everythin
lways just like to
try it anyway.
Additionally... Translate the documentation, does it sound too
ambitious?
It does sound like a lot of work and it would certainly be
worthwhile. BUT I think we need to wait until it is fully converted
to LaTex (Andrea/Andrey are getting pretty close a
Andrea, my understanding is minimal, but since Terje says it looks good,
then I say when you are satisfied with it yourself, let's make it a PDF
document to put on the website and have the Manual reference it.
I used this shell script to Latex create Terje's
Nice work @IgorBeg.Thanks for the corrections. I put the link to
download the latex and also the pdf of the proxy section so you can
see it right away:
https://ufile.io/0g9vqrx6
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Hi,
uploaded to github my latest revision of chapter 5 (now it is complete).
- Same Caption error
- How to colorize (red) some words inside the tables of the Shuttle?
PS: good news the Glossary!
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Added chapter 6.
I had problems with git and I could not synchronize our two
repositories. I downloaded yours and updated mine locally. Then I
uploaded it back to git. I hope it's okay now.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Hi Andrea,
Your last commit has conflicting merge. See lines in .tex
files. We have to deal with it manually.
I've made my changes based on your version.
I can sync our versions again based on your version.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/
Thanks, I merged your commits into my repo.
вт, 8 окт. 2019 г., 15:33 Andrea paz :
> I'm sorry, my fault. It' ok now.
> --
> 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.cinelerr
I also think it is better to complete the manual in Latex.
As for the term cakewalk, it is also an Afro-American dance:
https://en.wikipedia.org/wiki/Cakewalk
And an audio editing program:
https://www.bandlab.com/products/cakewalk
;-)
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https
Added chapter 10 (only 4 pages).
I was thinking of using "subcaption" to create grids of images each
with its own caption. What do you think? Actually, I tried to put it
on, but it doesn't work for me.
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/c
Hi Andrea,
I have added chapters 12 and 13. I have taken the initiative of
splitting the original chapter 13 into two new chapters (12 and 13,
I have an error:
File `images/preset01.png' not found
Is it preset.png file?
--
Best regards,
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://li
In the manual; in chapter 14 ("the 5 multi-s"; section "14.5 multi
session"), you can say that, by starting multiple sessions of CinGG,
you can assign to each one its own .bcast through:
Settings --> Preferences --> Interface --> Index files --> index files
go here: ?
--
Cin mailing list
Cin@lists
Please, I don't quite understand where I went wrong. I am confused.
Can you write the exact text to put in the manual, also using your
wonderful example and images, and I will translate it into latex to
upload it?
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-g
About compositing_pipeline_masks you're completely right. I put it in
its place (mask section) and apologize (same dropbox link).
As for the section on the mask tool, I think it needs to be rewritten
to incorporate the latest news. Phyllis, could you get me the odt?
--
Cin mailing list
Cin@lists.c
1 - 100 of 251 matches
Mail list logo
