http://bugs.cinelerra.org/show_bug.cgi?id=229

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From [EMAIL PROTECTED]  2006-03-04 10:24 -------
Okay I have been working on this MPEGII video render bug and it is no longer "a
problem with mpeg2enc".  I have got the mpeg2enc render working now with the
MPEGII-Generic preset (which didn't work before) as well as the DVD preset
(which was my workaround until now).

I'm not sure what happened.  I did discover the need to run autogen again before
configuring and compiling a new version of cinelerra.  Is that always
neccessary?  I also found some dodgy files in my /usr/local/bin which might have
been blocking more up-to-date versions.  Mainly ffmpeg files - no obvious
culprits.  There were possibly a lot of wrong default settings in the video
render settings dialog - but for now I'm not going to delete my .bcast to see
what they were. 

On the other hand:
I still can't get a yuv4mpeg pipe going at all to render my PAL-DV footage (dv
format 2 from dvgrab).

Not with  "cat > /dev/null" as the pipe command (suggested in the course of this
bug as a test)
Nor with any basic mpeg2enc or ffmpeg pipes as discussed in recent times on the
cinCVS list and in the Beginners Guide to Exporting Video from Cinelerra
http://content.serveftp.net/video/renderTest/guideToCinExport.html

It makes no difference between using the Quicktime or the avi container type.

I can do ffmpeg renders using the yuv4mpeg pipe when the footage is mpeg4,
mpeg2, and even from blank DV clips generated by Cinelerra.

I have tried compiling the latest ffmpeg.  I'm not sure I got that completely
right but it didn't help or change things.  I have now reverted to the livna 
rpms of ffmpeg x86_64 (built Dec 2005).  When I first posted this bug I was
working with the freshrpms version of ffmpeg.

I have a feeling the problem is not with ffmpeg but with the data being piped to
it by Cinelerra.  But that is an uneducated feeling and may be wrong.

I would appreciate any ideas or, instead, confirmation this is a legitimate bug.
 Please email me if you wish me to post files for download.

Anyway this bug is closed because the header says it's about mpeg2enc and that
one is behaving for now.

Graham Evans



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Cinelerra mailing list
[email protected]
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra

Reply via email to