https://free-astro.org/index.php?title=USBGrabber:TM5600&feed=atom&action=history USBGrabber:TM5600 - Revision history 2024-03-29T01:53:53Z Revision history for this page on the wiki MediaWiki 1.40.0 https://free-astro.org/index.php?title=USBGrabber:TM5600&diff=378&oldid=prev Vincent: /* TM5600 USB video grabber */ debugging the TM5600 2013-06-22T21:22:49Z <p><span dir="auto"><span class="autocomment">TM5600 USB video grabber: </span> debugging the TM5600</span></p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 21:22, 22 June 2013</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l5">Line 5:</td> <td colspan="2" class="diff-lineno">Line 5:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>First of all, Trident seems to be well known for [http://www.redaelli.org/matteo-blog/2010/01/01/do-not-buy-dvb-usb-devices-with-trident-chipsets/ refusing to help coding free drivers] and even disclosing information about the chipsets, so that&#039;s a good reason not to buy it in the first place.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>First of all, Trident seems to be well known for [http://www.redaelli.org/matteo-blog/2010/01/01/do-not-buy-dvb-usb-devices-with-trident-chipsets/ refusing to help coding free drivers] and even disclosing information about the chipsets, so that&#039;s a good reason not to buy it in the first place.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>The driver supporting this chipset is [http://www.linuxtv.org/wiki/index.php/Trident_TM6000 tm6000]. The kernel doesn't know the device in particular, but recognizes the chipset: &lt;code&gt;tm6000: Found Generic tm5600 board&lt;/code&gt;.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>The driver supporting this chipset is [http://www.linuxtv.org/wiki/index.php/Trident_TM6000 tm6000]. The kernel doesn't know the device in particular, but recognizes the chipset: &lt;code&gt;tm6000: Found Generic tm5600 board&lt;/code&gt;<ins style="font-weight: bold; text-decoration: none;">. </ins></div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">Warnings from the kernel "&lt;code&gt;xc2028 2-0061: Error: firmware xc3028-v24.fw not found&lt;/code&gt;" must not be fixed as explained on the [http://www.linuxtv.org/wiki/index.php/Xceive_XC3028/XC2028 XC2028 page], because it crashes the driver, or at least it makes the device not work, I don't know why</ins>.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>'<del style="font-weight: bold; text-decoration: none;">''Grabbing video works fine </del>in <del style="font-weight: bold; text-decoration: none;">some circumstances</del>.<del style="font-weight: bold; text-decoration: none;">''' You plug </del>the <del style="font-weight: bold; text-decoration: none;">USB, you run "&lt;code&gt;mplayer tv://&lt;/code&gt;" and you have </del>the image, <del style="font-weight: bold; text-decoration: none;">it's as simple as that if your kernel was compiled with &lt;code&gt;CONFIG_VIDEO_TM6000&lt;/code&gt; (distribution's kernels </del>are<del style="font-weight: bold; text-decoration: none;">)</del>. <del style="font-weight: bold; text-decoration: none;">With mplayer displaying </del>the <del style="font-weight: bold; text-decoration: none;">feed, it takes 20% of user space CPU on an AMD64 2GHz</del>.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">The image is not completely stable (it moves up and down a bit), but I don</ins>'<ins style="font-weight: bold; text-decoration: none;">t know how stable is the source being tested </ins>in <ins style="font-weight: bold; text-decoration: none;">the first place and it is probably acceptable for guiding</ins>. <ins style="font-weight: bold; text-decoration: none;">There is a green line at </ins>the <ins style="font-weight: bold; text-decoration: none;">bottom of </ins>the image<ins style="font-weight: bold; text-decoration: none;">. Supported video standards are NTSC (720x480) and PAL (720x576)</ins>, <ins style="font-weight: bold; text-decoration: none;">supported image formats </ins>are <ins style="font-weight: bold; text-decoration: none;">YUYV and UYVY</ins>. <ins style="font-weight: bold; text-decoration: none;">Care has to be taken in programs to select the correct standard with </ins>the <ins style="font-weight: bold; text-decoration: none;">correct definition</ins>.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">However, </del>'''<del style="font-weight: bold; text-decoration: none;">in some cases, it doesn't </del>works fine'''<del style="font-weight: bold; text-decoration: none;">, one frame on two is not obtained right from </del>the <del style="font-weight: bold; text-decoration: none;">driver</del>, <del style="font-weight: bold; text-decoration: none;">and I have no idea why. The [http</del>://<del style="font-weight: bold; text-decoration: none;">moinejf.free.fr</del>/ <del style="font-weight: bold; text-decoration: none;">SVV V4L2 application]</del>, <del style="font-weight: bold; text-decoration: none;">[http:</del>/<del style="font-weight: bold; text-decoration: none;">/www.mplayerhq.hu/ Mplayer] and [[Unicap]] get a correct image. [[GoQat]]</del>'s <del style="font-weight: bold; text-decoration: none;">V4L2 mode, qastrocam-g2 (not always?</del>) <del style="font-weight: bold; text-decoration: none;">and [[OpenPHD Guiding|open-phd-guiding]] seem to have a buffer problem in V4L2 mmap mode grabbing</del>, <del style="font-weight: bold; text-decoration: none;">and the image flickers</del>.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>'''<ins style="font-weight: bold; text-decoration: none;">Grabbing video </ins>works fine<ins style="font-weight: bold; text-decoration: none;">, but not always.</ins>''' <ins style="font-weight: bold; text-decoration: none;">You plug </ins>the <ins style="font-weight: bold; text-decoration: none;">USB</ins>, <ins style="font-weight: bold; text-decoration: none;">you run "&lt;code&gt;mplayer tv</ins>://<ins style="font-weight: bold; text-decoration: none;">&lt;</ins>/<ins style="font-weight: bold; text-decoration: none;">code&gt;" and you have the video feed</ins>, <ins style="font-weight: bold; text-decoration: none;">it's as simple as that if your kernel was compiled with &lt;code&gt;CONFIG_VIDEO_TM6000&lt;</ins>/<ins style="font-weight: bold; text-decoration: none;">code&gt; (distribution</ins>'s <ins style="font-weight: bold; text-decoration: none;">kernels are</ins>)<ins style="font-weight: bold; text-decoration: none;">. With mplayer displaying the feed</ins>, <ins style="font-weight: bold; text-decoration: none;">it takes 20% of user space CPU on an AMD64 2GHz</ins>.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">The image is not very stable (it moves up </del>and <del style="font-weight: bold; text-decoration: none;">down a bit), but I don't know how stable is the source being tested. There is a green line at the bottom of the image. Supported video standards  are NTSC (720x480) and PAL (720x576), supported image formats are YUYV and UYVY.</del></div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">==Grabbing problems </ins>and <ins style="font-weight: bold; text-decoration: none;">solutions==</ins></div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;">Warnings </del>from the <del style="font-weight: bold; text-decoration: none;">kernel "&lt;code&gt;xc2028 2-0061</del>: <del style="font-weight: bold; text-decoration: none;">Error: firmware xc3028-v24</del>.<del style="font-weight: bold; text-decoration: none;">fw not found&lt;</del>/<del style="font-weight: bold; text-decoration: none;">code&gt;" must not be fixed as explained on the </del>[http://www.<del style="font-weight: bold; text-decoration: none;">linuxtv</del>.<del style="font-weight: bold; text-decoration: none;">org</del>/<del style="font-weight: bold; text-decoration: none;">wiki/index</del>.<del style="font-weight: bold; text-decoration: none;">php/Xceive_XC3028/XC2028 XC2028 page</del>], <del style="font-weight: bold; text-decoration: none;">because </del>it crashes the driver, or at <del style="font-weight: bold; text-decoration: none;">least it makes </del>the device not <del style="font-weight: bold; text-decoration: none;">work</del>, <del style="font-weight: bold; text-decoration: none;">I don</del>'<del style="font-weight: bold; text-decoration: none;">t know why yet</del>.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">However, '''in some cases, it doesn't works fine''', one frame on two is not obtained right </ins>from the <ins style="font-weight: bold; text-decoration: none;">driver. The [http</ins>:<ins style="font-weight: bold; text-decoration: none;">//moinejf.free</ins>.<ins style="font-weight: bold; text-decoration: none;">fr</ins>/ <ins style="font-weight: bold; text-decoration: none;">SVV V4L2 application], </ins>[http://www.<ins style="font-weight: bold; text-decoration: none;">mplayerhq</ins>.<ins style="font-weight: bold; text-decoration: none;">hu</ins>/ <ins style="font-weight: bold; text-decoration: none;">Mplayer] and [[Unicap]] generally get a correct image. [[GoQat]]'s V4L2 mode (&lt;= 1.0</ins>.<ins style="font-weight: bold; text-decoration: none;">0), [[Qastrocam-g2]] (not always?) and [[OpenPHD Guiding|open-phd-guiding]</ins>] <ins style="font-weight: bold; text-decoration: none;">seem to have a buffer problem in V4L2 '''mmap mode''' grabbing, and the image flickers.</ins></div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">This issue has been tracked down to a driver's issue AND to misbehaving V4L2 software. The driver issue is that polling the device always indicates that there is a frame ready in the buffer while when asking for buffer dequeue, the request fails with a not-ready image error. In that case</ins>, <ins style="font-weight: bold; text-decoration: none;">looping on the DQBUF ioctl while </ins>it <ins style="font-weight: bold; text-decoration: none;">returns a not-ready state </ins>crashes the driver<ins style="font-weight: bold; text-decoration: none;">. What has to be done is wait for a frame to be actually ready, by sleeping before retry, or doing something else. SVV has been fixed for this particular issue, making it working fine all the time: [[:File:svv.c]].</ins></div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">On the userland side, the issue was that some software take too long to process the image and when they query the buffer, another frame has been partially written over the ready-frame. This is clearly a driver bug too, but V4L2 programs should not do it anyway. MPlayer for example has a thread dedicated to reading the frames as they become available</ins>, <ins style="font-weight: bold; text-decoration: none;">storing them for future processing by another thread when required (frame rate enforcement) </ins>or <ins style="font-weight: bold; text-decoration: none;">when the CPU will be able to do so. '''Images have to be captured and dropped if they can't be used, instead of being captured </ins>at <ins style="font-weight: bold; text-decoration: none;">a rate which is slower than </ins>the device<ins style="font-weight: bold; text-decoration: none;">'s rate.''' If the driver or device were </ins>not <ins style="font-weight: bold; text-decoration: none;">buggy</ins>, <ins style="font-weight: bold; text-decoration: none;">this issue would probably not be noticed, as it</ins>'<ins style="font-weight: bold; text-decoration: none;">s the case with other V4L2 devices</ins>.</div></td></tr> </table> Vincent https://free-astro.org/index.php?title=USBGrabber:TM5600&diff=125&oldid=prev Vincent: v4l2 issues 2012-09-14T02:26:21Z <p>v4l2 issues</p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 02:26, 14 September 2012</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l7">Line 7:</td> <td colspan="2" class="diff-lineno">Line 7:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The driver supporting this chipset is [http://www.linuxtv.org/wiki/index.php/Trident_TM6000 tm6000]. The kernel doesn&#039;t know the device in particular, but recognizes the chipset: &lt;code&gt;tm6000: Found Generic tm5600 board&lt;/code&gt;.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The driver supporting this chipset is [http://www.linuxtv.org/wiki/index.php/Trident_TM6000 tm6000]. The kernel doesn&#039;t know the device in particular, but recognizes the chipset: &lt;code&gt;tm6000: Found Generic tm5600 board&lt;/code&gt;.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>'''Grabbing video works fine.''' You plug the USB, you run "&lt;code&gt;mplayer tv://&lt;/code&gt;" and you have the image, it's as simple as that if your kernel was compiled with &lt;code&gt;CONFIG_VIDEO_TM6000&lt;/code&gt; (distribution's kernels are). With mplayer displaying the feed, it takes 20% of user space CPU on an AMD64 2GHz.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>'''Grabbing video works fine <ins style="font-weight: bold; text-decoration: none;">in some circumstances</ins>.''' You plug the USB, you run "&lt;code&gt;mplayer tv://&lt;/code&gt;" and you have the image, it's as simple as that if your kernel was compiled with &lt;code&gt;CONFIG_VIDEO_TM6000&lt;/code&gt; (distribution's kernels are). With mplayer displaying the feed, it takes 20% of user space CPU on an AMD64 2GHz.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>The image is not very stable (it moves up and down a bit), but I don't know how stable is the source being tested. There is a green line at the bottom of the image. Supported video standards  are NTSC (720x480) and PAL (720x576).</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">However, '''in some cases, it doesn't works fine''', one frame on two is not obtained right from the driver, and I have no idea why. The [http://moinejf.free.fr/ SVV V4L2 application], [http://www.mplayerhq.hu/ Mplayer] and [[Unicap]] get a correct image. [[GoQat]]'s V4L2 mode, qastrocam-g2 (not always?) and [[OpenPHD Guiding|open-phd-guiding]] seem to have a buffer problem in V4L2 mmap mode grabbing, and the image flickers.</ins></div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>The image is not very stable (it moves up and down a bit), but I don't know how stable is the source being tested. There is a green line at the bottom of the image. Supported video standards  are NTSC (720x480) and PAL (720x576)<ins style="font-weight: bold; text-decoration: none;">, supported image formats are YUYV and UYVY</ins>.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Warnings from the kernel &quot;&lt;code&gt;xc2028 2-0061: Error: firmware xc3028-v24.fw not found&lt;/code&gt;&quot; must not be fixed as explained on the [http://www.linuxtv.org/wiki/index.php/Xceive_XC3028/XC2028 XC2028 page], because it crashes the driver, or at least it makes the device not work, I don&#039;t know why yet.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Warnings from the kernel &quot;&lt;code&gt;xc2028 2-0061: Error: firmware xc3028-v24.fw not found&lt;/code&gt;&quot; must not be fixed as explained on the [http://www.linuxtv.org/wiki/index.php/Xceive_XC3028/XC2028 XC2028 page], because it crashes the driver, or at least it makes the device not work, I don&#039;t know why yet.</div></td></tr> </table> Vincent https://free-astro.org/index.php?title=USBGrabber:TM5600&diff=69&oldid=prev Vincent: standards 2012-09-01T23:08:33Z <p>standards</p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 23:08, 1 September 2012</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l9">Line 9:</td> <td colspan="2" class="diff-lineno">Line 9:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>&#039;&#039;&#039;Grabbing video works fine.&#039;&#039;&#039; You plug the USB, you run &quot;&lt;code&gt;mplayer tv://&lt;/code&gt;&quot; and you have the image, it&#039;s as simple as that if your kernel was compiled with &lt;code&gt;CONFIG_VIDEO_TM6000&lt;/code&gt; (distribution&#039;s kernels are). With mplayer displaying the feed, it takes 20% of user space CPU on an AMD64 2GHz.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>&#039;&#039;&#039;Grabbing video works fine.&#039;&#039;&#039; You plug the USB, you run &quot;&lt;code&gt;mplayer tv://&lt;/code&gt;&quot; and you have the image, it&#039;s as simple as that if your kernel was compiled with &lt;code&gt;CONFIG_VIDEO_TM6000&lt;/code&gt; (distribution&#039;s kernels are). With mplayer displaying the feed, it takes 20% of user space CPU on an AMD64 2GHz.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>The image is not very stable (it moves up and down a bit), but I don't know how stable is the source being tested. There is a green line at the bottom of the image.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>The image is not very stable (it moves up and down a bit), but I don't know how stable is the source being tested. There is a green line at the bottom of the image<ins style="font-weight: bold; text-decoration: none;">. Supported video standards  are NTSC (720x480) and PAL (720x576)</ins>.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Warnings from the kernel &quot;&lt;code&gt;xc2028 2-0061: Error: firmware xc3028-v24.fw not found&lt;/code&gt;&quot; must not be fixed as explained on the [http://www.linuxtv.org/wiki/index.php/Xceive_XC3028/XC2028 XC2028 page], because it crashes the driver, or at least it makes the device not work, I don&#039;t know why yet.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Warnings from the kernel &quot;&lt;code&gt;xc2028 2-0061: Error: firmware xc3028-v24.fw not found&lt;/code&gt;&quot; must not be fixed as explained on the [http://www.linuxtv.org/wiki/index.php/Xceive_XC3028/XC2028 XC2028 page], because it crashes the driver, or at least it makes the device not work, I don&#039;t know why yet.</div></td></tr> </table> Vincent https://free-astro.org/index.php?title=USBGrabber:TM5600&diff=56&oldid=prev Vincent: more info 2012-08-30T03:29:31Z <p>more info</p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 03:29, 30 August 2012</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l3">Line 3:</td> <td colspan="2" class="diff-lineno">Line 3:</td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>This page explains how the Trident TM5600 chipset works in Linux, in particular with the following product that embeds it: [http://www.konigelectronic.com/en_us/55831665 KÖNIG CMP-USBVG6] (bought [http://www.ascii-info.com/acquisition-video/3067-konig-editeur-audio-video-usb-20.html here] 30€).</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>This page explains how the Trident TM5600 chipset works in Linux, in particular with the following product that embeds it: [http://www.konigelectronic.com/en_us/55831665 KÖNIG CMP-USBVG6] (bought [http://www.ascii-info.com/acquisition-video/3067-konig-editeur-audio-video-usb-20.html here] 30€).</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>First of all, Trident seems to be well known for refusing to help coding free drivers and even disclosing information about the chipsets, so that's a good reason not to buy it in the first place.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>First of all, Trident seems to be well known for <ins style="font-weight: bold; text-decoration: none;">[http://www.redaelli.org/matteo-blog/2010/01/01/do-not-buy-dvb-usb-devices-with-trident-chipsets/ </ins>refusing to help coding free drivers<ins style="font-weight: bold; text-decoration: none;">] </ins>and even disclosing information about the chipsets, so that's a good reason not to buy it in the first place.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>The driver supporting this chipset is [http://www.linuxtv.org/wiki/index.php/Trident_TM6000 tm6000]. The kernel doesn't know the device in particular, but recognizes the chipset: <del style="font-weight: bold; text-decoration: none;">"</del>tm6000: Found Generic tm5600 board<del style="font-weight: bold; text-decoration: none;">"</del>.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>The driver supporting this chipset is [http://www.linuxtv.org/wiki/index.php/Trident_TM6000 tm6000]. The kernel doesn't know the device in particular, but recognizes the chipset: <ins style="font-weight: bold; text-decoration: none;">&lt;code&gt;</ins>tm6000: Found Generic tm5600 board<ins style="font-weight: bold; text-decoration: none;">&lt;/code&gt;</ins>.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>'''Grabbing video works fine.''' You plug the USB, you run "mplayer tv://" and you have the image, it's as simple as that if your kernel was compiled with CONFIG_VIDEO_TM6000 (distribution's kernels are).</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>'''Grabbing video works fine.''' You plug the USB, you run "<ins style="font-weight: bold; text-decoration: none;">&lt;code&gt;</ins>mplayer tv://<ins style="font-weight: bold; text-decoration: none;">&lt;/code&gt;</ins>" and you have the image, it's as simple as that if your kernel was compiled with <ins style="font-weight: bold; text-decoration: none;">&lt;code&gt;</ins>CONFIG_VIDEO_TM6000<ins style="font-weight: bold; text-decoration: none;">&lt;/code&gt; </ins>(distribution's kernels are)<ins style="font-weight: bold; text-decoration: none;">. With mplayer displaying the feed, it takes 20% of user space CPU on an AMD64 2GHz</ins>.</div></td></tr> <tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr> <tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>The image is not very stable (it moves a bit), but I don't know how stable is the source being tested. There is a green line at the bottom of the image.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>The image is not very stable (it moves <ins style="font-weight: bold; text-decoration: none;">up and down </ins>a bit), but I don't know how stable is the source being tested. There is a green line at the bottom of the image<ins style="font-weight: bold; text-decoration: none;">.</ins></div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr> <tr><td colspan="2" class="diff-side-deleted"></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">Warnings from the kernel "&lt;code&gt;xc2028 2-0061: Error: firmware xc3028-v24.fw not found&lt;/code&gt;" must not be fixed as explained on the [http://www.linuxtv.org/wiki/index.php/Xceive_XC3028/XC2028 XC2028 page], because it crashes the driver, or at least it makes the device not work, I don't know why yet</ins>.</div></td></tr> </table> Vincent https://free-astro.org/index.php?title=USBGrabber:TM5600&diff=55&oldid=prev Vincent: first data on tm5600 2012-08-30T03:13:38Z <p>first data on tm5600</p> <p><b>New page</b></p><div>=TM5600 USB video grabber=<br /> <br /> This page explains how the Trident TM5600 chipset works in Linux, in particular with the following product that embeds it: [http://www.konigelectronic.com/en_us/55831665 KÖNIG CMP-USBVG6] (bought [http://www.ascii-info.com/acquisition-video/3067-konig-editeur-audio-video-usb-20.html here] 30€).<br /> <br /> First of all, Trident seems to be well known for refusing to help coding free drivers and even disclosing information about the chipsets, so that&#039;s a good reason not to buy it in the first place.<br /> <br /> The driver supporting this chipset is [http://www.linuxtv.org/wiki/index.php/Trident_TM6000 tm6000]. The kernel doesn&#039;t know the device in particular, but recognizes the chipset: &quot;tm6000: Found Generic tm5600 board&quot;.<br /> <br /> &#039;&#039;&#039;Grabbing video works fine.&#039;&#039;&#039; You plug the USB, you run &quot;mplayer tv://&quot; and you have the image, it&#039;s as simple as that if your kernel was compiled with CONFIG_VIDEO_TM6000 (distribution&#039;s kernels are).<br /> <br /> The image is not very stable (it moves a bit), but I don&#039;t know how stable is the source being tested. There is a green line at the bottom of the image.</div> Vincent