> Love to but I deleted them from vdr already. I don't know if FFMPEG was > actually doing anything because I couldn't get anything to show -- it > was encoding.. what who knows. I'm in Canada btw -- is that the same > area? Well, the same landmass and TV standard :) I'm a New Zealander, lived in the UK for several years using VDR with DVB-T, moved to Washington 3 months ago > I have a Hauppauge WinTV to GO card -- basic analog no encoder and not > supported by ivtv. Apparently its much easier if you have a card > supported by ivtv. Mine's a WinTV-USB2 - similarly not supported by ivtv >> KOMOTEST1:4:B7C12D0:C:0:301:300:0:32001:0:0:0:0 Where did you come up with the 301/300? > I've made some changes to the above that I used to get some output. I > also use C0 rather then C12 but that varies depending on your card. > You also need to put in a frequency instead of the '4'. I don't recall > the program I used to get them but I know xawtv will show them as well. I can't get xawtv to work for FC5 :( I wasn't sure about the frequency - as tvtime just stores 'channel 4' and not the frequency. So didn't know what the thing wanted in the way of channel definitions. > When you run VDR at the console, you should see it trying to start > ffmpeg -- does it give you an error? I also had issue where the plugin > had configured PAL resolutions and no NTSC resolutions so FFMPEG had > issues with the mixed command line for NTSC but a PAL resolution that > was incompatible. It involved modifying the source code to get it past > that point. If this is the blocker, it should give you an error in the > vdr output though... I don't get anything on the console when I change channels??? > Also, did you apply all the recommended patches from the vdr wiki page? > I use the German pages because the english ones are way out of date for > most of the plugins. I applied all the patches against VDR - but no others. > Norm Simon
