<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Adobe Blogs</title>
<link>http://blogs.adobe.com/</link>
<description></description>
<lastBuildDate>Sat, 04 Jul 2009 00:40:03 +0000</lastBuildDate>
<pubDate>Sat, 04 Jul 2009 00:40:03 +0000</pubDate>
<generator>http://www.movabletype.org/?v=3.38</generator>
<docs>http://blogs.law.harvard.edu/tech/rss</docs> 

<item>
<title>PS User Group San Jose to meet July 14</title>
<dc:creator>John Nack</dc:creator>
<description><![CDATA[<p>The next meeting of the San Jose Photoshop User Group is scheduled for July 14.  Group organizer Dan Clark writes,</p>

<p><blockquote>Photoshop questions? Samples of your Photoshop work? Bring either to our next meeting. We'll have an evening of Photoshop show and tell, as well as answers to your questions. Let's see some tough questions and nice work! Please send questions and sample files ahead of time to: dan at weinberg-clark.com</p>

<p></blockquote>For complete info &amp; directions, <a href="http://www.evite.com/pages/invite/viewInvite.jsp?inviteId=ANFUFOLNIZZFTPXNHZAT&li=iq&src=email&trk=aei6">check out the event page</a>.</p>]]></description>
<link>http://blogs.adobe.com/jnack/2009/07/ps_user_group_san_jose_to_meet_july_14.html</link>
<guid isPermaLink="true">http://blogs.adobe.com/jnack/2009/07/ps_user_group_san_jose_to_meet_july_14.html</guid>
<category></category>
<pubDate>Fri, 03 Jul 2009 15:27:57 -0800</pubDate>
</item>
<item>
<title>Notes about PS printing performance</title>
<dc:creator>John Nack</dc:creator>
<description><![CDATA[<p>Recently an iMac user asked about ways to speed up large scan & print jobs in Photoshop:</p>

<blockquote>In your opinion, would a Mac Pro significantly accelerate the processing [while printing]? Is the printing engine in Photoshop multiprocessor aware?</blockquote>

<p>I put the question to Photoshop printing engineer Dave Polaschek, and here's his reply:</p>

<blockquote>While Photoshop's printing code isn't multi-threaded & is mostly disk-bound*, another core may be used by the OS for color management if you're printing in "Printer Manages Color" mode. More cores won't hurt.

<p>That said, the disk (or better, disks) in a Mac Pro are significantly faster than the disk in an iMac, which will help since every printed job is spooled to disk. Plus you can put more RAM in a Mac Pro, which will help in preparing the image for printing.</p>

<p>As with most things in Photoshop, the two biggest gains you can get in speed are:</p>

<p>1 - Put in as much RAM as you can afford and the machine can hold. When friends are buying new Macs, I tell them they should have an absolute minimum of 1G of RAM per core, and 2G per core will still be a noticeable improvement over that. For running Photoshop with big images, I've found some operations which run over 10x faster since I moved from 4GB to 8GB of RAM in my quad-core Mac Pro just because it keeps all the images and intermediate data in memory.</p>

<p>2 - Put in the fastest disk (or RAID array - four 500GB disks in a RAID array are cheaper and faster than a 2TB disk, and the default controller in my Mac Pro could do RAID with no new hardware) you can afford after you're done buying RAM. When we do have to read or save a file, or spool something to disk, that fast disk will mean less time spent looking at progress bars.</blockquote></p>

<p>[Question via Colin Smith]</p>

<p><i>* In other words, the speed of printing depends on how quickly data can be moved to/from your hard drive.</i></p>]]></description>
<link>http://blogs.adobe.com/jnack/2009/07/notes_about_photoshop_printing_performance.html</link>
<guid isPermaLink="true">http://blogs.adobe.com/jnack/2009/07/notes_about_photoshop_printing_performance.html</guid>
<category></category>
<pubDate>Fri, 03 Jul 2009 07:34:11 -0800</pubDate>
</item>
<item>
<title>Masking Multiple Layers</title>
<dc:creator>Julieanne Kost</dc:creator>
<description><![CDATA[<p>Not only are Layer Groups great for organizing your layers, you can also use them to mask the contents of multiple layers at a time. With the Group targeted in the Layers panel, click the Add Pixel (or Vector) Mask icon from the Masks panel. This mask will control the visibility of all layers within the Group. </p>]]></description>
<link>http://blogs.adobe.com/jkost/2009/07/masking_multiple_layers.html</link>
<guid isPermaLink="true">http://blogs.adobe.com/jkost/2009/07/masking_multiple_layers.html</guid>
<category></category>
<pubDate>Fri, 03 Jul 2009 06:04:21 -0800</pubDate>
</item>
<item>
<title>CS4 @ the FCP Supermeet London &amp; Nehalem Power!</title>
<dc:creator>Jason Levine</dc:creator>
<description><![CDATA[<p>Hello, my friends! I'm just back from my brief tour in the UK, and this time the focus was around Universities, broadcast and industry clientel, and a special appearance at the FCPUG Supermeet in London, reprising my performance from the 'meet' in Vegas during NAB. </p>

<p>This time around, my colleague Michael O'Neill joined me at the event, and I took the stage in the early evening to an enthusiastic capacity crowd.  As in Vegas, the session was titled <em>Sharing the Love - FCP & CS4</em>, and I did indeed share it 'round, getting some great responses from the crowd. </p>

<p><strong><em>My intro slide, snapped by Michael from the audience</em></strong><br />
<img alt="FromTheCrowd-Web.jpg" src="http://blogs.adobe.com/jlevmedia/FromTheCrowd-Web.jpg" width="520" height="339" /></p>

<p><strong><em>Just about to begin, standing on stage, snapping with the iPhone</em></strong><br />
<img alt="FCPUG-LondonPanoWeb.jpg" src="http://blogs.adobe.com/jlevmedia/FCPUG-LondonPanoWeb.jpg" width="520" height="195" /></p>

<p>Prior to the Supermeet, Michael and I spent several days visiting Universities in the South of England, focusing on workflow and integration between CS4 and FCP, as well as Avid Media Composer integration and even mentions of incorporating ProTools into a CS4 project.  What was especially cool about these visits is that we got a chance to show-off performance from the latest MacBookPro 8GB laptops, as well as the newest Intel Nehalem Workstation (similar to the one I used at LLB a few months back).  Once again, the Nehalem processor continues to WOW people (even primarily Mac-based set-ups) and in conjunction with the supah-speedy MBP 17", it's a true one-two performance punch, for both online and offline production. </p>

<p>And, in case you thought that Universities still have basic 'Broadcast Journalism' majors (well, I 'sort of' though that!) here's a list of what you might be studying at Falmouth U.  Where was this stuff when *I* was in school? ;)</p>

<p><a href="http://blogs.adobe.com/jlevmedia/FalmoutUniv.html" onclick="window.open('http://blogs.adobe.com/jlevmedia/FalmoutUniv.html','popup','width=520,height=726,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false">Falmouth University Media Degree Programs</a></p>

<p>With that, my friends, I'm going back to the studio to 'shed' and work on some new materials for upcoming Adobe TV episodes.  I've also got a few musical creations in the works, so perhaps I'll post some 'in-progress' versions, if anyone has any desire to hear them.  And, since a few people asked where they can get a 'proper headshot', here's the one I used at the SuperMeet (and will likely update my Twitter account with).  </p>

<p><strong><em>Healing People Daily, with my hair down...;)</em></strong><br />
<img alt="JaseHeadshot09.jpg" src="http://blogs.adobe.com/jlevmedia/JaseHeadshot09.jpg" width="520" height="408" /></p>

<p>Until next time, </p>

<p>Blog on.<br />
</p>]]></description>
<link>http://blogs.adobe.com/jlevmedia/2009/07/cs4_the_fcp_supermeet_london_n.html</link>
<guid isPermaLink="true">http://blogs.adobe.com/jlevmedia/2009/07/cs4_the_fcp_supermeet_london_n.html</guid>
<category>General</category>
<pubDate>Thu, 02 Jul 2009 12:53:21 -0800</pubDate>
</item>
<item>
<title>Tips to reduce editing time for Captivate movies</title>
<dc:creator>Nandini Gupta</dc:creator>
<description><![CDATA[<p>Anyone who creates computer-based tutorials for a client knows the kind of effort that goes into applying a consistent style, in on-screen text as well as visuals. If you are using Captivate to create these tutorials, there are many ways you can reduce post-production editing time.</p>

<p>One of the least-known ways is perhaps the way to <em>change the default captions added by Captivate </em>for various actions you record. </p><p>Let’s say the default caption for clicking a menu is “Select the <menu_name> menu” and the style mandated by your client is “Click <menu_name>”. Instead of editing the captions after you complete recording, you can minimize your editing time by editing the template file from which Captivate sources the default captions.<br />
This file is CaptureTextTemplates_English.rdl, and can be found in your Captivate installation. Open the file in any text editor (wouldn’t it be wonderful if you could edit this file from within Captivate?) and modify the captions as you wish. Save and start recording.<br />
The Captivate team shares many smart tips and tricks on their blog. Here are some of my favorites:<br />
<em>How to create training and assessment modules from one Captivate project</em><br />
<a href="http://blogs.adobe.com/captivate/2009/06/reduce_your_editing_hours_crea.html">http://blogs.adobe.com/captivate/2009/06/reduce_your_editing_hours_crea.html</a></p>

<p><em>How to set default timing and transition properties and use them across slides, projects and sessions</em><br />
<a href="http://blogs.adobe.com/captivate/2009/03/rapid_elearning_authoring_is_t.html">http://blogs.adobe.com/captivate/2009/03/rapid_elearning_authoring_is_t.html</a></p>]]></description>
<link>http://blogs.adobe.com/nandinigupta/2009/07/tips_to_reduce_editing_time_fo.html</link>
<guid isPermaLink="true">http://blogs.adobe.com/nandinigupta/2009/07/tips_to_reduce_editing_time_fo.html</guid>
<category>Captivate</category>
<pubDate>Thu, 02 Jul 2009 11:09:34 +0530</pubDate>
</item>
<item>
<title>Feedback, please: Copying hex values</title>
<dc:creator>John Nack</dc:creator>
<description><![CDATA[<p><a href="http://www.sampottsinc.com/">Designer</a>/Twitter <a href="http://top.sampottsinc.com/">crazy person</a> Sam Potts made what I thought was a good suggestion earlier today:</p>

<p><blockquote>The Copy Color as HTML in the color panel is awesome. Everyone uses it all the time. However, times have changed and my guess is that most of the people who use this are writing their colors in CSS. So you always have to delete the <em>color=""</em> part after you paste it into a style sheet.</p>

<p>It would be awesome to simply have a "Copy Color Hex Code" option and get <em>#CCFF00</em> instead of the full <em>color="#CCFF00"</em> tag.</p>

<p>Or, to cover both bases, add to the panel menu: </p>

<p>Copy Color as HTML ---&gt; <em>color="#CCFF00"</em> as it is now</p>

<p>AND</p>

<p>Copy Color as CSS ---&gt; <em>color:#CCFF00</em></p>

<p></blockquote>I know it's a tweaky query, but if you have a preference, please chime in.</p>]]></description>
<link>http://blogs.adobe.com/jnack/2009/07/feedback_please_copying_hex_values.html</link>
<guid isPermaLink="true">http://blogs.adobe.com/jnack/2009/07/feedback_please_copying_hex_values.html</guid>
<category></category>
<pubDate>Thu, 02 Jul 2009 10:50:41 -0800</pubDate>
</item>
<item>
<title>Copying Merged Layers (and Groups)</title>
<dc:creator>Julieanne Kost</dc:creator>
<description><![CDATA[<p>Copying Merged Layers (and Groups)<br />
Command (Mac) / Control (Win) + Shift + C (with a selection) copies a merged view of all visible layers onto the clipboard.<br />
Option-Command (Mac) / Alt-Control (Win) + Shift +E, pastes a merged copy of all visible layers on a (single) new layer above the topmost currently selected layer.</p>]]></description>
<link>http://blogs.adobe.com/jkost/2009/07/copying_merged_layers_and_grou.html</link>
<guid isPermaLink="true">http://blogs.adobe.com/jkost/2009/07/copying_merged_layers_and_grou.html</guid>
<category></category>
<pubDate>Thu, 02 Jul 2009 07:43:49 -0800</pubDate>
</item>


</channel>
</rss>