Bouke Vahl
Forum Replies Created
-
well, even starting /stopping a lot of times is not a problem if there is common TC.
But for the OP, this can work just fine. However, do test yourself.
Bouke
https://www.videotoolshed.com/
smart tools for video pros -
Wireless most of the time includes a delay. You can’t have that when editing.
Got to the audio forum and ask there about wired ones.
Bouke
https://www.videotoolshed.com/
smart tools for video pros -
I know what your problem is, and as i’ve already stated, in my optinion you should fix the port.
I don’t think the cable will work, as besides data, there is also communication between FCP and the deck over the same port. (Unless you have a 422 port as well, but since you capture from a camera, i don’t think so…)
But for 7 lousy bucks, just try it.
Not sure about you, but my time is valuable to me.
In my hourly rate, my time on this thread alone is worth more than the 7 bucks for the cable.Now we’re all very interested if it will work or not, so go to the local computer store, buy one, try it and please report back.
If it fails, and you’re too poor to get your computer fixed, any half decent G4 running OS9 can do the capture also, and those machines can be had for free nowadays.
Bouke
https://www.videotoolshed.com/
smart tools for video pros -
This should work (at least for media), if you use a XDcam style MXF format on output.
The files then are identical to camera generated XDcam MXF, and the XDcam plugin on Mac won’t know the difference.I do this all the time, although not from Vegas.
But since Vegas is Sony, it should be compatible.Over here broadcast standard is Sony style MXF, and our national broadcaster uses Vegas for QC on commercials…
(and lot’s of people use FCP to EXPORT to MXF, intended for broadcast)So, check what flavour of MXF the Vegas side is spitting out.
Bouke
https://www.videotoolshed.com/
smart tools for video pros -
No, not sustained.
And DV ain’t 50 Mb/s either, it’s 25 (senior moment here)
Nevertheless, even if it is not sustained, it is way enough to capture.
Low end Avid / Premiere / FCP users do it all the time, and i do it when i have to capture for a client who brings in a disk.
I even have captured with success to pocketdrives without a powersupply of their own.Bouke
https://www.videotoolshed.com/
smart tools for video pros -
DNxHD 180 is overkill, 36 if offline. Try 120,
But the compression isn’t the limiting factor. Data rate is.
Now 180 runs at 180 /8 = 22 megaByte per second.
Any half decent harddisk can do so.
No need to go back to the originals to conform, it won’t get better than this….Your machine seems fine, just toy with it and you’ll see.
Bouke
https://www.videotoolshed.com/
smart tools for video pros -
eeer, Walter,
USB2 is 480 mb/s.
DV runs at 50 mb/s, so speed is not an issue…
I often capture to USB disks, no problem there. The reason FCP cannot capture over USB lies somewhere else. (Start with looking for an USB port on the back of your deck…)(for correct numbers, note that the bus speed can be the weakest chain, but often the drive speed is the weakest chain, so actual speeds may be lower)
But i agree with the others, just get the darn port fixed and be done with it.
Bouke
https://www.videotoolshed.com/
smart tools for video pros -
It highly depends on the output format.
Some computers allow to rotate the screen, in that case normal export would be good.
You can also use QT pro to rotate the display setting.
Or, make a sequence that is 9:16, paste in your work and rotate the whole shebang, then render out.
(most illogical option in my book, but again, it highly depends on what the intended output is.)So, talk to your client about what he is going to do, then decide what is wise.
Bouke
https://www.videotoolshed.com/
smart tools for video pros -
Bouke Vahl
December 31, 2010 at 11:38 am in reply to: Reel information disappears when using Raid 1 G-Safe drveI don’t think it’s the storage per se…
TC/Reel info lives in TWO places.
In the QT itself, AND in the project.
This makes sense. If it was not in the project, it would be impossible to re-capture / export XML if the files are not online.
(remember the first versions of Premiere where this was the case. Loose mediadrive, start editing again…)So indeed after changing tc / reel info, the mediafile must have an updated file modification time. If not, FCP only updated it’s own database.
Reasons for that could be too long pathnames, or network storage.
(Not sure in this case. I do know for sure there is a bug in QT, changing TC info on some network drives can make clips corrupt.)Now sometimes FCP can get confused, if the actual clip attributes (tc/reel, but also amount of video/audio tracks!) do not match original attributes in the project.
Now the solution for this:
Reconnect the media files, even if they are online!
On a reconnect, the project is updated with the actual media attributes.
(You need to club it into submission, as the files are online.
So do a search and force FCP to reconnect)For the OP:
If the file modification date is not changed, probably the clip isn’t changed. Simple to test the clips though, get QTchange from my site, it will display the TC and Reel info. (The free demo will do just fine for this)
https://www.videotoolshed.com/product/42/qtchangeIf the clips indeed are not changed, you can try if QTchange is able to do it.
(Again, the free demo will do this as well, although just on one clip at a time)
If both fail, it has to do with your drive, pathname or file permissions.
(Of course the QT’s must be write enabled)In all cases it is a good idea not to have too long pathnames / filenames, and no special characters in your pathnames.
(No idea why that is, just in my experience i’ve encountered lots of trouble coming from just this)hth,
Bouke
https://www.videotoolshed.com/
smart tools for video pros -
Bouke Vahl
December 30, 2010 at 1:52 pm in reply to: Timecode issue when capturing through Sony JH3 – AJA IO into FCP[Simon Davies] “AJA IO -(Firewire 9pin”
and then:
[Simon Davies] “I’m capturing 422.”
So, are you capturing 422 video with FireWire machine control, or are you capturing with RS 422 control?
Or, worst case, are you indeed capturing composit video while using Firewire machine control?
If you have an AJA, use 9 pin serial control and SDI video. Firewire control is not as fast as 422 control.
Easy to test. do NOT have a firewire cable between the deck and other equipment.Bouke
https://www.videotoolshed.com/
smart tools for video pros