two more english tips?
Because this part of Cinelerra(GG) also not intuitive for modern users - what about adding two more lines in tips.en? diff --git a/cinelerra-5.1/tips/tips.en b/cinelerra-5.1/tips/tips.en index 781df953..8b2dc4fc 100644 --- a/cinelerra-5.1/tips/tips.en +++ b/cinelerra-5.1/tips/tips.en @@ -26,6 +26,12 @@ Use the +/- keys in the Compositor window to zoom in and out. Pressing Alt while clicking in the cropping window causes translation of all 4 points. +Batch jobs in batchrender respect their saved playhead position, so set it at +very beginning if you want whole project to be rendered. + +You can batchrender only region of project by defining selection with mouse +highlight or setting in/out points before saving it as EDL (Shift-S). + Pressing Tab over a track toggles the Record status. Pressing Shift-Tab over a track toggles the Record status of all the other tracks. If you think wording is OK - may be active translators (incl. me) should add the same to their tip files. (I tried this procedure with mouse highlight and in-out points by saving same proj four times with different selection and then making batch out of them) Project files also attached. media file should be at https://cloud.mail.ru/public/KKY8/o86j62p2z (quite a captivity propaganda translated to russian, from my point of life, but quick enough for testing something)
It would be nice to add these lines in the tips, since this is a great rarity and people should know it ... so they don't get frustrated with this wizard. I keep thinking, is it possible to add a button (Help) that opens a short pdf about the use of this tool? I could make this pdf, with very little text and explicit images on how to use it. It really is very unintuitive, but I think that any user with a few lines is going to take advantage of this tool. The playhead thing is something very strange and that people should know ... this should be an option in the wizard interface, it does not have to be hidden, such as the ones of Save EDL and that of the projects if they coincide or not. Something like that: □ Render from the position of the play cursor (or cursor of insertion) Can you do something like that, is it easy? Would Phyllis allow it? This simple option would stop this feature from being something that many users see as a wizard bug. And former users would simply have to enable this option. If I have to extract parts of a video I use Avidemux, because of how simple and fast it is, but I liked the selections to extract parts of a project in a batch, it is a shame to have to make an xml for each fragment when You could add the option I mentioned in another email, or create new render marks, which would go in pairs, label render start, label render finish, and be able to define the desired fragments with these labels, or as I indicated with the points of input and output and the time code in the render. Although I understand that this could be too much work for you. These labels that I quote usually carry these icons: ▶ = for the beginning of the render, ◀ = to indicate where it ends. (I hope your unicode setup shows the correct characters) But just in case I make an image. [image: 42.png] In the event that only a beginning mark is indicated, the render will be made from this mark at the end, if only the final mark is indicated, then from the beginning of the project to this mark. These marks may or may not be visible from the "Show Overlays" window as "Render Marks" and in the batch render window, an option: □ Use render marks ▶ ◀ (insert render labels). A new section could be added to the edit menu: Labels ... Insert generic label l Label of Render - Start Label of Render - End In the Render window under the option to use render marks there could be icons to insert these labels. ▶ ◀ Maybe it is too much work to do something like that, I wish I had programming knowledge and could help. For me, the important thing now would be the option cited for the position of the cursor and a help button that opens a short pdf that would be attached to the Cinelerra installation files and can be in English if there is no translation or in local language if someone translates them. I could do the English, Spanish and French (Although both in English and French someone native should review them). I repeat that it would take very little text. Greetings Andrew and thank you very much for your excellent work. El jue, 21 ene 2021 a las 15:52, Andrew Randrianasulu via Cin (< [email protected]>) escribió:
Because this part of Cinelerra(GG) also not intuitive for modern users - what about adding two more lines in tips.en?
diff --git a/cinelerra-5.1/tips/tips.en b/cinelerra-5.1/tips/tips.en index 781df953..8b2dc4fc 100644 --- a/cinelerra-5.1/tips/tips.en +++ b/cinelerra-5.1/tips/tips.en @@ -26,6 +26,12 @@ Use the +/- keys in the Compositor window to zoom in and out. Pressing Alt while clicking in the cropping window causes translation of all 4 points.
+Batch jobs in batchrender respect their saved playhead position, so set it at +very beginning if you want whole project to be rendered. + +You can batchrender only region of project by defining selection with mouse +highlight or setting in/out points before saving it as EDL (Shift-S). + Pressing Tab over a track toggles the Record status. Pressing Shift-Tab over a track toggles the Record status of all the other tracks.
If you think wording is OK - may be active translators (incl. me) should add the same to their tip files.
(I tried this procedure with mouse highlight and in-out points by saving same proj four times with different selection and then making batch out of them)
Project files also attached. media file should be at https://cloud.mail.ru/public/KKY8/o86j62p2z
(quite a captivity propaganda translated to russian, from my point of life, but quick enough for testing something) -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
I have reworded these tips and hope to check them in today (+ the transition fixes of Andrew). I keep thinking, is it possible to add a button (Help) that opens a short
pdf about the use of this tool? I could make this pdf, with very little text and explicit images on how to use it. It really is very unintuitive, but I think that any user with a few lines is going to take advantage of this tool.
A future goal was to hook up the HTML form of the manual for help via the "h" key. That would take you right to: https://cinelerra-gg.org/download/CinelerraGG_Manual/Batch_Rendering.html
I was referring to a "first steps" guide in English, you call it "Quick Start". Today the time that I allot every day to write Cinelerra tutorials I am going to dedicate to making an example of what I mean. The manual is very good, but there are people who when they see so much text get scared. :-D I do not know if you saw the error that I reported about the first time it is used and it is intended to export in mp4. Perhaps the solution would be as simple as choosing FFMPEG that the extension box is empty, to force the user to put the desired extension there. I am going to make this example pdf and send it to you in an email, along with the .odt file. Also the es.po file in which I had to make an exception in using lowercase of a term, because people are used to seeing the shortcuts in uppercase and a user has notified me that accessing the tags was not working and that it was opening a clips window... and this is because he confused the ( l ) (lowercase letter L) with the ( I ) (uppercase i). El jue, 21 ene 2021 a las 21:10, Phyllis Smith via Cin (< [email protected]>) escribió:
I have reworded these tips and hope to check them in today (+ the transition fixes of Andrew).
I keep thinking, is it possible to add a button (Help) that opens a short
pdf about the use of this tool? I could make this pdf, with very little text and explicit images on how to use it. It really is very unintuitive, but I think that any user with a few lines is going to take advantage of this tool.
A future goal was to hook up the HTML form of the manual for help via the "h" key. That would take you right to:
https://cinelerra-gg.org/download/CinelerraGG_Manual/Batch_Rendering.html -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
В сообщении от Thursday 21 January 2021 23:48:55 Rafa Mar Multimedia en Gnu\Linux via Cin написал(а):
I was referring to a "first steps" guide in English, you call it "Quick Start". Today the time that I allot every day to write Cinelerra tutorials I am going to dedicate to making an example of what I mean. The manual is very good, but there are people who when they see so much text get scared. :-D
I do not know if you saw the error that I reported about the first time it is used and it is intended to export in mp4. Perhaps the solution would be as simple as choosing FFMPEG that the extension box is empty, to force the user to put the desired extension there.
I saw this error, and tried to combat it ... no results so far :/
I am going to make this example pdf and send it to you in an email, along with the .odt file.
Also the es.po file in which I had to make an exception in using lowercase of a term, because people are used to seeing the shortcuts in uppercase and a user has notified me that accessing the tags was not working and that it was opening a clips window... and this is because he confused the ( l ) (lowercase letter L) with the ( I ) (uppercase i).
El jue, 21 ene 2021 a las 21:10, Phyllis Smith via Cin (< [email protected]>) escribió:
I have reworded these tips and hope to check them in today (+ the transition fixes of Andrew).
I keep thinking, is it possible to add a button (Help) that opens a short
pdf about the use of this tool? I could make this pdf, with very little text and explicit images on how to use it. It really is very unintuitive, but I think that any user with a few lines is going to take advantage of this tool.
A future goal was to hook up the HTML form of the manual for help via the "h" key. That would take you right to:
https://cinelerra-gg.org/download/CinelerraGG_Manual/Batch_Rendering.html -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
I saw this error, and tried to combat it ... no results so far :/
the extension box empty, to force the user to put the desired extension there? ---- Quik start batch render (en). El jue, 21 ene 2021 a las 23:44, Andrew Randrianasulu via Cin (< [email protected]>) escribió:
В сообщении от Thursday 21 January 2021 23:48:55 Rafa Mar Multimedia en Gnu\Linux via Cin написал(а):
I was referring to a "first steps" guide in English, you call it "Quick Start". Today the time that I allot every day to write Cinelerra tutorials I am going to dedicate to making an example of what I mean. The manual is very good, but there are people who when they see so much text get scared. :-D
I do not know if you saw the error that I reported about the first time it is used and it is intended to export in mp4. Perhaps the solution would be as simple as choosing FFMPEG that the extension box is empty, to force the user to put the desired extension there.
I saw this error, and tried to combat it ... no results so far :/
I am going to make this example pdf and send it to you in an email, along with the .odt file.
Also the es.po file in which I had to make an exception in using
lowercase
of a term, because people are used to seeing the shortcuts in uppercase and a user has notified me that accessing the tags was not working and that it was opening a clips window... and this is because he confused the ( l ) (lowercase letter L) with the ( I ) (uppercase i).
El jue, 21 ene 2021 a las 21:10, Phyllis Smith via Cin (< [email protected]>) escribió:
I have reworded these tips and hope to check them in today (+ the transition fixes of Andrew).
I keep thinking, is it possible to add a button (Help) that opens a short
pdf about the use of this tool? I could make this pdf, with very little text and explicit images on how to use it. It really is very unintuitive, but I think that any user with a few lines is going to take advantage of this tool.
A future goal was to hook up the HTML form of the manual for help via the "h" key. That would take you right to:
https://cinelerra-gg.org/download/CinelerraGG_Manual/Batch_Rendering.html
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
В сообщении от Friday 22 January 2021 05:42:55 Rafa Mar Multimedia en Gnu\Linux via Cin написал(а):
I saw this error, and tried to combat it ... no results so far :/
the extension box empty, to force the user to put the desired extension there?
I think problem may be exactly in this - we see selection, but no specific signal (generated when we *change* selection) sent yet, so whole function send down empty string, and ffmpeg class not prepared for this .... Again, a lot of functions (re)used in different places, so fixing this a bit harder than just sticking one value in one file. Or at least this file might be not that one ...
---- Quik start batch render (en).
El jue, 21 ene 2021 a las 23:44, Andrew Randrianasulu via Cin (< [email protected]>) escribió:
В сообщении от Thursday 21 January 2021 23:48:55 Rafa Mar Multimedia en Gnu\Linux via Cin написал(а):
I was referring to a "first steps" guide in English, you call it "Quick Start". Today the time that I allot every day to write Cinelerra tutorials I am going to dedicate to making an example of what I mean. The manual is very good, but there are people who when they see so much text get scared. :-D
I do not know if you saw the error that I reported about the first time it is used and it is intended to export in mp4. Perhaps the solution would be as simple as choosing FFMPEG that the extension box is empty, to force the user to put the desired extension there.
I saw this error, and tried to combat it ... no results so far :/
I am going to make this example pdf and send it to you in an email, along with the .odt file.
Also the es.po file in which I had to make an exception in using
lowercase
of a term, because people are used to seeing the shortcuts in uppercase and a user has notified me that accessing the tags was not working and that it was opening a clips window... and this is because he confused the ( l ) (lowercase letter L) with the ( I ) (uppercase i).
El jue, 21 ene 2021 a las 21:10, Phyllis Smith via Cin (< [email protected]>) escribió:
I have reworded these tips and hope to check them in today (+ the transition fixes of Andrew).
I keep thinking, is it possible to add a button (Help) that opens a short
pdf about the use of this tool? I could make this pdf, with very little text and explicit images on how to use it. It really is very unintuitive, but I think that any user with a few lines is going to take advantage of this tool.
A future goal was to hook up the HTML form of the manual for help via the "h" key. That would take you right to:
https://cinelerra-gg.org/download/CinelerraGG_Manual/Batch_Rendering.html
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
I think problem may be exactly in this - we see selection, but no specific signal (generated when we *change* selection) sent yet, so whole function send down empty string, and ffmpeg class not prepared for this ....
I am useless for the code, I am sorry I cannot help, I can only think of the option that the first time FFMPEG is chosen the extension box is empty, that the user sees it empty, without content, this will force him to choose the extension, or at least the error will not reference the .mp4 file. Another solution I can think of is to change mp4 to an extension that is not usual today, simply to force the user to change it. Anyway, in the guide that I have written to facilitate the understanding of the tool, I recommend clicking on mp4 the first time the wizard is used to avoid this error. I sent it to you in case you want to translate in Russian. I would love to know Russian, it is a language that has always been pleasant to the ear. El vie, 22 ene 2021 a las 8:51, Andrew Randrianasulu via Cin (< [email protected]>) escribió:
В сообщении от Friday 22 January 2021 05:42:55 Rafa Mar Multimedia en Gnu\Linux via Cin написал(а):
I saw this error, and tried to combat it ... no results so far :/
the extension box empty, to force the user to put the desired extension there?
I think problem may be exactly in this - we see selection, but no specific signal (generated when we *change* selection) sent yet, so whole function send down empty string, and ffmpeg class not prepared for this ....
Again, a lot of functions (re)used in different places, so fixing this a bit harder than just sticking one value in one file. Or at least this file might be not that one ...
---- Quik start batch render (en).
El jue, 21 ene 2021 a las 23:44, Andrew Randrianasulu via Cin (< [email protected]>) escribió:
В сообщении от Thursday 21 January 2021 23:48:55 Rafa Mar Multimedia en Gnu\Linux via Cin написал(а):
I was referring to a "first steps" guide in English, you call it "Quick Start". Today the time that I allot every day to write Cinelerra tutorials I am going to dedicate to making an example of what I mean. The manual is very good, but there are people who when they see so much text get scared. :-D
I do not know if you saw the error that I reported about the first time it is used and it is intended to export in mp4. Perhaps the solution would be as simple as choosing FFMPEG that the extension box is empty, to force the user to put the desired extension there.
I saw this error, and tried to combat it ... no results so far :/
I am going to make this example pdf and send it to you in an email,
along
with the .odt file.
Also the es.po file in which I had to make an exception in using lowercase of a term, because people are used to seeing the shortcuts in uppercase and a user has notified me that accessing the tags was not working and that it was opening a clips window... and this is because he confused the ( l ) (lowercase letter L) with the ( I ) (uppercase i).
El jue, 21 ene 2021 a las 21:10, Phyllis Smith via Cin (< [email protected]>) escribió:
I have reworded these tips and hope to check them in today (+ the transition fixes of Andrew).
I keep thinking, is it possible to add a button (Help) that opens a short
pdf about the use of this tool? I could make this pdf, with very little text and explicit images on how to use it. It really is very unintuitive, but I think that any user with a few lines is going to take advantage of this tool.
A future goal was to hook up the HTML form of the manual for help via the "h" key. That would take you right to:
https://cinelerra-gg.org/download/CinelerraGG_Manual/Batch_Rendering.html
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
В сообщении от Friday 22 January 2021 12:41:18 Rafa Mar Multimedia en Gnu\Linux via Cin написал(а):
I think problem may be exactly in this - we see selection, but no specific signal (generated when we *change* selection) sent yet, so whole function send down empty string, and ffmpeg class not prepared for this ....
I am useless for the code, I am sorry I cannot help, I can only think of the option that the first time FFMPEG is chosen the extension box is empty, that the user sees it empty, without content, this will force him to choose the extension, or at least the error will not reference the .mp4 file.
Another solution I can think of is to change mp4 to an extension that is not usual today, simply to force the user to change it.
I think this may affect normal rendering too (because they use same code!) But something to test more ....
Anyway, in the guide that I have written to facilitate the understanding of the tool, I recommend clicking on mp4 the first time the wizard is used to avoid this error. I sent it to you in case you want to translate in Russian. I would love to know Russian, it is a language that has always been pleasant to the ear.
Sorry, I'm very bad at translating even few pages of documentation :{ I think you did excellent work on making this document, THANK YOU A TON! There might be typo at very last line ("manual inline.") Do you mean "online manual" ?
El vie, 22 ene 2021 a las 8:51, Andrew Randrianasulu via Cin (< [email protected]>) escribió:
В сообщении от Friday 22 January 2021 05:42:55 Rafa Mar Multimedia en Gnu\Linux via Cin написал(а):
I saw this error, and tried to combat it ... no results so far :/
the extension box empty, to force the user to put the desired extension there?
I think problem may be exactly in this - we see selection, but no specific signal (generated when we *change* selection) sent yet, so whole function send down empty string, and ffmpeg class not prepared for this ....
Again, a lot of functions (re)used in different places, so fixing this a bit harder than just sticking one value in one file. Or at least this file might be not that one ...
---- Quik start batch render (en).
El jue, 21 ene 2021 a las 23:44, Andrew Randrianasulu via Cin (< [email protected]>) escribió:
В сообщении от Thursday 21 January 2021 23:48:55 Rafa Mar Multimedia en Gnu\Linux via Cin написал(а):
I was referring to a "first steps" guide in English, you call it "Quick Start". Today the time that I allot every day to write Cinelerra tutorials I am going to dedicate to making an example of what I mean. The manual is very good, but there are people who when they see so much text get scared. :-D
I do not know if you saw the error that I reported about the first time it is used and it is intended to export in mp4. Perhaps the solution would be as simple as choosing FFMPEG that the extension box is empty, to force the user to put the desired extension there.
I saw this error, and tried to combat it ... no results so far :/
I am going to make this example pdf and send it to you in an email,
along
with the .odt file.
Also the es.po file in which I had to make an exception in using lowercase of a term, because people are used to seeing the shortcuts in uppercase and a user has notified me that accessing the tags was not working and that it was opening a clips window... and this is because he confused the ( l ) (lowercase letter L) with the ( I ) (uppercase i).
El jue, 21 ene 2021 a las 21:10, Phyllis Smith via Cin (< [email protected]>) escribió:
I have reworded these tips and hope to check them in today (+ the transition fixes of Andrew).
I keep thinking, is it possible to add a button (Help) that opens a short > pdf about the use of this tool? > I could make this pdf, with very little text and explicit images on how > to use it. It really is very unintuitive, but I think that any user with a > few lines is going to take advantage of this tool. > > A future goal was to hook up the HTML form of the manual for help via the "h" key. That would take you right to:
https://cinelerra-gg.org/download/CinelerraGG_Manual/Batch_Rendering.html
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
participants (3)
-
Andrew Randrianasulu -
Phyllis Smith -
Rafa Mar Multimedia en Gnu\Linux