SSD as capture scratch disk?

Given that SSD disk aren't that big in size yet - does it work to have a SSD disk as capture scratch disk (DVCPRO50 and DVCPRO HD)?

DVCPro50 and HD are relatively low load codecs. I can edit multiple streams of 720p24 easily from a good quality sata drive.
It seems to me there is no real advantage for capture. It probably makes more sense to use one as the system drive.
x

Similar Messages

Hardware: SSD drives and scratch disks

Hi,
I am building a new system for Photoshop. Two quick questions:
1. I note in Adobe's system reqs it says Photoshop cannot be installed on flash-based storage devices. Does this include SSDs? Is there a genuine problem here (i.e. if my application drive is an SSD the PS won't work)?
2. I have not previously had a so-called "scratch" disk so I don't really know what it is or whether I need one, or more than one. What's the general advice here? - separate drive to the PS application drive? also separate to the Windows drive? How big? Will an SSD be a good choice for a scratch drive?
Thanks in advance,
Alastair

G'day,
In answer to your query SSDs work fine to install cs4 on bar the following I'm having.
I've built a new system using ssds.and is working fine bar one problem
Specs of the system is
I7 920 cpu, Asus P6t se mb, 12gb ram, 128gb ssd, 64gb ssd, 4gb raid 1+0 array onboard, nvidia geforcegtx260. I use the 128gb ssd as the os and programs drive. The raid is the data drive. All works brilliantly except when I set the 64gb ssd as the scratch disk the following happens
"Could not open a scratch file because the file is locked. Use the 'Properties' command in the Windows Explorer to unlock the file."
I hit OK and get this error -
"Could not initialize Photoshop because the file is locked. Use the 'Properties' command in the Windows Explorer to unlock the file."
Pressing ok then shuts the program and I need to reset cs4 prefernces and then it all works fine. OS is Win7 64 bit.
Now I have just got to try and fix this problem Anyone got suggestions?
Cheers
Onslow
Hmm, seems to have stopped doing this now after resetting the scratch to the ssd and then rebooting. All is now fine and wonderfully quick.

How do I work around incorrect capture scratch disk use estimates in FCP?

Hi Everyone,
I am trying to find a work around solution for FCP incorrectly estimating the space required on my capture scratch disk. I am using a Panasonic AJHD1400 to play back some DVCAM footage. I want to capture it 720x480 Anamorphic H264, via the firewire output on the deck. I am able to "free" capture the clip by hitting play on the deck and crash recording ("capture now") on the log and capture tool. From this process, I know the final captured file will be somewhere in the 3GB range, give or take. The clip is a little less than an hour long. I have 343 GB available on my scratch drive according to the information in the "Capture Settings" tab of the log and capture tool but according to the same info FCP thinks only 36.9 minutes of footage will fit on the disk. Consequently I can't log and capture the clip properly due to "insufficient disk space". What gives?
Any suggestions and responses will be appreciated.
Thanks in advance

It isn't an Easy Setup per se. I modified the "generic capture" template in the capture preset editor to use DV video from the AJHD1400 as the "Digitizer" and set the "Compressor" to be h.264 at 100% quality.
The whole point of the strange capture is for our sound editorial staff to edit to in pro tools. We don't have networked video storage for our audio department. If i capture in DV, the files are still like 20GB. using my "custom" settings I get a reasonably sized file that looks decent enough for the editors in a file that is small enough to fit on a data dvd if need be. I save rendering time as well.

I deleted my capture scratch disk

yea so i just threw away my capture scratch disk how do i get them back im freaking out i cant capture any vidoe

The capture scratch folder will be automatically created if it doesn't exist, in the location specified for capture scratch under Final Cut Express -> System Settings. If there is no location specified, you should specify one.
If that doesn't solve the problem, it's probably an entirely different problem, in which any seeing any error messages you're getting would be helpful.
FYI: I'm an FCP user, so I'm only guessing at the menu configuration. If you can't find it, look around for scratch disk settings.

What size for OS/apps SSD and scratch disk SSD ?

