If you have ever wanted to test DVBStreamExplorer export to WS features but gave up because of the hassle of creating a web service, then check out http://www.jensvaaben.com/dvbsewstest/.
It will allow you to export directly from DVBStreamExplorer to a live web service. Afterwards you can view the data that you have exported. Detailed instructions on http://www.jensvaaben.com/dvbsewstest/.
Sunday, 23 June 2013
Saturday, 2 February 2013
TS File Demux split PES/ES files on continuity error
TS File Demux V2.1.8 has just been released. A new feature has been introduced that will allow PES/ES files to be split whenever a continuity error is detected in TS packet.
In previous version you could end up with PES/ES files with missed packets due to continuity error in TS packet.
It might be desirable to produce PES/ES files without missed packets. The new feature will split PES/ES files every time continuity error is detected in TS packet for the PID in question. A new file will be created with name derived from the base name of PES/ES file and .001, .002 etc appended.
Below is shown a screenshot below of output folder where split PES files have been created.
NOTE:
In previous version you could end up with PES/ES files with missed packets due to continuity error in TS packet.
It might be desirable to produce PES/ES files without missed packets. The new feature will split PES/ES files every time continuity error is detected in TS packet for the PID in question. A new file will be created with name derived from the base name of PES/ES file and .001, .002 etc appended.
Below is shown a screenshot below of output folder where split PES files have been created.
NOTE:
- Only TS packet header is decoded in order to detect continuity errors. Content of PES/ES packet is not decoded and/or analyzed in any way.
- This option can cause an excessive number of files to be created in output folder if there are a lot of continuity errors in TS file.
Friday, 1 February 2013
DVBStreamExplorer V4.0 configuration changes
Introduction
A new feature in DVBStreamExplorer V4.0 is the ability to run multiple instances. This feature is described in following blog post: Running multiple instances of DVBStreamExplorer. Introduction of this feature has some effect on how DVBStreamExplorer handles configuration and logging compared to DVBStreamExplorer V3.0.
Configuration
In DVBStreamExplorer V3.0 all configuration data, excpet for MUX lists, was stored globally while MUX lists were stored in context of the selected device.
With the introductiion of multiple running instances this was not pratical since changes made in one running instance would affect configuration in another running instance.
As a consequence all configuration is now stored in the context of selected device. This has the negative side effect that all custom configuration done must be applied for each device that you are using with DVBStreamExplorer. However that would seem a reasonable price to pay for the ability to run multiple instances of DVBStreamExplorer.
With the introductiion of multiple running instances this was not pratical since changes made in one running instance would affect configuration in another running instance.
As a consequence all configuration is now stored in the context of selected device. This has the negative side effect that all custom configuration done must be applied for each device that you are using with DVBStreamExplorer. However that would seem a reasonable price to pay for the ability to run multiple instances of DVBStreamExplorer.
Logging
When options preferences window is opened following will show.
Here the logging folder is shown. In DVBStreamExplorer V3.0 log files are saved in the root of this folder. In DVBStreamExplorer V4.0 log files are saved in subfolders of this folder. Each subfolder is created at run-time with a name derived from process ID of running DVBStreamExplorer instance. A negative side effect is that these subfolders with content are left behind and accumulate used disk space over time. This issue will be addressed in a future release. Until then it is advised to clean up log folder from time to time. Note that log files are not really targeted application user. They are intended to be used by DVBStreamExplorer author to troubleshoot any issues found.
Here the logging folder is shown. In DVBStreamExplorer V3.0 log files are saved in the root of this folder. In DVBStreamExplorer V4.0 log files are saved in subfolders of this folder. Each subfolder is created at run-time with a name derived from process ID of running DVBStreamExplorer instance. A negative side effect is that these subfolders with content are left behind and accumulate used disk space over time. This issue will be addressed in a future release. Until then it is advised to clean up log folder from time to time. Note that log files are not really targeted application user. They are intended to be used by DVBStreamExplorer author to troubleshoot any issues found.
Thursday, 24 January 2013
Running multiple instances of DVBStreamExplorer
When DVBStreamExplorer V3 is launched and another instance is already running one is faced with message below.
This limitation has been removed in DVBStreamExplorer V4 which has just been released.
Below is a screenshot from a Windows desktop where two instances of DVBStreamExplorer are running. One instance is scanning DVB-T data from a Cinergy HTC USB XS DVB-T Tuner and the other is scanning DVB-S data from TBS5925 DVB-S2 TV Tuner USB.
As a convenience DVBStreamExplorer application window title bar now includes name of capture device.
This limitation has been removed in DVBStreamExplorer V4 which has just been released.
Below is a screenshot from a Windows desktop where two instances of DVBStreamExplorer are running. One instance is scanning DVB-T data from a Cinergy HTC USB XS DVB-T Tuner and the other is scanning DVB-S data from TBS5925 DVB-S2 TV Tuner USB.
As a convenience DVBStreamExplorer application window title bar now includes name of capture device.
Monday, 31 December 2012
Decoding user defined Nordig, DTG (D-Book) and IEC 62216 (E-Book) descriptors
Next version of DVBStreamExplorer will include the option to select which syntax to be used for decoding of user defined (0x80 - 0xFE) descriptors.
This is of special interest with regards to Logical Channel Number descriptors which are defined in each of the above standards except for EN 300 468. While the syntax is very similar in the standards, there are minor differences regarding the allocation of bits for each field.
The standard to be used for decoding can be selected in DVB PSI/SI / Multiple DVB-S/T/C MUX scanning window before starting scan operation. See screenshot below.
On SI scan completion you can switch to service view. A new 'lcn' column has been added. A value of -1 means that there was no LCN descriptor applicable for service. See screen shot below.
LCN information is also shown for each service found in MUX in DVB TS Monitor. Like for for SI scanning the syntax to be used for decoding has to be selected before starting scan operation. See screenshot below.
Finally LCN information has also been added as a new field to the CVS export of service information.
While LCN descriptor is probably the one of most interest, other user defined (0x80 - 0xFE) descriptors will also be decoded. You will find these in the various descriptor loops of decoded sections.
Follow +DVBStreamExplorer to keep up to date with DVBStreamExplorer related news.
The standard to be used for decoding can be selected in DVB PSI/SI / Multiple DVB-S/T/C MUX scanning window before starting scan operation. See screenshot below.
On SI scan completion you can switch to service view. A new 'lcn' column has been added. A value of -1 means that there was no LCN descriptor applicable for service. See screen shot below.
LCN information is also shown for each service found in MUX in DVB TS Monitor. Like for for SI scanning the syntax to be used for decoding has to be selected before starting scan operation. See screenshot below.
While LCN descriptor is probably the one of most interest, other user defined (0x80 - 0xFE) descriptors will also be decoded. You will find these in the various descriptor loops of decoded sections.
Follow +DVBStreamExplorer to keep up to date with DVBStreamExplorer related news.
Sunday, 25 November 2012
Export to folder after SI scan in DVBStreamExplorer
If you are using DVBStreamExplorer to scan entire DVB, ATSC or ISDB networks for PSI/SI/PSIP information, you might appreciate a new feature in DVBStreamExplorer Professional Edition V3.0.113 that allows you to have various files exported and saved automatically when PSI/SI/PSIP scan is completed. Note that this feature is only applicable for 'Multiple * MUX scanning' features found in PSI/SI/PSIP menu.
The new feature can be enabled from Options / Preferences / SI scan page as shown below.
Here you can enable/disable the feature, select destination folder and select which file types you want to export.
'Save SI XML' corresponds to File / Save/Save As file, which is a file type that can be loaded by DVBStreamExplorer for offline viewing of PSI/SI/PSIP information.
'Save service XML' and 'Save CSV' corresponds to options found in File / Export / XML and File / Export / CSV.
All files will be saved in specified folder. File name will be automatically generated based on network type, export type and date/time of export. The date/time part of file name is based on, but does not necessarily strictly conform to, ISO 8601. The time is specified in UTC to allow files to be easily exchanged between different time zones.
The new feature can be enabled from Options / Preferences / SI scan page as shown below.
Here you can enable/disable the feature, select destination folder and select which file types you want to export.
'Save SI XML' corresponds to File / Save/Save As file, which is a file type that can be loaded by DVBStreamExplorer for offline viewing of PSI/SI/PSIP information.
'Save service XML' and 'Save CSV' corresponds to options found in File / Export / XML and File / Export / CSV.
All files will be saved in specified folder. File name will be automatically generated based on network type, export type and date/time of export. The date/time part of file name is based on, but does not necessarily strictly conform to, ISO 8601. The time is specified in UTC to allow files to be easily exchanged between different time zones.
BDA tuner configuration in DVBStreamExplorer
DVBStreamExplorer V3.0.113 fixes a problem that it would fail to initialize some BDA devices on Windows 7. The old device selection box looked like below.
In case of device initialization failure you would see a message like below when starting application.
While fixing this issue, it was found that the application was not always able to reliably detect BDA tuner configuration. I.e. it was possible that a DVB-T device could be detected as DVB-S device.
You can verify how your BDA tuner device was detected by application by opening Device / Settings page.
Below is a screenshot showing how a DVB-C device was detected as DVB-S.
As a workaround a new feature has been added, so that it is now possible to specify network (tuner) type when selecting device during application launch.
The new device selection box is shown below.
You can select between auto detect, DVB-S, DVB-T, DVB-C and ATSC.
It is recommended to first try with auto detect. If then network type is not detected correctly by application, you will need to specify correct network type when launching application.
Note that application can only remember the last network type used. So if you change between different BDA device types, you will have to specify correct network type every time you launch application unless you are using auto detect option.
While fixing this issue, it was found that the application was not always able to reliably detect BDA tuner configuration. I.e. it was possible that a DVB-T device could be detected as DVB-S device.
You can verify how your BDA tuner device was detected by application by opening Device / Settings page.
Below is a screenshot showing how a DVB-C device was detected as DVB-S.
As a workaround a new feature has been added, so that it is now possible to specify network (tuner) type when selecting device during application launch.
The new device selection box is shown below.
You can select between auto detect, DVB-S, DVB-T, DVB-C and ATSC.
It is recommended to first try with auto detect. If then network type is not detected correctly by application, you will need to specify correct network type when launching application.
Note that application can only remember the last network type used. So if you change between different BDA device types, you will have to specify correct network type every time you launch application unless you are using auto detect option.
Subscribe to:
Posts (Atom)