Photoshop CS2 - Blowing scans up with as little loss of quality as possible

What's the best way to make a file that you can blow up into a big poster, say 10 by 20 feet, for example, without the image being too blurry?
I plan to scan in some drawings I did on 8.5x11", colour them in Photoshop CS2, and then make a file so that you can print it out as a big poster, like the 10 by 20 feet example above. I would like the printout to be sharp (as little loss of quality as possible).
What's the best way to do this?
Which dpi should I scan the pictures in, so I can blow them up big?
Which file type should I save the working file, and the file I'm going to print them out?
Please advise. Thank you.

What are your specifics (how high is the resolution of the scans, how many pixels do you have in the image you want to print)?
There are some tools out there for doing just that kind of thing, but you have to realize that there are limits - no software yet can invent detail where none exists.
Starting with very CLEAN image information, a product called Perfect Resize (which used to be called Genuine Fractals) is pretty good at this, as it finds "edges" in the image and tries to preserve them.  I have a beautiful 24 x 30 inch print I made from an old Canon D30 capture (just 3 megapixels) upsampled with Perfect Resize and it stands up even to close inspection.
But the good news is that people don't usually scrutinize giant prints from too closely.  A rule of thumb is that viewing distance will typically be no closer than about the long dimension of the image (e.g., 20 feet in your case).
OnOne Software has a trial version of Perfect Resize available (chances are you'll only need the standard edition).  Alternatively, if you'd like to post a small part of an image you're considering blowing up, I'll be happy to run it through Perfect Resize and post the result so you can see.  Here's a small example using one of my own images:
Original:
Upsampled 400% in each dimension (this forum software may mess up the display but you should be able to copy and paste it into Photoshop or a viewer app):
-Noel

Similar Messages

  • Photoshop CS2 crashes when importing with Mustek A3 scanner

    First off, yes, I know I have an old version of Photoshop. When I got my new Macbook a year or 2 ago I was only able to scan via TWAIN using Photoshop CS2, and it has been the best way.
    However, lately the scanning has been buggy. I've had no problems using PS as a whole, but sometimes when I got to Import < ScanExpress A3 USB 1200 Pro it'll scan halfway and crash, or the program will just outright crash. Today I've spent about 2 hours just trying to scan one image. It managed to work once, and now it crashes every time I try scanning.
    These are the specs of what I'm using:
    Mac OSX 10.6.7
    Photoshop CS2
    Mustek ScanExpress A3 USB Pro
    Any help is appreciated. I need to use this scanner daily for work - If I can't get these images scanned then I don't get paid!
    EDIT: Here's the crash report I get.
    Process:         Adobe Photoshop CS2 [313]
    Path:            /Applications/Adobe Photoshop CS2/Adobe Photoshop CS2.app/Contents/MacOS/Adobe Photoshop CS2
    Identifier:      com.adobe.Photoshop
    Version:         9.0 (9.0x196) (9.0)
    Code Type:       PPC (Translated)
    Parent Process:  launchd [85]
    Date/Time:       2012-11-07 17:38:12.325 -0500
    OS Version:      Mac OS X 10.6.7 (10J4139)
    Report Version:  6
    Interval Since Last Report:          669489 sec
    Crashes Since Last Report:           19
    Per-App Interval Since Last Report:  514085 sec
    Per-App Crashes Since Last Report:   18
    Anonymous UUID:                      FF05BC6E-BF99-4005-853D-2B2516CC35D4
    Exception Type:  EXC_CRASH (SIGILL)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
    0   libSystem.B.dylib                  0x8023950a __pthread_kill + 10
    1   libSystem.B.dylib                  0x80238dab pthread_kill + 95
    2   com.adobe.Photoshop                0xb80f5a71 gettimeofday_wrapper + 37593
    3   ???                                0x3756eb8f 0 + 928443279
    Thread 1:
    0   libSystem.B.dylib                  0x801430ba mach_msg_trap + 10
    1   libSystem.B.dylib                  0x80143827 mach_msg + 68
    2   com.adobe.Photoshop                0xb819440f CallPPCFunctionAtAddressInt + 206231
    3   libSystem.B.dylib                  0x80170819 _pthread_start + 345
    4   libSystem.B.dylib                  0x8017069e thread_start + 34
    Thread 2:
    0   com.adobe.Photoshop                0xb815acc0 spin_lock_wrapper + 90152
    1   com.adobe.Photoshop                0xb8179c5b CallPPCFunctionAtAddressInt + 97763
    2   com.adobe.Photoshop                0xb80c6b13 0xb8000000 + 813843
    3   com.adobe.Photoshop                0xb80c0037 0xb8000000 + 786487
    4   com.adobe.Photoshop                0xb80dd8e8 0xb8000000 + 907496
    5   com.adobe.Photoshop                0xb8145397 spin_lock_wrapper + 1791
    6   com.adobe.Photoshop                0xb801ceb7 0xb8000000 + 118455
    Thread 3:
    0   com.adobe.Photoshop                0xb815a8ff spin_lock_wrapper + 89191
    1   com.adobe.Photoshop                0xb8176e5d CallPPCFunctionAtAddressInt + 85989
    2   com.adobe.Photoshop                0xb80c6b13 0xb8000000 + 813843
    3   com.adobe.Photoshop                0xb80c0037 0xb8000000 + 786487
    4   com.adobe.Photoshop                0xb80dd8e8 0xb8000000 + 907496
    5   com.adobe.Photoshop                0xb8145397 spin_lock_wrapper + 1791
    6   com.adobe.Photoshop                0xb801ceb7 0xb8000000 + 118455
    Thread 4:
    0   com.adobe.Photoshop                0xb815a8ff spin_lock_wrapper + 89191
    1   com.adobe.Photoshop                0xb8176e5d CallPPCFunctionAtAddressInt + 85989
    2   com.adobe.Photoshop                0xb80e88cb 0xb8000000 + 952523
    3   ???                                0x8b65b3f2 0 + 2338698226
    Thread 5:
    0   com.adobe.Photoshop                0xb815aa8b spin_lock_wrapper + 89587
    1   com.adobe.Photoshop                0xb818c3eb CallPPCFunctionAtAddressInt + 173427
    2   com.adobe.Photoshop                0xb818eeec CallPPCFunctionAtAddressInt + 184436
    3   com.adobe.Photoshop                0xb80e88cb 0xb8000000 + 952523
    4   ???                                0x8aace226 0 + 2326585894
    Thread 6:
    0   com.adobe.Photoshop                0xb815a8ff spin_lock_wrapper + 89191
    1   com.adobe.Photoshop                0xb8176e5d CallPPCFunctionAtAddressInt + 85989
    2   com.adobe.Photoshop                0xb80e88cb 0xb8000000 + 952523
    3   ???                                0x8b65b3f2 0 + 2338698226
    Thread 7:
    0   com.adobe.Photoshop                0xb815a8ff spin_lock_wrapper + 89191
    1   com.adobe.Photoshop                0xb8176e5d CallPPCFunctionAtAddressInt + 85989
    2   com.adobe.Photoshop                0xb80e88cb 0xb8000000 + 952523
    3   ???                                0x8b65b3f2 0 + 2338698226
    Thread 8:
    0   com.adobe.Photoshop                0xb815a8ff spin_lock_wrapper + 89191
    1   com.adobe.Photoshop                0xb8176e5d CallPPCFunctionAtAddressInt + 85989
    2   com.adobe.Photoshop                0xb80e88cb 0xb8000000 + 952523
    3   ???                                0x8b65b3f2 0 + 2338698226
    Thread 9:
    0   com.adobe.Photoshop                0xb815a8ff spin_lock_wrapper + 89191
    1   com.adobe.Photoshop                0xb8176e5d CallPPCFunctionAtAddressInt + 85989
    2   com.adobe.Photoshop                0xb80e88cb 0xb8000000 + 952523
    3   ???                                0x8b65b3f2 0 + 2338698226
    Thread 10:
    0   com.adobe.Photoshop                0xb815a8ff spin_lock_wrapper + 89191
    1   com.adobe.Photoshop                0xb8176e5d CallPPCFunctionAtAddressInt + 85989
    2   com.adobe.Photoshop                0xb80e88cb 0xb8000000 + 952523
    3   ???                                0x8b65b3f2 0 + 2338698226
    Thread 11:
    0   com.adobe.Photoshop                0xb815a8ff spin_lock_wrapper + 89191
    1   com.adobe.Photoshop                0xb8176e5d CallPPCFunctionAtAddressInt + 85989
    2   com.adobe.Photoshop                0xb80e88cb 0xb8000000 + 952523
    3   ???                                0x8b65b3f2 0 + 2338698226
    Thread 12:
    0   com.adobe.Photoshop                0xb815a8ff spin_lock_wrapper + 89191
    1   com.adobe.Photoshop                0xb8176e5d CallPPCFunctionAtAddressInt + 85989
    2   com.adobe.Photoshop                0xb80e88cb 0xb8000000 + 952523
    3   ???                                0x8b65b3f2 0 + 2338698226
    Thread 13:
    0   com.adobe.Photoshop                0xb815a8ff spin_lock_wrapper + 89191
    1   com.adobe.Photoshop                0xb8176e5d CallPPCFunctionAtAddressInt + 85989
    2   com.adobe.Photoshop                0xb80c6b13 0xb8000000 + 813843
    3   com.adobe.Photoshop                0xb80c0037 0xb8000000 + 786487
    4   com.adobe.Photoshop                0xb80dd8e8 0xb8000000 + 907496
    5   com.adobe.Photoshop                0xb8145c1d spin_lock_wrapper + 3973
    6   com.adobe.Photoshop                0xb801ceb7 0xb8000000 + 118455
    Thread 14:
    0   com.adobe.Photoshop                0xb815a8ff spin_lock_wrapper + 89191
    1   com.adobe.Photoshop                0xb8176e5d CallPPCFunctionAtAddressInt + 85989
    2   com.adobe.Photoshop                0xb80c6b13 0xb8000000 + 813843
    3   com.adobe.Photoshop                0xb80c0037 0xb8000000 + 786487
    4   com.adobe.Photoshop                0xb80dd8e8 0xb8000000 + 907496
    5   com.adobe.Photoshop                0xb8145c1d spin_lock_wrapper + 3973
    6   com.adobe.Photoshop                0xb801ceb7 0xb8000000 + 118455
    Thread 15:
    0   com.adobe.Photoshop                0xb815a8ff spin_lock_wrapper + 89191
    1   com.adobe.Photoshop                0xb8176e5d CallPPCFunctionAtAddressInt + 85989
    2   com.adobe.Photoshop                0xb80c6b13 0xb8000000 + 813843
    3   com.adobe.Photoshop                0xb80c0037 0xb8000000 + 786487
    4   com.adobe.Photoshop                0xb80dd8e8 0xb8000000 + 907496
    5   com.adobe.Photoshop                0xb8145c1d spin_lock_wrapper + 3973
    6   com.adobe.Photoshop                0xb801ceb7 0xb8000000 + 118455
    Thread 16:
    0   com.adobe.Photoshop                0xb815a8ff spin_lock_wrapper + 89191
    1   com.adobe.Photoshop                0xb8176e5d CallPPCFunctionAtAddressInt + 85989
    2   com.adobe.Photoshop                0xb80c6b13 0xb8000000 + 813843
    3   com.adobe.Photoshop                0xb80c0037 0xb8000000 + 786487
    4   com.adobe.Photoshop                0xb80dd8e8 0xb8000000 + 907496
    5   com.adobe.Photoshop                0xb8145397 spin_lock_wrapper + 1791
    6   com.adobe.Photoshop                0xb801ceb7 0xb8000000 + 118455
    Thread 17:
    0   com.adobe.Photoshop                0xb815a93a spin_lock_wrapper + 89250
    1   com.adobe.Photoshop                0xb8176f67 CallPPCFunctionAtAddressInt + 86255
    2   com.adobe.Photoshop                0xb80e88cb 0xb8000000 + 952523
    3   ???                                0x8baa523e 0 + 2343195198
    Thread 18:
    0   com.adobe.Photoshop                0xb815a8ff spin_lock_wrapper + 89191
    1   com.adobe.Photoshop                0xb8176e5d CallPPCFunctionAtAddressInt + 85989
    2   com.adobe.Photoshop                0xb80e88cb 0xb8000000 + 952523
    3   ???                                0x8b65b3f2 0 + 2338698226
    Thread 19:
    0   com.adobe.Photoshop                0xb815a8ff spin_lock_wrapper + 89191
    1   com.adobe.Photoshop                0xb8176e5d CallPPCFunctionAtAddressInt + 85989
    2   com.adobe.Photoshop                0xb80e88cb 0xb8000000 + 952523
    3   ???                                0x8b65b3f2 0 + 2338698226
    Thread 20:
    0   com.adobe.Photoshop                0xb815a8ff spin_lock_wrapper + 89191
    1   com.adobe.Photoshop                0xb8176e5d CallPPCFunctionAtAddressInt + 85989
    2   com.adobe.Photoshop                0xb80e88cb 0xb8000000 + 952523
    3   ???                                0x8b65b3f2 0 + 2338698226
    Thread 21:
    0   com.adobe.Photoshop                0xb815a8ff spin_lock_wrapper + 89191
    1   com.adobe.Photoshop                0xb8176e5d CallPPCFunctionAtAddressInt + 85989
    2   com.adobe.Photoshop                0xb80e88cb 0xb8000000 + 952523
    3   ???                                0x8b65b3f2 0 + 2338698226
    Thread 0 crashed with X86 Thread State (32-bit):
    eax: 0x00000000  ebx: 0x802fc540  ecx: 0xb7fffa6c  edx: 0x8023950a
    edi: 0xb81f8714  esi: 0x00000004  ebp: 0xb7fffa98  esp: 0xb7fffa6c
    ss: 0x00000023  efl: 0x00000286  eip: 0x8023950a   cs: 0x0000000b
    ds: 0x00000023   es: 0x00000023   fs: 0x00000000   gs: 0x0000000f
    cr2: 0x80239500
    Binary Images:
    0x80000000 - 0x8005dff7  com.apple.framework.IOKit 2.0 (???) <4389DF74-E070-C787-4EC1-7754B5AE19B3> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x8007d000 - 0x800e7fe7  libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <411D87F4-B7E1-44EB-F201-F8B4F9227213> /usr/lib/libstdc++.6.dylib
    0x80142000 - 0x802e9ff7  libSystem.B.dylib 125.2.10 (compatibility 1.0.0) <D9530E9D-E14D-96B0-DCCE-448AD081D61C> /usr/lib/libSystem.B.dylib
    0x8036b000 - 0x804e6fe7  com.apple.CoreFoundation 6.6.4 (550.42) <BA29C5CE-77DB-87DB-5B74-9EEFF5265681> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x805de000 - 0x805ecfe7  libz.1.dylib 1.2.3 (compatibility 1.0.0) <E1B922F4-23DC-467E-631F-7E1B9C9F51CB> /usr/lib/libz.1.dylib
    0x805f1000 - 0x805fdff7  libkxld.dylib ??? (???) <4088783A-C805-4191-0E77-4D949B48F49D> /usr/lib/system/libkxld.dylib
    0x80601000 - 0x80647ff7  libauto.dylib ??? (???) <7CB1AB76-50A2-8E56-66E4-CF51CA75B177> /usr/lib/libauto.dylib
    0x80654000 - 0x807d6fe7  libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <9F0FEEDC-A79D-86D2-D937-C4EC2A39C224> /usr/lib/libicucore.A.dylib
    0x80838000 - 0x808e5fe7  libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <F237B77D-75A3-7240-931D-4735B91D365F> /usr/lib/libobjc.A.dylib
    0x808f9000 - 0x808fcfe7  libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <1622A54F-1A98-2CBE-B6A4-2122981A500E> /usr/lib/system/libmathCommon.A.dylib
    0x8fe00000 - 0x8fe4163b  dyld 132.1 (???) <67866EA0-11AD-E175-066C-48E996265855> /usr/lib/dyld
    0xb8000000 - 0xb81defff +com.adobe.Photoshop 9.0 (9.0x196) (9.0) <6437A74D-607F-7339-5F7E-F6B0EF81C25D> /Applications/Adobe Photoshop CS2/Adobe Photoshop CS2.app/Contents/MacOS/Adobe Photoshop CS2
    0xffff0000 - 0xffff1fff  libSystem.B.dylib ??? (???) <D9530E9D-E14D-96B0-DCCE-448AD081D61C> /usr/lib/libSystem.B.dylib
    Translated Code Information:
    objc[313]: garbage collection is ON
    NO CRASH REPORT
    Model: MacBookPro8,2, BootROM MBP81.0047.B0E, 4 processors, Intel Core i7, 2 GHz, 4 GB, SMC 1.69f1
    Graphics: AMD Radeon HD 6490M, AMD Radeon HD 6490M, PCIe, 256 MB
    Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 384 MB
    Memory Module: global_name
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 5.100.198.104.3)
    Bluetooth: Version 2.4.5f1, 2 service, 12 devices, 1 incoming serial ports
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: Hitachi HTS545050B9A302, 465.76 GB
    Serial ATA Device: MAT****ADVD-R   UJ-898
    USB Device: FaceTime HD Camera (Built-in), 0x05ac  (Apple Inc.), 0x8509, 0xfa200000 / 3
    USB Device: Hub, 0x0424  (SMSC), 0x2513, 0xfa100000 / 2
    USB Device: Composite Device, 0x055f, 0x040b, 0xfa130000 / 6
    USB Device: Apple Internal Keyboard / Trackpad, 0x05ac  (Apple Inc.), 0x0245, 0xfa120000 / 5
    USB Device: BRCM2070 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0xfa110000 / 4
    USB Device: Bluetooth USB Host Controller, 0x05ac  (Apple Inc.), 0x821a, 0xfa113000 / 8
    USB Device: Hub, 0x0424  (SMSC), 0x2513, 0xfd100000 / 2
    USB Device: IR Receiver, 0x05ac  (Apple Inc.), 0x8242, 0xfd110000 / 3

    Perhaps a full uninstall will help. here is the link to the OSX uninstaller and drivers.
    http://www.mustek.com/mustek/supportdrivers.php?&show=drivers&disp_cat=Scanner&disp_sr=USB %20Port&disp_mod=ScanExpress%20A3%20USB%201200%20Pro&disp_catid=18&disp_srid=31&disp_modid =207
    Then proceed to reinstall the OSX 10.6 driver for that scanner.

  • Photoshop CS2: "file not compatible with this version of Photoshop" error

    So, I've been working with Photoshop for almost 20 years now, and lately I've been getting this error message on occasion (but not on every file) when I go to open a file I worked on just yesterday: "Could not complete your request because the file is not compatible with this version of Photoshop." I just worked on it yesterday in Photoshop. The file was saved as a PSD, and when I attempt to open it through Painter IX, that program tells me that it's not a Photoshop document. Why can't I open this file anymore, and why is it giving me this error message when I don't have Norton AntiVirus installed, and my 'maximize PSD and PSB file compatibility' is set to 'always'??
    Does anyone have an idea on how I can open my file? How can I get around this, and how do I prevent it from happening again?
    OS: OSX 10.4.11
    Photoshop CS2
    Info:
    Kind: Adobe Photoshop file
    Size: 394.4MB
    Created: December 13, 2007
    Modified: Yesterday at 3:54 PM

    This is the boilerplate text I use in connection to saving to a network (please NOTE the part where it explains that normally, it does work, but that it is impossible to troubleshoot someone else's network remotely, and that's why it's not supported by Adobe):
    If you are opening files over a network or saving them to a network server, please
    cease and desist immediately
    in the event you are currently experiencing problems with one or more files.
    Working across a network is not supported.
    See:
    http://www.adobe.com/support/techdocs/322391.html
    Copy the
    CLOSED file from your server to your local hard disk, work on it, save it again to your local hard disk, close it, and copy the closed file back to the server.
    Of course, the fact that Adobe does not support working across a network does not necessarily mean it won't work. It should.
    Adobe's position is that there are too many variables in a network environment for them to guarantee that everything will work correctly in every network, especially given the fact that if something does
    not work properly, it's probably the network's fault, and Adobe has no way of troubleshooting your network.
    If you can't work locally, you are on your own, and if something happens, you're on your own. If you must work from a server, make sure your network administrator is a competent professional.
    When problems arise, a lot of valuable work can be lost.

  • Which Mac should I upgrade to if I am a Photoshop, Illustrator, and Indesign user, with a little iMovie thrown in?

    I've been using a 24" iMac (originally purchased in mid-2006) to do graphic design with Adobe Creative Cloud, primarily Photoshop, Indesign, and Illustrator. I am also starting to do some very ametuer video prep (like iMovie) etc. With just Photoshop and Indesign alone, what is the minimum Mac I should upgrade to, if I am still concerned about performance, but budget and mobility could come into play too? For instance would the 13.3" Mac Book Pro with Intel Graphics be sufficient for doing my usual print design, with a little iMovie thrown in? At that price, I could afford a big display to plug into when I am at my office desk.
    I like the idea of mobility (which I haven't had before with the big iMac), but don't want to notice a horrible lag in performance if I get a weaker machine. The guy at PeachMac said that when it came to display the Retina (in the Macbook Pro, 13.3 in edition) made a high difference despite the lack of a dedicated graphics processor. I don't do heavy-duty, memory-intensive graphics work but about once every two years anyway, and my iMac only has 2GB of RAM to begin with. I just want to make sure that true designers who have switched from older iMac machines to Macbook Pro's (not the most expensive models) didn't regret it when trying to run Photoshop, et al.
    (My absolute budget is "no more than $2,000" which is why I am considering the new iMac vs. the MacBook Pro 13.3" and getting a nice external display.)
    Thanks!

    To run the new Studio you need Leopard and it will not spec'd to run on Tiger (Leopard 10.5.6 [specs here|http://www.apple.com/finalcutstudio/specs>) I have run it in Leopard and Snow Leopard, and both seem fairly similar, though I generally like my Leopard machines a bit more. Still breaking in the Snow Leopard and getting various kinks out of it. It seems I have some more little things go wrong in Snow Leopard.
    Overall I like the upgrades in the Studio and you may just want to make another boot drive with clean Snow Leopard and the new Studio to work with until you feel you are happy with how it is performing. Bascially that is what I do until I am fully comfortable with the system and always have my rollback plan in place in case something goes awry and I need to get things done....

  • Pushing Photoshop CS2 to its limits with ActionScript

    I'm using Photoshop CS2 with Windows XP (lastest SP) and a Core2 4 Gb RAM PC.
    Here's what I did :
    I developped a javascript file for photoshop that opens another (pretty huge) file and reads it line by line and executes line by line.
    This helped me to execute a huge javascript stuff.
    This javascript stuff... generates one of the biggest (if not the biggest) maze in the world.
    But.
    Photoshop "agrees" to create a big file.
    Photoshop "agrees" to draw in it for a lot of times.
    Each 20 draws, Photoshop "agrees" to empy ALL the history (i think this would help to free RAM or whatever).
    After say 80 % of the stuff done, there's an error that pops up.
    This is not a javascript problem, I swear I've been looking for it for months now.
    My generated javascript file is okay.
    You can download the whole stuff here, uncompress it into the Photoshop script folder (usually "C:\Program Files\Adobe\Adobe Photoshop CS2\Paramètres prédéfinis\Scripts") and launch it (via "File=>Scripts=>m")
    What I don't get is :
    - if Photoshop "agrees" to create a big file.
    - if Photoshop "agrees" to draw in it for a lot of times.
    - if each 20 draws, Photoshop "agrees" to empy ALL the history (i think this may help to get RAM)
    why on earth does it stop with a problem that seems to have nothing to do with memory allocation (but it has actually : I've just generated more than 1500 scripts and each time I made the script bigger and launched it : it worked without any problem at all so this is not a problem from my script (I've generated (with my own C program) a BMP file based on that javascript file and it generated the maze properly)).
    I'm pretty convinced this is a problem with Photoshop, and only Photoshop.
    Another problem I had to face that is documented nowhere, even in the JavaScript help file, (I told you I pushed Photoshop to its limits ) is that you are limited to 999 points when you create a path in JavaScript. Why is that ? This is not normal. So I had to modify my entire Javascript program to make it work properly. It has to create paths with 999 pixels, then draw them, clear the path, and son on.
    Please tell me if my script works either with CS4 and / or with Windows Vista.
    My goal is to create something like 15000 x 15000 pixels files (I'm not joking).
    I was counting on Photoshop to use its own swap file and help me to generate mazes bigger than the ones my C program generates. But it can't for now.
    Any help is greatly appreciated.

    Here's what I've just tried : a vbs file that launches photoshop CS2, then executes action "M1" then action "M2"
    Action "M1" executes the JavaScript "M1"
    Action "M2" executes the JavaScript "M2"
    The JavaScript M1 executes 998000 lines
    The JavaScript M1 executes 1000 lines then stops.
    So in essences I should have to :
    (1) launch "M1" that creates the image and then executes 998000 lines
    (2) save the image
    (3) quit photoshop
    (4) re-launch photoshop
    (5) re-load the previously saved image
    (6) launch "M2" that creates the image and then executes 998000 lines
    I'll try that tonight.
    This is far from being easy and nice. I hate when we need hacks to make simple things work
    Anyway here's the source codeto launch Photoshop then the ActionScript M1 then the ActionScript M2 (if it is of any use) :
    REM =======================================================
    DIM objApp
    SET objApp = CreateObject("Photoshop.Application")
    REM Use dialog mode 3 for show no dialogs
    DIM dialogMode
    dialogMode = 3
    DIM id1
    DIM id2
    DIM id3
    DIM id4
    DIM desc1
    DIM ref1
    id1 = objApp.CharIDToTypeID( "Ply " )
    SET desc1 = CreateObject( "Photoshop.ActionDescriptor" )
    id2 = objApp.CharIDToTypeID( "null" )
    SET ref1 = CreateObject( "Photoshop.ActionReference" )
    id3 = objApp.CharIDToTypeID( "Actn" )
    Call ref1.PutName( id3, "M1" )
    id4 = objApp.CharIDToTypeID( "ASet" )
    Call ref1.PutName( id4, "Olivier" )
    Call desc1.PutReference( id2, ref1 )
    Call objApp.ExecuteAction( id1, desc1, dialogMode )
    id1 = objApp.CharIDToTypeID( "Ply " )
    SET desc1 = CreateObject( "Photoshop.ActionDescriptor" )
    id2 = objApp.CharIDToTypeID( "null" )
    SET ref1 = CreateObject( "Photoshop.ActionReference" )
    id3 = objApp.CharIDToTypeID( "Actn" )
    Call ref1.PutName( id3, "M2" )
    id4 = objApp.CharIDToTypeID( "ASet" )
    Call ref1.PutName( id4, "Olivier" )
    Call desc1.PutReference( id2, ref1 )
    Call objApp.ExecuteAction( id1, desc1, dialogMode )

  • How do I get Photoshop CS2 to resume working with Lion upgrade?

    How do I get Photoshop CS2 to resume working now that I have installed Lion upgrade?
    Can I uninstall Lion and get back to a working system?

    RoaringApps Mac OS X Lion Application Compatibility
    Lion App Compatibility Table - RoaringApps
    Using Cloning as a Backup Strategy
    Clone X 4.0
    Carbon Copy Cloner 3.4.1
    How to prepare your Mac for OS X 10.7 Lion
    Upgrading to Mac OS X Lion Protocol

  • Exporting to WMV with a massive loss of quality

    Hi there!
    I've never had an issue with this before, but I need a little expert help on this one.
    I'm trying to export a time line, source of 1280x720, into a WMV file. I've done it before with no issues.
    But now, it seems like when the exporting is done, and I open the file, there is a loss of quality in the beginning. It's odd because, it seems like the video starts off just fine, but then a few seconds in, it degrades. The degragation continues for about 5 seconds, making the image a little blurry, but then it kicks back into the high quality it was. It maintains the high quality for the rest of the sequence.
    What is even odder is that, when I export the individual, 5 second scene that looks degraded in the main file all by itself, it looks just fine.
    I can't help but thing that it's something about it in my sequence that is making it do that. There is no effects or transistions between scenes involved at all.
    Im exporting:
    FORMATL Windows Media
    PRESET: HDTV 720 60 High Quality (thought I have used 30 as well, with the same issue)
    Video settings are
    CODEC: Windows Media Video 9
    Encoding Passes: Two
    Bitrate mode: Variable Constrained
    Framerate: 59.94
    Pixel Aspect: Square Pixels
    Decoder complexitiy: Auto
    Keyframe interval: 5  seconds
    Average video bitrate 5000
    Peak Video bitrate 8000
    peak video buffer size 5
    Thanks in advance for any help!

    Correct, it has its own ways to mess up your video.
    So, you're not helping with the question at all, you're just rallying against YouTube?
    Thanks for your help.
    We had issues like that with 2 Pass VBR. We even dialled in huge data rates which did not fix the issue,m Switching to a CBR profile fixed it "good enough" but not perfect. In our case wmv was demanded by the client (PowerPoint). I concluded the wmv encoder was defective in AME and best avoided.
    Can you use H.264 instead for your purpose?
    Thanks for the suggestion! I just tried H.264 and had the same exact issue, though.
    Since the individual pieces weren't having the problem, I decided to try some tests. Every piece along was fine, except for the "Begin Transmission" part, which still screwed up.
    So, I tried various renderings with and without it, the words, the static...and eventually came to find out that it was the "Static" video that was doing it. I suppose it may have been because that video was originally 640x480, and I just zoomed into it to make it fit the screen. For whatever reason, that was the problem, and when I re-encoded it with the static gone, it worked just fine.
    Thanks for your help, though!

  • Photoshop CS2 is NOT compatible with my MacBook Pro!

    Despite Apple's marketing hype to the contrary, I had the following experience with the CS2 Suite. I loaded it from disks, registered and activated it, and then immediately opened a photo image for editing. I tried to crop the image, and the response was "That operation cannot be completed - Your scratch disks are full." Now, I have ~90GB available on the "scratch disk," so it is NOT full.
    I called Adobe Tech Support. The tech said "CS2 was not really designed to work with the new Intel chips. If it's not working for you, we're sorry, but there's not much you can do about it. No 'patch' or software upgrade is anticipated soon."
    The tech said that he hadn't heard much about this issue; is that for real? Am I having a unique problem for some reason? At least he didn't charge me $39, that's one benefit I can think of. Any hope out there for a solution to this issue from the Apple side?
    17" MacBook Pro   Mac OS X (10.4.6)  

    I just completed a CS 2 project involving both Photoshop and InDesign on my MBP 17 and had only two problems -- InDesign prefs got corrupted. I cleaned them out and then went from there with no problems until I opened a figure in Photoshop -- the program informed me I was missing components and needed to reinstall Photoshop. But it let me edit the file. Once I was done I did a reinstall of CS2 and everything seems to be fine now.
    I have noticed a prevalence for prefs files to get trashed on this machine more so than on my G5 iMac or my PPC PB.
    MBP 17   Mac OS X (10.4.6)   2GB

  • I have Photoshop CS2 vsn 9.0 with the Camera Raw 3.7 update and the Digital Negative Converter.  I cannot open any RAW files. Does the fact that I've opened them in Lightroom 5.0 before make a difference?

    When I try to open the RAW file (CR2) from the Photoshop application or from the Bridge (even while holding down the shift key) I get a message saying it's not the right kind of file. When I try to convert using the converter, it won't recognize the files.

    Which operating system are you using?
    Which camera are the camera raw files from?
    Did you convert the files to dng using lightroom or the standalone dng converter?
    If using the standalone dng converter, which version?
    In the dng converter did you try setting the Compatibility for Camera Raw 2.4 and later
    (Preferences>Compatibility)
    You should also be able to send the files from lightroom to cs2 without converting to dng, either by using Photo>Edit In>Photoshop or setting cs2 as an external editor in the lightroom preferences

  • Photoshop CS2 will not work with RAW images in the Minolta DimAge A2.  It use to work fine

    I have used Photoshop CS 2 with my DimAge A2 for over 5 years in the RAW format.  Now it will not work with RAW with my camera.  I am using Vista 64.Any answers ?  Thanks

    It would seem to me that you have probably had to reinstall Photoshop CS 2.  If that is the case, then you should download and install Camera Raw 3.7.  The version that was on your install disk was updated several times.  And one of those updates probably included support for your camera.  Install ACR 3.7 and see if that helps.

  • Photoshop - Fade is onion ringed with high contrast? - No true fade possible?

    Hi everyone, am I being totally stupid (possible) or can you just not get a true fade on a computer / Photoshop?!
    Any image I take, if I make the contrast high enough, the fade / vignette gets onion ringing. I paint with the most
    blurry brush, I can 'Blur' it ad nauseum, and it doesn't really change it. Is it a mode, I've tried Adobe RGB 98 and
    sRGB. This doesn't seem to be a common problem, but mabye people don't notice it too much? PLEASE HELP!
    Thanks!
    Guy

    What you want to do is work in 16 bits/channel mode.
    With a good monitor and video card, you can see the distinctions between each of the 256 levels of grayscale.  This is also sometimes visible in nearly solid colors as well - such as skies.
    Video cards and monitors generally provide 8 bit/channel color, but they don't always maintain that all the way through.  Better ones do, and now we're starting to see the advent of 10 bit/channel pipelines, though that's not mature.
    What you see on the monitor isn't necessarily what's in the document, especially if you use deep data, as I mentioned above.
    From the sound of things, it seems as though your video card / monitor pipeline isn't providing very high bit depth at some point in the process.  As you were told in another thread (if I recall correctly) a poorly set monitor and a radical profile created by a calibrator to compensate could be involved in this.
    -Noel

  • PhotoShop CS2 and PDF Presets question.

    Hello,
    I have installed the recent free release of Adobe Photoshop CS2 on my Win 8.1 PC.
    I am creating the artwork for a CD Cover, by using a CYMK template from CD-Baby.
    They require that the finished artwork be submitted to them in PDF format, using the [PDF/X-4:2008] preset.
    I found that Photoshop CS2 didn't come with this preset, but after searching the web, I came across this forum whereby a user posted a link to a "JobOptions" archive file at...
         http://dl.dropbox.com/u/16243351/joboptions.rar
    ... I downloaded this RAR file and found that there was a file inside called "x4;2008.joboptions"
    I installed this preset by the 'EDIT/Adobe PDF Presets/' route, and it seemed to successfully install the preset.
    (No errors at least).
    Now when I go to save my finished project as PDF, I am given the choice of...
    * [PDF/X-1a:2001]
    * [PDF/X-3:2002]
    * x4;2008
    (this is the exact description of each preset).
    My only question is, do you think the desired [PDF/X-4:2008] was correctly installed?,
    I'm not sure since the naming format is not exactly the same as the first 2 presets descriptions.
    Thank you.

    thanks for your reply  Mylenium.
    is it possible that this user preset might not exactly conform to the desired preset I'm after?
    is there any way I can get a genuine copy of the factory preset [PDF/X-4:2008]?
    thanks.

  • PhotoShop CS2 crashes at start up

    Hi,
    I've been using PhotoShop CS2 for 4 years with no problems.  I work on Mac OS X 10.4.11. Couple of days ago I tried to open PhotoShop and it crashes at start up, after running the opening script. Recently I installed a new printer, which I removed now. I've done nothing different than that to my system.
    I'm not a technical person but if you please can help with any suggestion, I will follow step by step your instructions.
    Thank you

    Boilerplate-text:
    As with all unexplainable Photoshop-problems you might try trashing the prefs (after making sure all customized presets like Actions, Patterns, Brushes etc. have been saved and making a note of the Preferences you’ve changed) by pressing command-alt-shift on starting the program or starting from a new user-account.
    System Maintenance (repairing permissions, purging PRAM, running cron-scripts, cleaning caches, etc.) might also be beneficial, Onyx has been recommended for such tasks.
    http://www.apple.com/downloads/macosx/system_disk_utilities/onyx.html
    Weeding out bad fonts never seems to be a bad idea, either. (Validate your fonts in Font Book and remove the bad ones.)
    If 3rd party plug-ins are installed try disabling them to verify if one of those may be responsible for the problem.
    Take care with Onyx, though, as you are on a old system!

  • Photoshop CS2  & Catalyst

    I have Photoshop CS2, Does catalyst works with the cs2 files?

    We don't support CS2 files, but it might work.
    Thanks,
    Winsha

  • How to import B & W from Photoshop CS2

    Hi, I'm new to this forum, so be gentle! <g>
    I'm trying to make a slideshow, mixing color and black-and-white images. All of these images are scanned, from prints or slides. The b&w images are then converted from 16-bit RGB to 8-bit grayscale, then edited in Photoshop CS2, then imported into iPhoto.
    (Just as a sidenote of possibly dubious relevance, the color images begin digital life as 16-bit, the grayscale as 8-bit.)
    These images look fine as 8-bit grayscale images in CS2, but when I import them into iPhoto, either in a batch, or individually, they show up as black rectangles. If I click on the rectangle, I see a negative of my image.
    This used to work ok, before I upgraded both to CS2 and iPhoto 6. How can I get this to work again?
    I have both a 15-inch G4 Powerbook, and a dual 2.7 GHz G5 PowerMac, running the current system and the same version of all software. The PB has 2 GB of RAM, the tower 3.5 GB.

    Hi! Thanx for your response.
    It is not clear that he has imported it as wmv or pdf, but the slideshow has to be imported in such a manner that it can still be edited (Captions, effects etc.)
    Creating a wmv or pdf will not allow the same.
    Any Ideas?

Maybe you are looking for

  • Syndicating based on Addition of a Remote System Key

    Hi We have a distributed system syndication scenario where we need to syndicate a record automatically when a remote system key is added to an existing harmonized record in MDM. By adding the Remote System Key, it essentially means the remote system

  • Hard-drive seems to be constantly in use?

    Hello, I've recently bought the Lenovo Idea Centre K430 and while I have been very pleased with it to date I've noticed that the white hard-drive light on the top of the box is constantly flashing even if I'm not doing much with the computer and I wa

  • RFC destination names and logical names

    Hi, I have an RFC connection set up in the DBCON table. Is there any way to test these connections? I tried using SM59 but I couldnt match the RFC destinations in SM59 with the connection names in DBCON? Any help will be appriciated. Thanks, Praveen

  • Cheque Printing issue incase of Vendor advance payments

    Hi all,      We are doing vendor payments using F-58 and printing cheque from there itself, and in case of advance payments we are using F-48 for payments and to print cheque we are using FBZ5.       When we take printout from FBZ5 for advance paymen

  • Problems when editing videos in IOS 8.02

    I recorded a slowmotion video with a moving train the other day; but when I wanted to edit it, I couldn't like I used to. I wanted to cut the first seconds out because of shaking image, but when I tried doing that, it also cut the ending; I couldn't