Well, the DC Series do have an excellent mjpeg hardware encoder on board as they where/are sold as semi professional capture cards.
Keep in mind that mjpeg is like mpeg but in YUY2 AND like "I" Frame only while CBR capturing.
So a professional Studiostream can be found beside some others as
- Betacam SX (Mpeg-2 @18 MBit/s)
- Betacam IMX (Mpeg-2@ 50 MBit/s)
And all these are "I" Frame only as thats needed for frame acurate cutting and also CBR is used.
Betacam SX already is quite lossy as "I" Frame only would need much more bitrate.
So Betacam IMX at 50Mbit/s is a mega HQ Studio way of digitizing.
Now your DC10 (or mine DC30) are able to capture at 6000/kbytes per second using a very good Zoran/Philips chip.
6000*8 = 48000
48000/1024 = ca. 47Mbit/s!! And that at 4:2:2 YUY2! (PVR 250 mpeg2@MainProfile uses 4:2:0 YV12, Digi Betacam uses mpeg2 4:2:2 profile!)
So the VERY big potential of that card is just by 20% used if using for digitizing "TV Sheep-crap"
The only disadvantage is that this card doesnt got component Inputs like the mega expansive Targa system (in the past).
But s-video connection (means Y/C separated) at least is a very good quality mode/connection.
So this card can even be used to digitize streams provided by a Betacam SP Device and that was the standard some years ago in broadcasting editing services.
See the point? Thats why you should everytime "smile" when looking at this card.
A friend of mine (from whom I got my DC30) used that one on a MAC for preparing/cutting video jobs to give them to the WDR afterwards (West German Broadcasting Station).
BUT! 3300kbytes/s when capturing 768x576 is at the limit!
Why? Cause even if TV Signal is crap (in relation) and even its less detailed - on the other hand its much more complex cause of uneasy components like noise! And if you would inspect your stream very carefully at 200%-400% Zoom in Vdub you already can see some artifacts, cause mjpeg needs much more bitrate then mpeg2 when using B and P Frames.
And thats the goal from mjpeg as its like I frame only, means now extra compression-lossy-routines given like predicted and Bidirectional frame algorhythms (P / B). Give it room to breath and an excellent signal as input and you can see the difference.
BTW: We talked at gleitz forum about that Picvideo3 YV12 issue!
It seems that avisource() from avisynth 2.5x on uses as default a request of a YV12 stream. And if the codec is able to provide that, then the picvideo
3 internally changes the colorpspace to YV12.
Now that Pixel_Type="YUY2" workout "could" be the solution, ... IF Its proofed that picvideo3 REALLY doesnt change the colorspace by that!
But if he again re converts the conversion to YUY2 again, that would be a mess!
So I personally would stay with picvideo2 till that is proofen not to be the thruth