Please tell us how we can make AYON work better for you.
We love your Feedback!
Webpublisher - Needs a Disk space check and/or max file size limit
Recently we had an artist try and upload a 50GB render, it filled up our ayon server and crashed it. A general disk space check for Webpublisher ( and also ayon in general ) seems like a necessity when youre potentially working with bigger transfers.
In Progress
Planner: Duplicate Scenario
The “Duplicate Scenario“ feature disappeared from the planner frontend. I believe that was introduced in 2.0.0. In the “Schedule“ tab of a project that feature is still present tho. Would be great if we could duplicate scenarios from the project-agnostic “Plan“ tab. Could be this was removed on purpose. If so, what is the reasoning behind this? Thanks :)
Loader - drag and drop
Content aware drag and drop feature to the loader Use cases User drag and drops assets directly to specific location in the scene User drag and drops materials directly onto objects for fast lookdev User drag and drops EXR sequences directly into AE or Davinci timeline Reference of asset manager with similar modern features. https://www.youtube.com/watch?v=rjTv9jWfY4s
Allow regex customization for folder entity names
We want to ban users from creating assets with leading digits (e.g. 01_character_A). Ayon currently is missing controls for this on the backend, would be great to add regex options.
Different date formats
I was wondering if it is at all possible to change the formatting of dates are displayed on the server? We are used to different formatting for readability and I'm wondering if its configurable.
Mandatory Message for Settings Changes
inspired by https://feedback.ayon.app/p/per-bundle-note-or-description When users are changing settings (either studio-wide or per-project) I’d love to require a little message asking for the reason of this settings update. Basically a commit message for settings changes. This message should be part of `bundle.updated` event’s payload. Usecase: We’re running a service that tracks all AYON studio settings with git in order to know who changed what when and also to be able to revert settings more easily. With this I would also be able to know why it was changed.
AYON Publisher issues with Mac Intel processor
We have experienced problems when using the publisher on mac machines with intel processors. Logs show dependency packages issues with the specific architecture (arm64 vs x86_64). Is there a version of the app that would work with these machines ? How do we go about it ? Thanks.
JPG vs JPEG
inconsistency in format name causing render/publishing errors when rendering JPG in Blender. …\addons\blender\1.1.6\private\client\ayon_blender\api\render_lib.py https://community.ynput.io/t/blender-jpeg-vs-jpg/3222 getting this error when publishing: * `ValidateExpectedFiles` does a string-exact filename comparison * Expected: `...Beauty1001.jpeg` * Actual on disk: `...Beauty1001.jpg` def set_render_format(ext: str, multilayer: bool): """Set Blender scene to save render file with the right extension""" bpy.context.scene.render.use_file_extension = True image_settings = bpy.context.scene.render.image_settings if lib.get_blender_version() >= (5, 0, 0): if multilayer: image_settings.media_type = "MULTI_LAYER_IMAGE" else: image_settings.media_type = "IMAGE" if ext == "exr": file_format = "OPEN_EXR_MULTILAYER" if multilayer else "OPEN_EXR" image_settings.file_format = file_format elif ext == "bmp": image_settings.file_format = "BMP" elif ext == "rgb": image_settings.file_format = "IRIS" elif ext == "png": image_settings.file_format = "PNG" elif ext == "jpeg": image_settings.file_format = "JPEG" elif ext == "jp2": image_settings.file_format = "JPEG2000" elif ext == "tga": image_settings.file_format = "TARGA" elif ext == "tif": image_settings.file_format = "TIFF" ## def get_file_format_extension(file_format: str) -> str: """Convert Blender file format to file extension.""" # TODO: Figure out if Blender has a native way to convert to extensions if file_format == "OPEN_EXR_MULTILAYER": return "exr" elif file_format == "OPEN_EXR": return "exr" elif file_format == "BMP": return "bmp" elif file_format == "IRIS": return "rgb" elif file_format == "PNG": return "png" elif file_format == "JPEG": return "jpeg" elif file_format == "JPEG2000": return "jp2" elif file_format == "TARGA" or file_format == "TARGA_RAW": return "tga" elif file_format == "TIFF": return "tif" # Blender 5+ elif file_format == "CINEON": return "cin" elif file_format == "DPX": return "dpx" elif file_format == "WEBP": return "webp" elif file_format == "HDR": return "hdr" else: raise ValueError(f"Unsupported file format: {file_format}")
I would like tasks to publish updates to kitsu
OK after a little post on the communities this appears to be not just me. Publishing anything from tray publisher - kitsu works, model families, look dev, whatever. However publishing a model / look dev update from the maya publisher doesn’t update in kitsu. Personally I’d rather not be using kitsu at all but the studio are sticking with it. Currently publishing reviews from Maya - Ayon - Kitsu works fine. Mainly it’s models, I want kitsu to change status and show a thumbnail and comment when a user publishes a model.
Payload.mp4 when downloading files is confusing clients a lot
Hey there, When using Review ( or generally looking at reviewables and wanting to retrieve the original reviewable ) we need clients ( not logged in guests, this is already shielded correctly ) to be able to fetch the reviewables from the viewport. This currently works, BUT the file is renamed to a generic payload.mp4. Causing a mess. I want to suggest to keep the original name of the uploaded reviewable here, so our own naming keeps things sensible/tidy. I'd say this is quite essential for a clean workflow Thanks :)
Predefined/Enumerated Task Names/Labels
I would like to configure a project with the allowed tasks ahead of time and then whenever a task is created, it must be one of the tasks provided on this list. These tasks should continue to be sorted by task type (e.g. fx_fire is an fx task type). I would like the task project definitions to be first class citizens so that I can query the project configuration or the shot configuration of a particular task. I have plans to tie tasks/task categories into the layering order of our USD workflow and this will then tie into that potentially. You can think of the tasks as assets and a shot task as being an instance of that asset, if you like. If it is too much of a burden to create tasks on the project first, before making them in shots, you could potentially make a mode that will author a new project task from the same dialog for certain permission types. I want to eliminate areas where artists or coordinators need to enter strings by hand. At scale it is a virtual guarantee that we end up with slight deviations in spelling (tire_burnout or tyre_burnout), or spaces (spiderwebs or spider_webs), or capitalization (SpiderWebs or Spiderwebs). These inconsistencies make it much more challenging to build automation templates or track same-things across/between projects for forecasting the cost of certain tasks. Discord conversation here: https://discord.com/channels/517362899170230292/1528631102762127490/1530456273873797151 Thanks Ben
"Project Root Not found" Pop UP
For artists especially remote ones, they may have the shared storage mounted under a different letter. And sometimes, they are clueless that they need to go to roots tab under project settings on the server. I wonder if this can be easily detected at earlier time. E.g. when they select a folder in the the launcher, the launcher can check if the roots exist. if not it can prompt them to pick the correct location for them. which will be set as a root override. THIS IS A MOCKUP.. This can potentially save some frustration for remote artists.
PowerPack Sync Statuses (Studio level) ignores custom Anatomy Presets
At the Studio Settings level, the PowerPack Sync Statuses feature only pulls status options from the built-in/default Anatomy Preset. It doesn't read from a custom Anatomy Preset that's been created and set as primary in the studio. Steps to reproduce: Create a custom Anatomy Preset with custom statuses and set it as the studio's primary preset. Go to Studio Settings → PowerPack → Sync Statuses. Search for a status to use in a sync rule. Expected: The status search/dropdown should include statuses from the active custom Anatomy Preset (or at least the primary preset), not just the built-in default. Actual: Only the built-in default preset's statuses appear, with no way to change the source preset. Impact: Studios using custom status pipelines can't build Studio-level sync rules that reference their own statuses — they're forced to duplicate the setup at the Project level for every project, which defeats the purpose of a studio-wide rule. Suggested fix: Either let Studio-level Sync Statuses pull from the primary Anatomy Preset (whichever is currently set), or add a setting to choose which preset the Studio-level rules should read from.
Powerpack Status sync from folder to tasks
Sunrise would find it helpful if an ‘Omit’ status set by a producer on a shot folder would automatically set the children tasks to Omit as well. This is so that artists in their kanban view can see their assigned shot/asset task in Omit, and know not to waste time on it anymore.
Merging Project Setting Team and Project Access
Wild thought: Doesnt it make more sense to merge both of these pages together? Both of them define user access rights, one group based and one individual based. What are the benefits of not merging both functionalities on one? I've had producers get lost because they were overlooking Project Access because they went straight for Team, and the other way around, because they were looking for just “Assigned Users” functionality but split over two different pages.
Frontend addons could customize other frontend parts
Being able to hook parts for one addon to other views/pages on frontend would be very useful. Adding custom widgets/buttons to predefined places could be enough.
Isolate RGB(A) channels in web player/review addon
For checking more technical issues or switching between technical data encoded in RGB (like wireframe, ulit texture, color masks) it would be great to be able to switch between individual channels and full composite view in similar fashion as is in other players. Having small buttons next to the Brightness control for example with associated keyboad shortcuts.
Settings Apps
It would be great to wrap parts of the settings into their own individual “modules” that would have UI more suited for the specific task. As example: Color management settings are very cumbersome - you need to set many things on many places, sometimes write exact strings (color spaces names), etc. Having dedicated UI that would ease the pain (along with presets, etc.) would help a lot. Having this modular and customizable, it would open up a way for building much more easier layer on top of low-level settings.
Scheduler Question - Snapping Events
Currently I’m looking to input events in line with the tasks that are set out amongst the hierarchy however it keeps snapping to the task above when I want it to align with the task - why is this the case - anyone have any suggestions to fix this?
Automatic artist unassignment when a task is started
I want to be able to automatically unassign other artists from a task when one artist starts working on it, to prevent duplicate work.