PSE 10 Mac - Animation "Bug" Fixed?

PSE 9 returned the ability to create animated gifs for those with Macs. YAYAY!
BUT... the delay didn't work, so it couldn't be changed from .02.
Has this been fixed... yet?
Thanks!

I knew you were going to be the one to answer, Barbara! Thank you!
I found the answer to someone else regarding 9.0, recommending GIFfun. I've downloaded that, and it works.
Adobe has been ignoring this for so long for Mac users, it is very, very disheartening.
Again, thank you for the prompt response, Barbara!

Similar Messages

  • Is PSE 3 (Mac) able to fix skin / flesh tones?

    I have an old photo of my son as a 1 year old. It was taken by one of the major department stores'"professionals". So, those of you familiar with that process of over 20 years ago can guess that the entire, once full-color, picture now has a bluish tint to it.
    I've fooled around with the red, green, blue, increase/decrease with some (limited) success on the entire photo.
    Can anyone suggest how I might make his skin tone (both lit and shadowed skin) look more natural? Using my method in the second paragraph, if he's not blue, he's too red, or green, or yellow - but never natural looking.
    Thanks in advance for any advice.

    In addition to Barbara's excellent suggestions, I offer you a technique which served me well a few weeks ago with a faded photo, which I scanned in order to work on it:
    1. Obtain skin color swatch. I downloaded swatches palette from Adobe Studio Exchange a while back, but cannot find its source at this time. However, you can get RGB & Hexadecimal values here and enter appropriate one for your foreground color
    http://www.retouchpro.com/pages/colors.html
    2. Duplicate your background layer, set blend mode of background copy layer to luminosity, opacity 20-25%. Shut off visibility of background layer by clicking on its eye icon
    3. Select soft paint brush, mode:color, opacity: 100%, may need to reduce same
    4. Zoom way in and paint gingerly on faded areas
    Ken

  • PSE 6 for Mac -- animation not working!

    i've had pse 6 for my mac for a long time, and the animation settings won't work.
    it's been stuck at 0.2 for a while, and i need it faster.
    someone mentioned deleting a cache, how would that be done?
    help? :/

    This is known bug in several versions of PSE for mac, It can't be fixed. I would suggest creating your frames in PSE and download the free GIFFUN from stone.com to combine and animate them.

  • PSE 8 Mac version - Animation Speed settings not working

    I just recently bought PSE 8 Mac version and pretty happy with it, I am having a problem with animation speed, I understand that you have to use the tab key in anination settings to get the speed to opne, but now It will not let me adjust the speed, it is stuck on 0.2 ! does anyone know how to correct this problem, Should I got to adobe with the bug?
    Sure would appreciate some help
    Thank you
    DLBryce

    How big is the file size for the completed gif? Does it display like this in other programs?
    Also, are you sure that it's not affecting the display rate? Remember that .2 second is really fast. Even duping will still leave it going pretty quickly. What puzzles me is that you say it makes no difference at all. If you want a sloow gif, like one where an eye blinks every five seconds or so, you'll need to use something else to create it.

  • Bug fix for Mac book wireless - problem solved!

    Aparantly there is a rather large number of folks out there who've discovered this dillema with wireless not working very well at this point on the Macbook.
    Well, I can attest there is one very good solution out there for this issue. This application called Sonar Theater from www.sunray.tv includes a bug fix for the wireless connection issues with Macbook in their latest 1.5 release of Sonar Theater.
    I downloaded it, put it into my start up folder and waalaa! problem solved. I've haven't any more issues with dropped wireless since - it's been running constantly for over 2 weeks now.
    I haven't even attempted to touch my router configuration - don't need to.

    Welcome to the better life of Macs. I am using Sonar Theater too and it's been working very well for me. In fact, I'm getting hooked on just texting a message to my Mac book to fire up user sessions now. I think if you give the Mac Book some time however, you'll find that there really is no comparison to PC's. Your life overall is going to just keep getting better as you dig in to the resources available to new Mac users.
    I'm sure it seems confusing to PC users at first, but here's how to set up any application as part of your startup sequence. It really is extremely easy and simple compared to the PC world. Oh and by the way, in reality, Mac users refer to this as your login sequence. So, at login time, you can do a multitude of different things for each user account you might want to set up. Naturally, you can choose to share or not share applications and data between these user accounts on your Mac too....
    Mac OS X 10.3 or later
    1. Log in as the user who wishes to have a login item or as an admin user.
    2. Choose System Preferences from the Apple menu.
    3. Choose Accounts from the View menu.
    4. Click the name of the user.
    5. Click the Startup Items button
    6. Click the "Add {+}" button.
    The item you selected will automatically open the next time you log in.
    there are several ways to get good info from the apple community on tips and tricks as well. you should just try the apple os x web site...here,
    http://www.apple.com/macosx/resources/
    happy mac-ing!

  • May Release: New partner support, Infrastructure updates, Site templates and bug fixes

    Link: http://www.businesscatalyst.com/_blog/BC_Blog/post/May-release-New-partner-support-Infrast ructure-updates-Site-templates-and_bug-fixes/
    We are announcing a new Business Catalyst release, scheduled to go live on Thursday, May 3rd. With this release, we are continuing our investments in system performance and stability by increasing our web servers capacity, enabling HTTP acceleration to provide faster site loading times, and improving the site creation speed by using pre-generated sites.
    On the product side, we have completely revamped our partner support workflow taking advantage of the Adobe support infrastructure and tools, enhanced the site templates workflow for partners, and included lots of bug fixes and improvements. Read through the following sections to get detailed information about this release:
    Partner support
    Infrastructure updates
    Features and enhancements
    Issues fixed by this release
    What's next
    You can jump to the corresponding section by clicking the above links.
    Partner support
    Updated Help & Support partner experience
    Following Adobe ID support, we have upgraded BC  support tools (cases, chat, documentation) with standard Adobe tools. As a partner, you can now benefit from the same support tools as the rest of Adobe Creative Suite, and can track your support cases with Adobe BC, Dreamweaver, Muse or Photoshop in a single place.
    Partners with more than 100 paid sites will get 2nd level chat support, which includes a higher priority, by default. If you have more than 100 paid sites, but spread across different Partner Portals, please ask support to enable 2nd level chat for you.
    Support experience for your Small Business owner clients can now be owned by partners (see below).
    Custom Help & Support URL for your clients
    As a partner, you are probably already offering various additional services to your clients besides building & maintaining their BC site. Support, tailored specifically to your client needs, is usually one of these value-added services. We are now enabling you to take your Support service to the next level. In  Partner Portal Settings, you have the option to set a custom URL for what will open when your client clicks on Help & Support inside Admin Console:
    If you have multiple partner accounts, for different verticals, you can specify a Support URL for each of these.
    The default Support experience provided by BC for your clients will be updated in a few releases to be similar to the partner support experience. This includes BC-branded support cases and documentation. If you'd like to keep a white-label experience for your customers, please set your own Help & Support URL in Partner Portal.
    For more details please read the Improved support workflow and new forums announcement on our blog.
    Infrastructure updates
    Between our April release and the following infrastructure updates have been enabled
    Limited trial sites for free partners – starting with our May release, the number of trial sites a Free Partner can have will be limited to 100. Once the limit is reached, Free Partners that need to create a new trial site have the options to upgrade to a higher partner plan, upgrade some of the trial sites to paid or delete unused/expired trials.
    Automatic trial expiry extension - with this release, trial site expiry date will be automatically extended with 30 days every time an admin user logs in  the system through the admin interface or through FTP.
    Installed additional hardware - we have installed additional web servers on all our data centers, that translate into an increase of the existing capacity with over 70%.
    Updated DNS infrastructure - we have improved the DNS resolution for email delivery so that we can increase the rate at which we're sending the system operational emails
    HTTP acceleration – all sites static assets are served from a new cache engine (images, CSS and JavaScript files, together with improved headers that should allow the browser to cache them better for a browsing session). This update has been turned on along with our April release, and has made all the BC sites load faster on first and on subsequent loads.   
    Accelerated site/partner creation – we've changed the way new sites are created for faster speed, pre-creating them and reusing pre-created sites when needed, and have also improved the creation process for new partners, minimizing the impact of new CCM customers on the existing datacenters.
    Adobe ID for partners - in order to support an integrating experience between the various Adobe tools a partner may use (Dreamweaver, Muse, Support forums) we have added Adobe ID support for Business Catalyst partner accounts. Starting April 19, partners are asked to merge their current Business Catalyst account with their Adobe ID accounts. For more details about the transition process and FAQ please read the Introducing Adobe ID blog post.
    Updated Terms of Use - Along with several other changes in our processes in the past few months, we also revamped our Terms of Use and the signature process by requesting every admin user to sign a TOU. We have completed the rollout for partners, and we might be pushing an updated partner Terms of Use version within the following weeks. For more details and questions about this change, read the New Terms of Use for Business Catalyst blog post.
    Features and enhancements
    Site templates
    To support the increasing number of partners building, sharing or reusing  templates to create  new sites, we're extending our site templates support from our partner portal with a new template type and improved  management support. The update is going to enable partners to mark sites as templates and   choose between making them available in Online Business Builder and keeping them private in their partner portal. A template site will not expire and has the same limits as any other trial site.
    Based on your partner level, you can create private or public templates using the Site Details screen or the Tools>My Site Template section from your Partner Portal. Standard partners can only create private templates, while Free Partners can only view site templates that have been transferred to their accounts by other partners.
    The number of templates a partner will have will be limited and will vary based on partner level: free partners can store up to 5 templates in their partner portal, standard partners have up to 100 site templates while Premium Partners might have up to 200 templates. Paid sites marked as templates are not counted against these limits.
    Business Catalyst Partner fixes
    While we are really focused on making the Business Catalyst integration into Creative Cloud a smashing success, we are slowly resuming our efforts to deliver fixes that have been requested by our partners. This release includes the following partner fixes:
    Improved product custom fields - we have increased the maximum number of characters for product custom fields to 1024 (previous limit was 256); this gives partners and customers additional space to use when working with products
    Improved Secure Zone subscribers list - we have added the customer email address in the Secure Zone Subscribers list to enable partners better filter and manage customers
    Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
    Social plugins integration updates
    Starting with our May release, we are updating the social plugins support to require users to get the plugin code from the third party provider and saving into his Business Catalyst website. The module tags and configuration will remain unchanged, but will render an empty tag until the partner or site owner will  update the module template to include the corresponding module code snippet from the third party platform provider.
    For more information about how you can enable the Social Plugins on a Business Catalyst websites, read the Social Media: Integrating Facebook and Twitter knowledge base article.
    Other changes
    Updated weekly emails - Starting with our May release, the information in the site weekly emails has been filtered based on the site's plan. For example, webBasics site reports will no longer include the sales report.
    Localization - we improved and increased the coverage of the admin interface translations into German, French and Japanese
    Site Settings -> Ignored IP addresses has been relocated under Reports -> Visitors -> More.
    BC-Dreamweaver integration performance improvements
    Development Dashboard has been removed, as it didn't provide a clear useful, ongoing benefit. The information present in the development dashboard has been integrated into our new Help & Support section.
    Payment gateway settings - for more privacy and data protection, we have updated the Payment Gateway configuration screens to obfuscate the sensitive login information. Fields that have been obfuscated are now requiring confirmation.
    Report abuse badge on trial sites - for compliance reasons, a "Report Abuse" link has been added to the front-end of all trial sites of free partners that don't have any paid sites. When they click the Report Abuse link, site visitors are redirected to a form submission page on businesscatalyst.com site.
    Issues fixed by May release
    Issues 3051303, 3168786 - Workflow notifications - Fixed a problem preventing workflow notifications emails from being sent.(see get satisfaction forum discussion)
    Issue 3164074 - Fixed a bug causing the lightbox gallery created from Muse to be displayed behind page elements
    Issue 3162810 - Fixed a bug in rendering engine to prevent  content placed between body and head tags being incorrectly moved inside the body tag
    Issue 3166610 - Fixed a broken link to Partner Portal in Internet Explorer
    Issue 3175003 - Fixed an issue that caused an incorrect price display for the Year One-Off Setup Fee when upgrading a site from Admin using CB
    Issue 2567278 - Fixed a bug causing site replication to ignore product attributes
    Issue 2947989 - CRM passwords are now case sensitive
    Issue 2723731 - Removed CSS files from the head section of the Layouts files, when downloaded and opened in Dreamweaver, via the BC extension
    Business Catalyst new admin interface updates
    Added "Save and Add New" button in Web App Item Add & Edit screens (see get satisfaction forum discussion)
    Updated Quick Actions menus to add more actions (see get satisfaction forum discussion)
    Fixed an issue causing Recent items menu to display deleted items (see get satisfaction forum discussion)
    Fixed a display issue on File Manager making top buttons unreachable (see get satisfaction forum discussion)
    Fixed the scrollbars in Email Marketing>Campaign>Stats>Bounced Emails reports (see get satisfaction forum discussion)
    Fixed an issue causing Recent items menu to brake after selecting the current page from the Recent Items menu (see get satisfaction forum discussion)
    Replaced the Success notification displayed when selecting Users or Permissions tabs from User Roles with an Warning
    Change the action label displayed in User Roles list from View to Edit to match the list pattern from Admin Users
    Fixed a missing file JavaScript error occurring when trying to open image manager from product details-> Attributes -> options
    Moved System Emails section from Site Setting to Site Manager (see get satisfaction forum discussion)
    Updated Domain Management interfaces to close the modal window and refresh the domain list after successfully adding a domain
    Fixed an issue preventing the Hyperlink Manager to function properly (see get satisfaction forum discussion)
    Updated the confirmation message received after copying a page to match the new workflow and button names
    Fixed an issue causing the current screen or section to not be highlighted in the menu
    Updated styling on the new dashboard, user management and email accounts interfaces
    Updated  dashboard reports filters and chart display; made the chart and the filter use the site time zone
    Fixed an issue preventing users from inviting new admin users or create new email accounts on Internet Explorer 8
    Fixed an issue preventing users from deleting Email Accounts or Admin Users in Internet Explorer 8
    Fixed some issues preventing password recovery email from being sent
    Removed the alert message displayed when the user or email account limit has been reached
    Added localization for the simplified dashboard
    Fixed display issues for site limits, domains and user list in the simplified dashboard
    Added Custom reports for webBasics plan
    Fixed a bug generating a "500:Collection error" on the simplified dashboard when user did not had View users permission
    Added TOU checkbox in the email account setup screen
    Updated Site Preview link in the dashboard to load the default domain
    Fixed an issue in the new File Manager forcing a user to press Undo twice in order to see the change take effect if the code that was previously formatted contained any <"tag" with more than 2 lines
    Fixed an issue causing the File Manager editor toolbar to incorrectly render if page URL path is longer than certain value; starting with this release, the site URL is trimmed
    Fixed an issue causing the invite users to be displayed as [object Object] in dashboard and admin user list
    Fixed a bug in the new admin causing the interface to become unresponsive when using the browser Back button
    Fixed an issue in the new File Manager causing "Save Draft" button to publish the default page template instead of creating a draft version
    Fixed a broken invite link issue in the Email Account invite email
    Updated loading indicators in File Manager and Email Accounts screens
    What's next
    The first item on the what's next list might not be news for many of you, but it's definitely one of the most important milestones this year. The Creative Cloud launch is just around the corner, and Business Catalyst is playing an important role in that, as the publishing platform for Adobe® Muse and Dreamweaver. This launch will capture all our attention within the next weeks as we want it to be our best ever. 
    We'll start our next development cycle on May 15th, while the next Business Catalyst release is going to be pushed live in mid June. That being said, the following items are already on our launch plan for the next release and a few more will join the list. Please expect an update on our 2012 plans around mid May.
    HTTP throttling – all page load and API calls to BC will be protected against attacks, this might trigger problems for API heavy sites. We are looking into enabling this update along with our June release, and will help make sure that a reasonable number of requests will be accepted from the same computer per minute.
    Automatic site deletion - Starting with the June release, we are going to start automatically delete expired trial sites and canceled sites. Customers will be notified twice before we are going to proceed with deleting the sites.
    Thank you,
    Cristinel Anastasoaie
    Adobe Business Catalyst Product Manager

    In reference to this change in the Custom Reports... Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
    What is the customer confusion we are trying to stop here? I've got even more confused customers at the moment because all of a sudden they can't find the export to excel option but know it exists if they log in on a PC?
    Mark

  • ITunes 11 is a bag of hurt in Snow Leopard (multiple bugs) - Fixes? Workarounds?

    iTunes 11 is a bag of hurt in Snow Leopard (multiple bugs) - Fixes? Workarounds?
    I had been using iTunes 11.0.2 in Snow Leopard 10.6.8 on early 2011 Mac Book Pro. When I went to iTunes store on August 1, it would no longer display the iTunes store, it shows just a blank white screen. Upgrading to the current iTunes 11.0.4 does not help, I still get white screens when I try to go to the iTunes store. If I run iTunes 11.0.2 on a different Lion machine it displays the store just fine.
    Before this crippling issue began, I was having two other problems with iTunes 11.
    1) When I was able and did view app descriptions in the iTunes store, I would try to click on the links for reviews, or related apps, etc, and none of the links worked. This problems also does not occur in Lion.
    2) Also, I really do not like the new app sync buttons, "Remove", "Will Remove", "Update", "Will Update". Sometimes iTunes becomes confused on the state of an app, especially when I sync two devices to have the same apps on each. Also, when I have many apps, its a pain to find and click all the "Update" buttons to make them say "Will Update" as I have to read the buttons closely. There should at least be a way to sort the apps by status so I can see all the ones that say "Update" together.
    I am on Snow Leopard because I have some Mac apps that still require Rosetta and I do not wish to upgrade. However, it seems that even though Apple says iTunes is compatible with Snow Leopard, they are doing a poor job of testing it in Snow Leopard.
    Anyone else seeing these issues with iTunes 11 in Snow Leopard? Any Fixes? Or Workarounds?

    tkoyn wrote:
    2) Also, I really do not like the new app sync buttons, "Remove", "Will Remove", "Update", "Will Update". Sometimes iTunes becomes confused on the state of an app, especially when I sync two devices to have the same apps on each. Also, when I have many apps, its a pain to find and click all the "Update" buttons to make them say "Will Update" as I have to read the buttons closely. There should at least be a way to sort the apps by status so I can see all the ones that say "Update" together.
    You are simply not understanding how app updating works in iTunes 11. Apple has changed it up a bit. When viewing your apps in iTunes, along the top, directly under the LED display click the "updates" tab. This will show you all the apps that have available updates. Then click the "update" button in the lower right of the screen.
    tkoyn wrote:
    1) When I was able and did view app descriptions in the iTunes store, I would try to click on the links for reviews, or related apps, etc, and none of the links worked. This problems also does not occur in Lion.
    This is generally a network issue. As a first trouble shooting step, restart your computer. If that does not work power cycling the internet modem will generally clear up the problem.

  • How long for updates and bug fixes usually?

    I'm new to Logic and even new to Macs. I'm just wondering how long does it usually take for Apple to release bug fixes and updates to Logic?
    Also, how long did Apple take to get around to providing worthwhile updates to Logic 7? Were there substantial updates changed work flow, functionality, etc?
    Basically I'm wondering how long until Logic 8 will be more stable and complete?

    Logic 7 was never updated so as to provide any significant changes in workflow over its initial release. But apparently L7 so intrinsically broken that they abandoned any effort to fix it. Instead, they developed Logic 8.
    L8 has some very obvious bugs, yes. They need to be fixed yesterday. But as usual, Apple is dragging its feet in this regard.
    To your question, how long.... well, L7 updates occurred about every 4 months. There's no telling if they'll be on a more conscientious schedule for releasing L8 updates. They only offer end-users one choice: wait and see what happens.

  • Two bug fixes for DeferredWrite databases

    Hi all,
    If you are using DatabaseConfig.setDeferredWrite(true) to configured a deferred write database, you will be interested in two recent bug fixes. These fixes will be in the next patch release (JE 3.2.69 and later), but we haven't decided when that release will be made. In the mean time, please email me (mark.hayes at the obvious .com) and I'll make these fixes available to you.
    The change log entries for the two bugs are below. Note that first bug can cause data loss, since a log file is incorrectly deleted by the log cleaner.
    # Fix a bug that could cause LogFileNotFoundException when using a Deferred Write database (DatabaseConfig.setDeferrredWrite(true)). The bug could occur when a Deferred Write database was opened sometime after opening the Environment. The bug was very unlikely to occur if all Deferred Write databases were opened immediately after opening the Environment. [#15913]
    # Fix a bug that could cause Database.sync to hang. This bug was introduced in JE 3.2.68. [#15920]
    Thanks to Tyler (user611159) for working with us to diagnose these bugs and verify the fixes. He did many test runs over many days and supplied the log files we used to discover the bugs.
    --mark                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    2. Logic 7.1.1 had an annoying bug in the event list
    where if you selected, for example, four notes in the
    matrix editor, only three would be highlighted in the
    event list until you change their values. This seems
    fixed, too.
    Thanks for mentioning this.
    Would you mind checking something else out? In the attached pic (from 7.1.1) I have 4 notes highlighted in the matrix editor but only 2 are highlighted in the event editor. This correlates more or less with the behavior you reported (3 notes highlighted) and which you say is fixed (and is great news!).
    But notice where the SPL is positioned -- bar 1, beat 1. Yet in the event editor the pointer is aligned with "---Start of List---". In fact, when the sequence is played, the pointer is always aligned one event behind the currently playing event. This behavior has been a real problem.
    So I'm wondering if that specific behavior is fixed in 7.2. Would you mind checking and letting me know if this has been fixed?
    Thanks!
    [Note the pointer in the Event Editor,
    directly below, and what it is
    pointing to at bar 1, beat 1]
    G5, dual 2.7G, 2.5G RAM   Mac OS X (10.4.3)   LP7.1.1, MOTU 424/2408/1224 x 2
    G5, dual 2.7G, 2.5G RAM   Mac OS X (10.4.3)   LP7.1.1, MOTU 424/2408/1224 x 2

  • Using PSE on Mac - when attempting to Edit a file system is saying need Premiere Elements to proceed. Help pls!!

    Using PSE on Mac.  When attempting to Edit a file system advises that requires Premiere Elements.  Help!!!

    Hi Cody
    Sorry to hear about your difficulties.
    It should be very uncommon for Pages to crash. I've been using it for years on a daily basis and it's only happened to me once except when I was trying to replicate a bug for someone.
    Your experience might be a symptom of an underlying problem with your system. I recommend that you back all your stuff up now.
    Whilst trying to isolate the issue, I recommend that you manually create frequent backups of your documents using the Finder after a successful save until you can trust it.
    Next, use disk utility to do a repair permissions on your hard drive.
    Also, after quitting Pages, try trashing your ~/Library/Preferences/com.apple.iWorks.Pages.plist file (back it up first if you want) and restarting Pages.
    If this doesn't work, there are loads of troubleshooting tips here: http://www.thexlab.com/faqs/faqs.html. I also recommend that you read the tips on system maintenance.
    In case you didn't already know this, Pages files are actually packages. Control-click on the icon and select Show Package Contents to see what's inside. You may be able to recover some text from the files in there. I don't believe there are any repair utilities. Nor is the file format available.
    I hope this helps you.

  • Mac quarantine bug returns to Leopard

    In my email today from ITWire:
    *Mac Quarantine Bug Returns in Leopard*
    Mac OS X includes a mechanism that's supposed to warn users before they execute files downloaded from the Internet, but the reappearance in Mac OS X 10.5 Leopard leaves systems vulnerable to Trojan attachments received in Mail.
    The issue was fixed by Security Update 2006-001 for Mac OS X 10.4 ("Download Validation fails to warn about unsafe file types"), but somehow made its way back into the latest version of Apple's operating system.
    http://www.itwire.com/content/view/15458/53/
    comments, please, support staff? Are we getting a security update sometime soon?
    Also, is there anywhere in this forum or a definitive article regarding Macs and infections?
    As far as I know (which ain't too much):
    --Macs are generally invulnerable to viruses but can be inadvertently passed on via email. (Is Mail safer than Outlook or Entourage for Mac, which comes in MS Office for Mac)
    --Viruses are passed on in .exe and other PC-based files.
    --Viruses can't be passed in image files or .pdf files.
    --Viruses cannot launch unless a file is opened.
    --As Macs get more popular, will they be more vulnerable?

    Same issue; I share my Documents folder and everyone can see the folders below it but have NO access ot most of the sub folders (the minus symbol). The one exception is a folder "Civilization IV Demo";
    Permissions:
    Documents (MAIN FOLDER):
    tpfannes(ME) read and write
    everyone read and write
    Sub folders (sub folders under Documents)
    Civilization IV Demo (works):
    tpfannes(ME) read and write
    everyone read only
    staff read only
    Data Folder (No workie)
    tpfannes(ME) read and write
    everyone no access
    I did a erase and install with Leopard and restored the files from a backup using Apples Backup utility.
    I could probably get to a terminal window and modify permissiosn these via. chmod but I'm not all that comfortable with that.
    Any ideas????
    tim

  • FCPX Text Animation Bug

    Hi Everyone!
    I'm working through a 30+ minute video sequence showing photos and video clips of an event I attended recently.  This is my first foray into FCP.
    I've come across a rather weird text animation bug, where text is animated onto the screen incorrectly.
    So what I've shown above is one typical text box I've added for narration, using the "Typewriter" effect.  Of course, the text should render (appear) on screen one character at a time, but I have been getting a random number of characters at the end of the block that do not animate.  The only way I have been able to get these blocks to animate correctly is to add enough spaces to the end of the text to force FCPX to rerender the block correctly.
    At some point in the future, this bug resurfaces, and I have to delete the spaces, and re-add them, to get the block to render and animate correctly once again.
    If I go and "share" the resulting sequence, the bug is rendered into the sequence. 
    Deleting the text block, and adding a new block, doesn't seem to help.
    I have reported this as a bug to Apple.
    It's not just the Typewriter text effect doing this.  As far as I can see, it is every text effect bar the lower thirds (so far as I can see).
    Any ideas on how to get around this?  Does anyone else experience this bug?

    I'm starting to pull my hair out on this one.  My video is essentially ready for final rendering, but I've hit a snag re the rendering itself.
    Check out this image I've just snapped:
    http://www.becsta.com/pics/skitch/FCPvCompressor-20110918-225758.jpg
    On the left is the Compressor 4 preview pane.  Note that the text animations are screwed up, just like the screenshot at the start of this discussion.
    On the right is the FCPX preview pane, showing that the rendering is complete and correct. All I did was select "Send to Compressor", and skipped the Compressor timeline up to review the same frame.
    These text blocks are using the "Typewriter" effect.
    So, what do I do to fix this once and for all?
    Build it from scratch in Motion?
    Any ideas?
    /cue Princess Leia voice/ Help me Obi-Wan Kenobi, you're my only hope!

  • Bug Fix Lament

    Adobe: It does not bode well for Lightroom to have relatively-easy-to-fix bugs persist, release after release.
    I highly recommend finding a way to get more of them out between releases.
    In my opinion, one should almost be able to assume certain bugs are not there since they were reported well in advance of latest release - just like we can assume certain popular new cameras will be supported...
    If I remember correctly, there was precisely one item on the "known issues" list of the 3.3 release - hiding them does not make them go away.
    Rob

    Lightroom 3.3 Bugs Fixed below (these are probably the major bugs, and there may be many more minor ones not listed).  It would seem that they weren't exactly sitting on their hands.
    Bug fixing is about priority and risk.  If a bug fix has a high risk of creating other bugs and a low priority because of few users affected or easy workarounds, then it might be better to leave it alone.  It's also possible that bugs that seem easy to fix actually require a near entire rewrite of entire sections of code.
    Edit in PS CS4 from LR 3.2 did not give option to render to TIFF/PSD
    Process Version defaulted to PV 2003 when Lightroom’s installed Develop Presets are applied on Import
    All Auto-ISO values were not properly handled for the Nikon D3s
    An error could be generated when sorting by “User Order” in Collections
    There was an incorrect Profile Name tag for Canon 18-55 and 17-40 lens profiles
    Facebook album selection only displayed up to 25 albums
    Lightroom 3 could fail to launch Photoshop CS5 if Photoshop CS4 was uninstalled after the Photoshop CS5 installation
    Numerous cloning or healing spots could have caused Lightroom to become unresponsive
    Lightroom could have crashed when the metadata filter is selected and the grid is displaying all images in the catalog
    Lightroom 3.2 could have failed to import all of the images from an iPhone 4
    Some Sigma X3F raw files were rendering incorrectly
    Choosing the “Make a second copy to” option on import would result in incorrect folder structure for the second copy
    Resetting the crop angle by double-clicking the Angle slider removed a custom aspect ratio
    A tooltip for the Japanese language version of Lightroom 3 displayed the wrong keyboard shortcut for “Flag as Pick”
    Paste Settings did not apply to all images in the Develop module Filmstrip
    Smart collections in Lightroom 3 did not use the same definition of  “All Searchable Metadata” previously available in Lightroom 2
    Text watermarks or portions of text watermarks could have failed to be applied to images on export
    SmugMug publish collection dialog included a mixture of English text  when using a language setting other than English
    Lightroom would not import files from the Panasonic LX5 that were shot with the iZoom Function set to above 90mm
    Choosing the Limit File Size option in the export dialog could have stripped certain EXIF fields from the exported file
    The Targeted Adjustment Tool may have performed slowly in the Lightroom 3.3 release candidate
    A single image published to multiple collections for a single publish service did not display comments properly
    Updating an existing Develop preset with all settings could have failed under certain conditions
    The watermark drop shadow settings behaved differently in Lightroom  3.2 when compared to Lightroom 3.0.  They have been returned to the  Lightroom 3.0 behavior.
    The YYYYMMDD file renaming option was not available when the Lightroom language setting was set to Dutch
    An existing Smart Collection updated to filter for all photos with “Ratings is Zero” would show all images in the catalog
    Publishing an empty category to SmugMug would cause an error
    JPEG exports in the Lightroom 3.3 Release Candidate were significantly slower than the same export process in Lightroom 3.2.
    A graphical Identity Plate included in output was not correctly color managed
    Deleting all images in a Flickr photoset could have caused Lightroom to return an error message
    Changing the sort order to “User Order” while in Survey View on the Mac may have caused an error to appear
    Lightroom could have failed to respond when viewing an image containing numerous cloning or healing spots at 1:1 view
    RGB values were not displaying properly in the white balance tool
    The Smart Collection criteria “Folder starts with” was not working properly
    The navigator panel in the Develop module would incorrectly display  threshold information when holding down the alt or option key and  applying adjustments
    Applying a flag, star or label setting to an image via the toolbar  in the Develop module while in auto-advance mode would result in an  incorrect setting display for the subsequent image
    The application of color noise reduction at low color temperatures  (e.g., tungsten or candlelight) could have provided results below our  quality standards

  • [svn] 4611: Various bug fixes in effects, mostly in the area of seeking, auto-reversing, and shader transitions.

    Revision: 4611
    Author: [email protected]
    Date: 2009-01-21 16:30:21 -0800 (Wed, 21 Jan 2009)
    Log Message:
    Various bug fixes in effects, mostly in the area of seeking, auto-reversing, and shader transitions.
    QE Notes: None
    Doc Notes: None
    Bugs: sdk-17783, sdk-18767, sdk-18759, sdk-18461, sdk-18309, sdk-18013, sdk-18688
    Reviewer: Jason
    Tests: checkintests, Mustella: Effects, gumbo/effects, ListDataEffects
    Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-17783
    http://bugs.adobe.com/jira/browse/sdk-18767
    http://bugs.adobe.com/jira/browse/sdk-18759
    http://bugs.adobe.com/jira/browse/sdk-18461
    http://bugs.adobe.com/jira/browse/sdk-18309
    http://bugs.adobe.com/jira/browse/sdk-18013
    http://bugs.adobe.com/jira/browse/sdk-18688
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/Animation.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/FxAnimateShaderTransition.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/SetAction.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateInstance.a s
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateShaderTran sitionInstance.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/AddChildAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/AddItemAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Effect.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/EffectInstance.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Parallel.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/RemoveChildAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/RemoveItemAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/SetPropertyAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/SetStyleAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/UnconstrainItemAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/effectClasses/ParallelInstanc e.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/effectClasses/SequenceInstanc e.as

    Revision: 4611
    Author: [email protected]
    Date: 2009-01-21 16:30:21 -0800 (Wed, 21 Jan 2009)
    Log Message:
    Various bug fixes in effects, mostly in the area of seeking, auto-reversing, and shader transitions.
    QE Notes: None
    Doc Notes: None
    Bugs: sdk-17783, sdk-18767, sdk-18759, sdk-18461, sdk-18309, sdk-18013, sdk-18688
    Reviewer: Jason
    Tests: checkintests, Mustella: Effects, gumbo/effects, ListDataEffects
    Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-17783
    http://bugs.adobe.com/jira/browse/sdk-18767
    http://bugs.adobe.com/jira/browse/sdk-18759
    http://bugs.adobe.com/jira/browse/sdk-18461
    http://bugs.adobe.com/jira/browse/sdk-18309
    http://bugs.adobe.com/jira/browse/sdk-18013
    http://bugs.adobe.com/jira/browse/sdk-18688
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/Animation.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/FxAnimateShaderTransition.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/SetAction.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateInstance.a s
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateShaderTran sitionInstance.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/AddChildAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/AddItemAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Effect.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/EffectInstance.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Parallel.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/RemoveChildAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/RemoveItemAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/SetPropertyAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/SetStyleAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/UnconstrainItemAction.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/effectClasses/ParallelInstanc e.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/effectClasses/SequenceInstanc e.as

  • After Effects CS6 (11.0.2) update: bug fixes and added GPUs for ray-traced 3D renderer

    We just released the After Effects CS6 (11.0.2) update.
    There are a lot of bug fixes and additions in this update.
    See this page for details:
    http://adobe.ly/AE1102
    Let us know if you have any trouble with this update.

    I have this too, with ML 10.8.2 - pretty sure you can't install custom drivers. Did you find a solution?
    EDIT: Didn't realise I had to update the CUDA drivers manually on OS X! Downloaded from here: http://www.nvidia.com/object/cuda-mac-driver.html and all is OK

Maybe you are looking for