But it is unexpected. What did I do?
- 1. I changed the audio transcoding a little bit: ffmpeg -i %s -acodec libmp3lame -b 192k -h mp3 -
2. Earlier I replaced the ffmpeg.exe & the lame.exe inside the \transcoding directory with the most recent release (Subsonic played happily after that!)
3. I exchanged the existing lame.exe and the lame_enc.dll for the most recent ones, both in \WINDOWS and in \WINDOWS\system32
4. After everything stopped playing - external player with m3u and internal player - I reversed the alterations, and everything in Windows is back to the old files
5. I also reversed the changes in the transcoding string, with no result. It is now back at the string above
6. Of course I rebooted or stopped Subsonic and restarted the service after every alteration
What visually happens, is that when I hit 'Play All', the speaker icon jumps erratically to track number one or two, and then, after about 10 seconds, ends at the last track, without a sound. The m3u file is sent to the player, the player sees the file, and tells me that it is starting playing Subsonic at 192 kbps MP3. But it never produces any sound. After some time there is a popup telling me that there is a corrupted file. Significant is that that also happened earlier with some (very few) files.
EDIT: I changed the switch -h back to the -f switch, and now everything (with or without LAME) working like before. The -h switch should result in a better quality, but maybe it is not fast enough to be used in 'on the fly' coding. Thanks for your response Gary!
The string I am using now: ffmpeg -i %s -acodec libmp3lame -ab 192k -f mp3 - - meaning that I am using LAME within FFMPEG.
It would be good to know the exact meaning and use of the switches. Why to use LAME within FFMPEG (see: http://sourceforge.net/apps/mediawiki/subsonic/index.php?title=Transcoders#Transcoding_to_MP3?
Who wants to write a tutorial or edit the Sourceforge/Subsonic wiki?
http://lame.sourceforge.net/
http://ffmpeg.org/
PB
