[CinCVS] End credit scrolling: it works! =)
Hello, Thanks to Andraz and Joe help, I managed to create a fine scrolling from Cinelerra. Before that, I had to use Imagemagick and Mjpegtools to convert my end scrolling picture into an mpeg2video file which I then imported into Cinelerra. Here's what I did: - create a new video track - import the picture - click on the "Generate keyframes while tweeking" small icon (it looks like a key) on the main window - I modify the Y position of the camera, in the compositor window (one can click on the "?" icon to enter the value directly), when I'm at the start of the scrolling - I click on the end of the scrolling, and then I go back 1 frame, and I edit the Y camera position again - I then go back to the main window, and I then select "Camera Y" in the view menu. - I then type "Alt-F" to modify the "Camera Y" green line height, to see it entirely on the video track - then I click on the start keyframe while typing "CTRL" to modify the keyframe curve slope - I do the same for the end keyframe, the goal being to get a straight line between the start and end keyframes And then I get a smooth and constant speed scrolling! Thank you very much for the help, guys !!! =) Nicolas, Paris. ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCVS] Can't scroll picture. I think that's a bug... :-/
Hello, Joe explained me how to use those handles and the CTRL key on the timeline. He even sent me an example .xml file to show me. Thanks you very much, Joe! =) Well, I then discovered the method described by Joe (which is, I assume, the RIGHT method to scroll a picture in Cinelerra) does not work with tall pictures. To explain this, I show you 2 screenshots: http://www.europephoto.com/info/screenshot_scrolling_1.png http://www.europephoto.com/info/screenshot_scrolling_2.png The first screenshot is my project, with a picture to scroll whose size is 720 x 3000 pixels. I can't access the handle. The second picture is a screenshot of Joe's example. On his project, one can edit the handle with the CTRL key, since the image is smaller. I assume there's a bug somewhere, don't you think? Nicolas, Paris. ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCVS] Crash upon loading file
Hi, I've tried for quite some time to run cinelerra, without success. As soon as I try to load a file, it crashes with this message: Cinelerra 2.0 Sat Aug 27 21:05:30 PDT 2005 (C)2005 Heroine Virtual Ltd. Cinelerra is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. There is absolutely no warranty for Cinelerra. Timestamp 00:00:00.02 Timestamp 00:00:00.02 Timestamp 00:00:00.02 signal_entry: got SIGSEGV my pid=18081 execution table size=33: mwindowedit.C: paste_edls: 1345 mwindowedit.C: paste_edls: 1352 mwindowedit.C: paste_edls: 1361 mwindowedit.C: paste_edls: 1371 file.C: file.C: 313 mwindowedit.C: paste_edls: 1384 mwindowedit.C: paste_edls: 1422 track.C: insert_track: 372 track.C: insert_track: 387 track.C: insert_track: 372 track.C: insert_track: 387 track.C: insert_track: 372 track.C: insert_track: 387 mwindowedit.C: paste_edls: 1502 mwindowedit.C: paste_edls: 1505 mwindowedit.C: paste_edls: 1509 mwindowedit.C: paste_edls: 1513 mwindowedit.C: paste_edls: 1517 mwindow.C: load_filenames: 1048 MWindow::load_filenames 91MWindow::load_filenames 100 MWindow::update_project 3 timebar.C: update: 401 timebar.C: update: 403 timebar.C: update: 406 timebar.C: update: 408 timebar.C: update: 410 timebar.C: update: 412 TrackCanvas::draw 1 TrackCanvas::draw 10 TrackCanvas::draw 20 TrackCanvas::draw 30 file.C: file.C: 313 signal_entry: lock table size=37 0x89518d8 PlaybackEngine::start_lock PlaybackEngine::create_objects * 0x8951650 CWindowTool::input_lock CWindowTool::run 0x8971ea0 TransportQue::output_lock PlaybackEngine::run * 0x89d9eb0 PlaybackEngine::start_lock PlaybackEngine::create_objects * 0x89fa198 TransportQue::output_lock PlaybackEngine::run * 0x8a1b080 MainIndexes::input_lock MainIndexes::run 1 * 0x8a9e048 BC_Repeater::startup_lock BC_Repeater::initialize * 0x848ac78 BC_Repeater::startup_lock BC_Repeater::initialize * 0x85766f0 BC_Repeater::startup_lock BC_Repeater::initialize * 0x8483940 BC_Repeater::startup_lock BC_Repeater::initialize * 0x852d2f0 BC_Repeater::startup_lock BC_Repeater::initialize * 0x842ec40 BC_Repeater::startup_lock BC_Repeater::initialize * 0x84831d8 BC_Repeater::startup_lock BC_Repeater::initialize * 0x8a9dff0 BC_Repeater::pause_lock BC_Repeater::stop_repeating * 0x8a9dff0 BC_Repeater::pause_lock BC_Repeater::run 0x898bd90 BC_WindowBase::event_condition BC_WindowBase::get_event * 0x88030a0 BC_WindowBase::event_condition BC_WindowBase::get_event * 0x88e5778 BC_WindowBase::event_condition BC_WindowBase::get_event * 0x89774d8 BC_WindowBase::event_condition BC_WindowBase::get_event * 0x898bd90 BC_WindowBase::event_condition BC_WindowBase::get_event * 0x88030a0 BC_WindowBase::event_condition BC_WindowBase::get_event * 0x88e5778 BC_WindowBase::event_condition BC_WindowBase::get_event * 0x8a9f558 BC_WindowBase::event_condition BC_WindowBase::get_event * 0x88e5778 BC_WindowBase::event_condition BC_WindowBase::get_event 0x89774d8 BC_WindowBase::event_condition BC_WindowBase::get_event 0x898bd90 BC_WindowBase::event_condition BC_WindowBase::get_event 0x88030a0 BC_WindowBase::event_condition BC_WindowBase::get_event 0x8a9f558 BC_WindowBase::event_condition BC_WindowBase::get_event 0x8a1cde0 BC_WindowBase::event_condition BC_WindowBase::get_event * 0x8a1cde0 BC_WindowBase::event_condition BC_WindowBase::get_event * 0x8a1cde0 BC_WindowBase::event_condition BC_WindowBase::get_event 0x8971ea0 TransportQue::output_lock PlaybackEngine::run 0x89fa198 TransportQue::output_lock PlaybackEngine::run 0x8a1ba60 Cinelerra MWindow::paste_edls * 0x8a1b0f8 MainIndexes::interrupt_lock MainIndexes::run 2 * 0x8a1ba60 Cinelerra MainIndexes::run 1 0x8ada230 CICacheItem::item_lock CICache::check_out * BC_Signals::dump_buffers: buffer table size=0 BC_Signals::delete_temps: deleting 0 temp files SigHandler::signal_handler total files=0 My system is a P4, 512 mb ram running Gentoo linux. uname -a Linux lien 2.6.15-gentoo-r1 #16 SMP PREEMPT Sun Apr 23 10:05:06 CEST 2006 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz GNU/Linux At first, I installed cinelerra-cvs from portage, a snapshot from 2006-02-19. The build completed painlessly on the first try, but crashed according to the message above. Next, I removed cinelerra and fetched the latest version via svn. After some time I managed to build it (ran into the rev-799-thingie, solved it with "svn merge -r 798:797 title.C"), but it still crashes when I try to load a file. What I try to open is a movie clip grabbed from a DV camera using dvgrab --format qt. Any suggestions on what I can do to begin useing cinelerra? Thanks, Lukas Garberg ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Bezier curve alternative?
On Sat, May 27, 2006 at 12:16:17AM +0200, Nicolas MAUFRAIS wrote: > On Fri, May 26, 2006 at 10:42:57PM +0200, Nicolas MAUFRAIS wrote: > > On Thu, May 25, 2006 at 11:04:06AM +0200, Andraz Tori wrote: > > > if you press cntrl while tweeking x/y/z camera/projector on the > > > timeline, you can control slope... at least in theory. > > > > > > bye > > > andraz > > > > Thanks Andraz, > > > > I'll try that CTRL key! Thanks for the information! =) > > > > Nicolas. > > Well, I did try the CTRL key while tweeking the Y camera position, but > I still get a bezier curve. I read the manual, but damn, that part is > too complicated and not explained very clearly. An easy way to set the > curve style would really be nice. > M... I go back to that manual. I hope I'll find the way to do what I > want to do... :-/ > > Nicolas. I did try again, and that still does not work. I also tried the translate plugin, but it can't translate my 720 x 3000 pixels picture. I think I'll have to use Imagemagick and Mjpegtools to convert my picture into an mpeg2video which I will import in Cinelerra. That's a bit frustrating to do not be able to simply correctly scroll an end credit in a video editor. =/ Thanks, Nicolas. ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Bezier curve alternative?
On Fri, May 26, 2006 at 10:42:57PM +0200, Nicolas MAUFRAIS wrote: > On Thu, May 25, 2006 at 11:04:06AM +0200, Andraz Tori wrote: > > if you press cntrl while tweeking x/y/z camera/projector on the > > timeline, you can control slope... at least in theory. > > > > bye > > andraz > > Thanks Andraz, > > I'll try that CTRL key! Thanks for the information! =) > > Nicolas. Well, I did try the CTRL key while tweeking the Y camera position, but I still get a bezier curve. I read the manual, but damn, that part is too complicated and not explained very clearly. An easy way to set the curve style would really be nice. M... I go back to that manual. I hope I'll find the way to do what I want to do... :-/ Nicolas. ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Bezier curve alternative?
On Thu, May 25, 2006 at 11:04:06AM +0200, Andraz Tori wrote: > if you press cntrl while tweeking x/y/z camera/projector on the > timeline, you can control slope... at least in theory. > > bye > andraz Thanks Andraz, I'll try that CTRL key! Thanks for the information! =) Nicolas. -- Conti O -- Kawasaki-Nikon-Linux --- ._ /\_> --- Powered --- (x)> (x) ~~~ ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCVS] [Bug 264] svn build 799 won't compile
http://bugs.cinelerra.org/show_bug.cgi?id=264 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2006-05-26 22:20 --- Thanks, but it turned out that there're FREETYPE_MAJOR and FREETYPE_MINOR with the information that I needed. Sorry for the noise. --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Re: Bezier curve alternative?
On Friday 26 May 2006 15:24, Johannes Sixt wrote: > On Friday 26 May 2006 01:12, Ichthyostega wrote: > > There seems to be another Problem: If I am informed right, > > Cinelerra uses this bezier-courve feature for all Plugin Autos as > > well. Is this correct?? > > As far as I can tell, this is not correct. Plugins usually > interpolate the parameters linearly. Only the autos that are > represented as lines in the timeline interpolate with bezier curves. If this is the case, then Nicolas should probably just use the Translate plugin with keyframes to get the desired scrolling effect for his titles. Still, I also like the idea of having linear beziers available for camera/projector automation, so you could mix and match different types of motion for a particular still image. -Joe ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Bezier automation
On Friday 26 May 2006 18:17, Ichthyostega wrote: > Hi all, > > just another question to the cinelerra source code gurus -- > what is the "standard procedure" if you want to extend some object with > a new property? I can figure out how to save and re-read property values > from the session XML. But what is your policy to handle old XML? > Is there a version numbering of session file formats somewhere? > Is there a "migration component" somehwere or is it the responsibility > of every single component to handle missing values or migrate old values? First of all, you should ensure that the extension is a proper superset of the old functionality, so that no functionality gets lost. Then I'd only ensure forward compatibility and care about backward compatibility only if it is easy to achieve. (If someone disagrees, please speak up!) Then when you read in an XML file, just make sure you check for old properties and values and translate them to the new settings. Each component is itself responsible to handle the migration; there is no general "migration component". There is a version number somewhere, but at the moment I don't see much of a use for it. Currently it is identical to the program's version number, I think. -- Hannes ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Re: Bezier curve alternative?
On Friday 26 May 2006 01:12, Ichthyostega wrote: > There seems to be another Problem: If I am informed right, Cinelerra uses > this bezier-courve feature for all Plugin Autos as well. Is this correct?? As far as I can tell, this is not correct. Plugins usually interpolate the parameters linearly. Only the autos that are represented as lines in the timeline interpolate with bezier curves. -- Hannes ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] how to do splitscreens in cine?
On Fri, 26 May 2006 16:42:02 +0200, Joe Stewart <[EMAIL PROTECTED]> wrote: On Friday 26 May 2006 10:15, Jan Luo wrote: okay, i understand now how to use the translate plugin. but how do i succeed - i know this is somehow basic ;-) - in putting several resized frames/tracks into on frame/ track? You won't get them to appear as one track unless you render the project to a file(s) and append the output of the render job in a new track. ...which is hardly what he wants to do. The videos should stay at their respective tracks, it is how they are mixed in the compositor window that matters. Try changing the "overlay mode". You have to expand the UI to the left of the track to see the overlay mode selector. Click the arrow button to do that. The overlay modes work like the layer modes in the Gimp. -- Herman Robak ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Bezier automation
Hi all, just another question to the cinelerra source code gurus -- what is the "standard procedure" if you want to extend some object with a new property? I can figure out how to save and re-read property values from the session XML. But what is your policy to handle old XML? Is there a version numbering of session file formats somewhere? Is there a "migration component" somehwere or is it the responsibility of every single component to handle missing values or migrate old values? I just don't want to do nasty things to cinelerra's decent sourecode :-) Hermann ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Bezier automation
Pierre Marc Dumuid wrote:
> We'll probably also need to include backward compatible loading of previous
> files. (i.e. increase
> the version no in the xml file, and if xml version is less < AND
> CONTROL_{IN,OUT}_VALUE != 0)
> then they should be modified to get exactly the same behaviour... (or
> alternatively, a message
> should pop-up saying the types of incompatibilities that may exists between
> different versions of
> xml files -- less elegant, but probably easier since cinelerra seems to be a
> moving target..
>
> Pierre
>
Yesterday night, I did more "code exploring" and got a somewhat clearer picture.
I thik now, most of this problem could be a "GUI and editing" problem, so old
session files should work the same way as before.
Even if we add a new state field to every keyframe (my proposal for this was
the three states "smooth", "linear", and "free") we need to asure only that
every old keyframe without this state value gets the value "free". Then it
should work as before.
I looked up the use of the fields control_{in,out}_{value,positon} in the
source. As far as I could see, every keyframe gets this values (initially
set to zero). They are preserved in the respective XML properties and correspond
to the posititon of the control point handles you can drag off with ctrl-mouse
and edit for every keyframe node.
But for the real calculation of the bezier courve, the x-coordinates of the
control points (the *_position-field) are simply thrown away and not used.
Only the information of the y-coordinates is used.
After working a bit with the automation courves, I got the impression this
bezier feature "feels strange" in some way, if you are experienced with bezier
courves (photoshop, corel draw, inkscape...). This would explain why: the
control points you see in the GUI arn't the control points used for the
calculation.
It /is/ a real bezier courve, but in fact the movement of the control points is
restricted to y-direction, as the x-coordinates are fixed to certain values.
I draw this conclusion from the properties of the bezier function
V(t) = (1-t)^3 * V0 + 3*(1-t)^2*t * V1 + 3*(1-t)*t^2 * V2 + t^3 * V3
The V-s are vectors, V0 and V3 are the end points, V1 and V2 the two control
points.
This functon yields a simple linear progression with t along a linear segment
if we set:
V(t)= ((1-t)^3 * 1 + 3*(1-t)^2*t * 1 + 3*(1-t)*t^2 * 1 + t^3 * 1 ) * V0
+ ( 0 + 3*(1-t)^2*t *1/3 + 3*(1-t)*t^2 *2/3 + t^3 * 1 ) * (V3-V0)
= 1 * V0
+ t*(1-t +t)^2 * (V3-V0)(by using the binomial theorem)
My Argument is: if we don't calculate the x-component of the function V(t),
we effectively set it to this linear function Vx(t) = V0x + t*(V3x-V0x)
I think, according to the WYSIWYG philosophy we should modify the gui and
constrain
the control points, so they reflect this behaviour visually!
After considering this, I think, the modifications needed are not difficult,
form a conceptual point of view. The practical problem is: if we want to
implement
some rule to set the control points automatically in some way (for allways smoth
courve or for always linear segments), we have to take into account the
neibouring
keyframes. The current code /elegantly/ gets around this problem by initially
setting V1y=V2y=0
OK, next I will be looking more in the details how this could be done. As a
sidenote,
we all have the same problem: we are rather busy with other things... :-)
Cheers,
Hermann
___
Cinelerra mailing list
Cinelerra@skolelinux.no
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] how to do splitscreens in cine?
On Friday 26 May 2006 10:15, Jan Luo wrote: > okay, i understand now how to use the translate plugin. > but how do i succeed - i know this is somehow basic ;-) - in putting > several resized frames/tracks into on > frame/ track? You won't get them to appear as one track unless you render the project to a file(s) and append the output of the render job in a new track. -Joe ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] how to do splitscreens in cine?
okay, i understand now how to use the translate plugin. but how do i succeed - i know this is somehow basic ;-) - in putting several resized frames/tracks into on frame/ track? thanks again! jan Joe Stewart wrote: On Thursday 25 May 2006 10:29, Graham Evans wrote: Use camera automation (pan x pan y and zoom z) to pick up the screen segment you want from your footage tracks and use projector automation (pan x pan y and zoom z again) to place those parts onto the render screen. You can project multiple tracks onto different parts of the render. If you don't need to do any kind of cropping of the scenes you are split-screening/etc you can use the Translate plugin to move/resize each track to where you want it in the output frame. It's a little more straightfoward than using camera/projector automation - you can specify position/scale of each track by x:y w:h instead of having to tweak the position by hand or play with the bezier curves. -Joe ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
