Search found 2245 matches

We don't understand Norwegian here, so this would not help you, to get helped. Plus, mods and admin HAVE to read everything, due to legal reasons. That's why we are strictly limited to english, plus russian in the language section. Regarding subs, what satellite(s) are you watching? Which TXT module...

At least over here, both NTSC relevant device settings now are executed at start time properly. Don't have original NTSC signals here, but I'm testing with overlay frame, that's changing to NTSC525 frame format then, as expected. And the SS21 TV out goes to 60Hz and NTSC color (for OSD at least). No...

Oh come on dear friend, seems, it was a little to early that morning ;) Noone here talked about timeshift in this thread. This is about file playback, in hard mode and ProgDVB. [quote=mlz]In my version Progdvb 4.80.1 the Slider for playback don't work. If I start a video the slider is only in the le...

...partly :? The installer (over?)writes some entries into the ProgDVB.ini To avoid any trouble and always be able to step back, I am installing each and every new version into a new folder, named like the version. Them I'm making a full safety copy of the working version, to another folder with the...

BTW, use the notepad / editor, to look inside of and perhaps edit the .bat files.
The routine for other codecs (not yet available from the system) is similar.
Of course you've got to have the codec you want to install, either in a windows known path, or in the same folder.

Well, I don't know any true NTSC signals available for me from 13°E, 19.2°E, 28.2°E or 30°W. If any existing, please would somebody point me there... My TV equipment is compatible to all existing NTSC, all PAL and even SECAM B/G + D/K (frame and line ID) standards. But I'm only getting OSD, no pictu...

We could also read about this before, both on the old ProgDVB forum and on DVBN.

Seems the device setting for NTSC is not initialized on ProgDVB start time, perhaps the relevant Options.ini setting not read.
May even be a timing issue around firmware loading.

Go to advanced search