RE: dvgrab data on Windows machine
Brought to you by:
aeb,
bencollins
From: Mark K. <mk...@co...> - 2000-05-31 16:27:25
|
Arne, I have a mixture of machines here, so this is all getting confusing. Possibly I should limit my reporting to only one or two machines until we get things under control... My stable of 1394 enabled machines: Work Linux boxes: a) 433 Celeron b) 200MHz Pentium c) 333 Pentium II Home Linux Box: a) 750MHz Athlon b) 500MHz Pentium III (no 1394 card - on network) Work NT Box: a) 300MHz Pentium II with Adaptec Hot Connect 8940 Your table below is essentially correct, but the two entries under xdvplay that say 'works' should also say 'plays at about 1/4 speed'. Watching the clips it looks like xdvplay is not dropping too many frames - it's just going VERY slowly. My 10 second dv1 format dvgrab clips played using xdvplay take about: 45 seconds on the Celeron 433 55 seconds on the Pentium II 333 doesn't play on the Pentium 200 (no MMX?) My 10 second dv2 format clips, when played with WMP take about 14-15 seconds. I tried them at 50%, 100% & 200% screens. All three screen sizes took the same amount of time. It is very clear that WMP is dropping most of the frames in these clips. On Real Player 7.0 Beta, they 'play', take about 14-15 seconds, but the screen is black. (No picture) I tried another simple test to look at WMP. I downloaded an mpeg clip from the Broadcast 2000 site (titanic.mpeg) and played this clip. It reports that it is 38 seconds long, and it takes 38 seconds to play in WMP. Granted, different compressors/codecs, but it worked as expected with respect to time. I wanted to download some AVI clips from the web, but a quick search yields only XXX sites and I don't want to get fired!!! I guess I'll have to deal with that problem on an after hours basis!! ;-) I am unclear what I am to expect from xdvplay. Is xdvplay expected to drop frames automatically to stay in time? (Probably necessary to sync with audio...) Or does it just cycle through the database and display the info? (45 seconds/55 seconds) almost == (333 MHz / 433 MHz) -- Coincidence? I am personally hoping that the problem on the Windows box may be small. I am particularly curious about the differences between the two file formats when I look at the file properties. The dv2 format, which plays, also provides information about the encoding of video and audio. The dv1 format, which does not play, does not provide any information about the encoding, which is consistent with the type of failure in WMP. I am hoping that the data is good, but something simply got messed up in the packaging of the file? I'm happy to provide more info as you need it. Mark -----Original Message----- From: Arne Schirmacher [mailto:ar...@sc...] Sent: Wednesday, May 31, 2000 9:00 AM To: 'lin...@li...' Cc: mk...@co...; 'Mark W. Knecht' Subject: RE: dvgrab data on Windows machine Hi Mark, thanks for testing the dvgrab software, I can't do any NTSC related work here. xdvplay currently does not recognize the dv2 format. I'll fix that later. The weird thing is that your windows box doesn't display AVI files created with dvgrab 0.7. I thought this version is working and stable. I would guess that you do not have DV codecs on your windows system, but then the dv2 format should not play either. Let me recollect the information from your emails, could you please verify this: | xdvplay | Windows media player | RealPlayer ---------------------------------------------------------------------------- dvgrab 0.7 (dvgrab_latest)| works | fails | fails dvgrab 0.8 --format dv1 | works | fails | fails dvgrab 0.8 --format dv2 | core dump | plays at half speed | fails Sigh. Let me get back to the code... Arne |