PDA

View Full Version : I'm pissed and disappointed in SD



bflatmajor
2006-11-21, 19:48
I've logged a bug into the bug system.
I even called the support desk and talked to a live person regarding the issue that I have streaming an internet radio.

First some background.

I was able to stream the same url and a similar one in version 5.?? and 6.0. The urls stopped working during one of the many nightlies of 6.0 and still isn't working in 6.5.1.

Now the reason I'm pissed at SD;

After logging the bug and talking to their support people I get an email or two, telling me that the issue is a duplicate and that I should use the same fix that I mentioned in my comment of the duplicate. I figure dummy me!! I Forgot that I did figure it out the last time. So I attempted to do exactly what I said in the comment I posted.

Did it work? NO!!
Am I pissed that it didn't work? No

I'm PISSED because tech support was too lazy to test the so-called fix before they emailed me telling me it was a dupe of another issue and for me to do what I said I did when I originally posted the bug many months ago.

People, SD et all, this is basic functionality. If it didn't work in the beginning I would never have purchased the hardware.

This is very poor customer service and they need to get their act together. I've worked in the tech industry for over 20 years, developer and account manager and what just happened is totally unacceptable.

I know people are dying in Iraq and this is a minor issue when compared with other things in the world, but please don't send me an email telling me to do something that doesn't work and it hasn't been tested.

Enough...

Flame me if you must/desire

kdf
2006-11-21, 22:00
Quoting bflatmajor <bflatmajor.2hnkxb1164163801 (AT) no-mx (DOT) forums.slimdevices.com>:

> After logging the bug and talking to their support people I get an
> email or two, telling me that the issue is a duplicate and that I
> should use the same fix that I mentioned in my comment of the
> duplicate. I figure dummy me!! I Forgot that I did figure it out the
> last time. So I attempted to do exactly what I said in the comment I
> posted.
>

It wasn't tech support, it was me. It was YOUR comment saying a
solution was found for a similar URL. I also said that if it didn't
work, please leave a comment.

It isn't lazy, it is simply asking for more details and collecting the
data where it belongs so that the issue isn't diluted and prevents a
proper solution.

I'm sorry you feel snubbed.

-kdf

bflatmajor
2006-11-21, 22:15
Once again KDF, You and I tend to disagree regarding a bug.

so be it

kdf
2006-11-21, 23:13
Then please feel free to reopen and leave a comment explaining why you feel that is it NOT the mms streaming issue. At the very least, make note that your own suggested workaround no longer works.

Disagree all you want, but fuming about it doesn't get anything closer to working. d_source, d_http_async, d_remotestream and d_directstream logs just might.

Your other option is to contact support@slimdevices.com and get them to open a support ticket on it. Then someone there will be trying to reproduce it as well.

You have the tools. Use them as you see fit.
-kdf

slimpy
2006-11-22, 04:50
Maybe SD can be held responsible for the deaths in Iraq, too ;)

At least you could provide links to the relevant bugs and the URLs of your problem streams.
It would make you look less like a troll...

-s.

bpa
2006-11-22, 05:14
Here is the problem analysed and posted in another thread. It's been logged as bug for ages but nobody has voted to cure it and so it lingers.

I'm not interested in it per se but I felt analysing it would help.

http://forums.slimdevices.com/showpost.php?p=156398&postcount=16

kdf
2006-11-22, 09:28
Quoting slimpy <slimpy.2hoa5n1164196501 (AT) no-mx (DOT) forums.slimdevices.com>:

>
> Maybe SD can be held responsible for the deaths in Iraq, too ;)
>
> At least you could provide links to the relevant bugs and the URLs of
> your problem streams.
> It would make you look less like a troll...

http://bugs.slimdevices.com/show_bug.cgi?id=3383

and

http://bugs.slimdevices.com/show_bug.cgi?id=4522

not so much trolling, just upset. I can only guess this is because
the second bug was merged with a bug marked as "future". This doesn't
mean it's being pushed aside. I just means it doesn't have a specific
version target. If bpa's analysis can lead to a fix, it could be in
much sooner than 7.0.

I noted that it was my actions that marked it as a dupe, assuming
perhaps mistakenly that the two jazztrax urls are similar streams. I
also took the comment as a viable workaround and something bflatmajor
would be willing to do, is it was his own comment that appeared to
suggest that there was a workaround.

I'm still perfectly happy to see the second bug reopened if there is a
reasons for them to be kept discrete. The point of bugzilla is to
track bugs. If two issues are the same problem, tracking as a
combined issue keeps any data together. However, tracking two
distinctly different problems needs to be tracked separately. The
things that make them different are also critical.

The notes from bpa are helpful in that, at least to me, it shows why
the http streaming has failed. As I mentioned before, the mms only
streams are known to be a problem (hence why these got combined). One
possible solution worth investigating is to note that 404 error and
then try a transcoding option. This fallback-type function may also be
required for the few ogg decoder failures, but the infrastructure to
do this isn't in place yet. I'm currently in no position to help
beyond that as I don't have a working development system at the moment
(hard drive crash), not to mention an unfamiliarity with radio
streaming :)

Again, please vote and add any comments and/or details where possible
to bugzilla.
-kdf

bpa
2006-11-22, 10:03
The log of the error was done with WMA built-in disabled so I think checking for 404 and then trying transcoding won't work.

Also adding ":1755" at the end of the address to force SS to use port 1755 and not 80 which was OK as a workaround in 6.2, doesn't work in 6.5 with SS unable to understand the HTTP response.