forked-daapd

[Samuel Cole]

Just wanted to let you know, that I am successfully running forked-
daapd from the experimental feed. The only issue I had was that forked-
daapd was crashing on a font file inside an iTunes LP (tried to run
ffmpeg against it). Everything seems snazzy now!

I'll try more complex things, like adding an iPhone remote, when I get
home later.

I have a couple Macs running iTunes, is there anything else you want
me to try?

[Samuel Cole]

Oh, on a side note: I've been running Automatic through FFP, I'll try
to port over to your package a bit later. Thanks for including it!

[Joao Cardoso]

On Feb 15, 4:28 pm, Samuel Cole <s...@samuelcole.name> wrote:

> I'll try more complex things, like adding an iPhone remote, when I get
> home later.

Excelent. Please post your findings.
There are instructions on how to use Remote (whatever that is) and
other settings in the README that you can find here.

https://github.com/jasonmc/forked-daapd#readme

> I have a couple Macs running iTunes, is there anything else you want
> me to try?

Could you try netatalk/afpd? I have no idea if it works with real
Macs.
And finding what options are needed to enable a share to be used by
the TimeMachine was also very helpful.

Thanks.

[Hamish Campbell]

I've moved over to the experimental feed and installed forked-daap.
Didn't have much time but so far....

Found by Itunes on mac and plays successfully on the laptop from the
shared library (will check ubuntu next).

Could't get remote to pair. Samuel, have you tried this yet? I
haven't tried the debugging options from the readme yet so they will
be the next step
- could be the name of the iphone gives trouble (unicode vs ascii)
- could be msDNS isn't working properly (need to check logs, maybe
enable verbose logging on forked).

Once I get that going I'll try to get playing on the airport express,
seems there's some enabling of ipv6, so we'll see how that goes.

After that I can try out netatalk and time machine.

Cool :)

Haim

[Samuel Cole]

> Could you try netatalk/afpd? I have no idea if it works with real
> Macs.
> And finding what options are needed to enable a share to be used by
> the TimeMachine was also very helpful.

Netatalk works perfectly, pretty impressive that you got it going
blind.

[Hamish Campbell]

Ok, issues so far:

Forked wouldn't start and stop, but then it suddenly would, no idea
what happened to make it work. Oh now it's not working again, nothing
coming out in system log or the forked log either, when I try to stop
it I mean, weird.

Default puts forked log file in /var/log/forked which is not under
Alt-f directory so you can't get to it via the samba share, which is
kinda a hassle, perhaps its worth mapping that, note that the database
file is mapped to /var/lib/daapd which holds song3.db

Had lots of trouble with the iphone remote, until I read on the
authors site that remote 2.0 is not supported yet. No way to
downgrade to ver 1.3.3.3 so will have to wait for forked to support
the new one and for the new forked to make it over to alt-
f.......hmmmm now found http://forum.qnap.com/viewtopic.php?f=177&t=37472
where it's been put on QNAP, it suggests remote v2 is supported, is
the ALT-F an older version of forked?

I've made the logging more verbose and get this:

[2011-02-18 21:13:49] remote: Adding Remote pin data: name 'Gitte',
pin '9788'
[2011-02-18 21:13:49] remote: Remote 'Gitte' found
[2011-02-18 21:13:49] db: Running query 'SELECT * FROM inotify
WHERE wd = 4;'
[2011-02-18 21:13:49] scan: File event: 0x8, cookie 0x0, wd 4
[2011-02-18 21:13:49] remote: Adding Remote pin data: name 'Gitte',
pin '9788'
[2011-02-18 21:13:49] remote: Remote 'Gitte' found

but the remote on the iphone doesn't register that it's been
recognised, so not sure where to go from there, there doesn't seem to
be any support forums for forked.

Without remote I don't think I can get airport express playing as
don't know how to play anything without the remote, hmmm probably
there are some manual commands, but can't find these anywhere. It
says it needs ipv6 enabled, so have set that to yes on avahi conf to
prepare.

Any success from you Samuel?

Haim

[Hamish Campbell]

oh, and I can't make avahi and forked be enabled for boot up, is there
a trick to that?

[Hamish Campbell]

Remote issue:

comment on that qnap

'Regarding the remote problem (menaing using the Apple Remote App for
ipad or iPhone) I found out that this a bug which is related to
version 2.x of the Apple Remote App. Version 1 of that App worked fine
with the forked-daapd 0.12 but version 2 does not because Apple
changed "something". I was informed that Julien has been working on
that and already included a fix in the new source code. This is either
available on the web as sources (and could be compiled as needed) or
will be released with the 0.13 version of forked-daapd. See following
discussion: https://github.com/jasonmc/forked-daapd/issues/issue/23/#issue/23/comment/588851'

Looking at the discussion quoted it says either to build from trunk or
wait for 0.13 (whever that is).

I presume you picked up the stable rather than building from trunk?
Would be a sensible thing to do.

Haim

[Sam Cole]

I never ended up trying Remote, but it sounds like we'll be waiting a bit.

As for the randomly stopping: I found that forked-daap would crash
when it tried to scan certain files. I put logging on 'spam', and then
removed (or I could have moved) the last file it scanned before it
crashed.

As for setting it to start on bootup: I had the same problem on the
web interface, but I was able ssh in and chmod +x the /etc/init.d
file. Is that dangerous? Curious why I could do it on the shell, but
not on the web.

> --
> You received this message because you are subscribed to the Google Groups "Alt-F" group.
> To post to this group, send email to al...@googlegroups.com.
> To unsubscribe from this group, send email to alt-f+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/alt-f?hl=en.
>
>

[Joao Cardoso]

On Friday, February 18, 2011 21:19:48 Hamish Campbell wrote:
> Ok, issues so far:
>
> Forked wouldn't start and stop, but then it suddenly would, no idea
> what happened to make it work. Oh now it's not working again, nothing
> coming out in system log or the forked log either, when I try to stop
> it I mean, weird.

forked-daap needs avahi-daemon who needs dbus.
Make sure they are running, first dbus, then avahi-daemon, then forked-daapd.

On the cmd line:
rcdbus start
rcavahi-daemon start
rcforked-daapd start

to stop them all, proceed in the reverse order.
Notice that dbus is not an end-user service, it does not appear in any of the
web pages.

Also, mt-daapd is incompatibe with forked-daapd, so don't start it.

I'm changing how the initscripts infrastructure works to accomplish this
automatically, but it is not something that can be easily changed.

> Default puts forked log file in /var/log/forked

That is the standard. In B7 you can access all log files from the web
interface.

> which is not under Alt-f directory
> so you can't get to it via the samba share,

Don't do that... read the README.txt in the ALt-F directory.

> which is
> kinda a hassle, perhaps its worth mapping that, note that the database
> file is mapped to /var/lib/daapd which holds song3.db

That is also standard, /var/lib is where package "users" has its "home"
directory, for persistent storage.

> Had lots of trouble with the iphone remote, until I read on the
> authors site that remote 2.0 is not supported yet. No way to
> downgrade to ver 1.3.3.3 so will have to wait for forked to support
> the new one and for the new forked to make it over to alt-
> f.......hmmmm now found http://forum.qnap.com/viewtopic.php?f=177&t=37472
> where it's been put on QNAP, it suggests remote v2 is supported, is
> the ALT-F an older version of forked?

No, it is the latest stable release.
Perhaps the QNAP version is build from the dev version?

