I got it working - wma9.so was failing to load mainly due to
my build
system not being up to date.
However that was on cayenne_1_5_0. I'm now trying a HEAD
build (as we
want rtsp:// support) and am getting some build errors. I'll
send
another email on that one.
John
Eric Hyche wrote:
>
>
>>-----Original Message-----
>>From: helix-client-dev-bounces helixcommunity.org
>>[mailto:helix-client-dev-bounceshelixcommunity.org] On
>>Behalf Of John Stirling
>>Sent: Tuesday, March 27, 2007 5:48 AM
>>To: helix-client-devlists.helixcommunity.org
>>Subject: Re: [Helix-client-dev] helix wma support
>>
>>I tried the folliwing build :
>>cayene_1_5_0 restricted
>>splay_wm
>>linux-i586
>>
>>and it built with no errors and produced the
following:
>>
>>MD5
(release/asfff.so)................3eab9a83a37f324b9e3d681253
b22b8f
>>MD5
(release/clntcore.so).............d20e13ac15c81a2b5a97e99b40
29361b
>>MD5
(release/log.so)..................c5a973611ff0ccef919c9929c5
d4aafb
>>MD5
(release/logobserverfile.so)......001e8db58a28381c5f896462a5
fe1006
>>MD5
(release/ramfformat.so)...........5ceb629a26ee85062ac6b1c5fd
fa52a0
>>MD5
(release/ramrender.so)............05bcde49acc71cc4a20a640cc4
055ced
>>MD5
(release/wma9.so).................03bc500e57262163ba3fd4a178
2022fd
>>MD5
(release/wmarender.so)............00d1c44ad043dd48dfd07fb030
b8c536
>>MD5
(release/wmv9.so).................29f1874f7ef8ff479e5923109a
bc86ac
>>MD5
(release/wmvrender.so)............5eaddc4fe7c719280785af0bd8
5534e0
>>
>>
>>
>
>Is that all of them? I would expect smplfsys.so
>and httpfsys.so to be there. Were there any build
>errors? Also, I may have not kept the
"splay_wm" target
>up to date in hxclient_1_5_0_cayenne_restricted.bif.
>Check to make sure that the "splay_wm" target
in
>helix_restricted.bif is the same as the one
>in hxclient_1_5_0_cayenne_restricted.bif.
>
>
>
>>I can't get it to play any WMA content though :
>>
>>./splay file:///home/js/music/wma/pulp.wma
>>Simpleplayer is looking for the client core at
./clntcore.so
>>Common DLL path DT_Common=.
>>Plugin path DT_Plugins=.
>>Codec path DT_Codecs=.
>>opening file:///home/js/music/wma/pulp.wma on player
0
>>Report(3, -2147221487, "(NULL)", 0,
"(NULL)", "HXR_NO_RENDERER")
>>
>>Do I need any other plugins to make this work ? I
notice that
>>https://helix-client.helixcommunity.org/20
05/devdocs/windowsMedia.html
>>mentions an asx fileformat plugin which I can't see
a target
>>for. Is the documentation just out of date or is
this the problem ?
>>
>>
>>
>
>If pulp.wma is indeed a WMA file and not an ASX file
(which
>I would assume), then you should not need the ASX file
format
>and renderer.
>
>
>
>>I also tried a clean splay_mp3 build, which produced
the following:
>>clntcore.so hxsdp.so hxxml.so mp3fformat.so
mp3render.so
>>ramfformat.so ramrender.so smplfsys.so
>>However it wouldn't play any MP3 content until I
dumped ramfformat.so
>>and ramrender.so into the directory. Why are these
plugins needed to
>>play mp3 content ?
>>
>>
>>
>
>The client core always first tries content to see if it
is
>a .ram file before trying anything else. I think this
was
>added a LONG time ago when the mime types on lots of
>web servers were misconfigured.
>
>Eric
>
>=============================================
>Eric Hyche (ehychereal.com)
>Technical Lead
>RealNetworks, Inc.
>
>
>
>>John
>>
>>
>>
>>John Stirling wrote:
>>
>>
>>
>>>Is WMA playback available on cayenne_1_5_0
(file:// and rtsp://) ?
>>>
>>>What targets do I need to build ?
>>>
>>>John
>>>
>>>_______________________________________________
>>>Helix-client-dev mailing list
>>>Helix-client-devhelixcommunity.org
>>>http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev
>>>
>>>
>>
>>_______________________________________________
>>Helix-client-dev mailing list
>>Helix-client-devhelixcommunity.org
>>http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev
>>
>>
>>
>
>
>
_______________________________________________
Helix-client-dev mailing list
Helix-client-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev
|
