![]() That Canon and others might choose to release a new camera (or lenses, etc.) at around the same time just adds to the challenge of balancing resources against unknown needs and externally influenced timing of events. Realistically any release schedule at this time of year (from any multi-platform developer, not just C1) would need to take into account the needs for the latest Mac OS and most often Windows too. If anyone knows of a simpler and more elegant workaround, I would appreciate your guidance. It's much easier to process wildlife images in C1 Pro and keep the end result looking 'natural'. It's obviously a lot a more effort, and you lose some metadata (plus you obviously need access to Lightroom), but I tried going back to Lightroom for post-processing and it reminded me why I made the move in the first place. The fix for this is to apply the ICC Profile 'Canon EOS R Generic' to the imported images, which looks pretty close to the 90D. The trick is to import the 90D CR3s into Lightroom, export them as DNGs, then import the DNGs into C1 Pro.īy default, C1 Pro applies a generic DNG ICC Profile which renders images with all of the colours washed out. The support team confirms lack of support with the usual advice to 'watch this space'.įortunately, I still have access to Lightroom and have used this to implement a workaround. ![]() ![]() Just got the new Canon 90D and found that it is not yet supported in C1 Pro - it doesn't recognise the CR3 files produced by the camera as legitimate images for import. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |