Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Setting System Preferences To Internal SSD

  • Setting System Preferences To Internal SSD

    Posted by Shawn Larkin on March 24, 2011 at 7:46 pm

    For years, I’ve managed my media with FCP (and all the other FCS Apps) pointing to a fast external drive / RAID.

    Now, I’m considering keeping everything pointed to my MBP’s new internal SSD. I just got a 240 GB Mercury Extreme SSD from Other World.

    My case is unique in that almost all the media I edit will stay on an external network share so only my render files and project backups will be directed to my internal SSD.

    I get that traditionally you don’t want to burden your OS drive with reading / writing media files, but the blazing speed of this SSD and the fact that most of the media won’t actually exist on this boot drive, makes me think it should be fine.

    Any thoughts or sage advice on dong this is much appreciated.

    Urs Lotze replied 14 years, 7 months ago 5 Members · 7 Replies
  • 7 Replies
  • Bret Williams

    March 24, 2011 at 8:17 pm

    That’s not a very big drive in general. Why clutter it up with media? Why not render to the network if you need the network drives to play the project anyway? My .02

  • Joseph Owens

    March 24, 2011 at 8:51 pm

    I agree, you’re going to eat up 240GB in a big hurry — even faster if its a blazing fast SSD.

    jPo

    You mean “Old Ben”? Ben Kenobi?

  • Shawn Larkin

    March 24, 2011 at 9:00 pm

    Thanks for the input.

    Actually, I will end up rendering to an external HD. I send all jobs to Compressor which defaults to rendering to an external HD. So really the only files saved to my boot drive will be the cached render files and project backup files each FCS app generates. And I will clean these up regularly.

    My question was really more of a…

    Does anyone see any foreseeable problems with allowing your boot drive to be your media drive (by keeping all your FCS apps pointed to it instead of an external drive) IF it’s a super fast SSD and the majority of the media you edit is located on an external network drive?

    My guess is there is not real concern. But maybe someone knows something I don’t so I thought I would ask.

    Thanks again in advance.

  • Scott Sheriff

    March 24, 2011 at 9:09 pm

    There was a post not that long ago from someone that started using an SSD and was having problems.
    I don’t remember the particulars, but you might want to do a search.

    Scott Sheriff
    Director
    https://www.sstdigitalmedia.com

    I have a system, it has stuff in it, and stuff hooked to it. I have a camera, it can record stuff. I read the manuals, and know how to use this stuff and lots of other stuff too.
    You should be suitably impressed…

  • Shawn Larkin

    March 24, 2011 at 10:07 pm

    Thanks Scott.

    I have only found that certain SSDs had problems running ProApps in the past. Anything new SSD formatted HFS+ should be fine under OS X 10.6.7.

    I think what I am getting at is more of an paradigm shift idea: you might not need to set your media scratch disk to a non-boot drive. I mean, in the past, there was good reason for this. And if you capture files — small or big — you still need more space than the average SSD can provide.

    However, if blazing fast SSDs were the norm and they had lots of storage space on them, would we really want to have an external drive for scratch disks, cache files, and render locations? Probably. But in some cases, probably not. I think mine is one of those cases. And, well, I guess I’ll have to test the performance once I install the drive.

    Thanks for the feedback all.

  • Bret Williams

    March 26, 2011 at 3:53 am

    You should quit calling it your media drive. If all your media is on network drives, those are your media drives. Apparently you\’re not planning on rendering anyway since you\’ve referred to compressor as the application that is doing your rendering. ??? And FCP doesn\’t use temporAry cache renders. Render files are your tender files. If all your doing is rendering the occasional effect to the SSD, then this would not really be your scratch/media drive.

    Don\’t forget, that drive is also being used to read os, program, FCP file, and used as ram if necessary, all while you\’re trying to read from it. It\’s not the speed of the drive that has been the problem. It\’s been all the access demand on it.

  • Urs Lotze

    October 3, 2011 at 8:49 pm

    Hi there,

    Thanks for all the info.

    I’ve placed a SSD Kingston V+100 512GO in my MBP 17 Alu (Core 2 Duo 2,6 GHz, ram 4GO) with fantastic results for the system overall (OSX 10.5.8). By overall I mean for the sys and all applications.

    For all apps…? Not realy… Not for FCP at all!
    FinalCut runs way slower with the SSD!
    The original boot disk was a Hitachi 200GO/7200tm and the SSD is “one of the best” on the market with Intel inside and one of the best controler Hitachi T6UG1XBG. In addition this SSD has a “TRIM like” function inside de controler. Therefore it does’nt need TRIM and should not decrease in speed with time…

    Never the less, FCP runs far slower than before. With the datas on external FW800/7200tm drives, or even with the datas placed inside de boot disc. (no eSATA connection available on my older MBP 17).

    If nobody has any clue to what I realy could do to get better perfs with FCS using SSD for the boot and FW800/7200tm HDs for external datas, I’m gonna go back to my original 7200tm boot disk…

    This SSD priced a hefty $900 … 🙁
    Thanks in advance for some help.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy