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.
What problem do you see this solving?
Flickr is standard de facto for sharing creative work online for both amateur and professional photographers. It would be great to see C1 Flickr support out of the box, as it's implemented in competitor's products already - Adobe Lightroom or DXO PhotoLab (also see this wonderful alternative plugin for Lightroom - http://regex.info/blog/lightroom-goodies/flickr).
When was the last time you were affected by this lack of functionality, or specific tool?
All the time.
|
Current workaround
Are you using any workarounds or other solutions to achieve your goals in Capture One? Currently I'm publishing from Lightroom (with Jeffrey Friedl's plugin). It's a two-step process, and is a real hassle. |
I personally use photomechanic. Final images exported from C1 can be opened directly into PM and from there they can be uploaded in a variety of formats to many different Web sites and clients, and PM handles Flickr addressing, album creation adding metadata etc seamlessly.
388362679437
You seem determined to convince us this is Capture One's responsibility. It is not. They provide the publishing plugin SDK. The social media sites can leverage that and their own API to make a plugin for Capture One. I am sure Capture One would be willing to help and coach them.
>> So, that does mean that any party can utilize the public APIs from both C1 and Flickr and create a plugin, right?
Finally...
>>Do you see the author or a copyright hint for the Glass plugin in the C1 preferences?
No, I don't, because I don't have Glass plugin.
>>Btw, the more you convince me that C1 staff would be needed the less likely I am going to upvote :-)
I'm not convincing anybody, I just explained how it usually works. Sapienti sat.
388362679437
Well, Smugmug has such an app (albeit only for Mac use), presumably Flickr could work with whoever they need to at SmugMug to make progress with such an App?
Out of interest, does anyone know how many people use the Smugmug plug-in?
So, that does mean that any party can utilize the public APIs from both C1 and Flickr and create a plugin, right? Surely with at least permission of C1.
This party can of course be C1, Flickr or any 3rd party, correct?
Do you see the author or a copyright hint for the Glass plugin in the C1 preferences?
Btw, the more you convince me that C1 staff would be needed the less likely I am going to upvote :-)
*sigh*
Capture One SDK is intended for creating integrations with Capture One. It's just one side of the process.
Let me quote C1 API documentation, IPublishingPlugin interface description, in particular:
"The protocol allows plugins to implement publishing capabilities. Publishing plugins are plugins that take the path of processed variants as inputs, publish them to a remote service and produce a PluginActionPublishResult upon successful completion. This protocol defines the action and result layers in the Action-Task-Result paradigm, for publishing plugins. Plugins that adopt this protocol provide PluginAction definitions that Capture One uses to populate its UI, allowing users to start the tasks required by those actions."
So, to interact with that "remote service" plugin uses the service API, in this case, Flickr - flickr.com/services/developer. Plugin basically acts like a black box to C1, wrapping all REST API interactions with the service, and communicates with Capture One by using documented SDK interfaces (public interface IPublishingPlugin : IFileHandlingPlugin), and implementing required methods (e.g., GetPublishingActions, that returns a collection of possible PluginAction's, depending on the service used).
Flickr developers don't need to build plugins for every app out there, they already provided all the interested parties with open API (and that's the point of APIs). It's up to C1 devs (or any other enthusiasts) now to implement required publishing functionality.
Yes, I think think so too, heavy lifting on the 3rd party side.
from
https://support.captureone.com/hc/article_attachments/360010792917/capture-one-12-0-4-release-notes.pdf
I have nearly 40 years of experience in this field I know exactly what I am talking about. Capture One has a plugin SDK they can use.
>>Those plugins are likely written by the social media companies and not the app owners
No, they are not. Have you ever used any open REST/GraphQL API in your code?
Walter, please stop writing about topics you have no idea about. You made your point.
369260519517 .. people see social media publishing plugins in other apps and then want Capture One to do it too. Those plugins are likely written by the social media companies and not the app owners. This is why I am advocating for people to ask Flickr to do this. I bet Glass did the heavy lifting with Capture One's help.
The reason you see those plugins in other apps is because those other apps have huge market shares and the social media companies feel the return is worth the investment. With Capture One being a fraction of the market size of some other apps the social media sites likely don't see the return worth the investment to do a plugin for Capture One.
One company that previously supported Capture One removed their plugin.
I was very surprised about the Glass integration.
But I guess I am not the only one who does not see C1 as an image publishing system to (maybe hip but) proprietary website. I see it rather a raw converter/editor, and maybe a photographer-client conversation tool about photo shoots, which is missing much even in its core functionality.
No, I don't.
I explained why in the comment above, but it's still shown in Pending state (because of hyperlinks, I guess)...
@syborg .. you need to ask Flickr to do this.
@SFA I don't mean just automated uploads, I mean full integration (collections mapping/sync, ratings/comments retrieval etc.).
What sort of integration are you seeking?
I note that Flickr's other half, Smugmug has a C1 plug-in app. Mac only though.
From what I can see Flickr operates on a watched folder basis, much like Onedrive for example.
So in theory the basic upload is just a matter of making outputs to a specific folder or folders that are being watched by Flickr.
I have not user Flickr for years. I think it came free with an internet service at one time. Probably Yahoo, But then that option disappeared when Yahoo UK was subsumed into BT. Or something like that.
I wonder if my account still exists? Probably not.
There's such thing in software development world as API. Most of the free and commercial services/products have open APIs allowing developers to build integrations. Flickr is not an exception - https://www.flickr.com/services/developer. There's no need to 'pursue' anybody.
The Glass plugin was probably written by Glass. If you want a Flickr plugin you should talk to Flickr.
It would be great for Capture One to pursue Flickr to do this.
If only the entire process up until export was already polished and covered all possibilities... what happens after is not C1P's responsibility, so I don't understand viability of spending resources on post-export actions in light of numerous improvements that did not fit into backlog despite high count of votes, that would have an effect on WHAT is exported and using how much effort, which is primary focus of the application.
Presumably one could write an AppleScript script to do this. Maybe I'll have a go; clearly, it's not going to be built-in anytime soon.
I also don't understand, why prioritize support for some exotic hosting services (and for Mac only) not noticing an elephant in the room.