Hello Britney, On Wed, May 6, 2009 at 5:02 PM, Britney Fransen <britney.fransen@xxxxxxxxx> wrote: > On May 6, 2009, at 1:50 PM, Devin Heitmueller wrote: > >> First off, the QAM64 patches that Frank provided have not been merged >> it. It's on my todo list. > > I see that now. Weird that MythTV is tuning the QAM64 channel now. Could > it be related to the DVB-T additions? Could the DVB-T additions cause the > QAM256 corruption I am seeing? I don't see how that could be the issue. However, if you want to confirm, you can just roll back that patch and see if it makes a difference. >> Has the MythTV situation gotten *worse* with this code compared to the >> current v4l-dvb tip? It would not surprise me if there are some >> general MythTV issues with the 950q (I am in the process of building a >> MythTV box so I can test/debug). However, I would be surprised if >> there were *new* issues. > > Looking at the MythTV logs I would say the situation is better as there are > fewer errors. It returns to the menu much quicker so it could just be that > it is failing before it hits a timeout. Well, it may return faster if the firmware is already loaded, since the 3 second tuning request now only takes 300ms. >> I do know that mkrufky was mentioning there >> was some sort of way to tell MythTV about hybrid devices, so that the >> application doesn't try to use both the analog and digital at the same >> time - and if you didn't do that then this could explain your issue. > > I believe that mkrufky is referring to input groups. I do have the analog > and digital set to the same group. Ok. Well if you're getting mplayer problems too, then it's probably not the input groups. >> Regarding the mplayer issue, please try this: >> >> <unplug the 950q> >> cd v4l-dvb >> make unload >> modprobe xc5000 no_poweroff=1 >> <plug in the 950q> >> >> ... and then see if mplayer still has issues. This might be somehow >> related to the firmware having to be reloaded taking too long for >> mplayer (the firmware has to be reloaded when the chip is woken up >> after being powered down). > > Did that and it still failed with the following (same as before): > Playing dvb://2@FOX. > FE_GET_INFO error: 19, FD: 4 > > DVB CONFIGURATION IS EMPTY, exit > Failed to open dvb://2@FOX. > > FOX is the first entry in my .mplayer/channels.conf file. Could you try using azap to tune? It seems like you have a basic tuning problem, independent of the application. So, let's forget about MythTV for now and focus on the low level tools like mplayer/azap until we are confident that works. If you want to help debug this, try rolling back the individual patches until you either get to the starting point of the series or the code starts working. Once we know which patch causes it to start failing, we can go from there. Devin -- Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
