Trouble with the 48kbps aac+ Subscriber Stream

[Xestrix]

As per the topic title, I've been having some serious issues with the aac+ stream lately

This is my choice listening format, but I've had to switch the the 128kbps mp3 stream the last few days.

Starting about a week ago, the aac+ stream would buffer for about 30 minutes before playing normally, if the stream was stopped and restarted, another 30 minutes had to be waited out before the stream took off again.

Tonight I decided to try the aac+ stream again only to find that now, audio starts instantly, but stops after about 1 second of play and then goes silent. The stream still shows as active, just silent. I can start and stop the stream over and over to keep hearing new 1 second clips, but this obviously isn't a suitable way to listen to anything

I see that these forums are nearly deserted, but I thought I'd give 'em a shot.

Thanks in advance,

--X'estrix

[shon]

Hello,

Which player and it's version number are you using? How are you tuning into the server? Are you tuning in by the dropdown tune in box on the website, a bookmark, or some other method? Are you tuning into the subscription AAC+ servers or the public AAC+ servers. Are the public AAC+ servers doing the same behavior as the subscription ones?

Just so you know, this is the first time I've heard any reports regarding the 48k AAC+ stream, so I'd like to get the particulars so I can look into it for you.

[Xestrix]

Hi, sorry, I had stop checking here after the first week of no replies :x I also sent a support request to the email address but never heard back



Player : The KMPLayer 2.9.4.1434
Method: Bookmark, Playlist, Old Site link, New Site link (drop-down)
Server: Subscription

The problem persisted across 3 different pc's and a wii gaming console, both  public and sub streams. Using WinXP Pro x86, Vista Ultimate x64, GCLinux. Alos using Windows Media Center 10/11, KMPlayer, MediaPlayerClassic, and MPlayer.

So, pretty all encompassing. Though also moot now, since my subscription expired before I could resolve the issue.

Another thing to note: The public stream is now working fine for me, I am listening to it as I type.