Help with Stream.

[SwiftWave]

Hey guys,

I've been having this problem since I started broadcasting and I can't seem to be able to fix it, after asking console game broadcasters and http://en.justin.tv/help I'm still stuck, so I was hoping anyone here could help me out. :/

Okay, so here's the situation.

I'm broadcasting gameplay from my Xbox 360 by using a USB Capture Card (BlitzBox B1) with Flash Media Encoder 3, The quality is amazing after tweaking with the settings and bitrate but here's the thing, the stream gets delayed. And not just normally delayed, no it gets delayed by 1 minute at first and the delay keeps building up. Till eventually I get people asking how I did something they just saw that actually happened 20-30 minutes ago.

The weird thing is that this only happens when I broadcast Game sounds, whenever I broadcast with my computer mic or anything else the delay remains at a solid 5 second delay, even after hours of broadcasting.

Please, do not tell me to lower my bitrate or adjust the size, format.
I've basicly tried anything, my own conclusion would be that the audio capture of my Capture Card isn't good enough, resulting into the video being delayed to match the audio. Now before I make up my mind and get a new Capture Card, I'd like to hear what you guys think about this.

Extra Info...

Flash Media Encoder settings ;

Video Format : H.264 ( Main, 3.0, 4 Keyframe seconds) <-- Has been switched to VP6 and tried all the possible settings without change in delay.

Frame Rate : 25.
Input Size : 480x288.
Video Bitrate : 1200 (No change in delay when lowering bitrate, just lower quality)

Audio Format : MP3 (I've tried NellyMoser aswell, no change)
Channels : Stereo (Tried Mono.)
Sample Rate : 22050 Hz (Same story, no difference with other rates)
Audio Bitrate : 48 (You can guess...)

I've also used Justin.tv's Broadcasters, without any change in delay.

Thanks for your time.

[MikeZen]

ok, the only thing here that you are missing is to tell us what up/down speed do you have.

understan as "bitrate" as the speed you have to broadcast, so, if you have 1200kbps - video + 48kbps - audio you must have at least (teorical) 1248kbps for upload in your internet conextion, (note: i recommend you a wire conexion).

check your conextion at speakeasy.net/speedtest

remember, if you have any speed, keep in mind that you probably use also msn, internet browsers, etc.

this problem is very common when users set more than they can give. (experience)

good loock :)

[justtheavocado]

The bitrate you are using is too high, and you are using a non standard resolution for PAL. High bitrate ,non standard resolution, and cpu intensive x264 means that more processing time will be needed to encode, which causes delay. adjust resolution to a standard PAL, such as 384x288. and lower video bitrate to somewhere more reasonable, such as 400kbps, you will not experience tiling since 400kbps is suitable to standard SD resolution of 384x288. you should also increase capture framerate to 50fps, this will allow for frames to be dropped without noticeable loss in quality.

[MikeZen]

The bitrate you are using is too high, and you are using a non standard resolution for PAL. High bitrate ,non standard resolution, and cpu intensive x264 means that more processing time will be needed to encode, which causes delay. adjust resolution to a standard PAL, such as 384x288. and lower video bitrate to somewhere more reasonable, such as 400kbps, you will not experience tiling since 400kbps is suitable to standard SD resolution of 384x288. you should also increase capture framerate to 50fps, this will allow for frames to be dropped without noticeable loss in quality.

i dont agree this at all, i have a channel working perfect with HD using 800 of bitrate with 640x360, the image fit perfect and i dont have that problem, here is about internet conexion, you cant send more than you really can, if you try to broadcast mor packages fme will make a little buffer, so this is what you have. ofcourse if you try to set down your bitrate this could be fixed.

ok, looks this is fixed :)

PD. justin use NTSC wide.