If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
I'd like to know why they couldn't have made this announcement months ago. Only when it comes down to the FSCKING DEADLINE do they tell us that "We don't have working drivers, we never did, never will, and you'll get partially working drivers in another month."
How long have TS known that they weren't gonna get MJPEG operational under Win2k? Why couldn't they have made MJPEG a secondary priority to important things for Win2k like fixing dualhead and writing stable capture drivers (YUV and RGB)?!?!
For the past year I've wanted to utilize Dualhead and my capture capability under Win2k. MJPEG is lost, and though I am very disappointed to see it go, I can deal with it because YUV is "BETTAR." But what I cannot comprehend is Matrox's constant procrastination of this issue up to the point where they've decided to use this MJPEG issue as an excuse to push back the deadline for real fixes.
i'm as disgusted as everyone else. i asked them before i bought the card if it would be fully supported in win2k. i just bought it a couple months ago.
at a minimum, they should allow customers the option of trading the g400tv in for the 450etv.
You asked about the Osprey. While I can't give you any personal experience, I would suggest contacting Neils Johnson at www.downrecs.com
He's written in DV both about using Osprey cards, and about his interest in hearing from others who put video on CD, so I'd imagine he'd be fairly easy to talk to.
Jkun, do a web search for "Ospry 200" These are "big" in the streaming video market. However, they are based on the Brooktree/Conexant chips.
I did get one bad Hauppauge card it had a very noisy tuner, captures from line in were fine however. Yes many PAL people have problems we don't see in NTSC land, true for DV too.
I also had to RMA two G200 Marvels to get one that worked right, but its now useless on W2k for lack of decent drivers.
OK, maybe it's me, but i don't understand why mjpeg support isn't possible in W2K when it was managed in the beta drivers, and the 5.32 drivers and VT 202 work fine so long as you have the tv tuner option.
How can it be claimed that it can't be done when it already has been?
Couldn't matrox just disable the tv tuner detection in quick connect and give more people a chance to get it working?
Well I suppose there are two ways at looking at this situation either there were technical difficulties they couldn't overcome or they don't have or won't commit the resources to the coding of the drivers.
Personally, I think every single person that has the opportunity should sue this lame excuse of a company and force them to give their money back to the customers it stole it from. This way of dealing with customers is simply outrageous, one year with beta drivers and tools for Win2000 and now they say they won't support hardware MJPEG? Then what the f*** did I buy this piece of s*** for? And hey, they even dare to say that the Marvell G400 was only intended for win98... and their own hardware codec in Win98 is the worst piece of crap I've ever seen!!! You can't do anything with it, and although it's suposedly accelerated by hardware, it's actually lots of times slower than software mjpeg codecs like PicVideo, and you can't edit with it!! Try to edit a small movie in Premiere or play with it in After Effects and then export the timeline to the Matrox codec. Disaster!!! And not only that, they make the YUY2 option invisible, so users that didn't find out yet about the YUY2 patch are stuck with their f**** buggy codec!!!
Jesus Christ, I'm soooo regretful of having bought a Matrox product, and I can swear I will never buy a Matrox product again!!! X-(X-(X-(X-(X-(X-(X-(X-(X-(
Comment