• Completion and stats
• duration
• format
• deadline and time remaining
• number of users
• number of shots / sequences
• list of sequences (and shots and duration for each)
• number of assets / asset groupes
• list asset groups and number of assets in each

and buttons for folders

Option to compress copies of files

• compress versions
• compress copy of source file in publish

Compression, try or add option:

• .tar.gz
• .7z
• .zip

dark/light/color

• copy selected file to the "_published" folder
• copy to the "_versions"

• Fuzzy logic for lateness color in status
• Fuzzy logic for completion color in steps

• Copy and increment version

• Option: by sequence
• Option: in the corresponding step or in the 06-EXPORTS/Previews folder
• One click assemble for the step
• Assemble for a shot
• In the addons: auto-copy in the right folder

Concernant les playblasts et previews, certains étudiants n'utilisent
pas l'outil Ramses (et ils devraient, sinon on a jamais les numéros de
frames dans leurs playblasts), parce que Ramses les enregistre dans le
sous dossier "preview" du shot. Il y a besoin, pour le montage, de la
possibilité de rassembler tous les playblasts dans un dossier unique,
que le monteur puisse les importer facilement.

Ajouter une option de compression des données : pour les versions et
autres fichiers de backups, et économiser pas mal de place par la même
occasion.

• Tasks for steps, which are neither assets nor shots

(optional) auto config of shares:

• whole ramses folder
• users folder
• per project

options for include lists:

• ignore versions

nodes management:

• accept nodes
• add nodes
• remove nodes

• Check/explicitely set the encoding of the sent JSON

• Store color values in the DB, in RGBA8, RGBA32, HEX, CMYK, Name

• Export/load as json (.ramses.palette)

• Shared by project or by steps.

• Dev a palette for Ae (simple popup in Ramses)

• A section in the view panel of shaders and comp view in Blender

Dans l'appli Ramses : un accès rapide aux dossiers autres que ceux des
shots : exports/medias, preprod, postprod, templates des steps, etc.

je ne sais pas si ça vient de Ramses directement en fait mais sous Linux on ne peut pas l'ajouter aux favoris dans la barre des tâches

using and listing tasks

Auto version / backup

Use vlc qt
And dufrap

Option to sync player to table display (select rows depending on player timecode)

import / update / export

if published & right file format available -> set next step to TODO

Let Ramses know the color management of the files and apps

• ColorSpace object and list in Ramses (just a basic object with name and shortname). Shortname could be read from an OCIO config

• Add a few default common colorspaces

• Application: add attribute sceneReferredColorSpace and displayColorSpace

• Application: for each output file association: add colorSpace attribute

• FileType: add default colorSpace

OCIO

To do later

• Ability to set an OCIO config file for the project
• and a different OCIO config for each application

ColorSpace list is built from the available OCIO spaces, using defaults from the config file

(optional) auto config of shares:

• whole ramses folder
• users folder
• per project

options for include lists:

• ignore versions

nodes management:

• accept nodes
• add nodes
• remove nodes

• Dayly schedule
• What's changed (notifications)

Dans l'appli Ramses, un outil de planning global (précision à la
semaine) par step; pouvoir dire : tel step va de telle semaine à telle
semaine.

move dbi calls into classes

• Add a "suspend" option in DBInterface to temporarily suspend calls when getting updates from the db.

• Move createUser in RamUser constructor

• Move removeUser in RamUser destructor

RamUser

• Change password without specifying current one (when set by admin) (and add necessary dbi call)

Server

• check if user is admin/lead/standard, and keep uuid, for further checks when modifying things

A panel with tasks per person and with states/completion ratio/comments
maybe with groups
and these groups or tasks in the schedule

Ability to use DuME

• Ramses: store DuME presets path per project
• Add DuME to the default applications
• For medias, a convert field with a DuME preset list and launch button

import / update / export

• Ubuntu 18.04
• Ubuntu 20.04
• Win
• Mac
• build on older ubuntu with Qt 5.9 &openssl 1.0 /// and 20.04 with Qt 5.12(test!!) & openssl 1.1 (use 20.10 or 21.04?)
• package 2 deb for both ubuntu versions / openssl 1.0 / 1.1
• package 2 appimages for both ubuntu versions / openssl 1.0 / 1.1
• add openssl in dependencies for the deb package / warn it must be avail with the appimage
• win
• mac

add a comment to specific files/versions

-> Copies the file to the step common folder

Hi, reposting from discord: Blender files are saved without extensions (and every time asks what app do I want to use). Also in admin-File types it's .lend instead of .blend , and .ep instead of .aep. I change those, but for some reason it revert back to .lend and .ep
OS Win10

import / update /export

• File tools:
  • Folder access
  • Clean Tree: Remove non tracked asset/shot dirs, etc (collect in a trash)
  • Create assets/shots from tree
  • Empty trash (using optionnal date filter)
  • Remove _versions (in selected folder)
  • Remove _trashes (in selected folder)
• Data tools
  • Import / Export data
    • Server side: https://www.tutorialspoint.com/php/perform_mysql_backup_php.htm // do it regularly ? option in config.php , protect sql dumps folder with htaccess (create it in install.php)
    • Client side: define a data structure (json?) // Copy the sqlite local db once a day
  • List and manage/restore/delete removed objects