I am transferring mini-DV tapes to PC, and have gone through 8 of 9 tapes with no issues. Am using Ulead DVD Movie Creator 3 Disc Creator, capturing the mini-DV to MPEG format, settings: Variable Bit Rate 7000, 25 frames PAL.
The one tape is causing me problems, because it's a 1 hour 2 mins 30 seconds, and when I go through the above process, the end result file is only 48 mins in length. During the record process, the tape really plays through the 1 hour 2 mins and 30 seconds.
Reviewing the content, the last half of the Video file is playing a fraction sped up? I have tried options like 'Transfer Full DV tape' 'Fixed length - 1:03:00' about 5 times - (yes, wasted 5 hours) each time the end file size result is slightly different (~2.8gb) but never the same.
I have never had this problem before, used over length tapes too. The settings are definitely SP, never LP, the tape is Sony Mini-DV PRO tapes, using Firewire, and definitely enough disk space.
Tried:
1. WinDV to capture the AVI RAW - 13.x gb and it's fine - plays normal speed.
2. Another computer with DMF 4.0 Trial - captures 1:02:22. (Didn't want to screw up my setup of DMF 3.0, as it asked me to uninstall it before installing DMF 4.0 Trial). Anyway, aside, what on earth is with DMF 4.0 Transcoding every x mins. I can't stand it... DMF 3.0 on my main computer can get through a whole tape before doing any transcoding. Is there a new setting or something
So definitely, can anyone suggest or think of anything wrong, or is this something Ulead need to look at and fix it.
Transcoding - wrong timing - software bug in DMF3?
-
heinz-oz
How could Ulead look at and fix your tapes? There is definitely something fishy here. Why do you capture to mpeg?
I'm glad you have plenty of disk space. By the way, how much is plenty? What about memory, CPU speed? I think there is something wrong with your tape or your system is running out of resources.
I'm glad you have plenty of disk space. By the way, how much is plenty? What about memory, CPU speed? I think there is something wrong with your tape or your system is running out of resources.
You've totally misread what I wrote. Ulead need to look at fixing DMF 3. Not my tapes... there's absolutely nothing wrong with them, as evidenced with the RAW capture (the RAW capture DV-AVI was 13.x gb as mentioned). I capture to MPEG only because it fits on a DVD as a backup and is relatively good enough.heinz-oz wrote:How could Ulead look at and fix your tapes? There is definitely something fishy here. Why do you capture to mpeg?
I'm glad you have plenty of disk space. By the way, how much is plenty? What about memory, CPU speed? I think there is something wrong with your tape or your system is running out of resources.
As said, I tried all options, Capture fixed length, Capture Full DV Tape, everything and it comes to approximately 48 mins, but not always exactly the same on each 5, now 6 attempts.
I've got multiple disk, 180gb and 200gb. Memory is 2gb, (2x 1gb DDR400 Dual Channel/Paired, 2-3-2-5 OCZ Platinum) - absolutely no problem there. CPU is a Pentium 2.8ghz HT 800FSB. Plenty of memory, paging, resources; temperature runs a cool 36 degrees celcius; 480W Antec NEO.
I believe there's a bug in the algorithm in my above mentioned situation, causing the failure to capture the correct speed. I have not come across it before, so if anyone else has had this happen, I would like to know why.
You capture 8 or 9 tapes with no issue, then one causes a problem? I would also look to the tape and its contents, not the software. Remember, capturing with windv is not really a capture, it is a copy. Whatever is on the tape is transferred 'as is' to the disk. Capturing to mpeg requires encoding, as evidenced by the file sizes. What is on the tape that is giving problems, particularly at the point were it speeds up. If for example, there is high motion or fast scene changes, the pc may not be able to keep up with the input and create the mpeg at the same time, and may be hastening the encode process.
Try changing the capture options, lower the bitrate or make it CBR, this may help with the 'on the fly' encode. Alternatively use the avi and convert to mpeg, it will take longer than your usual process, but hey, you've wasted 5 hours already!
Regards,
Greg
Try changing the capture options, lower the bitrate or make it CBR, this may help with the 'on the fly' encode. Alternatively use the avi and convert to mpeg, it will take longer than your usual process, but hey, you've wasted 5 hours already!
Regards,
Greg
Hi,
Yeah, thanks for the help... sorry if I sound annoyed, i'm just very frustrated - it's worked flawlessly for a year before. Checked all patches etc...
It worked with DMF Trial 4, so it seems there is something in DMF 3 DC it doesn't like - all the settings were exactly the same.
I might just log a ticket for the Ulead developers to see if they bother fixing it... though, i won't be upgrading to Version 4 any time soon. The features I tried in the trial are a very limited upgrade from 3... pan/zoom from stills was something that interested me, until I found it could only be applied once.
I'm quite certain this is bug though - I can repeat it too.
Yeah, thanks for the help... sorry if I sound annoyed, i'm just very frustrated - it's worked flawlessly for a year before. Checked all patches etc...
It worked with DMF Trial 4, so it seems there is something in DMF 3 DC it doesn't like - all the settings were exactly the same.
I might just log a ticket for the Ulead developers to see if they bother fixing it... though, i won't be upgrading to Version 4 any time soon. The features I tried in the trial are a very limited upgrade from 3... pan/zoom from stills was something that interested me, until I found it could only be applied once.
I'm quite certain this is bug though - I can repeat it too.
No problem,
You said it worked with MF 4, but on another computer, not really a definitive test, you need to compare apples to apples.
Maybe the other pc can handle the transcoding, maybe whatever is causing the bug is fixed in MF 4.
I have my doubts, however that Ulead will look at supplying a patch to potentially fix something in an older version that is already fixed in the newer version.
Out of curiosity, install MF 3 on the other machine, and see what happens.
Regards,
Greg
You said it worked with MF 4, but on another computer, not really a definitive test, you need to compare apples to apples.
Maybe the other pc can handle the transcoding, maybe whatever is causing the bug is fixed in MF 4.
I have my doubts, however that Ulead will look at supplying a patch to potentially fix something in an older version that is already fixed in the newer version.
Out of curiosity, install MF 3 on the other machine, and see what happens.
Regards,
Greg