Auto export for tethered shoot.

Raymond Harrison/

Again, people dont see that way especially digitechs. Is it really difficult to admit the problem? Probably need to join other community and see what we say cause the performance is just one of the problem. Not able to utilize all performance is already a great proof in terms of computer technology's perspective. Just because they are different doesn't mean not comparable. 

If sending tickets was the way, it wouldn't end up like this. Even now, professionals using C1P always complain how C1P poorly support and optimize despite their efforts. As a result, C1P doesn't really care about professionals for a while instead of focusing on amateurs demands. Cant believe it? Ask digitechs or other professionals. 

368108974477 I definitely agree that comparing the export speed of two different pipelines / code bases is comparing apples and oranges. That said, I was thinking more from a digitech persona perspective, where they have to accomplish an "export task" or an "import task" (or whatever) across different applications in the course of a work-week (or day), it's a consideration and hence why I expect Benjamin is making a comparison. Could be wrong though.

370130554297 As Walter said, most (if not all) of the people responding here are private people who aren't employed by Capture One. We're offering a perspective that reflects our experience. You have yours, which is awesome. I think everyone wants better performance. I mean, who wouldn't? However, to make a blanket statement that another tool is multiple times faster simply doesn't reflect reality. At least my reality and I expect others,, and I do put the application through its paces. If it's your reality - not a youtuber (respected or not) and not someone you've heard about - then the most effective thing you can do is to get logs and a ticket in to the Capture One developers so they can take a look. If your friends are experiencing this, they should get logs and tickets in too. I don't mean the digitech petition I think you've brought up before. Tickets makes a difference. And in this case, comparing times for actions (imports/exports/etc) makes more sense to me than whether an application floods cores (which may or may not increase performance). The more Capture One hears through tickets, the more change can happen. Drama here doesn't change much, I feel. 

No more responses from me.

I don't work for Capture One. I'm a user like everyone else and I volunteer here.

I'm just describing how this difference could have a very legitimate explanation.

Walter Rowe/

That's a stubborn way to say, "we dont care". I am very disappointed. 

378474658737 & 370130554297

It is not realistic to compare export speeds of one app vs another. The apps are entirely different. Their image processing pipelines are entirely different. Their demands on the system are entirely different. If the quality of Capture One is why you use it, the engineering behind that quality might be the very reason it is slower. It may be doing more to ensure you get the best quality.

That’s telling me that Capture One doesn’t use resources as efficiently as it could. We probably all agree to that. What I’m saying is the time it takes to do a task is not multiple times faster on LrC, at least on my systems. Two different stories so no, not “already proven” 😀. What matters to me is my own outcomes on my own systems. Outcome for me is “elapsed time from when I hit the go button”. For me, it’s not poor performance, it’s comparable performance “but I’ll take improvements anytime” and “they can always improve”.

Walter Rowe/ Doesn't justify poor performance. Beside, they both export images. 

Again, the auto export feature while tethering has nothing to do with performance and yet you are changing topic as if Capture One is not slow. 

Raymond Harison/

https://support.captureone.com/hc/en-us/community/posts/9978699539485-Improve-C1P-s-exporting-performance-as-it-does-not-use-all-CPU-powers

Already proven that Capture One is slower. 

To be clear, for me, Lightroom Classic is in no way multiple times faster than Capture One for either import or export workloads. They’re on par for the most part on my systems, with Lr maybe edging C1 for some exports for a mixture of Phase, Nikon, Fuji and Leica files (although I have to export TIFF and JPEGs separately on Lr because of some bug). Don’t point to a youtuber. Measure it on your system. If LrC is multiple times faster, as Walter says, consider a support ticket.

Comparing LR to Capture One export makes no sense. The two programs do things entirely differently. Their engines are different.

Walter Rowe/

https://www.youtube.com/watch?v=HS4Faoa96Ks

It's already discussed here and it's a well known issues for digitechs. C1P is several times slower than LR Classic which is a great proof.

Also, I'm talking about the feature, not performance which is totally different. 

I don't think your statement "poor export performance" applies to everyone. Perhaps this is an issue with your specific system. I have no issues with export performance. I have 2017 Intel iMac, 2019 Intel MacBook Pro, and M3/Pro MacBook Pro. All have excellent export performance relative to expectations for the specific system.

Many things could contribute to your specific performance issue. Can you be specific about your export performance? Can you describe the configuration of your system? What CPU? What GPU? How much memory? Do the files resides on external storage? How is the external storage connected (network, cloud, USB, Thunderbolt, etc)? Is the external storage SSD or HDD?

Have you opened a support case about it?

I support the idea of automatic export while tethering. I would separate that request from complaint about export performance.