Something weird with Scratch disk allocation

I've recently switched to a new pc with Vista-64. After installing my CS3 I tried to give it a test to see how it performs. Medium sized files run very fast on difficult filters such as Lens blur. But when I open a large file like 300mb and try to run a Lens Blur filter on it, things get very slow for this PC. I think it takes 3-4min to complete the task.
What also bothers me is CS3 is writing/using on a external HD that's not chosen to be used as a scratch disk. I noticed this as I see the blue lights get active on the WD external HD. Then I checked what's happaning in the disk going to my computer. When I look into the HD I see bunch TMP files written during this filter task. Same type of files (different sizes)are also seen in the dedicated scratch disk. Is it normal that CS3 will access other HD's eventhough they are not chosen as Scratch disks or is it there anything wrong with my CS3 or OS? Also I believe that I should get a better performance with my setup, anything you might suggest?
My computer: Gigabyte EX38T-DQ6 motherboard, Intel Core2 Extreme x9650, Vista 64-bit, 4GB DDR3 RAM, OS, other programs and CS3 located on 4 WD Raptor HD's configured as RAID 0+1, separate 70GB Raptor HD for scratch disk, all photo files are stored on 2 750GB Lacie HD's as RAID 1 and I have one WD external 2 TB HD for back up connected with Firewire800. This is the one that's being accessed by CS3.

Could it be something in your backup settings that is triggering the disk activity on that drive? With so many other drives to choose from, it seems strange that Photoshop should pick that one.

Similar Messages

Weird RAM/Scratch Disk issue

Having a weird memory problem with Photoshop CS4 on my G5 Quad.
Let me see if I can explain this properly....
When I open up a file in Photoshop, I notice that the available space on my hard drive reduces (info at the bottom of any Finder window). Essentially, it's using the scratch disk.
I would expect this with a very large file that exeeds the amount of ram in the machine. But it does it even with files of 5-10 Mb. It appears to me (just a guess) that Photoshop isn't using RAM when opening or manipulating a file. Though I have more than enough to open it.
Even when I close the file, or "purge all" from PS's edit menu, my available disk space does not come back. Only when I quit out of Photoshop completely, will it come back.
Make sense?
No other application seems to be having this issue. Any ideas on what might be causing this?
I've run Apples Disk Utility, and everything came out fine. Ran TechTool Deluxe, and no problems there either. Hoping maybe I'm just missing some piece of the puzzle first, before I uninstall/reinstall Photoshop.
System specs:
G5 Quad (2.5 GHz)
4 GB RAM
OSX 10.5.8
Photoshop CS4 (11.0.1)
Memory usage set to allow up to 70% (but doesn't seem to matter what I set it to)

This is normal.
Photoshop needs to allocate scratch space for data, in case it needs to write that data to disk later -- otherwise you would randomly fail with "out of scratch space" in the MIDDLE of an operation.
Photoshop is using RAM, but needs to allocate the scratch space, and make sure the allocation succeeded.
And yes, RAM and scratch space get reused, so rarely decrease.
Other applications that deal with datasets larger than RAM will have the same issues.
And technically your OS swapfiles do the same things.

Any advice for teacher struggling with scratch disk problems?

Hi,
Just wondering if anyone out there has advice for me. I am a Media Teacher with very little technical expertise. We use Premiere Elements 4.0 in my school. This is accessible to students on the school network but is located on a separate drive. I am experienceing a lot of problems at the moment which I suspect may be to do with having multiple users. The students work in groups. Some of them do not seem to be able to access their current coursework - a scratch disk error message comes up and they are asked if they want to locate the scratch disks into their own area of the school network. As personal space is very limited, they always say no, and then cannot access the projects. Other students do not have this problem. The scratch disks are located by default to the same drive as the main work.
A further problem is that in one project, the clips in the second half of the project seem to be 'offline'. I have seen this before and have been able to fix it by locating the clip in the project menu and using 'locate media' to reconnect it. However, this time round, the clip can be seen and runs perfectly in the project menu. It also looks as normal on the timeline. It is only in the viewing window that it comes up as offline. The locate media option isn't available. If I save as an avi, the offline message appears, so the project burns as it appears in the viewing window. If I drag the clips down from the project area and reconstruct, everything plays normally until I close the project down and open it again, when the clips are back offline. I can tell something strange is going on because the project is loading very quickly - it was taking a couple of minutes previously.
Any advice at all would be welcome, as we are near the end of the coursework and the projects we can't access represent a term's work for the students!

You may need to contact Adobe Tech Support for your specific needs.
Is Premiere Elements installed on your network or on the C drives of each computer? The program must be installed on the C drive in order to work properly. You can't run the program from a network installation, and that could explain why you're having the problems you're having.
If you've got Premiere Elements installed on your C drive, you should be able to access your video files if they're stored on the network. But this depends on how your network is set up. It may not be possible for all of your students to access material out on your network drive and remain connected to it the same way every time you open your project.
In other words, you're using the program in ways it's not designed to be used. This is why you may need to contact Tech Suport and see if they can recommend a solution, short of each student having their own complete installation on each computer.

Disk error with scratch disk

All my MACINTOSH versions of Photoshop - S5, Elements 10, Elements 11 - display the opening start screen, but ABORT THE LAUNCH of the EDITOR with the error message:
"Could not open scratch file because of disk error."
"Could not initialize Photoshop Elements because the preferences file was invalid (it has been deleted)"
I have cleaned up my external disks so that they all have at least 100GB of free space
How can I correct this so that I can recover the Preferences, re-establish the Scratch Disk, and launch the Photoshop Editor?
<E-mail address removed by Moderator>

Please change the disk permission . Right click on the disk and choose "Get Info". Change the permissions for everyone to "Read and Write". You can also refer to this related post
http://forums.adobe.com/message/4331448#4331448

Problem with scratch disk in CS4

Hi
I used Premiere Pro CS4 on my MacBook to import from my Panasonic DC-TM700 HD camera and set the scratch disks to an external disk.
But now there´s nothing on the external disk, and I got 8GB less space on my internal hard drive.
So it seems like all my footage was imported to the internal hard drive, but the promblem is: I can´t find it!
I´ve searched my mac for capture, scratch, log and premiere, but I still can´t find the folder. It´s not in the Premiere-folder in documents eather.
Where can this folder be?
Thanks
Lise

I used Premiere Pro CS4 on my MacBook to import from my Panasonic DC-TM700 HD camera and set the scratch disks to an external disk.
But now there´s nothing on the external disk, and I got 8GB less space on my internal hard drive.
sounds like you imported from your panasonic camera. Also sounds like you have no clue where they were being imported TO. There is one clue....which is having less space on your internal hard drive now ( 8gb). Leads us to believe that maybe you imported the video to your internal HD.
If you have any idea at all what sort of file extension your imported video would have ( eg. AVI, MOV, MPEG, etc ) you could do a "search" on that hard drive for any files that have the extension you saved the video as.
Once you find them on your hard drive you can do what you want with them.

The problem with scratch disk space.

I have been using Priemere products for over ten years now and have run into a problem recently using Premiere Pro that surprised me. I was editting a project last week that required me to reuse a lengthy clip several times. I would set a different in/out point with each use because the clip was not broken up into separate pieces when it was captured. This is the first time that I have had to do this with such a long clip so I never encountered this problem before. After saving a considerable amount of different versions of the same clip, I received a notice that the hard drive that I was saving the project in was full.
When I checked the project file I found that with each use of the long clip, Premiere would save the entire clip under the preview files sub-folder. This meant that in no time at all I had compiled a total of 35 gig of video files from a single 1.2 gig original. I determined after the fact that I could have redefined a different in/out point on the same original clip without having to reinsert it each time. This would have resulted in a much smaller preview file size.
I have two questions. First, is there some way for me to easily back out all of the duplicate clips from the project window of Premiere so that the preview sub-folder size decreases? Second, will Premiere always duplicate every clip that I select for the timeline in the scratch disk file? This seems like a tremendous waste of space even though it is suppose to improve realtime preview. I always thought that the project file just recorded the locations of the clips and when and where to use them. Maybe I have been wrong all of these years or maybe Adobe Premiere has become more demanding over the years. Either way, some clarification on these points would be greatly appreciated.

Consider a single clip that may contain 45 minutes of video. I wanted to use numerous segments from within that large clip in my video. So, I imported the same clip into the project window of Premiere for each segment that I wan't to use. Each time I imported the file I would set a different in/out point on it and drag that to my Timeline. After about the 10th import, Windows informed me that I had exceeded the storage capacity of the hard drive that my scratch disk was on. I have done numerous videos with both static and video images in the past and have never run into this problem. That was the nature of my inquiry.

Problem with Scratch Disk - CS4 - Mac

Under project settings, scratch disks, I have set everything to a folder on my external drive, and it shows me for each item that there is 1TB of space available. I am attempting to capture from my Panasonic camera. As soon as I start capturing, it shows me I only have 27.2MB of space available! This doesn't make any sense at all, and is not even enough space to capture this half-hour of footage; the capture keeps dropping frames and will only capture about 10 min of film.
I don't understand this program. Every time I capture video it seems to take up an unbelievably HUGE amount of space on my internal hard-drive. I have deleted everything I can find to delete on my internal drive, and deleted the trash as well, and it does show that I have 15 gigs available internally, but Premiere just can't seem to find enough space.
WHY, when I'm giving it 1 terabyte of space to use, does it tell me I only have 27MB of space available?? This should have taken me only half an hour to capture (I did one earlier that was just fine, but that seems to have taken the last bit of space available) and instead I have wasted the past 4 hours trying to figure this out.
Please help!!!

OMG - even tried rebooting my computer to clear RAM etc... and STILL it is showing me "Remaining disk space: 27.22 MB." I just cannot figure this out! And why did it capture just fine prior to trying this one (can't remember how much disk space it was showing me then, but I recall it was a lot more than 2 megabytes)? I didn't change any settings...
The program will only capture 9min ~25sec, then it says something like "unexpected recorder error" and stops the capture.
I really need to be able to capture this stuff - HELP, please???!!!

Something weird with the keyboard

Hello everyone, i have this strange problem with my wireless keyboard. Everytime i type down a letter, it appears down as many times as i hold the button. Every letter, except X. It is the only letter that i can only type one time, even if i hold it down for several seconds. I don't think there is something wrong with the keyboard or the specific number, because when I hit it again and again the letter appears. Only when i hold it down it only appears once. I know this is not something to bother about, since i can type the letter, but i am curious to find out why this happens. If anyone could tell me, please, do not hesitate

Quote from: sjay on 18-April-11, 04:52:57
This is due to the manufacturing of the keyboard itself. The way its setup is that the keys that are giving problems are obviously located on a different chip and are being recognized as a different device, therefor fail to start or function at all in lowlevel driver enviroment.
There are threads all over the internet about how these expensive keyboards are causing problems with Win7 because of how they are made. Just don't buy too expensive of a keyboard that has a bunch of extra things because those "extra things" are handled differently then a typical keyboard, which is counted as one device. My Saitek red Eclipse works perfectly fine, though it doesn't have extra programmable macro buttons or anything (and thats why it works). It does have volume + -, mute, and backlight adjustment buttons though.
Surely that cannot be the case. This keyboard works fine with every other motherboard including the lower-end P67S-C45 that I have sitting next to me. Also, lets not confuse the issue, this problem does not affect Windows.

I think I did something weird with foundation/server patching

We've built many SP sites over the last 3 years. We're now moving in to 2013. most of our sites are 2010.
For the old sites, both myself and my colleagues were just learning on the fly how to deploy and patch. Over the years we've gained a better understanding of both.
Something I've done though in the past, i don't know how it affects the deployments and I was wondering if someone could shed some light on it.
We used SharePoint server with internet, mostly. When patching, we saw that there were two sets of patches, foundation and server.
We didn't have a full understanding of both but now do. They are stand alone products. However, we though they were component levels of the same installation, and for years we've been applying both the foundation patches, and the server patches
right behind that. It's worked fine. We've never received any errors about patching.
Now that I know better, i'm only deploying server patches to the new 2013 deployments.
I was asked to add a 3rd server to one of our old farms. I ran in to a patching mismatch warning when trying to join the farm. This made me think about how we patched foundation and server even though we're running server. One of the warnings
was that those foundation patches were missing.
So I restarted and used the exact same patches and it worked fine. Still, i'm wondering what the overall impact of our old patching methods has on the product?
My hope is that everything in SP foundation is part of SP server, so the patches I made, assuming the same level of patching, only duplicated patching effort, and there are no technical drawbacks to having patched foundation then server on the same environment.
Anyone know?

Hi,
There are some different patches for SharePoint, to better understanding the different patches, I think you can have a look at the following articles which contains the different patches in SharePoint.
Hey! Should I install this SharePoint patch?
http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=433
For example, the “cumulative” part means if you install the August 2012 CU you don’t need install the June 2012 CU first.
CUs are also cumulative in the sense that the SharePoint Server patch includes the patches for SharePoint Foundation.
The Project Server CU includes the SharePoint Server and SharePoint Foundation patches as well. You only need to install the CU for the product you have.
This is a welcome change from SharePoint 2007 where we had to stack the patches.
Also, CUs contains the patches for all the supported languages which is why they’re so large.
Thanks,
Jason
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Jason Guo
TechNet Community Support

Something weird with nvidia

Hi, when I'm watching glxgears for example on Workspace3 I get:
1805 frames in 5.0 seconds = 361.000 FPS
1957 frames in 5.0 seconds = 391.400 FPS
2006 frames in 5.0 seconds = 401.200 FPS
1970 frames in 5.0 seconds = 394.000 FPS
1995 frames in 5.0 seconds = 399.000 FPS
But when I switch to another workspace for awhile and return to workspace3 I watch this:
10452 frames in 5.0 seconds = 2090.400 FPS
10092 frames in 5.0 seconds = 2018.400 FPS
10160 frames in 5.0 seconds = 2032.000 FPS
10158 frames in 5.0 seconds = 2031.600 FPS
9755 frames in 5.0 seconds = 1951.000 FPS
9920 frames in 5.0 seconds = 1984.000 FPS
EDITED: at this point, when I'm already back on worspace3 again I get 400FPS
:s:s is there some kind of explanation to this?
I've got a nvidia GeForce2 MX 32MB with driver 7176.

Yeah, it's easy to render something that isn't there.
It doesn't really have to render anything when you aren't viewing a workspace, so the FPS will get really high (seeing as it's not rendering anything) but will drop back when it's required to start rendering things.

Something weird with comments

http://web.mac.com/varkgirl/iWeb/The%20Baroli%27s/Magnolia/Magnolia.html
On the main blog page, the comments don't show up (at least in my browser, everything says "no comments"), but on the archive page and on indivitual pages, they do.
Anyone else experiencing this?

Have you changed anything since? The comment count is correct now on your main blog page.
[ Visit here for iWeb Tips, Tricks and Hacks ]

Macbook Pro with Dual hard drives. Scratch Disk, Memory 64bit, Raid, Set Up Questions.

Hello, this is my first post.
I just upgraded from the original 2006 17" Macbook Pro to a refurbished 13" Macbook Pro 2.53GHZ 4GB Ram (2009 model).
I bought the MCE Tech Optibay and installed it (if you dont know anything about it, ask me, its amazing.) So now I have 2x 500GB 7200RPM Seagate hard drives installed.
I am running Snow Leopard, CS3, Lightroom 1.4.
I have the main hard drive set up with Snow Leopard and all the Applications. I keep all my files on external firewire 800 drives, except files I am currently working on.
The second hard drive is set up as a scratch disk for Photoshop CS3 and that is it.
I am looking to upgrade to CS5 and Lightroom 3 here within this month or so. Or if I get anxious, tomorrow, haha.
I want to know the best setup I can do with my current set up with CS3 and for my future setup with CS5.
Any info will appreciated.
-Would some kind of raid set up with my internal drives be better? How does raid work with scratch disks?
-If I upgrade to 8GB memory in my macbook pro, would I even see a difference in performance if I didn't have a scratch disk? Since CS5 and Snow Leopard can use more memory in 64bit.
I think thats all I have on my brain right now. I may have more questions, or I can guarantee I will have more later.
Thanks alot.

First the scratch. Like you said, most everyone has a different take on scratch discs but I'd guess you're wasting one heck of a lot of hard drive space using all 500 GB for Scratch, did I read that right? If I did read it correctly YES, partition it and get some use out of it!!
I've got a unibody MBP 2.93GHz, OS 10.5.8, CS3 & PS 5 (running in 32bit mode), and 8 gigs of ram. I've partitioned the one 300 GB drive so 50GB is scratch, the other partition is for OS, & Apps, and documents (images).
I use LR 2 first than export to PS 5 to finish up. My photos get to be 300MB to 500MB in size and both versions of PS work on this setup just fine. Using PS 5 in 64 bit mode is faster opening files but NON of my plugin's are 64 bit yet, that's why I'm still stuck in 32 bit mode.
Not knowing what size or kind of files you work on makes giving advice a bit tough but try setting the status indicator (don't know the right name for it) in the bottom left corner of any PS open file to "Efficiency" and watch what happens when you process your files. I rarely see mine drop below 90%, I've got the usable RAM in PS Prefs set to it's max suggested, cut way back on History and Cache.
Can't wait for NIK and others to offer their plugin in 64 bit, later this year is what I was told.
There used to be an old "rule of thumb" with old version of PS about Scratch disc size. I don't remember exactly but it may have been 3 to 5 times the size of your biggest file??
Good luck, Alan

Scratch disk is almost full

Hello, I just got a message while I was using photoshop that my scratch disk is almost full and that I need to delete files to clear up space. I am not sure how to clear files from the scratch disk. I cleared all the files listed under open recent.
I am on a mac dual 2 GHz PowerPC G5. There is 3 GB of memory installed and the start up disk is my harddrive. The OS is 10.5.4. I am using photoshop CS3. My hard drive is not partitioned. The L2 Cache per CPU is 512 KB.
The file I am currently working on in photoshop displays under scratch 1.35/2.05G. The file size is 38.5M/490.5M. Their have been some occasional crashes lately and I am noticing that when I am very rapidly dragging low opacity radiant gradients set to foreground to transparent, photoshop is not keeping pace with my rapid drags of the tool. I may do a 100 drags of a gradient to feather a mask and I will get a spinning disk. I have the same problem with multiple fills with the paint bucket. Also clicking file save while I work gets a delayed response and spinning gear. When I check Efficiency it hovers between 95 and 100%.
I would really appreciate any help with dealing with a scratch disk that is almost full. How do I find the temp files so I can empty them? Where is the cache so I can empty that too? How do I defrag photoshop? I have run disk utility from the utilities menu and not had any errors show up. Thanks.
Reading the answers to my question under similar topics, they all say to reduce the size of the file. I don't want to do this as the image is for print and set for 300 ppi.

"Lundberg02", what is
ridiculous is someone that feels some bizarre need to follow me to various threads simply to debate. The problem you fail to realize is that you are not really debating me. I'm just quoting what Apple and Adobe recommend. Arguing what the computer and software makers recommend makes you appear ridiculous.
>"The file I am currently working on in photoshop displays under scratch 1.35/2.05G."
>What does this mean?
Lundberg, to answer your question, this means Michael is looking at either the info panel or the values that appear in the bottom left of every Photoshop document window. You can learn more about this in the Help section. This value has been available in Photoshop for many years.
So how does Lundberg02 explain why a full scratch disk warning appears when the drive has plenty of space?
Let's see what the informed folk say:
>It is also possible to get the "scratch disk is full" error, even if the scratch disk drive has free space. This is because Photoshop requires contiguous, unfragmented free space on the scratch disk drive. If you are getting the "scratch disk is full" error message and your scratch disk drive does show a good amount of free space, you may need to run a disk defragmentation utility. [
source]
>Your primary scratch disk should be your fastest hard disk; make sure it has plenty of defragmented space available... Drives with scratch disks should be defragmented regularly. [
source]
>f) decided to buy Idefrag and try to see if fragmentation could be an issue. My drive was very fragmented ... improved speed very significant[
source]
The comment of '
Conventi[on]al wisdom is that Mac drives don't need defragging' at the Photoshop LR forum linked above makes me wonder how the idea of avoiding defragmentation tools could ever be considered conventional or wise...and who is responsible for spreading such misinformation that Lundberg and others apparently fall for blindly. Apple.com makes no claim that defragging is something to be ignored. They even advertise
a defrag app on apple.com.
So "Lundberg02", if that is your real name, why don't you explain what authority or resource led you to such an erroneous belief about how to maintain your computer? Do you have tech docs to share from Apple or Adobe or are you simply here to stir up trouble?
Don't we all like to cite
Macfixit.com?

PPro CC 2014 freezes upon clicking Browse for scratch disk

Hi forum.
I just upgraded from CS6 to CC 2014. When I open up one of my many current CS6 projects, CC says it needs to save it as a new CC file, ok no problem.
Then it pops up with scratch disk options, and they are all set to the C:\ by default. When I click Browse, to locate and select my cache drive, Premiere freezes for about 2 minutes. In fact, I thought it froze indefinitely until it unfroze while typing this post
I don't have any drive issues, no disks in the bd rom, no memory cards in the usb card reader, no drives set to sleep....what's causing this?
Thanks

Thanks for the quick response, Mr. Haugen. So I tried that. It kind of works, and it'll have to do for now just so I can finish up.
Opening up a previous auto-save actually does the same as the main project file I'd been working with. But like I mentioned, if I open a working project file first and then this one, it does allow me to play back. The auto saved one at least let's me make edits and export without freezing. But I still can't switch over to another timeline, otherwise it freezes again. So, problem not really solved, but I'll kind of walk on eggshells as I work just to complete the edit, and then hopefully never have to come back to this project file again if I can't figure out the issue completely.
I'm still open to more suggestions if anyone has them!

Scratch Disks full error in Photoshop - 107 Gigs of space on hard drive

I am trying to edit pictures under a dead line. I have used this computer a few times to edit pictures with no problems, now that I it is work and I have a dead line...there are problems.
I have dealt with scratch disk problems before and it was always that my hard drive was to full. I would delete stuff and the problem would go away.
I don't think my hard drive is full now, but I went along with everyone suggestions and deleted 10 gigs of stuff. And emptied my garbage, and rebooted...still I have the same problem.
I have 2.33 Ghz Intel Core 2 Duo and 2 GB 667 MHz DDR2 SDRAM...
Using Photo shop CS on files processed with Capture One Pro
Any ideas of what else could be causing the problem...do I have to partition my hard drive...cause I don't want to...why would it work before and now all the sudden I get this error massage?
Thanks

I should have also said I get an error massage from the Computer at the same time saying my startup disk is full. So the computer tells me that it has 107 Gig but also tells me my hard drive is almost full. That is why I posted it here. The computer is telling me 2 different things.

Something weird with Scratch disk allocation

Similar Messages

Maybe you are looking for