Sunday, February 15, 2009

I'm still unsure about how to play videos in Haiku/Senryu.

I received a couple of suggested reasons for the failure of either MediaPlayer or VLC-0.8.6d to play videos in either Haiku (r29155) or Senryu (r29143).
The first was that the problem was with my .avi file. However, the same file plays perfectly in VLC-0.8.6e in Ubuntu on the same machine. Also, I tried another .avi file which gave exactly the same result.
The second (comment to this blog) was that there's a bug somewhere. This ties in with this ticket which is entitled "(Haiku) Intel Video Driver Does Not Work With 945G". My Asus EeePC 901 has the 945G card.
Another possibility that I stumbled upon myself is that the BeOS version of VLC-0.8.6 has a bug. See here for a fix for this bug.
However, the terminal outputs, in both Haiku and Senryu, using either MediaPlayer or VLC-0.8.6d, suggest that codecs are the problem.
With Media player, for both OSes, the terminal outputs the following relevant lines:

PluginManager::CreateDecoder: can't get decoder for format: Bad media format
MediaExtractor::CreateDecoder _plugin_manager.CreateDecoder failed for stream 0, format: cvideo;0;2.28158e+06;3.04211e+06;0;(15.0001;0x0;1;320;240;0;TopLR;1;1)
Controller::SetTo: 1 audio track, 1 video track
AudioAdapter() - using format converter
AudioAdapter() - using resampler
AudioAdapter() - using channel converter
MediaTrackVideoSupplier::_SwitchFormat() - fVideoTrack->DecodedFormat(): Initialization failed - retrying with B_RGB32
MediaTrackVideoSupplier::_SwitchFormat() - fVideoTrack->DecodedFormat(): Initialization failed - giving up

With VLC-0.8.6d, both OSes output these relevant lines in the terminal:
Compiler did not align stack variables. Libavcodec has been miscompiled
and may be very slow or crash. This is not a bug in libavcodec,
but in the compiler. Do not report crashes to FFmpeg developers.

I posted to the Haiku forums, from which I have received a lot of very thorough help in the past, about this problem but have yet (5 hours) to receive a reply.
Let's wait and see.

No comments:

Post a Comment