> I've made the logging more verbose and get this:
>
> [2011-02-18 21:13:49] remote: Adding Remote pin data: name 'Gitte',
> pin '9788'
> [2011-02-18 21:13:49] remote: Remote 'Gitte' found
> [2011-02-18 21:13:49] db: Running query 'SELECT * FROM inotify
> WHERE wd = 4;'
> [2011-02-18 21:13:49] scan: File event: 0x8, cookie 0x0, wd 4
> [2011-02-18 21:13:49] remote: Adding Remote pin data: name 'Gitte',
> pin '9788'
> [2011-02-18 21:13:49] remote: Remote 'Gitte' found
>
> but the remote on the iphone doesn't register that it's been
> recognised, so not sure where to go from there, there doesn't seem to
> be any support forums for forked.
>
> Without remote I don't think I can get airport express playing as
> don't know how to play anything without the remote, hmmm probably
> there are some manual commands, but can't find these anywhere. It
> says it needs ipv6 enabled, so have set that to yes on avahi conf to
> prepare.

Alt-F does not has IPV6 builtin... and the QNAP link you post above says to
enable IPV6 on the box.

But the forked README only says:

You should enable IPv6 on the host machine and the AirTunes devices for
AirTunes to work properly. You do not need to do any configuration on the
host machine

But it continues:

Avahi returns IPv4 link-local addresses more often than not when discovering
AirTunes devices. Any device discovered with only an IPv4 link-local address
will be ignored as it cannot work anyway.

Puzzled.
.
I have to see what consequences might arise to build Alt-F with IPV6

Thanks for your research and links, you saved me some time :-)

[Joao Cardoso]

On Friday, February 18, 2011 21:21:37 Hamish Campbell wrote:
> oh, and I can't make avahi and forked be enabled for boot up, is there
> a trick to that?

You found a bug.
You can't also set avahi-daemon or mt-daapd to start on boot.

They share a '-' in their names, and the shell doesn't accept a hyphen as a
valid character in a variable name.

Thanks

[Joao Cardoso]

On Friday, February 18, 2011 21:29:31 Hamish Campbell wrote:
> Remote issue:
>
> comment on that qnap
>
> 'Regarding the remote problem (menaing using the Apple Remote App for
> ipad or iPhone) I found out that this a bug which is related to
> version 2.x of the Apple Remote App. Version 1 of that App worked fine
> with the forked-daapd 0.12 but version 2 does not because Apple
> changed "something". I was informed that Julien has been working on
> that and already included a fix in the new source code. This is either
> available on the web as sources (and could be compiled as needed) or
> will be released with the 0.13 version of forked-daapd. See following
> discussion:
> https://github.com/jasonmc/forked-daapd/issues/issue/23/#issue/23/comment/
> 588851'

Unfortunately the indicated patch does not apply cleanly to 0.12.

> Looking at the discussion quoted it says either to build from trunk or
> wait for 0.13 (whever that is).
>
> I presume you picked up the stable rather than building from trunk?
> Would be a sensible thing to do.

If I only had forked-daapd to maintain, and an Mac and AirTunes, it wouldn't
be that hard to keep in sync with development, so yes, I'm using stable.

I have to see if the indicated patch can be hand-tuned to be applied to 0.12

Thanks again for the research and links.

> Haim

[Joao Cardoso]

On Friday, February 18, 2011 22:06:42 Sam Cole wrote:
...

> As for the randomly stopping: I found that forked-daap would crash
> when it tried to scan certain files. I put logging on 'spam', and then
> removed (or I could have moved) the last file it scanned before it
> crashed.

Its difficult to say if problems come from Alt-F build or are from forked
itself.
Unless there is a 0.12 binary release for linux or MSW to use as a reference.

As I said in the annoucement, some dirty patches have been applied to forked
(and the uClibc system library), to enable building it on Alt-F, and its
difficult to say if problems arise from them.

How severe are the issues? Is forked still usable?

> As for setting it to start on bootup: I had the same problem on the
> web interface, but I was able ssh in and chmod +x the /etc/init.d
> file. Is that dangerous? Curious why I could do it on the shell, but
> not on the web.

I have already answered that question.

You have done the right thing:

chmod +x /etc/init.d/S<whatever>
loadsave_settings -sf

Thanks

[bobcote]

Does the included Forked-daapd in experimental have the ability to
transcode Flac like this one for ffp ? (http://files.hesse-n.com/
ch3snas/)

[Joao Cardoso]

It was compiled with flac and musepack support, but I'v not tried it.
Will you?

[Hamish Campbell]

I guess that transcoding only occurs during playing out locally (sound
card) or sending to airport express. If itunes is playing it I guess
the itunes client is transcoding (or playing natively) ?

If this is the case I'll need to wait until/if the airport express is
working to try this.

Oh, and I agree, maintaining patches etc for this package should be
kept to a minimum, how about we wait for the 0.13 release of forked
before you use more time on remote and airport express (as much as I
would like to play with it :) )

[Joao Cardoso]

On Tuesday, February 22, 2011 09:00:04 Hamish Campbell wrote:

> On Feb 21, 1:53 am, Joao Cardoso <whoami.jc...@gmail.com> wrote:

> > On Feb 20, 9:25 pm, bobcote <baril...@gmail.com> wrote:

> > > Does the included Forked-daapd in experimental have the ability to

> > > transcode Flac like this one for ffp ? (http://files.hesse-n.com/

> > > ch3snas/)

> >

> > It was compiled with flac and musepack support, but I'v not tried it.

> > Will you?

>

> I guess that transcoding only occurs during playing out locally (sound

> card) or sending to airport express. If itunes is playing it I guess

> the itunes client is transcoding (or playing natively) ?

I'm not sure about that.

The readme says:

It uses ffmpeg to extract metadata and

decode the files on the fly when the client doesn't

support the format.

I setup the force_transcode on the configuration file, together with the loglevel to info (or warning?) and saw in the log a transcoding message.

The message implied that ffmpeg was doing the transcoding, but there was no ffmpeg process running, and I could listen the flac (and others) encoded tracks. (this was not done with the packages in the experimental feed, see bellow)

The flac track appears in MSW-iTunes as a wav file, as do vob files (that can be listen); aac and m4a files can't be played, as well as wma (Microsoft ASF) ones... odd!

When invoked from the cmdline ffmpeg-0.6.1 can decode them all.

oh well

> If this is the case I'll need to wait until/if the airport express is

> working to try this.

Actually I'm in the final tests for IPV6, and it seems to be working fine.

Most packages that support ipv6 were recompiled to support it.

Looks like Apple is promoting ipv6, using it in their products.

I have also applied to forked the patch that you found, and I hope that with it plus ipv6 you can use airport with remote V2. (Not that I know what I'm talking about :-! )

A negative side effect of the patch is that one of the apps I use in linux to test forked, banshee, ceased working, with a message saying that probably the server was iTunes 7 and that some changes made by Apple had the purpose of making difficult to use it with non-Apple apps...

> Oh, and I agree, maintaining patches etc for this package should be

> kept to a minimum, how about we wait for the 0.13 release of forked

> before you use more time on remote and airport express (as much as I

> would like to play with it :) )

Too late, it's done :-)

[bobcote]

> > > It was compiled with flac and musepack support, but I'v not tried it.
> > > Will you?

I just discovered Alt-F the day I posted my message and don't have
much time right now, but since you say it has transcoding feature, I
will sure have a look soon because my DNS-323 is only used as a music
server for my Mac/iTunes.

> > I guess that transcoding only occurs during playing out locally (sound
> > card) or sending to airport express.  If itunes is playing it I guess
> > the itunes client is transcoding (or playing natively) ?
>
> I'm not sure about that.

Exactly, the point of transcoding is because iTunes does not support
Flac. So, when Forked-daapd is about to serve a Flac file to a client,
if configured to do so, it will transcode the Flac file to wav and
serve the wav file instead, which is a format supported by iTunes.

[Hamish Campbell]

Couldn't get round to it last night, and tonight I'm busy, so
hopefully will take a look on thursday night.