Hi !
I need a SSD for my OS with the full CS6 Cloud and few others apps (but no games, pictures, songs or other personnal stuff),
that's mean between 70 and 80Gb. So I think I'll need only a 128Gb for that.
I also need a scratch disk, so despite I prefer a fast and large disk like the Barracuda 3Tb, I read it will be better to take a SSD.
My workstation is a 6x core, with 64Gb RAM, and 6x HDD for projects, render and footage (4K R3D and 1080p PRORES).
My questions are :
1) OS/apps SSD :
Even if I only need 80Gb (or a few more like 90Gb max) of storage, do I need to take more than 128Gb ?
Is it possible that the OS fill my disk with lots of temporary files ?
And the same for Photoshop, Premiere, After Effects or others apps ?
I know those apps will use the scratch disk, but maybe others temporary files will be write on this OS/apps drive ?
2) scratch disk SSD :
Like I said, I prefer larger drives, but as I understood, SSD will be better for preview and temp files,
and actually I'm working with 4K R3D footages and 1080p PRORES.
So do you think 128Gb will be enough for a scratch disk, to use with CS6, Blackmagic Resolve, and others 3D apps, like Maya ?
Of course I can empty them regularly.............. but is it enough ? Or 256Gb, or higher will be better ?
Or just a fast WD Velociraptor 1Tb or even a cheaper Barracuda 3Tb hard drive will be good enough ?
Thanks guys.

Thanks for your fast reply.
But, I'm confused.... if the OS and the apps can fill my disk with lots of temp files, how a 128Gb can be enough ??
Maybe you mean that those apps will fill the SSD with "hidden" files, but not reach the limit of 128Gb ?
About Windows, I didn't knew I could make a scratch disk only for this temp files.
Do I have to put the Windows temp files in the scratch disk also ?
And you don't think a Velociraptor with 1Tb will be a good solution between the speed of a SSD and the size of a HDD ?
My drives (alone or in RAID 0) are directly connected from the motherboard P9X79 PRO, trought the X79 chipset, and the Marvell chipset.
But I read that the Marvell chipset has only 500Mb/s in total bandwitch divided between the 2 drives..... I'm not really sure....
but even if it's true, I don't think the OS/apps will take a lot of bandwitch (except when I'll start an apps),
and it will surelly let the full bandwitch for the scratch disk. Don't you think ?
4 drives are connected to the X79 chipset :
- 1x SATA 6Gb/s - Barracuda 3Tb (projects)
- 1x SATA 6Gb/s - Barracuda 3Tb (renders)
- 2x SATA 3Gb/s / RAID 0 - Barracuda 3Tb (footages)
- 2x SATA 3Gb/s / RAID 0 - Barracuda 3Tb (footages)
2 drives will be connected to the Marvell chipset :
- 1x SATA 6Gb/s - SSD (OS/apps)
- 1x SATA 6Gb/s - SSD or HDD (scratch disk for CS6 and other "video" apps)

Easily switch between scratch disk locations?

I have a project which I need to edit and it's going to take up a lot of room as it's shot throughout the summer and will contain hours of footage. I already have a hard drive devoted to all of my current editing projects (lets call that Drive 1) however this new project will be so big it needs another drive entirely. I have installed a hard drive (Drive 2) into my Mac Pro just for this new project.
I know by going into FCP > System Settings I can designate a new scratch disk on Drive 2 however I have a question.
I want to upload this project to Drive 2 at various points throughout the summer but at the same time I still need to upload and access my other final cut pro projects and content on Drive 1.
How can I easily switch between the capture scratch disk locations and make sure that content is being uploaded and rendered in the right location? I want to make sure I do this right before I add any new content to Drive 2.
Hope this makes sense.

Thanks for your reply.
So if I want to upload, edit etc content to Drive 1, I just unselect all of the Drive 2 preferences in FCP > System Settings and vice versa Then when I want to use them again I just re-select them?

How do I transfer my project from one scratch disk to another?

My current scratch disk is too slow because it uses WiFi and I'm wanting to transfer all my work from my current disk to another. How do I do this?

Copy all the media files associated with your project to the other drive (preferably a Firewire connected 7200rpm hard drive). Don't worry about the render files; they usually don't reconnect properly. After copying the files, delete the originals (but don't empty the trash yet) and then open the project and you will need to reconnect the media files by navigating to the new location. You'll also need to set the new location as the Capture/Scratch disk in FCE's preferences.
Once that's completed, re-render.
-DH

Need Urgent Help! RAM and Scratch Disk Problem

I was recently working on making a gigapixel panorama. I made the panorama in AutopanoGiga and rendered it as a .psb. I went to go fix some stuff on the file and the first thing I did was content aware fill. The panorama ended up being 4 gigapixels before cropping. So I wanted to try content aware fill on a small portion of the image. I am using a 12-core Mac Pro with 20GB 1333 MHz RAM. I have an SSD as my boot drive and four 2TB mechanical drives, none of which in a RAID.
When I first installed Photoshop on my Mac Pro, I went into the preferences to change the memory and scratch disk settings. The first thing I did was set Photoshop to use 12GB RAM. Then I went to the scratch disk and noticed that only my SSD was set up as a scratch disk. So I unchecked the activate box next to the SSD, activated all 4 other drives, and moved the SSD to the bottom of the list.
So I started content aware fill and saw that it would take some time. So I left and when I came back a little over an hour later, Photoshop gave me a message saying that the scratch disk was full and it couldn't complete the content aware fill. Why did this happen????? I deactivated my SSD and activated four separate 2TB drives!
I went on MacRumors Forums and asked some people, and the only advice I got was to reset my settings. I did that, redid my scratch disk settings, and it is still using my SSD as the scratch disk! Can someone please help??

CAF is processor and memory intensive... most of the flashy demos of this feature have been on much smaller images.
CAF has also been known to kick RAM errors when it simply farts and dies. Is CS5 fully patched?
Wear a helment when you try to hit your head on the ceiling.

Photoshop CS6 scratch disk on hard drive or SSD?

I've purchased a Windows 7 PC with 16 MB RAM, 2 terabytes and a 250 GB SSD. I'm going to load Photoshop on the SSD and the OS on the hard drive. Where should the scratch disk go?

It's a bit tough to answer, as you have not described how you'll be using your system overall. Are you going to be doing almost exclusively Photoshop work with it or are you looking for good all-around performance?
What brand and model SSD is it that you have, specifically? Generally speaking, if it's a modern model SSD with wear-leveling features in its internal controller, and with the other givens you mentioned, you will probably want to use the SSD for scratch, as SSD throughput is very high (hundreds of megabytes per second). With SSD throughput levels, when Photoshop starts using its scratch space heavily the performance hit is much less severe than with an HDD. There is also not nearly as much concern with an SSD about dedicating the drive to the task, as even if there are other activities on the drive the near-zero latency means that SSD supports multitasking much better.
However, if you feel you'll never exceed 250GB for OS and applications (i.e., you're going to keep a relatively simple system), using the SSD for operating system and apps alike might be a better approach. In that case there won't be enough space also for Photoshop scratch.
Just keep in mind, when planning your "this goes here, that goes there" distribution that Windows and its apps are really most comfortable with EVERYTHING running on drive C:. That's not to say it's a necessity, just that things tend to work more smoothly in that setup. Given that, you might actually consider getting a second SSD and making a RAID 0 array for drive C: with plenty of space available. That's the approach I took (in my case with four SSDs).
-Noel

HELP! "Insufficient Disk Space Remaining in the Capture Scratch"?!

Please Help Me ASAP!
im not like lierally dieing but i do need help urgently with Final Cut!
I am trying to capture my video from the camera and the message pops up that says "Insufficient Disk Space Remaining in the Capture Scratch".
So I have 2 questions:
1) What does it mean
2) What do I do to fix it?
im cluless here guys! any input asap would be so greatly appreciated! thanks
Ben

