Re: [CinCVS] Suggested GUI improvement; some notes from today's IRC meeting.
Salut Herman, > Now, if I suggest starting a total rewrite from guicast to Gtk+, I > expect to get shot down. However, we could consider making some of > the dialogs in Gtk, to get started. Or Qt, or WxWidget... Sylvain. ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCVS] Klocwork results
Cinelerra people- I now have a bit of time in the coming week (and motiviation to create a new video since my 3rd child was just born). (The joys of paternity leave) My plan is to try and use the latest merge source (will be working on gentoo). Start making a simple video and whenever I hit a crash, try to figure out what caused it. I'll compile with debug options and run valgrind as well when necessary. If anyone has hints or suggestions that might be handy feel free to share them. Otherwise I'll be popsting my comments/questions here. Hopefully the klockwork results will still be somewhat relevant to the latest source. If others are interesting in the klocwork results, please let me know. I don't think that klocwork would mind me sharing their results as long as you credit them for any fix done using their analysis. I've got a speadsheet export that is probably easier to use than their web interface. -matt ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCVS] [Bug 253] cinelerra exits when reframe video effect is used
http://bugs.cinelerra.org/show_bug.cgi?id=253 --- Additional Comments From [EMAIL PROTECTED] 2006-09-14 04:48 --- cinelerra_2.0.0-3svn20060606_i386.deb runs fine but the newest ... Cinelerra 2.1CV Wed Sep 13 exits when Reframe or ReframeRT is applied as Render effect .. but not if ReframeRT is Attached and then Render . --- 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
[CinCVS] [Bug 253] cinelerra exits when reframe video effect is used
http://bugs.cinelerra.org/show_bug.cgi?id=253 --- Additional Comments From [EMAIL PROTECTED] 2006-09-14 04:43 --- Created an attachment (id=169) --> (http://bugs.cinelerra.org/attachment.cgi?id=169&action=view) strace log ... same bug here. Cinelerra 2.1CV Wed Sep 13 20:00:35 CEST 2006 (C)2006 Heroine Virtual Ltd. signal_entry: got SIGSEGV my pid=3728 execution table size=16: mwindowedit.C: paste_edls: 1576 mwindowedit.C: paste_edls: 1580 mwindowedit.C: paste_edls: 1591 mwindowedit.C: paste_edls: 1594 mwindow.C: load_filenames: 1133 mwindow.C: load_filenames: 1138 mwindow.C: load_filenames: 1141 mwindow.C: load_filenames: 1143 mwindow.C: load_filenames: 1146 mwindow.C: load_filenames: 1150 mwindow.C: load_filenames: 1152 vrender.C: run: 414 vrender.C: process_buffer: 103 vrender.C: process_buffer: 113 vrender.C: run: 416 vrender.C: run: 555 signal_entry: lock table size=13 0x8573f58 BC_Synchronous::next_command BC_Synchronous::run 0x93b58c8 TransportQue::output_lock PlaybackEngine::run 0x93b5ed8 MainIndexes::input_lock MainIndexes::run 1 0x9425638 ResourceThread::draw_lock ResourceThread::run 0x93035b0 TransportQue::output_lock PlaybackEngine::run 0x944fe88 BC_Repeater::pause_lock BC_Repeater::run 0x93b7cc0 BC_WindowBase::event_condition BC_WindowBase::get_event 0x932b098 BC_WindowBase::event_condition BC_WindowBase::get_event 0x8dfbd60 BC_WindowBase::event_condition BC_WindowBase::get_event 0x9235f80 BC_WindowBase::event_condition BC_WindowBase::get_event 0x9304e70 BC_WindowBase::event_condition BC_WindowBase::get_event 0x9451460 BC_WindowBase::event_condition BC_WindowBase::get_event 0x92af350 BC_WindowBase::event_condition BC_WindowBase::get_event BC_Signals::dump_buffers: buffer table size=0 BC_Signals::delete_temps: deleting 0 temp files SigHandler::signal_handler total files=1 --- 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
[CinCVS] Render timing?
I notice that the render time display that used to appear in the status bar is no longer visible here. It seems that because of the auto indexing that occurs if you use 'load resources only' at render time, the status bar will update the index, replacing the render time display... One way around this is to use 'insert nothing'. This also prevents the lockup mentioned in my prior mail, confirming my suspicion about the possible cause. -- Kevin ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCVS] Cin 2.1 lockup on re-load
Can anyone else repeat this Cin 2.1 lockup I am seeing? Launch cin from an xterm Load a source file (using a few minutes of dv here) edit ~1min of video into the timeline save your project render the timeline to qt/linux (audio twos, video dv) exit cin (confirm yes to save project) restart cin use the quick reload items to reload your project the main cin window is hung, with the hourglass. Pressing ctrl-c in the xterm to kill cin. I suspect it is a problem with trying to find the rendered clip, which usually appears in the clips resource window. Once that is rendered, and you save the project, Cin seems to get confused trying to reload it. -- Kevin ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] compile error in bcsynchronous.C / ATI OpenGL2.0 implementation incomplete
Hannes, You beat me to the punch, as I've been in meetings all day and have not had time to close out this issue. So thanks for clarifying the resolution. All you ATI folks, I'm sorry to say that you probably are in for a rude surprise with ATIs' "OpenGL2.0" Linux driver implementation. After 1 1/2 days of finally getting my ATI All in Wonder 9800 Pro to actually use OpenGL and see it working well (5000FPS on glxgears), it was very disheartening to see that ATI had not provided the proper 2.0 hooks for Cinelerra to use. In light of this situation, today I went to B&H Photo and bought an Nvidia 7800GS AGP, 512MB. Twenty minutes after getting home, the card was in the box, drivers were compiled, installed and working. Fifteen minutes after that, Cinelerra was compiled and I was using OpenGL2.0! Yeehoo!! And at twice the playback speed of what I was getting previously with the ATI card. I will report back on the performance of this card once I actually USE it. :) For those who might find the troubleshooting conversation interesting, the IRC chat log from yesterday is here: http://cvs.cinelerra.org/irclog/index.php?file=2006-09-13.html I learned quite a bit, not being an active C programmer. By the way, that log is a font of information for folks who'd like to know more about anything Cinelerra related. I learned quite a bit just by perusing the last few days of entries. However, I find it hard to get up at 3:30am EDT to join in! ;) Also, I'm considering pulling out and categorizing some relevant tips from the past few months like this one from HermanR: "You can get cool twinkle effects with animate blurs. Those are hard to check out without test rendering..The most noticeable twinkles are when the x blur and y blur vary independently, or in opposite direction. That creates a wobbling deformation. Combine it with the wave plugin, and you could get a fairly convincing water reflection simulation." In my beginner's head, that's pure gold. Thanks again to Hannes for all the help, scott On Wed, 2006-09-13 at 22:12 +0200, Johannes Sixt wrote: > On Tuesday 12 September 2006 22:05, Johannes Sixt wrote: > > On Tuesday 12 September 2006 01:30, [EMAIL PROTECTED] wrote: > > > Guys, > > > With the --enable-opengl switch on, I get this compile error: > > > > > > bcsynchronous.C: In member function 'void > > > BC_Synchronous::delete_window_sync(BC_SynchronousCommand*)': > > > bcsynchronous.C:408: error: 'glDeleteShader' was not declared in this > > > scope > > > > Join in on IRC at #cinelerra to debug this. I (j6t) will be there in 11 > > hours from now. > > The conclusion after our chat was that the ati-fglrx package for FC4 > advertises OpenGL 2.0 in glxinfo, but in fact lacks the necessary entry > points in its libGL.so.1.2. > > -- Hannes > > ___ > 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
[CinCVS] [Bug 304] compile error: glDeleteShader was not declared in this scope
http://bugs.cinelerra.org/show_bug.cgi?id=304 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2006-09-13 22:17 --- It turned out that there is a problem with the fglrx driver (package ati-fglrx): It advertises OpenGL 2.0, but does not provide the required entrypoints in its libGL.so.1. Furthermore, the x11-xorg-6.8.* package seems to be old enough not to provide OpenGL 2.0 headers; therefore, the build fails early. --- 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] compile error in bcsynchronous.C: 'glDeleteShader' was not declared in this scope
On Tuesday 12 September 2006 22:05, Johannes Sixt wrote: > On Tuesday 12 September 2006 01:30, [EMAIL PROTECTED] wrote: > > Guys, > > With the --enable-opengl switch on, I get this compile error: > > > > bcsynchronous.C: In member function 'void > > BC_Synchronous::delete_window_sync(BC_SynchronousCommand*)': > > bcsynchronous.C:408: error: 'glDeleteShader' was not declared in this > > scope > > Join in on IRC at #cinelerra to debug this. I (j6t) will be there in 11 > hours from now. The conclusion after our chat was that the ati-fglrx package for FC4 advertises OpenGL 2.0 in glxinfo, but in fact lacks the necessary entry points in its libGL.so.1.2. -- Hannes ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Rumours about a GTK port of Cinelerra; is it for real?
On Wed, Sep 13, 2006 at 09:27:52PM +0200, Herman Robak wrote: > The IRC channel had a visitor today who was positive he had > seen a Gtk port of Cinelerra. He also said it had a different > name and that it was hard to find. > > I would like to verify or falsify this. If there is indeed > a feature-complete fork of Cinelerra with a Gtk UI, I would > really want to hear about it. > > -- > Herman Robak Herman, Perhaps that visitor was talking about the GTK theme? http://fr.lprod.org/wiki/doku.php?id=video:cinelerra:pluginlprod Nicolas, Paris. ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCVS] cinelerra 2.1 debian packages
debian packages of 2.1 have been uploaded to the http://www.kiberpipa.org/~minmax/cinelerra repository they are not linked to the opengl... please report problems/submit fixes :) bye andraz ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Suggested GUI improvement; some notes from today's IRC meeting.
On Wed, 13 Sep 2006 20:56:57 +0200, Nicolas <[EMAIL PROTECTED]> wrote: On Wed, Sep 13, 2006 at 07:03:08PM +0200, Herman Robak wrote: Some suggestions on how to singnalise status in more ways: Darkening unarmed tracks (rejected, better ideas?) Graying "don't play" tracks (inconclusive. maybe darkening?) Changing the mouse pointer over unarmed tracks Having the View menu turned into a panel Cinelerra needs a status bar. (displaying what info?) IMO, the first action to do is to redesign the arm icon. When I switched from the Blond theme to the SUV theme, I immediately noticed it's more difficult to quickly see which tracks are armed and which ones are not. That's because when the icon is selected, it becomes orange. But the icon, when not selected, is red. If the "not selected" arm icon was white on grey, highlighting it in red would make it far more visible. Using colour only to indicate on/off state is bad usability, and a big no, no in UI design. Colour blind users will be at a total loss! We should either have a thorough discussion on how to make a widget look like "on" or "off", or adopt the way popular widget toolkits do it. One of the big problems with Cinelerra's user interface is the lack of familiarity. If Cinelerra used one of the major UI toolkits, most of the widgets would look familiar, and users would recognise the on/off states they had seen in other programs. Now, if I suggest starting a total rewrite from guicast to Gtk+, I expect to get shot down. However, we could consider making some of the dialogs in Gtk, to get started. Final note: Does "arm" really ring a bell? Would not "unlock" make more sense as a label? -- Herman Robak ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCVS] Rumours about a GTK port of Cinelerra; is it for real?
The IRC channel had a visitor today who was positive he had seen a Gtk port of Cinelerra. He also said it had a different name and that it was hard to find. I would like to verify or falsify this. If there is indeed a feature-complete fork of Cinelerra with a Gtk UI, I would really want to hear about it. -- Herman Robak ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Suggested GUI improvement; some notes from today's IRC meeting.
Hello, On Wed, Sep 13, 2006 at 07:03:08PM +0200, Herman Robak wrote: > This afternoon (European time) Johannes Sixt (j6t), > Gustavo Iñigues (ga), Pierre Marc Dumuid (pmdumuid) and > I (hermanr) had an IRC meeting discussing Cinelerra's > user interface. > > > DV grabbing and export leaves a lot to be desired. > We needed more research to know where to start... > > -- > > Timeline UI: better indication of arming, and play on/off. > > Some suggestions on how to singnalise status in more ways: > > Darkening unarmed tracks (rejected, better ideas?) > Graying "don't play" tracks (inconclusive. maybe darkening?) > Changing the mouse pointer over unarmed tracks > Having the View menu turned into a panel > Cinelerra needs a status bar. (displaying what info?) IMO, the first action to do is to redesign the arm icon. When I switched from the Blond theme to the SUV theme, I immediately noticed it's more difficult to quickly see which tracks are armed and which ones are not. That's because when the icon is selected, it becomes orange. But the icon, when not selected, is red. If the "not selected" arm icon was white on grey, highlighting it in red would make it far more visible. > -- > > Klipper and sound daemons keep causing new users grief. > > * Klipper: Cinelerra's clipboard handling is wrong. TODO: Fix it > * Sound daemons: display notification TODO: add a status bar Mmmm, about Cinelerra's clipboard, I find it very frustrating (when editing hundreds of keyframes) to do not be able to paste the keyframe on the insertion point when there's a IN or OUT point defined on the timeline... > -- > > Tracks should be groupable, so that they will be (un)armed > in unison. This will make it easier to keep audio and video > tracks in synch when they are moved around. When media files > are imported, their audio and video tracks should be grouped > by default. > > To keep things simple, only adjacent tracks should be > groupable, with an obvious (un)group widget between tracks > to click on. I really would like that feature! My projects have tens of tracks, and I often have to cut/paste a group of tracks. In fact, generally, the same cut/paste operations are applied on the video and audio tracks... > -- > > Tracks are at least 32 pixels tall, and a video recording contain > 3 tracks, taking up much screen estate. Dealing with many tracks > gets unmanagable on normally sized screens; some more aggressive > collapsing features are needed. > > j6t: > "so we don't need a menu, just an icon between tracks, only neighboring > tracks are linked, and it means that they share the same armed/unarmed > state" > > There are two needs: Hiding and grouping > > Suggestion: if linked tracks are collapsed, one of them becomes the > "master" > (needs more research) > > -- > Herman Robak Nicolas, Paris. ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Suggested GUI improvement; some notes from today's IRC meeting.
On Wed, 2006-09-13 at 19:03 +0200, Herman Robak wrote: >This afternoon (European time) Johannes Sixt (j6t), > Gustavo Iñigues (ga), Pierre Marc Dumuid (pmdumuid) and > I (hermanr) had an IRC meeting discussing Cinelerra's > user interface. > > > DV grabbing and export leaves a lot to be desired. > We needed more research to know where to start... completely remove "record" from main menu... > Timeline UI: better indication of arming, and play on/off. > > Some suggestions on how to singnalise status in more ways: > > Darkening unarmed tracks (rejected, better ideas?) i like this one actually, hard to implement -> changes all over the place. bye andraz ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Pipes question ...
On Wed, 2006-09-13 at 18:30 +0200, Richard Rasker wrote: > Good GUI design is not an easy thing at all - especially if it's > technicians who know the ins and outs doing the designing. What's > totally obvious to them, is often quite mystifying to novice users. And > then you have the hardcore Linux users, who go running to the command > line at the first appearance of the word "pipe" - "Ceci n'est pas une > pipe" - or is it? :-) > > Anyway, I have everything working nicely now, so I'm one happy camper > (or should I say: camp moviemaker) :-) The problem is that is considerably harder to implement this in easy-GUI way, even if this way is known. Cinelerra's guicast library is not what you need for quickly creating simple guis. bye andraz ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCVS] Suggested GUI improvement; some notes from today's IRC meeting.
This afternoon (European time) Johannes Sixt (j6t), Gustavo Iñigues (ga), Pierre Marc Dumuid (pmdumuid) and I (hermanr) had an IRC meeting discussing Cinelerra's user interface. DV grabbing and export leaves a lot to be desired. We needed more research to know where to start... -- Timeline UI: better indication of arming, and play on/off. Some suggestions on how to singnalise status in more ways: Darkening unarmed tracks (rejected, better ideas?) Graying "don't play" tracks (inconclusive. maybe darkening?) Changing the mouse pointer over unarmed tracks Having the View menu turned into a panel Cinelerra needs a status bar. (displaying what info?) -- Klipper and sound daemons keep causing new users grief. * Klipper: Cinelerra's clipboard handling is wrong. TODO: Fix it * Sound daemons: display notification TODO: add a status bar -- Tracks should be groupable, so that they will be (un)armed in unison. This will make it easier to keep audio and video tracks in synch when they are moved around. When media files are imported, their audio and video tracks should be grouped by default. To keep things simple, only adjacent tracks should be groupable, with an obvious (un)group widget between tracks to click on. -- Tracks are at least 32 pixels tall, and a video recording contain 3 tracks, taking up much screen estate. Dealing with many tracks gets unmanagable on normally sized screens; some more aggressive collapsing features are needed. j6t: "so we don't need a menu, just an icon between tracks, only neighboring tracks are linked, and it means that they share the same armed/unarmed state" There are two needs: Hiding and grouping Suggestion: if linked tracks are collapsed, one of them becomes the "master" (needs more research) -- Herman Robak ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Pipes question ...
Op wo, 13-09-2006 te 18:11 +0200, schreef Herman Robak: > On Wed, 13 Sep 2006 15:26:38 +0200, Richard Rasker <[EMAIL PROTECTED]> > wrote: > > > Op wo, 13-09-2006 te 21:32 +0930, schreef Pierre Marc Dumuid: > >> Heh, > >> There are actually "pipe presets" that cinelerra demonstrates how to > >> use it.. > > > > [snip] > > > > Yeah, I just found it ... "Hey, let's see what this little wrench thingy > > does ..." That took me only, what, one day to find? A perfect > > demonstration of overly simple thinking (command line) on my part when > > it's right under your nose in the GUI ... > > I think the wrench is a clear example of the many features of Cinelerra > that are only obvious once you know them. To me, a wrench suggests > "tweak". > Only expert options should be labeled "tweak". It is highly misleading to > suggest that the codec choice is an expert setting and the choice of > container is all you need to know about! I don't mind that aspect too much; it's the fact that I didn't even *identify* the wrench symbol as a control - especially because it sits right next to an unmistakable control (the checkbox), and because there is no colour difference between controls such as these and static dialog elements (e.g. text). Only when I moved the mouse cursor over it by accident, I realized that it was a button ... All the same, I *did* read about it when I started with Cinelerra (without the "Secrets" manual it's virtually impossible to operate the application efficiently) - but it was rather quickly forgotten when trying to get to grips with the countless other, more important features. Good GUI design is not an easy thing at all - especially if it's technicians who know the ins and outs doing the designing. What's totally obvious to them, is often quite mystifying to novice users. And then you have the hardcore Linux users, who go running to the command line at the first appearance of the word "pipe" - "Ceci n'est pas une pipe" - or is it? :-) Anyway, I have everything working nicely now, so I'm one happy camper (or should I say: camp moviemaker) :-) Regards, Richard Rasker ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Pipes question ...
On Wed, Sep 13, 2006 at 11:23:28AM +0200, Richard Rasker wrote: > Hi, > > I'm trying to get better control over the quality of an MPEG result, > found this one (among many similar solutions) in the mailing list > archives: > > "Export as an YUV4MPEG stream and use a pipe to encode the YUV stream : > yuvcorrect -v 0 -T INTERLACED_BOTTOM_FIRST | mpeg2enc -v 0 -r 32 -4 1 > -2 1 -D 10 -g 15 -G 15 -q 5 -b 9400 -f 8 -o $1 > > Export an AC3 sound stream at 224 kbps > > Mplex everything with : > mplex -f 8 -V audio.ac3 video.m2v -o movie.mpeg" > > And there are many more references to piping - quite justified, as it > prevents *huge* temporary files from being created (the YUV4MPEG stream > is about 1GB per minute of video). Otrherwise, one would need at least > 60GB of free HD space at all times for every hour of video rendering. > > > Alas, there's one thing I somehow don't understand: how exactly do I > pipe the output from Cinelerra to the yuvcorrect line? > > I thought I understood pipes (they're equally simple as useful), but I > can't seem to make it work here. I tried the following procedure: > > [CLI]: mkfifo cinepipe > [Cinelerra]: Render to YUV4MPEG Stream - file name: cinepipe > [CLI]: yuvcorrect ... -o video.m2v < cinepipe > > However, Cinelerra says it's busy rendering, but it just sits there and > does nothing; nor does top show any activity in the yuvcorrect/mpeg2enc > department. > I suspect that Cinelerra somehow has trouble with named pipes - if I > replace the last CLI command with cat cinepipe > /dev/null, there's > still no progress in Cinelerra. > > I'm pretty certain that the solution is *really* simple - but I'm afraid > that I'm even simpler - too simple in fact to see it. Google turned up > lots of tips about plumbing, and the usual explanations and examples > about the | symbol, but nothing much useful on using pipes to process > (stream) output from GUI applications. > > > Thanks in advance for any explanation, > > Regards, > > Richard Rasker Hello Richard, I described the steps in the Wiki page : http://ftconsult.taxnetusa.com/twiki/bin/view/Cinelerra/Rendering#RENDERING_OPTIONS_encoding_tips (at the bottom of the page) Nicolas, Paris. ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Pipes question ...
On Wed, 13 Sep 2006 15:26:38 +0200, Richard Rasker <[EMAIL PROTECTED]> wrote: Op wo, 13-09-2006 te 21:32 +0930, schreef Pierre Marc Dumuid: Heh, There are actually "pipe presets" that cinelerra demonstrates how to use it.. [snip] Yeah, I just found it ... "Hey, let's see what this little wrench thingy does ..." That took me only, what, one day to find? A perfect demonstration of overly simple thinking (command line) on my part when it's right under your nose in the GUI ... I think the wrench is a clear example of the many features of Cinelerra that are only obvious once you know them. To me, a wrench suggests "tweak". Only expert options should be labeled "tweak". It is highly misleading to suggest that the codec choice is an expert setting and the choice of container is all you need to know about! -- Herman Robak ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCVS] [Bug 269] libmpeg: mpeg files incorrectly indexed, resulting in audio / video sync and searching problems...
http://bugs.cinelerra.org/show_bug.cgi?id=269 [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2006-09-13 17:04 --- I consider that both patches have been applied in 2.1 by HV, (and integrated as a result of the merge into 2.1CV) I am now closing this bug. Those who had problematic files, please test, and re-open this bug if needed. --- 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
[CinCVS] [Bug 293] Audio noise in raw dv export -- with patch
http://bugs.cinelerra.org/show_bug.cgi?id=293 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2006-09-13 16:59 --- Patch has been applied, and bug considered closed. --- 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] Pipes question ...
FAQ food 2006/9/13, Richard Rasker <[EMAIL PROTECTED]>: Op wo, 13-09-2006 te 21:32 +0930, schreef Pierre Marc Dumuid: > Heh, > There are actually "pipe presets" that cinelerra demonstrates how to > use it.. [snip] Yeah, I just found it ... "Hey, let's see what this little wrench thingy does ..." That took me only, what, one day to find? A perfect demonstration of overly simple thinking (command line) on my part when it's right under your nose in the GUI ... Anyway, thanks for the reply :-) Regards, Richard Rasker ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra -- ^ ^ O O (_ _) muzzol(a)gmail.com jabber id: muzzol(a)jabber.dk No atribueixis qualitats humanes als ordinadors. No els hi agrada. "El gobierno español sólo habla con terroristas, homosexuales y catalanes, a ver cuando se decide a hablar con gente normal" Jiménez Losantos bomb terrorism bush aznar teletubbies
Re: [CinCVS] Raw DV rendering problems?
Op di, 12-09-2006 te 23:30 -0700, schreef Craig Lawson: [snip DV export sound bug] > If you want to patch it yourself, see details here: > http://bugs.cinelerra.org/show_bug.cgi?id=293 > > It's a small patch. OK, fixed it, and everything works great now - thank you very much! Regards, Richard Rasker ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Pipes question ...
Op wo, 13-09-2006 te 21:32 +0930, schreef Pierre Marc Dumuid: > Heh, > There are actually "pipe presets" that cinelerra demonstrates how to > use it.. [snip] Yeah, I just found it ... "Hey, let's see what this little wrench thingy does ..." That took me only, what, one day to find? A perfect demonstration of overly simple thinking (command line) on my part when it's right under your nose in the GUI ... Anyway, thanks for the reply :-) Regards, Richard Rasker ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Pipes question ...
Heh, There are actually "pipe presets" that cinelerra demonstrates how to use it.. Cinelerra actually starts whatever program is specified in the textbox, and pipes the YUV data into that program. Basically, what you place in the textbox next to the "Use Pipe" check box is the actual program that receives the pipe) In regards to the statement, make a bash script that contains: #!/bin/bash yuvcorrect -v 0 -T INTERLACED_BOTTOM_FIRST | mpeg2enc -v 0 -r 32 -4 1 -2 1 -D 10 -g 15 -G 15 -q 5 -b 9400 -f 8 -o $1 calling yencode.sh (possibly needing a chmod +x on it) Then place yencode.sh in the textbox. "Export as an YUV4MPEG stream and use a pipe to encode the YUV stream : yuvcorrect -v 0 -T INTERLACED_BOTTOM_FIRST | mpeg2enc -v 0 -r 32 -4 1 -2 1 -D 10 -g 15 -G 15 -q 5 -b 9400 -f 8 -o $1 Export an AC3 sound stream at 224 kbps Mplex everything with : mplex -f 8 -V audio.ac3 video.m2v -o movie.mpeg" And there are many more references to piping - quite justified, as it prevents *huge* temporary files from being created (the YUV4MPEG stream is about 1GB per minute of video). Otrherwise, one would need at least 60GB of free HD space at all times for every hour of video rendering. Alas, there's one thing I somehow don't understand: how exactly do I pipe the output from Cinelerra to the yuvcorrect line? I thought I understood pipes (they're equally simple as useful), but I can't seem to make it work here. I tried the following procedure: [CLI]: mkfifo cinepipe [Cinelerra]: Render to YUV4MPEG Stream - file name: cinepipe [CLI]: yuvcorrect ... -o video.m2v < cinepipe However, Cinelerra says it's busy rendering, but it just sits there and does nothing; nor does top show any activity in the yuvcorrect/mpeg2enc department. I suspect that Cinelerra somehow has trouble with named pipes - if I replace the last CLI command with cat cinepipe > /dev/null, there's still no progress in Cinelerra. I'm pretty certain that the solution is *really* simple - but I'm afraid that I'm even simpler - too simple in fact to see it. Google turned up lots of tips about plumbing, and the usual explanations and examples about the | symbol, but nothing much useful on using pipes to process (stream) output from GUI applications. Thanks in advance for any explanation, Regards, Richard Rasker ___ 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
[CinCVS] Pipes question ...
Hi, I'm trying to get better control over the quality of an MPEG result, found this one (among many similar solutions) in the mailing list archives: "Export as an YUV4MPEG stream and use a pipe to encode the YUV stream : yuvcorrect -v 0 -T INTERLACED_BOTTOM_FIRST | mpeg2enc -v 0 -r 32 -4 1 -2 1 -D 10 -g 15 -G 15 -q 5 -b 9400 -f 8 -o $1 Export an AC3 sound stream at 224 kbps Mplex everything with : mplex -f 8 -V audio.ac3 video.m2v -o movie.mpeg" And there are many more references to piping - quite justified, as it prevents *huge* temporary files from being created (the YUV4MPEG stream is about 1GB per minute of video). Otrherwise, one would need at least 60GB of free HD space at all times for every hour of video rendering. Alas, there's one thing I somehow don't understand: how exactly do I pipe the output from Cinelerra to the yuvcorrect line? I thought I understood pipes (they're equally simple as useful), but I can't seem to make it work here. I tried the following procedure: [CLI]: mkfifo cinepipe [Cinelerra]: Render to YUV4MPEG Stream - file name: cinepipe [CLI]: yuvcorrect ... -o video.m2v < cinepipe However, Cinelerra says it's busy rendering, but it just sits there and does nothing; nor does top show any activity in the yuvcorrect/mpeg2enc department. I suspect that Cinelerra somehow has trouble with named pipes - if I replace the last CLI command with cat cinepipe > /dev/null, there's still no progress in Cinelerra. I'm pretty certain that the solution is *really* simple - but I'm afraid that I'm even simpler - too simple in fact to see it. Google turned up lots of tips about plumbing, and the usual explanations and examples about the | symbol, but nothing much useful on using pipes to process (stream) output from GUI applications. Thanks in advance for any explanation, Regards, Richard Rasker ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] [Bug 305] utf-8 support
feel free to code it up. sorry andraz. i know you're tired of lot-of-suggestions-but-no-single-line-of-code. im just a user and just know some bash scripting. im pretty sure there's lot of things to work on before utf-8 support. regards, muzzol -- ^ ^ O O (_ _) muzzol(a)gmail.com jabber id: muzzol(a)jabber.dk No atribueixis qualitats humanes als ordinadors. No els hi agrada. "El gobierno español sólo habla con terroristas, homosexuales y catalanes, a ver cuando se decide a hablar con gente normal" Jiménez Losantos bomb terrorism bush aznar teletubbies
Re: [CinCVS] [Bug 305] utf-8 support
On Wed, 2006-09-13 at 11:02 +0200, muzzol wrote: > even if it supports additional locales i think utf-8 support would be > great. all is now in utf-8 so cinelerra should take that direction feel free to code it up. bye andraz > 2006/9/13, [EMAIL PROTECTED] > <[EMAIL PROTECTED]>: > > http://bugs.cinelerra.org/show_bug.cgi?id=305 > > > > > > > > > > > > --- Additional Comments From [EMAIL PROTECTED] 2006-09-13 10:57 --- > > Hi! I know that Croatian is iso8859-2, but here on utf-8 locale it does not > > work, ie. in the dialog (Title --> Show), there are latin-1 chars, while in > > Compositor are latin-2, but it is cumbersome. > > > > Maybe it would be required to change locale to latin-2 which is not very > > convenient. > > > > Which locale you have on your computer? > > > > Sincerely, > > Gour > > > > > > > > --- 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 > > > > > -- > > ^ ^ > O O > (_ _) > muzzol(a)gmail.com > > jabber id: muzzol(a)jabber.dk > > No atribueixis qualitats humanes als ordinadors. > No els hi agrada. > > "El gobierno español sólo habla con terroristas, homosexuales y > catalanes, a ver cuando se decide a hablar con gente normal" > Jiménez Losantos > > > bomb terrorism bush aznar teletubbies > > � <)ޕjf)+- <)ޕj(bgmx)鮉ff(bgbا~܊wz ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] [Bug 305] utf-8 support
even if it supports additional locales i think utf-8 support would be great. all is now in utf-8 so cinelerra should take that direction 2006/9/13, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: http://bugs.cinelerra.org/show_bug.cgi?id=305 --- Additional Comments From [EMAIL PROTECTED] 2006-09-13 10:57 --- Hi! I know that Croatian is iso8859-2, but here on utf-8 locale it does not work, ie. in the dialog (Title --> Show), there are latin-1 chars, while in Compositor are latin-2, but it is cumbersome. Maybe it would be required to change locale to latin-2 which is not very convenient. Which locale you have on your computer? Sincerely, Gour --- 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 -- ^ ^ O O (_ _) muzzol(a)gmail.com jabber id: muzzol(a)jabber.dk No atribueixis qualitats humanes als ordinadors. No els hi agrada. "El gobierno español sólo habla con terroristas, homosexuales y catalanes, a ver cuando se decide a hablar con gente normal" Jiménez Losantos bomb terrorism bush aznar teletubbies
[CinCVS] [Bug 305] utf-8 support
http://bugs.cinelerra.org/show_bug.cgi?id=305 --- Additional Comments From [EMAIL PROTECTED] 2006-09-13 10:57 --- Hi! I know that Croatian is iso8859-2, but here on utf-8 locale it does not work, ie. in the dialog (Title --> Show), there are latin-1 chars, while in Compositor are latin-2, but it is cumbersome. Maybe it would be required to change locale to latin-2 which is not very convenient. Which locale you have on your computer? Sincerely, Gour --- 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
[CinCVS] [Bug 305] utf-8 support
http://bugs.cinelerra.org/show_bug.cgi?id=305 --- Additional Comments From [EMAIL PROTECTED] 2006-09-13 10:25 --- croatian is iso8859-2. it works. --- 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
[CinCVS] [Bug 305] New: utf-8 support
http://bugs.cinelerra.org/show_bug.cgi?id=305 Summary: utf-8 support Product: Cinelerra Version: 2.0 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: Medium Component: Effects/Transitions AssignedTo: cinelerra@skolelinux.no ReportedBy: [EMAIL PROTECTED] Hi! When I was exploring Cinelerra's ability to add titles, I discovered that there is no support for utf-8 (Unicode) encoding in Title's Encoding combo box, there is no support for utf-8 encoding and if I choose eg. latin-2 encoding for entering Croatian chars, all I get are latin-1 characters. Since utf-8 encodong & Unicode are more & more present on today's desktops, here I'm humbly submitting feature request whether it is possible to add utf-8 support to Cinelerra? Sincerely, Gour --- 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] Playback stops, but counter keeps going
this is FAQ food. 2006/9/13, Andraž Tori <[EMAIL PROTECTED]>: On Tue, 2006-09-12 at 14:50 -0700, James Colannino wrote: > Andraž Tori wrote: > > Can you please read/search list archives _before_ posting ? > > > > It has been answered numerous times! > > Perhaps if I knew some keywords that I could search under that > suggestion would be of more help to me. What would you suggest I search > for, specifically? look at the topic "play won't stop" in august, "cinelerra hungs on playing video" in july, "cursor doesn't stop in timeline" in may ... "play stop freeze prob" in march, "preview does not stop on amd64" in december, "playback won't stop with cinelerra 2 on debian" in november, "Playback not stopping" in october ... it is extremely easy to find in google, entering "cinelerra playback stop" would lead you to the answer very fast. bye andraz ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra -- ^ ^ O O (_ _) muzzol(a)gmail.com jabber id: muzzol(a)jabber.dk No atribueixis qualitats humanes als ordinadors. No els hi agrada. "El gobierno español sólo habla con terroristas, homosexuales y catalanes, a ver cuando se decide a hablar con gente normal" Jiménez Losantos bomb terrorism bush aznar teletubbies