[Hamish Campbell]

Transcode seems to be working.

I changed the setting to force transcode for flac, popped some flacs
over to my music library on the NAS.

In Itunes (on mac) the flacs showed up, get info reported them as WAV
files. I played them successfully, no issues, played smoothly.

Forked log file (on debug level) wrote a lot of lines saying it was
transcoding, so everything suggests it really was.

Load on the status screen of ALT-F was at 0.35, when I stopped the
playing it spiked to 0.37 then dropped to 0.22

Also plays and reports as wav on Rhythmbox on ubuntu (lucid).

Itunes can skip ahead, Rhythmbox can't.

If I have itunes playing a transcoded file then rhythmbox can play a
non-transcoded, however playing a transcoded causes itunes to stop and
loose connection to the shared library.

Cool.

[Hamish Campbell]

Is the patch applied to the experimental feed?

I'm not getting any difference with remote, finds the remote, says it
connects it, but nothing happens.

Haim

[Joao Cardoso]

On Feb 23, 9:52 pm, Hamish Campbell <haimcampb...@gmail.com> wrote:
> Is the patch applied to the experimental feed?

It is now.

But you should need IPv6 in the experimental Alt-F release. Please
report back if it works with your current Alt-F release and with the
experimental one.

[Hamish Campbell]

On Feb 24, 3:54 am, Joao Cardoso <whoami.jc...@gmail.com> wrote:
> On Feb 23, 9:52 pm, Hamish Campbell <haimcampb...@gmail.com> wrote:
>
> > Is the patch applied to the experimental feed?
>
> It is now.
>
> But you should need IPv6 in the experimental Alt-F release. Please
> report back if it works with your current Alt-F release and with the
> experimental one.
>

My reading suggested that the IPv6 was required for airport express,
and iphone remote was not impacted. But that could be completed
wrong :)

I'll reinstall the packages again tonight and have a bash with the
remote.

Haim

[Hamish Campbell]

Struggling to get any further at the moment.

I've tried the ipv6 firmware (try it), it installed nicely with a very
flashy status page :)

I was a bit worried about how it would cope with installing packages
as not supposed to save settings, so I went back to B6 to update dbus
and ffmpeg and reinstalled forked-daapd.

then I tried ipv6 firmware again.

Issues:

Remote still not working. Still getting the same logs saying that it
found the iphone and has added it (perhaps the is an inotify log there
too?), but then nothing happening on the iphone.

Stop/start of forked via the web screens not working, comes back with
a message saying it was requested but slow to finish. 'ps' still
shows forked running. Using rcforked_daapd stop (noticed that '-'
changed to '_') replies that it is successful however 'ps' still
showing forked.

Reboot and poweroff on ipv6 firmware doens't seem to be working via
web screens. Works fine via the front button.

Didn't try the airport yet....though not sure how one chooses that
output should go there, maybe it automatically does if it has been
found? Don't think the remote will have any selection of speakers.

Oh and presumably due to the change to '_' for forked, the new
experimental package won't start in B6. off to bed now, but perhaps I
can run it with command line??

Might need some guidance now as feeling I might be making some
mistakes in my testing.

[Joao Cardoso]

On Thursday, February 24, 2011 21:51:56 Hamish Campbell wrote:
> Struggling to get any further at the moment.
>
> I've tried the ipv6 firmware (try it), it installed nicely with a very
> flashy status page :)
>
> I was a bit worried about how it would cope with installing packages
> as not supposed to save settings, so I went back to B6 to update dbus
> and ffmpeg and reinstalled forked-daapd.

Right.

But other packages have been rebuilt, because of ipv6. Avahi is one of them,
you should reinstall it also, at least for the airport tests.

> then I tried ipv6 firmware again.
>
> Issues:
>
> Remote still not working. Still getting the same logs saying that it
> found the iphone and has added it (perhaps the is an inotify log there
> too?), but then nothing happening on the iphone.

Perhaps the forked patch you found should be applied to the current (at the
time) development tree, and not to 0.12?

Have you increase forked log level, editing /etc/forked-daapd.conf? to
warning, or even info?

> Stop/start of forked via the web screens not working, comes back with
> a message saying it was requested but slow to finish. 'ps' still
> shows forked running. Using rcforked_daapd stop (noticed that '-'
> changed to '_') replies that it is successful however 'ps' still
> showing forked.

Some daemons take too long to stop after being signaled to do so. minidlna
might take up to one minute! fuppes also takes some time. But forked uses to
be fast -- wasn't it busy indexing folders?

You can see the log in the System->Utilities->logs web page.

> Reboot and poweroff on ipv6 firmware doens't seem to be working via
> web screens. Works fine via the front button.

You found a bug. Corrected now. Thanks.

> Didn't try the airport yet....though not sure how one chooses that
> output should go there, maybe it automatically does if it has been
> found? Don't think the remote will have any selection of speakers.

I can't help you here.

> Oh and presumably due to the change to '_' for forked, the new
> experimental package won't start in B6. off to bed now, but perhaps I
> can run it with command line??

As usual with the experimental feed, when running B6 you need the "common"
file in the /etc/init.d/ directory. But the "common" file that you can find in
the "Packages Update" topic is not valid anymore, I will post the current one
under the same topic.

But the updated forked does not work on B6. I noticed it now when trying to
reproduce your findings. I will fix it and announce in the Packages topic.

> Might need some guidance now as feeling I might be making some
> mistakes in my testing.

You are doing things just fine.
You could get more help, regarding remote or airport, in some forked forum.

[Hamish Campbell]

On Feb 25, 2:44 am, Joao Cardoso <whoami.jc...@gmail.com> wrote:
> On Thursday, February 24, 2011 21:51:56 Hamish Campbell wrote:

> But other packages have been rebuilt, because of ipv6. Avahi is one of them,
> you should reinstall it also, at least for the airport tests.
>
> > then I tried ipv6 firmware again.

I'll reinstall all the packages again to be certain. Can the packages
install correctly with B6....I mean they don't need ipv6 enabled to
install ok?

>
> > Issues:
>
> > Remote still not working.  Still getting the same logs saying that it
> > found the iphone and has added it (perhaps the is an inotify log there
> > too?), but then nothing happening on the iphone.
>
> Perhaps the forked patch you found should be applied to the current (at the
> time) development tree, and not to 0.12?
>

Yeah, that could be true, I'll try again though with all the packages
updated to see if that makes a difference first.

> Have you increase forked log level, editing /etc/forked-daapd.conf? to
> warning, or even info?
>

Yes, set to debug. Otherwise I get nothing almost. Maybe I should
try 'spam' setting just in case there is something else useful.

> > Stop/start of forked via the web screens not working, comes back with
> > a message saying it was requested but slow to finish.  'ps' still
> > shows forked running.  Using rcforked_daapd stop (noticed that '-'
> > changed to '_') replies that it is successful however 'ps' still
> > showing forked.
>
> Some daemons take too long to stop after being signaled to do so. minidlna
> might take up to one minute! fuppes also takes some time. But forked uses to
> be fast -- wasn't it busy indexing folders?
>
> You can see the log in the System->Utilities->logs web page.
>

Heh, forgot to look in there at all!

>
> > Oh and presumably due to the change to '_' for forked, the new
> > experimental package won't start in B6.  off to bed now, but perhaps I
> > can run it with command line??
>
> As usual with the experimental feed, when running B6 you need the "common"
> file in the /etc/init.d/ directory. But the "common" file that you can find in
> the "Packages Update" topic is not valid anymore, I will post the current one
> under the same topic.
>

Hmmm did I need this in for ipv6? I don't remember updating it,
perhaps this was the issue with starting and stopping forked.

