Do we think this would be different between the Retail and the MCE?
Cause the retail works...
As of tonight's testing, my MCE works. I don't have a signal to test
the tuner with, but I get sound and color on both the composite and
s-video ports (although it took me a bit to figure out which po
Hello,
In <[EMAIL PROTECTED]> message,
petemartin wrote:
> I have got the basic driver running with the help of the instructions below,
> but the video is just a mess of green with a changing colour pattern at the
> bottom of the screen. Audio appears to work when fed into the audio jack
> tho
There is really only one tuner on the 150. There appear to be two because the 150 and the 500 (which is treated as 2x150s) apparently use different inputs for the audio into the cx25840 chip. Input 6 is for the 150 and 7 is for the 500. As far as brightness and contrast, I'm pretty sure those ar
Hi folks -
In the couple days since my last post, I have narrowed this down to a
problem of not getting any autio from my captures.
I have done my best to search for possible solutions, and have tried all
that I have been able to find.
This includes:
1.) The card is not muted (verified through
I've revised Jose Alberto Reguero's patch for ivtv-0.3.2b.
This is along the lines of my revision to his patch for
ivtv-0.2.0-rc3d.
I have NOT tested this. I tried to use that ATrpms source RPM and
found that this is a very difficult poposition. Darn. Can anyone
else suggest an easy path to tes
Do we think this would be different between the Retail and the MCE?
Cause the retail works...
kevin thayer wrote:
# ivtvctl --device /dev/video1 -Y
ioctl: VIDIOC_QUERYCTRL
Brightness = -1208049664
Contrast = -526981127
Saturation = -611254672
Hue = 0
Volume = 65535
Mute = 0
Brightness, contrast a
I use 2.4.27 with 2 pvr250s and it's working fine. Though I'm not so
sure about the HD-3000. I don't have one of those.
On Wed, 26 Jan 2005 15:30:28 -0800, Jason Weinstein <[EMAIL PROTECTED]> wrote:
> After long trials on getting both my PVR-350 and HD-3000 working under
> FC3 (i think I tried
There is really only one tuner on the 150. There appear to be two because the
150 and the 500 (which is treated as 2x150s) apparently use different inputs
for the audio into the cx25840 chip. Input 6 is for the 150 and 7 is for the
500. As far as brightness and contrast, I'm pretty sure those
Ok, so then the recommended
firmware and driver are:
Firmware - pvr48wdm_1.8.22037.exe
ftp://ftp.shspvr.com/download/wintv-pvr_250-350/win9x-2k-xp_mpeg_wdm_drv/pvr48wdm_1.8.22037.exe
- which follows
the recommendation from Chris's site
Driver -
ivtv-0.2.0-rc3e.tgz
http://205.209.168.201/~cke
Hi Kevin,
On Thu, 2005-01-27 at 09:24 -0800, kevin thayer wrote:
> The reason for the -ivtv versions is that the ivtv
> modules are branches from the mainline kernel
> versions, and other (non-ivtv) hardware uses them. It
> wouldn't be playing nice to simply remove or overwrite
> the kernel versio
Unfortuneatly, while I wouldn't mind using Gentoo or Debian, these
systems have to fit in with the Operations department's standards which
require Redhat of some sort.
On Thu, 2005-01-27 at 23:07 +0100, Peter Karlsson wrote:
> On Wed, 26 Jan 2005, Zed Shaw wrote:
>
> > But, there's a downside to
Hi
I don't know if it might help but below is the output of dmesg with
ivtv_debug=255.
tveeprom: Ignoring new-style parameters in presence of obsolete ones
msp3400: Unknown parameter `standard'
msp3400: Ignoring new-style parameters in presence of obsolete ones
Linux video capture interface: v1.
On Thu, 27 Jan 2005 10:37:43 -0800 (PST), kevin thayer
<[EMAIL PROTECTED]> wrote:
> > I was going to start trying to categorize the FAQ,
> > but can't seem to
> > edit that page. How is this done currently?
>
> the faq is tricky. You have to do this:
> 1) log in
> 2) click FAQs on the left (not t
On Thu, Jan 27, 2005 at 10:47:11PM +0100, Peter Karlsson wrote:
> On Thu, 27 Jan 2005, Axel Thimm wrote:
>
> > The true story is that there the video4linux project and ivtv share
> > some namespace. In order to avoid conflicts in the kernel modules the
> > names of one of the project's modules hav
> I was going to start trying to categorize the FAQ,
> but can't seem to
> edit that page. How is this done currently?
the faq is tricky. You have to do this:
1) log in
2) click FAQs on the left (not the ::!)
3) click the "questions" icon under 'actions' (not
edit!)
that should get you going.
>
Correct, no bttv is loading.
Jason
On Tue, 25 Jan 2005 23:01:09 -0500, Alan Gonzalez
<[EMAIL PROTECTED]> wrote:
> and no bttv right?
>
>
> On Tue, 25 Jan 2005 19:52:52 -0800, Jason Weinstein <[EMAIL PROTECTED]> wrote:
> > I don't think that eeprom is necessary for IVTV or the PVR-350. The
> >
Hi,
I was looking at the different values of my 150MCE and stumbled on this:
# ivtvctl --device /dev/video1 -n
ioctl: VIDIOC_ENUMINPUT
Input : 0
Name: S-Video 0
Type: 0x0002
Audioset: 0x0003
Tuner : 0x
Standard: 0x000
On Thu, 27 Jan 2005, Axel Thimm wrote:
> The true story is that there the video4linux project and ivtv share
> some namespace. In order to avoid conflicts in the kernel modules the
> names of one of the project's modules have to be altered.
Why not share the same code instead, i.e. merge v4l & iv
i'm havin' some problems tryin' to capture both PAL-N
n' PAL-M via de composite/s-video inputs. i have a
pvr250 and pvr350.
this is what i'm doing:
1- swith from NTSC to PAL (the dmesg shows that both
card start in NTSC) with ivtvctl -u 0xff
2- change imput to s-video/composite with ivtvctl -p6
3-
Hi,
I have just been sent one of the mpg600gr cards to see if we can use it,
since it works in 3.3volt pci motherboards. Yuan told us that we could just
use the ivtv code (they pointed us to 0.9) and it would work - clearly not
quite true!
I have got the basic driver running with the help of the
After long trials on getting both my PVR-350 and HD-3000 working under
FC3 (i think I tried everything) I've decide to start over again from
scratch. I've decided to use Debian "Sarge" and would like to know is
there any reason to, on my MythTV-only box, not use a 2.4.x kernel.
The default install
Hi
I also posted this on the general list
Further to my last message I did not specify that the card is an Adaptec
Videoh! Media Center, part number AVC-2410.
I have captured the audio from /dev/video24 and imported it into Audacity as
signed 16 bit Little endian 48000Hz stereo PCM. Then I
Hi
Further to my last message, I have peeled the label of the video encoder chip
and found out it is a CX23416-12. The product overview on the Conexant
website does not list a higher audio capture rate than 48kHz. So I have no
idea how I am apparently getting a speed of 96kHz from the raw audio
what's the busid of the card?
it's the first portion of the stuff that lspci prints
out.
eg:
/sbin/lspci | grep Internext
BUSID IN HEX Rest of line
00:14.0 Multimedia video controller: Internext
Compression Inc iTVC15 MPEG-2 Encoder (rev 01)
and my busid in X config(in decimal!):
BusID
On Wed, 26 Jan 2005, Zed Shaw wrote:
> But, there's a downside to every story, and that downside is the sudden
> appearance of parallel modules in the kernel modules directory for
> tveeprom, msp3400, and tuner all ending in "-ivtv". Somehow, two
> different sets of modules for the ivtv RPMs were
Some items I think we should do...
Change up the Wiki FAQ into sections on the driver version. At the
same time clean it up a bit to make it easier to find solutions to
common problems.
I was going to start trying to categorize the FAQ, but can't seem to
edit that page. How is this done current
The reason for the -ivtv versions is that the ivtv
modules are branches from the mainline kernel
versions, and other (non-ivtv) hardware uses them. It
wouldn't be playing nice to simply remove or overwrite
the kernel versions of things with our own.
audio for the [23]50 series cards is handled by
I've been sticking with what Chris Kennedy recommends. If you look at
the top of the page,
http://ivtv.no-ip.com
There is a link for "Current Recommended Firmware".
ftp://ftp.shspvr.com/download/wintv-pvr_250-350/win9x-2k-xp_mpeg_wdm_drv/pvr48wdm_1.8.22037.exe
---Dan
--
whatever it says on the wiki page. I think newer
ivtv's even print out the recommended version, or a
warning if you're not running that version.
-tmk
--- Don Brett <[EMAIL PROTECTED]> wrote:
> Which driver and firmware do the developers
> recommend for the Pvr 350?
> I've tried several combinati
Hi, I just got my PVR-150 MCE yesterday, and with a little work and a
lot of help on #mythtv-users, managed to get it almost functional.
Figured the next step would be to join this list and see if anyone had
more info, and what I could do to help.
I'm running 2.6.10-741 from FC3, recompiled to
30 matches
Mail list logo
