Background Saving

Does anyone know if it will be possible in cs6 to script the background save and continue working or will it tie up photoshop until the script is done. Also, is there any code that could release photoshop while a script is running? Any help would be...helpful.

Save in Background does not work when saving via script...?? right? is there a setting you can have to make it save in background?
When you have your preferences set ON to Edit > Preferences > File handling > Save In Background, and you save a file the normal way, File > SaveAs ... the file saves in the background so you can continue working. Great!
... BUT....
When you do that same action via script... activeDocument.saveAs() I get an annoying progress bar, which inhibits being able to work while the save is running.
Any ideas on how to turn that progress bar dialog off? I want the save in the background, just like if I selected the menu.
( app.displayDialogs = DialogModes.NO; does no good.)
Suggestions welcome. Thankyou!

Similar Messages

To which folder does OSX background saved TextEdit recovery files?

Hi, while traveling without an internet connection I workd on a TextEdit file which was probably saved in the background automatically as a temp recovery file...somehow I lost the file, whether through a failed iCloud synch upon returning home or whatever...I think though that I may have backedup my system with Time Machine before losing the file altogether. Could a background recovery version of it be in a folder accessible through Time Machine?
(By a background saved recovery file I mean the temp TextEdit file which in the event of a crash or system restart would allow the file to be recovered.)
Thanks

sorry...was exhausted, will rewrite more clearly

Background saving does not work in background when it is part of an action

I LOVE the new background saving function. I do agree with a nother post that it would be nice to have some kind of progress bar when in full screen mode though.
The other thing I noticed is that if you make an action that has a "Save" command in it, it will NOT do that in the background but rather in the way of previous versions, with the progress bar window pop-up.

Agree

Background saving bug CS6 (stalls)

Background saving bug CS6
Problem:
1. Was Editing a rather large and complex file, 16bit, 1,6GB
2. Pressed ctr+s to save the progress
3. Immediately launched a 3rd party plugin, Niksoft Define 2 (I mean with two keyboard shortcuts in a row, within seconds of each other)
4. Plugin started
5. Background saving got stuck at 0% and went nowehere as the plugin launched.
6. No progress on the background saving after the plugin exited, and not able to save as a new file because PS said it was already saving the file. After 20 minutes still no progress. Taskmanager showed PS using 0% CPU and no disk i/o activity even though it stated it was saving.
Workaround
1. Duplicated the entire psb to a new file inside photoshop.
2. Saved and it worked fine.
3. Had to terminate photoshop via the task manager as it wouldnt let me exit "before file saving was complete".
My workflow here was probably a bit quick and "incosiderate", but I would still consider this behaviour a PS bug - I mean whats the use of background saving if it stalls when you are doing other tasks. Anyone else experienced this?
(OS W7 x64+PS CS6 EXT)

I have experienced this bug many times and it is very frustrating. There is no pattern to when it will happen it just happens out of the blue, I work full time commercially in 8, 16 and 32 bit regularly, file sizes averaging 5gb sometimes much larger and the bug has occurred in all these instances. I have however made these observations:
The original PS version with bg save had this fault and to my knowledge there was no easy work around apart from a very laborious process of Scripts/Export layers to files. Any duplication and resave of the document did not work as it was held in a queue behind the first file stuck on 0%
The next version of PS, CC and possibly first release of 2014, had a work around as suggested by someone else, by simply duplicating the file and saving. This would then jump the queue of the first file which was stuck on 0%.
The latest version of CC 2014 updated a couple of days ago has resorted to the first patten, i.e. duplicate and save but stuck in the queue, thus no work around.
This is a very serious problem which has gone on a bit too long. I am prompted to write this because it happened to me again last night whilst working on a 6gb 32bit render layer file, costing me a fair bit of time and effort on a commercial job.
I always use bg save and 10mins recovery, when the problem occurs I am able to use PS as if nothing has happened but unfortunately cannot save, I am thus forced to force quit the application. Unfortunately in this instance the force quit is not seen by PS as a crash and therefore offers no file recovery. What I think we need is the following:
The ability to force abort a save of the stuck file so that we can save another.
The ability to access background saved files even if PS has not actually crashed, this would have saved me last night.
In addition, a 5-10gb file takes a while to background save, during this save I cannot make a smart object. I would like to be able to pause a save so that I can make the smart object and then carry on my work whilst the save continues. This applies to recovery save also.
Adobe please help us out and address the problem.
Many thanks, Mark.

Background saving via script? CS6/CC?

Any suggestions out there for getting script to save a file, in the background?
When you have your preferences set ON to Edit > Preferences > File handling > Save In Background, and you save a file by selecting File > SaveAs   ... the file saves in the background so you can continue working. Great!
...BUT...
When you do that same action via script... activeDocument.saveAs() I get an annoying progress bar, which inhibits being able to work while the save is running.   This makes an autosave script that is supposed to silently run, saving files in the background every few minutes while I work, kinda useless.
Any ideas on how to turn that progress bar dialog off?   So Photoshop behaves the same as if I selected SaveAs in the menu??
I Do have app.displayDialogs = DialogModes.NO; but it seems to do no good.
suggestions welcome.

