Bugzilla – Bug 3181
Not playing url - MMS only stream
Last modified: 2009-09-08 09:28:27 UTC
I've gone through this before and now it's back again. I can not play the url that is listed below. I can play the url when I'm using version 6.1.1. Now I'm on 6.2.2 with firmware version 35 and it does not work AGAIN. Can someone please fix this once and for all. mms://69.43.137.40/jazztrax060319h1.wma Thank you
Any information on this issue? (In reply to comment #0) > I've gone through this before and now it's back again. > I can not play the url that is listed below. > I can play the url when I'm using version 6.1.1. > Now I'm on 6.2.2 with firmware version 35 and it does not work AGAIN. > Can someone please fix this once and for all. > mms://69.43.137.40/jazztrax060319h1.wma > Thank you
2006-03-24 08:35:56.4604 Song queue is now 0 2006-03-24 08:35:56.4611 00:04:20:05:aa:bb: Switching to mode play from stop 2006-03-24 08:35:56.4618 openSong on: mms://69.43.137.40/jazztrax060319h1.wma 2006-03-24 08:35:56.4783 00:04:20:05:aa:bb New play mode: play 2006-03-24 08:35:56.4803 This player supports direct streaming for mms://69.43.137.40/jazztrax060319h1.wma as mms://69.43.137.40/jazztrax060319h1.wma, let's do it. 2006-03-24 08:35:56.4814 setting up direct stream (1160481064:80) autostart: 3. 2006-03-24 08:35:56.4816 request string: GET /jazztrax060319h1.wma HTTP/1.0 Accept: */* User-Agent: NSPlayer/4.1.0.3856 Host: 69.43.137.40 Pragma: xClientGUID={7347a8a6-5345-25ce-6464-1d4b21b6647b} Pragma: no-cache,rate=1.0000000,stream-time=0,stream-offset=0:0,request-context=1,max-duration=0 Connection: Close 2006-03-24 08:35:56.4836 00:04:20:05:aa:bb: Current playmode: play 2006-03-24 08:35:56.6761 processing headers for direct streaming 2006-03-24 08:35:56.6767 $VAR1 = 'HTTP/1.1 404 Object Not Found Server: Microsoft-IIS/5.0 Date: Fri, 24 Mar 2006 16:47:29 GMT Content-Length: 3243 Content-Type: text/html '; "Not Found" would seem to be an interesting problem...
any idea when this bug will fixed in a nightly release?
It appears that this service does not support HTTP streaming of Windows Media on their server, something that's used in the new versions of slimserver and squeezebox software. Who is the provider? Is it possible to contact them and ask them to enable this on their streaming server? As a workaround, you can disable "Windows Media (built-in)" under Server Settings -> File Types.
Subject: Re: Not playing url Interesting, This same url works on 6.1.1 if you go to the website www.jazztrax.com and click on their weekly syndicated show line at the top of the page and then click on the On Demand icon after you get the new page, it will display other mms: links that play their music. So how can it work in one version but not in the next version of your software? Also, i've disabled the "Windows Media (built-in)", as you suggested and it still doesn't work. Please help. Thank you Quoting Slim Devices Bugzilla <bugs@bugs.slimdevices.com>: > https://bugs-archive.lyrion.org/show_bug.cgi?id=3181 > > > > > > ------- Comment #4 from dean@slimdevices.com 2006-03-26 14:56 ------- > It appears that this service does not support HTTP streaming of Windows Media > on their server, something that's used in the new versions of slimserver and > squeezebox software. > > Who is the provider? Is it possible to contact them and ask them to enable > this on their streaming server? > > As a workaround, you can disable "Windows Media (built-in)" under Server > Settings -> File Types. > > > > > ------- You are receiving this mail because: ------- > You are a voter for the bug, or are watching someone who is. > You reported the bug, or are watching the reporter. >
Any idea when this will be fixed?
Can someone provide me with a timeframe on when the bug that I reported will be fixed. Is it being looked into or has it been deemed 'not important'? I could go back to 6.1.1 but I would like a stable product at 6.2.2 and I promised not use the nightlies.
please try to refrain from 'nagging' all problems are important, and fixes come when they come. the question has been asked, and review will come when it comes. Please appreciate that while they appear simple, none of the above solutions are immediately so. Care must be taken not to break anything else and make sure it is the proper solution going forware. Every user has important issues, and you are not being ignored. We ALL want a stable 6.2.2 product, and your patience is appreciated.
I don�t consider me saying that my problem is important as nagging. Anytime a product is developed with basic functionality and then that product is upgraded and that functionality disappears, normally the company puts out a statement saying that the functionality is no longer being supported or a hot fix is put in place. It works in 6.1.1 but not in any version after that. Not responding with an estimated time to fix the problem or responding with a �sometime in the future� is not good business. I understand bugs in software and I understand the entire development life cycle, I work in the industry as a software engineer. All I was seeking was an estimate of time from someone who knows what is going on. So, can someone who knows when this issue will be addressed, please let me know.
my point is that asking every 3 days for a status, is not going to get an answer any sooner. All bugs are being worked on, and when there is a change in status, or anything to update, you will see it here and recieve a notice in your email. There is no need to add more to already full inboxes to ask a question that can only be answered as I am now: "we're working on it". When someone knows more, they will post something.
The problem you are experiencing would seem to be due to the native wma decoding, put in place for 6.2.1. Streaming IS supported, but as reported in earlier comments, http streaming. By disabling the "built-in" wma, it reverts to the same method that is used for 6.1.1. The fact that this doesn't work, is odd to say the least. Being odd, the solution isn't so simple. Now, I wouldn't recommend the pain of going back and forth to 6.1.1, but I would recommend taking a look at the log using d_http and d_source just to be sure that the url is getting recieved properly and that the playback is using the right transcoding. btw, for me, even WMP is saying it cannot find the stream. I really don't know how to test or repair a stream that is not found. Given this state, no matter how important or how much I may want to try and help with this one, there is nothing else I can offer. Rest assured, however, that everyone is doing the best that they can.
Marvin - you're right - we regressed this functionality. I've just checked in a work around as change 6985. You will need to disable WMA built-in under Settings -> File Types. These changes will be in the 2006-04-20 build.