You're right!! Thanks.
:)
But now I have a different problem. The mplayer screen starts but only gives snow so that means I have to fill in the frequencies. I have this list..
1 Ned 1
11-
216,00 2 Ned 2
6+
184,00 3 Ned 3
7+
192,00 4 RTL 4
12-
224,00
etc etc... But filling in these frequencies still gives me snow. Yesterday when I used 'test_ioctl -r tuner=0,freq=2944' and mplayer /dev/video0 I got Nederland 2, but this list says it should be 184.00. I have tried both and they both give only 'snow'.
Ok, I am pretty sure I know what's going on here. You have to find the right units for your frequency for our table. Mplayer expects it one way and I think test_ioctl expects another. Mplayer is being more user friendly but behaves a bit nonstandard in the units it accepts the freq in - most actual frequency tables don't store it in KHz. I think test_ioctl just take the input and passes it to the driver without massaging it (usually the app does this). So, you need to find the middle ground.
If that explanation is confisung its because I forget the units and calculations used right now... and I am just finishing my first coffee. :)
When using the frequency table and ivtv Freevo takes the value from the table and * 16 / 1000. So:
freevo_freq * 16 / 1000 = tuner_freq freevo_freq * 16 / 1000 = 2944 freevo_freq = 2944 * 1000 / 16 freevo_freq = 184000
Give 184000 a try in your frequency table in Freevo.
HTH, -Rob
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Freevo-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-users
