Dmitry, (and anyone else on 64-bit Linux) can you try the new
Libav-based linux-x86-64 version I just put together?

The FFmpeg people haven't been any help, and I found that there's an
active fork of FFmpeg called Libav.

https://github.com/downloads/AVbin/AVbin/avbin-linux-x86-64-v8-libavfork.tar.bz2

~ Nathan

On Sat, Nov 26, 2011 at 6:30 PM, Nathan <[email protected]> wrote:
> I've got an updated version of ffmpeg merged in, but so far
> linux-x86-64 is giving me fits.  I've figured out everything except
> the final linking error:
>
> ld -shared -soname libavbin.so.8 -o dist/linux-x86-64/libavbin.so.8
> build/avbin.o -whole-archive ffmpeg/libavformat/libavformat.a
> ffmpeg/libavcodec/libavcodec.a ffmpeg/libavutil/libavutil.a
> ffmpeg/libavcore/libavcore.a ffmpeg/libswscale/libswscale.a
> -no-whole-archive -R /usr/local/lib -R .
> ld: dist/linux-x86-64/libavbin.so.8: version node not found for symbol
> av_dup_packet@LIBAVFORMAT_52
> ld: failed to set dynamic section sizes: Bad value
> make: *** [dist/linux-x86-64/libavbin.so.8] Error 1
>
> I'm asking about it on one of the FFmpeg mailing lists.  I can't
> figure out this weird "version node" stuff.
>
> ~ Nathan
>
> On Thu, Nov 17, 2011 at 6:37 PM, Dmitry Chichkov <[email protected]> wrote:
>>
>> I should have been more specific. Your libavbin version had fixed
>> http://wpcvn.com/tmp/2816522621.mp4
>> But on the h.264 videos (for example http://wpcvn.com/tmp/h.264.mp4 ) now it
>> returns empty frames and None in timestamps.
>> On ubuntu 11.04/x.64/pyglet from dev trunk/your libavbin).
>>
>> wget http://wpcvn.com/tmp/h.264.mp4
>>
>>>>> import pyglet.media
>> source = pyglet.media.load("h.264.mp4")
>> print source
>> print source.get_next_video_timestamp(), source.get_next_video_frame()
>> print source.get_next_video_timestamp(), source.get_next_video_frame()
>> print source.get_next_video_timestamp(), source.get_next_video_frame()
>> print source.get_next_video_timestamp(), source.get_next_video_frame()
>> print source.get_next_video_timestamp(), source.get_next_video_frame()
>>
>> Results in:
>> <pyglet.media.avbin.AVbinSource object at 0xdc0750>
>> 0.0 None
>> None <ImageData 640x512>
>> 0.04 <ImageData 640x512>
>> 0.08 <ImageData 640x512>
>> 0.12 <ImageData 640x512>
>>
>> With the standard ubuntu libavbin&piglet these h.264 files were working
>> fine:
>> <pyglet.media.avbin.AVbinSource object at 0x7f9c249a0a10>
>> 0.0 <ImageData 640x512>
>> 0.04 <ImageData 640x512>
>> 0.08 <ImageData 640x512>
>> 0.12 <ImageData 640x512>
>> 0.16 <ImageData 640x512>
>>
>>
>>
>> Intrestingly, with standard libavbin in Ubuntu 11.04 and NEW pyglet from the
>> github I'm also getting somewhat strange results:
>>
>> [aac @ 0xfed510]Transition from an ONLY_LONG or LONG_STOP to an EIGHT_SHORT
>> sequence detected. If you heard an audible artifact, please submit the
>> sample to the FFmpeg developers.
>> <pyglet.media.avbin.AVbinSource object at 0xff8750>
>>     Last message repeated 3 times
>> [h264 @ 0x113c750]Missing reference picture
>> [h264 @ 0x113c750]decode_slice_header error
>> [h264 @ 0x113c750]concealing 1280 DC, 1280 AC, 1280 MV errors
>> None None
>> [h264 @ 0x113c750]Missing reference picture
>> [swscaler @ 0x7f00502abc60]No accelerated colorspace conversion found from
>> yuv420p to rgb24.
>> 0.04 <ImageData 640x512>
>> [h264 @ 0x113c750]Missing reference picture
>> [swscaler @ 0x7f005040daa0]No accelerated colorspace conversion found from
>> yuv420p to rgb24.
>> 0.08 <ImageData 640x512>
>> [h264 @ 0x113c750]Missing reference picture
>> [swscaler @ 0x7f0050411ea0]No accelerated colorspace conversion found from
>> yuv420p to rgb24.
>> 0.12 <ImageData 640x512>
>> [swscaler @ 0x7f005042e470]No accelerated colorspace conversion found from
>> yuv420p to rgb24.
>> 0.16 <ImageData 640x512>
>>
>> -- Dmitry

-- 
You received this message because you are subscribed to the Google Groups 
"pyglet-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/pyglet-users?hl=en.

Reply via email to