From: Steven Maddox <s.maddox@lantizia.me.uk>
To: linux-media@vger.kernel.org
Subject: tm6000: new board id [15e4:0140]
Date: Sat, 30 Nov 2019 14:33:56 +0000 [thread overview]
Message-ID: <c745d5a7-79a4-a8d8-8caf-5944856e561d@lantizia.me.uk> (raw)
Hi,
New device...
Manufacturer: ION
Model: VCR 2 PC
Vendor/Product id: [15e4:0140]
Manufacturers URL: https://www.ionaudio.com/vcr-2-pc-vcr2pcx110
Chipset: tm6010 (see link to photos below)
Tests made:
- Forced it to use the tm6000 module via...
echo 15e4 0140 > /sys/bus/usb/drivers/tm6000/new_id
- Closest match (as this also has no DVB but also has composite) was a
"TM6010_BOARD_BEHOLD_VOYAGER" so used...
modprobe tm6000 card=11
- After selecting input 1 on something like VLC - the video comes out
with a lot of green crap all over it, see this image...
https://i.snipboard.io/JdSqKQ.jpg
- Also the audio is undecipherable and choppy... however sometimes when
you're not capturing the video - bizarrely the audio becomes clear and
you can capture it just using something like Audacity. I'm finding it
tough to always reproduce this however.
- Since this is a VCR, clearly no DVB, Radio or Remote functions!
More photos of this unit after I've opened it up here...
https://photos.app.goo.gl/iMmjtgQuyeDK4NdA9
Basically if anyone has the time... I wouldn't mind a second opinion on
getting this to work. I feel like it's fairly close.
My other option is to take the tm6010 board out of the VCR and put
something else in it which will be less problematic for most Linux-based
distributions (any suggestions?).
~lantizia
reply other threads:[~2019-11-30 14:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c745d5a7-79a4-a8d8-8caf-5944856e561d@lantizia.me.uk \
--to=s.maddox@lantizia.me.uk \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).