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. ⚠️

Crop ratio bug?

Comments

11 comments

  • Dangerous Lee
    In CO7 none of the crop ratios worked for me. They all acted like unconstrained.
    I upgraded to CO8 and they work finally. I have a list of ratios including "Original", 2x3, 3x4 etc.. and they all seem to work. I am on Yosemite and CO8 Full. Hopefully, someone has some help for you because I know how annoying this problem can be.
    0
  • SFA
    FWIW


    Running on Windows I have never seen this sort of problem. I would guess it is something installation specific perhaps to do with permissions? (Not something one has to be too aware of with Windows these days for a single user per machine installation. Hence my guess.)

    Hope this helps you on some way to discover where the problem originates.



    Grant
    0
  • Paul Steunebrink
    [quote="DFM" wrote:
    Yosemite /CO 8.0 (trial)

    I almost gave up on my recently purchased CO 7.xx.xx due to various bugs - the fact that I'm a litle annoyed to have to purchase a new version already after just a few months aside, the problems seems to continue:

    First, I encourage you to trial CO 8.0.1. Second, Yosemite is not yet supported. With OS X Mavericks I do not have this issue.

    If you have complaints, that's all right. But complaining while using an unsupported OS is not. It is OK to experiment with Yosemite, but let it be an experiment.
    0
  • Ario
    I do not think it is a Yosemite issue, I run CO 8.01 on Yosemite on a MBP I use for testing and I do not have such a problem (all the crop options are there, all active).
    0
  • DFM
    [quote="Paul_Steunebrink" wrote:

    First, I encourage you to trial CO 8.0.1. Second, Yosemite is not yet supported. With OS X Mavericks I do not have this issue.

    If you have complaints, that's all right. But complaining while using an unsupported OS is not. It is OK to experiment with Yosemite, but let it be an experiment.


    FYI I tried it on Mavericks prior to the Yosemite upgrade and I have since my post upgraded to the CO 8.01 version with no different result. I'm on the trial version here simply because I'm not at all convinced I will purchase this version due to the experience I had with the 7.x versions - even on a clean install Mavericks it just didn't work properly, with poor window handling and general instabilities, which I see also a few others reported.

    As for Yosemite being unsupported, there is no mentioning of this anywhere - the download links states "Requires Mac OS 10.9 or later / Windows 7 or 8.". So where do you find that the Yosemite is "unsupported" ?

    [quote="SFA" wrote:
    FWIW
    Running on Windows I have never seen this sort of problem. I would guess it is something installation specific perhaps to do with permissions?


    Yes, this was my initial guess too, but running to through the permissions checks in the os has not helped solving the issue.
    0
  • Permanently deleted user
    https://dl.dropboxusercontent.com/u/144211/Capture%20d%E2%80%99%C3%A9cran%202014-10-21%20%C3%A0%2011.29.14.png

    Capture One 8 et Yosemite 😉
    0
  • SFA
    I think then this is one of those strange situations, also sometime seen with Windows of course, where something for some reason does not get set up as required during installation and therefore presents the user with a number of problems that other users do not experience. Worse still if they are not at all obvious in the report logs but the logs can only report generically or based on the encoders previous experiences or guesswork about likely problems - a constantly moving target in the "agile" computer world we have these days.

    There are several threads running about OS updates - mostly Mac centric. It always happens when an update is released. Here is an example.

    viewtopic.php?f=55&t=17356&start=0#p82496


    From personal experience over the years I usually try to avoid any releases, OS or application, to a production environment until I have some idea of what they are like from user feedback. If I am testing for someone or have a spare device on which I can run tests without risking a full production environment then I join the throng discovering the latest features and functions but I really try to steer clear of anything new where a glitch of some sort could cause problems.

    Using Windows the Crop ratio definitions are held in a specific folder in the application data area. I assume it will be something similar on a Mac. I'm not minded to mess around with my system at the moment being in the middle of processing a large project but my assumption would be that if that folder did not exist or was not populated with definition files or was simply not accessible then you would see the greyed out options that you see and the presets would also be absent of course.

    Have you in the past raised a Support Request with Phase One in an attempt to get to the bottom of your problems in V7 (or V8)? If not I would think it would be wise to do so in order to identify the reasons for your problems. Finding the root cause might be more challenging, there being so many possible factors and actors to consider.


    HTH.


    Grant
    0
  • DFM
    [quote="SFA" wrote:
    ....

    Have you in the past raised a Support Request with Phase One in an attempt to get to the bottom of your problems in V7 (or V8)? If not I would think it would be wise to do so in order to identify the reasons for your problems. Finding the root cause might be more challenging, there being so many possible factors and actors to consider.

    ....


    I have done this as recently as having a support case "solved" mid August. The "solved" result was

    [quote="tech support" wrote:
    "Hi - we can inform that we have solved the issue and this will be present in a major comming release of Capture One - we cannot say when the release will happen for now.



    This means I will have to purchase the fix to my problems. Not so very impressive really and I have given up on ver 7.2.3 ( I think it was) completely. CO8.x is the last attempt I'm going to have at CO and if this 8.x version also has its base functionality bugged down randomly on a "per user" level, I'll have to consider my options here. For whatever strengths CO has, it's only worth so much hassle.

    Let me just add that I have a feeling it is missing the target to start discussing Yosemite vs Mavericks in all of this - I have no issues with any other software I have, just CO. I think any problems encountered here are CO only and not the OS itself...
    0
  • Doug Peterson
    I agree with the previous poster.

    Yosemite is not yet officially supported. If you want to evaluate C1 you should do it on an OS which is supported (10.9). If you want to play or experiment with unsupported OS+C1 combinations you are of course feel free to do so, but I would not draw any conclusions from it.

    Most other software is not going to be as deeply intertwined with the OS as Capture One is. It is high-grade software with advanced memory, disk-usage, and graphics cards code which often relies on OS technology (e.g. Open CL and memory handling). The fact that you're not having "any problems with any other software" is not necessarily meaningfully related to C1.
    0
  • Permanently deleted user
    I am running Mavericks and have this issue on Capture One 8. I also had it on 7, but installed an older seven, then upgraded.

    There is a glitch somewhere and I need mine fixed.

    Any help would be great.
    0
  • SFA
    [quote="NN635403414647372650UL" wrote:
    I am running Mavericks and have this issue on Capture One 8. I also had it on 7, but installed an older seven, then upgraded.

    There is a glitch somewhere and I need mine fixed.

    Any help would be great.


    Based on previous posts in this thread it seems that some people have problems but most do not which suggests that the problem, whatever the cause, is limited to the specific machine(s) in some way.

    I would recommend creating a support case so that Phase One Supporters can have the opportunity to take you through relevant checks of what has or has not been installed satisfactorily on your machine and perhaps identify why things may go wrong.

    On the basis of what has gone before there is no clear User provided remedy known to those Forum Users currently active here. So a Support Case makes sense (in my opinion.)


    HTH.


    Grant
    0

Post is closed for comments.