Improve Capture One
Request a new feature, or support for a camera/lens that you would like to use in Capture One.
Request a new feature, or support for a camera/lens that you would like to use in Capture One.
Details: When shooting a mix of stills and video, if I want to do anything with the video, including simply export it for editing, I need to go through Finder (cumbersome, inconvenient, and inconsistent with the way I can access image files with Capture One).
I want to search for ALL items meeting specified metadata criteria, like location, subject name, subject type. Because Capture One doesn't let me enter any of this for video files, I can't find them when searching.
Example: I shoot an event (like a Museum Board of Directors meeting I'll shoot next week). The shoot includes stills and videos of the event. As it stands, I can't add metadata to identify the people in video clips, which is a problem. Another example: I do a lot of bird photography and currently can't add metadata to identify the bird(s) in the video, or add Keywords to identify bird families or other attributes.
Workaround: I currently store all videos in a separate folder, which makes them a little easier to find. This is bad, because it means I'm splitting shoot materials. Also, I have to play each video in Capture One (or Finder) to identify what's needed. Then I can find it manually in Finder and proceed in my video editing program.
When this affects me: In the last year, it's affected me at least weekly, as I'm shooting more video and need to work with it.
Capture One can already catalog video, but that's it. Please add at least 2 capabilities:
1. User-added metadata (this should be as simple as modifying the metadata entries in the catalog database).
2. Export videos. I'm amazed that I need to have Capture One "Show in Finder" and then I need to manually copy/move the file from the Finder. I should be able to export the saved video file from within the catalog.
Note that this request is NOT about editing video; simply enable Capture One to manage it.
Thank you very much for editing the post 370130528417 :)
Hi Abbott,
I believe or at least hope that they have a database with a few fields in which they manage the requests, and yes, the way they gather feedback hasn't matured over time.
Thanks for the compliment, the same applies to you.
Mee too.
How does the new license policy benefits you regarding the macOS updates, the number of free upgrades will reduce. Once a feature update is out, which you don't get without paying, there will be no free bug fix updates anymore.
At least that's what they say, but maybe, if an OS update breaks a C1 version they will give you newer version (maybe within a two year period since purchase date) for free in order to avoid a shitstorm and in order to comply with EU law. Or, they will abandon perpetual licences altogether, in two years or so from now.
We'll have to wait and see, and complain once in a while to show them there is a part of their customers which they pushed away or pushed to circumvent their intentions behind their licence policy changes.
Cheers,
BeO
Hi BeO,
Thanks for your comment. Actually, I believe that if they're looking for "structure, then your thought about Zendesk a better approach than free-handing text into a single "feature request" field. I wonder why Capture One doesn't just create a simple online form for user input. They've done it for Support Requests, and a Feature Request form should be straightforward, simpler than Support, and would ensure that they get feedback in the format they want. Also, I'll bet that a form (which presumably would actually consist of several fields in a database) would make it easy to group and summarize requests. I still write databases as a hobby (OK; I'm "different"), and it's trivial to retrieve the data I'm after as a result.
I still believe that if you really want customer input, then you make it easy for the customers to provide it. Support Requests demonstrate that somebody at Capture One knows how (or used to know how) to do that.
As for the slap they just gave us perpetual license customers, frankly it ends up not affecting me. I used to upgrade annually regardless of what the new features were, and in the past 2 years or so have been more pleased in the mid-year feature additions than in the original release ones. The new policy actually ends up reducing my cost-of-ownership, as there's no longer an incentive to upgrade annually. Now I'll wait until they release a feature that I really want.
And as a Mac user, an indirect benefit is that I don't have to worry so much about a macOS update breaking something else in my ecosystem. Unfortunately Apple tends to mess with OS underpinnings that have unintended consequences for third party applications. I just got dinged when I was forced to upgrade to Ventura 13.2.1 (which broke a couple of apps) because I bought a new Mac. And I'll be seriously impacted when Apple drops Rosetta 2, as too many of my important apps haven't yet been rewritten for Apple Silicon.
Anyway, thanks for your comments. Also, I think you've been an excellent contributor to Capture One forums over time.
Abbott
Hi Abbott,
I only wanted to quickly explain my workaround, I'd rather like to have video files supported as you requested, hence I upvoted. No need to convince me.
For your second response, I'm still in that business. And I suggest that the requested structure of the new forum topic posts is derived from someone who knows something about requirements engineering. That makes is easier and more efficient for them and that's ok for me if they are overwhelmed with requests and / or are understaffed, which I assume both is true.
I am more unlucky about the fact that this is already the third approach to get user input, (1) submit a request form, (2) Feature Request topic in this forum and now (3) the new forum topic, and it does not appear to be any better (I believe there is better software out there for that purpose than the zendesk forum), I don't even know yet if I really want to post my requests a third time. Especially given the slap in the face for perpetual license customers.
Cheers
BeO
BeO, just to add, I was an engineer and tech guy for several decades. I had input to several industrial apps' user interfaces, interacted with [international] customers with varied levels of technical know-how, participated in other companies customer advisory boards, and have taught photography classes and led workshops for about a decade.
When I genuinely want "customer" input/feedback, I don't put up barriers. I am the one who's asking for input, and I view it as my "job" to translate customer/client feedback into actionable items for myself (now) or engineering teams (in the past) to accomplish. It seems to me that there's a disconnect between how I've worked with customer input and how Capture One wants to. That's their choice. But in my experience, putting up barriers like "you've got to give input exactly the way I want to see it" too often results in missed opportunities, irate customers who think you don't really want to improve, and evolving products that don't excite customers and entice them to "buy more". It results in marketers having to work harder to explain to customers why the features they didn't think they wanted are really super important. While that's worked for Apple, it's far from universally successful (in my experience).
Sorry for the rant, but I passionately like Capture One, have introduced a number of clients and friends to Capture One (and they're now passionate about it), and I want to see Capture One be fabulously successful. I wanted to provide input for something simple that's missing, and have learned a valuable lesson as a result.
Thanks BeO; I appreciate your thoughts. Frankly, I've spent enough time on this. I've seen enough comments in other forums indicating that I'm not alone in wanting better support for video files, and the metadata comment is the one I've seen the most.
Your idea's OK, but in the end adds more user work to get the same result: to export a video, I still need to go into the Mac Finder and edit/export/whatever the file from there (I assume that Windows has an analogous process). Your idea does provide a workaround for associating metadata with a video as long as the proxy file never gets separated from the source video. However, the workaround still won't let me search for a video using metadata, because the metadata isn't directly associated with the video.
Another workaround would be to create a separate catalog for videos, and organize the video files on-disk into folders that reflect what the metadata might have been. However that, too, is awkward and permanently separates video and still files that were shot for the same project. Fixing the metadata fields in the database to allow entry regardless of the filetype "should" be trivial, and so should the ability to export original video files. It's not like Capture One doesn't do this already for other types of files!
Given that some metadata issues have existed since I started using Capture One (v8), I've concluded that Capture One has decided to focus their resources elsewhere. Their customer focus seems to be on photographers other than nature/wildlife (that's me), and focusing on improving Capture One's editing capabilities may be the right thing for them to do. Oh well, at least I tried to provide some constructive input.
+1 upvoted
Abbott, there is another way to work around the metadata part or your request. You can work with a 'proxy' image file, i.e. extract an image file from your video (e.g. on Windows with the app "Photos"), give it the same name but add a suffix (for ordering by name) and assign metadata to that image. This is far from being a real substitute of your request though but maybe helps a bit.
It allows you to find the video by first finding the proxy image via metadata search.
Hi Abbott,
I believe what is missing to match the requested format are the paragraph headlines:
What problem do you see this solving?
here comes your text
When was the last time you were affected by this lack of functionality, or specific tool?
blabliblub
Are you using any workarounds or other solutions to achieve your goals in Capture One?
loriseptum nobilis
Are you happy to be contacted further about this suggestion or request?
Yes
Actually, I had read the referenced post and thought what I wrote complied with it. Also, after watching David's webinar yesterday, I tried to find the "Feature Request" tab and failed. He went over it so quickly that I missed the URL (I should have made a screenshot).
I'll try what you suggest, and maybe I'll meet the post criteria.
Your post has been hidden for moderation. Please read the pinned post and use the template provided.
You can edit your post by clicking the "gear" icon on your post and then selecting "edit".
I understand that rules and guidelines are annoying, but it has to be this way in order to make the requests and feedback usable by our Product Management team, and to ensure that you get the response you deserve.