We Loudcast is a forum sponsored by Loudcaster and managed by community members. It's a place to exchange ideas about broadcasting online. Loudcaster Support does not participate in this forum. Issues related to the Loudcaster service must be emailed to support [-at-] loudcaster.com
Unplayable tracks and secondary stream
  • QEZradioQEZradio January 18
    I am having an issue with tracks which apparently begin to play but then suddenly "skip" to the next track...almost as though the file is corrupt or the track is the incorrect file type and the DJbot refuses to play it. I just hear a slight noise for about half a second, and then the next track begins to play. I scanned the list of tracks in my acct via my ftp program, and I was only able to locate one file (a .jpg) which was uploaded in error; the rest of them appear to be mp3 files. I deleted the jpg file, but I'm still experiencing the skips intermittently (maybe once every 2-3 hrs). I have tried to check when a track skips and see what is "now playing" but the titles of those tracks are never displayed, so I have no idea which of the tracks are causing the problem. Do tracks that are incompatible with the DJ bot usually create this sort of skipping phenomenon, or does the system just ignore them, anyway? Would tracks that are corrupt cause the DJbot to skip them in that manner I mentioned above.

    In regards to the secondary stream I can choose to use on my acct (an mp3 version)...would that stream be limited to being heard only via the loudcaster page or tunein app, as is the case with my acct? The reason I ask is that I have a few listeners who have inquired about an mp3 stream because they are unable to hear my station on their wi-fi radios (since the AAC+ format is incompatible with most of these types of radios).

    Thanks for the help in advance! :)
  • reaperreaper January 18
    I would check your mp3's and look for VBR (Variable Bit Rate) files. Not sure if that is the culprit, but I believe that CBR (Constant Bit Rate) only should be used. VBR mp3's are common when purchasing songs from Amazon and a few others.

    Your alternate encoder can be set to 64k mp3 or 64k AAC+. I recommend setting it to mp3 due to the fact that it will be compatible with just about any device or media player.
  • QEZradioQEZradio January 18
    Some of the tracks I am using are from amazon. However, if those files are VBR, they seem to be playing fine. If that is the case that the VBR files are causing the problem, would it refuse to play those files every time they begin to play, or just intermittently? I read somewhere online that the 320 kbps downloads are CBR by default. Most of those from tracks from amazon that I am using are 320 kbps, and many of the others from other sources are as well (around 80% of the total uploaded).

    As far as the encoder goes, if I chose to add an mp3 stream in addition to the AAC+ stream I'm already using...can only one file type be select as the primary stream? In other words, is it possible to use the AAC+ stream for my loudcaster page, and the mp3 stream for other devices? If I were able to use the mp3 stream and have it available via most of the wi-fi radios, if I were to add a listing for my station using the loudcaster URL (http://icecast01.loudcaster.com:80xxx) to one of the online station directories such as Reciva, would that be legal for me to do so?

    Thanks again. :)
  • reaperreaper January 18
    All mp3's will list their bitrate no matter if VBR or CBR. The files I buy from Amazon that are VBR will usually be 320k. I run EVERY track through Goldwave and save them as a CBR file at 192kbs.

    Your default stream (the one that will be used on your Loudcaster page) will always be AAC+, 24k or 32k. The alternate encoder was used for the HQ stream or mp3 stream will be used for 3rd party listing sites such as TuneIn or SHOUTcast. The use of your raw URL for use with certain devices is in a gray area for which I cannot give you an answer. I would contact Loudcaster via support for clarification on that.
  • thelegacythelegacy January 18
    Since we're talking about the Internet Listings I think if your station's service provider (in this case Loudcaster) pays Royalties to sound exchange it should be legal to list your station whereever you want to list it. However these huge greedy organizations want it all and will stop at nothing to get it. They even want to censor the Internet and this could be BAD for everyone and could even effect Loudcaster (Who Knows) so please sign the petition and the easiest way to get to the petition is going to:
    https://www.google.com/landing/takeaction/

    Don't let America become a communist country. Nuff said on that one.
  • Hi Reaper, so Loudcaster doesn't broadcast at 128Kbs mp3? I added a bunch of stuff at 128Kbs mp3 CBR and thought that would be ok, and although they are better than the 64Kbs they are playing alongside, they still show their lo-fi edge in moments due to them being re-encoded by Loudcaster, any advice on improving the end listener experience?
    Thanks
  • reaperreaper January 20
    I recommend you find a sweet spot as far as bitrate goes. I use 192kbs for all my tracks. I broadcast live and I am not worried about storage space limitations. But I have found that if you buy VBR tracks, it can be a crap shoot on finding a good bitrate when converting them to CBR. If you try 320kbs for example, the track may have artifacts of lower bitrate sounds and quality, while a higher bitrate, will actually be poorer.

    While Loudcaster does not offer a 128k stream, I have found that the 64k mp3 stream is very popular regardless of the sound quality. This is due to the ease of use for the end user IMHO. Remember, most listeners are listening at work and on crappy lap top speakers, so they really don't hear the lower bitrate artifacts. Plus, most companies frown on employees installing software on their computers and thus making the AAC+ stream useless to them unless the tune in through Loudcaster. Several broadcasters think that because the AAC+ stream wont work with the TuneIn web player, that the stream is "broken". That is not the case, the problem is the user does not have a compatible player installed and available.

    So, in a nut shell, I would upload tracks at the highest bitrate you feel comfortable using that gives you good sound quality and conserves storage space. I find 192kbs to be that bitrate, but would not go lower than 128kbs.
  • reaperreaper January 20
    Also, if tracks seem to be getting skipped by your DJ Bot, make sure your tags are correct and complete. Be sure to remove special characters like, but not limited to [ ], { }, / \ and _ -. These have caused a problem in he past.
  • Thanks. I have been converting from 320 down to 128 and they sound good, they just don't seem to be the same quality when i then hear them back from Loudcaster?
  • reaperreaper January 20
    I believe that could be anomaly of AAC+ encoding. IMO it seems to enhance or emphasize the highs and lows but nothing to the midrange. Almost like some of the depth is missing. I understand what you are talking about but when I pump my 32k AAC stream through the stereo in my van, it sounds pretty damn good.

    Here are some converting tips:
    1. Never overwrite the original file especially if purchased from an on line site.
    2. When re-encoding, use he original file, not a copy. The more you re-encode a file the more of a chance the file will sound like $hit.
  • ok.
    from what I've read above, once you get subscription, people will see you listed on SHOUTcast etc and then they can get the 128Kbs stream anyway, or am i reading that wrong?
  • reaperreaper January 20
    Nope. Your tracks are uploaded at your desired bitrate and then Loudcaster encodes them to whatever you have your encoders set for. It will not change where ever you get listed. I have a 128k stream for 2 of my stations because I broadcast with 2 hosting companies, Loudcaster and Live365.
  • golfing123golfing123 January 21
    why do you guys hate answering my questions for
  • Hi Reaper, on the new - what I assume is new as it looks different to your post pic - interface, there doesn't seem to be any choice of encoders. Would you know if there will be a choice? Thanks again for all your pointers, very helpful.
  • reaperreaper January 21
    Sorry to say I'm kind of in the dark about the new dashboard. I'm not much help there, sorry.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with OpenID Sign In with Google Sign In with Twitter

Sign In Apply for Membership

In this Discussion

Tagged