On Wed, 2009-10-07 at 20:55 -0500, Chuck Cole wrote: > Didn't say the data had no existence, only that my drivers emulate TV remotes which have channel buttons (or equiv) at user > interface levels. The lower level software for mine is closed proprietary stuff one cannot see into. Which TV PCI and USB TV > tuners have fully open source that shows this? The source isn't necessary, simply look at the publicly available APIs or even the .ini files that come with the software. It's how things were standardized a very long time ago (do you not remember TVs with tuner dials where you could change any channel number to a different actual channel?) > > > Didin't ask your opinion of that. He mentioned very low kilohertz for some reason when the much higher megahertz range > > seemed more > > > relevant. Yu could try reading the context and threads of this before pontificating. > > > > I read the entire thread multiple times, he said "channel 13 is 211.25 > > mHz, or 211250 kHz" that is absolutely correct for "Standard" cable and > > Broadcast NTSC. It's not "very low" and it's the exact same frequency no > > matter if he specified it in terahertz or hertz. > > He said that after you posted the table, but was speaking of lower frequencies at first when that issue entered the thread. You are > out of sequence in your capture and compaint. Actually, I posted the table today at 10:42am. He posted that yesterday at 2:30pm. Perhaps you're the one with the reading comprehension problems? Consider your own advice and re-read the thread. > > You do realize that 211.25MHz is the same as 211,250 KHz, which is the > > same as 211,250,000 Hz right? > > They are not: the extra decimals should express actual precision of measurement, so fewer digits may indicate different actual > numbers when the same precision of measurement is applied. You did know that, didn't you? :-) You're seriously going to debate that 211.25 MHz is not the same frequency as 211,250,000 Hz? He used the decimals which meant they were significant, I quoted precisely what he said, he was very clear. > > > Not ignorant, it's 100% accurate for what VLC itself does, and THAT was the question. > > > > It is not a "digital data format issue" and there is no "pseudo-code". > > The frequency *is* the issue as he was trying to tune into a specific > > channel and needed to know which frequency to configure VLC to tune. > > That was all HE asked about. Any more is your inference and assumption. Hello reading comprehension, his exact statement: "I am working with VLC on Linux Mint, and need help determining what frequencies (KHz) are assigned to channels 4,8, and 13. Is there a good doc on this?" further clarified: "... Our cable provider uses VHF channels 4, 8, and 13 to feed video to our TVs. If my research is correct channel 13 is 211.25 mHz, or 211250 kHz. I haven't gotten it to work yet, which is why I wanted to be sure the frequency I am using is right. I can view channel 13 on TVTime, so I know the tuner is working correctly." Yes, I believe it is *excruciatingly* clear that he was asking for a list of channel numbers <-> frequency mappings. > Speak for yourself. Heed your own advice and learn to read better. See above, you're confused about what he even asked. > You did not identify and confirm the correct block diagram Put away the diagrams and start actually reading peoples email. > interface for THIS question before pontificating about quasi-relevant low-level bits. Identify the open source tuner driver > interfaces that show this and require frequency domain setup and do not allow or use normal TV set channelizations. Show your info > is mabe as much as half-vast :-) Here is the ioctl to set a frequency: http://www.linuxtv.org/downloads/video4linux/API/V4L2_API/spec-single/v4l2.html#vidioc-g-frequency Here is the structure you pass to it: http://www.linuxtv.org/downloads/video4linux/API/V4L2_API/spec-single/v4l2.html#v4l2-frequency " 1.6.3. Radio Frequency To get and set the tuner or modulator radio frequency applications use the VIDIOC_G_FREQUENCY and VIDIOC_S_FREQUENCY ioctl which both take a pointer to a struct v4l2_frequency. These ioctls are used for TV and radio devices alike. Drivers must support both ioctls when the tuner or modulator ioctls are supported, or when the device is a radio device. " Video standards, and how to set them if the tuner card supports more than one, and isn't currently on the one you need: http://www.linuxtv.org/downloads/video4linux/API/V4L2_API/spec-single/v4l2.html#standard I challenge you to actually educate yourself instead of trolling a mailing list about something you obviously have no knowledge of. Don't bother replying unless you've actually re-read the thread, and read through the relevant parts of the various APIs (Video for Windows, DirectX, Video4Linux).