just a short note… on ‘releasing’ the easter egg mode…
I’m just back from Superbooth, and got a bit of a cold, but hopefully in next few days my plan is… release the ‘template’ easter egg patch, and a video that explains what the feature is, how to use it , and its limitations. (subject to how im feeling etc )
the basics are already detailed above, but to add some details to the picture…
the idea is simple, you will take a template patch and throw it and an existing organelle patch into a directory as a subdirectory under ‘usermodules’ - then you can use that patch as a module in Orac.
(one directory for each patch/module - the name of the directory is the module name)
it should ‘just’ work, with many different types of patches,
but there are some limitations:
(this is the reason this is both experimental, and unsupported)
- you can only have one ‘patch’ module loaded at any time
- no parameters will be saved in presets, since organelle patches don’t have them… a preset will merely load the patch module.
- no midi or modulation learn
- I’m supporting mode, and its unlikely it will be ‘improved’
- I don’t want these ‘converted’ modules to be ‘advertised’ as Orac modules (which should probably come up with a name for them).
users should be able to expect that an orac module is ‘fully featured’, unlike these hack modules.
will all patches work? probably not…
- there may be some issues with initialisation on some patches
- patches that are dependent on the ‘current directory’ may fail
however, in these cases it should fairly quick/simple to modify the patch to make it work.
all these limitations exist because of how Organelle patches are written,
its why we ‘convert’ patches to modules, to make them co-operate, and integrate nicely into a common environment (orac)
the reason I created this ability, was really to be a way to help people into module development for orac, to see the limitations ‘patches’ have, which really helps show why Orac is designed the way it is… to understand the difference between a module and a patch. by doing this, I hope users will understand why its not possible to ‘just load organelle patches’ into a module.
hopefully also if users find a particular patch useful in the Orac environment, then some one will be willing to make it a proper module , so that the above limitations are removed.
(this ‘mode’ also might help patch developers move a patch gradually from organelle patch into a full patch, a bit at a time - though its not personally the way I do it )