- Cin - Cinelerra-GG Mailing Lists

Google summer of code 2019?
by W P 08 Dec '18

08 Dec '18

1 0

Today's GIT repository checkins + Ubuntu16 and Mint 18 test builds
by Phyllis Smith 07 Dec '18

07 Dec '18

Because this covers a couple of BugTracker issues, I thought it best to email a summary. 1) Adjustable size for thumbnails in Resources window for Media, Proxy, and Clips via Settings->Preferences, Appearance tab, Layout section right hand side. Defaults are as what has been in effect. View thumbnail, bigger number = bigger thumbnail. Vicon memory size = how much memory to use for each vicon -- this helps solve the pixelization when making the thumbnails bigger but takes more memory. Vicon color mode = low, medium, or high - also takes more memory. 2) Wheel mode to temporarily make preview thumbnail bigger. This is nice and we did not even know you could do this in the browser. You only use this in preview mode - wheel the middle mouse button up or down after you click on the thumbnail and get into preview mode. Once in that mode, you can either wheel on the thumbnail itself or the preview. 3) Clips now also have a preview mode, but only a still image instead of the 5 second play. 4) 2 bugs in Proxy Resources window display were fixed where the thumbnails were just plain crazy. Part of the craziness occurred when the media had more than 1 proxy type - that is a proxied mp4 and a proxied webm, for example. 5) The drag select white bar highlight was not always correctly highlighting. This was a bug we discovered while looking into a solution for issue #7 (which is scheduled to have work start on some of it tomorrow). 6) Inter-View mode - This is the EXCITING NEW FEATURE prompted by Pierre's request. We were dubious at first, but now think it is a very useful function for more than 1 reason. A short how to is next. - do your editing as usual - make sure you are in Preview mode in the Resources window; that is the right facing green colored arrow to the left of the word Search which is surrounded by a gold color when enabled. - middle mouse click on a thumbnail in the Resources window and a popup occurs of that media with a white colored bar at the top and a red colored bar at the bottom The bars represent the presence or absence (the black sections) of where that media is used on the timeline. Here are the buttons: - click on the top white or black spaces in the top bar, and in the Viewer, the In/Out [/] pointers will show location of that edit - click on the bottom red or black space in the bottom bar, and in the timeline and composer the position will change AND you can even drag on this line and it will correspondingly update the position in the timeline - Ctrl-click on the bottom bar and the timeline and composer are re-positioned to the beginning of that section NOTE to Pierre, point #2 in your latest Issue #5 is not feasible because the timeline and the composer should be at the same place to ensure that an insert or delete occur in the right place. -Shift-click on the bottom bar and a "selection" is made of that section and the composer is updated with that start position NOTE to Pierre, switching #1 and #3 as in issue #5 note would make this inconsistent with "shift-click" as already designated in the timeline as selecting/highlighting a section. I hope this makes sense to you. NOTE to IgorBeg, I hope you come up with a demonstration of this to put on datafilehost so other users can see it. See: https://www.cinelerra-gg.org/download/testing/cinelerra-5.1-ub16-x86_64-sta… https://www.cinelerra-gg.org/download/testing/cinelerra-5.1-mint18-x86_64-s…

2 2

First message to the new mailing list (and can RSS feeds be added to the website news?)
by W P 07 Dec '18

07 Dec '18

3 3

Bug Tracking, again
by Andrea paz 05 Dec '18

05 Dec '18

Sorry, I still have a couple of questions about how to handle bug tracking. I wanted to ask for the following changes: a) Forum: you can change the title to insert, for example; [Solved]. Another requirement is to insert a Logout button. b) Bug Tracker: As mentioned by Pierre, make sure that every bug you enter automatically results in a notification in the mailing-list. Put a Legend for visual symbols used to describe bugs (orange dash; red arrow, etc.). c) Documentation: Also include a link to the manual-CV for basic operation. 1) Are they requested by Bug Tracker --> new features, or is the mailing list always better and, after any discussion, create the request in Bug Tracker? I don't want to clog the page with useless or even wrong requests (for my ignorance). 2) Is it better to make 3 separate requests for a), b) and c)? Or is it better to split even more, for example in the case of the forum (a), make two separate requests for [Solved] and for Logout? I apologise again for the insistence, but I think that once these doubts have been resolved I should understand the best procedure to use.

4 5

Neophyte
by Andrea paz 04 Dec '18

04 Dec '18

Olaf, can I ask you the favor to update the image in settings/Preference/About by changing "Unify" to "Infinity"? It would make Neophyte more homogeneous with the new website.

1 0

