Registering custom payload

Question

First of all i had a media file from which i could generate a perfectly fine output when run from a local file.
Then i finally managed to to configure the VLC-player as RTSP/RTP Server and tried to request that same media file via those protocols,
Unfortunatly i soon found this error-message in my logfile:
XX No format has been registered for RTP Payload type 96
As far as i understood the JMF, i figured that there already is a working format/codec for my mediafile - otherwise it couldnt be played locally in the first place.
Therefore i managed to extract the format information via:
System.out.println("Video format: " + videoTrack.getFormat());
And i got the following response:"FFMPEG_VIDEO, 640x480, FrameRate=25.0, Length=307200 0 extra bytes"
I then put that data into a new Format-Class (FfmpegVideoFormat) and registered it with:
AviVideoFormat format = new FfmpegVideoFormat();
int customPayloadNumber = 96;
mgr.addFormat(format, customPayloadNumber);
Et voila. Error message was gone. Unfortunatly so was the video output. The logfile doesnt show any errors at all but for some reason my processor doesnt generate any output at all:
The interesting part of the log-file ist :
## outgoing msg:
## PLAY rtsp://192.168.178.22:5554/Test RTSP/1.0
CSeq: 3928214
Session: 15724
Range: npt=now
User-Agent: HBT RTSP Client 1.0
## incoming msg:
## RTSP/1.0 200 OK
Server: VLC Server
Content-Length: 0
CSeq: 3928214
Cache-Control: no-cache
Session: 15724;timeout=5
## RTP video socket buffer size: 30825 bytes.
## RTP video socket buffer size: 41437 bytes.
## RTP video buffer size: 11 pkts, 7476 bytes.
## RTP video socket buffer size: 49387 bytes.
## RTP video buffer size: 21 pkts, 18832 bytes.
$$ Profile: instantiation: 3 ms
## Processor created: com.sun.media.processor.unknown.Handler@148cc8c
## using DataSource: com.sun.media.protocol.rtp.DataSource@1786e64
$$ Profile: parsing: 6 ms
## Building flow graph for: null
## Building Track: 0
## Input: FFMPEG_VIDEO, 640x480, FrameRate=25.0, Length=307200 0 extra bytes
## Custom options specified.
## A custom renderer is specified: de.hbt.customer.jmf.renderer.RotatingRenderer@ed0338
## Here's the completed flow graph:
com.sun.media.parser.RawBufferParser@199f91c
connects to: com.omnividea.media.codec.video.NativeDecoder@1b1aa65
format: FFMPEG_VIDEO, 640x480, FrameRate=25.0, Length=307200 0 extra bytes
com.omnividea.media.codec.video.NativeDecoder@1b1aa65
connects to: com.sun.media.codec.video.colorspace.JavaRGBConverter@129f3b5
format: RGB, 640x480, FrameRate=25.0, Length=307200, 32-bit, Masks=16711680:65280:255, LineStride=640, class [I
com.sun.media.codec.video.colorspace.JavaRGBConverter@129f3b5
connects to: de.hbt.customer.jmf.renderer.RotatingRenderer@ed0338
format: RGB, 640x480, FrameRate=25.0, Length=307200, 32-bit, Masks=255:65280:16711680, LineStride=640, class [I
$$ Profile: graph building: 582 ms
$$ Profile: realize, post graph building: 45 ms
## Created RTP time base for session: 192.168.178.22
<End Of File>
Anyone an idea what went wrong?

Answer 1

Looks like a bad kludge job to me...
Telling the manager what format is associated with a given RTP payload type doesn't do anything if the Manager doesn't have a codec associated with that format type.
[http://java.sun.com/javase/technologies/desktop/media/jmf/2.1.1/formats.html]
FFMPEG isn't listed there, which means JMF doesn't have a codec for it... So the system goes "Oh, ok...this is an FFMPEG_Video stream, I'll create a Processor for that because I identified the video" and then it creates a Processor that can't actually do anything with the stream because it can't find a codec for it.
I'm suprised it isn't throwing an error telling you that it can't do anything with that video format, but, I'm guessing that the way you've registered the format has caused JMF to think it can do something with it and thus prevent that error from being thrown. I'm not 100% sure what's going on, but, I'm sure that what you did won't work unless JMF has a codec for the video format.