Question about Custom XML File Type Syntax
Posted: Mon Jul 03, 2017 3:37 pm
I've used R-Studio a fair amount to create custom file types for files not natively supported by the software. It's one of my favorite features of the program.
One issue I've been running into more and more relates to image files with embedded preview files. I've found a fair number of cases where different RAW image types such as NEF have an embedded preview file with its own starting/closing signature which throws the software off on finding it. Is there a way (even manually in the xml) to set a minimum file size to look for?
Basically after it finds an opening signature I add in, I want it to ignore other signatures within a certain amount of kb before it even starts to look for a closing signature or a next file. I realize this would have to be a separate scan with all file types but the one disabled, but it'd really help if there was a way to do this. Perhaps even a list of available XML rules the software will understand and their usage could be of help.
I've managed to do it for a few types of files like this already by just using some rather complex and/or functions, but it was time-consuming to do it that way and I don't think will be possible for all file types like this.
One issue I've been running into more and more relates to image files with embedded preview files. I've found a fair number of cases where different RAW image types such as NEF have an embedded preview file with its own starting/closing signature which throws the software off on finding it. Is there a way (even manually in the xml) to set a minimum file size to look for?
Basically after it finds an opening signature I add in, I want it to ignore other signatures within a certain amount of kb before it even starts to look for a closing signature or a next file. I realize this would have to be a separate scan with all file types but the one disabled, but it'd really help if there was a way to do this. Perhaps even a list of available XML rules the software will understand and their usage could be of help.
I've managed to do it for a few types of files like this already by just using some rather complex and/or functions, but it was time-consuming to do it that way and I don't think will be possible for all file types like this.