>
> > Might need some guidance now as feeling I might be making some
> > mistakes in my testing.
>
> You are doing things just fine.
> You could get more help, regarding remote or airport, in some forked forum.
>

Yeah, struggling to find a forked forum, but haven't really tried,
perhaps I'll settle for an ubuntu or qnap forum where others are using
it.

>  common
> 2KViewDownload


Cheers, have some more stuff to try so thats good.

[Hamish Campbell]

Sorry Joao,

I've disappeared off the radar for a bit.

I noticed a version bump for forked to 0.13 which should have the best
chance of working for the remote and express. Is the experimental
package updated? Or perhaps B7 is so imminent it's best to wait for
that? Especially as I need the ipv6 as part of it....

oh about that, found out my router (Dlink DIR655) doesn't support
ipv6, so I'm not sure if that kills it dead in the water.

Hopefully some time in the weekend for a play.

Hamish

[Joao Cardoso]

On Mar 18, 10:44 am, Hamish Campbell <haimcampb...@gmail.com> wrote:
> Sorry Joao,
>
> I've disappeared off the radar for a bit.
>
> I noticed a version bump for forked to 0.13 which should have the best
> chance of working for the remote and express.  Is the experimental
> package updated?  Or perhaps B7 is so imminent

Both :-)

> it's best to wait for that?

Don't you want to be a beta tester when you grow-up? :-) Try it now!

>  Especially as I need the ipv6 as part of it....

Not sure. According to forked-daapd README commit log, IPv6 is not
needed anymore:

Remove paragraph about IPv6 for AirTunes; IPv4 works reliably now

However, the commit was done after 0.13 was released, not sure if it
applies.

> oh about that, found out my router (Dlink DIR655) doesn't support
> ipv6, so I'm not sure if that kills it dead in the water.

But the switch part of the router certainly does, so you can have IPv6
in your local network.

> Hopefully some time in the weekend for a play.

Sun is shinning here, after weeks of rain and grizzly days, I will go
for a walk ;-)

> Hamish

[Hamish Campbell]

OK, have had a tiny play.

B7rc worked on the second try it attempt. First one froze.

Forked wouldnt work initially, had to

create database directory /var/lib/daapd , this is the default in the
conf file but does not get created.
chown that directory to 'daapd' user.

Then on next start of forked the 'songs3.db' file was created
successfully and I could see my music library in rythmbox on my ubuntu
machine.

in case its interesting:
have the 'common' file from your post above. avahi and forked start
and stop fine.
deinstalled packages and then reinstalled again before trying the b7,
experimental feed of course.

Next up is to try the remote on the iPhone, but might have to be
another night.

Oh and being able to access the log files in the web admin screens is
very convenient, nice :)

Haim

[Hamish Campbell]

Didn't have any luck with the remote, but afterwards I saw I had done
something in the wrong order.

Will try again tonight I hope.

Oh and shutdown and reboot from the b7 web admin wasn't working,
button on the device worked fine (with the flashing left and right
led's). Was off to bed so haven't checked the log for anything about
that.

Haim

[Joao Cardoso]

On Monday, March 21, 2011 21:46:47 Hamish Campbell wrote:
> OK, have had a tiny play.
>
> B7rc worked on the second try it attempt. First one froze.
>
> Forked wouldnt work initially, had to
>
> create database directory /var/lib/daapd , this is the default in the
> conf file but does not get created.
> chown that directory to 'daapd' user.

I couldn't reproduce that.
The install script creates the "user" and its directory...

> Then on next start of forked the 'songs3.db' file was created
> successfully and I could see my music library in rythmbox on my ubuntu
> machine.
>
> in case its interesting:
> have the 'common' file from your post above. avahi and forked start
> and stop fine.
> deinstalled packages and then reinstalled again before trying the b7,
> experimental feed of course.

That is not really necessary, although desirable.
It is possible to force a reinstall of a package keeping its configuration
files. After changing the feed to the experimental feed and updating the
package list, type in the command line:

ipkg -force-reinstall -force-defaults install <pkgname>

and the other way around to return to the default feed. This should only be
done when the package version is the same.

> Next up is to try the remote on the iPhone, but might have to be
> another night.
>
> Oh and being able to access the log files in the web admin screens is
> very convenient, nice :)
>
> Haim

On Tuesday, March 22, 2011 09:05:47 Hamish Campbell wrote:
> Didn't have any luck with the remote, but afterwards I saw I had done
> something in the wrong order.

If you still don't succeed in the next attempt, try turning IPv6 on in Setup-
>Host, no reboot is needed (only to turn it off)

> Will try again tonight I hope.
>
> Oh and shutdown and reboot from the b7 web admin wasn't working,

Bug now fixed, thanks.

[Hamish Campbell]

Tried the remote, this time with the correct order of events. Still
no luck.

Log looks quite good, seems the remote is found (mDNS stuff) and can
translate to the ip address.
It then says it finds the remote related to the name in the *.remote
file.

But then nothing happens on the remote, so it seems pairing doesn't
really occur.

Seems there is no forum anywhere, so I'll post on the QNAP forum I
think as they are somewhat succesful with it.

I'll try the ipv6 thing first...in a couple of days unfortunately but
hey.

Hamish

[Hamish Campbell]

Tried again with the new version 0.14

No improvement. Had ipv6 enabled.

Still haven't got round to posting anywhere yet, will try now....

Oh and in system log I get:

eth0: no IPv6 routers present

Not sure if that impacts on the local network ??

[Hamish Campbell]

I've posted to the QNAP forums

http://forum.qnap.com/viewtopic.php?f=177&t=37472&p=189970#p189970

And got some suggestions from the guy who has got forked running on
QNAP.

Unfortunately not going any better with the remote.

