I'm using FAST.forward 1.7 and a Canon MVX1i PAL camcorder connected via the firewire cable.
When I try to record a DIF clip to a tape, the recording starts correctltly for 1 second, then small squares appear scattered on the screen, they progressively cover the whole image, the sound gets inaudible and after 5 seconds the recording stops on a blue screen.
When the I stop the clip on a steady image and start the recording, it records the image OK.
This does not happen at all with my other (previous)camcorder JVC DVX4 which records the same clip OK.
Has anyone an idea of what happens?
Thanks to all
(I have tried to set the Fast output to "Sony" with no result).
------------------
Szutt
Have you tried the registry value change discusse in another thread that spoke to similar problems with SOny camcorders. It may be that Canon has changed the IEEE 1394 chip set in their newer models and that has cause someslight change intimings.
Thanks for your input.
Can I add that I am operating under Win98SE and with a PAL camcorder. I have the feeling that the comments on previous threads refer to NTSC systems under WIn 2000 and XP. However, I am willing to look at this but, this sounds ridiculous, I can't locate this famous file "HKEY_LOCAL_MACHINE\SYSTEM...etc", where is it?
Another bit of information is that my cam corder records perfectly when I export the clip through the analog output of DVnowAV !!!
It is in the Registry. Run the program REGEDIT from the RUN or command line (DOS) prompt. But use great care to not make any other changes. I do not know whether or not it applies to WIN98 or PAL systems.
It probably effects timing of the IEEE1394 drivers, so it may not effect analog I/O.
OK, I could find:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
But in there no trace od FAST1394/Parameters?
I have mailed DAZZLE and found someone who seems keen to help. I pointed him towards those threads. It may trigger some ideas !!!
I'll try the same on Canon's side.
have you solve your pb?
I have the same with a canon mv300 camcorder
No, I haven't solved it and the Dazzle support service apparently let me down. I can't get anyone trying to help.
In addition to the above, The Canon DVin input works very well when it receives a signal from my ex-JVC camcorder firewire output.
So there is apparently nothing wrong with it.
Daazzlz seems to be the problem.
Have you finally resolved your problem. I see that your posted your question to thonderson who previously indicated:
"Not sure if your problem's been resolved, but mine turned out to be tape related. I have 4 Sony Premium, 2 Sony Excellence and 2 TDK whatever tapes. None of the Sonys can record from the Firewire port (symptoms above), but the TDK tapes work OK most of the time."
I must admit that I hadn't seen this indication until now and that all my tapes are Sony Premium's !!! I'm gonna try the TDK tapes but have you tried yourself with any result?
Sorry, the previous post is adressed to ygokou
quote:I'm gonna try the TDK tapes...
Did this help you? Getting curious...
Thonderston,
I tried a TDK tape and it did not help.
Not a surprise because actually the progressive image scrambling starts before I start the tape, when the cam is still on Pause.
The support service of the french Dazzle distributor (now that Dazzle have very couragesly abandonned any direct support... Thank you to them! My next acquisition will NOT be Dazzle) has recommended that I load the FAST version 1.75.
It did not cure the problem either.
------------------
Szutt
I've finally got it to work, but I'm not certain which is the change which made it work.
What I did:
Changed from ABIT MB with AMD Athlon CPU to MSI MB (i845E chipset) with P4 Northwood CPU (this PC rebuild was independant of my problem but the decision to move away from AMD is deliberate).
Reinstalled Premiere 6.0 and Fast 1.75build 263 (this is not new, I tried with the previous MB and it did not work), but this time I made sure that the "HKEY_LOCAL_MACHINE\SOFTWARE\FAST-Dazzle" registry key was removed before installing Fast 1.75, which I admit I never did before.
In a nutshell, Fast 1.75 may have cured the problem with my previous configuration if I had removed the "HKEY_LOCAL_MACHINE\SOFTWARE\FAST-Dazzle" registry key before. This I will never know.
If this is not correct, then the Abit+Athlon combination had something to do with the problem.