Frage von niXwiss:
Good day,
I have a new ext. hard drive Maxtor OneTouch III FireWire 400 / USB 2.0 with 300GB, connected s.Firewire.
With Let's Edit I have recorded a video of the digicam. I will only edit video and burn it to DVD (DVD-RAM). For this reason, I have laid down in the record set equal to MPEG2.
Min after about 24th came the message that the hard drive is too slow and the recording was stopped.
Had the same procedure with the same video repeatedly minute message like the top to the 18th
The recording setting I then set to AVI2 and the video was completely captured.
Only on capture with AVI2 be yet more data transfer and has accepted the hard drive.
What happened?
Thanks for the enlightenment.
Antwort von StefanS:
I can only advise, not because you give some important information.
It is very likely the case that the error is wrong!
I simply presupposes times that you mean a digicam with MiniDV camcorder.
If you now the DV stream of the coming of the camera as a DV AVI (no preference whether importierst Type 1 or 2), then finds, in principle, only one copy of the data held with a Nenndatenrate of 25 Mbit / sec.
Please Erstpart s.dieser place the discussion of Nenndatenrate, effective data rate, etc., which we already had, who are interested, it is about the search :-)
Now, whenever you choose MPEG 2, then the import program has to unpack the DV stream equal, re-encode to MPEG 2 and then write them to disk. Since the calculator is already quite time to sweat. And then stop claims from any component, the other was to blame.
How it looks as if you can save to an external disk, but on a plate in the calculator?
It may be synonymous, that the import settings you have chosen wrong, I can not judge, however, because you withhold us.
In principle, however:
If you want to cut rework /, you have chosen the wrong path. Stay first with DV AVI, edit and cut, until you are walking into the highly compressed and so much more afflicted with loss of MPEG2.
Why this is so, if interested you can find with the search here in the forum.
Greeting
Stefan
Antwort von niXwiss:
Hi Stefan,
Thanks for your info. You're lying right with the error, the culprit is probably the sawn timber Let's Edit2.
In the Canopus forum I found some info about it, describing the same characteristics as those encountered.
What important information would you still needed? The next time I want to provide more accurate data.
Do you mean with the import settings as PAL, DVCAMERA etc.? Much more I can not select in the program.
I will follow your advice and just capture with AVI.
Antwort von StefanS:
What important information would you still needed? The next time I want to provide more accurate data.
Do you mean with the import settings as PAL, DVCAMERA etc.? Much more I can not select in the program.
I will follow your advice and just capture with AVI. Thanks for the feedback. That tells me again that my crystal ball ends up with only a light mist still out, and again a hit :-)
Fun aside. If you suspect a problem in your computing environment, no preference whether hardware or software, is a description of the system, just as accurately as possible, at least somewhat helpful, but usually necessary. How are we to limit the error otherwise.
And if the software is still synonymous in the game, then we need time as accurately as possible the settings for import / export / etc.
Otherwise it time to call at VW, say you had a car that is red and it is somewhere snapping. How will VW help you if you have Ford one s.dem you yesterday an incorrect exhaust yourself have screwed who strikes now against the floor pan?
Greeting
Stefan
