Author Topic: Extension Based Code replacements  (Read 125 times)

Offline Max Lemesh

  • Full Member
  • ***
  • Posts: 208
    • View Profile
Extension Based Code replacements
« on: March 14, 2025, 11:38:27 AM »
Trying to come up with a solution to separate files by extension during ingest, or to separate jpegs and raw files to be exact.
However images keep landing in JPEG folder, no matter if use {type} variable or custom [filext] in hotcodes to specify replacement for each file extension.

From my understanding PM sees raw+jpg pair, reads metadata from jpeg only (or raw) and considers both files type as jpeg.

If I go into the folder and separate raw and jpeg files, then it works, as PM looks at each file evaluating it correctly. However the counter in renaming template also work for each one making the filenames different.

So question is....
Is there a way to make PM evaluate files separately during ingest and not as a pair?
using {type} works fine if ingesting only RAW or NON-RAW files, but when I ingest both — everything is a jpeg

I guess I need some sort of {extension} variable which just returns file extension of the actual file, not of one of the files in pair



Code: [Select]
{year4}{month0}{day0}_{clientname}_{jobname}/[filext]
Code: [Select]

// Hot codes for forting files by extension
// extensions are case sensitive
//
//
//== {filename:-3}


//## filext
JPG JPEG
ARW RAW
arw RAW
CR3 RAW
cr3 RAW
CR2 RAW
cr2 RAW
MP4 RAW VIDEO
mp4 RAW VIDEO
MOV RAW VIDEO
mov RAW VIDEO
RAF RAW
raf RAW

jpeg JPEG

//?? OTHER

« Last Edit: March 14, 2025, 04:39:25 PM by Max Lemesh »