[Live-devel] Two copies of fmtp_config() data in m4e files

[Ron McOuat]

I am using the 2007.08.03a (latest) version.

1) Capture using openRTSP to a file test.m4e using this command line

./testProgs/openRTSP -V -v -T 80 -b 200000 -f 7 -w 704 -h 480 
rtsp://69.67.172.61/mpeg4/1/media.amp >test.m4e

The fmtp SDP line looks like

a=fmtp:96 
profile-level-id=245;config=000001B0F5000001B5090000010000000120008C401928B021E0A21F



2) Start testOnDemandRTSPServer which will serve the test.m4e file

Run open RTSP again against this server using

./openRTSP -V -v -b 200000 -f 7 -w 704 -h 480 
rtsp://127.0.0.1:8554/mpeg4ESVideoTest >/dev/null


The fmtp SDP line now looks like

a=fmtp:96 
profile-level-id=245;config=000001B0F5000001B5090000010000000120008C401928B021E0A21F00000001B0F5000001B5090000010000000120008C401928B021E0A21F


The config= string has been doubled up.

Using a binary file tool I was able to verify there were 2 copies of the 
data at the front of the file.

In playCommon.cpp I commented out line 725

fileSink->addData(configData, configLen, timeNow); and then recompiled. 
The next run of openRTSP produced the same option= as the pull from the 
original source after replacing the test.m4e file with one produced by 
the new openRTSP back in step 1.

It appears the entire block of code from line 714 to 727 which writes 
the option string to the start of the output file is no longer needed.

Regards,

Ron