Thanks for the reply Davide,
Yes, I've noticed when I run the save process via ANY other way, (regular action run, DOM ExtendScripted, Action Manger scripted, AS3 CS6) - it always has the progress bar.
This just seems to be one of those things that I just can't do automatically the same way as if you just pushed "Cntrl-S". Save in Background - is a great feature. Now if only it could be done through automation...   Anyone else have any luck?

Background saving for client runing on rmi

Hello I have a client side application that gets its data from an arraylist object that is sent over the rmi network from the server.
When ever a client logs on. The server allows the client to access its resources for only one hour
I want the client to be able to restore its data in case of pc failure i.e. power failure etc
When the client logs back in after pc failure i want it that the server should reset the client to the state it was before it disconnected.
I was thinking of using a background thread that saves the current state of the client lets says every 2mins but i cant seem to put it all together so i was looking for advice from experts here on how i can save the current state of a client and restore it back when needed.
Thanks.
Edited by: xcellng on Feb 17, 2008 5:06 PM

so i implement Serializable every 2mins have the background thread write status of client to a file also use deleteOnExit(); to delete file only on clean JVM shutDown.
so now when client logs back in from a pc failure this is how i plan to restore client status back:
//assuming i have a file tempFile that stores clients status
have a client call back method
have the server call that method to check if tempFile exist
if tempFile exist load client details from tempFile
else use defualt client settings from serveris this right?

PS CS6 beta - background saving is stucked or...

Hi guys,
OS: Win 7 Pro x64, Dual Xeon X5650, 96GB RAM, Disks: OS:480GB/270free 16TB/12TB free Disk storage, 1TB/700gb free Scratch disk,
I have been sitting and working on some tiff files (10) and when I got to the last one, and finished my work and started to save it, its stuck at 34%, I can still make duplicates of the file within PS, which will save just fine.
Interestingly, while I did the screen shot, it when to 0% again, and is still at zero % while typing this
Any ideas anyone? I do have the Photoshop edit log on! if that is any help..... it states that it has PSAutoRecovered the file... when I looked at the PSAutoRecovered folder there wasn't a copy of the file, only that document that I created last which is the attached image
thanks
Henrik
PS: Terminated PS via Task Manager.... start again no big deal

Further Noel... just tried setting the predetermined box in pixels... same problem...
What seems to happen is that the largest dimension reverts to the image boundary, while the smaller dimension crops into the image. This despite my setting the ppi to 300 - the same as the image's ppi.
The way i look at it, when i set a predertimed size, the crop box should be at that size... particularly, as you suggested, when i have pixels selected as my dimensions. And my rulers are also set to pixels.
The latest attempt as follows:
1. Image size is 20.32 x 26.14cm @300ppi (2400x3087 pixels)
2. Crop size is set to 1831 x 2776 pixels (ppi setting enabled to 300 and rulers are also in pixels)
What happens is the crop box defaults to the full height of the image and crops in at the sides. Info box shows: W:1831, H: 2776. But it's encomapssing the full 3087 pixels (height) of the original image.
The way i look at it i should get a crop box that is smaller than the image and now should be able to move the image around to gt th crop i want. This way i still have to crop into the image and it's then resampling the image.
Cheers...
S

Photoshop Latency Issues? when saving....1.5min to open 5.5 min to save same file.

