Listen to your favorite music from our licensed radio stations!   

Home Station Directory Radio Players  
Pricing & Signup Broadcaster's Area
Station Directory
Radio Players
Broadcasters Area
Pricing & Signup
Resource Partners
Community Forum
LoudCity Forum
Legal Info
Contact Us

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Brutish

Pages: [1]
Catch All Discussion Board / Re: IJS
« on: June 17, 2016, 09:35:40 PM »
IJS? Really?

Be careful what you wish for :)

Its good to see you both got your flags in the sand still.....

I've been dealing with the nightmare of terrestrial since the issues with CRB.

They mentioned my full name in the paper though, and that was kinda cool.  I head up to complete transmitter repairs (40 mile drive 1 way to the remote site, and it sucks to get there) tommorow.

Broadcasting Software / Lunarcaster
« on: August 04, 2013, 02:36:06 AM »
Im starting to become a big fan of it.  It  had some bugs to work out, but overall a great program for the price of free, written in XML (no heavy DB) and a lot of thought from a very hard driven developer who created it.

Radio Web Site Developmemt / Re: HTML code cleaner
« on: August 04, 2013, 12:13:47 AM »
I personally prefer alleycode editor.  Its like notepad++ on steroids.  A lot easier to program IFF functions if your working in the backend of WP.

Software Developers / Re: Useful Software
« on: August 04, 2013, 12:04:17 AM »
I will vouch for Icast.  Their bandwidth has been solid, and the techs know their stuff.  Im not impressed easily.  I was impressed.

But yeah, Win MTR over regular traceroute.  You will see some nice spikes to indicate issues, and you can leave it on, and have it consistantly monitor, so if you run into issues (like peski ISP choking bandwidth from your local ISP DC to save electricity, grrrrrr) you can call them up with some hard documentation thats graphic, so they can wrap their skulls around your complaint.

How Streaming Works / Wrapping your head around a stream
« on: September 21, 2011, 01:50:47 AM »
"But you know, I always said that no one else on my block was on the radio, and it was fun."
-Ed Bradley

Before I start a lot of these tutorials, I’m going to need to break down some terms Iwill be using frequently.  This will make other tutorials later make sense.

~Source~(WINAMP, WMP, REAL, ALSA PLAYER)- Think of this as what you use to play music from.  what you use to play an mp3, or where the sounds are coming from locally.  Does it have to necessarily need to be a music player to be a source?  Talking on your microphone, you would be the source.  If you have a sound effect board like the  Michas Jingle-Player, that’s a source. You get the drift.

~Transcoding~ The process of turning your source into a file type readable by listeners music listening devices (WINAMP, WMP, REAL, FLASH PLAYER, ect.)

~CODEC~ In simplest terms, its what you choose to make a file type for listeners.
 In example: I want my listeners to hear my stream in MP3.  I would choose an MP3 codec.  Why are these important?  Some listening devices/Streaming servers do not support some types of codecs. Since 2009, most listening devices (including flash) devices have started supporting open source codecs (FLAC, OGG).  However, a lot of mobile devices have still not got up to speed with supporting all codecs.

~DSP~(SHOUTcast DSP, B.U.T.T,) Digital signal processor- This is the program that you choose to do your transcoding through a codec. Some more well developed programs (SAM, IDJC)  have been designed to be a complete package of source and DSP.

~Streaming server~(SHOUTcast, SHOUTcast2, ICEcast2, ect.)  Before I begin this, for all the IT types out there.  THIS DOES NOT HAVE TO BE A STAND ALONE BOX IN A DATACENTER.  In simplest terms, this is the place where your codec sends the stream, and where listeners players do the handshake to receive the stream.  Is it a server? Yes.  Lots of connections to listening devices (If your lucky)  But can you have more than one streaming server on the same box in a datacenter? Absolutely.

ID3 Metadata(ID3, ID3v2) Simplest terms- When you play a song, and are not able to see the "Artist-Song Title" you are missing ID3 metadata, or have chosen not to display it.   There are lots of programs (picard, Mp3Tag, MediaMonkey) that will tag your songs with the appropriate metadata.  This is very important as STREAMLICENSING needs this metadata displayed in order for their tracking servers to work correctly.

