jen_at_floyd

Members
  • Content Count

    43
  • Joined

  • Last visited

About jen_at_floyd

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I recently came across the news that CentOS 8 is effectively being killed, so the last production release of CentOS will be CentOS 7. The end-of-life for CentOS 7 is 2024. I know that future versions of Ftrack will be distributed as Kubernetes Helm files. As a consequence of these changes to CentOS it's very likely that our studio will run Kubernetes on Ubuntu instead of CentOS. Will there be Ftrack documentation to support other OSes besides CentOS 7? Reference: https://blog.centos.org/2020/12/future-is-centos-stream/
  2. The docs for on-prem installation recommend using Sentry for error handling, so we've set that up for our studio. I've noticed that Sentry collects at least 3 or 4 errors every day but they are all related to internals of the Ftrack server so there's nothing here that we can really fix. Is there some system for sending these errors to Ftrack devs periodically?
  3. This is a fairly minor pain point but on our on-prem Ftrack instance we have LDAP logins enabled and since the login screen placeholder says "Username or Email" we've had a few users get confused when they try to use their email address to log in. We have our "Login attribute" in the LDAP settings set to `sAMAccountName` and I could set it to `mail` instead but then we'd have the same problem but in reverse. It would be nice to maybe have an 'alt login attribute' setting or maybe even have the 'login attribute' be a comma-separated list of values. As an alternative, a simpler solution might be to allow for on-prem installs to add a bit of explanatory help text to this login window or change the placeholder text for the input box.
  4. It seems like thumbnail previews in the UI are locked to a 16:9 aspect ratio. It would be great to have an option to change this ratio. Or perhaps an option to not clip the image but instead use black bars on the sides if it doesn't fit the ratio? Our renders adapt to the 16:9 ratio just fine, but animation assets are often better suited to a square thumbnail.
  5. A means for specifying the formats was precisely what I was asking for in my original post! I have just tried adding the ftrack.image_conversion_formats option and it works perfectly. It would be great if this option could be documented on the Image Encoding page for future reference. Thank you!
  6. Uploads are happening via drag-and-drop, but I was hoping I wouldn't have to go the event-listener route because I've had missed events if the event listener process is down. I'd feel better if I could have multiple event listener processes running at the same time, but if I recall that just caused events to be processed multiple times.
  7. I tried calling `encode_media` on the session object and got this: >>> job = session.encode_media(component, version_id=version['id'], keep_original=True) Server reported error: ValueError(Encoding is not supported for component with file type u'.ai'. Valid formats are: ['3g2', '3gp', 'asf', 'avi', 'drc', 'flv', 'm2v', 'm4p', 'm4v', 'm4v', 'mkv', 'mng', 'mov', 'mp2', 'mp4', 'mpe', 'mpeg', 'mpg', 'mpv', 'mxf', 'nsv', 'ogg', 'ogv', 'qt', 'rm', 'rmvb', 'roq', 'svi', 'vob', 'webm', 'wmv', 'yuv', 'jpg', 'jpeg', 'png', 'tiff', 'tif', 'bmp', 'pdf', 'psd', 'gif', 'dpx', 'exr', 'svg']) This is moving out of 'feature request' and into 'bug' territory. Can your devs point me to how I can add the '.ai' format to the encoding list?
  8. Per the Image Encoding documentation, the only formats that trigger an encoding event are jpg, jpeg, png, tiff, tif, bmp, pdf, psd, gif, dpx, exr, and svg. However, our studio makes heavy use of Illustrator files (.ai extension) and we need to be able to kick off this encoding somehow. Illustrator files are compatible with PDFs, so the image encoder is technically capable of the conversion. However, the web UI never sends these files to be converted because it does not consider files with the .ai extension to be images. Since we already have the capability to run our own image conversion servers, it makes sense that we should be able to specify what formats are supported in the system settings or in the configuration file.
  9. That ZenDesk link doesn't work for me. It says I'm not authorized to view the page.
  10. At our studio we can have many different concurrent connections at the same time -- from 100 to 150. I've noticed that at peak times, the responsiveness of the site suffers a lot. However, even when not at peak times, realtime features like inbox notifications do not work consistently. Many of our artists have resorted to browser extensions that refresh their Ftrack page every 5 minutes or so in order to stay on top of their notifications. Of course, all of this extra refreshing also increases server load, so it would be better to come up with a different solution. Is there some sort of chart or recommendation about server specs based on the number of concurrent users?
  11. Currently solving this by just passing a URL parameter to the widget so that it knows what environment it's in. So widgets in an action will be specified as https://myftrackwidget.com/?env=action, for example. Still, it would be cool to get that info from Ftrack itself by having it pass data to the widget somehow.
  12. This is something folks on my team have complained about also. Would be great if the bookmark also saved the view.
  13. The View list at our studio is getting quite long. Particularly the Shared Views, but I have seen some very long personal View lists as well. It would be great if we could arrange views into folders or groups. To get around this and to help with organization, we've adopted a norm of using a per-department prefix for views. For example: Harmony - Needs Assets Harmony - Ready for Comp Tweens - Missing Imports Tweens - No EFX Paint - Reuses These prefixes are basically serving the same function as folders, but folders would make the list considerably shorter.
  14. I was following the instructions for configuring Sentry for error monitoring, but when I restarted the server I kept getting "ValueError: Invalid Sentry DSN" in my logs and the server refused to start. It turns out that in the Client Keys section of my Sentry project, I need to hit the "Show deprecated DSN" link in order to show the DSN that includes the secret. Apparently newer Sentry clients no longer require having the secret in the URL, which is why Sentry lists it as deprecated. It would be useful to specify in the instructions that the deprecated DSN is required in order to avoid confusion.