I am struggling to optimize my computer for Photoshop.
An example file opens in 85 seconds. Same file saves in 340 seconds.
PhotoShop CS6 (13.0.1)
File is 21000 x 21000 - 50 layers (5.8gb .psb saved)
Why so big? - 5k.com/C.jpg
When I open image, I see 2 swap files 67gb & 8.5gb
Hard drives
C: Samsung 830 256 ssd boot drive.
Raid0 SSD Samsung 840Pro 256x2 (512total) PSswap/temp (Tests @1100mb/s read @880mb/sec write)(Z77 intel RST v11.0+ raid0 trim)
Samsung 830 ssd media drive (open & save)
File opens in 90 seconds. Saves in 340 seconds.
stays at 0% saved for 270 secs
INTEL I7 3770K 3.5G 8M R8 - CPUs utilization - about 12%+- overall - no one cpu above 50%
ASUS SABERTOOTH Z77 lga 1155 MoBo
32gb MEM 8Gx4 GSKILL F3-1866C10Q-32GXL R
variables:
tried video card at (Adv, int, basic) no change.
Toyed with an NVIDIA QUADRO 6000 PCI-E 6GB - did not see performance change.
Tried opening&saving to raid0 SSD no change.
switched PSswap & media drives - slowed it down on open & close +- 100sec.
I don't understand why it would take so much longer to save than open....
Would a better video card (4gb or 6gb) make a difference?
Would 64gb ram (dif mobo) or 6 core i7-39*0K CPU make a difference?
Unrelated - When I pan to bottom-right of image there is a major lag in display. Up to 20 sec. regardless of video settings.
Is there an easy way to calculate video ram needs based on image size? Prefer ATI - was looking at trying v9800 4gb.
Tried NVIDIA QUADRO 6000 PCI-E 6GB - didn't seem better.
I recall reading that with SSD drives, having seperate drives for OS, TMP, Media is no longer adventageous....True/False?
I am grasping at straws to figure out what my bottlenecks are and how to elliminate them.
Thanks in advance for any suggestions/advice.
SysInfo
Adobe Photoshop Version: 13.0.1 (13.0.1 20120808.r.519 2012/08/08:21:00:00) x64
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
System architecture: Intel CPU Family:6, Model:10, Stepping:9 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
Physical processor count: 4
Logical processor count: 8
Processor speed: 3510 MHz
Built-in memory: 32723 MB
Free memory: 5709 MB
Memory available to Photoshop: 29745 MB
Memory used by Photoshop: 84 %
Image tile size: 128K
Image cache levels: 4
OpenGL Drawing: Enabled.
OpenGL Drawing Mode: Basic
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
OpenGL Allow Old GPUs: Not Detected.
Video Card Vendor: ATI Technologies Inc.
Video Card Renderer: ATI FirePro V8800 (FireGL)
Display: 2
Display Bounds:= top: 0, left: 0, bottom: 1600, right: 2560
Display: 1
Display Bounds:= top: 0, left: -2560, bottom: 1600, right: 0
Video Card Number: 1
Video Card: ATI FirePro V8800 (FireGL)
OpenCL Unavailable
Driver Version: 8.911.3.3000
Driver Date: 20120309000000.000000-000
Video Card Driver:
aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dl l,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Video Mode: 2560 x 1600 x 4294967296 colors
Video Card Caption: ATI FirePro V8800 (FireGL)
Video Card Memory: 2048 MB
Video Rect Texture Size: 16384
Serial number: 90148609589462100194
Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
Temporary file path: C:\Users\Ivy1\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
E:\, 238.5G, 154.4G free
Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
Additional Plug-ins folder: not set
(shortened)
Optional and third party plug-ins: NONE
Plug-ins that failed to load: NONE
Flash:
   Mini Bridge
   Kuler
Installed TWAIN devices: NONE
I am struggling to optimize my computer for Photoshop.
This example file opens in 85 seconds. Same file saves in 340 seconds.
PhotoShop CS6 (13.0.1)
File is 21000 x 21000 - 50 layers (5.8gb .psb saved)
Why so big? - 5k.com/C.jpg
When open image, I see 2 swap files 67gb & 8.5gb
Hard drives
c: Samsung 830 256 ssd boot drive.
Raid0 SSD Samsung 840Pro 256x2 (512total) PSswap/temp (Tests @1100mb/s read @880mb/sec write)(Z77 intel RST v11.0+ raid0 trim)
Samsung 830 ssd media drive (open & save)
File opens in 90 seconds. Saves in 340 seconds.
stays at 0% saved for 270 secs
INTEL I7 3770K 3.5G 8M R8 - CPUs utilization - about 12%+- overall - no one cpu above 50%
ASUS SABERTOOTH Z77 lga 1155 MoBo
MEM 8Gx4|GSKILL F3-1866C10Q-32GXL R
variables:
tried video card at (Adv, int, basic) no change.
Toyed with an NVIDIA QUADRO 6000 PCI-E 6GB - did not see performance change.
Tried opening&saving to raid0 SSD no change.
switched PSswap & media drives - slowed it down on open & close +- 100sec.
I don't understand why it would take so much longer to save than open....
Would a better video card (4gb or 6gb) make a difference?
Would 64gb ram (dif mobo) or 6 core i7-39*0K CPU make a difference?
When I pan to bottom-right of image there is a major lag in display. Up to 20 sec. regardless of video settings.
Is there an easy way to calculate video ram needs based on image size? Prefer ATI - was looking at trying v9800 4gb.
I recall reading that with SSD drives, having seperate drives for OS, TMP, Media is no longer adventageous....True/False?
I am grasping at straws to figure out what my bottlenecks are and how to elliminate them.
SysInfo
Adobe Photoshop Version: 13.0.1 (13.0.1 20120808.r.519 2012/08/08:21:00:00) x64
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
System architecture: Intel CPU Family:6, Model:10, Stepping:9 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
Physical processor count: 4
Logical processor count: 8
Processor speed: 3510 MHz
Built-in memory: 32723 MB
Free memory: 5709 MB
Memory available to Photoshop: 29745 MB
Memory used by Photoshop: 84 %
Image tile size: 128K
Image cache levels: 4
OpenGL Drawing: Enabled.
OpenGL Drawing Mode: Basic
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
OpenGL Allow Old GPUs: Not Detected.
Video Card Vendor: ATI Technologies Inc.
Video Card Renderer: ATI FirePro V8800 (FireGL)
Display: 2
Display Bounds:= top: 0, left: 0, bottom: 1600, right: 2560
Display: 1
Display Bounds:= top: 0, left: -2560, bottom: 1600, right: 0
Video Card Number: 1
Video Card: ATI FirePro V8800 (FireGL)
OpenCL Unavailable
Driver Version: 8.911.3.3000
Driver Date: 20120309000000.000000-000
Video Card Driver:
aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dl l,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Video Mode: 2560 x 1600 x 4294967296 colors
Video Card Caption: ATI FirePro V8800 (FireGL)
Video Card Memory: 2048 MB
Video Rect Texture Size: 16384
Serial number: 90148609589462100194
Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
Temporary file path: C:\Users\Ivy1\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
E:\, 238.5G, 154.4G free
Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
Additional Plug-ins folder: not set
(shortened)
Optional and third party plug-ins: NONE
Plug-ins that failed to load: NONE
Flash:
   Mini Bridge
   Kuler
