Photoshop plugin bug fixes and release schedule?

Hi,
I am a TD working in 3D computer graphics for architectural visualisation.
First off I really like Pixel Bender and the power it has. Amongst other things we use Photoshop and AE in our workflow. Photoshop for still compositing and AE for Animations. I already have some Pixel Bender tools coded for normal map relighting, toon lines for normal passes and a screen space ambient occlusion shader.
My question is with the Photoshop plugin for PIxel bender. I have the following problems with it:
If the GPU runs out of memory when using a filter it crashes Photoshop. Can we get an error message instead and have it switch to CPU processing? We have different spec machines in the studio so one person could crank up some sampling options and then the next person just gets a crashing file. Could the plugin run independently from Photoshop so if it does crash it does not take Photoshop with it?
UI. It seems that almost all of the UI meta data is ignored? Not sure why? While on the same subject it would be great to have a group box for UI layout or something for more complex filters. Can we also have it update the filter, not during the typing of a number but after enter is hit? Is it possible to get a typable number for integers and not just floats? Could we get something like presets implemeted that change multiple parameters? etc.
Multiple image inputs. It would be insanely useful to have, especially as pixel Bender supports it.
32 bit support image support. Is this planned at some point?
So I suppose my bigger question is asking if this is still something that is in active development and are any of these points planned to be fixed or implemented in the next 6months/ year. Is pixel bender more of a bonus feature not meant for production? Like I said, I really like Pixel Bender and the power it offers but I do not want to invest everyone into a technology that is not getting worked on or just seen as a lab project or something.

Thanks for the reply.
We have a few different cards. Quadro FX 1500, Quadro FX 1800, Geforce GTX 470 amongst others. They all have latest drivers and the Quadro's have the performance drivers installed. The gaming card is actually the most robust one with no errors or crashes so far.
The Quadro FX 1500 cards will not process an image over 4096x4096 because of the Max texture size limit in the GFX card.  It seems that Pixel Bender will process very big images in AE because it is using the CPU. Photoshop does not even launch if the image is above the max texture size. It would be nice to have the Photoshop Pixel Bender still work but just use the CPU only in these cases. Anyway I will add this to the wish list thread.
In terms of crashing, I have a sampling option in one of the kernels I have made that performs a 'sample' image in a for loop. The more times it samples the more likely it is to crash PB. Using the GeForce the sampling can be cranked up and be fine. Using the Quadros it will just crash when the sampling number gets too high even at dimensions of 720x480.
If you have any suggestions to stop the crash, please let me know what you would recommend next. I have no problem sending you a .pbk file and the steps to break Photoshop. It might be difficult to reproduce though if you do not have the same hardware. I could also make a video or send you any other info if you need it.
I understand that it is not possible to talk about specifics in terms of development. However, is it possible to give a very rough guide to how often releases and updates are planned. E.g. once every 6 months, once every 2 years? Once every 5 years? Is Pixel Bender 3D going to be the focus for the next few years? It is difficult to know which direction to steer our own development. I don't know if I have jumped on this too soon and if I should wait a couple of years for it to mature?
I will make a list and add it to the forum. Almost all my comments are for the Photoshop implementation of PB.

