Forum Replies Created
-
to mark the in-point for video press Control-I, to mark the out-point for video press Control-O
to mark the in-point for audio press Command-Option-I, to mark the out-point for audio press Command-Option-Oyou can do this in timeline or viewer and edit using the canvas overlays, or keyboard shortcuts, F9 and F10 etc, for Insert, Overwrite
you can see these split edit shortcuts under the Mark > Mark Split submenu
alternatively drag and drop or otherwise edit your clips to the timeline, then if not turned off you should turn off linking (Shift-L)
now you can use the roll tool (r) to pull your edit to the desired shape; or select your edit point first, then move your playhead to the desired new postion and press the extend key (e) to snap the edit to the new position… so many ways to skin a cat
-
Seems like you may need the Flip4Mac MXF Import Component https://www.flip4mac.com/mxf.htm
Their component will support the PDW-V1. You can follow the instrucitons in the MXF Import Documentation with the following notations: the PDW-V1 has the same slider switch as the PDW-1500 (remote/local/network). In order to FTP from the device, the switch must be in the “Network” position. Also before you log in, the deck must be in STOP mode. If the deck is in STILL mode, you will not be able to log in… To eliminate this problem before logging in, just press the STOP button on the deck.
-
as far as I know the Avid Meridian codecs that are available for direct download from Avid support are not OSX10.4 compatible.
one way to get Tiger compatible versions tho’, is to register for and download the free Avid FreeDV installer (from Avid’s website) … you don’t actually need to install the app, you just need to extract and install the quicktime components from the installers package:
right-click on the .pkg file and choose “Show Package Contents”
then double-click the Content>Archive.pax.qz file, which will un-archive first to an “Archive.pax” file and then to an “Archive” folder
inside Archive>Library>QuickTime are the codec components –
AvidAVDJCodec.component
AvidAVUICodec.component
and also, if you want it, the AvidAVdvCodec.component (which is Avid’s DV codec)drop these into your root Library>QuickTime folder then trash Archive.pax.gz, Archive.pax and the Archive folder
cheers
Andy -
choose Final Cut Pro > Audio/Video settings… and select the Capture Presets tab
choose the capture preset for DV Advanced and press the Duplicate button
in the Capture Preset Editor change the name to DV Advanced Anamorphic (or similar)
put a tick in the Anamorphic 19:9 checkbox
then press OKyou just created your own DV Advanced Anamorphic preset, now you just need to choose it
-
Hey Guys
No argument with your advice but its not the issue at hand.
the particular bug being described is visible both on the Canvas and any external monitor … its not particulatly apparent when working with DV varients but is markedly more visible when working with uncompressed footage.put some uncompressed clips on an uncompressed timeline then turn on range check and see for yourselves
bizarre but true
Andy -
its not titlesafe and wireframe overlays that tend to cause this, its usually the range check overlays.
do you have the range check overlays turned on? (Ctrl-Z to toggle on/off) -
I’m not sure if this is the issue at hand, but the Sebsky Tools application was coded prior to quicktimes ability to handle more than two channels of audio. If you’re trying to use it with polyphonic bwf’s then that might be the cause of the problem.
BWF2XML on the other hand is under active development … although not free, there is a free 14 day trial version, so you might as well see if it works for you first. -
I’m not sure if this is the issue at hand, but the Sebsky Tools application was coded prior to quicktimes ability to handle more than two channels of audio. If you’re trying to use it with polyphonic bwf’s then that might be the cause of the problem.
BWF2XML on the other hand is under active development … although not free, there is a free 14 day trial version, so you might as well see if it works for you first. -
almost certainly a permissions issue …
if you don’t need to set any user level permissions on you media drive then do as Don suggests, and turn on the “Ignore ownership permissions” for that disk
if you do need to use permissions to limit disk access then create up a scratch disk folder on your media drive first (using and admin login), and then ‘share’ it to all your FCP users by using Get Info (cmd-I) and setting the permissions to Read & Write for owner, group and all (or as required) … then in FCP set up the scratch disk to point to this shared folder