The log looks fine as far as I can tell, and checking with avahi
suggests that the iphone remote is recognised correctly. So
everything looking good, except that the remote doesn't move away from
the 4 digit code displaying screen :(

If anyone else could give this a try that would be great.

%%%%%%%%%%%%
forked-daapd log of remote pairing
%%%%%%%%%%%%%
[2011-04-03 21:03:22] mdns: Avahi Browser: NEW service
'2e63af3838e6937e3203d4879661f4695994c1c3' type '_touch-remote._tcp'
proto 0
[2011-04-03 21:03:22] mdns: Avahi Browser: NEW service
'2e63af3838e6937e3203d4879661f4695994c1c3' type '_touch-remote._tcp'
proto 0
[2011-04-03 21:03:22] mdns: Avahi Resolver: resolved service
'2e63af3838e6937e3203d4879661f4695994c1c3' type '_touch-remote._tcp'
proto 0
[2011-04-03 21:03:22] mdns: Avahi Resolver: resolved service
'2e63af3838e6937e3203d4879661f4695994c1c3' type '_touch-remote._tcp'
proto 0
[2011-04-03 21:03:22] mdns: Service
2e63af3838e6937e3203d4879661f4695994c1c3, hostname Gitte.local
resolved to 192.168.0.198
[2011-04-03 21:03:22] remote: Discovered remote Gitte (id
2e63af3838e6937e3203d4879661f4695994c1c3) at [192.168.0.198]:51172,
paircode 76DF556E39766D27
[2011-04-03 21:03:22] remote: Remote id
2e63af3838e6937e3203d4879661f4695994c1c3 not known, adding
[2011-04-03 21:03:22] mdns: Service
2e63af3838e6937e3203d4879661f4695994c1c3, hostname Gitte.local
resolved to 192.168.0.198
[2011-04-03 21:03:22] remote: Discovered remote Gitte (id
2e63af3838e6937e3203d4879661f4695994c1c3) at [192.168.0.198]:51172,
paircode 76DF556E39766D27
[2011-04-03 21:03:22] remote: Remote id
2e63af3838e6937e3203d4879661f4695994c1c3 found
[2011-04-03 21:03:39] db: Running query 'SELECT * FROM inotify
WHERE wd = 4;'
[2011-04-03 21:03:39] scan: File event: 0x100, cookie 0x0, wd 4
[2011-04-03 21:03:39] remote: Invalid Remote pairing file /mnt/
CampbellNas/Public/Music/r.remote
[2011-04-03 21:03:39] db: Running query 'SELECT * FROM inotify
WHERE wd = 4;'
[2011-04-03 21:03:39] scan: File event: 0x2, cookie 0x0, wd 4
[2011-04-03 21:03:39] remote: Adding Remote pin data: name 'Gitte',
pin '8515'
[2011-04-03 21:03:39] remote: Remote 'Gitte' found
[2011-04-03 21:03:39] db: Running query 'SELECT * FROM inotify
WHERE wd = 4;'
[2011-04-03 21:03:39] scan: File event: 0x8, cookie 0x0, wd 4
[2011-04-03 21:03:39] remote: Adding Remote pin data: name 'Gitte',
pin '8515'
[2011-04-03 21:03:39] remote: Remote 'Gitte' found

%%%%%%%%%%%%%%%%%%

%%%%%%%%%%%%%%%%%%%
Result of avahi-browse -r _touch-remote._tcp call (should also have -
k option supposedly but this isn't recognised in Alt-F)
%%%%%%%%%%%%%%%%%%%%

+ eth0 IPv4 2e63af3838e6937e3203d4879661f4695994c1c3 _touch-
remote._tcp local
= eth0 IPv4 2e63af3838e6937e3203d4879661f4695994c1c3 _touch-
remote._tcp local
hostname = [Gitte.local]
address = [192.168.0.198]
port = [51172]
txt = ["DvNm=Gitte" "DvTy=iPhone" "RemV=10000" "RemN=Remote"
"txtvers=1" "Pair=76DF556E39766D27"]

[Hamish Campbell]

A comment from the guy at qnap forum:

%%%%%%%%%%
Unfortunately I only have the Android Remote App to test against, and
it works. However, I have tried the iPhone Remote App v2 as recently
as last week and it worked as well. I never did find the git
repository for the Alt-F version of forked-daapd, but I did find a few
patches. One of them made me worry a little as it mentioned that you
guys are based on ulibc and not eglibc or libc. There was also a note
about some system level event functions that were missing. The patch
didn't elaborate, but if you don't have support for the way forked-
daapd uses events then you're certainly going to have trouble with
getting it to work. The pairing code definitely relies on eventfd and
threading. If your c library isn't up to snuff you'll get have a lot
of problems.
%%%%%%%%%%

I'm guessing that might mean something to you Joao :)

[Hamish Campbell]

A bit more info from the helpful chap at QNAP

%%%%%%%%%%%%%


Here's that patch I'm referring to:

http://code.google.com/p/alt-f/source/b ... 024&r=1024

There's a comment in there that questions whether or not the fdtimer
patch is working correctly. Based on the evidence I'd wonder if any of
the patches are working. You need to get the developer to sit down
iwth gdb and forked-daapd and verify that things are working.

%%%%%%%%%%%%%%%%%%%%

Joao, you might want to check how many people are actually interested
in this and weigh up against how much work it is. I seem to be the
only one trying this out, so perhaps I'm the only one who will use it!

[Bink]

Joao, you might want to check how many people are actually interested
in this and weigh up against how much work it is.  I seem to be the
only one trying this out, so perhaps I'm the only one who will use it!

There certainly must be others like me who are reading along hoping you guys can figure it out. I just jumped on the Alt-F bandwaggon a few days ago and was excited about this project after having tried uncessfully to get daapd up and running with a convoluted setup through ffp.

I haven't got the iPhone remote working yet, but the logs are interesting. Originally my iPhone had a longer name with an apostrophy so I changed it to be safe. Funny thing is that now it isn't even trying to pair with the remote and is instead reading that text file as a music scan. Obviously there are a few errors here, but I am not sure what to make of them and I don't understand what changed from the first try to the next. I'm not too techie, but let me know if I can provide any testing here in this quest.

[2011-04-03 12:39:12]     main: Forked Media Server Version 0.14 taking off
[2011-04-03 12:39:12]     main: mDNS init
[2011-04-03 12:39:12]     mdns: Avahi state change: Client running
[2011-04-03 12:39:15]   player: AirTunes 00145173D063@Home Stereo: no am field in TXT record!
[2011-04-03 12:39:35]   remote: Remote 'Brady's iPhone' not known from mDNS, ignoring
[2011-04-04 19:16:21]   remote: Invalid Remote pairing file /mnt/sda2/ClineShare/Media/Music/iTunes-NAS/iTunes Music/bphone.remote: device name too long or missing pin
[2011-04-04 22:37:28]     scan: Could not lstat() '/mnt/sda2/ClineShare/Media/Music/iTunes-NAS/iTunes Music/bphone6.remote': No such file or directory

[Joao Cardoso]

OK, I will try to do a test to see if the fdtimer patch for uClibc works or not.

The patch was submited and accepted in the uClibc mailing list.

Can you tell me what is the Android app that can be used instead of a true iPhone?

I own an Android htc phone. (version 1.5! shame on me! I have not yet flashed cyanogen mod, as I have a SPL phone)

[AntDok]

Hi I'm the guy on the QNAP forums that has gotten forked-daapd running
on that platform. I just had a discussion with Julien Blache (forked-
daapd's author). He shed a lot light on your issues with remote
paring. Here's what he said:

""
Anyway. The Alt-F pairing issue.

The log given by Haim shows everything works fine up to kicking off
the actual pairing. That involves posting an event to the eventfd.

Except they don't have eventfd, so they defaulted to the pipe() code.
Except that code uses pipe2() and they don't have it, so they just use
pipe() and discard the flags. One of the flags is O_NONBLOCK.

So the function handling the event on the pipe is just blocking on a
read() on the pipe now.
""

I'm nowhere near as competent as Julien when it comes to POSIX threads
and linux, but it seems as you'll need to find another way to read
from the pipe that doesn't block. You may want to look into using
ioctl(...FIONBIO...) and fcntl(...O_NDELAY...) on your file
descriptors before putting them into the pipe(). (However, this is
just an educated guess based on some Google-fu that I did today.)

Regards,

AntDok

[Joao Cardoso]

On Apr 4, 10:38 pm, AntDok <ant...@gmail.com> wrote:
> Hi I'm the guy on the QNAP forums that has gotten forked-daapd running
> on that platform. I just had a discussion with Julien Blache (forked-
> daapd's author).

Thanks AntDok.

Have you actually shown the patch to Julien? I had though in posting
it in the forked-daap github issues section.

After all uClibc is very common in embedded devices, Alt-F is surely
not the only one to suffer with the incompatibilities.

> He shed a lot light on your issues with remote
> paring. Here's what he said:
>
> ""
> Anyway. The Alt-F pairing issue.
>
> The log given by Haim shows everything works fine up to kicking off
> the actual pairing. That involves posting an event to the eventfd.
>
> Except they don't have eventfd,

Actually I have applied an eventfd patch to uClibc, as i said in a
previous message. Working?

> so they defaulted to the pipe() code.
> Except that code uses pipe2() and they don't have it, so they just use
> pipe() and discard the flags. One of the flags is O_NONBLOCK.
>
> So the function handling the event on the pipe is just blocking on a
> read() on the pipe now.

Knowing where the problem is will help a lot. I did not examine the
code, if pipe2() is only used in this place I might be able to provide
a real patch.

The patch I currently use was intended just for compilation. As
serving files worked fine... and as I don't have a iPhone to test
with...

But there is also another unexistent function in uClibc (that is often
used in embedded devices), inotify_init1()

[AntDok]

I haven't shown any patches to Julien. I suspect he looked at one that
I linked to from the QNAP forums. That one had some notes about
missing eventfd and some #defines for pipe2 to pipe. It also had some
#defines for messing with byte ordering.

I couldn't find the Alt-F git repository so I never was able to see
all the patches.

Regarding inotify_init1(); you're going to have similar issues as you
have with pipe/pipe2. The flags are important. If Julien set them up
for non-blocking IO then you will need add a patch to set the file
descriptors to be non-blocking. I think you can do this because non-
blocking IO was possible prior to the introduction of O_NONBLOCK.

Also you should check the host to network byte ordering macros and
make sure you're getting what you think you're getting. The host to
big-endian 32 functions might be equivalent, but you should verify
that they are. They are used in quite a few places within forked-daapd
and it's important they are correct. Otherwise you'll have issues
streaming to remote devices (like the Airport Express).

[Hamish Campbell]

I have 'Tunes Remote' which is free, and that successfully connects to
iTunes on my Mac, (not on Alt-F of course....yet!!?? :) ).

So I presume that is the one AntDoc is using too, although there are
some non-free (as in beer) remote apps too.

[Joao Cardoso]

> I have 'Tunes Remote' which is free, and that successfully connects to 
> iTunes on my Mac, (not on Alt-F of course....yet!!?? :) ). 

yet!? Of course.

I was sorting-out some possible problems with the new dlink-1.10b6 firmware (but found no problem!) and I will resume forked-daapd ASAP.

But it will not be simple to emulate pipe2() -- I will try a simple approach first, that might solve problems even if occasionally it will make forked to froze.

[Joao Cardoso]

I just put a recompiled forked-daapd in the unstable feed.

You have to update the feed list and remove/reinstall the app, as it has the same version number as the previous one.

It works with rhytmbox and android DAAP app, but when using TunesRemote the logs says it can't found alsa.conf.

I looked in the QNAP forum, and this seems to be an unsolved problem? At least I didn't found any solution.

The only modification I did was to:

#define pipe2(a,b) pipe(a); fcntl(a[0], F_SETFD, fcntl(a[0], F_GETFD) | (b)); fcntl(a[1], F_SETFD, fcntl(a[1], F_GETFD) | (b));

I didn't worry for now with the nonexistent inotify_init1(), as it is obviously related with inotify -- probably forked won't notice new/changed files.

[Ramza]

Sorry, I hope it's ok to post a question here. I just installed
forked_daapd 0.14, avahi and dbus are running. When I try to start it,
I get this message: "forked_daapd: Starting forked-daapd: Fail.".

There's a database directory(/var/lib/daapd), but It's empty. I'm
still using B6 Firmware, btw. Any idea what could be wrong? Thanks!

[Joao Cardoso]

Probably the daapd user is non-existent -- during the install it should have been created.

Try at the command line:

   

    id daapd

if it says unknown user, then use the following commands to create the user:

   addgroup -S -g 80 multimedia

   adduser -S -g "forked-daapd user" -G multimedia -u 16 -h /var/lib/daapd daapd

You should probably use 0.1B7.

[Ramza]

On 6 Apr., 21:15, Joao Cardoso <whoami.jc...@gmail.com> wrote:
> Probably the daapd user is non-existent -- during the install it should have
> been created.
>
> Try at the command line:
>
>     id daapd

with this command I get:

uid=16(daapd) gid=80(multimedia) groups=80(multimedia)

> You should probably use 0.1B7.

Can I update it with the system/firmware option? I haven't flashed the
my system with alt-f yet.

[Joao Cardoso]

You can try 0.1B7 from a running 0.1B6, either reloaded or flashed.

Just go to System->Firmware, upload 0.1B7.bin, then instead of hitting the "FlashIt" button hit the "TryIt" button, then "Reboot"

[Ramza]

I've updated to 0.1B7, now I get this when trying to start forked-
daapd:

Starting dbus-uuidgen: OK.
Starting dbus-daemon: Fail.
'avahi-daemon' can't be started, as 'dbus' is needed and can't be
started.
'forked-daapd' can't be started, as 'avahi_daemon' is needed and can't
be started.

[Joao Cardoso]

I don't know what course of action you took regarding packages, or if you have been using the experimental feed.

The usual method informatics "engineers" follow  is to uninstall and reinstall :-) What a mood!

Start updating the feed list, then uninstall forked, than avahi, then dbus; next install forked -- the others will follow automatically.

If you have been using the experimental feed, read the "release notes" following the announcement.

[Joao Cardoso]

I installed the full /usr/share/alsa hierarchy and customized /etc/asound.conf according to issue 17 (and also read the full alsa related threads in the QNAP forum).

Haim, if you want, I can post the /usr/share/alsa hierarchy for you to try.

And, with Android Tunes Remote I can see all Albuns/Artists/Song but when I try to start playing one of them, I get the error:

[2011-04-07 03:56:05]   ffmpeg: max_analyze_duration reached

[2011-04-07 03:56:05]   ffmpeg: Estimating duration from bitrate, this may be inaccurate

[2011-04-07 03:56:05]   laudio: Could not open playback device: No such file or directory

[2011-04-07 03:56:05]   player: Could not open local audio

[2011-04-07 03:56:05]     dacp: Could not start playback

which is the same reported in http://forum.qnap.com/viewtopic.php?f=177&t=37472&hilit=alsa&start=45#p167695

I have even enabled IPv6, same results.

With Android DAAP, or iTunes on MS, or rhytmbox I can play songs.

If I have no more hints, I have to leave it as is and wait for "local sound" to be a configure or runtime option.

[Hamish Campbell]

I only had a quick look late last night.

1. Reinstalled forked by uninstalling, updating packages and
installing again (only forked package, should I have done any
others?). I'm still experiencing that /var/lib/daapd is not being
created, so I need to create this and chown to daapd user. Forgot to
check the log to see if it tries to do this.

2. No change to Iphone Remote, not connecting, same log entries.

3. No change to Tunes Remote on android ( are we using the same one,
Tunes Remote by Jeff Sharkley...note that I don't think this is
maintained any more, maybe I should try another one...any suggestions
anyone?). When I select the library I think a passcode screen should
come up, but nothing comes up at all, just goes to a blank screen with
'play' controls.

4. Installed Daapd music player on my android, it worked well.

5. I don' t think Iphone and Android remotes (i.e. NOT daapd music
player) can stream music, they just control the library and set it
playing where it is install. So makes some sense that you can't play
anything when there is no output to play to. So if I can get to where
you are then there's a good chance my airport express can be connect
too (thats the idea from the start) and I can play via that. So no
need for alsa for me.....I also don't have a usb soundcard I could
play out of the dns323 to.

