Bugs item #1566574, was opened at 2006-09-27 21:09 Message generated for change (Comment added) made by duncanwebb You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=446895&aid=1566574&group_id=46652
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: other Group: 1.5.x svn Status: Open Resolution: None >Priority: 7 Submitted By: John Molohan (johnmolohan) Assigned to: Nobody/Anonymous (nobody) Summary: Frequency not being set with ivtv 0.7.0 Initial Comment: Hi, Freevo isn't setting the frequency with revision 8248 and ivtv 0.7.0. I can't see where this is failing but I guess that some of the v4l stuff has changed for this version of ivtv. >From freevo's logs I get: tvguide.py (142): TVGUIDE EVENT is MENU_SELECT main.py (465): clear: True Video Opened at /dev/video0 USING STANDARD FREQUENCY: chan="A7", freq="176000" Video Opened at /dev/video0 rc.py (425): register callback: <bound method ChildApp2.poll of <childapp.ChildApp2 instance at 0xb44b5bcc>> rc.py (421): register shutdown callback: <bound method ChildApp2.stop of <childapp.ChildApp2 instance at 0xb44b5bcc>> logging child to "/var/log/freevo/mplayer-stdout.log" logging child to "/var/log/freevo/mplayer-stderr.log" self.t1.isAlive()=True, self.t2.isAlive()=True ChildApp.__init__(), pid=5712, app= /usr/bin/mplayer -vo xv,sdl,x11, -ao oss:/dev/dsp -fs -autosync 100 -nolirc -autoq 100 -screenw 800 -screenh 600 -fs -slave -cache 8192 /dev/video0, poll=-1 main.py (465): clear: True Which all looks good. I've turned on debugging on the ivtv driver and see this in /var/log/messages Sep 27 19:57:28 freevo kernel: ivtv0 info: v4l2 ioctl: set frequency 2816 Mplayer runs but the channel is never tuned. I can set different frequencies manually with ivtv-tune. Any ideas? ---------------------------------------------------------------------- >Comment By: Duncan Webb (duncanwebb) Date: 2006-09-28 19:30 Message: Logged In: YES user_id=104395 There are a few problems at the moment with some of the ivtv calls. The problem is the API calls have been moved from calls like IVTV_IOC.. into the V4L calls :-(. This means that it is unsafe at the moment to use freevo and *ivtv* drivers greater than the 0.4.x. I have increased the priority of this problem, because as people upgrade the kernel more and more problems will be reported. ---------------------------------------------------------------------- Comment By: Duncan Webb (duncanwebb) Date: 2006-09-28 16:36 Message: Logged In: YES user_id=104395 Will you post the dmesg for ivtv The attached script helps to extract the ivtv stuff to ivtv.log. I'm just checking this against ivtv-0.8.0 and kernel-2.6.18. I found that I hadn't all the new modules being build. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=446895&aid=1566574&group_id=46652 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Freevo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-devel
