Hi, Julien.
On 13/10/2008, at 07:30, Julien BLACHE wrote:
Rogério Brito <[EMAIL PROTECTED]> wrote:
Perhaps it should be documented. The documentation shouldn't
assume that
all users are extremely dumb. This is a Microsoft-esque thing.
I'd rather have people send a log at level 9 before they send one at
level 10. 10 is very verbose (the level is called L_SPAM ...) and
makes very large logs that are difficult to read.
Yes, I read that in the code. :-) Funny thing.
Perhaps we can refactor it a little bit.
Done already, as I wrote in the previous mail :)
Nice. :-)
I will perhaps try asking debian-legal if writing just a *tag*
would be
acceptable or not.
You should check what libmp4v does for real and see what can be done
from here. I haven't looked into it in details, just using a local
build for gtkpod for my iPod.
Perhaps I didn't expressed myself clearly. I was thinking of
including just the needed files from libmp4v2 to easytag's diff.gz
(as a patch). It seems to me (IIRC), that there's one header that
needs to be included, but the core of the functionality is already
enabled in easytag.
I'd need a log snippet when you're trying to read an AAC file.
The log
you sent only contains the startup :)
Ok, sending it again. This time trying to play an iTunes generated
AAC
file.
OK, so the log tells that it's working fine. The file is being
streamed to the client just fine, with a content-type of audio/m4a
Emitting reponse header Content-Type: audio/m4a
I'm afraid you have a player FAIL here, and not a server FAIL ;)
No, I read the log before I sent it to you and the behaviour that I
see is that mt-daapd sends the *whole* file at once, *before* the
player even plays a second of it.
Tested with rhythmbox (with gstreamer back-end), with amarok (with
xine back-end), and with iTunes proper. Neither of these worked.
If you can send make the file available somewhere, I'd try playing it
on my SoundBridge. It's playing my m4a files just fine.
Right. We can talk about this in private in e-mail.
P.S.: Did you get the manpage that I wrote for mt-daapd? I'm not
sure if
all my mails are getting through. :-(
Yep. I'll rework it somewhat
Does it need any major surgery? :-) At least it is a good start, I
think. :-)
and include it in an upload later today,
together with the AAC scanning patch, so you can try that out and tell
me how it goes.
Quite nice.
(mt-daapd -f -d 9 -D scan for that purpose, if
scanning fails on one or more files, do it again with -d 10 and send
me the log snippet for that particular file)
OK with me. (Even though I don't seem to think that the problem is
scanning, or doesn't seem to be, based on the fact that the files are
all sent immediately to the client).
Regards, Rogério Brito.
--
Rogério Brito : [EMAIL PROTECTED],ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
