If at any point a render/animate command is used on a sequence (video) to output to ffmpeg, Blender dies and loses all work in current state. Reproducible: Always Steps to Reproduce: 1.Add video clip to Blender sequence 2.Select do sequence in animation tab 3.Select ffmpeg format for rendering 4.Click ANIM Actual Results: Blender dies... with messages... Starting output to /tmp/0001_0250.dvd(ffmpeg)... Using type=1, codec=2, audio_codec=86016, video_bitrate=6000, audio_bitrate=128, gop_size=18, multiplex=1, autosplit=0 render width=720, render height=480 [dvd @ 0x3494fc0]Aspect ratio mismatch between encoder and muxer layer Output #0, dvd, to '/tmp/0001_0250.dvd': Stream #0.0: Video: mpeg2video, yuv420p, 720x480 [PAR 1:1 DAR 3:2], q=2-31, 6000 kb/s, 90k tbn, 30 tbc Stream #0.1: Audio: mp2, 44100 Hz, stereo, s16, 128 kb/s Writing frame 1, render width=720, render height=480 [mpeg2video @ 0x34961f0]rc buffer underflow Video Frame PTS: 0 Floating point exception Expected Results: Should render or at least attempt to render to ffmpeg file. CFLAGS="-march=athlon64 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CXXFLAGS="${CFLAGS}" MAKEOPTS="-j3" ACCEPT_KEYWORDS="" INPUT_DEVICES="keyboard mouse evdev" VIDEO_CARDS="nvidia" ALSA_CARDS="usb-audio" USE="-gnome 3dfx 3dnow X a52 aac aim alsa amd64 apache2 arts avi cairo cddb cdparanoia cdr cdrom clamav crypt css cups dbus dri dvd dvdr dvdread emacs encode ffmpeg firefox flac foomaticdb fortran f77 gcj gd gif gimp gimpprint gtk gpm hal hdf5 icq java jpeg kde mad mmx mp3 mp4 mpeg mplayer msn mysql multilib mysql ncurses nptl nsplugin nvidia ogg opengl pam pda pdf perl png python qt3 qt4 quicktime readline samba sdl spell ssl sqlite svg threads tiff truetype win32codecs xine xscreensaver xml xv"
Thought this might be relevant. Seems that the blender binary which is pre-compiled and available from blender.org will render correctly. Some snooping leads me to believe that this is an ffmpeg backend issue. The binary which works has a static ffmpeg library built in. Is it possible to build ours this way? Or does this raise an eyebrow from someone who is more familiar with these products? I'm willing to do testing to help get this sorted but know very little with regards to how these particular libraries are built/used.
Please try again with blender-2.63a and reopen if it's still an issue. Thanks, Diego