Similar Messages

  • 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

  • How Long For Fixing and Release WPA/WPA2 on N900?

    Hay Nokia!!
    I use N900 Maemo PR1.2 Lasted update.
    At home i'm create WPA2-Shared-key (Belkin Router) it's worked.
    At Friend Home i'm used WPA2-Shared-key (Belkin, Lynksys, D-Link) it's  worked no problem.
    At Office i can not used WPA2-Shared-key with Lynksys difference model it's not worked, but many co-worker worked with iPhone.
    and My Friend use iPhone 3Gs worked with all WPA2 - Shared Key that i'm try with N900.
    i try change MAC by macchanger it's a same Not worked.
    i'm asking for Maemo.org they toll me it's BUGS -_-"
    How long For Fixing and Release??

    you will not get a response as other then the mods,  nokia folks do not really watch this blog.   your best bet is the maemo community where you were before.
    maemo.org

  • [svn:fx-trunk] 9661: Compiler optimized FXG 2. 0 bug fixes and updating to latest FXGUtils.

    Revision: 9661
    Author:   [email protected]
    Date:     2009-08-26 13:26:12 -0700 (Wed, 26 Aug 2009)
    Log Message:
    Compiler optimized FXG 2.0 bug fixes and updating to latest FXGUtils.
    From FXGUtils:
    Width and height attributes are now allowed on RichText.
    The textRotation attribute is now supported.
    Simple fix to recognize the paragraphEndIndent attribute.
    Added support for resizeMode in BitmapGraphic.
    From MXMLC: Simple fix to get tag for static FXG.
    Partially Fixed Bugs:
    SDK-22846 - Compiled FXG text with subformatting loses some text, colors, etc.
    SDK-22855 - tags don't work in static FXG content
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-22867
        http://bugs.adobe.com/jira/browse/SDK-22852
        http://bugs.adobe.com/jira/browse/SDK-22846
        http://bugs.adobe.com/jira/browse/SDK-22855
    Modified Paths:
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/fxg/FlexFXG2SWFTranscoder.java
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/fxg/FlexParagraphNode.java
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/fxg/FlexSpanNode.java
        flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/fxg/FlexTextGraphicNode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/fxg/FXGConstants.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/fxg/FXGException_en.properties
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/fxg/swf/FXG2SWFTranscoder.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/CDATANode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/RichTextNode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/TextGraphicNode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/TextNode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/AbstractRich ParagraphNode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/AbstractRich TextLeafNode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/AbstractRich TextNode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/DivNode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/LinkNode.jav a
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/ParagraphNod e.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/TCYNode.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/text/AbstractTextNode .java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/sax/FXGVersionHandlerRegi stry.java
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/swf/ImageHelper.java
    Added Paths:
        flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/types/TextRotation.ja va

  • [svn:fx-trunk] 13129: ASDoc bug fixes, and added a note that Scroller no longer has a default value of hasFocusableChildren ="false" and focusEnabled="true"

    Revision: 13129
    Revision: 13129
    Author:   [email protected]
    Date:     2009-12-21 13:50:37 -0800 (Mon, 21 Dec 2009)
    Log Message:
    ASDoc bug fixes, and added a note that Scroller no longer has a default value of hasFocusableChildren="false" and focusEnabled="true"
    QE notes: -
    Doc notes: -
    Bugs: - FLEXDOCS-386
    Reviewer: -
    Tests run: - checkintests
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/FLEXDOCS-386
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/VideoDisplay.as
        flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
        flex/sdk/trunk/frameworks/projects/framework/src/mx/events/VideoEvent.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/core/SpriteVisualElement.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/interpolation/MultiValueInterp olator.as

    I had a while ago similar problem with USB memory stick. At the end, I don't know why, just formatting it using WinXP helped me.
    S-
    Last edited by StenM (2011-07-22 17:56:32)

  • Understanding bug ID and release notes documentation

    Hi !
    we planned to upgrade IOS switch on some switches, most switches are running 4 to 10 or more IOS release in late in compare to the most recent one.  We would like to upgrade because we had some issue with port flapping and spanning-tree portfast issue with switches.  I find in one release document some element looklike solve some of our problems.
    So before upgrading we would like to avoid more issue or different issue which may have bigger impact we had actually, so I read latest release notes of our plate-form to choose the correct release for our need....
    I find some bug ID in release notes 12.2(55)SE mark as Resolved and do not find it in 12.2(54)SE or 12.2(53)SE as "open" and some bug open in 12.2(53)SE as open and nothing about those in the next 2 releases (Open or Resolved).
    So how can I choose correct release for our need, while also minimised required reading release notes documentation !
    Thanks !

    If the bug was discovered after the 12.2(54)SE release notes were published, only the 12.2(55)SE release note will show the fix. The older release notes will not be updated with bugs discovered after the relesae note is "printed."  Only the most current release note has the most current data.
    Bugs mentioned in 12.2(53)SE release note SHOULD have a follow up in future release notes, unless engineers determined that the bug was not a bug at all, but an expected behaviour, a customer misconfiguration, or a transient, unreproducable event.
    The interactive Bug Tooklit is the best way to tell where a bug applies.  If you plug in the bug ids about which you have questions, you can see a real time picture of the current state of every bug id mentioned in the release notes.

  • Logic Releases Bug-Fix and Enhancement List for 7.2 & 7.2.1

    ...I found this announcement on a post from nearly 1 month ago on www.logicprohelp.com...
    "Yesterday, Apple released two new articles listing in detail the enhancements that found their way in Logic 7.2 and Logic 7.2.1"
    Logic Pro/Express 7.2.1 Enhancements
    =AND=
    Logic Pro/Express 7.2.1 Enhancements

    Woah.
    Those are fixes? And there's still problems left? woah.
    Like swiss cheese, this program is.
    X
    but I love it anyway.

  • My Photoshop CS6 Bugs, Ideas and other things

    First of all, great job on many new features like: Dashed strokes, Styles for your Character and Paragraphs, Background saving.
    I'm a webdesigner and I am using it now this whole morning and midday. So far so good, install went fine, working perfectly. But below a list of features I miss and a list of bugs or some other things I miss.
    - Changing the opacity of a layer from any number to 100% doesnt work with the numeric pad
    - Great job on the styles for typography, but why not doing the same thing for colors/swatches. You can make your own swatch library and you can attach that color to any object, shape, whatever. What would be really handy if you change that color in the swatches it would affect all objects who share that swatch. Really missing that feature a long time!
    - Still missing external use of images/psd's/ any format. That I can place in my document, for example a psd, and when I change the original psd it would also automaticly update the placed object. It's like using a library like Fireworks.
    - I like it when I drag my documents into photoshop, but when I drag a PSD to Photoshop it will open as a smartobject into the file wich was open, not as a new window. You can only achieve that by dragging it outside of the document, more like dragging it onto the option bars... Imo that's irritating.
    - If you make a vector shape, it creates a path. If you select the shape it will show the path outlines around the shape. When you apply layer effects on the shape the shape is still selected, so you will see the path outlines around the shape. It's very annoying when you apply a stroke around the object it still showing the outline of the path around it. In CS4 (don't know about CS5) you could deselect the layer, then double click the effects icon on the layer and it will popu the layer styles menu without showing the outline of the path, in CS6 that doesnt work anymore.
    I try to update this once in a while

    So i finally started using the trial photoshop 6 and the first thing I notice, (that was wrong with 5.5) is that the zoom is zagged! Why must it zoom in large increments using the magic mouse? How it is possible to work with images zooming (very clunky) is beyond me. Photoshop 4 is fine. Nice and smooth when I'm using the finger scroll like a wel tuned machine, but then in the newest and greatest editions, it works like smashing the throttle to pull forward an inch!
    This is crazy that something as basic as this is not addressed. Thank god that I can use the lasso tool and the zoom with scroll wheel again in this version (didn't work in 5.5) but hopefully this get s addressed. I really don't want to have to suffer through this when the newest final version is out.
    Also, ( I assume this will be fixed in the final version) all of my preferences get reset everytime i open it. That is annoying.
    So far I like the new look and it is much better than 5, but the basic things should work!  I'm also not used to the tools not lining up with the cursors the same way. The lasso tool used to line up with the actual lasso, but now they line up with the arrow. Makes sense, but will take some getting used to.
    PLEASE FIX THE ZOOM!

  • After Effects CS6 (11.0.3) bug-fix update released, enables running on Mac OS X v10.9 (Mavericks)

    Adobe After Effects CS6 (11.0.3) fixes many crashes and other bugs.
    Details: http://adobe.ly/AE_CS6_1103
    This update is required to run After Effects CS6 on Mac OSX v10.9 (Mavericks).

    Thank you, Todd. I (and many others, I'm sure) are glad to see Adobe still supporting the older (purchased) software. Not a lot of companies do that sort of thing.

  • OVM 3.0.1 agent bug, fixes and workaround

    In OVM 3.0.1, the yaml configuration file in /etc/monitor/ disappears upon serveur add in a pool if /tmp is a different filesystem than /etc/monitor. The addition to the pool fails. This is due to the agent preparing the new configuration file in /tmp then calling python os.rename() to move it to /etc/monitor/. Possible fixes for OVM developpers ; don't use os.rename(), or create the new configuration file in os.path.dirname(MONITOR_CFG). For users, just umount /tmp before adding the server to a pool.
    Hope it helps.
    Christophe Varoqui

    user9336528 wrote:
    In OVM 3.0.1, the yaml configuration file in /etc/monitor/ disappears upon serveur add in a pool if /tmp is a different filesystem than /etc/monitor. The addition to the pool fails. This is due to the agent preparing the new configuration file in /tmp then calling python os.rename() to move it to /etc/monitor/. Possible fixes for OVM developpers ; don't use os.rename(), or create the new configuration file in os.path.dirname(MONITOR_CFG). For users, just umount /tmp before adding the server to a pool.Can you log this bug at http://bugzilla.oracle.com, please?

  • Waveform or plugin bug? and the difference between 8bit & 32bit psds

    I have recently come across some issues which I do not understand, not sure if it's lack of knowledge or bugs.
    Waveform monitor appears clipped after adjustment and 2 psd files with identical layers/luminance values - (one 8 bit and one 32 bit) come into prem
    with different gammas.
    I have created a video displaying these issues
    http://www.youtube.com/watch?v=rT2-d358KE4
    Hopefully someone can have a look and help me out.
    On a mac with all the latest updates etc
    Cheers

    Just realised that my psd issue may very well lie with PS and my lack of knowledge... apologies for that.
    I started from scratch... recreating files again.
    I think I need to learn about the 32 bit colour picker and how the "stops" and "intensity" relate.
    It appears that to get the same visual results the above mentioned slider needs to be at a negative value but I am not sure what.
    Apologies again... off to do some more learning.

  • Bug fixing and enhancements in reports

    can u please provide me the belo mentioned object 
       changes in budget variance report, added a new functionality by displaying the report in treeformat when user inputs fsv

    Welcome to SDN, please work yourself first on your requirement and study the rules of engagement before posting.
    Thread locked.
    Thomas

  • 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

  • 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.

  • CS6 update (bug fix)

    I downloaded the latest AICS6 bug fix, just released. Not sure what it fixed, but the same old bug is there that I've been complaining about for over a year. Still can't drag global colors between sliders in gradient. The more things change the more they stay the same. Adobe has proven they do not consider this important. I'll just keep beating this dead horse.
    https://www.youtube.com/watch?feature=player_embedded&v=LxOkkrMZzFc

    Same here... my bug has been reported by several people that I know (aliasing option when exporting to Photoshop does not function).
    Two updates later and the bug is still not fixed.
    Adobe is too big. I am searching for other options.

Maybe you are looking for