Differences

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

--- c3tracker:setup [2024/10/19 22:14] – explain why variant 2 does not work easily for more than one room stuebinm
+++ c3tracker:setup [2025/01/31 20:59] (current) – kunsi
@@ Line 6: / Line 6: @@
   * Adjust project properties, recommendations: (full reference at the bottom of the page)
   * Compare project properties with previous instalment of the same event
 ==== optimal properties from current project ====
+Replace `camp2023` with your chosen tracker project slug.
   Meta.Acronym                    camp2023
@@ Line 51: / Line 53: @@
 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
@@ Line 77: / Line 79: @@
-<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>
+<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. Use the  `CRS_ROOM` filter in bundlewrap if you need both tracker filters and room-specific encoding workers.</panel>
 === centralised storage (rsync) (Variant 1)