Mdp-130 Driver For Mac
I'm having a problem that was in b357 that has continued into b358. Source material is captured.tp files off QAM cable (motorola 6200 cable box or direct capture via MyHD MDP-130). Happens on 1080i, 720p, and 480i material.
Same happened with this setup, locked up at the 8922 driver install. Mine is not an isolated case, others have reported having this same problem with the 8922. Procured Window 8 Pro, installed on the new computer then the 8922 did install and work but my old MDP-130 ATSC/QAM tuner card would not work. Gave up, purchased the Pro 7301. Vieni e scarica driver per mdtv receiver leadership scaricare gratuitamente. Download rapidi. Disponibile anche il download diretto tramite HTTP. Available Drivers (0) For certain products, a driver is necessary to enable the connection between your product and a computer. On this tab, you will find the applicable drivers for your product or in the absence of any drivers, an explanation of your product's compatibility with each operating system.
I get occasional frames with MASSIVE pixelisation. It's not in the original.tp file. Same frame there is just fine. Running it through quickfix doesn't help, nor does trying to output to a.mpv and a.ac3. If I run the output file, after streaming it into a.ts, through mpeg2repair (a great freeware mpeg2 scanner util) I get LOTS of temporal timestamp errors (yes, they are still there in b358) as well as bunches of illegal MPEG2 startcodes on the frames that pixellise. This really has me bummed.
Videoredo is simply flat-out the best linear editor I've ever worked with. And this problem has me stopped cold from using it for all my regular editting. I'm still stuck with Womble's products and all their buggy annoyances. Thanks - litz. Since I just installed a MyHD MDP-130, I'm very interested in this topic. I think that QAM recordings are going to be difficult to support. Because of the massive amount of data (double the normal ATSC signal) with lots of multiple streams there is a lot of difficulty recording the stream.
The MyHD hardware decoder is very tolerant of corrupted data when viewing live programming but there are lots of glitches during the record process which show up when playing back or editing. There is a 90 page thread on the AVS forum about this card. With analog you can see immediately that you have a poor signal but with digital, signal strength is no indication of the quality of the signal. I have a 9.4Gb file (QAM -256) that VRD won't open, giving the message 'no data found for the requested file'.
QSF won't open it either. However if I cut it up into smaller chunks with the trim and copy feature it opens and edits just fine. (lots of errors but QSF and/or editing clean it up OK. The trimmed file has 2 streams that when edited are 85Mb and 94Mb in size (this is from a 1.0Gb original cutting!) I successfully edited a 4Gb file (single stream) that had 4943 input sequence errors. This was 1 hour of the UniversalHD network, actual bitrate 14.03Mbps. To get clean recordings (just viewing has no problems) I had to install a fast RAID controller on a 64 bit PCI bus and use reservation recording with audio off, otherwise the recording had glitches even though live viewing was perfect. OTA has far fewer problems.
Mdp-130 Driver For Mac Os
I could chop off part of this file but VRD opens it when reduced in size so I don't know if uploading part of it would help. If you do want to see part of it, let me know how much.
OK, here's a nifty problem. I have a 5Gb.tp file that plays OK with MyHD, Media Player Classic, and VideoReDo. I did a 'trim and copy source file' to reduce the size of the original file before editing and the resulting file is now full of pixelization! I used both 358 and 320 with the same results. Did not edit or QSF. Just copying the whole file from one drive to another leaves it OK.
To get a sample small enough to upload without using the trim feature will require recording a 30-45 second clip that still shows the problem. I'm getting ready to record Battlestar Galactica on UHD so I probably won't have time to do much more testing tonight. Sending you any of the HD stuff is somewhat pointless since 50mb of file is not going to give you anything much useful. So I sent you 480i stuff. The symptoms are the same, so you should be able to figure out what's going on from that. And you get a good chunk of material to play with.
All are Duck Dodgers (yeah, if I'm gonna send you something it's gonna be something cool.) Source.ts (cut with HDTVtoMPEG2 beta 39) - plays PERFECT on MyHD.mpg written from videoredo of that file - plays with BAD pixelisation on MyHD, but plays fine in VideoRedo If you have trouble playing the.ts file, I've gotten it to play flawless in MyHD's software, and with Videolan's VLC player. Text files: mpeg2repair output on the.ts (comes up clean) Dr M (from m2edit) output for both the.ts and the.mpg.ts shows some timestamp gaps,.mpg shows lots of baaaad problems. These are capped off the MyHD MDP-130. One difference between this and the 'normal' MDP-130 caps is that this is using the beta MyHD software that extracts a single PID from the QAM stream, thereby greatly reducing the disk throughput needs. This should not affect things here at all, as it's no different than what the Fusion does.
I've had NO trouble editting any of these with Womble's products, other than the fact that their output is somewhat screwy and they're buggier then you could possibly ever believe. What does 'Video DTS gap' mean? Never heard of that term before. Perhaps you have some documentation on that. A google search turn up empty. Besides the MyHD player, what other player is showing massive pixelization, or any pixelization for that matter?
Fusion, VLC, WMPC, and VRD all play the MPEG without any noticable problem. What frames are showing problems? What options do you have set/checked on the ToolsOptionsAdvanced Stream page? Perhaps its a muxing issue. Be glad to fix the problem, once we can see / duplicate it. What does 'Video DTS gap' mean?
Never heard of that term before. Perhaps you have some documentation on that. A google search turn up empty. Besides the MyHD player, what other player is showing massive pixelization, or any pixelization for that matter? Fusion, VLC, WMPC, and VRD all play the MPEG without any noticable problem. What frames are showing problems?
Mdp-130 Driver For Mac Download
What options do you have set/checked on the ToolsOptionsAdvanced Stream page? Perhaps its a muxing issue. Be glad to fix the problem, once we can see / duplicate it. I ran his file to see if it had the same problems that I had seen. I was able to duplicate the symptoms I had seen on my files.
His file as posted plays OK for me but the problems I see only occur after I run it through 'trim and copy source file'. One spot is between 00:00:14.28 and 00:00:15.08 and the last is between 00:01:02.04 and 00:01:02.19 on the spaceship engine as it passes. If I started the trim at 1Mb instead of the beginning the pixelization still occurs on the same image. The engine distortion at 00:01:02.xx is the easiest to see. I agree it makes no sense but I have duplicated it myself on a number of my own captures. If I run QSF first, then 'trim and copy' the file, it does not pixelate. Litz, are these some of the spots you see the problem at?
I admit I can't decode the log file myself but have to reference the time counter on the display. We may be seeing two different problems but they sound the same to me. I ran his file to see if it had the same problems that I had seen. I was able to duplicate the symptoms I had seen on my files. His file as posted plays OK for me but the problems I see only occur after I run it through 'trim and copy source file'.
One spot is between 00:00:14.28 and 00:00:15.08 and the last is between 00:01:02.04 and 00:01:02.19 on the spaceship engine as it passes. If I started the trim at 1Mb instead of the beginning the pixelization still occurs on the same image. The engine distortion at 00:01:02.xx is the easiest to see.
I agree it makes no sense but I have duplicated it myself on a number of my own captures. If I run QSF first, then 'trim and copy' the file, it does not pixelate. Litz, are these some of the spots you see the problem at? I admit I can't decode the log file myself but have to reference the time counter on the display. We may be seeing two different problems but they sound the same to me.
I've tried to get one, but due to layering it's impossible to actually snap it. I've tried SAVING.jpg's of the suspect frames, but the.jpg's come out perfect. I'm utterly baffled now. I.SEE. totally pixelised video, but if I save a snapshot of the frame, it's perfect. You HAVE to use some kind of hardware mpeg player or commerical-level software like windvd or powerdvd. Something that overrides the system level mpeg2 codecs and uses its own.
VLC does not show the problem nor does videoredo or microsoft's own mediaplayer. I see it with MyHD's player, womble's products, and m2edit. Oddly enough, Moonlight's mpg player works fine (I guess it uses its own codec). It does NOT show up on the original.ts file. It DOES show up on anything output from videoredo, whether the trim/cut tool, QSF, or an actual editted save. I don't think it's the muxer, either, as I see the same thing if I save direct to elemental streams. Mpeg2repair and dr m are usually VERY good at detecting problems, though.
There's definately something strange about the.mpg output from the cable-sourced.ts streams. I've tried to get one, but due to layering it's impossible to actually snap it.
I've tried SAVING.jpg's of the suspect frames, but the.jpg's come out perfect. I'm utterly baffled now. I.SEE. totally pixelised video, but if I save a snapshot of the frame, it's perfect. You HAVE to use some kind of hardware mpeg player or commerical-level software like windvd or powerdvd. Something that overrides the system level mpeg2 codecs and uses its own.
VLC does not show the problem nor does videoredo or microsoft's own mediaplayer. I see it with MyHD's player, womble's products, and m2edit. Oddly enough, Moonlight's mpg player works fine (I guess it uses its own codec). It does NOT show up on the original.ts file. It DOES show up on anything output from videoredo, whether the trim/cut tool, QSF, or an actual editted save. I don't think it's the muxer, either, as I see the same thing if I save direct to elemental streams. Mpeg2repair and dr m are usually VERY good at detecting problems, though.
There's definately something strange about the.mpg output from the cable-sourced.ts streams. What I have noticed, from experience, is that the MyHD card, due to its hardware MPEG, is VERY good at showing errors in files.
It's pretty much reference standard in what it will accept. If it glitches, there's a problem.
Mdp-130 Driver For Macbook Pro
Some of the software players will simply skip right over an error, where the MyHD glitches. It may be that you need a card to help diagnose the problem. Can you use the VLC Wizard to convert the video from TS to PS and see if that pixelates? Also, how about converting from VRD PS back to TS. Do you still get the pixelization? There's one possibility that I can think of where the TS could be different than the PS. It has to do with the extra few bytes in the last TS packet of a frame.
Since all of our test players, including VLC, play the TS files and VRD conversions just fine I thought we handled that properly. But who knows?
Obviously something subtle is going on. I can't imagine why it would display on-screen with pixelization and not in the JPG snapshot.