[Sean Oneil]

Or you can use NTFS on your Mac:

https://macntfs-3g.blogspot.com/
https://www.paragon-software.com/home/ntfs-mac/

Sean

[Sean Oneil]

Christian,

You need to read up on the difference between a “Fibre Channel Initiator” and a “Fibre Channel Target.”

Putting a fibre HBA card (like that Qlogic) in a storage server will not make it a Fibre Channel target device. HBA cards are initiators which designed to connect to external storage (targets) – not “become” the actual storage (hope that makes sense). You don’t just plug them into each other like you do with ethernet networking.

That said, there are special drivers and software that can turn a regular server into a FC target using certain HBA cards (particularly the Qlogic cards). But I warn you it is very complicated and unconventional. Here is one example:

https://opensolaris.org/os/project/comstar/
https://developers.sun.com/openstorage/articles/opensolaris_storage_server.html

Another option is to get something like this:
https://www.areca.com.tw/products/fiber_to_sata_ll.htm

Sean

[Sean Oneil]

[Stephen Franciosa] “When I drag them onto my 24 frame timeline I get a green bar along the top which I believe is associated with a speed filter. Which would make sense. If these files are dragged onto a 23.98 timeline (a different frame rate) no bar appears.”

This is a new “feature” in Final Cut. Final Cut does not actually know what speed the audio is supposed to be (24.00 or 23.98). So when you import it, it just assumes that whatever your Easy Setup is, that is what speed the audio is supposed to be. This problem also occurs with PAL stuff.

Remove the audio files from your project. Save and quit FCP. Now relaunch and change your Easy Setup to something that is 24.00fps (not 23.98). Now import the aif files. You’ll now see the exact opposite. On a 23.98 sequence you’ll get a green bar, but on a 24.00 sequence it will be fine. Since what you tried is out of sync, I would assume the Pro Tools audio is supposed to be 24.00.

Sean

[Sean Oneil]

A more nuanced option. Edit on an HDV sequence, but go into “Sequence Settings -> Render Control” and change “Codec” to ProRes.

Sean

[Sean Oneil]

[gary adcock] “STOP using the RT menu –

follow Jeremy’s directions and it will work.”

Follow this advice. Final Cut doesn’t do 2:3 pulldown. You need to use a 23.98 sequence and let the Kona add the pulldown during video playback.

Sean

[Sean Oneil]

You’re very misguided on this issue Zane. I’m sorry.

Yes, if a CPU is running at 3.2ghz, it will generate more heat than running at 1ghz. This is true for all CPUS. If you are rendering in Compressor, it will put out more heat than if it’s sitting idle. Overclocking has nothing to do with it. The Xeon in a Mac Pro is rated up to 3.2ghz. That’s why there are 3.2ghz Mac Pros for sale. So the temperature will NEVER exceed spec using this software based overclocker. It is physically impossible.

REAL overclocking involves increasing the core voltage. This is where significant excess heat comes from. This is where advanced cooling may be required. This is where you could potentially damage your computer.

But whatever, I don’t know why I’m arguing with you over this. I’ll make you a deal. If you can fry your Mac Pro’s CPU with this utility, I’ll give you 10 thousand dollars.

Sean

[Sean Oneil]

You can edit on an HDV sequence, go into sequence settings and set it to render effects-only as ProRes (this is a new feature with FCP6). That’s probably the best option.

Sean

[Sean Oneil]

[Zane Barker] “I am sorry but anything that overlocks the CPU is going to generate more heat, thus increasing the possibility of frying the CPU or the logic board.”

Don’t be sorry. Just do some research and understand why you’re wrong.

Sean

[Sean Oneil]

This app cannot fry the motherboard or the processor. It is just software that runs in the OS. It doesn’t increase core voltage, it doesn’t increase heat generation. Even if it did

Worst possible case scenario is that you have trouble starting up your system disk and you have re-install OSX – upon which there will be no trace of this overclocking app whatsoever.

Again, I think using this app is a very bad idea for several reasons. But voiding your warranty is not one of them.

Sean

[Sean Oneil]

I didn’t carefully read your fist post, I just skimmed through it.

So your final output is to go back to HDV? In that case forget what I said about ProRes. You need to edit in an HDV sequence. Any other workflow is pointless because all the footage will have to be processed and encoded to HDV regardless.

Sean