I'll try reinstalling again, as perhaps the update didn't work or
something and I just reinstalled the same one.

Sounds like you got connected fine though, so well done.....although
I'll leave the jumping up and down to when I can get it working too!

Don't know why I did numbers, just felt like it.

On Apr 7, 5:42 am, Joao Cardoso <whoami.jc...@gmail.com> wrote:
> I installed the full /usr/share/alsa hierarchy
> and customized /etc/asound.conf according to issue 17 (and also read the
> full alsa related threads in the QNAP forum).
> Haim, if you want, I can post the /usr/share/alsa hierarchy for you to try.
>
> And, with Android Tunes Remote I can see all Albuns/Artists/Song but when I
> try to start playing one of them, I get the error:
>
> [2011-04-07 03:56:05]   ffmpeg: max_analyze_duration reached
> [2011-04-07 03:56:05]   ffmpeg: Estimating duration from bitrate, this may
> be inaccurate
> [2011-04-07 03:56:05]   laudio: Could not open playback device: No such file
> or directory
> [2011-04-07 03:56:05]   player: Could not open local audio
> [2011-04-07 03:56:05]     dacp: Could not start playback
>
> which is the same reported

> inhttp://forum.qnap.com/viewtopic.php?f=177&t=37472&hilit=alsa&start=45...

