I'd like to be able to store patterns and have them in an easy accessible bank within Orion.
The suggestions i've heard don't really work unless you want to stop what you're doing (music) and start administrating
Suggestions include:
Exporting your patterns from a synth to individual midifiles. (really? and if i have 16+ from one, 7 in another, 20 in a third .. )
Saving them in a template. (9 instruments, 15 effects - delete them all, click through warning dialog every time or turn the dialog off and risk doing a very bad mistake in the future..)
Who is the developer of Orion btw? So many responding sound like they represent the vision of Orion
And please don't get me wrong, i really do like Orion! I recommend it wherever i can and where i see fit. Though it gets harder when you feel like you have to defend your suggestion, question or opinion whenever you post..
Storing patternsModerators: Christophe, Mark
14 posts
• Page 1 of 1
Re: Storing patternsProducing music and be an administrator are going hand in hand if you do it with software. But, for sure, if someone likes to access all possibilities (= MIDI and getting the hole f*ckin knowledge) he does it with cubase etc. As long as I don´t get across the line with Orion and midi, I´ll use this workflowing sound engine.
OK, let´s check if I´ve understood what you want to do with Orion. You wanna store your patterns from Orion´s synthies to a data bank, from where you can access them all. Pattern means the notation of the banks from A1-H8, not the knobs etc. of the synth by itself? Sorry, if I didn´t get it right, ok. If I am right, I would suggest that you use all 128 patterns from each generator, then insert the same synth (WASP #2 etc.) and load the same preset (after saving the preset from the first one, for sure) to extend your "notation-patterns". So you´re limited to have 128 notations each synth instead of having as much pattern as you want for just one synth, but that won´t be that bad, right? You can give each pattern an individual name. When placing them in the song-editor, just klick on the number (or name) of the pattern once. Now there´s a popup menu showing up, giving you an overview of all of the 64 patterns avaible (empty ones are marked as empty, the rest will be shown in order from A1 till H8 (or the names, if you gave them individual names). You can give each synth names, too. The disadvantage is, that you´ll have to do some basic administration like making backups of your pattern library (=Orion song) Ok, far enough. I hope that I´ve understood your request. If not, just tell me. For me, it´s a pleasure to help someone by showing up a possible solution for his demand, no matter if it´s professional or not... "I need more details."
Re: Storing patternswhy not use "STYLES" ? name them and order them how you want.
or is that too limiting, as they are for that generator, and you want to have them accessible for all generators? I have favourite patterns stored as styles, and then just copy the patterns to other generators, save them and build up my "banks" of "styles/patterns" that way. easy peasy, but I guess you want to pull in many patterns at once. otherwise i do a merge in, a do a copy all patterns etc but then i guess that can be lots of work if you want to pull patterns in from many other files.... "I am the all-singing all-dancing crap of the world."
Re: Storing patterns
Styles only stores the one pattern you have selected at the moment. If it would save all the patterns i think the problem would be solved.. I've been working with DIVA the last few days and i've made a couple of projects of which they all contain some cool patterns. I'd like to use these patterns for other projects in the future as they may very well fit in another track. I could store the patterns one by one as a style .. lets say i have 15 patterns in one project i want to save and that i have 3 projects.. 45 brainmelting saves And what would i name them? Im glad diva is a synth and not a drummachine Then there would be the triple amount of saves hehe. Did i mention i suffer from pain in my hands..? Is it possible to "extract" all patterns into separate styles from a generator? That could work for me But 45 times.. no thanks Thank you for your reply!
Re: Storing patterns
Thanks for your reply How do you store the 128 notations (patterns) in the generator? Must you not save it as a Template for that? And if so, deleting every single generator and effect in that project? If i could save the currently selected generator alone as a template and without everything else in the project the problem would be solved .. i think And yes, you understood me right! Im sort of amazed that no one else seem to have run into this problem. Maybe it's because im very spontanious (some would say erratic) and use intuition more than thought. I know some musicians set up a goal and take every step to achieve it. Im more like "Lets jump into the dark and see where we land!". A friend of mine was the first type and we worked pretty good together. I'd make a mess until i found something good, then he'd clean it up and make a song out of it We had a little argument about it once. He was questioning if i should have any credit for a song as according to him i just did some things at random and he did all the work of adding backing drums, building the track and mixing etc. Now, i don't believe in random. Everything that i do is based on what i've learned and how i connect the pieces of information. Im spending a lot of thought into using my subconscious for tasks normally processed in our conscious - though the main reason for this has not as much to do with music. Anyway, it is my opinion that the track would never have existed without the "random" groove i made and on which the track was built upon. I'd love to hear the developers view on this. Is it difficult to do? (i have no programming experience apart from some html years ago). Does it go against the vision of Orion? Is the work/possible sales ratio too low (aka bad investment)?
Re: Storing patterns
Where on Earth did you get the 128 patterns from??? A1 to H8 is 8 banks with 8 patterns each which gives you 64 available patterns per generator.
I think a better explanation of what your intentions are with stored patterns. Currently, templates are your best bet, though if you don't want to dabble with deleting the rest of the unneeded modules, you could use Merge to import only the generator you want (and the patterns with it). Personally, I can't see the need for having just patterns (MIDI data), unless you're making clones of one and the same song. But feel free to put that on my lack of understanding for the feature. That's why I thought a more detailed explanation would be needed.
Richard is as far as ideas and implementation goes (think of him as a main man), though Marcin also develops and fixes things for us
You can't have 128 patterns in one generator. As for the rest, I'm thinking Merge would be better option for you. Instead of having to delete ALL that you don't need, you'll just have insert effects to deal with that come with it... maybe even arrangement but that one is quick. SoundCloud ::: Facebook
Re: Storing patternsThere should be a Copy+Paste All Patterns/Pattern Bank possibility.
I may remember incorrectly, but I recall something 'copy all patterns' was possible in pre-V8. Am I right? Now imagine you were working with your fav synth or a new toy or demo and have made dozens of patterns on that which are there at its pattern bank. (I think it's natural, sometimes we're in the mood of jamming and creating patterns/melodies but don't wanna make songs right then. For me it's kind of two different states, when you're inspired musically and when you're arranging your musical ideas into songs.) So then you wanna free them up from there to browse through them later for some inspiration and to use them for other synths in other project. The Copy All Patterns feature comes in, you copy-paste the bank to a MIDI Out module and save that module with your pattern bank into a template. Later you load the template and will get your pattern bank. You can 'Receive MIDI' from the module for your desired synth in that project or will use the Copy All Patterns feature from module to synth. So a simple improving or the rehabilitation of a former copy feature would please you in your aim of storing, recalling patterns fairly easily and time efficiently. I'm not fully sure, but I remember for sure before V8 there was a copy dialog which had more functionality, than the current 4 copy commands. IMO it was a mistake dump those functionalities. OK, the dialog was dumped, but the Edit menu should have all the former copy commands.
Re: Storing patternsThanks hypnagogia, merge seems to be a tool that i not only missed/thought was something else, but also seems to do what i want
(not saying a way to store pattern's wouldnt be useful still )
Re: Storing patterns
which is why I do this. I have some song files set up, that just contain a bunch of cool patterns, something like a template, so using Styles, and merge, and copy and paste, I have access to all my fav patterns. It can take a little time, to set things up, to do a little admin, but that's not too long. merge is a great feature, and use I it all the time, though sometimes merging in from a complex file it (for me) may take a while, or might even hang, which is why I started seting up my on "templates" that contain stripped down files, makes it easier to merge in "I am the all-singing all-dancing crap of the world."
Re: Storing patterns
Hmmm that begs the question....Why? Instead of Pattern Banks a simple three digit readout box and a couple of spinners would yield 1000 patterns per generator.........certainly more than enough for most anyone? Just a thought.
Re: Storing patterns
Don't ask me, I didn't make it SoundCloud ::: Facebook
Re: Storing patternsMaybe the person who did make it could comment.....
Re: Storing patternsOf course, there are only 64 patterns per each generator. Just did a miscalculation. I wrote down the "64 patterns" at the end of the text when I was recognizing my mistake, but still forgot to correct the rest of the text. Sorry for this!
"I need more details."
Re: Storing patternsto resume :
merge the intrument from the song containing the original patterns in a new song. save as a template. now, in every new song you will be able to insert a template containing your patterns and CTRL-SHIFT-C to copy all the patterns to a new instrument. Yamaha CS-30, Roland SH-1, Roland MKS70, Focusrite Scarlett 18i6, Yamaha FS1R, Oberheim Matrix 1000, Novation Remote 37SL, Korg Legacy, Alesis M1Active 520, Novation Launchpad Pro, Push2, Intel i7-7700HQ
14 posts
• Page 1 of 1
Who is onlineUsers browsing this forum: No registered users and 345 guests |
© 2017 Synapse Audio Software. All Rights Reserved. |