Subject: General Tech | October 1, 2014 - 08:07 PM | Scott Michaud
Tagged: Adobe, photoshop, cloud
The Creative Cloud subscription service from Adobe allows users to pay a monthly fee to have access to one or every available product. This ranges from Photoshop, to Illustrator, to After Effects, to Audition, to Dreamweaver. This one subscription follows you, via your Adobe account, through every platform... that they support. Currently, that's Mac and Windows.
To expand that, they are now experimenting with a streaming service, bringing Photoshop to Chrome.
How it works is simple: send Currently, it is limited to Google Chrome on Windows and ChromeOS. Also, the servers do not currently support GPU-acceleration, but Adobe has already announced plans for that in the future. I assume that when this is a consumer product, or shortly thereafter, it will be a fully-featured application. Who knows, maybe they will even bring the rest of their products there? "Streaming access to Photoshop with other products coming soon" ...
People may remember that I was very much against services like OnLive and Gaikai. These do the same thing as Adobe, but for video games. Being an outspoken (to the say least) supporter of art, I found this to be an unacceptable sacrifice for intrinsically valuable content. It is a terrible idea to allow a service to pull your content and replace it, especially for scholarly review in the future.
This is different. While I would always prefer a local application, and would be upset if they stopped offering those, I do not mind having a utility be served from a virtualized instance. If I was working on serious, trade-secret-level content, then I would want to avoid it. On the other hand, getting it to work in one web browser might encourage them to bring the service to all browsers.
From there, Linux and other platforms might just have a valid way to access Adobe's Suite.
Subject: Editorial, General Tech | May 14, 2014 - 09:56 PM | Scott Michaud
Tagged: ultraviolet, mozilla, DRM, Adobe Access, Adobe
Needless to say, DRM is a controversial topic and I am clearly against it. I do not blame Mozilla. The non-profit organization responsible for Firefox knew that they could not oppose Chrome, IE, and Safari while being a consumer software provider. I do not even blame Apple, Google, and Microsoft for their decisions, either. This problem is much bigger and it comes down to a total misunderstanding of basic mathematics (albeit at a ridiculously abstract and applied level).
Simply put, piracy figures are meaningless. They are a measure of how many people use content without paying (assuming they are even accurate). You know what is more useful? Sales figures. Piracy figures are measurements, dependent variables, and so is revenue. Measurements cannot influence other measurements. Specifically, measurements cannot influence anything because they are, themselves, the result of influences. That is what "a measure" is.
Implementing DRM is not a measurement, however. It is a controllable action whose influence can be recorded. If you implement DRM and your sales go down, it hurt you. You may notice piracy figures decline. However, you should be too busy to care because you should be spending your time trying to undo the damage you did to your sales! Why are you looking at piracy figures when you're bleeding money?
I have yet to see a DRM implementation that correlated with an increase in sales. I have, however, seen some which correlate to a massive decrease.
The thing is, Netflix might know that and I am pretty sure that some of the web browser companies know that. They do not necessarily want to implement DRM. What they want is content and, surprise, the people who are in charge of the content are definitely not enlightened to that logic. I am not even sure if they realize that the reason why content is pirated before their release dates is because they are not leaked by end users.
But whatever. Technical companies, who want that content available on their products, are stuck finding a way to appease those content companies in a way that damages their users and shrinks their potential market the least. For Mozilla, this means keeping as much open as possible.
Since they do not have existing relationships with Hollywood, Adobe Access will be the actual method of displaying the video. They are clear to note that this only applies to video. They believe their existing relationships in text, images, and games will prevent the disease from spreading. This is basically a plug-in architecture with a sandbox that is open source and as strict as possible.
This sandbox is intended to prevent a security vulnerability from having access to the host system, give a method of controlling the DRM's performance if it hitches, and not allow the DRM to query the machine for authentication. The last part is something they wanted to highlight, because it shows their effort to protect the privacy of their users. They also imply a method for users to opt-out but did not go into specifics.
As an aside, Adobe will support their Access DRM software on Windows, Mac, and Linux. Mozilla is pushing hard for Android and Firefox OS, too. According to Adobe, Access DRM is certified for use with Ultraviolet content.
I accept Mozilla's decision to join everyone else but I am sad that it came to this. I can think of only two reasons for including DRM: for legal (felony) "protection" under the DMCA or to make content companies feel better while they slowly sink their own ships chasing after numbers which have nothing to do with profits or revenue.
Ultimately, though, they made a compromise. That is always how we stumble and fall down slippery slopes. I am disappointed but I cannot suggest a better option.
Subject: General Tech, Graphics Cards, Processors, Shows and Expos | April 8, 2014 - 03:43 PM | Scott Michaud
Tagged: Intel, NAB, NAB 14, iris pro, Adobe, premiere pro, Adobe CC
When Adobe started to GPU-accelerate their applications beyond OpenGL, it started with NVIDIA and its CUDA platform. After some period of time, they started to integrate OpenCL support and bring AMD into the fold. At first, it was limited to a couple of Apple laptops but has since expanded to include several GPUs on both OSX and Windows. Since then, Adobe switched to a subscription-based release system and has published updates on a more rapid schedule. The next update of Adobe Premiere Pro CC will bring OpenCL to Intel Iris Pro iGPUs.
Of course, they specifically mentioned Adobe Premiere Pro CC which suggests that Photoshop CC users might be coming later. The press release does suggest that the update will affect both Mac and Windows versions of Adobe Premiere Pro CC, however, so at least platforms will not be divided. Well, that is, if you find a Windows machine with Iris Pro graphics. They do exist...
A release date has not been announced for this software upgrade.
Subject: General Tech, Graphics Cards, Processors | February 5, 2014 - 02:08 AM | Scott Michaud
Tagged: photoshop, opencl, Adobe
Adobe has recently enhanced Photoshop CC to accelerate certain filters via OpenCL. AMD contacted NitroWare with this information and claims of 11-fold performance increases with "Smart Sharpen" on Kaveri, specifically. The computer hardware site decided to test these claims on a Radeon HD 7850 using the test metrics that AMD provided them.
Sure enough, he noticed a 16-fold gain in performance. Without OpenCL, the filter's loading bar was on screen for over ten seconds; with it enabled, there was no bar.
Dominic from NitroWare is careful to note that an HD 7850 is significantly higher performance than an APU (barring some weird scenario involving memory transfers or something). This might mark the beginning of Adobe's road to sensible heterogeneous computing outside of video transcoding. Of course, this will also be exciting for AMD. While they cannot keep up with Intel, thread per thread, they are still a heavyweight in terms of total performance. With Photoshop, people might actually notice it.
Subject: General Tech | June 20, 2013 - 02:03 PM | Ken Addison
Tagged: video, podcast, 780m, frame rating, nvidia, kepler, xbox one, Adobe, CC, opencl
PC Perspective Podcast #256 - 06/20/2013
Join us this week as we discuss Mobile Frame Rating, NVIDIA licensing Kepler, Xbox One DRM and more!
The URL for the podcast is: http://pcper.com/podcast - Share with your friends!
- iTunes - Subscribe to the podcast directly through the Store
- RSS - Subscribe through your regular RSS reader
- MP3 - Direct download link to the MP3 file
Hosts: Ryan Shrout, Josh Walrath, Allyn Malventano and Morry Teitelman
Program length: 1:33:43
Week in Review:
0:01:55 NVIDIA GeForce GTX 780M Testing
News items of interest:
0:43:30 Ryan's summary of E3
Oculus 1080p, Razer Blade, Monoprice, SHIELD
1:11:40 Steam might allow shared games?
1:22:00 Hardware/Software Picks of the Week:
1-888-38-PCPER or email@example.com
Subject: General Tech | June 20, 2013 - 02:00 PM | Jeremy Hellstrom
Tagged: Adobe, oops, SaaS
The initial outcry from users of Adobe's Creative Suite because of their move to providing only Software as a Service was mostly ignored by Adobe. The 10% decline in sales and 66.8% decline in profit for Q2 of this year compared to last year is a little harder to ignore however and shows just how upset Adobe's customers were with this decision. The Register reports that most customers were upset by the licensing fees which essentially force them to constantly pay Adobe instead of purchasing a product as a one time expense and skipping a few generations of software before purchasing a new Creative Suite. The solution Adobe has offered is to perpetually sell and support the last boxed edition, Creative Suite 6 ... and there was some rejoicing.
"Adobe dropped the D-bomb during a Q2 conference call with analysts after admitting some customers are "disappointed" it decided to murder future copies of its boxed Creative Suite.
Clearly top brass at the company were living in er…cloud cuckoo land when they revealed last month that future Creative Suite versions would only be web-based, a move that went down badly with some channel partners and their customers."
Here is some more Tech News from around the web:
- Nvidia Shield gets a price cut ahead of 27 June release date @ The Inquirer
- Sneaky Seagate slips 'world's fastest' enterprise disk mutant into the wild @ The Register
- PC makers REALLY need Windows 8.1 to walk on water - but guess what? @ The Register
- Windows RT facing pressure from being isolated @ DigiTimes
- PBX blade for multiple extension home telephony @ Hack a Day
OpenCL Support in a Meaningful Way
Adobe had OpenCL support since last year. You would never benefit from its inclusion unless you ran one of two AMD mobility chips under Mac OSX Lion, but it was there. Creative Cloud, predictably, furthers this trend with additional GPGPU support for applications like Photoshop and Premiere Pro.
This leads to some interesting points:
- How OpenCL is changing the landscape between Intel and AMD
- What GPU support is curiously absent from Adobe CC for one reason or another
- Which GPUs are supported despite not... existing, officially.
This should be very big news for our readers who do production work whether professional or for a hobby. If not, how about a little information about certain GPUs that are designed to compete with the GeForce 700-series?
Subject: General Tech, Graphics Cards | April 5, 2013 - 11:48 AM | Ryan Shrout
Tagged: premiere pro, opencl, firepro, amd, Adobe
As we prepare for the NAB show (National Association of Broadcasters) this week, AMD and Adobe have released a fairly substantial news release concerning the future of Premiere Pro, Adobe's flagship professional video editing suite.
Earlier today Adobe revealed some of its next generation professional video and audio products, including the next version of Adobe® Premiere Pro. Basically Adobe is giving users a sneak peek at the new features coming to the next versions of its software. And we’ve decided to give you a sneak peek too, providing a look at how the next version of Premiere Pro performs when accelerated by AMD FirePro™ 3D workstation graphics and OpenCL™ versus Nvidia Quadro workstation graphics and CUDA.
This will be the first time that OpenCL is used as the primary rendering engine for Premiere and is something that AMD has been hoping to see for many years. Previous versions of the software integrated support for NVIDIA's CUDA GPGPU programming models and the revolution of the Mercury Playback Engine was truly industry changing for video production. However, because it was using CUDA, AMD users were left out of these performance improvements in favor of the proprietary NVIDIA software solution.
Adobe's next version of Premiere Pro (though we aren't told when that will be released) switches from CUDA to OpenCL and the performance of the AMD GCN architecture is being shown off by AMD today.
Using 4K TIFF 24-bit sequence content, Microsoft Windows® 7 64-bit, Intel Xeon E5530 @ 2.40 GHZ and 12GB system memory, AMD compared several FirePro graphics cards (using OpenCL) against NVIDIA Quadro options (using CUDA). Idealy we would like to see some OpenCL NVIDIA benchmarks as well, but I assume we'll have to wait to test that here at PC Perspective.
AMD also claims that by utilizing OpenCL rather than CUDA, the AMD FirePro GPUs are running at a lower utilization, opening up more graphics processing power for other applications and development work.
While this performance testing is conducted on a pre-release version of the next Adobe Premiere Pro, we’re really pleased with the results. As with all of the professional applications we support, we’ll continue to make driver optimizations for Adobe Premiere Pro that can only help to improve the overall user experience and application performance. So if you’re considering a GPU upgrade as part of your transition to the next version of Adobe Premiere Pro, definitely consider taking a look at AMD FirePro™ 3D workstation graphics cards.
You can continue on to read the full press release from AMD and Adobe on the collaboration or check out the complete blog post posted on AMD.com.
Subject: General Tech | February 21, 2013 - 12:27 PM | Jeremy Hellstrom
"Mozilla's Firefox web browser now includes a built-in PDF viewer - allowing users to bin plugins from Adobe and other developers.
Here is some more Tech News from around the web:
- Seagate joins OpenStack foundation and Open Compute Project @ The Register
- BlackBerry squashes W-TIFF-F bug that's ripe for malware squirters @ The Register
- Nikon D7100 hands-on preview @ Hardware.info
- Giveaway at Rbmods together with Cm Storm
Subject: General Tech, Graphics Cards | May 19, 2012 - 03:27 AM | Scott Michaud
Tagged: Adobe, CS6, gpgpu
Last month, SemiAccurate reported that Adobe Creative Suite 6 would be programmed around OpenCL which would allow any GPU to accelerate your work. Adobe now claims that OpenCL would only accelerate the HD6750M and the HD6770M running on OSX Lion with 1GB of vRAM on a MacBook Pro at least for the time being at least for Adobe Premiere Pro.
Does it aggravate you when something takes a while or stutters when you know a part of your PC is just idle?
Adobe has been increasingly moving to take advantage of the graphics processor available in your computer to benefit the professional behind the keyboard, mouse, or tablet. CS 5.5 pushed several of their applications on to the CUDA platform. End-users claim that Adobe sold them out for NVIDIA but that just seems unlikely and unlike either company. My prediction is and always was more that NVIDIA parachuted in some engineers to Adobe and their help was limited to CUDA.
Creative Suite 6 further suggests that I was correct as Adobe has gone back and re-authored much of those features in OpenCL.
Isn't it somewhat ironic that insanity is a symptom of mercury poisoning?
AMD as a hatter!
CS6 will not execute on just any old GPU now despite the wider availability of OpenCL relative to the somewhat NVIDIA proprietary CUDA. While the CUDA whitelist currently extends to 22 Windows NVIDIA GPUs and 3 Mac OSX NVIDIA GPUs current OpenCL support is limited to a pair of AMD-based OSX Lion mobile GPUs: the 6750M and the 6770M.
It would not surprise me if other GPUs would accelerate CS6 if manually added to a whitelist. Adobe probably is very conservative with what components they add to the whitelist in an effort to reduce support costs. That does not mean that you will see benefits even if you trick Adobe into accepting hardware acceleration though.
It appears as if Adobe is working towards using the most open and broad standards -- they just are doing it at their own pace this time. This release was obviously paced for Apple support.