[Joao Cardoso]

On Thursday, April 7, 2011 7:55:11 AM UTC+1, Hamish Campbell wrote:

I only had a quick look late last night.

1.  Reinstalled forked by uninstalling, updating packages and
installing again (only forked package, should I have done any
others?).

No. But I might have downloaded the wrong version. Please try again

 

 I'm still experiencing that /var/lib/daapd is not being
created,

OK...? Now /var/lib/daapd is not deleted when forked is removed. But you will only notice that after the next install.

so I need to create this and chown to daapd user.  Forgot to
check the log to see if it tries to do this.  

2.  No change to Iphone Remote, not connecting, same log entries.

3. No change to Tunes Remote on android ( are we using the same one,
Tunes Remote by Jeff Sharkley...

I have downloaded it from http://dacp.jsharkey.org/, it is named TunesRemote-r2.apk, I couldn't find it in Market. On startup it says a new version with 9000! improvements is available, but Marked couldn't find it.

 

note that I don't think this is
maintained any more, maybe I should try another one...any suggestions
anyone?).  When I select the library I think a passcode screen should
come up, but nothing comes up at all, just goes to a blank screen with
'play' controls.

Yes... I also notice that. When connecting to MS iTunes a pairing dialogue appears. The forked log, in debug mode says:

[2011-04-07 14:52:52]    httpd: Found query string

[2011-04-07 14:52:52]     daap: DAAP request: /login?pairing-guid=0x0000

[2011-04-07 14:52:52]    httpd: Not gzipping; no Accept-Encoding header

[2011-04-07 14:52:52]    httpd: Found query string

[2011-04-07 14:52:52]     daap: DAAP request: /databases?session-id=100

In the connection dialogue I entered '0000' as the pairing code. No changes made to /etc/forked-daap.conf

4.  Installed Daapd music player on my android, it worked well.

5. I don' t think Iphone and Android remotes (i.e. NOT daapd music
player) can stream music, they just control the library and set it
playing where it is install.  So makes some sense that you can't play
anything when there is no output to play to.  So if I can get to where
you are then there's a good chance my airport express can be connect
too (thats the idea from the start)

ah. I have not understood that. So Remote acts as a control point (in uPnP jargon)  i.e., it locates a songs library (forked) and a player device (airport) and instructs the library device to stream to the player.

 

and I can play via that.  So no
need for alsa for me.....I also don't have a usb soundcard I could
play out of the dns323 to.

I don't know anything about daapd, I'm just trying to follow your instructions. But the lack of sound seems to be a problem, also in the QNAP forum. Latter on, on forked log, when I select a music to be played:

[2011-04-07 14:55:18]   player: Opening /mnt/sda2/Public/RW/Music/BB King/Kansas City, 1972/Introdu

ction.mp3

[2011-04-07 14:55:18]   ffmpeg: Probed with size=2048 and score=51

[2011-04-07 14:55:19]   ffmpeg: max_analyze_duration reached

[2011-04-07 14:55:19]   ffmpeg: Estimating duration from bitrate, this may be inaccurate

[2011-04-07 14:55:19]   laudio: Could not open playback device: No such file or directory

[2011-04-07 14:55:19]   player: Could not open local audio

[2011-04-07 14:55:19]     dacp: Could not start playback

Without the /usr/share/alsa hierarchy you should get a /usr/share/alsa/alsa.conf not found or similar

[Ramza]

I reinstalled everything and it worked! But now with 0.1B7 I can't
start Transmission 1.92 (don't want to update to 2.22), so it's either
B6 with Transmission or B7 with forked-daapd for me :-/

Anyway, thanks for all your help again!

[Hamish Campbell]

OK, better write down my status before I fall asleep.

I reinstalled forked from unstable feed.

Same problem with Iphone remote, finding and adding (says the log) but
doesn't move away from code screen in remote.

I was struggling to understand TunesRemote, so downloaded TunesRemote
+ (plus) which is supposedly an improved version (perhaps this is the
9000 improved one?).

This did connect!! Strangely with completely different log entries!
Weird, and no talk of a code!! Odd.

However the remote was not so successful, it showed nothing
initially. The only options are Artist and Playlists (where is albums
or songs??). Artists says there is nothing. Playlists comes up with
Movies and Tv shows, movies contained the two .avi files I'd put on
the NAS.
But I could search and find my music!!! Weird.

Trying to play a result of a search did nothing, the log showed :

[2011-04-07 21:28:38] dacp: DACP request: /ctrl-int/1/cue?
command=play&query=(('com.apple.itunes.mediakind:
1','com.apple.itunes.mediakind:4','com.apple.itunes.mediakind:8')+
('dmap.itemname:*kereru*','daap.songartist:*kereru*','daap.songalbum:*kereru*'))&type=music&sort=name&index=0&session-
id=101
[2011-04-07 21:28:38] daap: Trying DAAP query -
(('com.apple.itunes.mediakind:1','com.apple.itunes.mediakind:
4','com.apple.itunes.mediakind:8')
('dmap.itemname:*kereru*','daap.songartist:*kereru*','daap.songalbum:*kereru*'))-
[2011-04-07 21:28:38] daap: DAAP query parser terminated with 1
errors
[2011-04-07 21:28:38] player: Improper DAAP query!
[2011-04-07 21:28:38] dacp: Could not build song queue
[2011-04-07 21:28:38] httpd: Found query string
[2011-04-07 21:28:38] dacp: DACP request: /ctrl-int/1/
playstatusupdate?revision-number=1&session-id=101
[2011-04-07 21:28:38] player: Player status: stopped

Now interestingly the play command (command=play...) has itemname and
sogartist etc all listed as 'kereru', this is NOT what I tried to
play, this was my search string for finding the tracks. Note also
that the result of the search was not one song but ALL the tracks in
no particular order, weird again.

So I tried to play the .avi file. The log said it was trying to
transcode. Also the remote showed the file as playing.

I got the same alsa stuff.

However I turned on my airport express and it looks like this was
found and connected too. It was now available for selection in the
'speakers' section of the remote, very nice. Unfortunately no sound
coming out, but this may be due to the .avi file not really being
supported.

So it seems my main problem there is that the remote can't find and
display my tracks properly. Did that work for you ok Joao? I had a
mix of mp3's and mp4's. Interestingly forked didn't have any luck
with artwork, mine is in the file whilst forked seems to want a file
(cover.jpg etc). Maybe I should put one there, maybe that is stuffing
up the remote for some reason, though lack of artwork shouldn't break
it really.

I have also bought HyperFines 'Remote for Itunes'. It wants to use a
code just like the iphone remote, I had the same result with it,
appearing to find and connect correctly but doens't move away from the
code screen.


So, Joao, I need to replicate you with being able to see the tracks on
the TunesRemote app. I'm not sure what would be different between our
systems. I think that if I can see one and play it then it should
come over my airport express ok.

Thats all I can think of for the moment. Have got a bit of a flu, so
am off to bed :)

[Joao Cardoso]

...

So it seems my main problem there is that the remote can't find and
display my tracks properly.  Did that work for you ok Joao?  I had a
mix of mp3's and mp4's.

Try pointing forked to a music-only directory -- I can see Albuns/Artists/Songs contents.

But If the directory (or/and subdirs?) has avi files, I can't see nothing in android remote.

You might have to remove songs.db first.

Searching didn't work all right for me -- many files not obviously related with the search was returned.

Thats all I can think of for the moment.  Have got a bit of a flu, so
am off to bed :)

Wish you get better. 

[Hamish Campbell]

On Apr 8, 4:36 am, Joao Cardoso <whoami.jc...@gmail.com> wrote:

>
> Try pointing forked to a music-only directory --

I tried that, a good suggestion, but no luck. songs.db was recreated,
the avi's no longer appeared in the movies playlist on the remote, but
nothing coming up otherwise.

> I can see
> Albuns/Artists/Songs contents.

Do you get options for those in the menu of the remote? I only get
Artist to choose from.

There is a fair bit of talk on the http://hyperfine.com/remoteforitunes/help.aspx
and tips pages that router issues can cause problems.

Multicast is one thing, i've enabled something on my router with that
name, but no change. Some suggestion on forums that my router has
issues with multicast. But I think it might be more to do with
finding the remote which does work fine.

Also talk about some udp and tcp ports, so I'll next try to set them
as open on my router (can't really see that anything is specifically
closing them) and see if that helps.

Haim

[Hamish Campbell]

Ok, a little update.

I am a fool, the hifi attached to my airport express was not plugged
in heheee.

So if I select that .avi file (the only file type I can see in
TunesRemote), then it will play over my Airport Express!!! nice.

Now 'pause' didn't work, and finally hitting << instead stopped it
(log said 'at start of playlist and not set to reply' or something
similar). This also seemed to kill forked as well.

I tried moving some mp3's to my movies directory to see if they would
come in the Movie playlist, but that didn't work, must be done by file
type ??

thats all for now.

[Hamish Campbell]

I tried opening those ports, but didn't help any :(

So still iphone/remote for itunes (android) looks like they connect
ok, but don't on the app.
TunesRemote cannot see my mp3's, can see avi, puts it in a Movies
playlist, and CAN play it via aiport express.

[Joao Cardoso]

Well, you certainly made some advances.

Don't you have a linux computer? Even if you don't, you can try to install linux on a Virtual Machine under MS-W (might not be easy, depends on your expertise), or even start your computer from a linux LiveCD/DVD.

My idea is that you could use a pre-built forked-daapd in linux, with glibc and not uClibc, so you can figure out what is wrong: if Alt-F, if forked, if your remote skills :-)

