Wrong pixel count

Comments

23 comments

  • Klinke
    I posted that question e few days ago direct under the posting above. I didn't get a useful answer - but the posting was deleted !

    Are they really going to show that non working product on the PMA ??
    0
    Comment actions Permalink
  • Ulf Liljegren
    I will try to push to get more information on a time line.
    Give me a couple of days guys!!
    0
    Comment actions Permalink
  • Leif1
    [quote="UlfLiljegren" wrote:
    I will try to push to get more information on a time line.
    Give me a couple of days guys!!


    Thank you for your reply. Ok, I will try to be patient.

    Leif
    0
    Comment actions Permalink
  • Ulf Liljegren
    I have now an answer from Product Marketing group which have set this to be fixed in Capture One 3.7 which is the same release that will include tethered support for Canon EOS's.
    Release date is set to May 2005 (exact date will follow)
    0
    Comment actions Permalink
  • Leif1
    Is 3.7 a free update or do I have to pay for it?

    Leif
    0
    Comment actions Permalink
  • Ulf Liljegren
    It has been decided to be a free update.
    0
    Comment actions Permalink
  • Leif1
    [quote="UlfLiljegren" wrote:
    I have now an answer from Product Marketing group which have set this to be fixed in Capture One 3.7 which is the same release that will include tethered support for Canon EOS's.
    Release date is set to May 2005 (exact date will follow)


    Now we have the RC1 and it have still the wrong pixel count. Do we see a change in RC2 or the final 3.7?

    Leif
    0
    Comment actions Permalink
  • Jorge1211
    I also noticed that the image size was different when processed with sharpening enabled and disabled.
    0
    Comment actions Permalink
  • Leif1
    [quote="UlfLiljegren" wrote:
    I have now an answer from Product Marketing group which have set this to be fixed in Capture One 3.7 which is the same release that will include tethered support for Canon EOS's.
    Release date is set to May 2005 (exact date will follow)


    Now, we have 3.7 and still the wrong pixel count. Also I must read in the release notes to 3.7 that there will be "Currently no work around". Please ask your Product Marketing group when we will see a bug fix for this problem.

    Leif Tobias
    0
    Comment actions Permalink
  • PhotoArtisan
    This critical (to me) bug, is what makes me choose to still primarily use the old Rebel version. I was really hoping this would be fixed in 3.7!
    0
    Comment actions Permalink
  • Jorge1211
    3.7 (final) is still cliping pixels on 20D. Will this ever be fixed?
    0
    Comment actions Permalink
  • jrsforums
    This is very disappointing. I like what I have seen on C1, but, being a 20D user, I have held off buying it until this problem was fixed.

    I had downloaded the trial LE 3.7 to confirm that I would really like it...which I did. However, I will probably have to hold off any purchase until this problem is fixed....it is really an unacceptable problem.

    John
    0
    Comment actions Permalink
  • Leif1
    I can't understand why Phase One don't answer my question. The problem is not new. Why is it not possible to say if your software team work on a fix or not.

    So I ask again. Will we see a bugfix in the near future or not?

    Leif
    0
    Comment actions Permalink
  • Jorge1211
    I don't think they want to reply for some reason.
    0
    Comment actions Permalink
  • Anonymous
    Posted at the top of the Forum is a message regarding Known Issues. The pixel count is one of these. Right now there are several cameras that lose between 2 - 8 pixel rows of information at the edge in processing.

    Please know that I absolutely agree 100% that no pixels should be lost in processing. That said, the common sense in me thinks it really is not a big issue. How often does one Never Crop ?
    Run a test and process images in other software and compare size. It would be a micro fraction of total image lost and insignificant. I believe one can live with a few missing pixel rows in order to get superior image quality overall.

    This seems to not be a big deal to most Users, very few Tech Support Cases involve this problem. Yes there are some Forum posts wanting to know Why and I don't have an answer for this. This issue started with v3.6 and was not a problem before this.

    There is a Technical Feedback… link under Help in Capture One. There are not too many softwares out there that provide this… take advantage of it and let Developers know you are not happy about losing pixels. Input from Users has always been valued and effective. These are the folks that determine what priority an issue has and how to respond by fixing.

    Again, I do understand the underlying premise with the issue, but common sense should overcome.

    Sincerely,

    k c
    0
    Comment actions Permalink
  • Jorge1211
    I never crop. Just for the record. The question was not regarding whether you feel it is significant or not. I think that is for the customer to decide. The question very simply is... is this an issue that Phase One is working on to resolve? The answer could only be yes or no. Thank you.
    0
    Comment actions Permalink
  • Leif1
    [quote="Keith Carpenter" wrote:
    Posted at the top of the Forum is a message regarding Known Issues. The pixel count is one of these. Right now there are several cameras that lose between 2 - 8 pixel rows of information at the edge in processing.


    Nothing new. I already read the "Known Issues".


    Please know that I absolutely agree 100% that no pixels should be lost in processing. That said, the common sense in me thinks it really is not a big issue. How often does one Never Crop ?
    Run a test and process images in other software and compare size. It would be a micro fraction of total image lost and insignificant. I believe one can live with a few missing pixel rows in order to get superior image quality overall.


    It's not the same if I like to crop or the software crop all my pictures.


    This seems to not be a big deal to most Users, very few Tech Support Cases involve this problem. Yes there are some Forum posts wanting to know Why and I don't have an answer for this. This issue started with v3.6 and was not a problem before this.


    The problem was already in the "ReadMe" file. So mabye the people think that you work on this problem and don't inform you about the problem. So maybe it's a big deal.

    And yes, it came with 3.6 and I asked at this time for a bugfix.


    There is a Technical Feedback… link under Help in Capture One. There are not too many softwares out there that provide this… take advantage of it and let Developers know you are not happy about losing pixels. Input from Users has always been valued and effective. These are the folks that determine what priority an issue has and how to respond by fixing.

    Again, I do understand the underlying premise with the issue, but common sense should overcome.

    Sincerely,

    k c


    Why should I inform you developers? They know about this problem and I hope they work on a bugfix (that was promised by your staff with v 3.7).

    I agree with Jorge_Keys the only question is:

    Do you work on a bugfix or not?

    Leif Tobias
    0
    Comment actions Permalink
  • PhotoArtisan
    [quote="Keith Carpenter" wrote:
    This seems to not be a big deal to most Users, very few Tech Support Cases involve this problem. Yes there are some Forum posts wanting to know Why and I don't have an answer for this. This issue started with v3.6 and was not a problem before this.


    That may be because most users may be like me, and don't like to waste peoples time by opening Tech Support Cases for known problems that are supposedly being worked on.

    Let me be perfectly clear. This is a very important problem, that messes up my workflow. It keeps me using an old version for developing the majority of my photos.

    If opening a Tech Support Case will somehow help get this known problem solved faster, just let me know, and I'll open one...
    0
    Comment actions Permalink
  • FlemmingHandberg
    To be very honest - YES Phase One is working on this bug. Whether or not it is significant or not (however i do agree with my colleauge Keith) then it is still a bug and our developers are working on this. In 3.7 some cameras was fixed, some still are outstanding. In 3.7.1 as far as i am informed more cameras are fixed, but i can not promise that eash and every camera is solved, as some have been very tough to fix and require a larger amount of rewriting within the application.

    i hope this is understanable, but for my own sake could someone please teach me why this is significant and what the last 2-8 pixel rows is used for? or is it more a pinciple?

    Thanks a lot....
    0
    Comment actions Permalink
  • Leif1
    [quote="FlemmingHandberg" wrote:
    To be very honest - YES Phase One is working on this bug. Whether or not it is significant or not (however i do agree with my colleauge Keith) then it is still a bug and our developers are working on this. In 3.7 some cameras was fixed, some still are outstanding. In 3.7.1 as far as i am informed more cameras are fixed, but i can not promise that eash and every camera is solved, as some have been very tough to fix and require a larger amount of rewriting within the application.

    i hope this is understanable, but for my own sake could someone please teach me why this is significant and what the last 2-8 pixel rows is used for? or is it more a pinciple?

    Thanks a lot....


    Thank you for the answer. I waited over one month for this information. Now I know that I will maybe see a bugfix for my 10D in the next update. That was the only thing I like to know and for what I ask.

    Yes, 8 pixel are not much. But I don't want to loose any image information.

    Leif Tobias
    0
    Comment actions Permalink
  • Marko111
    [quote="FlemmingHandberg" wrote:
    ..........

    i hope this is understanable, but for my own sake could someone please teach me why this is significant and what the last 2-8 pixel rows is used for? or is it more a pinciple?

    Thanks a lot....


    I have Pentax *ist DS and there is much more crop than 2-8 pixels. In my opinion there is about 10-15% of entire image!

    Is this same problem or is it another issue?

    Thanks for reply.
    0
    Comment actions Permalink
  • Jorge1211
    I am insulted by you lecturing me \"the customer\" as to the significance of a bug. I am 48 years old and have been a photographer for a major part of my life.

    The reason it is significance is, that in Photoshop, actions and scripts are written for precise pixel counts for a given camera. OK buddy??

    I do not like to be patronized when I am forking out the cash for your salary.

    Dig it?
    0
    Comment actions Permalink
  • FlemmingHandberg
    Thank you for the answer.....
    0
    Comment actions Permalink

Please sign in to leave a comment.