Jump to content

DVBViewer GE


Recommended Posts

Sorry folks - updating this topic is long overdue. :( Since DVBViewer GE is a spare time project, it's not possible for me to do everything that should be done. For the same reason there is no complete and up-to-date English manual available in the members area - I hope you understand.


However, I will at least enumerate the main improvements of the last three versions here, and add instructions for multiple instance handling, which is one of the DVBViewer GE 1.7 highlights. Some hints for DVBViewer Pro users are included, since there is no other documentation about this topic available yet.


So let's start:


DVBViewer GE 1.5


- improved OSD (no HTPC stuff, but much better usability than before)


- New options under "Settings -> Options -> Control -> Mouse/OSD". They allow to map the OSD up/down commands to the channellist or favourites, and to reverse the effect of OSD up/down (PC or remote control mode)


- New loader screen


- New toolbar button for opening the scheduler window (-> clock icon)


- Toolbar in the playlist window (similar to the channellist window)


- New option "Settings -> Options -> Recorder -> Write log file". Lets DVBViewer GE write a log file for each recording, including EPG data (if available), format changes and stream errors (missing packets).


- Fast incremental search function for finding a channel in the channellist treeview: Just enter the initial letters. Also applies to the treeview in the scheduler and EPG window.


DVBViewer GE 1.6


- displays radio text (RDS), as broadcasted by the German radio stations on Astra 19° East, 12265 H.


The text shows up in the OSD ("Settings -> Options -> General -> Hide video display in radio mode" must be switched off) or in the status bar. Stations with RDS are marked with an attached "(RDS)", Click the channel name area in the status bar to toggle between the name and the (scrolling) radio text. Please rescan the channels or activate "Channel -> Auto-Update", if RDS detection doesn't work.


DVBViewer GE 1.7


- Reads radio text (RDS) from MP2 and TS files. DVB RDS is stored as ancillary data in the audio stream, thus being included in every audio recording.


- Supports DVB devices with BDA driver (formerly only SkyStar2/ AirStar2/ CableStar2).


- Supports a high compatibility mode for TechniSat cards (required for 64 bit Windows)


- New tab "Settings -> Options -> Hardware" for device settings. Read more about it in the TransEdit manual.


- Instance manager that prevents conflicts between two or more DVBViewer GE instances running at the same time, even if they are launched in different user accounts.


- Audio switching between two or more simultaneously running instances. Click the DVBViewer GE main window that you want to listen to with the middle mouse button.


DVBViewer GE 1.7.1


- some BDA improvements


There is a lot more to say about multiple DVBViewer GE instances. If you own two DVB devices that you want to use simultaneously, please read the following article carefully.

Link to comment

...we continue :(


How to run multiple instances of DVBViewer GE/Pro simultaneously (state of the art...).


A driver for TechniSat cards that enables using two or more of them in one PC is under development, but not yet available. However, some people already bought additional DVB hardware with BDA driver (like me), or two BDA devices. Here is an instruction that tells you how they can be used simultaneously.


Please note: DVBViewer Pro, in contrast to DVBViewer GE, does not check for conflicts between multiple instances yet, so there are some things you have to handle with great care.


First of all, using two DVBViewer instances at the same time requires installing DVBViewer twice in different directories. Additionally, for DVBViewer Pro the file DVBViewer.exe of the second installation must be renamed, e.g. to DVBViewer2.exe.


Furthermore, there are some things that must never happen, otherwise big trouble:


1) Two DVBViewer instances must never access the same configuration files simultaneously (e.g. Setup.ini/.xml, channels.dat, favourites etc. - everything that might be changed while DVBViewer is running).


2) Two DVBViewer instances must never access the same hardware at the same time.


3) Don't use out-dated plug-in and add-on versions. E.g. Videorecorder Plugin versions < 3.2 will cause heavy access violations if they are used by multiple DVBViewer instances.


For avoiding trouble with no-no number 1, it is important to understand the meaning of the file UserMode.ini in the DVBViewer directory. Open it with a text editor. You'll see two entries that specify where the DVBViewer configuration files are stored.


UserMode specifies the user mode in which DVBViewer runs. Possible values are 0, 1 and 2:


UserMode=0: Configuration files are stored in the DVBViewer directory, e.g. in C:\program files\DVBViewer. That's the "classic" mode, but it is not suitable for running DVBViewer in accounts with limited access rights.


