c3tracker:setup

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
c3tracker:setup [2024/10/19 16:50] – better document the "decentralised samba" setup stuebinmc3tracker:setup [2024/11/04 13:34] (current) – try to fix formatting jtbx
Line 6: Line 6:
   * Adjust project properties, recommendations: (full reference at the bottom of the page)   * Adjust project properties, recommendations: (full reference at the bottom of the page)
   * Compare project properties with previous instalment of the same event   * Compare project properties with previous instalment of the same event
 +
  
 ==== optimal properties from current project ==== ==== optimal properties from current project ====
Line 51: Line 52:
 Please note that the conditions in the "project to worker group" filter are currently always evaluated with logical OR.  Please note that the conditions in the "project to worker group" filter are currently always evaluated with logical OR. 
  
-Specifying a property with an empty value, which is often done for EncodingProfile.IsMaster, will match if this property does not exist at all on a ticket. So for EncodingProfile.IsMaster, specifying an empty filter will match on recording tickets which never have this property.+Specifying a property with an empty value, which is often done for `EncodingProfile.IsMaster`, will match if this property does not exist at all on a ticket. So for `EncodingProfile.IsMaster`, specifying an empty filter will match on recording tickets which never have this property.
 == Pipeline setup during event == Pipeline setup during event
  
Line 66: Line 67:
  
 For every worker: For every worker:
-* set room filters in tracker e.g. `Fahrplan.Room = Foobar`+* set `EncodingProfile.IsMaster = yes` to avoid encoding all sub formats 
 +* (set room filters in tracker e.g. `Fahrplan.Room = Foobar`, but this cannot be used at the same times as the above, see the warning below)
  
 For every recoding cube: For every recoding cube:
Line 75: Line 77:
 * start tracker scripts for encoding: `sudo systemctl start crs-encoding.service` * start tracker scripts for encoding: `sudo systemctl start crs-encoding.service`
  
 +
 +<panel type="danger" title="Attention">Since tracker filters are joined via OR and not AND, this setup cannot be extended to multiple rooms without hacks if you want to e.g. limit on-site encoding to master formats.</panel>
  
 === centralised storage (rsync) (Variant 1) === centralised storage (rsync) (Variant 1)
  • c3tracker/setup.1729349435.txt.gz
  • Last modified: 2024/10/19 16:50
  • by stuebinm