Radio-Info.com

Radio-Info.com Discussion Boards
Login March 21, 2010, 07:25:22 PM *
Username Password Session Length
 
Welcome, Guest. Please login or register. Did you miss your activation email? Did you forget your password?
:  
   Home   Help Search Login Register  
Pages: 1 [2] 3   Go Down
  Print  
Author Topic: 64k 100 Slots vs 128k 50 Slots  (Read 600 times)
V.Riley
rimember

Offline Offline

Posts: 373

Every station I love eventually changes formats.


« Reply #10 on: August 21, 2009, 08:50:42 AM »

If the 64Kbps stream was in AAC+ encoded and the 128Kbps was MP3 encoded then their quality would be for the most part the same.  Given that, the 64Kbps would be the better deal.  The thing to keep in mind is that currently AAC+ encoding is not as widely accepted as MP3 format and your listeners may not have the right player/codec to listen to an AAC+ stream.  You'd have to have some understanding of what players the majority of your listeners are using, and see if those support the AAC+ stream.  However, if both 64Kbps and 128Kbps streams are to be MP3 encoded, then for my ears (and I don't have perfect hearing) I would pick the 128Kbps in Stereo as I can hear the difference between 64Kbps MP3 and 128Kbps MP3 streams.
Logged
rickityone
rimember

Offline Offline

Posts: 82


« Reply #11 on: August 21, 2009, 10:37:12 AM »

I'd go with the 128K - and I'd start with less than 100 - why pay for so many when you are beginning. It takes time to build an audience. You can easily add more. Just an e-mail away.

rickity
gulchradio.com
Logged
streamer
rimember

Offline Offline

Posts: 78

One Day I'll own the Real thing!


« Reply #12 on: August 25, 2009, 08:30:43 AM »

I've found generally that switching between 64k Mono, 64k Stereo, 96k Stereo and 128k Stereo MP3 has had no impact on my listening figures. They've remained pretty consistent withe the usual seasonal variations and slow rises either way. Right now I'm 128k MP3 Stereo because I have the bandwidth to do it. I did drop to 96k some time ago, and whilst listener numbers actually rose slightly (I assume less buffering), I did get a real nasty email moaning about the quality. I asked for some contributions to streaming costs and then he went polite and understood.

What does help is being seen as 128k MP3 in directories as people see the higher numbers and assume it's better. I also have a 48k AAC+ stream and see on average only 0.5-1% of my daily listeners using it!
Logged

2NG - Two Nations Gold. is back. Great Oldies from the USA and the UK!
scanman1
rimember

Offline Offline

Posts: 176


« Reply #13 on: August 26, 2009, 02:33:58 AM »

Even at 32K that AAC+ codec can sound quite good! I tend to select AAC+ whenever it's available as an option.
Logged
radiookc
rimember

Offline Offline

Posts: 21


« Reply #14 on: August 27, 2009, 03:05:02 PM »

SAVE YOUR MONEY!!!!

Don't pay for more slots than you need. As you grow - add more.

64k Stereo sounds great. Keep in mind where our listeners are. Mostly at work.
The 128k might tick off the IT people in the office and get you blocked.

Pay extra close attention to the ripping quality and max out the use of
you plug in's and you will get a great sounding 64k stereo stream.