It means that you do not have sufficiant space on your scratch disk to capture your video.
What have you designated as your scratch disk? Which drive? Get Info on that drive to see how much space you have available. When you Capture, your Capture Window will give you info on how much space your drive has, and how much video (in time) you put on it
The solution is to get more space. Like clearing stuff off your drive or getting a new one
If you are capturing video to your system drive, in other words, this is your scratch disk, this is not reccomended. Designate another drive, either internal or firewire external as your scratch disk.
For more info on the scratch disk and how to target it, consult your FC manual and online help

Insufficient disk space remaining in the capture scratch

I’m using a PowerBook G4, 1.25GHz processor with 2 GB DDR SDRAM whit Final Cut Express version 3.5.1. I tried to capture footage from my camera and received a message, “insufficient disk space remaining in the capture scratch.” I moved all the files: Audio render files, Autosave vault, Capture scratch, etc to a new folder on my desk top, but still get the same message when I try to capture. To capture, I click the play button on the screen; hit the mark in button at the point I want to start and the mark out button at the end. Then I click the clip button followed by the ok button on the log clip dialogue box. The program then goes through what I assume to be the capturing process leading to the error message. How do I overcome this? Thank you.

Hi Geoffemn
The solution is to buy an external hard disk. Save the files to that. It does nothing to move the files from AV or scratch disk to a folder on the desk top. It still uses the same amount of space on the Power Book's HD. Of course you can look over current files on the HD and delete ones not needed. But that's a temporary fix. Large HD's have come way down in cost per GB. Go buy one. It should run at a speed of at least 7200 RPM and have firewire.
Carl

Additional SSD as Scratch Disk?

I have the NEW MacPro which is fast & virtually flawless. I am a photoshop power user (VERY large files), and am thinking that an additional (external) SSD drive dedicated to use as a Photoshop Scratch drive, should be extremely fast, and save wear & tear on the internal drive. SSD's are more than twice as fast as a top Thunderbolt drive. And as a Scratch Disk the low capacity to cost won't be a factor.
Opinions from other PShop power users? Anyone already doing this?
Thanks!