UserMode=1: Configuration files are stored in the current user's profile (Documents and Settings\Username\Application Data...).If there are no DVBViewer settings present yet, the default settings are automatically copied from the DVBViewer directory. In this mode each user account has individual settings. Changes applied by user A do not affect user B. This mode is suitable for running DVBViewer in limited accounts.


UserMode=2: Configuration files are stored in the common "all users" profile (Documents and Settings\All Users\Application Data...).If there are no DVBViewer settings present yet, the default settings are automatically copied from the DVBViewer directory In this mode all users resp. accounts share the same settings. Changes applied by user A will affect user B. This mode is also suitable for running DVBViewer in limited accounts.


So, how does the user mode affect multiple instances? In user mode 0, configuration clashes can never occur, since the instances originate from different DVBViewer directories, in which their individual settings are stored. However, if two instances are running both in user mode 1 or both in mode 2, they access the same configuration.


You can avoid the mode 1/2 clash by changing the second entry "Root=..." in the file UserMode.ini. It specifies the name of the DVBViewer configuration folder in the Application Data directory. E.g. if the first instance uses "Root=DVBViewer GE", change the entry in the second UserMode.ini to "Root=DVBViewer GE 2", and everything will be fine.


DVBViewer GE 1.7 and DVBViewer Pro 3.2.5 behave differently in case of a configuration clash. The DVBViewer GE 1.7 instance manager realises it and simply doesn't allow the second GE instance to launch. DVBViewer Pro 3.2.5 doesn't handle it at all, so you have to take care of it.


Now let's avoid clashes resulting from two instances accessing the same hardware. Multiple DVBViewer instances running simulaneously must be configured for different DVB devices. In DVBViewer GE, this is done under "Settings -> Options -> Hardware -> Device", in DVBViewer Pro under "Settings -> Options -> DirectX -> Device".


What happens if two instances try to access the same hardware? Again the DVBViewer GE 1.7 instance manager checks for conflicts. If a DVB hardware is already in use by another GE instance, the second instance will launch, but only as media player. It will refuse to tune a channel, unless configured for a different hardware, or the first instance closes. Thus you may launch two GE instances even if there is only one DVB device.


DVBViewer Pro 3.2.5 does not support this "hands off - I'm already using it" communication yet. So if you want to to use two DVBViewer Pro instances simultaneously (or DVBViewer Pro/GE mixed), first launch them as single instance and make absolutely sure that they are configured for different DVB hardware *before* running them at the same time. Otherwise the device driver's response may be very uncomfortable...


Finally let's talk about audio management. Listening to audio from different sources simultaneously can be quite annoying. Therefore the DVBViewer GE instance manager does its best to let only one instance bother your ears (not perfectly in certain situations, but usable).


If a new GE instance launches, it autmatically grabs audio and mutes all other running GE instances. If you want to listen to a specific GE instance, simply click the main window with the middle mouse button. Again this will mute all other instances. It works similarly to the main window vs. preview window audio management. The preview windows are included in this kind of game, of course. So if you own two DVB devices, you may open four TV windows and assign the audio monopoly to each of them.


DVBViewer Pro does not contain such an audio management, so you will have to handle it by using the mute function of both instances.


That are the main points - now it's up to you to try... :(

Link to comment
  • 2 months later...

It's time to update this topic again, since there is a DVBViewer GE 1.8.4 stable release available in the members area, and a new DVBViewer Pro public beta release - both with remarkable enhancements concerning the usage of two or more DVB devices in a single PC.


First an update of the "Multiple Instances" chapter above: DVBViewer Pro Beta now checks for hardware conflicts and avoids them, like DVBViewer GE, and GE and Pro Beta can run at the same time without a lot of "Don'ts". However, DVBViewer Pro Beta does not support the audio management for multiple instances, since it uses the middle mouse button in a different way.


Now let's deal with the outstanding feature of the new GE and Pro version: A single instance is able to use multiple DVB devices, even of different type. The following description applies to DVBViewer GE, but most of it is handled by DVBViewer Pro Beta in a similar way.


For understanding how it works let's have a look at some typical situations:


- You select a channel in DVBViewer GE. It checks which devices are available for the requested tuner type (DVB-S, DVB-T...) and takes the first one from the top that is free (unused) for playback.


So if you own a DVB-S and a DVB-T device, you can switch between terrestrial and satellite channels without special measures. You will hardly notice the device change.


