-
Notifications
You must be signed in to change notification settings - Fork 193
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
Comments
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 The Layer's Is Outline the optimal API for us to use to construct jobs? Should we be using pycue/opencue? Thanks DJM |
In general 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. |
Thanks Brian. |
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. |
It looks like the outputs is completely missing from the job spec. I wouldn't mind looking into implementing this. |
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
The text was updated successfully, but these errors were encountered: