PDA

View Full Version : AlienBBC, mplayer, Napster & SB1 ?



ijwoo1
2009-05-07, 13:38
I've tried searching for answers but I'm guessing there are not too many of us left running SB1 and even less that want to stream Napster to it:)

As per the title, should I be able to play Napster streams on an SB1 ?

I'm assuming that it would require AlienBBC with mplayer with an appropriate convert.conf file to transcode the WMA stream on the fly to MP3 or FLAC ?

I can play Deezer, BBC streams and other internet streams but not Napster. No matter what I do I always get an "invalid credentials" message.

I have set up my napster account in Squeeze network, I can browse my personal Napster library on the SB1, so I know the credentials are correctly set up but it refuses to play any tracks.

Is there a fundamental incompatibility or just incompetence on my part ?

I should also say that I'm running Squeezecenter 7.3.3 on a Synology DS NAS using SSODS - is the fact I'm not running windows the problem ?

Tks

mmca22gr
2009-07-24, 14:16
not just you. I wish to do the same and I get the same problems running 7.3.3 on a Windows box. Did you solve it?

bpa
2009-07-24, 14:27
No matter what I do I always get an "invalid credentials" message.


Softsqueeze users get this same message and apparently on Softsqueeze if "play" is pressed again, napster plays.

Softsqueeze is similar to an SB1 in that it cannot play WMA natively and it needs on Linux & OSX mplayer for WMA.

The other setting which Softsqueeze needs is "proxied streaming " in WebUI Player/Audio settings.

mmca22gr
2009-07-25, 09:21
Thanks BPA,
Pressing play twice only skips to next song, withe the same 'invalid credentials' message.
But with SB1 the proxied streaming is not an available option. I have no problems with the BBC iPlayer streams.

slimhase
2010-03-06, 11:23
Softsqueeze users get this same message and apparently on Softsqueeze if "play" is pressed again, napster plays.

Softsqueeze is similar to an SB1 in that it cannot play WMA natively and it needs on Linux & OSX mplayer for WMA.

The other setting which Softsqueeze needs is "proxied streaming " in WebUI Player/Audio settings.

Hello bpa; I am pulling my hair out. I am trying to be able to get BBC or NPR streams to run on my SLIMP3 (or Squeezeplay). No luck. (Everything is fine on my SB3 / Classic), so some issue w/ transcoding.

This is where I am:
I installed mplayer into SSODS (w/ FlipFlips help, I think it runs now).
BUT: What do I need to do w/ the convert.conf file to make the system understand that I need to convert WMA to MP3?

