No, you've made a case against something you don't understand, or that lives only in your head. What I've suggested is something quite different.
Teksonik wrote:I'm afraid your point holds no merit.
EVERYTHING TEKSONIK HAS SAID IS WRONG, LIKE LANCE, HE HAS MADE NO EFFORT TO UNDERSTAND THE CONCEPT AND, THEREFORE, HIS COMMENTS ARE FACTUALLY INCORRECT. PLEASE IGNORE HIS REMARKS. This is the "baggage" I was hoping to leave behind on the Beta Forum. Oh, well...
I still think Global Patterns are a bad idea since they break Orion's current Pattern per Generator workflow.
OK, I will address this one point, just to show how far off the mark you are. If you want to continue to work as you do now, you will be able to. The only thing that might change is the widget used to select patterns. If you want to continue to create patterns separately from each generator and never share them, you will be able to continue like that. Things will only change when you want to move beyond this basic workflow, and those changes will all be for the better.
Here is a way of organising things so that you would never even need to know that it was possible to share patterns. I don't think it is necessarily the best idea but it would mean you'd never even know they were there. When you insert a new generator, a virtual folder is created for it's patterns. e.g
Wasp #1. Now, that instrument would, by default, see and use only patterns from that virtual folder. You could even keep the A1-H8 naming within that folder. However, there could also be a little arrow widget or something that, when pressed, would reveal all the virtual folders for all the other generators in the project, allowing you to also use those patterns without having to copy them across. As I said, this is a way of having your cake and eating it too, but I don't think it is anywhere near the best idea for organising patterns and probably wouldn't be worth doing if that was all we could do with it. i.e. Copy/paste would be just as easy.
Teksonik wrote:Here's an example....Say I load up the fifth instrument in a song. Now I have to remember which patterns the first four instruments used and which patterns are still available to this new instrument.
Why do you? Maybe when you insert that instrument you want to use a pattern you've already made. I don't think I ever insert a second instrument and then create a pattern for it, it is always a case of having a pattern that I need a new instrument for. Anyway, who's to say that a new instrument doesn't automatically show the next empty pattern when you insert it, as happens when you combine patterns? Or that a new folder isn't created to store it's patterns? This is an issue that needs to be addressed, and a mechanism already exists within Orion, it not an insurmountable problem.
Then when I go to the Playlist I have to remember what patterns were written specifically for that instrument...
You already have to work out which patterns are fills, intros, middle-8s, verses, choruses, etc. If you can manage that OK, this won't make it any harder. If the pattern has the name of the instrument built into it, it won't be an issue at all. e.g. Dune-017 or Wasp #1-045. Again, issues to be addressed, not insurmountable problems.
And in the end how many times do you really use the same pattern for more than one instrument?
During the song writing process, I'd say between 20 and 50 times for each song, trying to find the best instrument for each part. OTOH, I only do the arrangement once and that is always when the locations of the patterns are fresh in my head. Once the basic arrangement is down, I can come back to it weeks or months later and the Playlist will tell me which patterns go with which instrument. Even with zero organisation of global patterns, it solves more issues than it creates. With just the tiniest bit of organisation, it eliminates the negative altogether.
Do you really need to have a Hi Hat pattern available for a Bass Synth or Lead Synth?
Why not? It might take you in an unexpected direction and lead to something wonderful. Serendipity is a great spark for creativity.
How many times are you going to use a Kick Drum pattern on a Piano part?
You might want to use it with a drumkit in the Sampler rather than a piano, or try it with Tomcat or Pro9. I've even done stuff where their is a voice sample triggered with every snare (an "ooomph" sound). It is quite a valid thing to want to do.
Or a Melody line in a Drum Synth?
Could be handy to layer it to give the synth part a percussive attack via Tomcat or with DrumRack in Multi Mode (like using the noise osc in Wasp). Again, something you might want to experiment with that is a bit out of left field. You wouldn't think to do it now but it might turn out to be a great effect if it was just a bit easier to broaden your experimental horizons.
Is pattern 87 a Bass drum pattern or a Bass Guitar pattern?
Is Pattern A1 the verse or the chorus? Is this the best instrument to use it with? Could it work better as a secondary rhythm? Your question assumes you already know the answers to these questions. It is in the pursuit of those answers (to the second and third questions) that global patterns work well. i.e. If it can answer these 2 questions whilst only raising one new one, then we are making progress.
Which patterns does instrument number 8 use?
The Playlist will answer that. A better question would be "which patterns
can Instrument number 8 use?" Right now that answer is only about 1/8th of all the patterns in the song. How much better answer is "any pattern you like"?
Think of how patterns will translate in the Playlist. It will be a hodge podge of unrelated numbers or you'll be spending all day renaming patterns so they make sense.
It is like that now. e.g. when you are doing an arrangement, you realise you need a drum fill somewhere that is based on Pattern A1, but the next empty pattern is C7. Those two numbers bear no relationship to one-another, yet would need to sit side-by-side in the Playlist. Mostly I tend to use tricks like making all the verse patterns twice the length of the chorus patterns so I can easily identify what goes where. Those things will still be possible. None of it needs to be any harder or less transparent than it is now. Again, issues to be addressed, not insurmountable problems.
With Orion's current Pattern Per Generator I know that the patterns I have created for Albino that's set to a bass patch will be bass patterns..
Again, you are making assumptions - that amongst your vast arsenal of sonic weapons, Albino is the only instrument that is right for that part. i.e. You are locking yourself in and making it less likely to find the absolute best synth for the job. Either that or you have arrived at that decision by spending some time copying and pasting patterns from one instrument to the next until you are sure you've got the right one, in which case global patterns will make your life much easier.
the patterns I've created for Pro9 will be drum patterns etc etc....if I want to use those Pro9 patterns in another Drum Synth I simply Clone To and if I don't want to keep the Pro9 I simply delete it..everything that Global Patterns can do already without the horrid mess of a jumble of unrelated patterns......
Hardly everything, just one very specific thing. e.g. What if you decided that Pro9 works better in the verse but DrumRack is best for the chorus? You'd have two sets of patterns doing the same thing and if you decide to make a change in one place, you need to remember to go and change it yourself in the other. With global patterns, you'd change it once and it would be changed everywhere. There are many more areas where global patterns will be of great benefit. Even here, there won't be any downside, just two ways of achieving a similar result. Choose the one that suits the situation better. Think of it as the Pattern Mode equivalent of "Receive MIDI from Generator", only much more transparent.