There are more terms to throw your way, but as I said from the beginning, I just want you to be able to wrap your head around the broadcasting concept...

So, for your average broadcaster, when you stream, it will go like this:

 Source----->DSP(/w codec)----->Streaming server----->Listener

Now, There is exceptions.  Since the 90's, broadcasters have been looking for ways to break these rules.  How?  Instead of streaming to a Server, how about streaming to another Transcoder (SC_Trans) that resides on the same computer as your streaming server , one that no matter what the DJ's codec/bitrate is, kicks the stream down to an AAC+ codec that is made to sound great at lower kbps.  Or over processing the source using a equalizer, so that the sound is not so great locally, however, makes a bass sound more full when transcoded and sent out to your listeners.

I don’t want to go into these concepts yet though.  Let’s stick to basics for now.  Expect this tutorial to be expanded a bit, and more to come.

How Streaming Works / Why a radio station?
« on: September 20, 2011, 11:02:55 PM »
"Brains, integrity, and force may be all very well, but what you need today is Charm. Go ahead and work on your economic programs if you want to, I'll develop my radio personality. "
Gracie Allen

Since the year of the first internet radio broadcast in January of 1998 by the founding fathers of internet radio (Tom Pepper, Justin Frankel, and Steve "Tag" Loomis), Internet radio has expanded by leaps and bounds, and technology has bridged a gap that allows even the leisure home broadcaster the ability to do shows with quality on a commercial level.

With all this aside, there are multiple reasons to run a broadcast.  A community based radio to keep your local social circle informed, a home broadcaster looking for a past time hobby, or a radio pioneer attempting to move up in the industry. The reasons are countless.   The biggest questions usually are "How do I do it?" or "What rules do I have to follow?"

If you are visiting the Stream Licensing site, I’m guessing you have already figured out the answer to the first question.  If you haven’t, I will answer that through these tutorials. Don’t worry; it's easier than you think.

Broadcasting Software / B.U.T.T. From Sourceforge
« on: September 20, 2011, 10:33:16 PM »
B.U.T.T.  was developed to be very easy to use, and multi platform
(Windows users and linux)

~Whats great about this program~

- If you want to broadcast live, This program is very low resource intensive ( Ran it on a 2001 Pentium 2/windows xp) and it also will ouput stereo mix (even on windows 7)

~The downside~

- Its very simple.  Being lightweight, it will only take "stereo mix" (what you hear through your speakers) and stream the sound out.

- It is pain to deal with metadata (song and title display wise).  The program is designed to be be linked to the metadata text file your player uses.  If you dont want to take the time to configure this, you can always update the metadata manually during a live show, and switch to a good automation program (like SHOUT! Radio Automation) afterwords.

~The shades of Grey~

Overall, I would recommend it to someone that doesnt mind typing/pasting band names and titles for a live show.  Its not the program you want for an automation, as it doesnt do anything like that.  Its simply a well designed and flexable way to take sound from any source and stream it to an Icecast/Shoutcast server.

If your a windows user, it does have special advantages, like the fact that it only does source out makes it the ideal software to use when attempting things like taking skype calls on the air.

But a good start for beginning broadcasters doing a closely monitored 1-2 hour live show.

Broadcasting Software / Linux user? check out IDJC
« on: September 20, 2011, 09:02:53 PM »
I have become an official fan of IDJC (Internet DJ Console)

Its free (and in the debian library for all linux Ubuntu users)

~Whats great about this program?~
- fully featured software with two decks, good crossfading, and all the same decent automation features you would look for in broadcasting software.

- Has lots of easy to add effects.

-  Includes the ability to use Jamin (free as well) as a three band processor for your overprocessing needs up to 40khz.

~The Bad~

- Has a somewhat difficult interface to initially set up.

~The shades of grey~

If your a linux user, you have heard of PulseAudio.  IDJC has NOTHING to do with that.  So the first thing you should be thinking is "How do I get sound input?"  Its through the use of a JACK audio server.  IDJC uses the JACK program like virtual cables, and while this was a brilliant move to ensure you get the capture device you want for your live show, it also makes it confusing at times with constant switchovers.

Once you get the hang of JACK interface, IDJC will wow you with all the potential it offers. This program deserves recommendation on my part.

Pages: [1]