(I tried the http://wiki.slimdevices.com/index.php/WMA listed method, but that did not work - it should convert anyhow to WAV - which SLIMP3 can not read....)

My error message is always this (or similar):
0071: [10-03-06 19:05:44.0764] Slim::Player::Song::open (404) Error: Couldn't create command line for wma playback for [mms://wm.npr.org/wm.npr.na-central/npr/asc/2010/03/20100301_asc_wholeshow.wma?v1st=1EB3D94AA30899EC&mt=7]


Any help appreciated!!

Thanks and regards, Heiner

bpa
2010-03-06, 11:32
You have not given any info on your SBS server such as SBS/SC version, SSODS version, NAS model and processor type - SSODS is a special system and SSODS 4 omitted some plugins.

If mplayer is installed - then I suggest leave any conf file as distributed and install playWMA plugin.

slimhase
2010-03-06, 11:47
You have not given any info on your SBS server such as SBS/SC version, SSODS version, NAS model and processor type - SSODS is a special system and SSODS 4 omitted some plugins.

If mplayer is installed - then I suggest leave any conf file as distributed and install playWMA plugin.


Thanks for the quick reply. My system:
SS7.4.2 on SSODS 4.6 on Diskstation DS207+ (arm processor).
Meanwhile I found your other thead and I installed playWMA plugin.
Still, my system does not play the streams.
The error file looks like this:
0115: /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/PlayWMA/Bin/wmamplayer.sh: /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/PlayWMA/Bin/wmamplayer.sh: 32: echo: not found
0114: /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/PlayWMA/Bin/wmamplayer.sh: /opt/ssods4/var/home/SqueezeboxServer/Cache/InstalledPlugins/Plugins/PlayWMA/Bin/wmamplayer.sh: 37: [: not found

Error on Squeezeplay says:
Problem: Can't open file for...

Maybe, the install of mplayer did not work? How can I find out?
(I also have to say that I am really not an linux expert to say the least.....)
Thanks again - any help appreicated!

Regards, Heiner

bpa
2010-03-06, 12:46
Is lame installed ?

Check the WebUI Settings/Advancec/Filetypes for Windows Media.

For SLiMP3 you need the WMA->MP3 settings - is it enabled ?

If not then is lame installed ?

slimhase
2010-03-06, 13:10
Is lame installed ?

Check the WebUI Settings/Advancec/Filetypes for Windows Media.

For SLiMP3 you need the WMA->MP3 settings - is it enabled ?

If not then is lame installed ?

Hi bpa;
yes, lame is installed, as it is part of the SSODS package & FlipFlip confirmed it.
SS says under player settings: "The LAME encoder appears to be installed correctly on your system."

Regarding mplayer: It is also installed - this is what your plugin (Play Windows Media) says to that:

"MPlayer
PlayWMA requires mplayer to play real audio streams.
For Mac and Linux/Unix platforms you will need to install MPlayer yourself.
Installed"

As for WMA -> MP3, it says WMAmplayer.sh/lame in the settings.

Note: I also tried to change wmamplayer.sh to pinpoint it to the install location of mplayer. So I changed the following:
....
elif [ -x /usr/local/bin/mplayer ] ; then
app=/usr/local/bin/mplayer
...
to:
...
elif [ -x /volume1/SSODS4/bin/mplayer ] ; then
app=/volume/SSODS4/bin/mplayer
...

Would that be ok? It did not help, though.

Here is the related error log:
0071: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 32: echo: not found
0070: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 37: [: not found
0069: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 23: echo: not found
0068: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 21: [: not found
0067: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 15: [: not found
0066: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 32: echo: not found
0065: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 37: [: not found
0064: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 23: echo: not found
0063: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 21: [: not found
0062: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 15: [: not found
0061: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 32: echo: not found
0060: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 37: [: not found
0059: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 23: echo: not found
0058: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 21: [: not found
0057: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 15: [: not found
0056: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 37: [: not found
0055: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 32: echo: not found
0054: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 23: echo: not found
0053: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 21: [: not found
0052: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 15: [: not found
0051: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 37: [: not found
0050: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 32: echo: not found
0049: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 23: echo: not found
0048: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 21: [: not found
0047: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 15: [: not found
0046: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 32: echo: not found
0045: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 37: [: not found
0044: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 23: echo: not found
0043: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 21: [: not found
0042: /opt/ssods4/bin/wmamplayer.sh: /opt/ssods4/bin/wmamplayer.sh: 15: [: not found


Thanks again for your help.

Regards, Heiner

bpa
2010-03-06, 13:43
A few years ago the version of Linux on Synology was missing some standard features so that flipflip had built a special version of mplayer and also modified the AlienBBC mplayer.sh and custom-conver.conf file to make them work.

I think you should contact fliflip and find out if these changes are still necessary. If they are you will need to make similar modification to conf and possible the wmaplayer.sh file.

slimhase
2010-03-06, 14:41
A few years ago the version of Linux on Synology was missing some standard features so that flipflip had built a special version of mplayer and also modified the AlienBBC mplayer.sh and custom-conver.conf file to make them work.

I think you should contact fliflip and find out if these changes are still necessary. If they are you will need to make similar modification to conf and possible the wmaplayer.sh file.

Thank you, bpa! I finally got it to work w/ FlipFlips and your help!

UPDATE:

Doh!
Well, not quite...
While I got it to work for Squeezeplay, my dear old SLIMP3 'plays' only some sort of a white noise (sounds similar to a detuned radio).

All other streams still work fine.

Any ideas?

Thanks again for your help!

Heiner

slimhase
2010-03-07, 04:02
Thank you, bpa! I finally got it to work w/ FlipFlips and your help!

UPDATE:

Doh!
Well, not quite...
While I got it to work for Squeezeplay, my dear old SLIMP3 'plays' only some sort of a white noise (sounds similar to a detuned radio).

All other streams still work fine.

Any ideas?

Thanks again for your help!

Heiner

Hello BPA
Maybe another input to help to identify the root cause:

When I play the WMA stream on squeezeplay, I see under more info:
"Bitrate 64kps CBR (converted to 705.6kps ABR)"

When I play the WMA stream on SLIMP3, I see under more info:
"Bitrate 64kps CBR (converted to 320kps ABR)"

No errors shows in the Server Log

Again; any help is greatly appreciated!

Thanks and regards, Heiner

bpa
2010-03-07, 05:30
Maybe another input to help to identify the root cause:

When I play the WMA stream on squeezeplay, I see under more info:
"Bitrate 64kps CBR (converted to 705.6kps ABR)"

When I play the WMA stream on SLIMP3, I see under more info:
"Bitrate 64kps CBR (converted to 320kps ABR)"


Root cause of what ?

slimhase
2010-03-07, 07:01
Root cause of what ?

The root cause of the slimp3 still not playing WMA streams, but giving white noise instead of Audio

Regrads, Heiner

bpa
2010-03-07, 11:33
What version of lame are you using ?

slimhase
2010-03-13, 08:26
What version of lame are you using ?

I am not sure - it is the version which came w/ FlipFlip latest SSODS install (4.6).
Can you point me somewere?
I susect that is has something to do w/ the bitrate it is using when converting the stream.

This is the string used in custom-convert.conf:
wma mp3 * *
# FR
[mplayer] -really-quiet -vc null -vo null -cache 128 -af volume=0,resample=44100:0:1,channels=2 -ao pcm:nowaveheader:file=- $FILE$ | [lame] --silent -r -x -q $QUALITY$ -b $BITRATE$ - - 2>/dev/null


Thanks for your help!
Heiner

bpa
2010-03-13, 09:59
Try removing the "-x" after "[lame]", restart SBS and test.

Lame had a bug where the use of "-x" was incorrect and it was changed between version 3.96 and 3.97 or 3.98.

slimhase
2010-03-13, 16:47
Try removing the "-x" after "[lame]", restart SBS and test.
Lame had a bug where the use of "-x" was incorrect and it was changed between version 3.96 and 3.97 or 3.98.
BPA, you are the MAN!
Thank you - deleting the "-x" worked! No more white noise, but an actual stream!
Thank you so much!

However, still a problem remains:
The system keeps rebuffering - no steady stream possible. (this does not happen on the squeezeplay - only on the SLIMP3.
Do you have any idea why this is?
A question potentially be related:
Why is an original 20kbps converted to a 320kbps stream (even when I limit the bitrte to 64kbps in the Audio Player settings??
Is there a way to reduce the converted bitrate?

Thanks again for your help!!

Heiner

bpa
2010-03-13, 16:55
For SliMP3 with mplayer - I think the workaround is to always use a "-b 64" and not $BITRATE$

If you have other players then you should have a special line in the conf file for Slimp3 class of players as well the standard one.

slimhase
2010-03-13, 23:53
For SliMP3 with mplayer - I think the workaround is to always use a "-b 64" and not $BITRATE$

If you have other players then you should have a special line in the conf file for Slimp3 class of players as well the standard one.

Hello BPA:
thanks again for your help!
Unfortunately, the problem persists - SLIMP3 keeps rebuffering and it converts to 320kbps

This is how I implemented your suggestion in my custom-convert.conf
Is this correctly implemented?

wma mp3 * *
# FR
[mplayer] -really-quiet -vc null -vo null -cache 128 -af volume=0,resample=44100:0:1,channels=2 -ao pcm:nowaveheader:file=- $FILE$ | [lame] --silent -r -q $QUALITY$ -b $BITRATE$ - - 2>/dev/null

wma mp3 slimp3 *
# FR
[mplayer] -really-quiet -vc null -vo null -cache 128 -af volume=0,resample=44100:0:1,channels=2 -ao pcm:nowaveheader:file=- $FILE$ | [lame] --silent -r -q $QUALITY$ -b "-b 64" - - 2>/dev/null

Thanks again;
Heiner

P.S. I also tried
... -q $QUALITY$ -b 64 - - 2>/dev/null
instead of
... -q $QUALITY$ -b "-b 64" - - 2>/dev/null

with the same neg. outcome....

bpa
2010-03-14, 02:03
I cannot help anymore as this worked for other users of SliMP3 and I don't have a SliMP3 to test.

Please do some reading and try to understand what the files are about as if you want to do more experiments to find correct settings.



Unfortunately, the problem persists - SLIMP3 keeps rebuffering and it converts to 320kbps

This means you changes are not working - either the conf file is not the file being user, it is syntactically incorrect or you have not restarted SBS (i.e stop SBS totally. make sure your conf file is changed and saved and editor closed before restarting SBS).

Read the lame documentation to see what is valid - Use
-b 64

the following is not valid
-b "-b 64"

Get it working with the standard conf file lines before trying adding a new one with "slimp3". When trying to solve a problem making two changes at the same time is never a good idea.

slimhase
2010-03-14, 05:54
I cannot help anymore as this worked for other users of SliMP3 and I don't have a SliMP3 to test.

Please do some reading and try to understand what the files are about as if you want to do more experiments to find correct settings.


This means you changes are not working - either the conf file is not the file being user, it is syntactically incorrect or you have not restarted SBS (i.e stop SBS totally. make sure your conf file is changed and saved and editor closed before restarting SBS).

Read the lame documentation to see what is valid - Use
-b 64

the following is not valid
-b "-b 64"

Get it working with the standard conf file lines before trying adding a new one with "slimp3". When trying to solve a problem making two changes at the same time is never a good idea.

Thanks, BPA.
I will partition the problem and get in contact again, when I isolated the problem better.
(But so far, I am sure that the line I added is used, since removing the -x did the trick to at least get rid of the white noise - after restarting SBS)
Thanks again and have a good day,
Heiner

Anto
2010-09-29, 08:02
MelodyCan is the next generation easy-to-use software that converts just about any video and audio file that can be played on your computer.
Extremely fast conversion speed and simple user interface.