May be some kind of smart-cache, or generating predefined naming table with sort of possible variants.
Create naming script > fire generator which create a expanded templates table, and then query from this table.
What i already can cut from query is {project.code}. That's all.
Running this Takes a 0.1 sesonds on 2.2 ghz cpu, it is really fast, until i got more and more files in a single or a batch of snapshots.
Create naming script > fire generator which create a expanded templates table, and then query from this table.
Code:
dir = {project.code}/episodes/{sobject.name}/{snapshot.process}{@CASE( @GET(file.type) == 'playblast', '/'+'__preview', @GET(file.type) == 'web', '/'+'__preview/web', @GET(file.type) == 'icon', '/'+'__preview/icon')}
file = {parent.name}_{sobject.name}/{snapshot.context[1]}/v{version}{@IF(@GET(file.type) == 'playblast', '_playblast' ))}.{ext}
condition = @GET(snapshot.process) == publishWhat i already can cut from query is {project.code}. That's all.
Running this Takes a 0.1 sesonds on 2.2 ghz cpu, it is really fast, until i got more and more files in a single or a batch of snapshots.