Old 28th November 2018, 12:36   #1
itdatatelecom
Junior Member
 
Join Date: Nov 2018
Posts: 1
SHOUTcast v2.6 with AAC+ bugs

Hello! We detected a problem with SHOUTcast v2.6, if you use it in AAC+ it starts to buffer you, and it is reconnecting to 10 seconds, if you use SHOUTcast v2.5 on AAC+ it goes smoothly without interruption.
itdatatelecom is offline   Reply With Quote
Old 17th December 2018, 15:13   #2
ultragain
Junior Member
 
Join Date: Dec 2018
Posts: 2
The reason is this message:
WARN [Licence sid=2] Format is not MP3, where only MP3 is allowed
in logs.
I´m using Centova and now have this problem with v2.6.
ultragain is offline   Reply With Quote
Old 17th December 2018, 16:48   #3
NurLutix
Senior Member
 
Join Date: Oct 2017
Location: Germany
Posts: 146
Hey,
Do you also own Premium?
If not, you can stream to 128 kbit/s. As well as only on mp3.

You don't need a premium if you don't use an authhash and you don't want to be listed.

Premium Features: https://www.shoutcast.com/Pricing

Greetings
Luca Stratmann
NurLutix is offline   Reply With Quote
Old 7th January 2019, 20:35   #4
asantoni
Junior Member
 
Join Date: Jan 2019
Posts: 2
As I was developing support for the Shoutcast V2 protocol for Rocket Broadcaster, I think I ran into the exact same issue you had here with AAC+ and Shoutcast 2.6.

Specifically, AAC, HE-AAC v2 (AAC+), and HE-AAC v1 all no longer work in Shoutcast 2.6. Confusingly, it's unclear if this is intentional or not, since it seems to correspond to Shoutcast.com introducing their "business" plans and I haven't found any official communication about the status of AAC+ in 2.6.

I also found another issue, which that AAC streams are unplayable on the Shoutcast.com
directory website if the streams are hosted by a Shoutcast 2.5 server. Streams are playable if they come from a Shoutcast 2.4 server. I think this one is more clearly just a bug. I was unable to test this case for Shoucast 2.6 since AAC is universally broken in that version.

I think these quirks are going to cause so much confusion for Shoutcast users that I even put them in my official Streaming Server Compatibility documentation. I also reached out months ago to the Shoutcast support team about these issues and never received any response.
asantoni is offline   Reply With Quote
Old 4th November 2019, 05:51   #5
packzap
Junior Member
 
Join Date: Jul 2001
Location: Tierra Del Fuego
Posts: 12
Yes, getting error,
code:
"stream detected AACv2, LC (2), 22050hz, estimated 96 kbps WARN [Licence sid=1] Format is not MP3, where only MP3 is allowed"

with Shoutcast DNAS/win32 v2.6.0.753 (Apr 25 2019). It will no longer serve the stream. I reverted back to 2.5.5.733 and it works correctly.

Does version 2.6.0 no longer allow AAC+ streams?
packzap is offline   Reply With Quote
Old 18th November 2019, 16:22   #6
Klaas
Member
 
Join Date: Sep 2018
Posts: 84
2.6.0 is allowing AAC+ streams but you need a Premium license.

In addition to that it takes ages for the Shoutcast server to recognise it has a valid AAC+ license. The last time I tested it took about 8 - 9 hours for the stream to come up. I could imagine this is a bug.
Klaas is offline   Reply With Quote
Old 19th November 2019, 11:09   #7
Cosmic Butter
Administrator
 
Join Date: Nov 2019
Posts: 8
Hi Klaas,

Do you confirm your automation software handles aac-mpeg4 and matches one of the above bitrates:
AAC4 128, AAC4 96, AAC4 64, AAC4 32
Cosmic Butter is offline   Reply With Quote
Old 19th November 2019, 11:51   #8
Klaas
Member
 
Join Date: Sep 2018
Posts: 84
Currently I have a stream connected with the following: AACv4, LC (2), 22050hz, 64kbps.
Klaas is offline   Reply With Quote
Old 19th November 2019, 13:20   #9
Cosmic Butter
Administrator
 
Join Date: Nov 2019
Posts: 8
Do you confirm it is fine now?

What playout system are you currently using?
Cosmic Butter is offline   Reply With Quote
Old 19th November 2019, 13:29   #10
Klaas
Member
 
Join Date: Sep 2018
Posts: 84
When I'm reconnecting the stream or even restarting the Shoutcast software I'm getting the "Format is not MP3, where only MP3 is allowed" message again.

So there still seems to be some kind of licensing issue with the Shoutcast DNAS.

As playout system I am using "mAirList" with enc_aacPlus.exe as an external encoder.
Klaas is offline   Reply With Quote
Old 19th November 2019, 14:21   #11
Klaas
Member
 
Join Date: Sep 2018
Posts: 84
Btw. The YP server is returning funny codes like: -211987348
Klaas is offline   Reply With Quote
Old 19th November 2019, 20:31   #12
Cosmic Butter
Administrator
 
Join Date: Nov 2019
Posts: 8
That is not a licensing issue, otherwise you won't be able to stream in MP3 192kbps.

I checked your streams several times today and noticed the aac one was very bad quality, bitrate was variating a lot, stream kept being disconnected.

It appears Mairlist does not handle AAC MPEG4 natively. Some users met the same issue here: https://community.mairlist.com/t/aac-mpeg-4/11042/34
You should check Mairlist community for support.
Cosmic Butter is offline   Reply With Quote
Old 19th November 2019, 20:43   #13
Klaas
Member
 
Join Date: Sep 2018
Posts: 84
I know it is not doing AAC natively therefore I'm using an external encoder for that.

I'm using the same settings to stream the AAC to an Icecast server (in port 8000) and that one works perfectly without any interruptions and in the past I was able to create a stable stream with AAC on Shoutcast too.

It has been stable for 1 - 2 hours today. Then I restarted the DNAS to replace the SSL certificate and now I'm getting this message again:

[Licence sid=3] Format is not MP3, where only MP3 is allowed

And the source is kicked again every few seconds with this message.

So is that error message misleading?
Klaas is offline   Reply With Quote
Old 19th November 2019, 21:46   #14
Cosmic Butter
Administrator
 
Join Date: Nov 2019
Posts: 8
both mp3 and aac streams are up:

Listing Status: Stream is currently up and public
Stream Status: Stream is up (HE-AAC @ 64 kbps, 22.05 kHz) with 1 of 512 listeners
Listener Peak: 2
Avg. Play Time: 31 seconds
Stream Name: ISN Radio
Stream Website: www.shoutcast.com

restart is always recommended after major changes such as ssl, mountpoint, config file, etc
Cosmic Butter is offline   Reply With Quote
Old 19th November 2019, 22:09   #15
Klaas
Member
 
Join Date: Sep 2018
Posts: 84
That is exactly the issue I am having. Now it is connected stable. However I can tell you if I would now restart the encoder or the DNAS the stream will be offline for hours. Here are the last logs before it stabilized:

2019-11-19 22:03:08 WARN [Licence sid=3] Format is not MP3, where only MP3 is allowed
2019-11-19 22:03:08 INFO [SRC xxxx:53871 sid=3] Shoutcast 2 source disconnected.
2019-11-19 22:03:18 INFO [SRC xxx:53882] Shoutcast 2 source connection starting.
2019-11-19 22:03:18 INFO [SRC xxx:53882 sid=3] Title update [Gary Jackson - My Generation]
2019-11-19 22:03:20 INFO [SRC xxx:53882 sid=3] stream detected AACv4, LC (2), 22050hz, estimated 64 kbps
2019-11-19 22:03:25 WARN [Licence sid=3] Format is not MP3, where only MP3 is allowed
2019-11-19 22:03:25 INFO [SRC xxx:53882 sid=3] Shoutcast 2 source disconnected.
2019-11-19 22:03:35 INFO [SRC xxx:53892] Shoutcast 2 source connection starting.
2019-11-19 22:03:35 INFO [SRC xxx:53892 sid=3] Title update [Gary Jackson - My Generation]
2019-11-19 22:03:37 INFO [SRC xxx:53892 sid=3] stream detected AACv4, LC (2), 22050hz, estimated 64 kbps

It now took about 6 hours to get connected and not being kicked by the DNAS because "only MP3 is allowed".

If I now restart the DNAS we will have the same situation over again. Wait about 6 hours and the AAC stream stays connected.
Klaas is offline   Reply With Quote
Old 19th November 2019, 23:15   #16
Cosmic Butter
Administrator
 
Join Date: Nov 2019
Posts: 8
I am two or the three IPs currently connected to your stream for one hour and a half and I confirm it is fine. IPs: X2.XX7.69.1 XX9.XX0.X4.1

Listing Status: Stream is currently up and public
Stream Status: Stream is up (HE-AAC @ 64 kbps, 22.05 kHz) with 2 of 512 listeners
Listener Peak: 2
Avg. Play Time: 1 hour 3 minutes 30 seconds
Stream Name: ISN Radio
Stream Website: www.shoutcast.com

Trust me, restarting your dnas is fine completely fine if your config file + playout are all good
Cheers.
Cosmic Butter is offline   Reply With Quote
Old 20th November 2019, 07:27   #17
Klaas
Member
 
Join Date: Sep 2018
Posts: 84
Okay you are saying the settings are fine now as the stream came up. This morning now I didn't change anything on the playout side. I just restarted the DNAS. Again Icecast is up and running and not complaining. Everything works fine.

