Support
| Contact | ||
|---|---|---|
 | Sales |  |
 | Support | |
 | Information | |
Software Version
Please check that you have the most recent version of the MPEG-2 Transport Stream Analyzer.
| Product | Current Version | Operating System | Release Notes |
|---|---|---|---|
| MP2TSAE | V5.0 | Windows, OS X, Linux | mp2tsae-relnotes-5.0.pdf |
We encourage all users to stay up to date with the current version. For upgrade and maintenance agreement information, please contact sales@manzanitasystems.com.
Frequently Asked Questions
Please check to see if your question about out MPEG-2 Transport Stream Analyzer products (MP2TSA and MP2TSAE) is answered here. If your question still has not been answered, please contact our tech support department at support@manzanitasystems.com.
- When I look at the PID Summary, why do I see many instances of the same PID?
- If a PID stream has changed certain characteristics during the transport stream, a new entry will be made in the PID Summary. The differences between the two instances can be determined by comparing the Properties of each. See the section, PID Summary Pane, for a discussion of PID stream instances.
- When I try to analyze a file which I thought was VBR I get an error about PCRs on more than one PID and the analysis stops. What does this mean?
- MPEG only allows VBR streams to have a single PCR PID. If your file has more than one PCR PID, then it can not be VBR. Try the analysis again, but use the 'Auto' setting for the rate. The stream must be CBR.
- I get a warning that my bit_rate field was 3.18 Mbps, but the actual rate was 3180023 bps. What does this mean?
- The analyzer reports both the rate as defined in the elementary stream syntax and also the rate which was measured over the duration of the stream. If the measured rate is higher than the rate specified in the syntax, this warning is issued. Small differences may probably be ignored. A large difference may cause problems with downstream equipment if it uses the rate in the syntax.
- My file has a single warning about a PCR discontinuity indicator in the first PCR packet. It says this is usually OK, but what does this mean?
- The discontinuity_indicator tells the decoder that something is changing beginning with this packet. There are several types of discontinuities, but this once indicates there is a time base discontinuity. This is almost always needed with the first PCR in a file because this tells the decoder that the system clock has changed and it should reload using this PCR value. This warning is expected and can be ignored. Note that the CableLabs profile requires this discontinuity be set, so no warning is issued when verifying a valid CableLabs stream.
- I am analyzing a file with 196 byte packets and I notice the PID rate plot and transport analysis rate values don't add up to my real data rate. Why not?
- MP2TSAE bases the analysis on 188 byte packets, so the extra inter-packet data is ignored both in the analysis results and by the PID Rate Plot Tool.
- I analyzed a stream which had PCR jitter and clock frequency errors. When I plot the PCR for this PID using the PCR Plot Tool, I do not see any jitter, only the excessive clock frequency. Where is the jitter reported by the analyzer?
- The analyzer begins verifying the PCRs assuming the encoder has a legal PCR clock, so it will report jitter errors when the clock frequency is out of spec. The PCR plot will show the computed clock frequency and the jitter based on a clock with the computed frequency, so the plot is a better representation of what is probably happening in the encoder.
- I have a stream that contains audio at 192 kbps. I looked at the stream with the PID Rate Plot Tool. The rate of the stream appears to have peaks at about 300 kpbs. Why is the rate so high?
- MP2TSAE measures the rate over a 10 ms window. This is a very narrow window and when rates are low there will be fluctuation due to the packet locations. For 192 kbps audio, this is about a 200 kbps transport rate, which is a packet every 200000 / 1504 = 7.5 ms. Assuming uniform distribution of packets, in some 10 ms windows you will see one packet, and in others you will see two packets. One packet over 10ms = 1504 bits / 0.01 sec = 150400 bps, while two packets over 10ms = 3008 bits / 0.01 = 300800 bps. Because the window isn't exactly 10ms, you should see fluctuations around 300 kbps. They should spike up to 300 kbps and then drop down to 150 kbps, then back up, etc. The plot will oscillate due to the interaction of packet locations and the sample window.