richard_george_herrmann

Edge, I approve! Works great! For an quick compare, I set the home page to Photo.net for the three browsers on I have installed on Windows 10. Loaded up Task Manager to check out memory use from a cold boot allocated to the browsers. Edge is small at 20 MB versus IE at 164 MB and Firefox around 140MB. Likely the higher mem usage is from Flash content in the ads. Plus legacy bloat in the old browser code found in IE/Firefox. I imported my favorites from IE and have made the switch over to Edge. This plus the return of re-sizable windows (no full screen by default on modern apps) should assist the migration to Windows 10.

Installed CS5 from DVD media to a Windows 10 test box with no other Adobe software previously installed. Setup prompts for serial numbers and Adobe login. Runs to completion with all side apps like Bridge getting installed correctly. Photoshop (32 and 64) versions installed. Seems to run fine with default bits under Windows 10 However when you go to Update the suite, things get complicated. Adobe Application Manager fails even if I run it under Administrator mode. Shows all items needing an update. Works through list, then says contact Adobe. You know what their answer will be, upgrade to CC 2015. Maybe if you installed and updated CS5 on a previous Windows version (7/8), then upgraded to Windows 10?

Upgraded from Windows 8.1 Pro on a recent X99-A build to the released build version 10.0.10240 The 8.1 install was previously activated with a valid PID. An upgrade in place will not prompt for the PID. Booting from install media will prompt. After a seamless upgrade in place, Adobe Creative Cloud desktop manager needed an update. Which in turn provided updates to Photoshop and Lightroom. If you want to upgrade now, visit the Windows 10 Media Creation page at Microsoft. Choose correct tool (32 or 64 bit), download, run, and select Update this PC. http://www.microsoft.com/en-us/software-download/windows10 Please upgrade ASAP when ready and share your experiences with the group.

What you are asking for is a SOC custom made for image processing like Nikon's family of a System On a Chip for all in-camera operations. http://en.wikipedia.org/wiki/Expeed Its very low power but does little more than simple image processing including some simple sharpening, resizing, and file format conversions from .RAW to .JPG. All in hardware, all really fast, and at hopefully low enough power so battery life is good enough. Not sure who fabricates them, but it is not Nikon in house. They specify features and requirements, possibly do the design in house, or just pass it off to the fabricators to do it all. SOC's need massive scale to earn back the R&D to bring to market. Do any camera companies see a market for a specialized machine? Maybe an AC power adapter, external monitor hooked up to the camera itself, and the next generation of in camera SOC. Ask for support some off camera UI and Tools suited for your needs. The new Raspberry Pi 2 could be used if one wanted to take the business risk and build a specialized image editing box. http://www.tomshardware.com/news/raspberry-pi-2-launches-35,28485.html This looks do-able from off the shelf software wise. It lacks the image specific hardware assist you can get from mini-ITX + PCIex16 GPU.

Sounds like a business opportunity for enterprising boutique custom builders to target the emerging small ITX format MB: http://www.asus.com/Motherboards/P8H77I/ GPU: http://www.asus.com/Graphics_Cards/GTX970DCMOC4GD5/ Select LGA 1155 processor, DDR3 memory and some SSD drives Install into mobile chassis with handle: http://www.lian-li.com/en/dt_portfolio/pc-tu100/ Would this be small enough?

Hyper threading makes one physical core appear as two logical cores for an OS to run separate threads. For example, Lightroom uses threading for simple things like File..Export. Lightroom fires up a worker thread to open the .RAW file, read the contents, apply settings from the catalog, create the export file, write the cooked contents to the export file, close the source and the export file. Easy for threading to perform since its a serialized workflow with OS managed thread safe objects. Hyper-threading is made for this type of multi-threading. Works great! Photoshop works directly with the CPU, the RAM, and optionally the GPU to do complex operations that need exclusive access. These operations are handled directly by Adobe. They have to manage access since the OS cannot easily make direct hardware access thread safe. Without processor affinity, multiple thread code could result in race conditions or getting locked out entirely waiting on another thread fighting over the same resources with hyper-threading. Adobe avoids resource conflicts making their code thread safe manually. One core, one system RAM memory window, one gpu working with its RAM and cores, all working in cooperation in a single worker thread. Does this help answer the "why" they are different? I use too many run-on sentences :)

