Thanks! Since there is no editor for the script (outside of regular json editors), I knew TimeSeq would be impossible to use without a decent manual. So I tried to make it as clear and detailed as I could. Good to hear that I didn’t mess it up 
1 Like
Can’t you make VSC do a schema validation on json? btw, possibly of interest - a few VCV sequencer support this JSON:
I actually started out with json schema since the idea was to use it in the module itself to validate scripts while loading. But the resulting error messages (though technically correct) were to cryptic to use towards end users (I doubt many non-developer VCV Rack users would know what to do if they got an error about a oneOf or an anyOf), so I started adding detailed validation with dedicated error messages as part of the loading of the internal data modal. And I didn’t maintain the schema as the script changed. I do plan to return to it, probably making a more high-level version that validates the object hierarchy and possible object properties without validating every little detail. And I have a couple of ideas that I want to look into that could provide additional validation on top of that. It’s one of the many things on the to-do list.
But even with such a json schema, I would still consider the current reference documentation as a must-have to provide details about what everything does.
Oh, I think what you did make a ton of sense. I also tried to document the JSON well for my relatively simple keyboard re-mapper inthe Seq++ manual.
I think I was reflexively reacting to your “there are no good JSON editors” with “yes, there are”. But obviously you meant the more useful “there are no JSON editor that is really appropriate for most VCV users”,
2 Likes
when I try to load your example scripts to TimeSeq I get an error:
I’m on win 11 and using vcv 2.6.3, do I need top update to 2.6.4?
Or what could be the problem?
I’m betting that you copied from text off of a web page. What you copied is something that has been reformatted for presentation in a web browser, and not the original plain text. All those spaces have been replaced with non-breaking space (U+000A) to make web rendering look right. It will work if you replace all the U+000A’s with regular space characters.
Or find a copy of the original json file.
Like Paul said, it does indeed look like you ended up with invalid formatting when downloading/copying over the script, resulting in invalid JSON. Which script did you try to load, and what steps did you take to get the script itself and load it into TimeSeq? I tried reproducing with either copying directly from the json file in GitHub, doing a “Copy raw file” or downloading the file from GitHub, but that gave me a valid JSON file for each of those tries.
The VCV Rack version shouldn’t have an impact on the JSON parsing.
Ahhh… , ok, I got it,
I did the download with a right mouseclick
and “save target as…” on the link in the manual.
After I tried it again, with the raw download,
it loads as expected. 
2 Likes
The script links in the documentation do indeed point to the regular GitHub urls for the json files, so “save target as…” will give the GitHub HTML rendered version. Good that you pointed this out, I’m going to update the documentation links to point to the raw versions instead so that the right-click-save also works.
3 Likes