Lightroom 3.3 Release Candidate

Journal Article
Labs page
Lens profile creator and downloader

clvrmnky wrote:
Thronsen wrote:
According to whom?
And Im not sure AVCHD should be counted as a new 'feature'. It is a format used by many, many cameras. It would be great if Adobe could provide support for the entire camera, not just part of it.
Video was one of the most highly touted of features for Lightroom 3. It was a key feature for me, and due to its incomplete implementation I find it more of a nuisance then any real use.
A new (container) file format would always be considered a feature. Adobe chose to not support this format for whatever reasons they had at the time.  Video support was obviously just introduced for Lr 3 to satisfy some basic requirements, and the fact is a large part of the user base could care less if it has video support at all.
Adobe is well aware of what some users would like. The problem is that if you consider what all the users would like across the product, you quickly realize that there is more work than time available for each release.
Point releases have traditionally been about stability, bug fixes and ACR support. These are the things that affect the greatest percentage of the user base.
I guess you are missing the users interests. If they would introduce a new container format only in major releases, would mean that we around 1.5 years before AVCHD is supported. Cameras with AVCHD are now for at least 1.5 years on the market. Needing 3 years to support this would be certainly not very acceptable. Thus, the request to support AVCHD as soon as possible is certainly absolutely legitmate. There is no reason not to include such a thing in a point release - its just product policy.
Kind regards
Thomas

