Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support custom image viewer for Preview feature #732

Open
bcipriano opened this issue Jul 23, 2020 · 5 comments
Open

Support custom image viewer for Preview feature #732

bcipriano opened this issue Jul 23, 2020 · 5 comments
Labels
feature request New feature triaged Issue has been screened and prioritized by a project lead

Comments

@bcipriano
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
The "Preview Main" and "Preview All" features in CueGUI only support Katana currently, by opening a web browser to a local instance of Katana. We should support a custom image viewer (e.g. RV) for displaying these previews.

Describe the solution you'd like
Add a new config value to the CueGUI config file which can be used to provide a template command used for opening image previews.

Describe alternatives you've considered
N/A

Additional context
N/A

@bcipriano bcipriano added feature request New feature triaged Issue has been screened and prioritized by a project lead labels Jul 23, 2020
@bcipriano bcipriano added this to To do in OpenCue Backlog via automation Jul 23, 2020
@donalm
Copy link
Contributor

donalm commented Apr 2, 2021

I looked into implementing a feature for our studio that would allow a user to right-click on a layer and choose "Preview Frames". I couldn't find a way in the API to get the command (layer.str_cmd) from the API.

We don't use the 'outputs' on the Layer API. I've tested it, but I can't see where the data is going, if anywhere. So our 'layer_output' table is empty - should we be populating that somehow? It seems like the str_filespec field would be a good home for data that would facilitate preview.

The Layer's add_output method accepts a name and an output that get added to a dictionary. This could be very helpful in constructing a menu that offers the user a preview of the different output sequences of the layer by name, but I'm not sure how that would translate into the layer_output table, which doesn't have a name field.

Is Outline the optimal API for us to use to construct jobs? Should we be using pycue/opencue?

Thanks

DJM

@bcipriano
Copy link
Collaborator Author

In general outline needs to be used to construct jobs, yes.

I agree that it sounds like the layer outputs is what we need. Let me look into this a bit more to see what's going on there.

@donalm
Copy link
Contributor

donalm commented Apr 8, 2021

Thanks Brian.

@bcipriano
Copy link
Collaborator Author

This is still a desired feature. If possible we should schedule it for development once the current round of work is completed.

I haven't had a chance to dig into the layer outputs issue.

If anyone is out there who is looking for a standalone task to work on, this would be a great option.

@lithorus
Copy link
Contributor

lithorus commented May 7, 2024

It looks like the outputs is completely missing from the job spec. I wouldn't mind looking into implementing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature triaged Issue has been screened and prioritized by a project lead
Projects
Development

No branches or pull requests

3 participants