Trouble Shooting

Trouble Shooting

I have tried to make DVB Inspector as robust as possible. Most errors will result in a pop up message telling you what happened, and which error occurred. However sometimes you need some more info.

Smaller input file

If DVB inspector crashes or gives unexpected errors you can always try to use smaller input files. This may prevent out of memory errors. A file < 100 MB should be fine.

Also sometimes a capture card or generator will produce 'illegal' data at beginning or end of a stream. Try to split your input file into multiple pieces using a program like 7-Zip file manager, FreeCommander or HJSplit. Either a piece from the beginning, middle or end might just work.

Out of memory

Sometimes DVB Inspector needs more memory. Especially parsing PES streams uses a lot of memory. The default settings for java may not provide enough memory. If you start DVB Inspector by clicking the DVBinspector-1.x.0.jar java will use a default setting for heap memory, depending on your machines available memory. Try to use dvb.bat (or dvb.sh for linux) and modify it to include a larger value for heapsize with the -xMx flag;

java -classpath .;.\lib\jfreechart-1.0.13.jar;.\lib\jcommon-1.0.16.jar;.\lib\opencsv-2.1.jar;.\lib\jlayer-1.0.1-1.jar;.\DVBinspector.jar -Xmx1000m -Djava.util.logging.config.file=src/main/resources/logging.properties nl.digitalekabeltelevisie.main.DVBinspector

DVB.bat

When DVB Inspector is started from dvb.bat (windows) or dvb.sh (linux/unix) a command window will be opened where some logging is displayed. The output in this window may help in determining the problem.

This page was last modified on 7/01/2017