Installed TWAIN devices: NONE
Message was edited by: PECourtejoie

That sounds like a pretty big document considering all the layers. What's the nature of all those layers? Pixel data edge to edge, or some vector data, some adjustment layers, a mix? Do the layers have masks?
I was curious, so I timed the saving of a very large image I have on hand, with 32009 x 21000 pixels, 16 bits/channel, 42 layers, some pixels, some adjustment layers, most layers with masks. I have "Maximize Compatibility" set to "Never" and I enabled Flate compression. The save was to a high bandwidth SSD array, and like you I have Windows 7 x64.
The save went like this:
It started at 0%
Jumped to 25% at 8 seconds into the save.
26% at 0:35
27% at 1:30
28% at 3:15
etc. at long intervals. The file psA3B2.tmp grew incrementally all during that time.
It seemed to stop at 73% for a few minutes.
The save completed in 22 minutes 10 seconds and the .psb file was ultimately 6.6 GB in size.
Since I have Background saving enabled in Photoshop CS6 I was able to interact with Photoshop and could potentially have been continuing editing during that time. Also I had no problem doing other things, like type up this message, chat on Skype, etc.
I have 48GB of RAM and actual usage rose to 43.4 GB. Photoshop created a 58GB scratch file.
It busied one logical processor (of 24) pretty much to the max the entire time (showing a total of 4% usage). As I understand it data compression is not something easily multi-threaded (though I wonder whether it could be done by multiple threads on a layer by layer basis). Your core speed is faster than mine with that i7-3770K processor (as compared to my Xeon X5690 CPUs), and who knows how different our documents are, but I'd say your system did rather well given that you have compression enabled.
The real workaround that could make it more usable for you is what Chris said above - for a document at this magnitude in size, disable the Flate compression and it will get right to the task of saving to disk. And yes, it will make the file HUGE - so you trade size for speed.
As a test I disabled compression and saved again. This time the save completed in 1 minute 29 seconds and the .psb file ended up being 36.5 GB in size.
-Noel

Error executing in Background

Hello people,
I have a program that when running on line, the files are saved in a local Folder or in a Folder in the server but when try to execute in Background saving in the same Folders, a error occurs.
Anybody knows what can I do to resolve this problem, please ?
tks
regards
Flavio Ferreira

If you are not scheduling it in Backgroung you can use that FM .
you cannot download to the frontend in a background job simply because the GUI isn't available. You will have to use OPEN DATASET and put the file on the Application server in the background and then use the transaction CG3Y in the foreground to download the file to the pc from the application server.
Rhea.
Edited by: rhea on Nov 27, 2008 3:31 PM

How to insert cropped images from photoshop without the white background

Basically all I want to do is take a peice of writing from a video and insert it into another video. To do this I've took a screenshot of the font from the video and imported it into photoshop. I've then cropped/cut/took the the peice of writing I want, letter by letter. I want to be able to insert it into another video, but whenever I attempt to do it, I have the default white background of photoshop. Is there anyway to insert an image from photoshop, without taking the background with it, or even insert a layer from photoshop straight into final cut pro? Sorry if this is confusing.

I don't think so. I cropped the letters, put them each an individual file, removed the background, saved them as a TIF then tried to import them onto Final Cut Pro, but a white background still appeared in the TIF file. Basically I just want to make the background transparent I believe.

Not saving work when app switch

I rated the app in the store and was to explain further regarding my work getting lost.    I've actually up'd the star rating because I think it's not really an Adobe issue. I think android closes apps when it reaches a certain limit of apps running. switching apps probably just closes photoshop touch. I know on HTC it's 7 apps.
Anyway, if you switch apps with the android app switcher, and use something else and come back, sometimes the app crashes, or just starts over, loosing your work. An example, switching to see a SMS and right back will close your project sometimes. Other times it goes back to exactly where it was at. Again, probably an android mememory thing..   Wondering if maybe you can have background saving to a temp file and reopen that if the app is closed by android.
phone: galaxy note 2
Anyway, thanks for looking into it. great app guys.
Maybe a way to import PSD's without adobe cloud? :-D

Never, ever, ever trust a program to save your work for you. I learned that several times myself -the hard way- losing data while working on projects.
Always
make
it a habit to obsessively save your a work during progress.
edounn wrote:
I rated the app in the store and was to explain further regarding my work getting lost.    I've actually up'd the star rating because I think it's not really an Adobe issue. I think android closes apps when it reaches a certain limit of apps running. switching apps probably just closes photoshop touch. I know on HTC it's 7 apps.
Anyway, if you switch apps with the android app switcher, and use something else and come back, sometimes the app crashes, or just starts over, loosing your work. An example, switching to see a SMS and right back will close your project sometimes. Other times it goes back to exactly where it was at. Again, probably an android mememory thing..   Wondering if maybe you can have background saving to a temp file and reopen that if the app is closed by android.
phone: galaxy note 2
Anyway, thanks for looking into it. great app guys.
Maybe a way to import PSD's without adobe cloud? :-D

Transparent background not staying transparent in dreamweaver

Hello all-
I am having an issue with importing a file with a transparent background into dreamweaver. I created the image with a transparent background, saved for web as a PNG, keeping the transparent background. When I pull the file into dreamweaver, the background of the image turns to yellow. Any ideas what I may or may not be doing?
I created the image in illustrator and pulled to photoshop to manipulate. I'm saving the image for web/devices from photoshop.
Thanks.
Brianne

You should repost in the Dreamweaver forum, this has nothing to do with color management.

IndesignCS3 not saving work

Indesign CS3 document did not save 6 hours of work eventhough i was continually saving...

Never, ever, ever trust a program to save your work for you. I learned that several times myself -the hard way- losing data while working on projects.
Always
make
it a habit to obsessively save your a work during progress.
edounn wrote:
I rated the app in the store and was to explain further regarding my work getting lost. I've actually up'd the star rating because I think it's not really an Adobe issue. I think android closes apps when it reaches a certain limit of apps running. switching apps probably just closes photoshop touch. I know on HTC it's 7 apps.
Anyway, if you switch apps with the android app switcher, and use something else and come back, sometimes the app crashes, or just starts over, loosing your work. An example, switching to see a SMS and right back will close your project sometimes. Other times it goes back to exactly where it was at. Again, probably an android mememory thing.. Wondering if maybe you can have background saving to a temp file and reopen that if the app is closed by android.
phone: galaxy note 2
Anyway, thanks for looking into it. great app guys.
Maybe a way to import PSD's without adobe cloud? :-D

CS5.5 Gripes/CS6 Wish List (from the perspective of an FCP switcher)

I have been a Final Cut Pro user for more than 10 years (starting with version 1.2 on a 500 MHz G4). Final Cut Pro X is a disaster, but that’s a well-covered topic for a different forum. After experimenting with Premiere Pro CS5.5 for a few months, I am ready to make the switch for all of my future projects.
I make a living editing video. I don’t, however, work for a big company, and I don’t have a lot of money to spend on third-party software or hardware. Much of my work is shot on DSLRs and delivered online. That may put me in the category of “pro-sumer” to some, but I wouldn’t be making the switch if I didn’t require a more professional alternative to FCPX to do my job.
I also don’t think “pro” has to be synonymous with clunky and ugly. (I’m looking at you, Avid.) When Final Cut was young, it was fun, intuitive, and sturdy. It became a robust, professional NLE over time. I think Premiere Pro is on that path now.
I like the look, the feel, and the functionality of CS5.5. It’s not quite Apple-slick, but it’s very much at home on a Mac. Overall, it’s an upgrade to FCP7 and a very strong alternative to FCPX. I have high hopes for CS6.
But this is not a comprehensive review. It is just a list of negatives: my gripes, wishes, and personal preferences. My list of positives would be much longer, but my concern right now is with CS6 and the improvements that I hope it delivers. As I am new to Premiere, it's quite possible that I am mistaken about certain functionalities or lack thereof, but I thoroughly researched each point in the help docs and forums before posting this.
My primary system is a 3.2 GHz iMac 21” (2010) with 8 GB RAM, 512MB VRAM (ATI Radeon HD), running Mac OS X 10.7 with external Firewire 800 drives and a DisplayPort-to-HDMI external display.
MAJOR ISSUES
Hardware acceleration support for ATI GPUs
There are rumors that Apple will be switching back to nVidia, but all recent iMacs have ATI and only ATI cards.
Background rendering (or at least improved rendering options)
Background rendering is probably FCPX’s most impressive feature and Adobe needs to catch up. However, even if true background rending can’t be achieved, there should be an auto-render option (after a set idle time), partial rendering (if you cancel a render, keep everything that has been rendered up until that point), and more render options (e.g. render all and render selected). Regarding that last point, I think the whole work area concept should be dropped. It makes sense for other apps, particularly for animation, but it just gets in the way of more important timeline functions while offering little functionality beyond being a clumsy way to control the area to be rendered. At the very least, have a way to hide it.
Full-screen preview
Maximizing the program frame just isn’t the same (although the grave accent key function may be reason enough to switch to Premiere). Full-screen preview isn’t just a nifty function for demo-ing sequences. It’s a big part of the way I work.
DisplayPort/Thunderbolt out to HDMI
It may be that a third-party card is required for proper color correction on an external display, but there’s no reason this feature shouldn’t exist.
Thumbnail images/show frames bug
This one drives me crazy. I’ve tested this on 3 different Mac systems with various hardware configurations. Thumbnail images in the bins and frame images in the timeline seem to be recreated every time a project is opened, even though the thumbnail image files in the media cache folder don’t actually appear to get rewritten. It’s as if there is no cache at all (even for the most recently viewed bins and timelines segments). It can’t be an intentional functionality for saving hard drive space because the cache files continue to take up more and more space.
Open multiple projects simultaneously
I know that you can cut and paste between projects but being able to open multiple projects at the same time is a very useful feature of FCP7.
Magic Mouse/Magic Trackpad scrolling
Premiere Pro is a cross-platform system and impressively so, but there need to be a few Mac-specific interface adjustments, the most important of which is support for the Magic Mouse and Magic Trackpad scrolling. I use a Magic Mouse. (It’s an irritating device sometimes, but once you get used to it, it’s hard to live without it.) When I’m in a window, I expect a flick up or down to scroll up or down -- in every situation, every time, including the timeline. Unless I stop using all other Mac apps, I will never get accustomed to the timeline suddenly flying left or right when I want to scroll up or down. Also, here’s a chance for Adobe to fix a problem that FCP7 shared: When you scroll up or down in the effect control window using the mouse, the drop-down effect controls sometimes twirl all over the place if the mouse happens to float over them. As it is, it very easy to throw settings into random disarray without even realizing it just by scrolling through the pane.
The timeline: selection indication, icons, and general improvements
It is very difficult to discern at a glance what, if anything, is selected in the timeline. Transitions always look selected! Audio tracks should be a different color or otherwise more distinct. There should be an option to show frames only without any text. The icons for track options are small, crowded, and ugly. Some of the editing icons are too similar, namely edit and ripple edit, although the excellent status bar at the bottom of the application goes a long way towards making up for this. Simply put, the timeline could use some polish. Don’t be afraid to steal from Apple on this one. Keep the tracks; just make it easier on the eyes!
Conforming audio
The ability of CS5.5 to work natively with DSLR footage is awesome, but it’s not fully DSLR native if it has to pre-render a major component of the footage before it can play, even if it’s just the audio.
Media loading
When launching a project, it can take a long time for all the media in the project to “load” as tracked in the status bar. I’m sure there’s a reason for this, but since the program is able to determine which source media files are missing before this step (and gives you the option to reconnect them), what is it doing and why must it load every clip in the project, even those not in use by any sequences?
Page up/page down and arrow key commands
For starters, the current page up/page down key functions should take the CTI to the next cut in the sequence, not the next cut in the track that happens to be targeted, which can be way down timeline. In FCP7, I frequently navigated cut to cut with the up and down arrow keys. I’ve avoided customizing the keyboard commands to match FCP7 -- I would rather endure some hardship and learn the proper Adobe commands -- but this one is flat-out backwards. The page up/down keys should page through the timeline (left to right and right to left), while the up and down arrow keys should take over the clip to clip function (assuming the targeted track issue is fixed). Currently, the down arrow takes you to the very end of the timeline, a function already duplicated by and better suited for the “end” key.
Bin management and clip relationships
Deleting an item from a bin should not delete it from the timeline, but this is part of a bigger problem, which is the whole master file versus instance versus subclip versus dup clip thing. There aren’t any good indicators regarding the relationships of these clips, and there are few ways to adjust them. If clips are going to be connected, then they should be fully connected. For instance, changing the name of a clip in the bin should change it in the timeline. Adding an effect or trimming should affect the corresponding clips between bin and timeline. Otherwise, the clips should just be completely separate instances. I haven’t been able to find an option to turn a clip into an independent instance, although I have to think it exists. Also, editing an instance of a title does change every other instance of that title throughout the sequence. I would prefer to be able to edit them separately without having to duplicate them in the title editor.
Bin effects
Related to the above, it should be possible to add effects to clips in bins or keep effects on clips added to bin from timeline. It would also be nice to be able to group effects together in bins for a specific project. The effects window is better suited for global collections.
Clearer visual indicators that a clip has been adjusted in the effect controls panel
Even with the effects panel visible, you have to take a close look to see if there have been any adjustments to the standard settings. An indicator on the clip in the timeline itself would be useful.
Snapping should include the CTI
It should also include the blade tool, although the Cmd-K option to cut at the CTI position does make this less of an issue.
Smoother scrubbing
Scrubbing is pretty awful. While this is understandable with native footage, FCPX somehow manages to make this silky smooth at full resolution.
Color correction shape mask and better color correction in general
Simplify the primary functions of the 3-way color correction effect. Keep all the rarely used adjustments out of the way. I use Magic Bullet for some purpose, but I’ve always done most of my color correction within FCP. Put the most common adjustments front and center (or up top, as it may be). The highlights/mid-tone/shadows drop-down is inconsistent in what controls it pertains to.
FCPX’s color correction is actually one of its more underrated features. The way it allows you to layer corrections is dead-simple yet as powerful as anything in FCP7 or Premiere. Stick with the 3 wheels, but rely less on hard to control tonal ranges and add simple keyframe-able shape masks for secondary color correction.
Better support for shared media access
AVID is king in this arena and Adobe needs to improve. It should be possible for multiple editors to safely work on the same project files and share media over a server.
MINOR ISSUES
More vertically compact playback/edit control area in source and program panes
Make room for either a taller timeline or bigger previews. The virtual scrubber and shuttle controls are the nifty things you drag with the mouse the first time you ever use an NLE and never touch again.
Larger icons in icon view
Remember size and position of bin windows
Playback resolution setting indicator
There should be an always-visible indicator of the playback res setting in the preview pane that’s easy to adjust without right-clicking.
Better markers for sequences and clips
Include colors and more keyboard shortcut control.
Clip sliding with keyboard commands
“Opt-,” (that’s Option-comma) should cause a clip collision, not overwrite. Either that, or “,” and “.” should slide, while “Opt-,” should overwrite. Opt-arrow should only extend an adjoining clip if in the middle of two clips. Basically, this whole arrangement should be re-thought.
Project browser should auto refresh/sort.
Option-drag on a Mac should always be copy, not move.
Copy is currently command-drag in the project browser.
Stop auto-save from interrupting adjustments in timeline.
Ideally, the auto-save should just be a background function, but it should at least wait until you’re not in the middle of dragging something.
Add ability to select a cut directly and add default transition.
CTI control
If you move the CTI while it’s in play mode, it should continue to play from that spot after you release the mouse, not stop there.
Show number of frames being adjusted during keyframe adjustments.
Enable/disable specific effect parameters/keyframes.
Clearing an effect should clear keyframes as well.
Or have an option to clear both.
Position controls
There should be a preference to make the default position 0.0 x 0.0 (as opposed to 50% of whatever the resolution happens to be), and include a reset button.
Through-edit indicator in timeline
And a quick way to join clips, such as a right-click menu option.
Border controls for images
Auto save location preference and functionality
In FCP7 I set the number of auto saves to keep to the maximum of 100 and Premiere can go even higher. I have always used this feature as an additional backup and archive system, which has come in very handy. Those files add up, however. So, I prefer to auto-save to an external drive. Also, auto saves in Premiere continue to occur whenever there are unsaved changes. This means that if you make a small adjustment and then leave Premiere for a while, it will keep auto saving the same iteration, which is not only inefficient but leads to my next point….
Tame the bouncing dock icon on auto save
While using other apps, there’s no need for the dock icon to bounce every time Premiere performs an auto save.
More/clearer control over cache locations
There should also be an option to reset the cache/render file locations to their defaults.
Export source range
When exporting, remember the last-used setting of the export source range (or just dump the whole work area thing as I previously suggested). It’s too easy to cut off a portion of the video when the export defaults back to the work area every time.
Larger timecode display
After spending hours and hours editing, the current timecode for clips and sequences is something you want to be able to track without squinting. Use the letters h,m,s and f instead of colons.
Simple slug
Creating a black matte works okay, but it involves a few extra steps.
Snapping toggle
FCP allows you to quickly toggle snapping while dragging a clip. Upon releasing the clip, the snap toggle returns to its original state. Premiere could use this fucntion, but I suggest something simpler. Holding down the “S” key should always turn snapping on regardless of toggle state, while releasing it returns it to however it was set before.
Ability to dock the audio meters along top
I like to give my timeline as much horizontal space as possible. I’ve noticed a lot of users keep the toolbar up there, myself included. I think it would be a good place horizontally aligned audio meters as well.
More detailed tool tips or hover explanations in preferences
For example: The options regarding XMP data should make it clear that the original files will be modified by Premiere. This caused me problems in other applications. (After researching these settings, I understand that various Adobe applications use this information to share resources, but it’s still very unclear what the specific benefits are or what functions are lost without this option.)
More detailed support documents
The online support documents on the Adobe site very good. They are nicely arranged and easy to search, but they could be more detailed and offer fuller explanations. (Peruse the support forums and you will discover all kinds of debates that could have been easily cleared up with one concise line in a help document.)
Icons and button design
Icons and buttons are often too small, too similar, and too crowded throughout the interface. Take some style tips from Apple on this one.
NEW FEATURE WISH LIST
Footage auto-analysis: shot recognition, color correction, and color match
If only Apple had just added these features and others to the FCP7 framework. Adobe can do it better though, by using smart folders in addition to the traditional bins that we know and trust (anything besides those dreadful iMovie-style “events”).
Effect previews
In the 64-bit era, there has to be a quicker way to preview effects.
Ability to render in alternate formats
Namely ProRes or DNxHD. This would save me considerable time on exports by allowing me to select the “use preview files” option.
PluralEyes functionality
Okay, I suppose I should just purchase PluralEyes...again.
Many, many more effects!
How about starting with the missing vignette effect? Just because an app is “pro” doesn’t mean you should have to custom build every effect.
Many, many more looks!
Will most of them be cheesy looks I would never touch? Sure...but give me some templates to play with before I tweak the look down to my exact specifications.
More speed!
FCPX, for all its flaws, blazes on any modern Mac. This probably comes back to hardware acceleration, but while Premiere Pro on a Mac isn’t slow, it doesn’t blow you away.

