C1 version 11 is out
C1 Version 11 is out and now we are waiting again for an update of Media Pro ☹️
0
-
+1 0 -
Don't hold your breath on that one 0 -
Oh that sounds ominous. I am not yet a customer but am coming from LR. I have been reading up on Capture One and feeling like its cataloguing capabilities are not quite where I would like. So today I started reading this form and the feature list for Media Pro and watching the C1 Media Pro workflow videos here https://www.youtube.com/watch?v=UPw7fNURlSY
Shouldn't MP just work with the version of C1 installed on your computer? Sounds like that is not how it works. How long did it take to get an update to MP when version 10 came out?0 -
[quote="IanL" wrote:
How long did it take to get an update to MP when version 10 came out?- Dec. 01, 2016: Capture One 10 released
- Jun. 27, 2017: Media Pro 2.2 with support for Capture One 10 released
That's a seven month gap with compatibility. Looks like Capture One has an annual, paid update early November and, maybe, Media Pro in late June.0 -
That is bad! My current assessment is that C1 is not quite a perfect fit for my catalogue needs which meant I started looking at Media Pro. This kind of thing really will not work well for me. At least not at the starting point.
I might have to consider making do with just C1.0 -
[quote="roberte" wrote:
That's a seven month gap with compatibility. Looks like Capture One has an annual, paid update early November and, maybe, Media Pro in late June.
Thanks for the history lesson.0 -
Another way to look at it is when Media Pro is updated you get five months compatibility with the current version of Capture One before it is upgraded and they no longer sync. 😄
More history? I reckon Phase One has a small, highly skilled team of software engineers. Their priority is for the flagship product and supporting their cameras.
Capture One needed DAM to compete with Lightroom and Aperture. For over five years Phase One worked closely with iView Multimedia and then Microsoft for a workflow solution. When Microsoft decided photography isn't part of their core business Phase One acquired Expression Media, probably for a song. Note: when Microsoft acquired iView in 2006 they also employed their top personnel and the latter was the real treasure. Phase One however only acquired the software.
The assumption was Phase One could cut out the DAM parts and graft it onto Capture One. While I'm not an engineer I doubt that would have ever been possible. Phase One slowly adds DAM features to Capture One.
The original iView team really understood DAM and photography. More than Microsoft did, more than Adobe thinks it does and far more than Phase One can. Too be fair Adobe and Phase One were light years ahead of the old iView team when it came to raw imaging processing. Being a small company iView Multimedia also couldn't compete with Lightroom or Aperture so they needed to be bought out for MediaPro to continue.
We are lucky Phase One acquired Media Pro back in 2010 otherwise Microsoft would have simply written it off. While I still use Media Pro weekly the DAM landscape has moved on since 2004 and it's no longer my main digital asset management application.0 -
@roberte
What is your main DAM today?0 -
[quote="Nordlicht" wrote:
@roberte
What is your main DAM today?
Lol, I was going to ask the same question....0 -
[quote="Nordlicht" wrote:
What is your main DAM today?
Lightroom.
Of course every photographer's requirements are different, mine is having family images accessible long into the future. For others it may be:- Working in a multiuser environment
- Using bleeding edge raw processing
- Speed of processing
- Access to their images anywhere
- A perpetual software license
- Etc,
0 -
[quote="roberte" wrote:
[quote="Nordlicht" wrote:
What is your main DAM today?
.... accessible long into the future. ]
Do you use C1 for developing RAW files? I've today a problem with LR under the aspect "accessible long into future".
Will we have this in practice without abo?
Is Mediapro your Backup DAM? How do you handle this?0 -
[quote="Nordlicht" wrote:
Do you use C1 for developing RAW files?
Yes when needed. I use DNG so that's the main feature and Capture One has good support.[quote="Nordlicht" wrote:
I've today a problem with LR under the aspect "accessible long into future".
Not at all. As a DAM Lightroom is usable even if you end your paid Adobe subscription. The "only" parts that stop working are Maps and Develop. No your raw edits don't come across (Capture One does a reasonable job of interpreting them though) and neither do Virtual Copies, History, etc. But IPTC metadata does and of course EXIF. Same for Adobe Bridge.[quote="Nordlicht" wrote:
Will we have this in practice without abo?
Adobe? My DAM set up is independent of any manufacturer. I learnt that the hard way using Extensis in the 1990s not to put my trust in one company.[quote="Nordlicht" wrote:
Is Mediapro your Backup DAM? How do you handle this?
Media Pro reads all the industry standard metadata I've entered in Adobe apps. It is a back up solution if I ditch Adobe.0 -
[quote="roberte" wrote:
[*]Working in a multiuser environment
Can you explain this a bit please?0 -
[quote="RobiWan" wrote:
[quote="roberte" wrote:
[*]Working in a multiuser environment
Can you explain this a bit please?
Working with shared catalogs.0 -
[quote="roberte" wrote:
Working with shared catalogs.
Shared like saved on network drive? You can use this catalog at the same time only from 1 person with RW permissions.0 -
In theory yes, but not in practise especially in a multi-platform environment. The safest method is to have each user install the catalog on their computer pointing to shared assets. Windows and Mac catalogs point to different paths in the same catalog so I've had to make a Mac one then open in it on Windows and reset the path to the top folder.
Expression Media had (better) shared catalogs on the roadmap, naturally being a Microsoft product at the time, but it never saw the light of day. Nowadays I'd recommend a web browser interface for ease of use cross platform compatibility. Something like Extensis Portfolio.0
Post is closed for comments.
Comments
16 comments