You can move them to the second monitor.
Bob
I guess if you can move the pallettes it is not obvious how to undock them. do you havc the procedure for undocking.
Fill slider also intermittenly locks-up the program requireing termination of CS3 with the task manager. This slider other than having the same focus problems works ok in lightroom 4.1.
OS is XP64. I was sure hoping that Adobe would give us a 64 bit version with this iteration.
Futher info: If you bring a large number of images ( 104ea of Canon 5D) into ACR from Bridge using Cntrl A and then Cntrl R and select each image one at a time for exp, recovery, fill, etc, after about 6 or 8 images are processed the program locks-up. closeing Photoshop lets you continue for several more images and then it locks-up again, requireing termination. Task manage shows that ACR is using over 2 GB of memory. System has 4 Gb of memory with a dedicated 9 gb SCCI scratch disk. Scratch disk selection will only remember 1 scratch disk when selecting in edit and moving the sequence of preference. I.E. S, E, D, C=unselected, only remembers the S disk.
My next step is to try changing the amount of memory allocated to PS.
Futher info: Backing up to CS2 and ACR 3.6 and preforming the same procedures. The memory levels off at about 780 Mb and changes very little between images, whereas ACR4.0 the memory usage continues to climb until it reaches the limits of memory and the one available scratch disk. It than gives an error message and requires termination.
I would suggest that the problem lies in ACR 4.0 memory management. Dosen’t anyone use Bounds Checker anymore?
Also the ACR profile still says 3.3, the same as Lightroom 4.1 while ACR 3.6 profile still says 3.2.
Dude (or dudette)…
PLEASE keep in mind that you are working with a BETA version of PSCS3.
It’s going to have some bugs. That’s the nature of a BETA, in case you’ve never worked with one before.
And understand that when you ask questions about new features or procedures or new UI conventions that it would be just as easy for you to discover the new stuff on your own as it would be for anyone else to write about them. Keep in mind that other BETA users are in the same boat as you are…it’s new territory for EVERYBODY.
It sounds like you know Photoshop in general well enough. How about if you do some exploring and write up your findings for the rest of us who won’t be trying out the BETA!?
Cheers!
π
while i kinda agree w/phos, sjprg is doing a great service by reporting these. however, this probably isn’t the best place. most betas have a formal reporting structure in place to report bugs or problems. does one exist for this one?
sjprg,
Please move your discussion to the PS3 BETA forum (it should be up soon @ Adobe Labs to save us from beta comments here).
Also, try spending some more time with the beta before commenting. It’s pretty easy to float your palettes…. Drag’n’drop!!
Thats why I’m giving the feedback as I go. My complaints really refer to memory management 101, which in my opinion PS has allways had all the way back.
Latest info: By just opening Bridge with the 104 5D images it requires 680 Mb. A workaround is to select each image individually and then do a Cntrl+R on one image. This takes the memory to about 780 Mb. After adjustment and selecting "Done" memory returns to ~680. So it does free when ACR closes, it just dosen’t between images the way that 3.6 does. I’ll check Lightroom 4.1 and see how it handles memory next.
Mathias:
OK will do.
But the drag and drop doesen’t work.
sjprg,
On my build, its just a matter of grabbing a palette, and moving it to float it.
The GUI has had a major overhaul, and it takes a while to get used to it all.
It’s a BETA, with all the foibles that engenders.
I don’t mean to harp, but that fact must be kept foremost in mind.
There are certain things which haven’t been totally nailed down yet, and users are bound to run up against limitations and some odd behaviors.
As has been said, the best place to report these is on the Labs.Adobe.Com forum…when they get it up and running:
<
http://labs.adobe.com/community/>
I, for one, wish to say that these dynamics are great!
It is great, for example, to see realistic dialogs before commercial release. Way to go Adobe!
dave milbut wrote
"however, this probably isn’t the best place. most betas have a formal reporting structure in place to report bugs or problems. does one exist for this one?"
There is no beta forum at labs yet. Just don’t read the "CS3" threads!
The beta seems OK so far. Not having researched or read the promo stuff yet I don’t see anything especially better about PS10 over PS9 having fiddled around for a couple of hours.
Bridge and Camera Raw are much improved. GOOD WORK ADOBE!
A couple of small points;
Dodge and Burn have no effect in PS10. If I load the image into PS9 they work just fine. In PS10 the Dodge and Burn tools display and adjust but that’s all.
My XP Pro Taskbar intermittently gets black areas in and around icons after working in CS3, doesn’t seem to effect much though.
I can’t run PS9 and PS10 at the same time. If I click on a thumbnail in Bridge2 and PS9 is open the image opens there. If PS10 is open then the image opens there. That’s almost convenient.
If I have "Double-Click Edits Camera Raw Settings in Bridge" selected, I open an image in Camera Raw and click "Done" the image is opened in PS10 but the screen goes back to Bridge2. I then have to click on "Ps" in the Taskbar. . . might be normal but it’s strange.
Other than that Adobe has got a winner here. Did I mention ACR4=WOW?
Just don’t read the "CS3" threads!
Mom: Kids, stay away from the candy jar! π
Maybe it’s me but CS3 is not working with my net worked printers. We have Kodak 1400’s Mitsubishi 9550 and Epson 4800 printers and I can’t get cs3 to work with any of the printers. More to the point, when I make settings to the printer i.e. paper size or color settings they won’t take.
Anyone having this problem?
off topic, how do you like the 1400s eric? i just got one and haven’t printed anything yet?
I like them, and think that they are well suited to the majority of the people that Kodak has marketed to.
A few issues for me though, first is that bright whites can come out pink/magenta and second is that the darn things aren’t sealed. All of my wedding prints are lab processed. I tested a few bridals when we put the 1400’s in last year. Don’t waste your time or money for bridals. Period.
Dust gets into them from every possible point. I’d say that 1 in five prints have to be re-made due to dust. The first print of every kit is just a sacrificial print. It will have dust as both the paper tray and dye tray are bound to attract dust while being loaded.
We have them as part of our event setup. They work, and the colors are on the money (as long as your pitcher or QB isn’t wearing a wedding dress)and if it weren’t for the dust issue I’d put two more on the list. There is nothing in this price range that will give you this quality.
Buy the 14 inch print kits as the 12 inch kits will limit you to an 8×10 print area. The printer uses a 2 inch leader. The 14 inch kit will allow you to print an 8×12 or (4) 4×6’s. The kits are priced the same so why not get something a little more versatile.
Eric
very kind eric. thanks for the great info! (now i hope you get the help you need!)
Could not install π
Also failed: Version Cue Client CS3, Asset Services CS3, Bridge CS3. And I even did not see them in Installation Option List (but Bridge CS3).
All installation process was perfomed by default (I’ve nothing changed). I’ve downloaded adobephotoshop_10_12-14-06.exe = 354 351 499 bytes. Windows XP SP2 Prof Engl.
What happened? I couldn’t find any log to discover the reason for failure.
I had the same error pipkin. i rebooted and started the install again, selecing "modify" and all went clean.
I suspect it might be a video card problem, however it works great on PS CS2 and every other program I use.
I am sure these problems will be addressed. That’s the whole purpose of a Beta. I am just surprised that there would be such a blatant problem.
I am just surprised that there would be such a blatant problem.
None of those "problems" here.
Me too, no any problems, because I still could not install CS3 at all so far π
Nothing like that, but lots of little display anomalies, especially in Bridge, but nothing you wouldn’t expect in a Γeta
lots of little display anomalies
As usual, there seems to be a lot of things tied to various kinds of video cards and drivers.
And also as usual…Adobe continues to ignore the merits of enhancing their GUI with customizable toolbars/button-bars that can be enabled/disabled in accordance with a user’s desire for such a feature. ~sigh~
The GUI mods for CS3 seem to improve upon the look; time will tell how much they also prove useful. I’d really like to have seen an option for the toolbox to be oriented in a horizontal layout, as I tend to prefer having tools, menus, buttons along the top rather than to the sides of an image. I’m not sure, but I think I’ll miss having the palette well, as it was one way to make good use of all the extra wasted space in the menu bar area, which now seems to have a lot of wasted, usable space again.
I’m sighing with you Daryl π
The new palette docking/minimising is cool though Β it obviates the need for a second monitor with Photoshop. I use mine now just for Bridge.
Re: My problem as stated above. It appears the Bridge views that were corrupted were ALL layered Tiffs. When opened and saved as a PSD Bridge did fine with the identical image.
A second observation. The thumbnail looked fine. It was only the enlarged version that was corrupted. Again, it opened fine. This would NOT seem to be a video card problem. By the way, I cleaned the cach repeatedly.
It’s a bug. And I am sure it will be fixed if I can ever get the info to Adobe. All the sites are pretty jammed up to download fever!
Adobe ever read this?
Of course they do (?) Unofficially (?)
Adobe ever read this?
These are User-to-User forums.
One or two of the engineers do pop in now and again – but usually on their own time. Chris Cox being one of the most frequent (and welcome) visitors from "the other side".
The CS3 BETA forum is another matter, however. Although still a U2U forum, you can bet the engineers will be monitoring every thread for signs of bugs (real or imagined) in their new baby.
Therefore, that has got to be the best place to go for Beta related issues.
Chris.
I’ve played with ‘Photoshop CS3 beta’ and think now that that version must be, for example, ‘Photoshop 9.0.3’ or even ‘Photoshop 9.1’ (i.e. "CS2 improved") but not 10.
That’s my opinion. And I don’t see now any serious reasons for imperative upgrading in future into this new version since it wouldn’t give me any appreciable gains in my work. My anticipations are down… π
So, looking forward for version 11 ??
Does anyone know if CS3 supports more than two processors? Or if not in the beta, if it’s planned in the release.
Pipkin – as a PC user I would have to agree. Disappointment! Big time! As a Mac user I would be thrilled – well sort of. Maybe. Faster, for sure . . . but . . . "Nearly all Photoshop plugins will not work on Intel Macs in Photoshop CS3 running native. We feel this is a major issue for many Photoshop users with larger plugin collections. The only solution is to run Photoshop CS3 under Rosetta. This works fine but also slows Photoshop down. Again the beta is a great help for all plugin developers to get their filters ported to an Universal version."
And then in the first part of 2007 we will have a four-core Kentsfield. Will PS CS3 take advantage of it? I would ASSUME so . . . but after this last round of surprises I am not so sure.
Pipkin – go read the CS3 FAQ or CS3 Release Notes. There are a bunch of new features in the CS3 public beta. But there are more features to come in the final release.
(and for every release of Photoshop, there is some wank who says "it’s only a .1 or .5", then they upgrade and learn the new features and won’t go back)
Lanny – Photoshop has supported Multiple Processors since version 2.5 (and there has only rarely been a limit on the number of processors).
Thank you, Chris. Wait for the final release…
The now side is now we can all get more repetitive stress problems with all of the extra mouse moving and clicking. Its’ nice looking but as practical as a lemming for a hood ornament.
Robert
"John Joslin" wrote in message
I’m sighing with you Daryl π
The new palette docking/minimising is cool though – it obviates the need for a second monitor with Photoshop. I use mine now just for Bridge.
Chris – Thanks for the comment. I am aware that Photoshop supports two processors, but I inferred [from benchmark results] that two was the limit. Tom’s Hardware benchmarking of the Core 2 Quadro (4-core Kentsfield) in September showed only a small improvement using the Photoshop CS2 benchmark when comparing the Quadro to the fastest Duo. Numerous other benchmarks, including Adobe Premier 2.0, enjoyed an almost 2X improvement, as would be expected with a jump from two to four processors (if all were supported).
So multiple yes, but does that mean more than two?
Multiple means "however many you’ve got". (although CS2 couldn’t go beyond 8 cores on Windows due to some problems with the Windows CPU detection API). We don’t intentionally limit the number of cores used unless there is something about the algorithm that doesn’t scale correctly with more cores (doesn’t happen often).
If you run something bandwidth limited – then you may not see much benefit from added processors. And most of the common operations in Photoshop are bandwidth limited. You have to run something more compute limited (lighting effects, radial blur, or median) to see a real speedup with additional processors. Premiere uses additional processors to pre-decode the video sooner, so it can get a little more speedup with additional cores… until they have to start waiting on the disk again. But Photoshop already has the image in memory, or is waiting on the scratch disks — so it can’t benefit that way (no expensive decoding needed).
Unless the CPU makers add more bandwith in and out of the chip, then you will get diminishing returns with added processors (even for compute limited tasks).
When they get to 8 cores per chip, it’ll be painfully obvious that they are starving the cores for data. Even 4 cores per chip is starting to show the problem for a lot of tasks.
I’ve just printed a $20 memo! Anyone have any idea why CS3 is changing the default printer in windows? I’ve just noticed that when I select a printer in cs3 it makes it the default printer for all of the other apps….I’ve just printed my email to an Epson 4800! On a related problem the driver settings for my printers gets reset by CS3 after each job?!?!
Man…that’s gotta hurt…we have to charge $10.00 per linear foot just to make our ink and paper cost on that machine…($800.00 just to re-ink the thing!)
As mentioned in the CS3 beta forum (where you should be posting this): it’s a bug.
I’ve posted the bugs in the lab forum. But people should definitely beware of some things with CS3 before they install the beta.
I cannot use even the old Bridge to open anything in CS2 after installing CS3. I can run CS2 then do a file open. But this limits my batch workflow where I utilize the bridge.
Some people have had beta serial number installations which then stops running CS3 after 2 days. And if you cannot open anything in CS2 using Bridge 1, this could be a problem.
And then some people have had major issues uninstalling CS3 which could potentially be a HUGE issue if you fall into either of the first two categories.
This beta program is a LOT different than lightroom. Lightroom was a new program. If it did not work for you, so what, oh well. But when CS3 does not work, it may not let you use your working CS2 functionality anymore. So the beta issues here are a LOT more risky. So please beware.
As far as the new feature set goes, I think that it is going to turn out great. There are some useful features for me. I think that the Bridge will turn out to be a big improvement over an already indispensable tool for me. However, right now it is unusable for me because the preview window shows through to my desktop. So I cannot see ANY previews. Camera RAW could also turn out to be even better than it is today. The fill light and especially the recovery sliders are awesome. However, if Adobe does not put back the "auto" check-boxes for each of the (at least previous generation) sliders then there is going to be mass mutiny from many of us. I am not sure who would have approved taking away this functionality, but it can dramatically take away from some users’ working functional workflow.
I think that the new version will end up being outstanding and I’d be happy to use the beta if I can enter a serial number and if my old Bridge 1 and CS2 functionality remained whilst I was running CS3 Beta. But I would strongly caution anyone from installing this version of the Beta until Adobe can guarantee that it can be uninstalled without consequence and can coexist with CS2 and Bridge without a loss of functionality in CS2, or you have a test box to install it on. I really do not think it should have been released prior sufficient testing to determine the impact on existing functionality of the previous release.
Valid points and important to post them here too!
(Not many people can be bothered to look in the Labs CS3 forum on Cold Fusion even if they have CS3 installed, let alone if they haven’t!)
Afterthought: Maybe the Beta install dialog should include the option not to modify file associations.
On Tue, 19 Dec 2006 03:58:31 -0800, wrote:
I’ve posted the bugs in the lab forum. But people should definitely beware of some things with CS3 before they install the beta.
I cannot use even the old Bridge to open anything in CS2 after installing CS3. I can run CS2 then do a file open. But this limits my batch workflow where I utilize the bridge.
You can go into preferences on bridge and reset the file type association to CS2. A pain, for sure, but you get your old bridge back and the new bridge still works with CS3.
As mentioned in the CS3 beta forum (where you should be posting this
If Adobe had wanted responses to their beta, they should have put the forum on the Adobe side forums, not the Macromedia forums that we (most of us) hate and refuse to use.
My home computer would lock up IE6 everytime I tried to go there … so I gave up on it.
My PSCS2 Bridge installation still works fine and opens pix in PSCS2, despite having the CS3 Beta installed. However, CS3 did change my Windows File Association for PSD files, but I rarely if ever open photos for editing from Windows Explorer.
And also as usual…Adobe continues to ignore the merits of enhancing their GUI with customizable toolbars/button-bars that can be enabled/disabled in accordance with a user’s desire for such a feature. ~sigh~
Agreed. We’re still left without Photoshop image thumbnails in Windows browsers and customizable toolbars are not part of Adobe’s design philosophy. I wonder if they think we should also go out and buy one-button mice?
Russell
You can go into preferences on bridge and reset the file type association to CS2. A pain, for sure, but you get your old bridge back and the new bridge still works with CS3
No, even this does not work. Bridge1 ignores these settings and still opens up CS3! How does something like this happen, even in Beta?
I think that there is no alternative for me other than to uninstall CS3 until a new release is made that addresses this issue. Hopefully, I will be able to uninstall without problems…
OK, I was annoyed before. But now I am really PISSED OFF. CS3 will not uninstall. I ran the uninstaller and checked to remove everything. It appeared to uninstall perfectly, but even after a reboot CS3 is still there and Bridge1 still opens up CS3 even though the preferences are set to open CS2.
Adobe, please remove the current beta from being downloadable to any new suckers who you want to do your Alpha, not public Beta, testing!
This version is obviously NOT ready for any sort of public beta testing if CS2 cannot function as it did and if CS3 cannot be properly uninstalled.
Or, Adobe how about screening the beta testers to make sure they know what they are doing and understand what Beta means.
Mike, if you don’t want problems to deal with don’t install beta software.
Robert
On Wed, 20 Dec 2006 04:16:49 -0800, wrote:
You can go into preferences on bridge and reset the file type association to CS2. A pain, for sure, but you get your old bridge back and the new bridge still works with CS3
No, even this does not work. Bridge1 ignores these settings and still opens up CS3! How does something like this happen, even in Beta?
It doesn’t happen that way for me. I just read the FAQ and followed the instructions and I can use both CS2 and CS3 and their respective bridges.
I think that there is no alternative for me other than to uninstall CS3 until a new release is made that addresses this issue. Hopefully, I will be able to uninstall without problems…
No problems on my computer with both programs installed. I can use either one, and when I click an image in Bridge 1, it opens in CS2. So far, I can’t find any bugs in CS3.
I updated my drivers the other day though, the only change I made, and CS2 needed to be reactivated. (I didn’t upgrade the BIOS, just the VIA chip drivers for my hard drives). I still hate the way I seem to be able to lose my activation so easily.
I can use both CS2 and CS3 – and their proper Bridge associations.
CS2 uses 1.04.6. No problem.
CS3 uses 2.0. Some problem with layered tiffs.
I made no changes in preferences or any other settings. They just run separately (as advertised).
Very funny Robert barnett. Please buy a clue. Before I started my own company and started using Photoshop daily, I was responsible for all aspects of software development (among other aspects) for software actively used by well over 500,000 people. So I know exactly what BETA means. If you want to redefine it, please elaborate. I would never had implemented a "public" Beta program where I suspected that functionality would have been broken in the live release for beta testers of a new release. A public beta for a new application should NOT produce bugs for existing applications. Case closed.
I am perfectly willing to to work through bugs on the new software as a beta user. But by your assumption, Adobe could release beta software that could wipe out someone’s operating system and you would say "oh well, what do you expect from beta software, if you didn’t want bugs, don’t install it". So unless you know something about software development, please refrain from slamming people with issues.
After going through the uninstall again, there was one item that was not uninstalled. I clicked it, Adobe Fonts, and it uninstalled it and CS3 and Bridge2. But then when I ran Bridge 1, I no longer had "tools<photoshop" available. The CS3 uninstaller removed this functionality entirely! I had to reinstall CS2, Bridge1 and all of its updates and manualy reinstall the multi-processor support in order to regain functionality.
Subsequently, on the beta forum, someone pointed out part in the FAQ about loosing the ability to open files in CS2 after installing CS3.
So the fact that I had this issue and others have reported that they did not is unconsequential. The fact is by Adobe’s own FAQ, it is a known issue that some users will face. So unless the posters who say that everything is OK can identify what specificaly causes this issue, my point about there being some risk that people should consider regarding this matter is still significant regardless of how many people’s systems it works for.
Sounds as if the machine you are running the Beta on is a mess.
Often happens with software developers and self-declared experts.
On Sun, 24 Dec 2006 09:30:29 -0800,
thought it was important to mention:
Very funny Robert barnett. Please buy a clue. Before I started my own company and started using Photoshop daily, I was responsible for all aspects of software development (among other aspects) for software actively used by well over 500,000 people. So I know exactly what BETA means. If you want to redefine it, please elaborate. I would never had implemented a "public" Beta program where I suspected that functionality would have been broken in the live release for beta testers of a new release. A public beta for a new application should NOT produce bugs for existing applications. Case closed.
Wow, Mike – I guess this is your first time ever testing *Adobe* beta software…<VBG> I can’t remember a version since 6 that didn’t go from troubled beta to dodgy version X.0 – usually they get it right around x.0.5, or at least tolerable. But this beastie is a different breed altogether.
I am perfectly willing to to work through bugs on the new software as a beta user. But by your assumption, Adobe could release beta software that could wipe out someone’s operating system and you would say "oh well, what do you expect from beta software, if you didn’t want bugs, don’t install it". So unless you know something about software development, please refrain from slamming people with issues.
Well you accurately described *my* CS3 beta experience. Thank God I do this often and have invested in a large USB External, Acronis and an Acronis Boot disk. I installed CS3 on a machine that has been stabile and clean for 8 months after a rebuild and used it approximately 5 – 7 minutes. I rebooted the machine once and it never came back. Thank the computer gods for a good backup system, I was back in business again after reimaging the system volume without CS3.
After going through the uninstall again, there was one item that was not uninstalled. I clicked it, Adobe Fonts, and it uninstalled it and CS3 and Bridge2. But then when I ran Bridge 1, I no longer had "tools<photoshop" available. The CS3 uninstaller removed this functionality entirely! I had to reinstall CS2, Bridge1 and all of its updates and manualy reinstall the multi-processor support in order to regain functionality.
Subsequently, on the beta forum, someone pointed out part in the FAQ about loosing the ability to open files in CS2 after installing CS3.
So the fact that I had this issue and others have reported that they did not is unconsequential. The fact is by Adobe’s own FAQ, it is a known issue that some users will face. So unless the posters who say that everything is OK can identify what specificaly causes this issue, my point about there being some risk that people should consider regarding this matter is still significant regardless of how many people’s systems it works for.
Again, what you describe is completely within S.O.P. for an Adobe Beta, right down to the shrugged shoulders and finger pointing to video drivers or ‘it’s just *your* machine. That’s one of the reasons I get mostof my info from the NAPP forums – you might want to check them out if your a member, or become one if you’re not. They really fill in the support gaps for Adobe users.
:subdude
P.S. – I’m sure Chris Cox will repudiate everything I just said, but I don’t hold it against him; it *is* a large part of his job and he’s one of the few staff that seem to actually care what the end user experience is. That doesn’t change the fact that I run most of what he says through my CBS <Corporate-Line Bull Shit> filters first. Nothing personal Chris <G>…
Some people on the beta have experienced that. Others have not. That’s a situation that was revealed by the beta — i.e., that’s what a beta is for. I’d rather have that brought out by the beta so it can be fixed than have it in the release version. In a closed beta, the odds are that the participants are a select group with very carefully tuned computers, who may not experience problems that occur when a wider variety of users with less carefully tuned computers are let loose. That’s why a relatively open beta is a good thing.
Often happens with software developers and self-declared experts.
you’ve been peeking at my hard drive john!!!
dave – software developer and self-declared expert
One MAJOR problem with CS-3 beta that is known, and stated up front by Adobe and it is doubtful will be fixed.
;(
It requires a CS-2 serial number so I can’t try it on one of my CS-1 machines.
Bill, who headed to the download page when he first saw the note.
PS: I DO know what beta means (why on just the older machine).
Actually, you only need a CS2 serial number to use it for the full beta period. Without one you get a two day trial.
THANK you!
I skipped the CS-2 upgrade as I overlooked the HDR information. Without knowing that, for me – the only useful part was the ACR evolution. As a non-professional… well I don’t do photography as a full time profession. The cost was steep for just ACR.
With what appears to be several "levels" of Photoshop possibly in CS-3, it looks like I better bite the bullet & upgrade to full complete Photoshop CS-2 while it is available.
Bill, starting saving up and once the ColorVision Spyder2Pro is paid off….
