[coherence-dev] Fwd: Having issues getting coherence working...
Phil Wild
philwild at gmail.com
Fri Jul 18 06:09:40 CEST 2008
I also looked at the source and noticed the reverse proxy code. I am
not a programmer, will write the occasional shell script but that is
about it...
I thought I may have been on track to finding a soln... I have been
digging through the coherence debug log but do not see anything that
seems to indicate a problem...
As the pioneer is a closed device, I can't determine where things go
wrong on that end so I can't exclude it from the equation. The only
thing I have to go on is the track not found message.
Could you point me to a linux or windows dlna client that I could use
to test the client side and perhaps give me some good logging to help
figure out where it is failing?
Cheers
Phil
2008/7/18 Cecil Coupe <ccoupe at cableone.net>:
> I don't have ampache but my recollection from browsing the source is the
> plugin is a proxy/tunnel to your (local?) ampache server. I stopped my
> reading when it appeared to me that I'd have to install and configure
> ampache locally and get an account somewhere and (re)upload music to it
> (either local or remote). That was way more work than I wanted to go
> through. It's a small plugin though and quite readable for the clues you
> seek.
>
> Congrats on getting Coherence working.
>
>
> On Fri, 2008-07-18 at 10:32 +0800, Phil Wild wrote:
>> Another question...
>>
>> Can someone explain to me how the plugin works. Does it act like a
>> proxy and tunnel the music stream to the device or does it just
>> provide a directory listing of the data in ampache and expect the
>> receiver to contact ampache direct via the URL to play the music. The
>> reason I ask is that I have configured coherence to point to the
>> ampache setup on the same host and so the configuration is setup up as
>> http://localhost/ampache...."
>>
>> If it simply tells my receiver to go to that address, it will not find
>> the track. Am I supposed to set up coherence to talk to the actual ip
>> address (i.e. http://10.3.0.3/ampache/....)
>>
>> I am at work at the moment and can not test.... I am guessing the
>> first option...
>>
>> Cheers
>>
>> Phil
>>
>> 2008/7/18 Phil Wild <philwild at gmail.com>:
>> > I have updated the Ampache page in the coherence wiki to include the
>> > instructions about multicast
>> > (http://coherence.beebits.net/wiki/Ampache).
>> >
>> > I am now a lot closer... I had not picked up that I needed the
>> > multicast route and with this in place, coherence appears on my
>> > receiver displaying a named entry for each plugin in my config file.
>> >
>> > I can browse and play music through the mediastore plugin so all good
>> > here. This shows that coherence can talk to my receiver and stream
>> > music to it. However...
>> > I can browse the ampache plugin, but when attempting to play music, I
>> > get a track not found message.
>> > Any idea what I might have missed?
>> >
>> > The ACL's in place in ampache are:
>> > local 127.0.0.1 127.0.0.1 Read/Write Ampache
>> > User (System) ampache RPC
>> > localstream 127.0.0.1 127.0.0.1 Read/Write Ampache User
>> > (System) Stream Access
>> > localweb 127.0.0.1 127.0.0.1 Read/Write Ampache User
>> > (System) Web Interface
>> >
>> > My config file curently looks like this:
>> >
>> > logmode = debug # none, critical, error, warning, info, debug
>> > logfile = coherence.log
>> > interface = eth1
>> > serverport = 30020
>> > controlpoint = no
>> > web-ui = no
>> > use_dbus = no
>> >
>> > # <plugin active="yes">
>> > # <backend>AmpacheStore</backend>
>> > # <name>CDCollection</name>
>> > # <url>http://localhost/ampache/server/xml.server.php</url>
>> > # <key>ampache</key>
>> > # </plugin>
>> > #
>> > [plugins]
>> > [[AmpacheStore]]
>> > name = CDCollection
>> > url = http://localhost/ampache/server/xml.server.php
>> > key = ampache
>> > [[MediaStore]]
>> > medialocation = /data/media
>> > name = Coherence MediaStore
>> >
>> >
>> >
>> > 2008/7/18 Cecil Coupe <ccoupe at cableone.net>:
>> >>
>> >> Somewhere on the wiki, there is a mention of a route add command
>> >> (building from source page?)
>> >>
>> >> Things do get confusing because mediatomb may use its own config for
>> >> it's coherence (or maybe it shares the ~/.coherence, I can't say). It's
>> >> hard to know which coherence server is being selected from the receiver
>> >> and as you have discovered the receiver keeps track of the servers it's
>> >> found.
>> >>
>> >> --Cecil
>> >>
>> >> On Fri, 2008-07-18 at 01:04 +0800, Phil Wild wrote:
>> >> > Hi again,
>> >> >
>> >> > looking through the startup script for mediatomb I see that it sets up
>> >> > a multicast route. I was wondering if this is why my pioneer receiver
>> >> > only sees coherence when mediatomb is running. Is this required for
>> >> > correct operation of meiatomb? I did not see any mention of it in the
>> >> > installation notes?
>> >> >
>> >> > Cheers
>> >> >
>> >> > Phil
>> >> >
>> >> > 2008/7/18 Phil Wild <philwild at gmail.com>:
>> >> > Still struggling here...
>> >> >
>> >> > I have gotten further though...
>> >> >
>> >> > I can not get coherence to talk to my pioneer by itself...
>> >> >
>> >> > It never appears. However, if I start up mediatomb, mediatomb
>> >> > appears on the tv and there is a lot of chatter in the
>> >> > coherence logs. If I then power cycle the pioneer, I see both
>> >> > mediatomb and coherence twice for the two plugins defined in
>> >> > my config file. The medistore plugin works... The ampache
>> >> > plugin does not. I can navigate to a song, but when I start to
>> >> > play it it says track not found...
>> >> >
>> >> > Log is attached....
>> >> >
>> >> > Any help would be greatly appreciated....
>> >> >
>> >> > Cheers
>> >> >
>> >> > Phil
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Tel: 0400 466 952
>> >> > Fax: 0433 123 226
>> >> > email: philwild AT gmail.com
>> >> > _______________________________________________
>> >> > coherence-dev mailing list
>> >> > coherence-dev at lists.beebits.net
>> >> > http://lists.beebits.net/cgi-bin/mailman/listinfo/coherence-dev
>> >>
>> >
>> >
>> >
>> > --
>> > Tel: 0400 466 952
>> > Fax: 0433 123 226
>> > email: philwild AT gmail.com
>> >
>>
>>
>>
>
>
--
Tel: 0400 466 952
Fax: 0433 123 226
email: philwild AT gmail.com
More information about the coherence-dev
mailing list