Damned Dirty Ape
Something looks wrong here. This should only appear on the dynamically generated files that have -tmp in their name. So you click the pencil icon, click edit from the menu, it opens notepad and that's what you see? If you locate the file mentioned there (you can click Show In Explorer off the popup menu when you click the pencil icon) and open the Reaticulate.reabank file yourself (again *not* the one that has -tmp in the name) can you confirm it says what you quoted?So? Is this the right file to edit?
This one's got me stymied. Reaticulate.reabank, when it doesn't exist (as it wouldn't on a fresh install), is created by the Reaticulate main script on first open, and Reaticulate copies the first few comment lines from Reaticulate-factory.reabank (located in the Scripts directory) to that file. I am not sure how the "Generated file. DO NOT EDIT!" comment landed in this file. Had you ever opened the -tmp file yourself? Do you think it's possible you might have copied/pasted something from there into Reaticulate.reabank? I'm mainly just trying to figure out how deep down the rabbit hole I should go on this oneYeah i checked the file. Its Reaticulate.reabank, not the temp, which has these 2 lines. I have started writing custom banks in it and they work fine though
The JSFX instances that are added to each track FX does the work of translating program changes to the output events defined by each articulation. It's actually a design goal that these JSFX instances are able to function autonomously, without the main GUI script, once they are configured. So indeed you should be able to load a project and have playback work without the Reaticulate GUI being open in that session. (While this is a design goal and it's true today, I'm not sure I can guarantee it in the future. )if i edit the bank manually and then the interface is not needed..whats the purpose of the MAIN script then?
Bearing in mind that if you're using your controller to change or insert articulations via Reaticulate by invoking one of the Reaticulate "activate articulation" actions, the main script will be needed to handle that.Once its setup, the idea is not having to look anywhere and just use your controller with your buttons the way they are supposed to work.
I will indeed! Thanks for this contribution. Having done this for all of my Spitfire libraries, I recognize it for the herculean effort that it is.@tack: Maybe you'd like to include these in your Userbanks, too
After I got used to it over a weekend, I decided it's an invaluable tool for digital composing, and in some ways, better than it's commercial counterparts.
I'm interested to know in what ways you think it's better? Knowing this helps me to ensure I avoid changing things that users actually like.
Yes, but there are several reasons for the current implementation.In Expression maps you can write the articulation in the notes themselves. Thst makes the most of using groups in Exp maps. AFAIK this is not possible with Reaticulate. Is that correct?
Not that I've seen, Kabraxis. If you do eventually cook something up, please share it here and I'll post it in the userbanks section on GitHub.So just wanted to ask here before proceeding if anyone else is also tackling that?