Yes, read up on the tips here:
http://www.macperformanceguide.com
OWC Thunderbay
http://macperformanceguide.com/Thunderbolt-cable-Optical30m.html
http://macperformanceguide.com/Reviews-OWC-Thunderbay4-SSD-RAID0.html
You are not going to 'wear and tear' as SSDs have been tested to hold up with 300TB and still going.
http://techreport.com/review/25889/the-ssd-endurance-experiment-500tb-update

I'm using PSCS6 on a 500GB SSD. Do I still reach a better performance by adding a scratch disk?

Hi,
OS X and PS are running on a 500GB SSD. Since I'm working with a MacBook Pro with 8GB RAM, I'm wondering if an external scratch disk would help to reach a better performance? The files, I'm working on, are usually between 300MB and 900MB.
I appreciate your suggestions.
Thanks,
Daniel

Photoshop PC version anyway seem to fill up the first scratch disk before allocating space from any other scratch disk. So if you has sufficient free space on your scratch SSD you don't need more scratch disk for Photoshop. A raid 0 of ssd will stripe data across ssd devices and my improve performance.

Insufficent disk space remaining in capture scratch

Hi all,
I am capturing for a small project off dvcam. I have run into a problem where I am unable to capture more material, I am getting an error message and the
prompt: insufficent disk space remaining in capture scratch .
what does this mean and how do I free up space? I have 100 gb left on my external drive, so I don't get it...
Grateful for advice.
LOF

Turn off any limiting of file size you may have checked on in the scratch disk settings, and also be sure it's that external drive that is selected as your scratch disk.
The external drive you have also must be formatted Mac OS Extended.
Jerry

If you have an SSD system drive, is a second dedicated scratch disk recommended?

Looking to buy a new MacBook Pro which has one PCIe-based 512gb SSD system drive. Unlike earlier MacBook Pro models, there is no internal DVD drive to replace w. a second disk drive.
I know that with HDD's a dedicated scratch disk that run's at least as fast as your application drive enhances performance of Photoshop. Is this also true with SSD's? Thanks.

Here's a suggestion (not aimed at anyone in particular, and I realize it may not be possible in all systems)...
If you're going to set up a system to access a certain amount of storage interactively - and what I mean is storage that's used all the time in the normal operation of the computer - consider making one big system partition out of a RAID array of SSDs.
With I/O operations averaging larger than the bare minimum (e.g., 4K bytes), RAID 0 effectively adds together the performance of the drives. This is because there's effectively no seek time with an SSD. It essentially randomly accesses stored data by address (it's quite complicated internally, but externally it works out that latency is almost negligible - literally measured as a few millionths of a second on a modern drive).
So...
Consider building your next system with multiple SSDs on task, making up an array of, say, a few terabytes. This yields the following:
Everything done by the system is done at the speed that's the sum of the drive speeds. With a modern system using SATA III, that's essentially about half a gigabyte per second per drive. Imagine throughput of more than a gigabyte a second - that's real. Forget about dedicating drives to tasks - EVERYTHING gets the benefit of the entire RAID array speed.
Since latency is virtually nonexistent, a great deal of multitasking can be done on the same volume without introducing any thrashing. Photoshop can be writing to scratch, the system swapping like crazy, and you just keep working without notice.
Everything's consolidated on one volume, which simplifies a lot of things (e.g., backup is simpler, applications install where they like on the C: volume).
All the free space pools together, so what's available as transient storage for whatever you're doing at the time is maximized. This tends to offset the extra cost of SSDs some.
SSDs themselves are fairly new tech, and it's not been widely known that they RAID together EXTREMELY well. They really do.
People sometimes worry that using multiple drives to make up a single volume increases the chances for failure, but consider that SSDs are solid state, and so by nature have a good bit higher reliability (higher MTBF; often 2 million hours), and they don't generate nearly as much heat (they consume just a few watts). Having SSDs in your system can actually increase the reliability of everything somewhat, because when everything is cooler it lasts longer. Plus they don't make any vibration.
This is not fantasy, I've done it.
My current Dell workstation has a nearly 2 TB C: volume made up of four 480 GB SSDs. My sustainable disk throughput is literally around 1.7 gigabytes per second (that's 15 times faster than a typical single hard drive). I do also have some HDDs in the system, but they normally spend all day spun down. They're for backup and very low access storage (e.g., downloads I've accumulated over time).
I wait for NOTHING on this system.
Oh, and it's been 100.0% reliable with this setup for 2-1/2 years now. ZERO glitches.
-Noel

SSD as capture scratch disk?

Similar Messages

Maybe you are looking for