- You start to record the current channel. The recorder shares the device with the playback section - no need to allocate a second device yet.


- You switch over to a different channel. If it is not on the same transponder (in the same data stream as the recorded channel), or belongs to a different tuner type, a second tuner resp. DVB device is required. So the recorder carries on with device 1, while playback grabs device 2, if available.


- You stop recording. Device 1 becomes free. However, playback always tries to stay with the device that it is currently using. So if you switch over to another channel, it will go on using device 2.


- You start scanning. Since the scanner needs a device exclusively on its own, it first looks for a free device with the requested tuner type. If there is none, it checks if the playback's device would be appropriate. If yes, the scanner takes it away, thus interrupting playback - but it will never grab a device that is currently used for recording.


- A scheduled recording starts. The recorder first checks if it can use the playback's device for it. If playback has one with the same tuner type, and it's tuned to the same transponder, no problem to share it. But if not, the recorder needs a free device. Whoops, there is none left! What to do now? Well, since recording has a high priority, the recorder *forces* playback to switch over to the requested channel, in case the device matches, and then shares it. If even that fails, the recorder finally checks if the scanner occupies a matching device and takes it over, thus merciless interrupting the scan (AFAIK DVBViewer Pro doesn't go so far...).


As you can see, there is cooperation between different DVBViewer sections, but also some hustle may go on if there are not enough DVB devices - so better go and buy some more, in order to prevent a cyber war... ;) well, don't take it serious. Of course DVBViewer GE 1.8.4 and DVBViewer Pro Beta can still be used with only one DVB device, and in general they will behave as former versions. If an action requires a device that is not present, a message box pops up, as before.


Let's conclude this chapter with limitations of the multituner versions:


- DVBViewer GE, in contrast to DVBViewer Pro, has only one internal recorder, so a second recording running simultaneously requires the Videorecorder Plugin (included in the GE package).


- All plugins are "attached" to the device that is used for playback, due to the plugin interface. E.g. if you are recording with the Videorecorder Plugin, it is not possible to switch over to a channel on a different transponder, even if a free device would be available for it.


- The Preview Function is fixed to the device that is used for playback. Thus it only offers channels on the same transponder.


There is still some work to do... however, you can use a second DVBViewer instance (see previous chapter) for extended playback capabilities.


- If a scheduled recording of a DVB-S channel shall start, but no DVB-S device is available at that time, the recording will not be redirected automatically to the according DVB-T or DVB-C channel (and vice versa). The tuner type must match.


Enough to digest? Ok, let's have a pause. I'll continue later with some more details about DVBViewer GE 1.8.4.

Link to comment

Let's proceed...


One thing you should pay attention to is the Hardware Tab in the DVBViewer GE options, and in DVBViewer Pro Beta as well (please read the PDF that is included in the DVBViewer Pro Beta ZIP). In DVBViewer GE it is similar to the Hardware Tab in TransEdit 2.5, so I suggest to first read the according chapter of the TransEdit Manual - saves some writing here.



Additional hardware options in DVBViewer GE 1.8.4:


- Low bandwidth mode: Tick this checkbox for USB 1.1 devices. It lets DVBViewer prevent you from doing things that are too much for the limited USB 1.1 bandwidth, particularly processing two or more TV channels at the same time. This option has no technical effect - it just limits the possible actions in the user interface.


- Shared LNB: Tick this checkbox for DVB-S devices that are connected to the same antenna cable resp. LNB via a two way splitter. LNB sharing implies some restrictions regarding channel selection: If both devices are active, they can only be tuned to channels with the same polarisation, frequency band (high/low, 22 khz signal on/off) and DiSEqC setting. The Shared LNB option lets DVBViewer GE take these restrictions into account when it checks wether a channel selection is possible or not.


This option will be added in DVBViewer Pro too, as I've heard.


- Open whole transponder (TechniSat devices only): Only available in DVBViewer GE. Configures TechniSat cards for receiving the transportstream of the whole transponder, thus enabling the Videorecorder Plugin to list all PIDs that are available in the stream and to record the stuff altogether. Please read more about it in the Videorecorder Plugin Manual and pay attention to the warnings.


Other devices (particularly BDA) don't need this option, since they always provide the complete transportstream.



Other multituner-related enhancements:


- If you want to know what uses which device: The signal strength field of the status bar shows the device that is used by playback as tooltip (BTW: No signal strength display for BDA devices yet - sorry, it's difficult). The recorder's device is displayed in the Recorder Control Window.


- The channel field of the Scheduler Window indicates the tuner type belonging to a scheduled recording with different colors: brown = cable, green = terrestrial, blue = satellite


- In order to find out wether a scheduled recording can be executed or not, DVBViewer GE internally simulates the sequence of recordings, considering overlapping, same transponders, the available devices and the number of installed Video Recorder Plugins. If a recording can not be executed at the specified time, the Scheduler Window displays it in red.


It is recommendable to delete or deactivate scheduled recording that are displayed as not executable. Otherwise they may start later and affect subsequent recordings in a way that is not foreseen by the internal pre-test.



Other recorder-related enhancements:


- When recording in minimized state, the start/stop messages apper as tray balloon tips.


- A new option in the Recorder Control Window: Auto split on channel data change. Lets the recorder check continuously if the channel data on which the recording is based really matches the available streams (by reading the PMT). If not, the recording is stopped immediately and re-started with corrected data. Works similar to Channel -> Auto-Update for playback.


Another measure against the popular disk space-saving 0 byte recordings. :( Please use it with care, since it has not been tested extensively.



Hardware-related enhancements:


- Support for Twinhan devices with WDM driver (no CI support yet).


- BDA DiSEqC support added for FireDTV, Hauppauge Nova-S Plus, Nova-SE2, Twinhan, all devices with TechnoTrend BDA driver (e.g. Nova-S), Terratec 1200-S (untested).



That are the main points, besides a lot of bug-fixes and smaller enhancements. I hope you will accept this enumeration as apology for the non-existing up-to-date English manual. Sorry, but writing it would keep me away from coding for a long time (have a look at the German manual, then you'll know why...).


However, if there are questions, don't hesitate to ask here. ;)

Link to comment

Hi Griga


First i must say, thanx to the team for a really great product

i have been testing alot of diffrent DVB software and this one is beating them all :(


Now two my questen:


- All plugins are "attached" to the device that is used for playback, due to the plugin interface. E.g. if you are recording with the Videorecorder Plugin, it is not possible to switch over to a channel on a different transponder, even if a free device would be available for it.


Is this something that is going to be fixed?

Edited by atener
Link to comment
  • 3 months later...

Hallo Griga,

tanks for the last GE ver., very appreciated the configurable button bar and the powerfull preview!


A unique "bug" I have is a strange remote administration (somewhere it have an annoyng autorepeat, somewhere where is useful it hasn't...)


But... I (and probably many others) cannot understand german (and google translation are funny but not so clear ;) ): can you report also here, in english, all the GE progress??? ;)


Tanks again ;)

Link to comment
can you report also here, in english, all the GE progress???

No, sorry - additionally reporting all the tricky details in English would require much time and keep me away from coding.


Currently German users are testing the version (see members area, beta section), and as soon as we are through with it, I'll post a summary of the main changes / enhancements of the GE 1.9.x versions here.

Link to comment
  • 2 weeks later...

Hi Griga.


Slickest DVB software by far.


The only thing stopping me from using it all the time is the lack of CI support.


Will the GE version include the CI Common Interface option in the future?



Link to comment
Will the GE version include the CI Common Interface option in the future?

Probably not, sorry. DVBViewer GE is more or less a private project, you know... I have no CI, so I wouldn't be able to do any testing. Since I don't want/need all that PayTV stuff, it would be pretty useless to spend money for additional hardware, subscription etc.

Link to comment

Hi Griga,

Im quite new to this forum, i've been using DVBViewer GE for about one month... I want to thank you for the great program, also thanks for the frequent updates!


I have a small request, i don't know how hard is it, but is it possible to increase the size of the OSD "Record" and "Volume" graphics? I am using a 15" TFT (1400*1050 pixels) and it is very hard to see the recording status when watching TV from a 3 meters distance... Especially when starting and stopping recording is triggered with the same key, so it would be nice to see a clear big recording sign on the screen when a recording is taking place.


Thanks for your support,




Link to comment
  • 3 weeks later...

If I remember correctly in early DVBViewer GE versions I could enter and search any number in Frequency under Channel Scan. Now only those predefined in .ini in Transponders are searched. Why was that changed? When searching for satellite feeds often my own transponder details are needed.

Edited by boborg
Link to comment
This topic is now closed to further replies.
  • Create New...