I seems that warp tries to process files by alphabetized file name order. Some programs don't write files using trailing zeros, so instead of processing 001, 002, 003, 004... the files are processed 1, 11, 111, 2, 22, 222, etc. You can see this in the attached screenshot where theres a gap in the file series. This makes it difficult to see what your latest files look like since they are not typically found on the right side of the display.
I think this also causes the file finder (listening routine) to fail. Warp will not detect new files continuously, only in bulk each time the warp executable is re-launched.
I seems that warp tries to process files by alphabetized file name order. Some programs don't write files using trailing zeros, so instead of processing 001, 002, 003, 004... the files are processed 1, 11, 111, 2, 22, 222, etc. You can see this in the attached screenshot where theres a gap in the file series. This makes it difficult to see what your latest files look like since they are not typically found on the right side of the display.
I think this also causes the file finder (listening routine) to fail. Warp will not detect new files continuously, only in bulk each time the warp executable is re-launched.