Andreas Kiel
Forum Replies Created
-
I have to be with my MBP on locations were no power supply is available several times a year. And I’ve to work longer then 2 hours.
So I bought some little moto bike gel batteries and a power converter. This allows to run the system (MBP + HD + FW camera – running 6 streams) for more than 8 hours – compared to less then 1 hour
It’s some additional weight, but it’s worth it for me.Spherico
https://www.spherico.com/filmtools -
-
You may try Jubler. From my experience you will loose font style settings or get control characters inside the subtitles. But it may fit your needs.
Michael’s web tool works fine with most of the standard text generators of FCP, even with my non standard ones.Andreas
Spherico
https://www.spherico.com/filmtools -
You also should be aware that the iPhone shoots “about” 29.97 fps.
Andreas
Spherico
https://www.spherico.com/filmtools -
Joe,
You should realize that PPro has integrated the old FCP XMEML interpretation in the app (more or less) and since it works (more or less) like FCP it’s somehow “easy”.
Phillip’s 7toX needs to convert from one kind of system to a totally different kind of system using the FCPXML “language”. 7ToX has a global approach to do the very best to translate (and it does well) but finally not every “sentence” can be translated from one language to the other.
So give it a try by eliminating tracks or filters and rebuild the things in FCPX.Andreas
Spherico
https://www.spherico.com/filmtools -
Yes any student can have his own sparse disk anywhere in the network.
But working with sparse disks need some understanding.
First a sparse disk image is a kind of “virtual volume” located on a another volume as a file. If you double click that file it will show up in the Finder as a new volume which can be used like any other volume directly attached to the local machine. Like any other volume it will have it’s limitation in size.
For example you got a 2 TB internal drive and you want to create some sparse disk images on it. What you can do is to create 3 500GB sparse disk images leaving 500G free for the OS, apps etc. Once the 3 sparse disk file are created they only cover a small amount of disk space – cause they are empty when you created them. Now working with them will let them grow (regarding used space). If you add more files to the internal (or external) drive will leave less space for the sparse disk images to grow to their limit maybe. Therefore the 500GB in some circumstances can’t grow up to 500GB cause there is not enough space on the “master volume”.
The other thing is that once the sparse volume grow up in size it will keep this size. You can delete files on the sparse volume but the current space used for this will keep the same coverage. You can shrink them using some terminal commands (or my app).
The other thing is that the 500GB (in my example) is not enough to hold a certain project and FCPX will give you an error. This can be fixed – as long there’s enough available space on the “master volume” – by some terminal commands as well (or with my app with a click).So go and try some some of the scenarios before you start and make sure the students understand what they do and can do.
Andreas
Spherico
https://www.spherico.com/filmtools -
Having a problem here.
FCPX doesn’t allow me to import movies over BlueTooth from my old cell phone even though it shows up as camera in the import window 🙂
Andreas
Spherico
https://www.spherico.com/filmtools -
Rich,
First of all it’s not possible and recommended that two people work at the same time on the same project.
You can take the route to exchange portable drives – this is the most simple approach.
Another approach is to create sparse disk images on either of the machines or on both.
As long the machines are connected the sparse disk can be mounted on any of the two machines. So create a sparse disk image and put event and projects there. You will have access from both machines (or any machine in the network).Using an NAS will require the same procedure since FCPX won’t see the required structure on any network attached volume. But if you got enough money you can use a SAN.
I created a little app which helps to create and handle sparse disk images with ease. It’s free.
https://www.spherico.com/filmtools/createDiskImage/index.htmlYou also can create them using Disk Utility and Terminal in case you want to modify them.
Andreas
Spherico
https://www.spherico.com/filmtools -
It’s actually not really true that FCPX does more during import than FCP in many cases it’s just the opposite.
Most people just import Alexa right away into any of both apps. With FCP you were able to use the Alexa XML, which slowed down the process by maybe 1 or 2 seconds but you got quite a lot of metadata ready to use.
FCP used to write the metadata into the QT file structure during import. That’s one the reason you see a new modification date on imported files even though you haven’t touched them.
An example: We used to sync Alexa and other files externally with BWAV files. Using XML it “forced” FCP to make the file match the given metadata. This for example allowed just to open a QT file in any project with SCENE/TAKE/NOTE automatically seen.Working with TC is kind of nightmare as well with FCPX.It can’t handle multiple TC tracks and doesn’t allow to use “virtual” TC tracks. With FCP that saved/saves us hours compared to FCPX.
In the beginning we did some XML import tests for subtitles average time with FCPX from import start to ready to work had been 6 Minutes (different machines same file) with FCP it had been around 10 seconds. Final rendering for this kind of job is still a kind of disaster. FCPX is about 150 times slower than FCP
Spherico
https://www.spherico.com/filmtools -
Hmm,
I think events/projects must be on local (direct attached) volumes either ejectable or not. A network volume won’t work regardless of the structure – except SAN. For NAS or other machines connected to your computer you need to work with sparse disk images.
The scenario I described obviously only works convenient with sparse disk images. 10.7 up also would allow to “auto-mount” them at boot time.
You also have to make sure that the root structure doesn’t contain any folder name like “VIDEO” or “DCIM” or anything that makes FCPX to think “Hey, that could be a cam card”.As said with my examples, if I need to boot from disk 1 the events/projects on this disk need to be in “~/Movies/” but they will be in “/Final Cut Events” and “/Final Cut Projects” because they where created when using another boot drive. So I have to move them to “~/Movies”. When have to boot from another drive I have to move them back to the root level – as long I want to make them visible for FCPX.
That’s how it works and there is no other way to make it work.@ Jeremy: Okay I agree, you where half right 😉
Andreas
Spherico
https://www.spherico.com/filmtools