You hit the nail on the head, Peter.
I recently started giving Premiere Pro CS5 a try, and was shocked by the amount of bugs and usability issues. I'm not even going as deep as you in the features, but the most glaring evidence of the lousy interface is that timecode offset bubble that appears everytime you move a clip in the timeline... the bugger appears just under your mouse pointer and won't go away, so if you try to just move a clip down a track quickly, and let go of the button ONTO the bubble, it acts as an obstacle and your drag/drop fails ! seriously, Adobe... don't tell me nobody has stumbled upon this one during beta-testing ?
Ditto on the autosave that basicly interrupts anything you're doing. No background saving in 2011 ? At first it bothered me to no end so I disabled the autosave. And then a few hours later, Premiere crashed, and didn't even try to recover my work. I lost 2 hours of intricate work. I put autosave back on, and learned to endure the constant, annoying save dialog. And it's not like the save process is instant... even the simplest of projects takes 5 to 10 seconds to save... on an SSD... come on... let me work already...
Of course, a headache-inducing implementation wouldn't be complete if the autosave didn't trigger even 30 seconds after a manual save. If I choose an interval of 5 minutes, just autosave 5 minutes after a manual save !
In thumbnail view, you can reorder the clips manually. It's all fine, but you can't reorder them by name or date or length, unless you switch to list view and of course, lose the thumbnails.
Dragging and dropping a clip in thumbnail view is a chore, because the palette doesn't scroll when the mouse reaches the edge. You know, when you want to move something at the top all the way to the bottom... so you have to drag, let go, scroll one screen, drag, let go, scroll one screen... it's a joke. Even the timeline can do it. Heck, it's a software standard, nowadays.
Renaming a clip and pressing ENTER takes you back to... the top of the folder !?! How many times I've renamed files that were at the end of the thumbnail view, and for each clip, I had to scroll back down. Time waster.
Want to locate a clip from the timeline, in the project ? the locate function takes you to the folder. But not to the file, you have to navigate towards it manually.
Ditto on the up/down arrows. I haven't found a way to jump from cut to cut like in FCP7. How often do I need to jump to the starting/ending points ? much less often than jumping to a nearby cut.
How come I can't reorder filters in the effects pane ? sorry, I can actually reorder the filters... provided I take them from the bottom and move them up. Moving effects down doesn't work. It's driving me crazy.
Conforming happens more or less anytime. Without reason. And even if the Media Cache is already full of conformed files.
When moving the boundaries of the work area, no timecode/offset appears. You need to let go of the button and THEN hover, then you'll know the exact time/duration.
Try scrolling up in the timeline, it scrolls to the left (which is stupid, it should scroll up). Now scroll up on the tabs of a palette : they scroll to the right !?!
Can't select an active track. Direct consequence : copy-pasting a clip overlaps anything that's on track 1. Say I want to duplicate clips on the same track... I can't do it.
Copy-pasting between projects doesn't keep the transitions, only the order of the clips.
Have you tried doing a frame freeze on a reversed clip and setting proper in/out points for the freeze ? Good luck.
"Duplicate" command, when you right click on a thumbnail, is way too far from the cut/copy/paste commands at the top, even though they're quite related.
The other day I transcoded footage with different audio parameters. Just the audio had changed. Upon opening the project, Premiere wanted me to locate the files, which I did. And it failed miserably. Instead, I opened the project ignoring the missing files, and then re-linked them. I pointed Premiere at the first missing file, and had to confirm the replacement. Premiere saw all the other missing files in that folder, and began prompting me FOR EACH SINGLE FILE !!! two hundred and forty three of them, precisely. Can't I have a "yes to all" button in 2012 ? and why does the relinking work inside the project and not when you open a project ?
That was just from 3 days with Premiere Pro CS5. I still can't believe it. Just to think people bashed Final Cut Pro X, praising Premiere in comparison... Sorry, but they both have serious issues. And Premiere doesn't even have the excuse of novelty.

Animated .GIF Issue Need Help

I made an animated gif with a transparent background, saved it for the web with the best quality settings I know of, and the image gets this weird white outline around it. Here's what it looks like on grey background so you can actually see the issue I'm having: http://imgur.com/ujKBJDu
at first I thought it was an anti alias issue with my crappy laptop, but then when I exported it on a high end gaming pc it looked exactly the same. Anyway I need to export this and not end up with this issue so any help is appreciated.

When it comes to gif, there is no anti-aliasing. As the transparency has only one shade of grey. The white line is residual from a white background.

Background Saving

Similar Messages

Maybe you are looking for