[Joao Cardoso]

Forked-daapd-0.15 was released, but only within two or three weeks I
will be able to release a ipkg.

The suggestion I gave above, installing forked on a standard llinux
computer is not likely to work, as forked requires a specially build
SQLite3. At least in opensuse-11.3 it ./configure does not work.

Forked is very susceptible, to be kind. Not only requires almost
unknown libraries, specially build packages, uses non-standard system
calls... but also has an enormous dependency list.
Infancy problems? perhaps.

[Hamish Campbell]

On Apr 11, 5:53 am, Joao Cardoso <whoami.jc...@gmail.com> wrote:
> On Apr 9, 1:12 am, Joao Cardoso <whoami.jc...@gmail.com> wrote:

>
> The suggestion I gave above, installing forked on a standard llinux
> computer is not likely to work, as forked requires a specially build
> SQLite3. At least in opensuse-11.3 it ./configure does not work.
>

It's a good idea though. I was busy over the weekend building a big
flower bed....takes me ages as I'm not much of a handyman. I had a
tiny look at how I could get it on my ubuntu machine. One guy has a
script for it, linked up to a PPA (is that a standard or an ubuntu
term?), but it had some trouble downloading what it needed. Anyway
I'll post on that forum and see if I can get some help to get it
going. I'm not used to compiling stuff but have done it before.
Anyway, it should be possibile if I read the instructions.

Haim

[Joao Cardoso]

It is not an easy task. 

The dependency list: zlib libavl libunistring libevent libgcrypt libconfuse mxml alsa-lib libantlr sqlite avahi ffmpeg taglib flac

Some might be available in Ubuntu, but you will have to install the development version (where the header files are)

You will have to download and install libavl (from the same site where you get forked, *not* the GNU version!)

I had to download a runtime version of libantlr (never heard of it!) in http://www.antlr.org/download/C/ 

mxml (mini-xml) can be found at  http://ftp.easysw.com/pub/mxml/

The others might be available in Ubuntu.

If, after downloading and extracting forked you type './configure'

it spits that no zlib was found (stupid!), you might have to tell it

  ./configure ZLIB_LIBS="-lz" ZLIB_CFLAGS=" "

if it spits

  checking for sqlite3_unlock_notify in -lsqlite3... no

  configure: error: SQLite3 was built without unlock notify support

you will have to recompile sqlite, kind of

  ./configure CFLAGS="-DSQLITE_ENABLE_UNLOCK_NOTIFY" ....

Better for you to finish your 'big flower bed' first :-)

[Hamish Campbell]

I can see it's in the packages for Ubuntu Natty (the next one) due at
the end of the month. So I can install that when it arrives and
hopefully the install of forked should be a few clicks.

[Andy Pemberton]

Curious if anyone ever got this working. On flashed Alt-F-0.1RC2.bin I cannot get Remote app from iPhone working.

Pairing gets somewhere:

[2012-12-31 14:27:39]       db: Running query 'SELECT * FROM inotify WHERE wd = 2;'
[2012-12-31 14:27:39]     scan: File event: 0x8, cookie 0x0, wd 2
[2012-12-31 14:27:39]   remote: Adding Remote pin data: name 'APiPhone', pin '5409'
[2012-12-31 14:27:39]   remote: Remote 'APiPhone' found

But then no pairing hash, etc generated... ?

[shredhead]

I just gave this another shot and so far it isn't working, meaning iTunes on my PC does not see the share. I don't have interest in using remote. The log entries I see make me thing it's still scanning through the contents of the directory I shared. But thjat can't be still happening since it's been a few days. Does the share show up when it's scanning or does it need to finish first?

[shredhead]

I think forked-daapd has problems with iTunes 11 based on my recent web searches. Can anyone confirm? 

[Andy Pemberton]

Confirmed. I never got it pairing after several hours trying. 

Sent from my iPhone

--
You received this message because you are subscribed to the Google Groups "Alt-F" group.
To post to this group, send email to al...@googlegroups.com.
To unsubscribe from this group, send email to alt-f+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/alt-f?hl=en.
To view this discussion on the web visit https://groups.google.com/d/msg/alt-f/-/6UANq6RAjgcJ.
 
 

[Tom Cadorette]

iTunes 11 certainly sucks donkey balls for me. Although it sees my shared library, and will play a song sometimes all the way through and then another, it immediately switches back to the default library from the shared, cutting the song off -- sometimes it does it in the middle of the first song.

Seems to work fine with Songbird 2.0 and the no-longer-being-developed DAAP plug-in written for Songbird 1.8 -- but you have to disable 2.0's XPI compatibility check to install it, so that's not a good long-term solution, particularly if the next Songbird upgrade totally breaks the plug-in. 

I should note: I am running 0.1RC2 on a B1 board (I think?), two Seagate ST31000340AS, 1TB each, RAID1, ext2 format, OS is Windows 7 64-bit. And I am a serious Linux n00b -- I likely shouldn't even be playing around with it, or I might end up launching a missile in Idaho or something. :) 

Tom

[nesta...@gmail.com]

On Monday, January 14, 2013 7:11:50 AM UTC-7, shredhead wrote:

I just gave this another shot and so far it isn't working, meaning iTunes on my PC does not see the share. I don't have interest in using remote. The log entries I see make me thing it's still scanning through the contents of the directory I shared. But thjat can't be still happening since it's been a few days. Does the share show up when it's scanning or does it need to finish first?

I know a whole community of people who'd be very, very happy if forked-daapd ever works with iTunes. Don't waste your time with it. Please.