my compöliments
by Andre Gronwald 03 Dec '18

03 Dec '18

hi, just wanted to say thanks to all for your effort: the new site looks great, and the development done for cin-gg is not what someone might expect - it is aboslutely great. although there were some complaints which might be correct, I think based on the fact that some guys are spending there time to improve cin-gg without any monetary benefit from it is exceptional. I wish I could support as well, but I am not a real developer (more a script kiddie). so thanks a lot! i enjoy working with cin-gg in the next weeks, when i have some more time again. regard,s andre

2 1

Bugtracker issue #5 - just email this time until...
by Phyllis Smith 03 Dec '18

03 Dec '18

Pierre: Since we do not know if you noticed issue #5 in the bugtracker yet, I am sending email this 1 time. GG has created a mod that we believe will make it easier to see what you requested -- he coded it in a manner that "fit" and that satisfied the methods he would actually use if he were doing this. This is NOT yet checked into GIT because I have not had a chance to test much yet. There is a Mint 18 test build at: https://cinelerra-gg.org/download/testing/cinelerra-5.1-mint18-x86_64-stati… And an ubuntu16 build at: https://cinelerra-gg.org/download/testing/cinelerra-5.1-ub16-x86_64-static.… If you have a chance to test, please "add a note" to the bugtracker issue with results. How to use: 0) test create a cut and a paste into media on the timeline (just so you can see what the following does) 1) turn on preview in the Resource window 2) mouse to the media that you want to see 3) click the middle mouse button on that media 4) you will see the a mini-view of the media first 5 seconds (you should hear no audio) 5) a White colored bar will be on the top of this mini-view, each segment (black/white) is a hot spot. 6) a Red colored bar will be on the bottom, clicks on it reset the main window timeline position. 7) you will see Yellow colored lines drawn from the top to the bottom showing where the media is or is not 8) click on a space on the top White colored bar, and voila! (I think that is French) that section is loaded in the viewer with In/Out [/] set to the clip of that section of the media. Tweak the edit in viewer, and then paste or overwrite to the timeline. 9) click on a space on the bottom Red colored bar and you will see where that exists on the timeline AND you can drag scroll along this color bar. Remember this is not a real window and if your mouse just leaves the window by a little bit, you will have to middle mouse button click again to get it back. Also, when in previewing mode, if you just mouse over another media file in Resources, it too will automatically show the White/Red bars.

4 3

Add in bug tracker
by Andrea paz 03 Dec '18

03 Dec '18

Sam, I was thinking of adding the following features to your request in the mask bug tracker: 1 - To be able to rotate the masks around a Pivot Point that we can set. 2 - To be able to resize the masks. 3 - Clone a mask on the same track (for example clone a Uruk-Ai in an entire army). What do you think?

2 1

To Forum Administrator
by Andrea paz 03 Dec '18

03 Dec '18

Stupidly I got the wrong user name for the forum (with a space). Now I'm blocked: I can't change it because the email is already registered and I can't proceed because the user name is wrong. Can you delete it so that it can start again?

2 1

Fwd: Clarification (bug tracker and mailing-list)
by Phyllis Smith 02 Dec '18

02 Dec '18

(This may be a duplicate - when I replied, I think it only went to Andrea. I will have to check why). Phyllis ---------- Forwarded message --------- From: Phyllis Smith <phylsmith2017(a)gmail.com> Date: Sun, Dec 2, 2018 at 6:45 AM Subject: Re: [Cin] Clarification (bug tracker and mailing-list) To: Andrea paz <gamberucci.andrea(a)gmail.com> Andrea: glad you like the new website. Sam used a lot of his artistic talent so it looks pretty good! I saw that the Bug Tracker also includes requests for new features, > not just Bug. For example, new features for masks. If I want to > request a new feature should I use the bug tracker or mailing-list? > Another question: If I want to add other features to a bug already > written by others (e.g. more options to the mask bug), can I add it to > the existing bug (with a note) or do I have to create a new one? > > Yes, the Bug Tracker is for new features. This surprised me also. If you use the pulldown on the *Severity *field, you will see "*Feature*" as one of the options. Please use that and it will be easy to organize. Yes, *add to an existing request with a Note *so it will be all in one place. This will be a lot easier to keep track of what is needed. I had to look through a number of emails to put this request together in the first place. Also, there was 1 change I made to your latest plugin.opts file that was checked in. The "chorus" plugin was not commented because it does function and that is what you had, but on the end of the line you had "### Invalid argument" which I took off because I do not know if cinelerra handles the comment correctly or just passes it to ffmpeg. gg/Phyllis

1 0