I use Loud City and tried to stream at 64k (they dont support it) and kept
getting bumped off the server. 64k momo is not a option for my format.
I stream at 96K Stereo (lowest speed the offer in stereo and after fine
tuning the plug in's in sam my 96k sound a lot better than some of the
128k's out there.

Welcome! I wish you good luck!!!


Chris
www.radiookc.com
Logged
LowPayDJ
rimember

Offline Offline

Posts: 197

We Are All Stars in Our Own Little World


« Reply #15 on: August 28, 2009, 12:42:34 PM »

If you do your homework, there are plenty of places that offer 100 slots at 128k for only $20-50 a month
Logged
streamer
rimember

Offline Offline

Posts: 78

One Day I'll own the Real thing!


« Reply #16 on: August 31, 2009, 08:42:03 AM »

If you do your homework, there are plenty of places that offer 100 slots at 128k for only $20-50 a month

Remember, you get what you pay for. I could write a book with posts on various forums that lament these deals.!!!! You'll be surprised how many have a great couple of months then all hell breaks lose! Usual problem, the providers oversubscribe the server. You pay for 100 slots but on average only use 20 or so, then one day you get more listeners and so do the others on the server and bang!
Logged

2NG - Two Nations Gold. is back. Great Oldies from the USA and the UK!
LowPayDJ
rimember

Offline Offline

Posts: 197

We Are All Stars in Our Own Little World


« Reply #17 on: September 01, 2009, 10:10:15 PM »

Even though my streaming server provider has been sold to a bigger company twice in the past year and a half that I've been using them, I still enjoy a cheap rate (100 slots @ 128k for $35 a month)and I have had very few issues.  I think their normal rate for new customers is now $50 for that plan, but that's still a good price.  You are crazy if you pay much more then that for streaming services.  Anyone wants their contact info, just send me a message.
Logged
Starbucks
rimember

Offline Offline

Posts: 506


« Reply #18 on: September 04, 2009, 09:02:51 PM »

SAVE YOUR MONEY!!!!

I agee with you. 64K is all you need, as far as listeners go. most listen in the office, plus the higher you go in streaming, alot less listeners you'll have even though it does sound better.  There is a difference at 128K, but that should be used for your own listening pleasure if you have a successful surround system and apekers. For you basic computer speakers, many potential listeners won't or will have high buffering access to your station if your at 256K or something and will be forced to tune out.


Don't pay for more slots than you need. As you grow - add more.

64k Stereo sounds great. Keep in mind where our listeners are. Mostly at work.
The 128k might tick off the IT people in the office and get you blocked.

Pay extra close attention to the ripping quality and max out the use of
you plug in's and you will get a great sounding 64k stereo stream.

I use Loud City and tried to stream at 64k (they dont support it) and kept
getting bumped off the server. 64k momo is not a option for my format.
I stream at 96K Stereo (lowest speed the offer in stereo and after fine
tuning the plug in's in sam my 96k sound a lot better than some of the
128k's out there.

>>>>I don't understand why people criticize 64K. I've been told it's an artifact decode. I don't understand why people say you should go 32K  or 64K in mono.
Sounds fine to me.



Welcome! I wish you good luck!!!


Chris
www.radiookc.com



« Last Edit: September 04, 2009, 09:08:25 PM by Starbucks » Logged
Chuck
rimember

Offline Offline

Posts: 2452


« Reply #19 on: September 04, 2009, 09:55:11 PM »

I'm sure that any of the people on these boards can hear the difference in streaming rates, but I'll bet that most of your listeners don't have a clue.  Most are listening with the speakers that came with their PC which are probably over-priced at $5.00.  Sure, some people have better speakers or maybe headphones, but that is the exception, not the rule. None of the usual computer speakers I've ever heard are exactly "audiophile quality," nor are many of the popular ear-bud headphones. 

It's your money, but in most situations, I'd go with more listeners and slightly less fidelity.  That thought assumes that you are actually providing programming that someone wants to hear.
Logged
Pages: 1 [2] 3   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP

Postings on Radio-Info.com are the opinions of the people who post them. Views expressed do not necessarily represent the views of Radio-Info.com or its parent in3 media, inc. In fact many of the views expressed here are just plain wrong. But they are opinions and this site allows us all to discuss those opinions. Any reliance on information posted is done so at the user's own risk. For a detailed look at the rules, regulations and uses of Radio-Info.com please see our TERMS OF SERVICE. 14

Valid XHTML 1.0! Valid CSS!
Page created in 0.769 seconds with 19 queries.