To be more specific, Photoshop creates threads using something called Processor affinity to tie work to a single processor core. http://en.wikipedia.org/wiki/Processor_affinity Apps that use simpler threading techniques create threads and let the OS manage multi-processing via Hyper-threading. Kinda off topic, but the OP is looking for a machine to run Photoshop CS6. I'd bite the bullet and upgrade to Photoshop CC due to OpenCL detection problems.

Photoshop uses all available physical cores. Lightroom uses all available logical cores via Hyper-threading. The white paper discusses why they use different methods. Lightroom uses some assist, or at least reports their existence in the System Information dump. Here is the results from Lightroom 5.7 Help...System Information and scroll to the bottom of the report CardID: 4480 Direct2DEnabled: false GPUDevice: D3D MaxTexture2DSize: 8192 OGLEnabled: true Renderer: NVIDIA GeForce GTX 680 ShaderModel: 11.1 Vendor: Nvidia VendorID: 4318 Version: 10de:1180:26803842:00a1

Upgraded to Photoshop CC edition. OpenCL is now enabled I encourage ALL users of CS6 to check their OpenCL in Photoshop's System Information results. Not some third party tool, but the System Information tool in PS itself. It's Adobe's test that is failing to detect OpenCL The bug effects both AMD and NVidia hardware on Windows 7 and Windows 8. Adobe's fix is in the CC edition, so unless you are running it, you have no hardware assist via OpenCL

Did anyone read the white paper from Adobe? Its goes into great detail on hardware requirements. For this discussion, Photoshop is similar enough to Lightroom in regards to hardware acceleration technologies exposed via OpenGL, OpenCL, and CUDA. To get the most of a computer system, the white paper goes further into why stand alone PCIE x16 graphics adapters are the right choice. Look at the section called "Photoshop CC Basic System Requirements" to see what Adobe recommends. Its the minimum, so when on a budget, it will be good enough.

As per the Adobe white paper Choose more physical cores versus a faster processor with less cores when picking CPU. More RAM is always better in both the computer and the graphics. Fill up all the RAM DIMM slots with matching RAM for best performance. With Photoshop, it suggests 8GB as the sweet spot for computer ram. Unless you have a brand preference AMD versus NVidia, go with what has more video RAM on the card. Finally the OS and Apps should be on a dedicated SSD. Data should be on a separate drive. How you setup that different drive is up to you. A simple file system is ok, but Adobe suggests a RAID array for best performance

How much is an HP Z820 with 512GB RAM spread across 16 DIMM's with a max'ed out core Xenon CPU? Remember the RAM is also the more expensive ECC type because its a WS grade MB paired with Xenon family processor. Plus 32GB per DIMM! The water cooled triple GPU kit from Evga seems like a good match for the above box. Or just go nuts with the WS grade GPU's like the Quadro family in a multi-GPU setup.

The white paper is full of the good stuff for those that really care about system performance with current Adobe Creative Cloud offerings. Especially if you go with a custom build either from the recommended HP and Mac offerings mentioned in the paper, other big box makers, boutique third party assemblers, or the DIY route. Apple OS and Windows PC requirements are covered in great detail. Especially what actions benefit from the hardware assist via OpenCL versus just raw CPU like encoding conversions. It is worth a read!

My system reports that its Windows NT Version 6.2 with OpenCL unavailable. Wrong and sucks that OpenCL hardware assist is turned off. Windows 8.1 x64 with latest GTX 680 drivers from NVida with all the optional drivers loaded like 3D Vision. I spend most of my time in Lightroom, so I missed this problem with my rig up until now. Do you users of CC on Windows 8.1 get the right information from System Information? Do you users of CS6 report the same with your Windows 8.1 system as me? The Windows Compatibility Tool tells me that CS6 is incompatible with Windows 8.1 and forwards me to Adobe to buy CC.

http://www.adobe.com/content/dam/Adobe/en/products/creativesuite/production/cs6/pdfs/adobe-hardware-performance-whitepaper.pdf Did not see it on photo.net, so I opened a thread to get comments from the community.