Phillip Grey
Forum Replies Created
-
I’m the latest victim of this problem. Tried deleting the related cache files and reimporting but am getting the same problems with the same set of clips. Again, this clips are the same as others. I’ve even tried opening a new project and only importing these clips but I get the same problem, even before they’re added to a sequence.
Any advice is highly appreciated.
-
Having the exact same issue with Quicktime Pro 7.7 for Windows, running Windows 7. At work, we use Quicktime Pro (not sure which version #) for Mac, and we can set the data rate to whatever we fancy (we go with 70,000).
Any help appreciated.
-
We were using third party batteries. Since the power cuts off, I’m wondering if this is the likely culprit. This has been an ongoing issue for a few months, occurring 5 times so far with four different shooters, which rules out user error. Wondering if there’s a reason third party batteries are so much cheaper than Canon’s… We had a third party charger spark a while back, so this is now my main suspect. Has anyone else experienced this?
-
I’ve done another test.
I tried using the same Firewire cable with the same camera using Sony Vegas 9.0e (32 bit) on my Windows XP computer. It did not exhibit this problem whatsoever.
This narrows down the problem: it may be related to Sony Vegas 9.0e 64 bit. Has anyone else encountered this problem?
I have serious doubts to believe it’s the Firewire port on the computer, because it captures trouble free with VidCap 6. I’ve tried all 3 Firewire drivers available on Windows 7 and have had no luck resolving the problem with any of them, but again I’m doubtful that’s the problem because there’s no trouble with VidCap 6.
I can only assume it’s related to Vegas Pro 9.0e (Build 1146) 64-bit. Any thoughts would be greatly welcome…
-
Update: I just tried a different camera and got the same results, so that rules out the camera. For the heck of it, I also tried all 3 drivers again, and this still hasn’t solved anything. It seems almost certain this is an issue with Sony Vegas 9.0e (especially considering it uses Vegas 6 capture) or one of its settings. I’m hoping it’s just a setting I can correct.
-
Thanks to all that have shared their input. I was able to resolve the freezing issue by reading the Canon manual. For future reference for anyone who has this problem, for me it was solved by:
turning off the camera and computer, disconnecting the camera from the firewire cable, turning the camera and computer on (don’t connect yet!), connecting the camera once the computer had fully booted, and then and only then opening up the NLE (Sony Vegas 9, in this case).
Now, it does periodically go on and off from the screen so there is still obviously a problem. Fridrikur, my new computer is running Windows 7 so I’ll look into that fix. My other computer is still Windows XP, so first I’ll check and make sure it doesn’t happen on that one. If it doesn’t, then I’ll know it’s a Windows 7 driver issue. Otherwise, that problem will remain an unsolved mystery.
-
So now that I’ve clarified, would you see I’m good to buy this computer?
-
Oh, I intend to transcode. I didn’t mean editing straight from the camera; I just meant editing transcoded 7D footage. I’ll probably use Neoscene.
I’ll definitely be staying with Vegas.
-
Alright, I updated to 9.0D and I see that command feature now but I still can’t get it to work.
I chose:
Command: WMClosedCaption*
Parameter: {RU4}{CR}{R15In00Wh}{TabOff1}New TextI rendered this and watched it in Windows Media Player with the Captions and Subtitles option turned on but to no avail.
*I also tried the TEXT command.
-
In that case, how do you do actual closed captioning? My plan is to take some video (with closed captioning) and then shoot it off the TV so if there’s a way to make closed captioning that would work, as well.
I’ve been experimenting with the cookie cutter method in the meantime. For the most part, it does the job but it’s painstaking and not 100% satisfactory. Thank you.