Zum Hauptinhalt gehen

Canon R5 C Support

Kommentare

19 Kommentare

  • Philippe GAUDENS

    Hi. Very frustrating indeed !
    I recently shot for a company and I'm stuck with all my CR3 from my brand new R5 C.

    0
  • Bernd Kusen

    I agree.

    The only way is to use the native Canon software or switch to Lightroom. Very sad.

    0
  • Keith R
    Top Commenter

    I recently shot for a company and I'm stuck with all my CR3 from my brand new R5 C.

    Here's a trick which I guarantee will make such problems a thing of the past:

    Don't buy your new camera until you know that Capture One supports it.

    Simple and fool-proof.

    The only way is to use the native Canon software or switch to Lightroom. Very sad.

    Nope.

    Anything stopping you from converting the R5 C's files to DNG and processing them in Capture One?

    Oh - and anything stopping either of you from doing something useful and posting in the Feature Requests forum, rather than complaining about your problems in this forum?

    For example (and it's not the only one):

    https://support.captureone.com/hc/en-s/community/posts/5175284149021

    -3
  • Bernd Kusen

    Don't buy your new camera until you know that Capture One supports it.

    Simply no. I love Capture One but I will not buy my camera depend on it.

    Anything stopping you from converting the R5 C's files to DNG..

    Sounds to be a good idea. But how will I do this? Canon Software does not convert to DNG.
    Anyway this will not solve the problem that tethered shooting with R5C in Capture One does not work.

    anything stopping either of you from ...posting in the Feature Requests forum...

    I already contacted Capture One support. They answered that they are working on it. 1 month ago.
    This should be useful enough.

    As you see I'm not just complaining about my problems. I started this thread with a factual question and also  suggested solutions (use Lightroom instead). But it IS frustrating when you once bought a software thinking that they will keep it up to date for the latest camera models.

    0
  • Philippe GAUDENS

    Keith,

    Please don't be condescending!

    I already know that Adobe DNG converter allows to convert CR3 files from R5C to DNG.

    Saying I'm stuck is not real, I admit. But, when you pay a license for C1 and the competition is up to date far before your favorite software, it IS frustrating. And I don't want to pay a second licence to cover that. I expect PhaseOne to work closer with camera brands to be up to date in the mean time cameras are released.

    Posting our complaint in Feature Requests forum is a non sense! Support of new file types is not a "new feature" in itself.
    And, sorry to tell you that, but would you really have think that R5C files wouldn't have been supported while R5 files was ? Really ?
    No R5C user has anticipated that CR3 files coming from so close camreas would be different! Still pictures part of R5 and R5C have been said to be strictly the same, by CANON itself.

    Please keep your sarcasm and be polite. We are not kids complaining for their toy.

     

    2
  • Kassur

    Have you try to use exiftool? You can change the camera name of the raw files to something C1 accept.

    Old trick for new Nikons :-) should work with Canons too.

    Kassur

    1
  • Keith R
    Top Commenter

    Please don't be condescending!

    I'll stop when people like you stop posting lazy, entitled, half-arsed posts that don't reflect reality at all, and point directly at you as "The Problem". 

    Posting our complaint in Feature Requests forum is a non sense! Support of new file types is not a "new feature" in itself. 

    Tell Capture One that - this is precisely how camera support requests work, and  how it has been since Capture One 3.7 at least. 

    Please keep your sarcasm and be polite. We are not kids complaining for their toy.

    That's exactly what you're doing - you get the response you deserve.

    Be clear about this: Capture One owes you nothing with regard what you think its camera support priorities should be: it's certain they're working on the R5 C, but that's all you're entitled to - the knowledge that support will come sooner or later.

    Are you really so arrogant that you assume nobody has been in this exactly same situation before?

    I remember posts about Canon 30D support being later than some user thought was acceptable, and the answer he got is exactly the same kind of answer you got - wait, and stop assuming that the world revolves around you

    Did Capture One force you to buy and use the R5 C? Did they keep the lack of support a secret from you?

    -2
  • Bernd Kusen

    Kassur

    Have you try to use exiftool? You can change the camera name of the raw files to something C1 accept.

    Thanks for the advice but I rather use Lightroom instead of a command line tool for converting. Renaming to C1 unfortunately didn't solve the problem. But it was worth trying.

     

    0
  • Philippe GAUDENS

    I'll stop when people like you stop posting lazy, entitled, half-arsed posts that don't reflect reality at all, and point directly at you as "The Problem". 

    My reality is that I'm allowed to say I'm frustrated, even if "your reality" can't deal with this. Who are you to insult me that way ?

    Tell Capture One that - this is precisely how camera support requests work, and  how it has been since Capture One 3.7 at least. 

    Capture One is a professional tool (I hope your reality won't deny it). In this perspective, professional photographers are allowed to expect a reactive support. I would add that: camera support should even come "before" the camera release on the market. I assume camera brands on a side, and C1/LR on the other side should anticipate by working together. It would be win/win for everyone and it would prevent to break photographers workflow. Lots of companies do it that way: Apple give all their phone dimensions to accessories dealers far before they release them. nVidia gives graphic card samples to game developers.

    I don't only blame Capture One. I mostly blame CANON for saying R5 and R5C have the same still camera, which leads to think their RAW files are strictly the same while they are not.

    Be clear about this: Capture One owes you nothing with regard what you think its camera support priorities should be: it's certain they're working on the R5 C, but that's all you're entitled to - the knowledge that support will come sooner or later.

    Each one puts his expectations where he wants. And I obviously know Capture One are working on R5 C, but as it is not a whole rewritten new RAW image format, but a minor change from CANON which has been qucikly handled by Adobe, YES, I expect C1 to deliver an update as fast as Adobe has been able to do.

    Capture Ones owes me nothing... Hmm... No customer, no company....

    Are you really so arrogant that you assume nobody has been in this exactly same situation before?

    I'm not arrogant. For example, CANON 5Ds and 5DsR didn't encounter this file format problem if I well remember. After CANON saying main differences between R5 and R5 C are IBIS and video features, YES I bet each R5 C buyer could never think still images format would be different fur such similar cameras.

    So I repeat, posting in Request Features forum is a non sense, as new camera file support is something obvious and not a new tool or new functionality.

    I remember posts about Canon 30D support being later than some user thought was acceptable, and the answer he got is exactly the same kind of answer you got - wait, and stop assuming that the world revolves around you

    For sure I can't do anything else but wait. Saying I'm frustrating doesn't mean I'm not patient. Don't mix both things.

    Did Capture One force you to buy and use the R5 C?

    Did anyone force you to read this thread ? We can play a long time to this stupid questions game....

    Did they keep the lack of support a secret from you?

    If you can't understand what I said earlier (R5 support meant R5 C support to me and regarding CANON says), I can't be more explicit.

    2
  • Bernd Kusen

    I agree with you, Philippe. But don't feed the troll.
    Finally the market will take care of it.
    Better let us search for other solutions or workarounds than discussing with someone who is not open for factual arguments.

    2
  • Jakob Frank

    Have you try to use exiftool? You can change the camera name of the raw files to something C1 accept.

    Thank you for this hint!

    Thanks for the advice but I rather use Lightroom instead of a command line tool for converting. Renaming to C1 unfortunately didn't solve the problem. But it was worth trying.

    I can confirm, that C1 works properly with the R5C RAWs, if you change the EXIF information with exiftool.
    After a little digging, this command did the trick for me:

    exiftool -model="Canon EOS R5" -CanonImageType="Canon EOS R5" -CanonModelID#="0x80000421" DIRorFILE

    If you don't want exiftool to create backup files, use this command:

    exiftool -model="Canon EOS R5" -CanonImageType="Canon EOS R5" -CanonModelID#="0x80000421" -overwrite_original DIRorFILE

    I used the C1 demo to try it out. As soon as the R5C is fully supported, I will buy the new version...

    1
  • Philippe GAUDENS

    Thanks a lot for the input. I'll give a try
    Converting from CR3 to DNG leads to weird colors in C1... Skin tones are flat, and colors don't have the CANON style I have with my 5DsR. It's a big loss of time trying to correct, trying to get something normal.

    0
  • Philippe GAUDENS

    Hello. Thank you very much for this amazing trick to change imageType and model !! It works like a charm!

    I struggled with color problem after CR3 R5 C convertion to DNG. Colors are just horrible and made me to loose time fixing by grading them.

    Changing image type and model name allowed me to get the expected result in C1.

    On the left is the CR3 tweeked by ExifTools, and on the right is the DNG conversion.

    This experience makes me think I'm allowed to complain about C1 not yet supporting CR3 files from R5 C, while it is obviously a simple field to handle in EXIFs !

    0
  • Jakob Frank

    Glad that I could help! I also don't see a reason why C1 still isn't supporting R5C - CR3 files.
    I don't know if there is a problem with implementing tethered shooting (but I guess it should be pretty similar to the R5), but at least C1 should support opening the CR3 files in the meanwhile...

    0
  • Stuart Matthews

    I downloaded the new update today but still no support for Canon R5C. Any news of when this will be happening?

    0
  • Kassur

    Read the release notes. It should be supported now. 

    https://support.captureone.com/hc/en-us/articles/5461293415197-Capture-One-22-15-3-release-notes 

     

    Kassur

     

    0
  • Stuart Matthews

    Dream! so good. thanks!

     

    0
  • Philippe GAUDENS

    Yes it is now supported. But they didn't update the files support page yet.

    0
  • Bernd Kusen

    After a lot of complaints I just want to say "Thank you" to Capture One.
    It works fine and Capture One is simply the best for tethered shooting and RAW file editing!

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.