Re: [CinCVS] Single (Powerful CPU with Hyperthreading) vs. SMP vs. Multiple Cinelerra Render Nodes
Kevin Brosius wrote: Have you tried cinelerra on this system? Your comments seem odd, as on my dual systems, cinelerra will use both cpus (or cpu pipelines on HT machines) during rendering. For actual rendering you're likely to see a performance hit if you let the renderer use both "cpus" of a hyper-threaded system. Best to check the force-single-processor flag in the settings and use the second execution unit for non-number-crunching operations (Surely your underlying OS has something else it'd like to do)! -Brendan ([EMAIL PROTECTED]) ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Single (Powerful CPU with Hyperthreading) vs. SMP vs. Multiple Cinelerra Render Nodes
Hmmm, we have very simmilar machine here (2x opteron 270 @ 2.0ghz), and I must admit that cinelerra takes advantage of that quite good, we are using automated splash titles generator, where user can type text within browser and scripts will glue xml together and send it to rendering , it usually contain a few effects, but one Athlon XP 1800+ used to have 1 minute 30 secs rendering time for classic template. Nowadays, with 4 CPUs, common time is around 20 seconds. I look forward to see openMosix for 2.6 kernel come out this year, it might be a pretty good for cinelerra. As you have mentioned Adobe Premiere,from my point of view it may use multiple cpu's , but the program doesn't have smart logic, so even that won't help (try applying a blur efect to an image which last a few minutes for example ... it will calculate frame by frame ;) - I gave up rendering after waiting an hour and receiving 40 hours expected rendering time - it was no big deal for fx and it had to be done yesterday already )(Yes, it used all 4 CPUs ... I've tried same video later on 2 CPU system and it should complete in 100 hours) If have to be less brief, yes , it's sad nowadays, as a new generation of codecs is out and HD resolutions are getting trendy, there are no traditional computers ready for this, not that even 4 or 8 CPU can be good enough, at least that x264 can handle threads well. greetings from Petr Vacek http://avc.sh.cvut.cz Dimitrios wrote: On Sun, 11 Jun 2006 01:19:08 -0400 Computer Lists <[EMAIL PROTECTED]> wrote: I have one P4 with HT, so I was wondering if Cinelerra would gain any extra benefit from that. I was also wondering if I get a new box(es) should I just put my money into an AMD64 Dual Opteron box with dual core CPUs? Or should I get a bunch of less expensive Athlon 64s as render nodes? Is there any "best" approach" for fast rendering? I own a Dual Dual Core Opteron system (4 logical cpu's), i'm using Opteron 270 cpus. Based on my experience, although this system is a beast you'll never find software that can take advantage of its abilities. Current applications don't really use the 64bit architecture in their coding and most of them don't render on multiple threads to take advantage of the SMP capability. Its a waste really. I've been told that Adobe Premier is the only application that can split rendering in multiple cpus, but i haven't tried it. ___ 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-06-12 03:47 --- (gdb) thread apply all bt Thread 37 (Thread -1542906960 (LWP 9107)): #0 0x082af086 in VModule::VModule () #1 0x082b1969 in VPluginArray::create_modules () #2 0x08244694 in PluginArray::start_plugins () #3 0x081ee183 in MenuEffectThread::run () #4 0xb7aaf17f in Thread::entrypoint () from /usr/lib/libguicast.so.1 #5 0xb73bc380 in start_thread () from /lib/tls/libpthread.so.0 #6 0xb7332c6e in clone () from /lib/tls/libc.so.6 Thread 36 (Thread -1542906960 (LWP 9107)): #0 0x082af086 in VModule::VModule () #1 0x082b1969 in VPluginArray::create_modules () #2 0x08244694 in PluginArray::start_plugins () #3 0x081ee183 in MenuEffectThread::run () #4 0xb7aaf17f in Thread::entrypoint () from /usr/lib/libguicast.so.1 #5 0xb73bc380 in start_thread () from /lib/tls/libpthread.so.0 #6 0xb7332c6e in clone () from /lib/tls/libc.so.6 Thread 34 (Thread -157646 (LWP 9104)): #0 0xe410 in __kernel_vsyscall () #1 0xb732c221 in select () from /lib/tls/libc.so.6 #2 0xb797f82c in _XWaitForReadable () from /usr/lib/libX11.so.6 ---Type to continue, or q to quit--- #3 0xb797fc6d in _XRead () from /usr/lib/libX11.so.6 #4 0xb7981bc4 in _XReadEvents () from /usr/lib/libX11.so.6 #5 0xb796fd38 in XNextEvent () from /usr/lib/libX11.so.6 #6 0xb7aa2e93 in BC_WindowEvents::run () from /usr/lib/libguicast.so.1 #7 0xb7aaf17f in Thread::entrypoint () from /usr/lib/libguicast.so.1 #8 0xb73bc380 in start_thread () from /lib/tls/libpthread.so.0 #9 0xb7332c6e in clone () from /lib/tls/libc.so.6 Thread 33 (Thread -1568085072 (LWP 9103)): #0 0xe410 in __kernel_vsyscall () #1 0xb732c221 in select () from /lib/tls/libc.so.6 #2 0xb797f82c in _XWaitForReadable () from /usr/lib/libX11.so.6 #3 0xb797fc6d in _XRead () from /usr/lib/libX11.so.6 #4 0xb7981bc4 in _XReadEvents () from /usr/lib/libX11.so.6 #5 0xb796fd38 in XNextEvent () from /usr/lib/libX11.so.6 #6 0xb7aa2e93 in BC_WindowEvents::run () from /usr/lib/libguicast.so.1 #7 0xb7aaf17f in Thread::entrypoint () from /usr/lib/libguicast.so.1 #8 0xb73bc380 in start_thread () from /lib/tls/libpthread.so.0 #9 0xb7332c6e in clone () from /lib/tls/libc.so.6 Thread 32 (Thread -1526121552 (LWP 9098)): #0 0xe410 in __kernel_vsyscall () #1 0xb732c221 in select () from /lib/tls/libc.so.6 ---Type to continue, or q to quit--- #2 0xb7a92578 in Timer::delay () from /usr/lib/libguicast.so.1 #3 0xb7a84853 in BC_Repeater::run () from /usr/lib/libguicast.so.1 #4 0xb7aaf17f in Thread::entrypoint () from /usr/lib/libguicast.so.1 #5 0xb73bc380 in start_thread () from /lib/tls/libpthread.so.0 #6 0xb7332c6e in clone () from /lib/tls/libc.so.6 Thread 31 (Thread -1534514256 (LWP 9099)): #0 0xe410 in __kernel_vsyscall () #1 0xb732c221 in select () from /lib/tls/libc.so.6 #2 0xb797f82c in _XWaitForReadable () from /usr/lib/libX11.so.6 #3 0xb797fc6d in _XRead () from /usr/lib/libX11.so.6 #4 0xb7981bc4 in _XReadEvents () from /usr/lib/libX11.so.6 #5 0xb796fd38 in XNextEvent () from /usr/lib/libX11.so.6 #6 0xb7aa2e93 in BC_WindowEvents::run () from /usr/lib/libguicast.so.1 #7 0xb7aaf17f in Thread::entrypoint () from /usr/lib/libguicast.so.1 #8 0xb73bc380 in start_thread () from /lib/tls/libpthread.so.0 #9 0xb7332c6e in clone () from /lib/tls/libc.so.6 Thread 30 (Thread -1551299664 (LWP 9101)): #0 0xe410 in __kernel_vsyscall () #1 0xb732c221 in select () from /lib/tls/libc.so.6 #2 0xb797f82c in _XWaitForReadable () from /usr/lib/libX11.so.6 #3 0xb797fc6d in _XRead () from /usr/lib/libX11.so.6 ---Type to continue, or q to quit--- #4 0xb7981bc4 in _XReadEvents () from /usr/lib/libX11.so.6 #5 0xb796fd38 in XNextEvent () from /usr/lib/libX11.so.6 #6 0xb7aa2e93 in BC_WindowEvents::run () from /usr/lib/libguicast.so.1 #7 0xb7aaf17f in Thread::entrypoint () from /usr/lib/libguicast.so.1 #8 0xb73bc380 in start_thread () from /lib/tls/libpthread.so.0 #9 0xb7332c6e in clone () from /lib/tls/libc.so.6 Thread 29 (Thread -1559692368 (LWP 9102)): #0 0xe410 in __kernel_vsyscall () #1 0xb732c221 in select () from /lib/tls/libc.so.6 #2 0xb797f82c in _XWaitForReadable () from /usr/lib/libX11.so.6 #3 0xb797fc6d in _XRead () from /usr/lib/libX11.so.6 #4 0xb7981bc4 in _XReadEvents () from /usr/lib/libX11.so.6 #5 0xb796fd38 in XNextEvent () from /usr/lib/libX11.so.6 #6 0xb7aa2e93 in BC_WindowEvents::run () from /usr/lib/libguicast.so.1 #7 0xb7aaf17f in Thread::entrypoint () from /usr/lib/libguicast.so.1 #8 0xb73bc380 in start_thread () from /lib/tls/libpthread.so.0 #9 0xb7332c6e in clone () from /lib/tls/libc.so.6 Thread 28 (Thread -1542906960 (LWP 9107)): #0 0x082af086 in VModule::VModule () #1 0x082b1969 in VPluginArray::create_modules () #2 0x08244694 in PluginArray::start_plugins () ---Type to continue, or q to quit--- #3 0x081ee183 in MenuEffectThread::run () #4 0xb7aaf17f in Thread::entrypoint () from /usr/lib
[CinCVS] [Bug 274] New: Ubuntu (Dapper) packages not Found
http://bugs.cinelerra.org/show_bug.cgi?id=274 Summary: Ubuntu (Dapper) packages not Found Product: Cinelerra Version: 2.0 Platform: PC OS/Version: Linux Status: NEW Severity: critical Priority: Critical Component: Building AssignedTo: cinelerra@skolelinux.no ReportedBy: [EMAIL PROTECTED] I do not obtain to install cinelerra in ubuntu dapper. When I will have the repositorios for this version ? --- 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] Single (Powerful CPU with Hyperthreading) vs. SMP vs. Multiple Cinelerra Render Nodes
Dimitrios wrote: > On Sun, 11 Jun 2006 01:19:08 -0400 Computer Lists <[EMAIL PROTECTED]> wrote: > > > I have one P4 with HT, so I was wondering if Cinelerra would gain any > > extra benefit from that. I was also wondering if I get a new box(es) > > should I just put my money into an AMD64 Dual Opteron box with dual core > > CPUs? Or should I get a bunch of less expensive Athlon 64s as render > > nodes? Is there any "best" approach" for fast rendering? > > I own a Dual Dual Core Opteron system (4 logical cpu's), i'm using Opteron > 270 cpus. > > Based on my experience, although this system is a beast you'll never find > software that > can take advantage of its abilities. Current applications don't really use > the 64bit > architecture in their coding and most of them don't render on multiple > threads to take > advantage of the SMP capability. Its a waste really. Have you tried cinelerra on this system? Your comments seem odd, as on my dual systems, cinelerra will use both cpus (or cpu pipelines on HT machines) during rendering. I haven't done testing to determine what kind of speedup this provides though. -- Kevin ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Single (Powerful CPU with Hyperthreading) vs. SMP vs. Multiple Cinelerra Render Nodes
On Sun, 11 Jun 2006 01:19:08 -0400 Computer Lists <[EMAIL PROTECTED]> wrote: > I have one P4 with HT, so I was wondering if Cinelerra would gain any > extra benefit from that. I was also wondering if I get a new box(es) > should I just put my money into an AMD64 Dual Opteron box with dual core > CPUs? Or should I get a bunch of less expensive Athlon 64s as render > nodes? Is there any "best" approach" for fast rendering? I own a Dual Dual Core Opteron system (4 logical cpu's), i'm using Opteron 270 cpus. Based on my experience, although this system is a beast you'll never find software that can take advantage of its abilities. Current applications don't really use the 64bit architecture in their coding and most of them don't render on multiple threads to take advantage of the SMP capability. Its a waste really. I've been told that Adobe Premier is the only application that can split rendering in multiple cpus, but i haven't tried it. ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCVS] [Bug 273] New: I can't use spanish special characters with Title video effect
http://bugs.cinelerra.org/show_bug.cgi?id=273 Summary: I can't use spanish special characters with Title video effect 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] I get improper characters instead of "รก", for example. I have configured ISO8859-1 coding, so it should work. I use Cinelerra in Debian, with CVS packages. Thank you. --- 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 272] New: I can't render mpeg video
http://bugs.cinelerra.org/show_bug.cgi?id=272 Summary: I can't render mpeg video Product: Cinelerra Version: 2.0 Platform: PC OS/Version: Linux Status: NEW Severity: critical Priority: High Component: Rendering AssignedTo: cinelerra@skolelinux.no ReportedBy: [EMAIL PROTECTED] When I select "Video MPEG" with options: Color model: YUV 4:2:2 Derivative: MPEG-2 Bitrate: Any Quantization: 4 I Frame Distance: 45 It seem render works but I can't find resulting file: It doesn't exist! Where is the problem. Cinelerra supports so little formats without problem, but "Video MPEG" always had worked. Help! --- 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] Any recommended x86_64 distribution for using cinelerra?
I run SuSE. SuSE 10.0 comes with Cinelerra 2.0 (Heroine Virtual edition). I haven't had time to install 10.1 yet, but the installed version is still pretty OK. -- Geoff Kuenning [EMAIL PROTECTED] http://www.cs.hmc.edu/~geoff/ Windows XP is the "most reliable Windows ever," which is like saying that asparagus is "the most articulate vegetable ever." -- Dave Barry ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
