Intro File Help

[EpiphoneG400]

Hey, back again, lol I finally found out all the stuff I need, and my stream is working great.
I just need some help with the intro and backup file.
I made a short intro for my server, and its in .wav format. I made it using a very simple recording program on my computer. I was just wondering....does the intro file have to be in mp3 format to work? And how do i find out my bitrate to adjust it to?

Also.... is the backup file the same as intro, only at the end of the broadcast... like when it disconnects?


Thanks again,
Cody

[Nick@ss]

does the intro file have to be in mp3 format to work?
>> yes

And how do i find out my bitrate to adjust it to?
>> make sure the file is the same as the stream.... so if your streaming @ 24k 22khz mono thats what the file needs to be.

Also.... is the backup file the same as intro, only at the end of the broadcast... like when it disconnects?
>> correct.

[EpiphoneG400]

ok righton. thanks much,

[Monster Boxx]

ok well there are holes in nick@ss' reply....

And how do i find out my bitrate to adjust it to?
>> make sure the file is the same as the stream.... so if your streaming @ 24k 22khz mono thats what the file needs to be.

Not to say that this is not true, but the thing you fail to mention is that you can denote the bitrate at the end of your mp3 filename.

i.e. you have a 128/44100 stream and you have "intro".mp3 that is encoded to 128/44100. and you still have buffer problems. it stands to reason as most of us have VBR (variable bitrate).
so this example would call for you to rename the file

"intro"128.mp3 the file still needs to be the same bitrate and channels as your stream.

Also.... is the backup file the same as intro, only at the end of the broadcast... like when it disconnects?
>> correct.

Incorrect...

The backupfile has no bearing on your broadcast. infact if say you have a 256kbps mp3 and you have a 128kbps stream. It does not seem to matter. This file does not even have to be the same as the one you used as the intro. It would make no sence to make it all the same. The into "intorduces the stream and the backup is a "backup" say the stream breaks or ends yet the server is still running. its a loop that can be whatever you want.

This all leads me to one point. I see a lot of questions without clear answers. Simply by experimenting I found my answer. I would highly suggest to the mods that there is a little more quality control of what is labeled as "help" when I see canned responces from people that seem to know nothing about how things work I just cant help but wonder how many experiences have been ruined due to a lack of good support. I found 3-4 other threads discussing this very subject that have very similar answers that lead people down a road or frustration. people just want a freaking intro. so please get off their back and provide superior support if you are so superior...

[dotme]

@Monsterbox

You have clearly shown your ignorance with your post. What a load of bullshit.

Renaming an intro file has no bearing on what it's encoded at. Your second rebuttal is just stupid. Players don't transition well from one bitrate to another. So if you have a 128k stream and a 64k backup file, the file won't play. It's that simple.

Nick spends a lot of his free time helping people here. You don't. So don't show up on these forums hurling accusations at people when you've been a member here for what... 10 minutes?

Go crawl off back under the rock you came from and stop attacking forum members that offer helpful, and correct, answers.

[Monster Boxx]

@dotme

thanks for the quick reply. once again I am not suprised by what the reply has brought me.

You are right. a 256kbps file for a backup is not a good idea for a 64k stream. Thats all well and fine.

what you fail to see once again is when you go into your config you will be addressed with the folowing.

; IntroFile can specify a mp3 file that will be streamed to listeners right
; when they connect before they hear the live stream.
; Note that the intro file MUST be the same samplerate/channels as the
; live stream in order for this to work properly. Although bitrate CAN
; vary, you can use '%d' to specify the bitrate in the filename
; (i.e. C:\intro%d.mp3 would be C:\intro64.mp3 if you are casting at 64kbps).
; The default is no IntroFile
IntroFile=C:\synthwhore128.mp3

originaly my synthwhore.mp3 file was encoded to 256kbps. I run an internal 128kbps server for a LAN party. so I automaticly noticed I had a problem iwas getting a 30-60-90 buffer problem. Ok time to go re-encode that bad boy. So I did. 128/44100...ok fire it up...

buffer problems again...so what do I do?

I take advantage of what the CONFIG told me to do. I put a 128 on the end of my filename that is encoded properly.

So if I am so f'd up and not understanding things what did I do before using the 128 after my file name that was wrong? If I am correct I would tend to guess that I was right to begin with and there was no need for your blast.

As for my calling out one particular person...It was a general statement. At anyone giving advice. Your return also was a indictment of your eleitest attitude that you know more that me. So please spare me the tough guy stuff... I simply wanted to make it perfectly clear that the advice given was sketchy at best, accurate yet not complete. I am not someone that will play games like that its the freaking internet. I simply wish that people involved could have bit more tact. You are the ones running the forums.

[dotme]

I'm no elitist. I've only been webcasting for a year, I certainly don't know everything, and I learn something new almost every day.

; IntroFile can specify a mp3 file that will be streamed to listeners right
; when they connect before they hear the live stream.
; Note that the intro file MUST be the same samplerate/channels as the
; live stream in order for this to work properly. Although bitrate CAN
; vary, you can use '%d' to specify the bitrate in the filename
; (i.e. C:\intro%d.mp3 would be C:\intro64.mp3 if you are casting at 64kbps).
; The default is no IntroFile

My understanding of that setting is this:

You can encode a 24k introfile and upload it as myintro24.mp3
You can encode a 64k introfile and upload it as myintro64.mp3
You can encode a 128k introfile and upload it as myintro128.mp3

You then set the introfile as C:\myintro%d.mp3

If your encoder is running at 24kbps and a listener tunes in, the DNAS will serve them myintro24.mp3

Likewise if you are broadcasting at 128k or 64k, the DNAS will offer the right file for the bitrate so there's no chipmunk effect on the listener.

I understood from your first post that you were contending that merely putting 128 at the end of the filename means the DNAS will transcode whatever it was originally encoded at to the new bitrate of 128k. I don't believe that to be the case. Sorry if I misunderstood.

[Monster Boxx]

no prob...I think we are at an understanding...I dont mean to be a prick. Sorry if I sounded that way.

THANKS!

[dotme]

Originally posted by Monster Boxx
I dont mean to be a prick. Sorry if I sounded that way.

Same here