Phil Leigh;536874 Wrote: 
> It is frustrating but you need to understand that there are (at least) 2
> seperate problems, both of which only impact certain people based on
> THEIR specific combination of platform and music files. As such these
> bugs can be very hard to prevent (and quite hard to fix). 
> 
> They certainly weren't hit during beta AFAIK.
> 
> However, Andy has fixed the faad memory exception bug that was
> occasionally causing faad to crash on alac playback. The "Can't open
> file..." problem is different... 
> 
> I've been trying to help with this but I can never recreate this error
> on XP SP3 with 7.6. I've used example files sent by people with the
> problem and they all work fine on my system. 
> 
> At one point it looked like the alac files were possibly being
> misinterpreted as AAC (or MPEG-4 as SBS refers to them) and hence faad
> was not being invoked - the native AAC decoder was being invoked
> instead.
> 
> This won't work, hence the advice to check your file types to ensure
> that MPEG-4 is set to stream as FLAC via faad (same as "Apple
> Lossless".
> 
> If you turn on player.source logging you can see exactly what SBS is
> trying to do when you play a track...
> 
> This is NOT the default.
> 
> However, this is only a workaraound (if I'm correct about the alac
> files being wrongly identified as AAC).
> 
> There may also be a problem with the tags generated via iTunes, but I
> can't comment on that...I think some other folks have been looking at
> that.
My ALAC files arent being seen as ALAC, just MPEG-4 So it never even
hits the ALAC filetype. And it was trying to convert to AAC, which I
guess cant be done.
M


-- 
mcullinan
------------------------------------------------------------------------
mcullinan's Profile: http://forums.slimdevices.com/member.php?userid=37399
View this thread: http://forums.slimdevices.com/showthread.php?t=77511

_______________________________________________
Touch mailing list
Touch@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/touch

Reply via email to