ynsairam
18th June 2008, 19:09
Hi,
Can any one help me find out an efficient tool (preferably freeware) that can put h.264 encoded bit-stream(.264) in to mpeg2 transport stream (.ts or .m2ts) while also muxing with audio with some tight constraints on bit-rate(CBR mode). I tried a lot of tools like universal media coder(ffmpeg, mencoder), VLC player, Elecard x muxer Pro, Total video container, tsMuxeR etc. But most of them gave an output, which would not either play back or end up using too many bits. The best result i could get is with tsmuxer, which gives an output that plays back well and increases the bit overhead of .ts stream by about 25-30 % over .264 bit stream among other tools. So can anyone help me understand why is it putting so much overhead? also when I tried to analyze the .ts stream using elecard stream analyzer, it shows up many packets of 184 bytes padding up in between slices for PIDs (0x0, 0x100,0x1F). Anyone have some idea what is the use of this..I thought prob these (null..??)packets are causing unnecessary overhead. Any help is highly appreciated. :thanks:
Can any one help me find out an efficient tool (preferably freeware) that can put h.264 encoded bit-stream(.264) in to mpeg2 transport stream (.ts or .m2ts) while also muxing with audio with some tight constraints on bit-rate(CBR mode). I tried a lot of tools like universal media coder(ffmpeg, mencoder), VLC player, Elecard x muxer Pro, Total video container, tsMuxeR etc. But most of them gave an output, which would not either play back or end up using too many bits. The best result i could get is with tsmuxer, which gives an output that plays back well and increases the bit overhead of .ts stream by about 25-30 % over .264 bit stream among other tools. So can anyone help me understand why is it putting so much overhead? also when I tried to analyze the .ts stream using elecard stream analyzer, it shows up many packets of 184 bytes padding up in between slices for PIDs (0x0, 0x100,0x1F). Anyone have some idea what is the use of this..I thought prob these (null..??)packets are causing unnecessary overhead. Any help is highly appreciated. :thanks: