[Red5] Confusion about different ApplicationAdapter methods

[Jeremy Morton]

On Thu, 26 Feb 2009 17:00:08 -0800, Art Clarke <aclarke at xuggle.com> wrote:
> I get a 404 for your source code, and the resulting FLV in your flvplayer
> plays fine for me.  The scrubbar does seem odd (it starts about 20% into
> the
> file), but this might because your starting timestamps for your FLV don't
> begin at 0 (would be wrong though).

Thanks again for the response Art.  Oops, I guess that's because rafb.net
only stores pastes for 24 hours.  Here's a similar version stored on my
server:
http://www.game-point.net/misc/flv/code.htm

Could you check through and see whether there's anything that could be
causing the errors with WMV conversion?  Or could it just be that ffmpeg
itself has trouble converting WMVs?  The same code seems to work OK for an
MPEG4 file.

[...]

> And you're right, it has 4 video streams.  Interestingly it's 4 different
> quality versions of the same video:
> Input #0, asf, from 'GOOSE.wmv':
>   Duration: 00:00:15.44, start: 3.000000, bitrate: 1191 kb/s
>     Stream #0.0: Audio: wmav2, 32000 Hz, stereo, s16, 32 kb/s
>     Stream #0.1: Video: wmv1, yuv420p, 320x240, 64 kb/s, 15 tbr, 1k tbn,
> 1k
> tbc
>     Stream #0.2: Video: wmv1, yuv420p, 320x240, 189 kb/s, 30 tbr, 1k tbn,
> 1k
> tbc
>     Stream #0.3: Video: wmv1, yuv420p, 320x240, 314 kb/s, 30 tbr, 1k tbn,
> 1k
> tbc
>     Stream #0.4: Video: wmv1, yuv420p, 320x240, 464 kb/s, 30 tbr, 1k tbn,
> 1k
> tbc
> 
> By doing this, you can have a player (or a streaming server) choose to
> send
> the highest quality video stream that will work within the given
> bandwidth.

Ahh, hadn't thought of that!  Interestingly, it seems that when my code
just grabs the first video stream, it actually crashes during conversion
because of an 'invalid timestamp' error; when I hardcode in to grab the
third (2nd video) stream, it does convert it (however dodgily).  Again,
maybe it's just hard to convert WMV files.

As you said before, the scrubbar starting some way into the video might
have something to do with Xuggler detecting this:
start: 3.000000

But why does it detect the starting timestamp as 3 seconds in?  Weird.

Best regards,
Jeremy Morton (Jez)