Have had Video factory about a year, and with my Dell laptop and Sony TRV-900 has been working like a charm. I piced up a BUSlink firewire hard drive a few months ago and have been having a great time playing around with my new toys.
Edited a program on my desktop (VF 2.0c). Clicked on "Make Movie". Copied the resultant AVI files to my firewire hard drive. Brought the firewire hard drive to the laptop and tried to print to tape. (Can't print to tape from the desktop. Don't know why and got tired of trying to figure out) Spent 5 hours trying to get VF(still 2.0c) to recognize the camera, to no avail.
One problem: On the desktop, the firewire drive appears as Drive M. On the laptop, it appears as drive F. The 30 minute program consisted of (2) AVI files, 4.0 and 2.5GB respectively. When I tried to Print to tape, I'd point to the firewire drive, tell it to load the first file, and get an error message telling me there's a reference to a second AVI file on Drive M, and there's no drive M on my system. Funny thing was that the second AVI file is in the same directory as the first AVI file.
Copied the AVI files to the timeline and hit "Make movie" again (only this time on the laptop). The files rerendered (with "compression" turned off), then VF recognized the camera without a hitch, but would print about 1/2 of a frame, followed by a second of digital mess and static.
After more trial and error, I turned off the PC, removed the USB Zip disk and USB printer, then rebooted.
However, now the firewire drive was Drive E and once again, I couldn't connect to the DV camera. Manually loading the first of the AVI files to the "print to tape" dialog box gave me an error message that it couldn't find the second file (this time on Drive F)
Once again, from the timeline, loaded AVI files, MAKE MOVIE, and this time printed to tape, no problem.
One day wasted dumping a 30 minute photo montage to tape, but finished successfully.
Obviously the program has limitations in being unable to handle file paths. I'll be careful not to render anything from the laptop, with no USB peripherals attached.
It would be a nice feature to allow the program to deal with changing file locations.
Dave
Edited a program on my desktop (VF 2.0c). Clicked on "Make Movie". Copied the resultant AVI files to my firewire hard drive. Brought the firewire hard drive to the laptop and tried to print to tape. (Can't print to tape from the desktop. Don't know why and got tired of trying to figure out) Spent 5 hours trying to get VF(still 2.0c) to recognize the camera, to no avail.
One problem: On the desktop, the firewire drive appears as Drive M. On the laptop, it appears as drive F. The 30 minute program consisted of (2) AVI files, 4.0 and 2.5GB respectively. When I tried to Print to tape, I'd point to the firewire drive, tell it to load the first file, and get an error message telling me there's a reference to a second AVI file on Drive M, and there's no drive M on my system. Funny thing was that the second AVI file is in the same directory as the first AVI file.
Copied the AVI files to the timeline and hit "Make movie" again (only this time on the laptop). The files rerendered (with "compression" turned off), then VF recognized the camera without a hitch, but would print about 1/2 of a frame, followed by a second of digital mess and static.
After more trial and error, I turned off the PC, removed the USB Zip disk and USB printer, then rebooted.
However, now the firewire drive was Drive E and once again, I couldn't connect to the DV camera. Manually loading the first of the AVI files to the "print to tape" dialog box gave me an error message that it couldn't find the second file (this time on Drive F)
Once again, from the timeline, loaded AVI files, MAKE MOVIE, and this time printed to tape, no problem.
One day wasted dumping a 30 minute photo montage to tape, but finished successfully.
Obviously the program has limitations in being unable to handle file paths. I'll be careful not to render anything from the laptop, with no USB peripherals attached.
It would be a nice feature to allow the program to deal with changing file locations.
Dave