[Andy Mees]

Looking at the specs I think the deck only allows 4 channel audio for IMX .. you’d have to record to an XDCAM HD format for 8 channel I think.

Edit: Took another look. 4 ch applies to IMX with audio at 24 bit … switch to 16 bit audio, then you can get 8 ch/16 bits/48 kHz. From the deck’s tech specs…

Recording/Playback Format:

Video:
MPEG HD422 (50 Mb/s)
MPEG HD:
HQ mode (VBR, maximum bit rate: 35 Mb/s)
SP mode (CBR, 25 Mb/s)
LP mode (VBR, maximum bit rate: 18 Mb/s) (Playback only)
MPEG IMX* (CBR, 50/40/30 Mb/s)
DVCAM* (CBR, 25 Mb/s)

Proxy Video:
MPEG-4

Audio:
MPEG HD422: 8 ch/24 bits/48 kHz
MPEG HD: 4 ch/16 bits/48 kHz
MPEG IMX*: 4 ch/24 bits/48 kHz or 8 ch/16 bits/48 kHz
DVCAM*: 4 ch/16 bits/48 kHz

Proxy Audio:
A-law (8 ch/8 bits/8 kHz)

*Optional PDBK-S1500 hardware key is required for DVCAM and MPEG IMX recording.

[Andy Mees]

Hey Adam
If you want to record SD you should be choosing MPEG IMX 50, not one of those HD presets that you listed. What is your sequence format, is it HD or SD?
Regarding audio on the reimported clip, lets get the export in the right format first! (But for what its worth, make sure you have not enabled Down Mix in the Audio Mixer tool).
Cheers
Andy

[Andy Mees]

Hey David

I use XDCAM Browser in the Canopus suites to facilitate tapeless import to our programmes projects but other than that I still just use XDCAM Transfer for FCP. Unless or until XDB allows to import/send in the background then its a step in the wrong direction for me … but it’s still early days for this new’ish Clip Browser / XDCAM Transfer hybrid incarnation tho so I’m quite hopeful it will eventually be the tool of choice for all the right reasons. Using Clip Lists is perfect to create simple feed point assemblies, good thinking … re the slowness with import of those lists, are you noticing this specifically and only with Clip List edits or with any and all import in XDB? And are you working with version 1.0 or version 1.1? Any difference in performance? Does the speed improve if you create the Clip List in XDB (or Clip Browser) but then bring it into FCP using XDCAM Transfer?

Cheers
Andy

[Andy Mees]

Sadly Niko you have your work cut out for you. The Boris text generators do not make text available through regular (XML) export, so there’s no way I know of to easily automate what you want. You might have a look at the Boris’s XML Transfer app and see if theres some straightforward way to roundtrip the needed text through After Effects … but I’m not sure that even their own tool can access Boris text generator data.

[Andy Mees]

how about a good old fashioned wipe?

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Andy Mees]

Dan’s spot on (and thats exactly why I asked you to supply more info). If you just want to remove entire specific filter(s) from multiple clips then I’d recommend Edit Mule’s Filer Remover … much more straightforward for the average user than messing about in XML, and it’s always worth supporting the FCP development community.
https://www.editmule.com/pages/plugins/plugin.php?id=3

But If you just want to manipulate a single attribute then XML is the only way.

Cheers
Andy

[Andy Mees]

Select a clip in the Browser, open it into the Viewer window and adjust some of the Motion tab properties
Now choose File menu > Export > XML… accept all following settings options to save the resulting XML to a location of your choice
Open the saved XML file using Text Edit and examine it, if you search through the clips attributes you will see its attributes are described there as text
Your mission, should you choose to accept it, is to figure out which element describes the single attribute you wish to change, and then to apply that knowledge by modifying a similar XML export of the clips or sequence you wish to target … you can then use File > Import > XML to reimport the changed XML so as to apply those changes within your project.

Sounds complicated? Its not that bad in practice but its not for the feint of heart. Question is tho, whether you really need to do it at all … if you told us specifically what attribute it is you need to change it may be that there is a much simpler solution.

[Andy Mees]

You can do it via manipulation of an XML copy of the clips.

[Andy Mees]

Yay! Thats good news Michael, thanks for posting back to let me know 🙂

Hence 2 theories:
a) I cleared up a lot of space on my external hard drive that was getting full (800 Gb out of 1000), now it’s less than 1/2 full; does that have anything to do with the playback issue? or…

Absolutely, that would certainly affect your playback performance as full drives will tend to perform more poorly than an emptier drive.

b) with my past set-up, the order in which I turned on the DV camera for playing back on the SD tube and refreshing A/V device once had an effect on the camera being recognized or not. Now it doesn’t appear to. But is that a theory?

View menu > External Video > Refresh A/V Devices should be all thats needed to allow FCP to see your external DV device if and when its not already been recognised … thats not something that should have been affecting the issues above tho, as the option for Apple Firewire would have been disabled in the Video Playback menu had it not been recognised.

c) I was just plain doing something wrong and I don’t want to admit it or can’t remember and I need a youth cure 😉

That’s always a possibility, but more likely it was option a) above. But if you find the youth cure you please please let me know.

Cheers
Andy

[Andy Mees]

Your friend is correct … dpi is meaningless with respect to your video work, its a term solely relevant to print resolution. As far as using images in your video is concerned you are only interested in the frame size.