They should look pretty cool side by side, much like they interact very well in the sonic domain. Here's a preview of the TR-707/727-style matrix editor that I have just created for it:Īnother side project is a TR80R skin, reusing much of the UI elements of Permut8. I'm making steady progress but it takes a lot of tweaking until I'm satisfied. In the end it will probably become a 808-ish 'dark mode' skin and a 707/909-ish light toned skin. The main skin I'm working on now is a vintage style mashup of the classic Roland drum machines. Things like those knobs with planets will likely end up there - which led me to the idea of using astrological symbols in the first place: So I'll probably make one skin more focused on some colourful eye candy at the expense of strictly rational functionality. And in some circumstances I find myself quite sensitive to variations in user interfaces when it comes to inspiration, style and creative flow. Well, not always, of course, but it is easy enough to switch between different skins now. Looks really nice, is that a freeware font? So you don't want to be able to read the patch and preset names? That's a bold move. Love to see you using Blender btw! I'm gonna do an 808-style knob in Blender as well - for the switch button I might get away with convincingly faking it in 2D. plenty more work needed, but definitely getting somewhere already. Still lots of tweaking, testing and polishing to be done. Here's a preview of what I'm working on, the design idea is "dark with blinking buttons" and now things are finally starting to look somewhat consistent. It's non random, because it is AI controlled! :p Messing up Roland's logo for some skins for D16's drum machines was both easier and funnier - I just scratched out the R's 2nd leg to get "Poland". I think I need to come up with a better solution that will not break with every update. Updates from us will often include changes to the. cushy files may be a bit too deep for skinning as they define all kinds of aspects of the user interface, including a scripting layer even. Check the main.cushy file to see what it looks like. We do have this technology fully implemented in the other products and partly in Microtonic (for the bar at the top, the PO-32 section and scripts). And I'm sure users would love to see an easy method to switch between skins once we have some interesting options available. how could we convince you to code up a minor update for slightly expanded skinning support? I'd love to be able to change control locations, dimensions, and hit zones. While I do enjoy a challenge of working within the given restrictions. In case anyone else likes to add those nifty log scales (for the 3 horizontal frequency sliders and the 4 vertical attack / release sliders) from the Vintage Tonic skin to the default skin, I quickly made both a light and a dark version - I haven't made up my mind which I like best. ![]() Library/Application\ Support/Sonic\ Charge/Microtonic\ V3.3\ Resources/ None of them seem to work. Library/Application Support/Sonic Charge/Microtonic V3.3 Resources/ Library/Application\ Support/Sonic\ Charge/Microtonic\ V3.3\ Resources Library/Application Support/Sonic Charge/Microtonic V3.3 Resources Library/Application\ Support/Sonic\ Charge/ Library/Application Support/Sonic Charge/ Library/Application\ Support/Sonic\ Charge Library/Application Support/Sonic Charge Then I tried various formats for the path, e.g.: It contains a variation of the file background_x2.png. On my MacOS 10.13.6 system, I placed a folder named Microtonic V3.3 Resources in /Library/Application Support/Sonic Charge (where Microtonic Scripts also resides). It is also possible to create a text file named "Microtonic V3.3 Resources Path.txt" containing the full path to where you want Microtonic to search for resources.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |