Zetav is a tool for verification of systems specified in RT-Logic language.
Verif is a tool for verification and computation trace analysis of systems described using the Modechart formalism. It can also generate a set of restricted RT-Logic formulae from a Modechart specification which can be used in Zetav.
With default configuration file write the system specification (SP) to the sp-formulas.in file and the checked property (security assertion, SA) to the sa-formulas.in file. Launch zetav-verifier.exe to begin the verification.
With the default configuration example files and outputs are load/stored to archive root directory. But using file-browser you are free to select any needed location. To begin launch run.bat (windows) or run.sh (linux / unix). Select Modechart designer and create Modechart model or load it from file.
In the landscape of peer-to-peer (P2P) file sharing and digital media preservation, release groups occupy a unique space between piracy syndicates and archival societies. One notable pseudonym within this ecosystem is "Tigole." This paper examines the phenomenon of "Tigole movies"—fan-encoded video files marked by distinct technical specifications (QxR releases), community trust, and a specific approach to codec efficiency. It argues that Tigole represents a shift from raw piracy toward curated, preservationist digital distribution.
The "Tigole movie" is more than a pirated file; it is a standard of care in the post-Scene P2P era. As streaming fragments into subscription silos, groups like Tigole provide a shadow archive—lower-fidelity than a disc, but higher-intent than corporate streaming. Whether one views this as theft or preservation, the technical craft behind the label demands study. tigole movies
Tigole does not crack or distribute the initial source (usually a BD Remux from a scene group). Their work is derivative: applying compression as a form of technical curation . Legally, it violates copyright in most jurisdictions. Ethically, users frame it as "abandoned media preservation" or "format-shifting." Notably, Tigole releases often cover obscure films, director’s cuts, or TV shows unavailable on modern streaming platforms. In the landscape of peer-to-peer (P2P) file sharing
The Tigole Encode: Digital Distribution, Quality Standards, and the Cult of the Release Group The "Tigole movie" is more than a pirated
Traditional "The Scene" operated on racing: the first to release a DVD/Blu-ray rip won prestige. However, by 2015, x265 (HEVC) allowed 10-15 GB 1080p files to shrink to 2-4 GB with minimal perceptible loss. Tigole, often collaborating with groups like QxR , capitalized on this. Their niche was not speed but deliberate encoding : fine-tuning parameters (crf, preset, no-sao) to balance sharpness and grain retention.
[Generated] Course: Media Studies / Digital Archiving Date: April 14, 2026
The term "Tigole movies" does not refer to a film genre or director but to a specific digital release label . Emerging from the P2P community around the mid-2010s, Tigole became synonymous with high-quality, efficiently compressed movie files, typically using the x265 codec. Unlike early scene releases focused on speed, Tigole encodes prioritized visual fidelity at smaller file sizes, catering to users with limited bandwidth or storage.
The Zetav verifier expects the input RRTL formulae to be in the following form:
<rrtlformula> : <formula> [ CONNECTIVE <formula> ] ... <formula> : <predicate> | NOT <formula> | <quantifiedvars> <formula> | ( <formula> ) <predicate> : <function> PRED_SYMB <function> <function> : <function> FUNC_SYMB <function> | @( ACTION_TYPE ACTION , term ) | CONSTANT <quantifiedvars> : QUANTIFIER VARIABLE [ QUANTIFIER VARIABLE ] ...Where predicate symbols (PRED_SYMB) could be inequality operators <, =<, =, >=, >, function symbols (FUNC_SYMB) could be basic + and - operators, action type (ACTION_TYPE) could be starting action (^), stop action ($), transition action (%) and external action (#). Quantifier symbols (QUANTIFIER) could be either an universal quantifier (forall, V) or an existential quantifier (exists, E). Connectives (CONNECTIVE) could be conjunction (and, &, /\), disjunction (or, |, \/), or implication (imply, ->). All variables (VARIABLE) must start with a lower case letter and all actions (ACTION) with an upper case letter. Constants (CONSTANT) could be positive or negative number. RRTL formulae in the input file must be separated using semicolon (;).
V t V u (
( @(% TrainApproach, t) + 45 =< @(% Crossing, u) /\
@(% Crossing, u) < @(% TrainApproach, t) + 60
)
->
( @($ Downgate, t) =< @(% Crossing, u) /\
@(% Crossing, u) =< @($ Downgate, t) + 45
)
)
Verif tool does not deal with direct input. Examples are load from files with extension MCH. Those files are in XML and describes model modes structure and transition between modes. There is no need to directly modify those files. But in some cases it is possible to make some small changes manualy or generate Modechart models in another tool.
If you have further questions, do not hesitate to contact authors ( Jan Fiedor and Marek Gach ).
This work is supported by the Czech Science Foundation (projects GD102/09/H042 and P103/10/0306), the Czech Ministry of Education (projects COST OC10009 and MSM 0021630528), the European Commission (project IC0901), and the Brno University of Technology (project FIT-S-10-1).