ralphpnj wrote:
> All versions of the Transporter absolutely support, i.e. play,
> 24bit/88.2kHz flac and wav files. The problem could be with the support
> for m4a/alac files.
Ahh !
Relax to playback of an arcane format. Welcome to the Bene Gesserit !
Life
--
ralphpnj wrote:
> All versions of the Transporter absolutely support, i.e. play,
> 24bit/88.2kHz flac and wav files. The problem could be with the support
> for m4a/alac files.
Indeed.
The transcoding path from alac to flac is via faad.exe (alac to wav) and
then sox.exe (wav to flac), and whil
And SoX and Flac support almost any rate so faad or some of the
convert,conf settings or other conversion logic in lms .
However it could behave wierd if try to convert to pcm instead of the
default flac ?
Mnyb's Profile:
bhaagensen wrote:
> TP supports 88, so problem must be elsewhere.
All versions of the Transporter absolutely support, i.e. play,
24bit/88.2kHz flac and wav files. The problem could be with the support
for m4a/alac files.
TP supports 88, so problem must be elsewhere.
bhaagensen's Profile: http://forums.slimdevices.com/member.php?userid=7418
View this thread: http://forums.slimdevices.com/showthread.php?t=97142
__
Could be that 88 kHz is not supported. I think I remember something like
that from iPeng testing.
I think the Touch supports it.
Doesn't the server transcode? Or are you trying to drive the Transporter
directly somehow?
p
Mnyb wrote:
> I found one bug in bugzilla, related to faad and path length .
>
> http://bugs.slimdevices.com/show_bug.cgi?id=16319
Thanks for the feedback; but this is not the issue; reducing the file
path+name length does not resolve the problem.
I suspect the issue is either because faad.exe
