Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: [crashware] foo_input_mslive (Read 274772 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[crashware] foo_input_mslive

Reply #100 –
I've got another local radio station that won't work.
Code: [Select]
http://www.mainstreamnetwork.com/listen/dynamicuasx.asp?station=kjwl-fm

It works in WMP 10.00.00.4040, which is the version I have, but I can't get it to work in foobar.
Whenever I try to use the mslive:// address it either locks up or reports the error:
Code: [Select]
Unable to open item for playback (Failed to query IWMReaderAdvanced6 interface):
"mslive://http://www.mainstreamnetwork.com/listen/dynamicuasx.asp?station=kjwl-fm


Are there files I forgot to copy over into foobar's directory? Or am I doing something wrong? Any help would be greatly appreciated.

[crashware] foo_input_mslive

Reply #102 –
Hello,
I have problem with polish radio...

I've read all posts since last update, but I could't find any solution of my problem.

I have problems with this radio:
Code: [Select]
http://www.itvp.pl/i.tvp/radio/media/pr3/
wmp link: http://lokal.itvp.pl/asx/2/5/83.29.77.121.45c3766e669a88.19420225.asx


In foo none of them worked... [in wmp10 this links work correctly]...


Is there any chance to listen this radio in foo?

TIA.
Greetz.

[crashware] foo_input_mslive

Reply #103 –
For me, it helped copying files (below) from WM11 runtime (above) to foobar directory

Code: [Select]
wmasf.dll
wmvcore.dll

[crashware] foo_input_mslive

Reply #104 –
foo_input_mslive version 0.2 works well for me. Thanks!

[crashware] foo_input_mslive

Reply #105 –
Does rtsp://213.200.97.107/energynuernberg$livestream.wma work for anybody? I sniffed it of www.energy.de by using Ethereal.

Thanks Acropolis - anyway!

[crashware] foo_input_mslive

Reply #106 –
Quote from: .misiek on
Hello,
I have problem with polish radio...

I've read all posts since last update, but I could't find any solution of my problem.

I have problems with this radio:
Code: [Select]
http://www.itvp.pl/i.tvp/radio/media/pr3/
wmp link: http://lokal.itvp.pl/asx/2/5/83.29.77.121.45c3766e669a88.19420225.asx


In foo none of them worked... [in wmp10 this links work correctly]...


Is there any chance to listen this radio in foo?

I'll check as I update it, I've been fairly busy with other stuff at the moment.

Quote from: Chaser on
Does rtsp://213.200.97.107/energynuernberg$livestream.wma work for anybody? I sniffed it of www.energy.de by using Ethereal.

I just realise that even the rtsp:// is specified, if the wma decoder is first asked if supporting than mslive, foobar will ask the decoder to handle it, so it gives invalid path, I will try to find a workaround.

[crashware] foo_input_mslive

Reply #107 –
Chaser: Doesn't work!

[crashware] foo_input_mslive

Reply #108 –
Acropolis, thank you for working on it!

bye

[crashware] foo_input_mslive

Reply #109 –
Have you had time to take a look at it?

[crashware] foo_input_mslive

Reply #110 –
not yet.
the way of determinating if a url is asx or actual file gives me real headache...
also the default wma decoder will be used when the extension is wma, even the prefix is mms or mslive://

[crashware] foo_input_mslive

Reply #111 –
What about using one more workaround:

If a file has the extension wma use the prefix "mslive_wma_ext://" and enter the url without the extension ".wma" (the user has unfortunatelly to take care of this). Now your plugin can handle the entry because the default wma decoder won't recognise it as a wma-file. You have to internally add ".wma" to the path.

Is my concept worth the hassle?

[crashware] foo_input_mslive

Reply #112 –
this will work, but will produce some other problems, e.g. what if the extension is asf? another prefix? and how about wmv?
proabably the ultimate solution is to implement file system again, and use the default decoder, but this is not what I want

[crashware] foo_input_mslive

Reply #113 –
Maybe a more expierienced user like foosion or musicmusic could give us a hint, that leads us into the right direction?

[crashware] foo_input_mslive

Reply #114 –
maybe i'm blind, but i can NOT find a link to d/l this here or on your blog.

[crashware] foo_input_mslive

Reply #116 –
I don't know what exactly I did, but somewhere in the mix of:

Your component + streaming live windows media + pausing + standby + wi-fi

I got:
Quote
Unrecoverable playback error: bad allocation

after unpausing after restore from standby (it froze for a while too). Its not some thing I would expect to work, but error doesn't sound too good.

Also, any chance you could get seeking working if there is a buffer built up from pausing? I doubt it, but it would be nice

More also, I don't know whose fault it is, but its pretty annoying that it stops playing if you do try and seek (e.g. using keyboard).

bye
.

[crashware] foo_input_mslive

Reply #117 –
Quote from: Chaser on
Maybe a more expierienced user like foosion or musicmusic could give us a hint, that leads us into the right direction?

Use a custom protocol scheme and enclose the original path in pipe characters |, for example "mslive:|http://some.domain.com/a.wma|". foobar2000 treats | as path separator, so this will effectively make the combined path have an empty filename - and extension, which blocks recognition by extension. foo_random uses the same approach.

[crashware] foo_input_mslive

Reply #118 –
BTW, what are your plans now? I wasn't using the component any more, after the incompatibility with w2k/wmp9... Most important for me is, no matter if an asx or pls resolves to multiple locations, to have your component displaying only one entry because otherwise online radio playlists get messy very soon...

[crashware] foo_input_mslive

Reply #119 –
Quote from: musicmusic on
I don't know what exactly I did, but somewhere in the mix of:

Your component + streaming live windows media + pausing + standby + wi-fi

I got:
Quote
Unrecoverable playback error: bad allocation

after unpausing after restore from standby (it froze for a while too). Its not some thing I would expect to work, but error doesn't sound too good.

Also, any chance you could get seeking working if there is a buffer built up from pausing? I doubt it, but it would be nice

More also, I don't know whose fault it is, but its pretty annoying that it stops playing if you do try and seek (e.g. using keyboard).

I'm going to rewrite again, so for the moment I will ignore your playback error.
not possible to get seeking working because foobar only checks for if it's seekable for once.
it's strange that even I return false for can_seek(), foobar will not disable the seek bar, I'll check again while rewriting.

Quote from: foosion on
Quote from: Chaser on
Maybe a more expierienced user like foosion or musicmusic could give us a hint, that leads us into the right direction?

Use a custom protocol scheme and enclose the original path in pipe characters |, for example "mslive:|http://some.domain.com/a.wma|". foobar2000 treats | as path separator, so this will effectively make the combined path have an empty filename - and extension, which blocks recognition by extension. foo_random uses the same approach.

thanks so much, this is the solution I don't even know it's possible.

Quote from: Squeller on
BTW, what are your plans now? I wasn't using the component any more, after the incompatibility with w2k/wmp9... Most important for me is, no matter if an asx or pls resolves to multiple locations, to have your component displaying only one entry because otherwise online radio playlists get messy very soon...

I'll rewrite, it will still use cue sheet approach, but this time it will only show the entries in the root asx, recursive entries will be handled internally.

[crashware] foo_input_mslive

Reply #120 –
I just upload a beta version of mslive 0.3, you can try it out (yes, no more WMP11, but VC8 SP1 runtime libraries needed):

location syntax:
mslive://|http://www.abc.com/stream.asx|/
mslive://|http://www.abc.com/stream.asx|list|/

mslive://|http://www.abc.com/stream.wma|/
mslive://|http://www.abc.com/stream.wma|live|/

"list" and "live" are to override the type, in case mslive can't determine if it's asx or actual stream.

e.g. mslive://|www.abc.com/stream.wma|list|/
this can make mslive try to load the file as asx playlist, but in fact mslive will try to load it as asx if it cannot play it.

for mms and rtsp you can still just type the url without anything added:
e.g. mms://www.abc.com/1.wma

[crashware] foo_input_mslive

Reply #121 –
Quote from: Acropolis on
location syntax:
mslive://|http://www.abc.com/stream.asx|/
mslive://|http://www.abc.com/stream.asx|list|/


Thanks Acropolis, I'll test it. Can't you make you component parse the location and insert the "|" by itself, so that the user has only put mslive:// at front of the location? This would be more user friendly I think.

[crashware] foo_input_mslive

Reply #122 –
Quote from: Acropolis on
location syntax:
mslive://|http://www.abc.com/stream.asx|/
mslive://|http://www.abc.com/stream.asx|list|/

mslive://|http://www.abc.com/stream.wma|/
mslive://|http://www.abc.com/stream.wma|live|/

General safety hint to everyone considering this approach: Be careful with multiple segments separated by | if you ever use this idea for local files. The pipe character is also used as delimiter in unpack:// URLs, so finding the next pipe character wouldn't be a good idea there. As long as you process the prefix and postfix of an URL, you should be safe.

In the context of foo_input_mslive you should be safe unless MS introduces zipped streams.

[crashware] foo_input_mslive

Reply #123 –
Quote from: Squeller on
Quote from: Acropolis on
location syntax:
mslive://|http://www.abc.com/stream.asx|/
mslive://|http://www.abc.com/stream.asx|list|/


Thanks Acropolis, I'll test it. Can't you make you component parse the location and insert the "|" by itself, so that the user has only put mslive:// at front of the location? This would be more user friendly I think.

this approach is to avoid foobar using other input components to handle the stream/asx, if you read the previous posts, you'll know the problem. it's not for identifying as "a mslive syntax", it's just force foobar to use mslive.

for local *.asx, you don't need to put in the location, just drag and drop.