Ross, Thanks for the reply, I'll try decreasing the constants. Bill "Woody" Boykin | SAIC Software Engineer IV | Software Solution Team
6725 Odyssey Drive Huntsville, AL 35806
Room : 370 Phone : 256-971-6738
email : william.c.boy...@saic.com
"It's better to wait for a productive programmer to become available
than it is to wait for the first available programmer to become productive." ~
Steve McConnell
________________________________
From: live-devel-boun...@ns.live555.com on behalf of Ross Finlayson
Sent: Wed 6/19/2013 2:04 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] testh264videototransportstream
I was comparing ffmpeg.exe to testh264videototransportstream exe and
have a question.
1. ffmpeg -i video.264 -vcodec copy video.ts
I see about 4 or 5 188 byte metadata payloads per second.
2. testh264videototransportstream exe video.264
I see about one 188 bytes metadata payloads per second.
Is there any way to get testh264videototransportstream exe to increase
or match the 188 byte metadat payloads that ffmpeg produces ?
What do you mean by "metadata packets"? Are you referring to Transport Stream
"PAT" (Program Association Table) and/or "PMT" (Program Map Table) packets?
If so, then the frequency at which these packets are inserted into the output
Transport Stream is determined by the constants "PAT_FREQUENCY" and
"PMT_FREQUENCY", defined in "liveMedia/MPEG2TransportStreamMultiplexor.cpp".
If you decrease these constants, then you will increase the frequency at which
the corresponding (PAT or PMT) packets are inserted into the output stream.
(As you can see, these constants are actually misnamed. They should have been
called "*_PERIOD", not "*_FREQUENCY".)
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
<<winmail.dat>>
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
