-
Notifications
You must be signed in to change notification settings - Fork 129
Deadline: checking existing frames fails when there is number in file name #3829
Comments
We're likely better off defining our own patterns like the So it could be Once we've found out the assembling/pattern matching that does what we want - then we should just provide it as a utility function in OpenPype so we can rely on that single entry to files collection. We might want this pattern? \D?(?P<index>(?P<padding>0*)\d+)\.\D+\d?$ And if we'd want to be more explicit with a specific extension (just so that a potential extension with a number in it is allowed - otherwise it'd take the right-most number) ext = ".ass.gz"
pattern = r"\D?(?P<index>(?P<padding>0*)\d+){ext}$".format(re.escape(ext)) This would allow any of: hello1001.ass.gz # 1001
hello_1000.ass.gz # 1001
hello.1001.ass.gz # 1001
fooV01_sdadw9w13ek091.001.1001.ass.gz # 1001
a1001.ass.gz # 1001
1001.ass.gz # 1001
1.ass.gz # 1
foobar1.1.ass.gz # 1 |
Yep, I agree that using that specific regex with provided extension will solve most of these issues. I haven't yet identified all the places we are doing this but my guess is that in most (if not all) of them we already know the extension to be used. |
General plugin got removed a while ago, for Unreal it gets fixed by #5533 Standardization of |
Problem
validate_sequence_frames
fails when there is number in file name (other then frame number). It breaksclique
asembly.[cuID:2uxa4yb]
The text was updated successfully, but these errors were encountered: