The unpack command will unpack the FW into a directory with the same as the original file. Then modify will add the database changes, and repack will pack it up back into an .op1 file (named op1_218-repacked.op1 in the case of the example)
The subtle fx params thing will be the next thing I add. Or maybe a GUI… not sure yet.
Enjoy!
EDIT: I’m doing a simple GUI right now so that’ll be coming first. It’ll allow selecting a FW file, choosing mods, and then applying the mods to the firmware in one single step.
After a hint from @crypto I noticed something weird: * Bootloader in the 067 Beta was “1.47” * Bootloader in the 218 release is "2.02"
When diassembling the current bootloader, the same problems arise which we are dealing with the whole time for OP1_vdk.ldr.
So I guess TE now uses the same obfuscation/security method on the bootloader as they do on OP1_vdk.ldr.
This can be seen even without IDA pro when looking at both Bootloader versions with the curretn version of LDRviewer (http://dolomitics.com/downloads/ldrviewer.html) which now has a built-in disassembler view.
The first DXE is looking okay (possibly the early stage boot, deciding whether to load the “rescue” or the normal FW), but the second DXE is pretty useless in the current V2.02 bootloader.
It would be enough to use the original 14203 FW and check if the bootloader stays at 2.02 after the up/downgrade.
That would mean we are not locked into the new bootloader.
Given that all update packs always contain a te-boot.ldr I guess that it always gets updated as well if the version is different.
Just can’t check right now without an OP-1 in reach ;o)
maybe a selection of "14203 patches OR 218 patches" to switch out the default patches in op1_factory.db I hear some peple liked the old patches better than the 218 ones. (I tried merging them but only 16 are recognized by the FW it seems)
Considering that its always possible to add patches and that the default ones subtract boot time (that says in the manual) and also the number of presets available in the op-1 are limited, I would not leave a single preset in a custom fw… Monolake said once that when he buys a synth, the first thing he does is to delete all presets and make its own sounds and then when he knows the synth, he checks through the presets to see if he missed some trick… I really like that approach. Thx for iter/filter btw. I wonder if there is a way to use that filter as a master effect?. cheers.
Again, there are 16 “slots” for factory patches and 42 for user.
Even if you delete the factory ones, you don’t get 16 more user patches.
So it’s just a waste to delete them.
You could of course put your own most favorite ones in as factory patches.
That would be a truly unique OP-1 then…
Again, there are 16 "slots" for factory patches and 42 for user.
Even if you delete the factory ones, you don't get 16 more user patches.
So it's just a waste to delete them.
You could of course put your own most favorite ones in as factory patches.
That would be a truly unique OP-1 then…
Ahh!. I guess the trick to have 58 user patches is elsewhere… Sorry for not reading the whole story…
Wow there is another effect/synth engine available??
Are there any links to pages that walkthrough how to set up? I went back a few pages in this thread and couldn't find anything. Computer programming is completely alien to me. Any help would be much appreciated!
Wow there is another effect/synth engine available??
Are there any links to pages that walkthrough how to set up? I went back a few pages in this thread and couldn't find anything. Computer programming is completely alien to me. Any help would be much appreciated!
Easiest is to load the patches that are shared on page 12 in this thread. No need to use custom firmware, but the filter effect and iter synth won’t show up in the menus and filter is not available as master effect.
Question to the people with customized firmware loaded: Is filter then indeed available as master FX?
Any tips on where to start if I want to… I guess… build customized firmware? Can someone with no experience in code learn somewhere how to do so well enough to create a custom firmware?? It would be great to have a new master effect…
So I just right clicked, downloaded the link on page 12 of this thread… and then dropped it into my drum folder on the op-1. Now i’ve got a keyboard that says “Op-1 patch” hell yeah.
If I click on that link directly it just takes me to a page that says op-1 patch. Not sure what to do to get iter and filter… can someone give me a hint?
Thx for iter/filter btw. I wonder if there is a way to use that filter as a master effect?. cheers.