Trying to get a Genpix working with VDR.
I thought my troubles started when Reinhard posted his new vdr-1.5.12-h264-syncearly-framespersec-audioindexer-fielddetection.diff cause I got compile errors, (should of known better).
But after digging back thru all the old patches I could find I believe this has been wrong for awhile.
What is/was wrong was that the ‘switch (frontendType)‘ function did not open and close the ‘{‘ ‘}’ properly (thankz Reinhard for pointing it out) after the patch.
The original code is like this
switch (frontendType) {
case FE_QPSK: { // DVB-S
The patched code looks like this
switch (frontendType) {
case FE_QPSK: // DVB-S
case FE_DVB_S: // DVB-S
case FE_DVB_S2: // DVB-S
As you can see the last ‘{‘ is missing and a ‘}’ had tobe removed later down in the code to make things happy. That is why I wonder how the patch has been working in the past.
I tried to add the ‘{‘ in after the S2 and leave the removed 1 in but it wouldn’t compile, (figured that be too easy).
What I have done is put the original ‘case FE_QPSK: { // DVB-S’ routine back into dvbdevice.c and have added a new ‘case FE_DVB_S: { // DVB-S’ that mirrors ‘case FE_QPSK: { // DVB-S’ routine and made a new ‘case FE_DVB_S2: { // DVB-S’ routine under the switch.
I am no coder by any means but can cut and paste with the best of them. It does seem to patch and compile fine but really unsure if what I did will be ok.
Was wondering if someone with a little more knowledge than me could take a look @ the patch and see if it all looks ok.
Thankz
No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.16.9/1155 - Release Date: 11/27/2007 8:30 PM
Hi,
ShorTie schrieb:
I tried to add the ‘{‘ in after the S2 and leave the removed 1 in but it wouldn’t compile, (figured that be too easy).
Seems like my instructions were not clear enough. The attached patch contains the mentioned modifications. Compiles here with some cheats. No further tests run.
Bye.
My G550's DVI port is connected TV's HDMI. On software side have tried xineliboutput's remote frontends. Otherwise everything is fine but I have small issues with both X and DirectFB.
1. With vdr-sxfe I seem to have some tearing effect. Does XV support sync-to-vblank?
2. With DirectFB the output seems to be limited to 16 bit colors. The pixelformat and depth values should be OK in /etc/directfbrc.
Both setups are using 720p50.
Any advice which one is easier to solve? And how?
- Kimmo
On 29 Nov 2007, at 16:07, Kimmo Taskinen wrote:
With more recent versions of DirectFB, the configuration file might be expected to be in /usr/local/etc.
I'd also recommend you trying softdevice output with a G550. It works quite well, but I'm biased though..
On Nov 29, 2007 6:07 PM, Kimmo Taskinen kimmo.taskinen@dnainternet.net wrote:
Yes its does. You can use xvinfo and xvattr to see the current settings, and xvattr to set them.
-Petri
Thanks for the answers. I also got personal mail with patch for the DirectFB color problem. With DirectFB I could not get good enough deinterlace setup. And I could not solve the tearing problem with XV. But fortunately I got very good result with vidixfb video driver.
/usr/bin/vdr-fbfe --video vidixfb --fullscreen --aspect=auto --post tvtime:method=Greedy2Frame,cheap_mode=0,pulldown=0,framerate_mode=full,use_progressive_frame_flag=1 --reconnect
mode "1280x720-50" # D: 74.250 MHz, H: 37.500 kHz, V: 50.000 Hz geometry 1280 720 1280 720 32 timings 13468 212 448 20 5 40 5 hsync high vsync high accel true rgba 8/16,8/8,8/0,8/24 endmode
CPU load is about 35% with Athlon 2500+ XP-M.
- Kimmo
Petri Helin wrote:
-
Kimmo Taskinen -
Petri Helin -
Reinhard Nissl -
ShorTie -
Torgeir Veimo