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: Pending
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-10-04 13:32
Message:
Logged In: YES
user_id=104395
I hadn't spotted this before but for 64bit machines this is
incorrect.
32bit gave:
Width: 720, Height: 576
64bit gave:
Width: 0, Height: 720
This should now be fixed in r8316.
----------------------------------------------------------------------
Comment By: Duncan Webb (duncanwebb)
Date: 2006-09-29 00:54
Message:
Logged In: YES
user_id=104395
I should also have said that all the calls are now
little-endian, but this may be incorrect for processors that
are big-endian.
Does anybody use a big-endian machine and if so can they run
the v4l2 module?
With a i386 machine with ivtv-0.8.0 the output is:
python ../src/tv/v4l2.py
QUERYCAP_ST=<16s32s32sII16x 104
FREQUENCY_ST=<III32x 44
ENUMSTD_ST=<IQ24s2II16x 64
STANDARD_ST=<Q 8
ENUMINPUT_ST=<I32sIIIQI16x 76
INPUT_ST=<I 4
FMT_ST=<I7I4x168x 204
TUNER_ST=<L32sLLLLLLll16x 84
AUDIO_ST=<L32sLL8x 52
Driver: ivtv
Card: Hauppauge WinTV PVR-350
Version: 800
Capabilities: 17236211
Enumerating supported Standards.
0: 0xf PAL-BGH
1: 0xe0 PAL-DK
2: 0x10 PAL-I
3: 0x100 PAL-M
4: 0x200 PAL-N
5: 0x400 PAL-Nc
6: 0xd0000 SECAM-BGH
7: 0x320000 SECAM-DK
8: 0x400000 SECAM-L
9: 0x800000 SECAM-L'
10: 0x1000 NTSC-M
11: 0x2000 NTSC-J
12: 0x8000 NTSC-K
Current Standard is: 0xff
Enumerating supported Inputs.
0: Tuner 1
1: S-Video 1
2: Composite 1
3: S-Video 2
4: Composite 2
5: Composite 3
Input: 0
Width: 720, Height: 576
Read Frequency: 0
('ivtv\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
'Hauppauge WinTV PVR-350\x00\x00\x00\x00\x00\x00\x00\x00\x00',
'0000:02:0b.0\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
2048L, 17236211L)
viddev.getinput=0
viddev.setinput okay
viddev.getfmt=1
(0L, 'Tuner
1\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
1L,
7L, 0L, 255L, 0L)
(0L, 'ivtv TV
Tuner\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
2L, 112L, 0L, 0L, 2L,
1L, 65535, 0)
(0L, 'Tuner
1\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
1L,
0L)
None
2132
None
8948
(0L, 2L, 8948L)
It's a bit different than ivtv-0.4.6!
----------------------------------------------------------------------
Comment By: Duncan Webb (duncanwebb)
Date: 2006-09-29 00:39
Message:
Logged In: YES
user_id=104395
I've committed r8249 which has the fix for this. The problem
is that the second argument to the set frequency command
should have been 2 for V4L2_TUNER_ANALOG_TV.
Also in this commit there are some changes for AMG64 bit
code, more than I expected.
Plus at the bottom some test code so that the v4l2.py
modules can be run standalone it gives this output on an amd64:
# python v4l2.py
QUERYCAP_ST=<16s32s32sII16x 104
FREQUENCY_ST=<III32x 44
ENUMSTD_ST=<QQ24s2II20x 72
STANDARD_ST=<Q 8
ENUMINPUT_ST=<I32sIIIQI20x 80
INPUT_ST=<I 4
FMT_ST=<I7I4x172x 208
TUNER_ST=<L32sLLLLLLll16x 84
AUDIO_ST=<L32sLL8x 52
Video Opened at /dev/video0
Driver: ivtv
Card: WinTV PVR 350
Version: 406
Capabilities: 17236211
Enumerating supported Standards.
0: 0x3000 NTSC
1: 0xff PAL
2: 0x7f0000 SECAM
Current Standard is: 0xff
Enumerating supported Inputs.
0: Composite 0
1: Composite 1
2: Composite 2
3: Composite 3
4: Tuner 0
5: Composite 4
6: S-Video 0
7: S-Video 1
8: S-Video 2
9: S-Video 3
Input: 4
Width: 0, Height: 720
Read Frequency: 8948
('ivtv\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
'WinTV PVR 350\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
x00\x00\x00\x00\x00\x00\x00',
'0000:05:06.0\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
x00', 1030L, 17236211L)
viddev.getinput=4
viddev.setinput okay
viddev.getfmt=1
(4L, 'Tuner
0\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
1L,
3L, 0L, 255L, 0L)
(0L, 'ivtv TV
Tuner\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
2L, 114L, 0L, 42949672
95L, 2L, 1L, 65535, 0)
(0L, 'Tuner Audio
In\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
1L, 0L)
None
2132
None
8948
(0L, 2L, 8948L)
As Robert says the API has changed, wasn't sure in which
version. From what I understand from the ivtv mailing list
is that the encoding api is not stable and Hans is working
on the decoding API. I've upgraded a test machine to
ivtv-0.8.0 and linux-2.6.18, took a while, for the tests and
did notice the api having changed and so recordings have
been failing.
----------------------------------------------------------------------
Comment By: John Molohan (johnmolohan)
Date: 2006-09-28 22:35
Message:
Logged In: YES
user_id=774680
This is weird. I've just got in and set DEBUG=0 and
everything works, recording, watching and changing channel.
Setting it back to DEBUG=9 and everything still works. I
haven't changed anything else, no svn update no distro
updates. I'll attach the log you were looking for anyway.
Still the issue exists as to what to do. How soon will the
0.8.0 be in widespread use? I really don't want to have all
this work going into a 1.6 release only for a large number
of people not to able to use what's probably the most
popular chipset out there but if widespread use is a long
way off then I guess we should just go ahead with support
for up to 0.7.x releases.
----------------------------------------------------------------------
Comment By: Robert Winder (robertwinder)
Date: 2006-09-28 20:37
Message:
Logged In: YES
user_id=195085
Duncan release ivtv 0.7.0 and even 0.7.1 should work with
freevo 1.5.4. Using ivtv 0.7.0 myself with freevo 1.5.4 and
works fine. From ivtv 0.8.0 new api calls are introduced but
you probably don't want to invest time to prepare freevo for
the new API. IVTV is constantly changing preparing for
kernel inclusion so it's a moving target.
IIRC, long time ago, when DEBUG in local_conf.py is enabled
some freevo ioctl's fail. I thought this was fixed a while
back and did make it into 1.5.4. but n ot sure.
John could you try again with DEBUG=0 in local_conf.py and
report back.
----------------------------------------------------------------------
Comment By: Michael Ruelle (mikeruelle)
Date: 2006-09-28 20:26
Message:
Logged In: YES
user_id=849534
I can record using the 0.7.0 drivers on gentoo using pretty
much a stock 1.5.4 after chaning my input num to zero. but i
cannot play live tv
----------------------------------------------------------------------
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
