More Presets!! 7th chords rule!
Couldn't believe it when I found the 7th chords option, but only for one patch... Those 7th chords sound nice! A quick diff between the 7th chords.orbapreset and others, shows that the only noticeable differences exist in the <ModifierList> and <SeekerList> entries - while I can't decipher any of the actual contents, simply swapping out the entire ModifierList and SeekerList from the 7th chords preset to other presets puts them into 7th chord mode!
Once again, an archive with all stock chord presets as 7th chords is attached. I've also included 'Normal Chords.orbapreset' which is the stock 7th chords preset, but modified to use the standard chord layout.
Furthermore, I've looked into switching out presets for the Android App - this can be accomplished by copying the relevant .orbapreset files to
/data/data/com.artiphon.orba/Artiphon/Orba/Presets/
Since this is not a normal user-writable partition however, root permissions are required
As a workaround, you could load up the modified presets onto your Orba using a PC, then save a new Song on your Android (or probably also iPhone) device. This will save an entire song with Drums, Base, Chords and Lead everytime, but it also includes the modified diatonic Lead voice.
So I've finally bit the bullet and got an Orba, immediately got annoyed by the lack of diatonic options for Lead voices, so I went ahead and copied every standard Lead voice and changed them to be diatonic. Archive with the .orbapreset files is attached, for anyone else interested (and those too lazy to do the work themselves :P)
Side Note; Did anyone else notice that the Lead voices respond to the bumping gesture with a 2-octaves-lowered D-note?
@Bogenregner - Nice to know, thank you.
The Orba stops recording after 8 bars. That could give a result of minutes if you decrease BPM to something like 10 instead of 120. I found this for calculations.
But maybe there are users who have 8 bars at the tempo they like and want it to be longer. In stead of decreasing BPM and re-recording they can simply add some bars.
Maybe I'm overlooking something obvious ;-)
Could it be, that the new firmware update changed the tunings?
My diatonic presets all sound really weird now, and the standard presets sound weird whenever I press the 3rd button.
I don't know if someone has a use for this: Orba + Chill presets with fixed 32 bars instead of maximum 8 bars.
And I don't know if there is a maximum of fixed bars or if it hurts your Orba.
Open song in a texteditor. Search and replace the value after "nBars="
Forgot to mention that there is one LoopData section for each Mode (drums, bass, chord, lead).
The latest desktop/mobile app version allows songs to be saved again. I recorded a simple 4 bar drum loop and saved it so I could see how the loops are stored in the song XML. There is a section called LoopData that contains base64 encoded event data:
I need to save a couple of different drum loops and compare the results. Here's what my first attempt looks like:
00000000: 10a4 0326 6144 4c00 10cf 0324 5e2b 5600 ...&aDL....$^+V. 00000010: 10be 0326 3f2d 4d00 10cc 0324 6a32 5300 ...&?-M....$j2S. 00000020: 10bb 0326 5931 4900 10b1 0324 5435 5700 ...&Y1I....$T5W. 00000030: 109d 0326 4c32 4300 10b1 0324 7146 6a00 ...&L2C....$qFj.
Thanks GJ. The editor is processing the image data (even though not changed) I just removed the ability to swap the image out. I’ll may remove the image processing as well if I cannot get the uuid and cover image hash to work.
PS I tried inserting a line ending + whitespace via editing XML in the editor. That didn't work; after saving the file the insertion was gone.
@ Roger - Not sure if this means anything.
I loaded a preset in the editor and saved it without editing anything. After that the picture didn't show in the Orba app; it was replaced by a generic Orba pic. In the editor it showed the original pic. After a compare in a texteditor I noticed a small difference.
In the original file there is a line ending and some whitespace before 'CoverImageHash'. Maybe that keeps the Orba app from displaying the right pic.
By the way, if you save a number with the old Windows app, you can choose a new pic. After that, the file contains the pic data with uuid / coverimagehash. That data can be transferred via copy / paste to other files, such as a preset. Not very practical, but it is possible.
Thanks, Alan, the base64 encode/decode is the easy part in LiveCode. You can see the image on the screenshot above that's from LiveCode doing a base64 decode of the XL attrubute. The problem is the uuid and coverimagehash. I cannot see how these are generated. I tried MD5 for the coverimagehash value with no luck. When I saved the XML back out with a new image base64 encoded the Orba tool just displays a generic Orba image. I actually don't think 120x120 is a requirement since a couple of custom presets on this forum have larger images but in LiveCode I do resize just to be on the safe side.
@ Roger, Excellent work there, I knew someone would beat me to it, but then I don't know how to code a GUI.
The Cover images are "Base64" encoded graphics files. Basically an ASCII encoded binary of an image, something I recognised from my days as a Production Engineer back in the '90s, which I had to do sending files over a modem and in the early days of to the WWW when you couldn't send binary files through some of the servers.
So to get the images to work,
Start by extracting the image from the XML file, that is the bit between :-
tagList="#basic" coverImage="
and
"coverImageHash
-: i.e. everything between the two quote marks (") and save as a plain text file.
Fire up an online converter, I used the one here
Use "Import from file" and you should see the Orba image created, if you did it right ;-)
Save the image and read its properties. The important bit is that it is 120x120.
Create your own image, in what ever package you prefer, and save it as a 120x120 PNG file.
Yet another online converter, I used the one here
Create the Base64 text file and insert it into the gap between the two quote marks (") in the XML file.
Sorry if this is a bit wordy, but better too much info than not enough.
Automate that into your editor, and we'll have something to wave at Artiphon as to what we have been waiting for.
Andrea Mannocci
This thread is intended to gather the feedback of Orba tinkerers.
27 people like this idea