Now that I at least have it working it isn't as fast as I thought. In VLC my test video is smooth, but in pyglet / libAVbin0 it is noticeably choppy (but still plays without issue). I will re-visit in the morning. Thanks!
Blaine On Wed, Nov 28, 2012 at 9:16 PM, Blaine <[email protected]> wrote: > holy crap holy crap. i got it to work. turns out i did not successfully > install pyglet 1.2alpha1. > > > - With pyglet 1.2alpha1 and livAVbin11 - segmentation fault when > playing several example videos (mpeg2 specifically) > - With pyglet 1.2alpha1 and libAVbin10 - mpeg2 video plays (fast!) > with audio!! > > THIS IS GREAT NEWS ;). I would love to help debug libavbin11 to see why it > is seg faulting, but for now i'm happy as a clam. > Blaine > > > > On Wed, Nov 28, 2012 at 9:02 PM, Blaine <[email protected]> wrote: > >> To be clear: >> >> When I use the latest libAVBin 10 or 11 (both binary and built on the >> machine), pyglet (both latest from HEAD and 1.1.4) is unable to play any >> videos both in my app and with examples/video.py >> >> It simply says that there is no video track available (or no picture >> source available in the video file). >> >> The micro-itx board i'm using is x86-32bit, and i can play videos on it >> with VLC without a hitch. libAVbin7 (debian stock) kind of works - it shows >> the first frame and plays audio, but then crashes (locks up) at the end of >> the audio. >> >> I can try libAVBin8 next, but I think my best bet is with the latest >> builds. I'm hoping to get more debug information but I'm not sure where to >> look. >> >> Blaine >> >> >> >> On Wed, Nov 28, 2012 at 5:31 PM, Blaine Booher <[email protected]> wrote: >> >>> Nathan, >>> >>> So both libAVBin 10 and 11 (latest from git), after installed, do not >>> show picture information (for the video). When I run a video, I get "h264 >>> no picture" (twice) debug output. Same thing with wmv, avi, mpeg2... not >>> crashing but not displaying any video. Simply says picture information is >>> not present in the video source. >>> >>> Where can I go from here? >>> >>> On Wednesday, November 28, 2012 12:19:54 AM UTC-5, Nathan wrote: >>>> >>>> On Mon, Nov 26, 2012 at 3:51 PM, Blaine <[email protected]> wrote: >>>> >>>>> Hi guys, >>>>> >>>>> I'm successfully using pyglet to display a video on my laptop, but >>>>> when I transfer the project to a small intel atom micro-itx board I run >>>>> into issues. Can I get some help in figuring out how to diagnose this? >>>>> >>>>> 1. I had to jump through hoops to get video drivers to work, but >>>>> they do work now (recompile kernel, extract binary drivers, downgrade >>>>> x11server, use old debian snapshot apt source, etc.). I am able to >>>>> play the >>>>> video in VLC on the intel atom board with no issues and I get >>>>> accelerated >>>>> performance compared to before I installed intel's cedarview drivers >>>>> (so I >>>>> at least know the video works) >>>>> 2. When I load it with pyglet into my app, I get the first frame >>>>> and all the audio but the video does not play. Pyglet also locks up >>>>> and I >>>>> have to hard kill the python thread. When I turn >>>>> pyglet.options['media_debug'] to True, I do get one more warning on the >>>>> intel board: "<pyglet.media.drivers.alsa.**AlsaAudioPlayer object >>>>> at 0xxx> underrun: reducing update period to 0.11" >>>>> 3. I'm actually using cocos2d on top of pyglet, but for video I'm >>>>> playing it directly with pyglet.media >>>>> 4. I've recompiled ffmpeg so that I use the version 1.0 AND h264 >>>>> support (which is identical in laptop and on the intel board) because >>>>> it >>>>> appeared to help with an audio lag issue I was having on my laptop. >>>>> Pyglet >>>>> is the same version on both (1.1.4). I am using libavbin0 version 7.1-3 >>>>> (installed from debian apt archives, unsure if actually using my >>>>> compiled >>>>> ffmpeg libraries) >>>>> >>>>> >>>> To answer the implied question at the end of #4: No, AVbin will not >>>> use external FFmpeg/Libav libraries. AVbin includes its own version of >>>> FFmpeg/Libav internally. >>>> >>>> AVbin 7 is very old (released either 2007 or 2008, if I remember >>>> correctly). Pyglet 1.1.4 is from around the same time period. One good >>>> thing to try is upgrading to the latest (development) version of pyglet >>>> 1.2. Another good thing to try is upgrading to AVbin 10 (or try the 11 >>>> prerelease). >>>> >>>> Give that a try and see if the problem persists. >>>> >>>> ~ Nathan >>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "pyglet-users" group. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msg/pyglet-users/-/WrRJpr8FiE4J. >>> >>> 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. >>> >> >> > -- 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.
