-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 1.19 released #74
Comments
dvb.bat does not work here unless I put lib\opencsv-5.5.2.jar from 1.18.0. New version that is packaged does not work. |
Thank you for reporting this, fixed in 1.19.1. |
d:\DVBinspector>java -classpath .;.\lib\jfreechart-1.5.3.jar;.\lib\opencsv-5.7.1.jar;.\lib\jlayer-1.0.1.4.jar;.\lib\commons-text-1.9.jar;.\lib\commons-logging-1.2.jar;.\lib\commons-lang3-3.12.0.jar;.\lib\commons-collections4-4.4.jar;.\lib\commons-collections-3.2.2.jar;.\lib\commons-beanutils-1.9.4.jar;.\DVBinspector.jar -Djava.util.logging.config.file=src/main/resources/logging.properties nl.digitalekabeltelevisie.main.DVBinspector d:\DVBinspector> |
@EnoSat For DVB Inspector you need to have at least java version 17. From the stack trace I think you are still on java 8 (or 1.8) The next version of DVB Inspector will need java 21, so its better to upgrade to java 21. |
Hi, Can JDK 23 also be used? |
Just released version 1.19
Most obvious change in this release is the LookAndFeel. Until now DVB Inspector used the "SystemLookAndFeel", where java tries to look as much as possible like a native application. I noticed for Windows with a 4K hiDPI screen this resulted in long start up times (>20 seconds) The performance is much better with the java default LookAndFeel.
A larger change is the support for AVCHD/Blu-ray M2TS files. DVB Inspector is and always will be a DVB analyzer first. But a lot of people (ab)used it by parsing m2ts streams, like used in Blu-ray and/or video-camera's. AVCHD uses 192 byte packets, but the 4 extra bytes are at the start of the packet (and contain a TP_header with arrival time information). DVB Inspector presented those packets with 4 extra bytes at the and, but those 4 bytes belonged to the next packet.
This is now fixed, streams with 192 bytes packet size will always be handled as AVCHD streams with the TP_header at the start of the packet. The timing info in the packets is now also used for calculations, so the various charts now correctly handle VBR AVCHD streams.
For all other packet size DVB Inspector still expects constant bitrate full MPEG transport streams.
Feedback/ bug reports are, as always, welcome.
The text was updated successfully, but these errors were encountered: