Editor: Invalid end range

[HD1080ide]

If the end range is greater than 1984, I get the invalid end range error message.

A range of 0-1984 still works:

Parsing JSON file...
EditConfig {
  "remove": [
    "0-1984"
  ]
}
Removed 1985 metadata frames.
Generating and writing metadata to JSON file... Done.

A range of 0-1985 results in an error:

Parsing JSON file...
EditConfig {
  "remove": [
    "0-1985"
  ]
}
Removed 1986 metadata frames.
Generating and writing metadata to JSON file...
thread 'main' (50428) panicked at hdr10plus\src\metadata_json.rs:115:37:
index out of bounds: the len is 0 but the index is 0
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

A range of 0-1986 (or higher) will result in the invalid end range error:

Parsing JSON file...
EditConfig {
  "remove": [
    "0-1986"
  ]
}
Error: invalid end range 1986

I use a Windows computer, in case that's relevant.

[quietvoid]

It's erroring because your final metadata becomes empty.

[HD1080ide]

That doesn't make sense. Of course, I double-checked the frame numbers. I'm now removing the excess frames directly in my Python script. That works perfectly.

[quietvoid]

What do you expect me to do? You didn't provide any sample JSON where you're encountering the issue.
To me it looks like your metadata is only 1985 frames long and you've removed them all.

[HD1080ide]

Here is an example metadata file, which contains the frames 90000 - 91985: https://drive.google.com/file/d/1eMErZQYjbUpUWbfsxf_6oiN7S7P7hJNz/view?usp=drive_link

Let's assume that I want to remove the frames 90000-91000. Then this is my edits.json file:

{
    "remove": [
        "90000-91000"
    ]
}

And this is my hdr10plus_tool command:
.\hdr10plus_tool.exe editor "example-metadata.json" -j edits.json -o "example-metadata_modified.json"

Then I get this output:

Parsing JSON file...
EditConfig {
  "remove": [
    "90000-91000"
  ]
}
Error: invalid end range 91000

I don't expect anything from you. I just want to help you to improve your tool, if this is not user error. I'm using the latest release version 1.7.2.

[quietvoid]

The frame numbers in the JSON are not currently used for the editor so everything starts at 0.
IIRC we use the offset somewhere else so possibly can be used here as well.