Yes, I can make some tutorial eventually. I am actually hooked up with other 2 developments at the same time, so it might take some time to get me started.
I have all of this perfectly integrated in my pipeline and it does work, however in order for others to use it we might need to clean up things and wrap them properly.
The issue here is that I am having to workaround the lack scripting documentation by using more system tools than it would be really needed. If Toon Boom would decide to eventually start supporting the community on scripting, we could make things a bit more accessible, right know I am using too many system tools and the overal usability gets too nerdy, better scripting would simplify it.
In a nutshell:
I am using the external module and storing data as files through the regular IO. However, in order to speed things up and dont waste the hardrives I am using the ram as a drive.
For example on mac I would use this command:
diskutil erasevolume HFS+ ‘RAMimageTOON’ hdiutil attach -nomount ram://8388608
)
The external module obtain transformation data, process it, and output it to the ram drive. Lightwave is instructed to load transformation data on frame change, so an empty animation is playing on the back (the playhead is on in order to force refresh, it is the same method that lightwave studio tools use). I am using lightwave´s nodal motion in order to process the file and translate it into bone transformations, in Maya I would simply use mel. (I omit some tricks for simplicity)
The Display module uses the external module too, this time an automator application wich runs a bash script collects the framebuffer of lightwaves window and loads it to the ram disk as a file, which then the very same module outputs back to the network.
The write module calls lightwave from command line and request a rendered file.
Nothing really too complicated, but the mapping of the bone values has to be scripted otherwise it is a pain. And the ramdrive + all the other elements could be just happening behind the lines in a more automated way.
This would work great as a plugin, maybe a combination of a script, and a lightwave project file.
Anyway I could make some tutorials how to get along with transformations and share data in and out of Toon Boom. Maybe not a final howto, but to look at the general concepts behind.