Similar Messages

  • Lightroom 2.1 Release Candidate - Note from Adobe

    Lightroom 2.1 has been posted as a release candidate to Adobe Labs:
    http://labs.adobe.com/wiki/index.php/Lightroom_2.1
    Blog post on the topic here:
    http://blogs.adobe.com/lightroomjournal/2008/09/lightroom_21_available_on_adob.html
    From that post: The Lightroom team would like to thank all of the photographers on the Lightroom User to User forum who helped provide constructive insight into the issues that we have fixed in this release.
    Regards,
    Tom Hogarty
    Lightroom, Camera Raw, DNG Product Manager

    Much better performance right from the start. I appreciate the speed improvements--- no beach balls yet. I don't think I am alone when I say that the beach ball is a real drain not only on time spent, but the stress of "what changes were saved" , "is this going to crash and corrupt my database" and "maybe I do miss my darkroom". The rest of the problems don't seem to bother me as much, and those seem to be fixed too.
    Occurs to me that we should have one sticky thread for single posts on bugs and separate ones for troubleshooting them.
    Anyhow, great to have my Lightroom back running like before with more tools than LR1.4.

  • Lightroom 3.2 Release Candidate Available on Adobe Labs

    This release includes camera support, bug fixes and new features.  Details here:
    http://blogs.adobe.com/lightroomjournal/2010/08/lightroom-3-2-and-camera-raw-6-2-available -on-adobe-labs.html
    Regards,
    Tom Hogarty
    Lightroom, Camera Raw and DNG Product Manager

    Despite the fact that the bug list does not announce any of this, I'm very happy to report that LR3.2 RC seems to run quite a bit snappier in many ways. Local edits are still slower with an image that already had a lot of tweaks applied compared to applying them on a fresh image, but overall the performance seems to be much improved.
    Its still early days and I'll have to do some real work but so far it looks very promising. Thanks for the release candidate!
    The stuttery cursors of the spot removal and red-eye tool are gone as well. Nice touch. I now have an idea why it had been these two cursors that were different. They are the only ones which may need to change mode if the cursors are run over previous applications (i.e. there has to be a collision test with round shapes other than the handles). In my current testing I noticed that said cursors sometimes can become stuck completely and only move on after a slight pause. I think this is a new bug as I haven't seen it before. Hope it is not Lua garbage collecting. Moving the cursors around shouldn't really be a problem even if there are some collision tests to be performed.
    A bug I reported about the spot removal tool not working well in corners also appears to have been addressed.
    I've only done a very quick test so nothing is definitive but indeed looks promising.
    The only issue that might have gone worse is the jerkiness of scrolling through the grid mode with the scroll bar. It wasn't great before but I now seem to experience more frequent and longer pauses in updating the grid. Please, everyone compare the (on my system jerky) way the scrollbar moves the grid to grabbing the grid with the mouse (move the cursor on a line between images and it will turn into a hand). If you move the mouse while having grabbed the grid, the updates are smooth and allow visual tracking of the images while they move. The movement with the scrollbar is so jerky that I cannot visually track the images as they pass by.
    Note that scrolling with cursor keys is very fast without pauses but the movement isn't smooth (jumps with the image height) so again visual tracking is hard.
    I have an idea why the scrollbar is as decoupled from the grid movement as it is, but I hope that there is room for improvement. I'd be prepared the grab the grid even though that would mean precision manoeuvres with the mouse, but unfortunately, you don't really get far with this method.

  • If I download the Lightroom 4.4  release candidate, will it keep all of my stuff?

    I am able to keep all of my photos/collections in Lightroom when I update, but I was wondering if I did the release candidate if it would do the same?

    I just installed it and it kept all of mine, but there was a problem with previews disappearing. How long does it take to back up your existing stuff? I'd back it up...just in case

  • Lightroom 2.1 Release Candidate is available in the Labs

    http://labs.adobe.com/wiki/index.php/Lightroom_2.1
    http://blogs.adobe.com/lightroomjournal

    Much better performance right from the start. I appreciate the speed improvements--- no beach balls yet. I don't think I am alone when I say that the beach ball is a real drain not only on time spent, but the stress of "what changes were saved" , "is this going to crash and corrupt my database" and "maybe I do miss my darkroom". The rest of the problems don't seem to bother me as much, and those seem to be fixed too.
    Occurs to me that we should have one sticky thread for single posts on bugs and separate ones for troubleshooting them.
    Anyhow, great to have my Lightroom back running like before with more tools than LR1.4.

  • RELEASE CANDIDATE VERSION EXPIRED?

    When I click on Lightroom 5 I keep getting a prompt saying ' THIS RELEASE CANDIDATE VERSION OF LIGHTROOM HAS EXPIRED' what does this mean? I bought the full package about 6 months ago and not had any problems with it.

    I think its a bit tricky, when you install the release candidate LR 5.3 RC it would have replaced the earlier version of LR you had on your computer e.g LR 5.0 or LR 5.2. The final version of LR 5.3 was released  a couple of weeks ago, however I do not believe the release candidate gives you a prompt that there is an update.
    Just download LR 5.3 update and run the install package and it will replace the release candidate version. If you had an earlier version of LR 5 there should be no need to imput the serial number again, unless you have removed it manually.

  • Can I run Release Candidate (19.02), Beta, Nightly, Aurora and ESR versions on the same computer?

    I know I can run the Beta and Nightly together on the same computer because they are installed in different directories. What I do then is that I have a Profile for each version. What I do is I run FireFox.exe -ProfileManager when I start either the Beta and Nightly builds.
    My Question is can I also install the Aurora, Release Candidate and ESR versions on the same computer like I do with the Beta and Nightly? If so, how do I go about installing them in different directories? I will create new profiles for each version. What I then do is, copy everything in my original Profile to the newly create profiles so I can keep all my plugin/addons, themes, bookmarks, etc. the same.
    Next question, (I think I know the answer but I just want to make sure) now can I sync my bookmarks from each of the different profiles that I created?
    Secondly, I now I can do the ABOUT:CONFIG in the address bar of Firefox, does anyone have any idea where I can read up on what each entry means? Also, are there any other secrets in Firefox, similar to the ABOUT:CONFIG trick? I know of one app where you can do ABOUT:ME, but that's all I know.
    I know this has been asked billions of times, but I also have to ask. Is there any chance at all that Firefox, Thunderbird, and/or Seamonkey will be ever release for the iOS from Apple? I know that it's impossible, but maybe someone MIGHT have some positive thoughts on this?
    Lastly, I know this is off topic, but I'll give it a shot. I'm using Outlook 2013, does anyone know if Outlook can handle Newsgroups? The reason why I ask is because I've just learned that there are a ton of newsgroups for Firefox, ThunderBird, and SeaMonkey. I would like to, somehow, get those Newsgroups in Outlook 2013. I already get allot of the feeds for other things, so that's not a problem.
    I would appreciate it very much if anyone could help me with these issues.
    Thank You.

    You can consider to use Firefox Sync to sync all the profiles.
    You can do a custom install of each version and install each version in its own program folder.<br />
    Safest is to modify the desktop shortcut and add -P "profile name" to the command line to start each version with its own profile.<br />
    Be careful with clicking a file in Windows Explorer to open the default browser, so make sure to select the correct profile in the profile manager and check the don't ask setting.
    * http://kb.mozillazine.org/Shortcut_to_a_specific_profile
    * http://kb.mozillazine.org/Using_multiple_profiles_-_Firefox
    * http://kb.mozillazine.org/Bypassing_the_Profile_Manager
    * http://kb.mozillazine.org/Opening_a_new_instance_of_Firefox_with_another_profile

  • ACR 8.7 release candidate, Nikon D750, Lens corrections tab

    I capture images using a Nikon D750 & AF-S NIKKOR 24-120mm f/4G ED VR lens with image quality set for NEF (RAW) + JPEG fine & image size set for Large. Slot 1 card saves the NEF files & slot 2 card saves the JPEG files. I download the images using Bridge CC Photo Downloader converting the NEF to a DNG while downloading. When editing the DNG image using the Lens Corrections tab in ACR it correctly recognizes the lens. When editing the JPEG image the same way it incorrectly identifies the lens as an AF-S NIKKOR 14-24mm f/2.8G ED and does not offer a choice for the correct lens. I hoping this can be fixed soon. A workaround that seems fairly accurate is to choose the AF-S NIKKOR 24-70 f2.8G ED instead for the JPEG images.
    I recently had to install Camera Raw 8.7 for CC Release Candidate Version: RC 1, Date: October 2, 2014 to recognize the D750 NEF files.

    What you’re seeing is normal.  Most lens profiles from Adobe are for RAW files only.  Many cameras do their own corrections, nowadays, so Adobe cannot assume the raw profile would work for JPGs from the camera as a general case.  For example with my new Canon 7D Mark II, which I'm awaiting raw support for at all, I can select vignetting, chromatic-aberration and geometric distortion correction as separate items on the menu to be used for producing camera JPGs.  Adobe doesn't attempt to interpret such proprietary information and apply the appropriate correction for corrections I haven't already asked the camera to do, they just don't supply a lens profile at all for JPGs.  The kit lenses for some cameras seem to be the exception to this, as well as a few other lenses, which I'm not sure why they've supplied profiles for.  You can also download profiles others have created, themselves, using the Adobe Lens Profile Downloader which you can find on the adobe.com site.
    If you are confident you won't ever have distortion or vignetting correction enabled on your camera for the JPGs it produces, then you can hack a copy of the Adobe-supplied raw profile for a particular lens to be for non-raws, by changing the whateverRAW tag from True to False, and put the modified profile in the user-created profiles area of your computer and it’ll be seen and used.

  • ACR 6.1 Release Candidate causing hangup in CS5

    I'm running Windows 7 and Photoshop CS5.  I've been using the program with ACR 6.0 for about 2 weeks with no problems.  I installed AC 6.1 Release Candidate tonight and opened a Canon raw file from a 7D.  I did all of my adjustments in Camera Raw and then opened the file in photoshop.  When I try to save the file  the program goes into a loop and hangs up, basically locking photoshop up and making me have to shut down the computer to reboot it. After the reboot, I went back into the same file again with the same results.
    How do I uninstall 6.1 and go back to 6.0?

    I have returned to ACR 7.0 and it does not have the issue described above for ACR 7.1 RC.  I am reprocessing images that were already processed with PV2010 and switch between PV2010 version and PV2012 version using the "Image Settings" and "Custom Settings" .  I can do this in ACR 7.0 while in the Basic Panel, but not in ACR 7.1RC.  In ACR 7.1RC I have to switch to something other than the Basic Panel before I switch between PV2012 and PV2010 using "Image Settings" and "Custom Settings", but after I do this one time for an image I can then do this in the Basic Panel. 
    This bug needs fixing before the production release. 

  • Announcing General Availability of PowerShell Connector and Release Candidate of Generic SQL and SAP Roles/Users

    The FIM team is pleased to announce the availability of some additional Connectors for FIM2010R2.
    General Availability of PowerShell Connector
    The PowerShell Connector can be used to communicate with a system through PowerShell scripts. This allows an easy and flexible way to communicate with other systems but also to pre-/post-process data and files before handed over to the FIM Synchronization
    Service. We believe the community will help providing scripts for this Connector for various systems and will open a place where scripts can be published for reuse.
    TechNet docs:  
    http://go.microsoft.com/fwlink/?LinkID=393057
    Download:         
    http://go.microsoft.com/fwlink/?LinkID=393056
    Release Candidate of Generic SQL Connector
    The Generic SQL Connector will allow you to connect to any database where you have an ODBC driver available. It enables new features compared to the built-in MA such as support for Stored Procedures, running SQL scripts, built-in delta import support, import
    multiple object types, connect to multiple tables, and much more. This Connector is built on ECMA2.3 which allows schema discoverability to be customized in the Sync Engine UI. A pre-release of the next Sync Engine hotfix is included with the Connector download
    and is required for the Connector to work.
    Download:         
    https://connect.microsoft.com/site433/Downloads/DownloadDetails.aspx?DownloadID=52652
    Release Candidate of SAP Users and Roles/Groups
    The updated SAP templates for Users and Roles/Groups allows you to manage Users, Roles, and Groups in SAP. This also include password sync for Users to SAP. The Connector will make sure roles are represented as groups to make it possible to manage these
    with bhold. This template will require the previously published WebService Connector:
    http://go.microsoft.com/fwlink/?LinkID=235883.
    Download:         
    https://connect.microsoft.com/site433/Downloads/DownloadDetails.aspx?DownloadID=52651
    If you have participated in any other Connector preview program you will have access to the Release Candidate downloads. If you have not participated before then to get access to the preview programs on Connect either join the program “Identity and Access
    Management”, “FIM Synchronization Service Connectors Pre-release” on
    http://connect.microsoft.com/directory or follow this link
    http://connect.microsoft.com/site433/SelfNomination.aspx?ProgramID=6709&pageType=1
    We have also published an update to the Generic LDAP Connector adding support for some additional LDAP directories, see
    http://support.microsoft.com/kb/2936070/. If you have additional LDAP directories you think we should support, please feel free to contact me.
                    On behalf of the FIM Sync team,
                    /Andreas Kjellman

    On Tue, 18 Mar 2014 08:09:43 +0000, David Burghgraeve wrote:
    We've been using the OpenLDAPXMA to be able to connect to ACF2 CA-LDAP (from Computer Associates) running on a IBM Z-OS Mainframe System. We've been using it for password synchronization since 2004 on MIIS. Today it's still used via the
    OpenLDAPXMA (64bit) on FIM 2010 R2.
    We had to tweak the password management component in the OpenLDAPXMA to support the error messages we get from the ACF2 System, as we support a multi-master password setup between Mainframe and Active Directory (one can change the password on
    MF and/or on Windows). by example  "LDP0406E ACF2 error modifying lid(ACF00155 NEW PASSWORD CANNOT BE THE SAME AS CURRENT PASSWORD)".
    Additionally, we cannot get the delta import to work with the CA-LDAP, there's no capability in it and we tried to use the time attribute to use in the query for recent changes, but it does not work. (I think we need it in a large integer format
    or unix time integer).
    Would be great to have Microsofts' support in this :)
    In a case like this where your follow-up has nothing to do with the
    original post you should create a new thread.
    Having said that, neither of the MAs to which you refer are official
    Microsoft MAs and as such there is no support from Microsoft available.
    Also, keep in mind that the ECMA1/XMA extensibility framework has been
    deprecated and replaced by the ECMA 2.0. You should plan on replacing
    existing ECMA1 management agents with ECMA2.0 connectors.
    Paul Adare - FIM CM MVP
    "It's 106 light-years to Chicago, we've got a full chamber of anti-matter,
    a half a pack of cigarettes, it's dark, and we're wearing visors."
    "Hotsync." -- Paul Tomblin & Peter da Silva

  • Printing layout problem with Lightroom CC 2015 Release

    Hello,
    I am working with the following configuration :
    MacBook Pro (15-inch, Mid 2010)
    OS X Yosemite Version 10.10.3
    Adobe Photoshop Lightroom CC 2015 Release
    EPSON Stylus Pro 3880
    I tried to print two images on a Super A3 paper sheet with an EPSON Stylus Pro 3880 directly from Lightroom and here is an example of what I expected (I resized and added a black border for better visibility on the forum):
    This is the preview I have in the printing module of Lightroom and this is also what I have when I print to a JPEG file with Lightroom.
    Sadly, after I launched the printing job, this is what came out of the printer:
    As we can see, the layout of the two pictures has been shifted toward the top of the paper sheet (cropping the top of the first image in the process) and about 30% of the right part of the layout has not been printed.
    Do you have any idea of what I am doing wrong here?
    For your information, I do not print very often so I am not 100% sure that I set everything correctly. However, I have been successfully printing in the past and it was with the same MacBook Pro on the same EPSON Stylus Pro 3880 printer but it was with OS X Yosemite Version 10.10.1 and with Lightroom 5.x (I cannot remember exactly which version).
    Moreover, because my print was urgent, I retried with a Windows machine running Lightroom 4.x with the same printer and it was a success. So I doubt that my initial settings on my MacBook Pro were wrong although I am not 100% sure.

    I am in France and I found out that EPSON is providing at least two different files for its v9.33 driver that relate to the Stylus Pro 3880 with OSX:
    epson16738.dmg: US version (https://www.epson.com/cgi-bin/Store/support/supDetail.jsp?UseCookie=yes&oid=141552&prodoid =63085147&infoType=Downloads&d…)
    epson379436eu.dmg: French version (Support et téléchargements - Epson Stylus Pro 3880 - Epson)
    and I realize that I was using the US driver which.
    After few minutes of refection, I realized that the 3880 driver that I installed on my MacBook pro was the only piece that was present when my prints failed and absent when my prints succeeded. So I though it had found out the cause of my problems until I tried with the french driver (epson379436eu.dmg)...
    In the meantime Adobe has release of new version of lightroom so let me recap my new configuration:
    MacBook Pro (15-inch, Mid 2010)
    OS X Yosemite Version 10.10.3
    Adobe Photoshop Lightroom CC 2015.0.1 [ 1018573 ] (info available in Help menu > System info > Lightroom version)
    EPSON Stylus Pro 3880
    Epson driver v9.33 epson379436eu.dmg
    ... and the result of my test is ... nothing at all! Lightroom sends the the print job to the printer but nothing comes out of it.
    However, when I printed to a file from lightroom and then tried to print this file with OS X Preview on the Epson 3880, it worked perfectly.
    It also worked when I printed from Photoshop CC (2014.2.2).
    It also worked when I printed from Lightroom but with a different printed and driver (Canon MF8580Cdw).
    Therefore, among the five elements of my configuration cited above, there is none for which the printing job is always failing. It is hard to find out what is the faulty piece of software!

  • J2SE 1.4 Release Candidate & Java Web Start

    Hi:
    We installed the J2SE 1.4 Release Candidate and our Java Web Start applications which previously worked now won't run. Upon their launch, there is the following error message :
    Error Code 11 (11 Could not locate requested version) returned from server when accessing resource (http://java.sun.com/products/autodl/j2se, 1.4.0-rc)
    Does anyone know why this is?
    All replies are greatly appreciated!
    Sincerely,
    Mona

    Hi:
    I tried what you suggested in the jnlp file:
    <j2se version="1.4 1.4.0-rc" href="http://java.sun.com/products/autodl/j2se"/>
    and I am still getting the error:
    The application has requested a version of the Java 2 platform (JRE) that is curently not locally installed. java Web Start was unable to automatically download and install the requested version. The JRE version must be installed manually.
    Error Code 11 (11 Could not locate requested version) return from server when accessing resource: (http://java.sun.com/products/autodl/j2se, 1.4 1.4.0-rc)

  • DNG Converter 6.7 release candidate

    Which version of the Mac OS is required to run the Adobe DNG Converter 6.7 release candidate application? I have successfully installed it, but seem unable to open it. The converter icon is sitting right there in my Applications folder, but it will not launch. My old Mac OS 10.4.11 is likely the cause of that, right?

    Thanks Station One. Fortunately I am running an Intel Mac. I can upgrade to OS 10.7, via 10.6. In fact I've had the 10.6 upgrade disc in my hands for months. Just too uncertain about sliding it into the machine and setting if off! I expect the worse that can happen is that some existing files will not open and applications will not run, and will themselves need to be updated. Never seems to be the right time to take that on. But, now I must. I've done a little research on taking precautionary, backing-up steps beforehand.

  • Bc4j-oc4j and Jdeveloper Release Candidate

    I developed a bc4j application with Jdeveloper Release Candidate. In another pc I installed 9ias and bc4j-oc4j server. Then I deployed my application using .ear file. I get an error when I try to run the application through the as. Here is the error:
    oracle.jsp.parse.JspParseException: Line # 18,
    Error: releasemode is not a property of oracle.jbo.html.jsp.datatags.ApplicationModuleTag
    I think it is not true that releasemode is not a property of ApplicationModule tag. Can anyone help me?
    thanks

    Hi, first of all thanks for your interest and sorry for my English.
    Actually I have tried some different combinations.
    First of all I downloaded 9ias v1.0.2.2 core form web-site. In it oc4j comes with version 1.0.2.2.1. I installed it and could not even get that error message. Then I installed bc4j runtime installer over it. Then I got that error message.(That message is just an example. I think not all of the necessary classes with correct versions are contained in the container.). Then I tried to use the oc4j that is embeded in the jdeveloper release candidate. I copied the directory and put to the proper place in the application server. It did not even start. Finally I downloaded 9ias Release2-j2eedeveloper's preview. It brougth me a version 9.0.2.0A. I was wery hopeful with it but it did not work either.
    I only want to deploy and use my jsp files that I created by jdeveloper release candidate. I need correct versions of application server and container I think.
    Thanks a lot.

  • Release Candidate - what does it mean?

    JavaTM 2 SDK, Standard Edition, v 1.4.0 Release Candidate (J2SETM)
    hi all,
    just found out that Java 1.4 Release Candidate has released.
    is that the final version for 1.4.0? or another beta version that is close to final?
    Thank you..

    Neither. That means something like "After all that beta testing, we don't think there are too many bugs left, so maybe what we have now can be released as 1.4.0, but we aren't quite certain of that yet."

Maybe you are looking for