Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Capture One 11.0.1 released!

Jim_DK
Capture One 11.0.1 is now available to download! This is a free service release for all Capture One 11 owners/subscribers.

Highlights:

Camera support
Fuji XE-3 support

Lens support
Olympus M.Zuiko Digital ED 17mm f/1.2 PRO
Olympus M.Zuiko Digital ED 45mm f/1.2 PRO
Leica Elmarit-M 21mm f/2.8 ASPH.
Leica Summarit-M 35mm f/2.4 ASPH
Leica Summaron-M 28mm f/5.6
Leica Elmarit-M 24mm f/2.8 ASPH
Leica APO-Summicron-M 50mm f/2 ASPH
Leica Tri-Elmar-M 28-35-50mm f/4 ASPH

Large number of bug fixes and stability improvements.

For full release information download the release notes https://www.phaseone.com/en/Download.aspx
0

Comments

20 comments

Date Votes
  • Frank.O
    Hi everybody,

    after reading that the Fuji X-E3 ist now supported by CO 11 I immediately upgraded because that was what I was waiting for. Unfortunately only to learn the hard way that being an early adopter is not always the best thing to do.

    Everything seems to work except for picture import.

    No matter which camera, file format (RAF uncompressed, RAF compressed, jpg,arw, raw...) import doesn’t work.

    I click the import-icon, choose the folder from which to import, highlight the previews of the pictures to import and klick import or import all and apparently nothing happens. The pics are not displayed in the browser. If I use an empty new session and click on the capture folder the browser says "there are no pictures in this collection".

    I then found out that the picture files are actually copied to where they belong (capture folder in case of a session, or the specified folder in my originals-folder-structure) with the naming I had set up (picture date and time) but without the file name extension (RAF, jpg...). There is no reference to the imported pics in the catalog or the session and in case of a catalog there is no collection created under "latest imports".

    I have already taken the usual trouble shooting measures (deleting the preferences, reloading my workspace etc) but to no avail.

    And I have created a support case, I just thought I would let you all know so that those who have work to be done are warned about a possible bug and with a tiny bit of hope that someone has a workaround.

    Regards,
    Frank
    0
  • John Doe
    Can you check you're using the Pro run-mode and not DB or Sony?
    0
  • Frank.O
    [quote="John Doe" wrote:
    Can you check you're using the Pro run-mode and not DB or Sony?

    Yes I do use the Pro-mode.
    0
  • Marco M. Jaeger
    wondering whether the import order numbering has been fixed - does anybody know?
    0
  • Ian Wilson
    Moderator
    Top Commenter
    [quote="mmjaeger" wrote:
    wondering whether the import order numbering has been fixed - does anybody know?

    The release notes seemed to say so.

    Ian
    0
  • Permanently deleted user
    Anyone tested whether the D850 is now fully supported in live mode (zoom, image formats, whether + writing on card)?

    Best
    Frank
    0
  • NNN635158767546269381
    [quote="Frank.O" wrote:
    Hi everybody,



    Everything seems to work except for picture import.




    Can you make a screencast of the issue ?
    0
  • Philipp Ringli
    11.0.1.40 is the worst update, ever. Getting kernel panic and crashes by the dozen within an hour, especially when doing color balancing.
    Downgraded to 11.0 release. And it's slow as molasses on a MacBook Pro
    (2.8 GHz Intel Core i7 with 16GB Ram, Radeon Pro 560 4 GB, Intel HD Graphics 630 1536 MB)
    0
  • Christian Gruner
    [quote="cmyk" wrote:
    11.0.1.40 is the worst update, ever. Getting kernel panic and crashes by the dozen within an hour, especially when doing color balancing.
    Downgraded to 11.0 release. And it's slow as molasses on a MacBook Pro
    (2.8 GHz Intel Core i7 with 16GB Ram, Radeon Pro 560 4 GB, Intel HD Graphics 630 1536 MB)


    Sounds more like you have hardware (thermal) issues.
    Have you contacted our support ?
    0
  • NNN636452453518237846
    Hello

    I miss completely the concept of updating in Capture One 11.
    When I see that there is an update of Capture one in the software. I double click the version and then I am redirected to the site of phase one where I have to download a full version C11 and when I open it , I have lost any previous data. I need to import my catalogs manually which is a tedious work..... Since I am a beginner, I have still not many to reimport but soon it will become quite irritating...

    Now I have just downloaded C11.0.1 hoping improvement .

    I double click the icon of C11 and C11 tries to boot but it stays still. I don't even have a launch screen . strictly nothing.

    I use C11 on DB version and I have a Mac Book Pro : 2,3ghz on OS X El Capitan, 16gb ram...

    it seems that my day of work is lost. Is there a way to revert to C11.0000 ?

    thanks for help.
    0
  • John Doe
    After you download the .dmg, you need to open it and then drag&drop the app from inside the .dmg to your /Applications folder. Then eject the .dmg and run the app from your /Applications folder.
    0
  • Paul Steunebrink
    [quote="Frank.O" wrote:
    Hi everybody,

    after reading that the Fuji X-E3 ist now supported by CO 11 I immediately upgraded because that was what I was waiting for. Unfortunately only to learn the hard way that being an early adopter is not always the best thing to do.

    Everything seems to work except for picture import.

    Make sure there is no dot in the file name and that you do not use a renaming scheme that introduces a dot in the file name.
    0
  • Frank.O
    [quote="Paul_Steunebrink" wrote:

    Make sure there is no dot in the file name and that you do not use a renaming scheme that introduces a dot in the file name.

    Ah...yes, thanks Paul, I already know that. A friendly supporter of PhaseOne pointed me in the right direction and I have posted my solution here.

    Regards,
    Frank
    0
  • Stephan Aschemann
    Found a small bug. In the import dialog I have chosen to add "lens" in my naming of the file during import. Captureone adds a dot after the lens. This breaks the naming of the file as the files are now ending after the lens name. the ending dng or jpg gets lost and CO does not recognise the correct file type. Further mistakenly for some new added lenses the name contains a dot at the end of the name which will lead to the same problem even if the developer will correct my above mentioned bug.

    Regards
    Steve
    0
  • SFA
    [quote="Stephan5" wrote:
    Found a small bug. In the import dialog I have chosen to add "lens" in my naming of the file during import. Captureone adds a dot after the lens. This breaks the naming of the file as the files are now ending after the lens name. the ending dog or jpg gets lost and CO does not recognise the correct file type. Further mistakenly for some new added lenses the name adds a dot which will lead to the same problem even if the developer will correct my above mentioned bug.

    Regards
    Steve


    You probably should send this to the C1 team as a Support Case where the problem will be recorded, assessed and managed officially.

    This forum is, officially, for User to User information exchanges.


    Grant
    0
  • Dana Bibeault
    [quote="Ian3" wrote:
    [quote="mmjaeger" wrote:
    wondering whether the import order numbering has been fixed - does anybody know?

    The release notes seemed to say so.

    Ian



    Oh, I must have missed it!
    0
  • Permanently deleted user
    [quote="Stephan5" wrote:
    Found a small bug. In the import dialog I have chosen to add "lens" in my naming of the file during import. Captureone adds a dot after the lens. This breaks the naming of the file as the files are now ending after the lens name. the ending dng or jpg gets lost and CO does not recognise the correct file type. Further mistakenly for some new added lenses the name contains a dot at the end of the name which will lead to the same problem even if the developer will correct my above mentioned bug.

    Regards
    Steve


    As far as I know, this bug has been identified by Phase One, and should find a solution in a next release.
    0
  • rsolomon
    I updated to the new release, all went fine, all working fine with one exception, I had created a custom tool tab, after the upgrade it disappeared - I think. its not that big a deal but did I miss a step in saving this. BTW I did create a workspace
    and that remained across the upgrade, so agin the question is on the custom tool tab

    Thanks
    Rich
    0
  • SFA
    The Custom tools tab exists in the Workspace in which it was saved but as far as I know it is not saved separately for loading into several workspaces.

    It has often been the case that tools have changed quite a lot for major releases and older tabs, standard or custom, may no longer be entirely (or indeed at all) relevant.

    The V11 changes and restructuring of the tabs is a significant example of that. It is likely to be be better to review the functionality and recreate custom tab combinations in most situations IMO.

    HTH.


    Grant
    0
  • rsolomon
    thanks,
    after reading your post I looked in the saved custom workspace and saw my tool tab, still learning and enjoying C1

    thanks again
    0

Post is closed for comments.