[coherence-dev] Having issues getting coherence working...

[Phil Wild]

Thanks,

I will give this a go tonight (at work at the moment). The Pioneer receiver
does not see the device at all. When mediatomb or windows mediaplayer share
is active, they appear. However both have been turned off to keep things
simple while trying to get this working.

The Pioneer provides a pretty ugly interface, black and white text. With
mediatomb active, I select the mediatomb and then can select album, artist,
genre, year, song etc and hit play. There is however no playlist hence why I
would like to get coherence with ampache working.

The only functions I get on the receiver for this are navigation, stop,
play, pause, skip, next, prev. No shuffle either.

Cheers

Phil




2008/7/16 Cecil Coupe <ccoupe at cableone.net>:

> [Seems I didn't send this to the list. Grump. Phil's going to get it
> twice. My bad.]
>
> Do the easy part first. Make a ~/.coherence. Just to remove that
>  annoyance.  Can your Pioneer see the coherence server at all? Choice of
> backends won't matter if the receiver won't matter if the client can't
> see the server.
>
> I managed to get Coherence talking to a Yamaha RX-N600 which is a pretty
> crippled device. It wasn't pretty. You have two servers that work
> (MediaTomb and WMP) so you've got a good baseline. I installed Wireshark
> on my Ubuntu Linux box and decoded the packets that Coherence and the
> Yamaha sends trying to find each other. Not something for the casual
> user to do. In my case, the XML headers sent back from Coherence had to
> in a particular order, with nothing extra added. Dumb device! Bad
> Device! But it's my device.
>
> Frank has my patches which may or may not get into the next release of
> Coherence and may not help you.  I'll send them to you if your willing
> to poke around in Python source code.You'll have to discover the HTTP
> UPnP-Client the Pioneer sends in HTTP headers. Coherence logging at the
> info level is sufficient.
>
> FWIW here's the  my ~/.coherence file (edited slightly) that I use:
> logmode = info # none, critical, error, warning, info, debug
> logfile = coherence.log
> interface = eth0
> serverport = 30020
> controlpoint = no
> web-ui = no
> use_dbus = no
>
> [plugins]
>    [[MediaStore]]
>        medialocation = /home/mmedia/Music
>        coverlocation = /home/ccoupe/.gnome2/rhythmbox/covers # optional
>        mediadb = /home/ccoupe/yamaha.cdb
>        name = Coherence MediaStore
>
> Disabling the controlpoint, web-ui and dbus really cuts down on the log
> traffic. At this point, the backend choice doesn't matter. You know
> Coherence is talking to it. It'll whine in the log if it can't connect
> to the back end. If it doesn't complain, you're back is good enough for
> now.
>
> --Cecil
>
>
> On Wed, 2008-07-16 at 13:29 +0800, Phil Wild wrote:
>  > My dlna client is a Pioneer VSX-LX70 AV receiver. It can see my
> > windows mediaplayer share on my PC. It also can see mediatomb running
> > on the same linux host that I am trying to get coherence running on. I
> > have shut down mediatomb for all testing purposes so only coherence
> > should be visible.
> >
>
>
>
>
>


-- 
Tel: 0400 466 952
Fax: 0433 123 226
email: philwild AT gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.beebits.net/pipermail/coherence-dev/attachments/20080716/79287d28/attachment.htm>