Subsonic Forum

This is more of a verification thing than anything else really. I am suspicious that subsonic is not transcoding. I have subsonic installed from the standalone version with SUBSONIC_HOME here:

/usr/local/subsonic

The Lame binary is here:

/usr/local/subsonic/transcode

I have made a soft link to SUBSONIC_HOME here:

/var/subsonic

That last was done just to try to get it to recognize that lame is available. It always displays the warning "Lame does not seem to be installed" beside the max bit rate selector. Additionally, when I play a song (nothing I have is lower than 128K and I have it set lower than that for each user) I never see a lame process fire off on the server.

I have checked the logs and there is nothing in there at all about transcoding... either failures or success or debug messages.

Any suggestions on how to verify that it is actually transcoding is working? The system transcodes pretty fast (15+- seconds for a high bit rate average length song) but I can type "ps -eaf | grep -i lame" a lot faster than that. I can't imagine that I'm missing it. However, since I suspect it isn't running lame (convinced actually) and I don't see any error messages in the logs I am lost.

P

it says "starting transcoder xxx..." in log if it does (attempt) to transcode, so somethings not right here...

how do you run subsonic? maybe subsonic gets its working directory mixed up the way you start it, and sees no transcoding-folder?

please post how you start up subsonic, since I had a similar problem maybe i could offer some help here.

Subsonic in: /usr/local/subsonic/ (we will call this SUBSONIC_HOME)
Standalone files in: /usr/local/subsonic/standalone/

Started with this at boot time:

su web -c "/usr/local/subsonic/standalone/subsonic.sh"

The folder SUBSONIC_HOME is owned by the user "web". My server binds to port 8080. The log files "subsonic.log" and "subsonic_sh.log" show up in SUBSONIC_HOME. The "db", "thumbs", and "jetty" folders are created in SUBSONIC_HOME.

I've played around with jinzora and just transcoding from the command line and both use lame just fine, even as the web user. The fact that I'm seeing no transcoding messages in the

Okay. A little more poking around has solved the problem. At some point I was trying to get it working and in the "Advanced" part of the settings I had put the full path to where lame normally resides "/usr/local/bin/lame". Evidently that doesn't work well... at least how I did it. I took off the path element and left just the command. It seems to be transcoding now and the warning message about missing lame is gone.

Thanks for checking it out. Your post got me thinking.

P