Nikolas Bäurle
Forum Replies Created
-
Peter, thanks for your reply.
I had the camera connected to the power source, and the usb connected properly. I was still able to record when it happened, it was simply green, and switching between play and camera mode solved the issue at first until hitting the power button.
It works perfectly fine now, so it was probably just a temporary glitch. All I did was drain the battery and turn it on again.
I tried updating again but the Utility software tells me its up to date. I’ll de and reinstall the Utility Software and see what happens.
“Always look on the bright side of life” – Monty Python
-
[Don Smith] “Simply not true.
Tell that myth to Final Cut Pro X now playing my 20,000 dpi image as easily as the same image next to it but with a dpi of 20.”
I stand corrected. I tried it out myself and just realised that all these years I always had resample clicked (as is by default in Photoshop). In this case it does resize when changing dpi. Something I never really thought about, probably because I rarely have to deal with 300dpi images.
But the myth does seem very prevalent. At the beginning of my career that was what I was told to do whenever FCP Legacy had problems with images, and it worked, of course, since resample was always clicked…:-)
Thanks for the clarification Don.
“Always look on the bright side of life” – Monty Python
-
Nobody said 300dpi had anything to do with size. Perhaps I wasn’t clear in seperating size and dpi. 300dpi images will bring any NLE to a halt no matter what size they are.In FCP 7 even one 300dpi image in the timeline can become very annoying when rendering or exporting. X can deal with 300dpi but the more you put in the sluggier it gets. Images need to be 72 dpi to edit smoothly.
“Always look on the bright side of life” – Monty Python
-
13,5 GB is nothing, really. Large JPEGS are usually 5 MB. When editing video you usually deal with a lot bigger files sizes. I have libraries that range between 50 GB and 1 TB, a minute of DSLR Footage is about 400 MB and today I just got my Blackmagic 4K and 1 minute of Ultra HD is 5 GB.
If your files have a very high dpi then that’s very likely causing your problem. You can edit 300 dpi images on the latest iMacs ver wellbut to play them smoothly you need to render, once in a while there’s a crash. In my experience on older macs and on FCP7 its pretty much impossible.
If you have 4500 of them and as many cuts then you are really straining your system.
“Always look on the bright side of life” – Monty Python
-
[Michael Harrington] “I wonder if you select to optimize media when importing still images if FCPX would resize the still image.”
No, it leaves it as is. Jpeg are already considered optimized, and it doesn’t make a proxy from a JPEG.
“Always look on the bright side of life” – Monty Python
-
There is no maximum file size I know of.
“Always look on the bright side of life” – Monty Python
-
Your jpegs might be too large. Over 5000 pixels can cause X too slow down, and if they are 300dpi then you need to bring them down to 72dpi.
“Always look on the bright side of life” – Monty Python
-
This is the FCP Legacy Forum. You should post this on the FCPX Techniques Forum.
It doesn’t look like Toonit is compatible yet. When I intalled Magic Bullet Looks I got the option to check FCPX. I just installed Toonit and It didn’t give me the option for X, only for FCP Legacy, and Motion 5 doesn’t work either. In Adobe CC it works.
“Always look on the bright side of life” – Monty Python
-
To me Fast turnaraound ist the stuff that needs to get done really quickly, and sometimes footage needs to be cut in at the last moment, even half an hour before going online. This would be te case for Start-News Magazines. A four minute piece needs to be done in 4 – 5 hours, then another hour for sound.
When I do commercials I get at least 8 hours to cut a one minute clip. And for higher end TV a 15 min piece takes about 5 days, sometime more so times less depending on the complexity.
Of course everything needs to get done quickly, but there still are differences between certain types of projects and clients.
Personally I prefer using FCPX for all the types of formats I’ve done sofar, wether its feature documentary or experiemental, musicvideos or short commercials, whatever. It has made everything I do work faster and smoother.
“Always look on the bright side of life” – Monty Python
-
[Aindreas Gallagher] “you’re not wrong – I personally think the timeline itself is utterly ridiculous, but it has many practitioners and everyone is polite about it at this point.”
Many of us FCPX-FCP7 editors, and in my case also Avid, prefer the magnetic timeline because it actually is faster than a classical one, especially when doing fast turnaround projects. And the 60 min experimental I edited almost two years a go was so much nicer to deal with than similar previous projects on FCP 6 and 7. And I still make more money on Avid and FCP7…
“Always look on the bright side of life” – Monty Python