-
FCPX Library File Size
Is there a maximum FCPX Library File Size? My system, Maverick and FCPX 10.1 runs sluggish with the project described below.
Ive just started editing in FCPX and working on my first cut, imported 4500 jpegs and did not copy or optimize for import, imported 10sec duration, edited all into time line, changed each clip duration to 1 frame, total duration about :55. When I had a few projects open the system runs very slow, spinning beach ball, huge lag time on executing a command.
Exported a ProRes file of the speed up project, imported it new project to play with speed changes in different sections. If I have just this project open the system runs smooth.
The entire Library has just three projects and pointers for the 4500 images, the file size is 13.5GB, is this considered huge considering the size of the project.
Michael Harrington
Mac Pro, Dual Quad-Core Intel Xeon 2.66 GHz, 12 GB, FCP7, Mavrick, ATI Radeon HD 4870, 30-inch Cine Display, 4 – 1TB internal, G Speed 6TB Raid 5, 1.25TB Esata, Numerous FW 800 external drives, Matrox MX02Max, FSI 17″ Broadcast Monitor, Black Magic Mini Sync Generator, Mackie 1402 & Event 20/20 monitors. -
15 Replies
-
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
-
Yes, of course, that makes since.
Is there a Maximum file size?
Michael Harrington
Mac Pro, Dual Quad-Core Intel Xeon 2.66 GHz, 12 GB, FCP7, Mavrick, ATI Radeon HD 4870, 30-inch Cine Display, 4 – 1TB internal, G Speed 6TB Raid 5, 1.25TB Esata, Numerous FW 800 external drives, Matrox MX02Max, FSI 17″ Broadcast Monitor, Black Magic Mini Sync Generator, Mackie 1402 & Event 20/20 monitors. -
I wonder if you select to optimize media when importing still images if FCPX would resize the still image.
Michael Harrington
Mac Pro, Dual Quad-Core Intel Xeon 2.66 GHz, 12 GB, FCP7, Mavrick, ATI Radeon HD 4870, 30-inch Cine Display, 4 – 1TB internal, G Speed 6TB Raid 5, 1.25TB Esata, Numerous FW 800 external drives, Matrox MX02Max, FSI 17″ Broadcast Monitor, Black Magic Mini Sync Generator, Mackie 1402 & Event 20/20 monitors. -
There is no maximum file size I know of.
“Always look on the bright side of life” – Monty Python
-
Hmmm, what would be considered a LARGE file?
Michael Harrington
Mac Pro, Dual Quad-Core Intel Xeon 2.66 GHz, 12 GB, FCP7, Mavrick, ATI Radeon HD 4870, 30-inch Cine Display, 4 – 1TB internal, G Speed 6TB Raid 5, 1.25TB Esata, Numerous FW 800 external drives, Matrox MX02Max, FSI 17″ Broadcast Monitor, Black Magic Mini Sync Generator, Mackie 1402 & Event 20/20 monitors. -
[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
-
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
-
I have libraries going over 200gigs and haven’t noticed any performance issues from that.
————-
OutOfFocus.TV – Original series, music videos, mini-docs. -
Hate to point this out but DPI has no effect on the file size of an image.
You can test this by saving the same picture with different DPI settings and the file size will remain the same. It may happen that the NLE will display the picture differently depending on the DPI setting but that has nothing to do with file size.
DPI is a printer instruction on how far apart to print each pixel. Some people think that the higher the DPI the higher the picture detail. Nope. Detail is how many pixels make up a given area. Want more detail? Look at the dimensions of the image. A picture of, say, 10 pixels by 10 pixels will be 10×10 regardless of the DPI setting. With a high DPI setting those 100 pixels will just be printed closer together on paper.
The detail of a picture depends on how many pixels make up the picture and that is determined by its length in pixels times its height in pixels. You don’t create new pixels or take away pixels by changing the DPI setting. DPI instruction to a printer tells it how much to spread out the printing of the pixels.
NewsVideo.com
-
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
Reply to this Discussion! Login or Sign Up