Shoutcast:

[Licence sid=3] Format is not MP3, where only MP3 is allowed

Is telling me only MP3 is allowed.

I have shut down the 2.6.0 server now and started the old 2.5.5.733. Started the Encoder and ACC is working without any problems.

So as Icecast is working perfectly and Shoutcast 2.5.5.733 is working perfectly I doubt it is something with my playout system.

I am willing to debug this issue further however I need more information how the DNAS can be actually debugged, if there are any hidden flags to set so I can see what is actually happening in the background.


Edit: Another issue I noticed is that with 2.6.0.753 it sometimes takes ages for the authhash to be registered correctly. So for some time it tells me "Please Register Your Authhash" and then suddenly everything is okay.
Klaas is offline   Reply With Quote
Old 20th November 2019, 08:41   #18
Klaas
Member
 
Join Date: Sep 2018
Posts: 84
Apparently AzureCast has the same issue with Shoutcast 2.6.0 whereas with 2.5.5 everything works fine:

https://github.com/AzuraCast/AzuraCast/issues/1030
Klaas is offline   Reply With Quote
Old 20th November 2019, 09:04   #19
Cosmic Butter
Administrator
 
Join Date: Nov 2019
Posts: 8
This is not an Azuracast or Mairlist forum Klaas, please stop posting outdated links.
You should focus on your radio and audience which egals to 0 today, thanks!

Visit this to master your dnas knowledge: http://wiki.shoutcast.com/wiki/SHOUTcast_DNAS_Server_2

Or go for a shoutcast for business plan if you are not confident enough on the dnas.
Thanks.
Cosmic Butter is offline   Reply With Quote
Old 20th November 2019, 09:10   #20
Klaas
Member
 
Join Date: Sep 2018
Posts: 84
Then please read my post from 8:27 CET.

Sorry but this is getting nowhere. You have to pay for a premium subscription of your Shoutcast Software and you are not getting proper support here. You are just waiting that the encoder stabilizes so you can say "everything is working fine".

I have shown you that an AAC stream is working with every kind of software except for the DNAS 2.6.0.753. However instead of actually making any effort in debugging these issues your customers are being told that the problem resides on their side if there is any reaction to a problemticket at all.

The link to the AzuraCast issue even proves further that before the upgrade to 2.6 an AAC encoder could connect to the DNAS without any problems.
Klaas is offline   Reply With Quote
Old 20th November 2019, 09:21   #21
Cosmic Butter
Administrator
 
Join Date: Nov 2019
Posts: 8
I don't need your example from 2018.
We have thousands of radios working fine with AAC, some are successful and have huge audience!
I can tell you those are a using great encoders and know how to use it well.
Cosmic Butter is offline   Reply With Quote
Old 20th November 2019, 09:45   #22
Klaas
Member
 
Join Date: Sep 2018
Posts: 84
I did one last experiment and got it finally working.

What did I do? I'm just not encoding directly to the DNAS, just relaying from our internal broadcasting system.
Klaas is offline   Reply With Quote
Old 21st November 2019, 09:22   #23
Klaas
Member
 
Join Date: Sep 2018
Posts: 84
@Cosmic Butter Just to follow up. I talked to some of the big stations in the Shoutcast Directory. They are still using Shoutcast 2.5.5 to run their AAC+ stream. I can confirm that Shoutcast DNAS 2.5.5 is rock solid in handling the streams.

In addition to that if I launch the 2.6.0 again following message appears at nearly every title update or request to the YP (on 2.5.5 it works!):

Quote:
[YP sid=3] response returned 500, NOK
If I follow your knowledge base, error 500 is described as a generic error on the YP server.
Klaas is offline   Reply With Quote
Old 27th November 2019, 18:25   #24
Klaas
Member
 
Join Date: Sep 2018
Posts: 84
So as an old Shoutcast DNAS user I decided to cancel the premium plan to the end of the month as 2.6.0 is actually unusable.

Why did I have an audience of 0 listeners? Simply because the 2.6.0 server was just a testserver to see how the new premium version works. It does not work good. Crashes, bugs with AAC+, YP server cannot be contacted because of a "generic server error", ad insertion is not pausing the stream just replacing it.

I will stay with 2.5.5 where AAC+ is working perfectly or migrate completely to Icecast.

From a paid service I expected much more than just an indirect or direct "shut up and don't bother me". If you don't want to have any customers just write it on your website.
Klaas is offline   Reply With Quote
Old 28th November 2019, 09:30   #25
LStratmann
Guest
 
Posts: n/a
Until recently I also worked with SHOUTcast and AAC and there were no problems.

Greetings.
  Reply With Quote
Reply
Go Back   Winamp & Shoutcast Forums > Shoutcast > Shoutcast Technical Support

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump