We love your Feedback!

Please tell us how we can make AYON work better for you. You can also report bugs or ask questions if our Help Portal is not helping.

If you’re looking for developer resources, you can find all of them on our Developer Portal

New workfiles for softwares without addon

I really love the simplicity of the Tray publisher. Any file with any extension can be published and be a part of the pipeline. It would be great to add this simplicity to work files as well (but not using the tray publisher) * Creating addons for every software in every industry will be hard to manage and take very long time. * “Simple” softwares like Excel, Word, Powerpoint, Notepad etc is in need of a simpler approach than addons, since there is simply no way to develop addons for every single software *The simplicity of the tray publisher could be applied to workfiles as well and therefore open up possibilites to add any type of software to the AYON pipeline, also for workfiles. To solve this we need a new feature to create new work files based on pre-existing template files. Maybe this could be done with the interactive web action? Example User creates a new task in overview and with web action the user gets to choose if it wants to create a work file from pre-existing template (For example there might be 5 different Excel templates for different purposes) Once the template is chosen there will be a new workfile created on disk and also a new database entry. For publishing we could still use the tray publisher. This feature would open up a lot of freedom for the user to add softwares that does not have an addon and not necessarily need a fancy pipeline. Problems to solve * Versioning of the workfiles would need to be added somehow. Maybe as a right click feature on the current workfile.

Olle Rydberg

3
💡

Feature requests

Set Product Status on Publish

To make it easier for users to set statuses it would be super helpful if the status of a product version could be set when publishing - I am thinking along the lines of two per instance attributes, one to set the status of the new version and the second to change the status of the currently existing version(s). So I want my new version status to be Pending review and the previous versions to be set to Omitted. This will also help with the status filters in the loader which hide versions based on status, so if you want to make sure all previous versions are excluded when Omitted is set to be hidden, all versions have to have their statuses changed manually, which is very tedious :(

Shea

7
💡

Feature requests

Planned

In the loader, make Hero selection easier

When Hero mode is OFF : artists can just load the product, no problem, they get the latest version. When Hero mode is ON : in the Loader, the default version that is selected is the latest version, and not the Hero version : Problem : if artists want to import a Hero, they need to manually select the [v] for each product they load (which can mean 4 or 5 textures, in the case of published Substance). If Hero mode is active, it would make sense to have it available easily in the Loader, which means force the Hero to be on the first position among the versions list. I think it would help avoid user errors, as we could ask users to not touch anything and just load. It is also discussed here : https://community.ynput.io/t/in-the-loader-make-hero-selection-easier/2537

a.xerri

1
💡

Feature requests

Custom endpoints should have a fixed url

Current situation : Currently, paths to addon endpoints always contain the addon version, since all endpoints from all versions are always exposed. Example : http:// myserverayon:5000/api/addons/my_addon/0.1.2/get-test-data/myProjectName Problem : If we code a custom endpoint, to be used by other departments, we can’t tell them it’s a moving target, they need a fixed url, as in usual REST APIs. Because other departments can’t use self.version or similar, as the calls are done from other softwares. Proposal Please provide a “production" placeholder, that would replace the version. Example : /api/addons/my_addon/production/my_endpoint Context : It is also discussed here : https://github.com/ynput/ayon-backend/issues/494

a.xerri

1
💡

Feature requests

Add Transcoding Options During Export in AYON for Hiero

In standard Hiero functionality, when exporting shots, there's not only the ability to create folder hierarchies and organize shots, but also to transcode frames into the desired format and colorspace: Currently, when exporting via AYON in Hiero — for example, working with.mxf files — we need to manually transcode the shots outside of AYON before publishing. AYON then copies these intermediate files into the correct structure, effectively duplicating the data. This creates issues, especially at scale. For example, exporting a film with 100+ shots to.exr results in around 10TB of unnecessary duplicated data — aside from the added manual steps and general inconvenience. It would be great to support format and colorspace transcoding directly during publish through AYON, so we can eliminate this intermediate step and avoid redundant storage usage.

Alexey Volynets

6
💡

Feature requests

Unified Launcher

Thanks to this post — it finally pushed me to take the time and share an idea I've been holding onto for a few months now: Right now, we have three separate dialog windows, each of which needs to be opened individually via the system tray. The first flow is pretty much the same in each: select a project, a shot/asset, and a task: Why not merge all three dialogs into a single unified launcher? This would reduce the number of required actions and bring all the functionality into one solid entry point. It would look something like this: 1. Workfiles tab Additionally, building on this post, I suggest combining the functionality of the "Working Files" tab with the "Launcher" tab (including Thumbnails). This way, the user can choose to either launch through a specific working file or go in via the selected software. 2. Browser tab 3. Publisher tab

Alexey Volynets

4
💡

Feature requests