transcoding

[Jason Holtzapple]

I have a question about transcoding in 5.0. I don't see the options in the
settings web pages any more about turning transcoding on for the
various formats.

Is transcoding controlled entirely in convert.conf, by the transcode-*
entries in the pref file, or both?

Thanks
--Jason

__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/

[dean]

Yes, those settings were made obsolete by the new transcode framework.

That said, a friendlier GUI for managing the transcode framework would
be most welcome.

On Nov 20, 2003, at 11:45 AM, Jason Holtzapple wrote:

> I have a question about transcoding in 5.0. I don't see the options in
> the
> settings web pages any more about turning transcoding on for the
> various formats.
>
> Is transcoding controlled entirely in convert.conf, by the transcode-*
> entries in the pref file, or both?
>
> Thanks
> --Jason
>
> __________________________________
> Do you Yahoo!?
> Free Pop-Up Blocker - Get it now
> http://companion.yahoo.com/
>

[michael]

Hello,

I was at work yesterday streaming from the new v5.0 server to my
software player (xmms) but the network was being a bit slower than
usual and I was getting a lot of skipping as a result. So I decided
that it was a good time to try out this transcoding/downsampling stuff
that's now in the server.

I essentially just uncommented the example in convert.conf and ended
up with this...
mp3 mp3 http *
$lame$ --silent --mp3input -b 96 $FILE$ -

After restarting the server (I'm assuming that's necessary) and
loading a playlist, I ran across a problem. The first song that I play
will transcode just fine. When the song ends, the player goes to
switch to the next song but then spins out of control, takes up 99% of
the cpu (lame is not running at this point), no sound comes out of the
player, and the status frame of the web page reloads continually
(rather than waiting the 30 or so seconds it usually does). If I hit
stop, everything goes back to normal. The server drops to 2% cpu
usage, and the web page responds normally. If I select a different
playlist, song etc, and hit play, the same thing will happen again.

Is there something I'm doing wrong on my end or is this a bug thats
been seen before?

Thanks,

-michael

[Kevin Deane-Freeman]

Quoting michael <michael (AT) fallenangel (DOT) com>:

> Is there something I'm doing wrong on my end or is this a bug thats
> been seen before?
its a bug. The flag to detect end of song gets skipped. It should be fixed in
the pre-release that Dean just posted.

Details about the refresh: Its default is 30s, but if the song end is less than
30s away, the refresh will set to the end of the song, to a minimum of 2s. This
bug, causes the time remaining to appear negative (it knows its past the end of
song, but missed the actual end in order to read the next song). This negative
result, sets the refresh to its minimum of 2s.

Check out the pre-release and you shoudl find it working better. Of course,
you'll need to edit the convert.conf again :)

-kdf

[michael]

Thanks for the info. Glad to hear it's not just me. :)

Unfortunately, this behaviour still seems to persist in
SlimServer_v2003-11-20.tar.gz
(I assume that's the pre-release you were referring to?)

-michael

Kevin Deane-Freeman <kevin (AT) deane-freeman (DOT) com> writes:
> Quoting michael <michael (AT) fallenangel (DOT) com>:
>
>> Is there something I'm doing wrong on my end or is this a bug thats
>> been seen before?
> its a bug. The flag to detect end of song gets skipped. It should be fixed in
> the pre-release that Dean just posted.
>
> Details about the refresh: Its default is 30s, but if the song end is less than
> 30s away, the refresh will set to the end of the song, to a minimum of 2s. This
> bug, causes the time remaining to appear negative (it knows its past the end of
> song, but missed the actual end in order to read the next song). This negative
> result, sets the refresh to its minimum of 2s.
>
> Check out the pre-release and you shoudl find it working better. Of course,
> you'll need to edit the convert.conf again :)
>
> -kdf

[Kevin Deane-Freeman]

Quoting michael <michael (AT) fallenangel (DOT) com>:

>
> Thanks for the info. Glad to hear it's not just me. :)
>
> Unfortunately, this behaviour still seems to persist in
> SlimServer_v2003-11-20.tar.gz
> (I assume that's the pre-release you were referring to?)

yes, that was it. The fix was held off a little longer :)
-kdf

[michael]

Kevin Deane-Freeman <kevin (AT) deane-freeman (DOT) com> writes:
> Quoting michael <michael (AT) fallenangel (DOT) com>:
>
>>
>> Thanks for the info. Glad to hear it's not just me. :)
>>
>> Unfortunately, this behaviour still seems to persist in
>> SlimServer_v2003-11-20.tar.gz
>> (I assume that's the pre-release you were referring to?)
>
> yes, that was it. The fix was held off a little longer :)
> -kdf

It looks like this fix made it into 2003-11-21
Thanks guys!

-michael