T&V HappyPlayer: FAQ (English version)


Q1: I didn't found my TV-card in the supported equipment list. Are there any chances that T&V HappyPlayer would work with it?

Q2: Video images draws too slow, and then only first points in each line refreshes. What's to do?

Q3: T&V HappyPlayer shows blue screen, auto-scanning switches frequencies, but no image brings. What's to do?

Q4: Video is present, but sound isn't. What's to do?

Q5: T&V HappyPlayer shows gray screen and/or freezes the system. What's to do?

Q6: Auto-scanning finds superfluous channels without image or with other channels' copies. Whatta hell?

Q7: Auto-scanning doesn't find some channels, which are successfully found by my TV set. What's to do?

Q8: Why the remote controller doesn't work?

Q9: Why the image refreshes so slowly in /BUF mode?

Q1: I didn't found my TV-card in the supported equipment list. Are there any chances that T&V HappyPlayer would work with it?

A1: The simpliest way is to run the program and check the result. It's unlikely to spoil something this way, because T&V HappyPlayer simply wouldn't work with unknown chips. Read about /TV command-line parameter in readme2.eng file. The common rule is that T&V HappyPlayer potentially can work with the majority of PCI tuners on Brooktree 848A and higher chips, but some code modifications could be required for some models (this question may be discussed by the authors). From another side, work with videocard-integrated tuners (e.g. S3 and Cirrus Logic) is definitely impossible, as well as with thouse which connects to videocard through the feature connector (e.g. ATI TV Tuner) or plugs directly to cable from videocard to monitor (e.g. Tekram M200). All those cards works completely different, and their software must be designed another way than T&V HappyPlayer.

Q2: Video images draws too slow, and then only first points in each line refreshes. What's to do?

A2: The reason is too slow one-way video memory (EDO DRAM) installed in your videocard, which lacks simultaneous reading pixels with monitor refresh frequency to display video and writing them with TV frame rate frequency to draw TV image in the window. You must decrease video resolution or color depth or refresh rate. The alternate way is to change memory in videocard to faster one, and even better - to two-way one (VRAM/SGRAM), or, if this is impossible, to change your videocard to faster one. One another way is to decrease TV frame rate with the /DEC command-line switch.

Q3: T&V HappyPlayer shows blue screen, auto-scanning switches frequencies, but no image brings. What's to do?

A3: First of all, check that your card is plugged to TV cable and try to run it's own software. Check that you specified right TV-card model with /TV command-line switch (see readme2.eng file). Try to switch video source with 'i' key. If you cannot get TV image that way, but can get test table consisting of vertical color bars, than the program recognized your videodecoder but can't recognize TV-tuner scheme or the way it connected. Search for up-to-date T&V HappyPlayer version or contact for support through USL.SUPPORT echoconference or directly to the authors, and don't forget to note your TV-card and tuner (large metal box on the card) models. If you can't get the table, it seems like a bug. Tell the authors about it, and send the description of your PC' configuration, including detailed description of TV-card and videocard, videodriver version, and description of other installed cards and peripherial devices.

Q4: Video is present, but sound isn't. What's to do?

A4: The program can't recognize the way your TV-tuner connected to videodecoder. See A3.

Q5: T&V HappyPlayer shows gray screen and/or freezes the system. What's to do?

A5: The problem is caused by the architecture of your videocard or by the bugs of the videodriver. First of all, reboot your system, pushing Reset key or switching computer off, because the TV-card can remain freezed. Try to run T&V HappyPlayer with /BUF command-line switch. Another way is to change the videodriver to another version or another architecture (e.g. the program can't work with S3 Trio 64V+ videocard using GRADD 0.079 drivers, but can do it using native driver 3.03.16; it can't work with CL54M30 using GENGRADD, but can work in /BUF mode only using native driver from Warp 4 distributive). Theoretically, some configurations are possible which can require the switch /VMEM:2. People says that disabling Bus Concurrency, Streaming or Peer Concurrency in BIOS also can help.

Q6: Auto-scanning finds superfluous channels without image or with other channels' copies. Whatta hell?

A6: This problem may be caused by non-optimal receiving of TV signals. Simply delete superfluous channels from configuration file, channels.dat.

Q7: Auto-scanning doesn't find some channels, which are successfully found by my TV set. What's to do?

A7: This may be caused by low TV signal quality, which is unappropriate for your TV-tuner, but is appropriate for your TV set. Try to repeat auto-scanning. If that wouldn't help, you can include those channels in configuration file manually, but the image quality would be likely too bad. Try to contact your TV-provider.

Q8: Why the remote controller doesn't work?

A8: Remote controller is a completely separate unit, which has virtually no common with other TV-card equipment. May be, some software would be written in feature to support it.

Q9: Why the image refreshes so slowly in /BUF mode?

A9: In buffered mode the CPU does all work on video image refreshing, not the Brooktree RISC-processor. So, slow CPUs couldn't make this work completely, especially if there are another running processes. Moreover, the /BUF mode is designed as last-chance option, not the usual work mode, so we didn't very much work on optimizing clipping in this mode. As the result, an acceptable perfomance in buffered mode could be reached only in the case where T&V HappyPlayer window isn't overclipped by another windows.


Интересные ссылки:
Комментариев к странице: 0 | Добавить комментарий
Домой | Проект ядро Core/2 | Проект OS/4 Download | Новости | Гостевая книга | Подробно обо всем | Нужные программы | Проекты | OS/2 FAQ | Всячина | За и Против | Металлолом | #OS2Russian | RDM/2 | Весёлые картинки | Наша галерея | Доска объявлений | Карта сайта | ПОИСК | ФОРУМ