As I understand, the "shared patterns" and "global patterns" are two different concepts.Lance wrote:that's wrong my wished improvements would only make some sense with your shared patterns! That's an outright lie! I let the readers decide if that idea what's seen on that video would need your shared patterns.bones wrote:The stupid thing is that Lance wants to see some other improvements that only make sense with global patterns, functionality he's seen in videos using other hosts, but he refuses to see it.
Shared PatternsModerators: Christophe, Mark
24 posts
• Page 2 of 2 • 1, 2
Re: Shared Patternsplease.. what are the basic differences between a "Pattern Pool" and "Global Patterns"?
Re: Shared Patternsglobal patterns are shared by all synths, a pool that you dip in and out to use a set of midi data, so you lose the A1-H8, and have, for example, 999 patterns that exist 'somewhere'
all ideas are based around that, in some form, tho others are trying 'new' ways to basically copy/paste notes and automation from one pattern to another copy/paste seems the obvious answer, that could get implemented for automation and the problems would be solvesd with no interference to current workflow, nmo addition GUI stuff needed etc, but otyhers seem to want to make it more complex. most of this seems based around an idea that musicians want to use the same notes and/or same automation over and over in various synths in the same project. very strange, kinda like phil spectors 'wall of sound' Windows 11 Home - 12th Gen Intel(R) Core(TM) i5-12400 2.50 GHz -32GB RAM
250GB SSD - 1TB HDD | M-Audio Oxygen 25 V
Re: Shared Patterns
There was a fear of losing the current and beloved instrument specific pattern system (pattern bank / instrument) of Orion because of a global pattern system (1 pattern bank / 1 song). I have proposed a compromise idea, which wouldn't upset the current instrument specific pattern system just would add some plus. I called it Global Pool. But these were closed beta discussions and idea, not intended to be brought here. In the Global Pool feature, the user could send patterns into a Global Pool by a single mouse click, and load from a pool of patterns made for shared usage. So not all the junk would be there, just those patterns which the user think useful or needed to have available at other instruments too. This mock-up shows the loading from the Global Pool (the upper arrow is the Send button area, the lower arrow is the Load button area):
Re: Shared Patternsokay. that's along the lines of what I was suggesting when I mentioned the MIDI-out generator; though I was thinking something more benign than that, it wouldn't be on the playlist even, but it would sort of act like a dummy-generator in that it just has A1-H8 patterns associated with it, but unique to these is their ability to be played by any instrument/generator.. to avoid confusion, they could only be edited via the Global-Pattern module piano roll.
Re: Shared Patterns
That's the culprit IMO. Even when I'm copy-pasting patterns I change the copied stuff immediately as I copied it mostly for reference and/or making the variation of it faster, by not recording/programming it again from scratch. So frequent reusing of the same stuff is not my cup of tea. So while I'm not against Bones' Shared Patterns idea, but I'm not keen to see my Global Pool idea to happen either. But at least these ideas wouldn't upset the current instrument specific system what couldn't be said about the original Global Patterns idea.
Re: Shared Patterns
Quite the opposite, it saves you having to create and discard a lot of garbage. You're working under the assumption that you will save every single thing you do. I probably only save 10% of the things I do, the other 90% is just experimenting with different things, to ensure that everything is the absolute best I can make it. So I end up with dozens of copied patterns that don't get used in the final mix.
Not even close. You have to make a copy of a pattern and then use it, instead of just using it from where it is. How can you not understand that creating copies is wasted time and effort, no matter which method you use to do it?
You don't need to import anything, that's the whole point. If you select the wrong pattern, then you just select another and another until you find the right one, exactly as you do now. Mind you, most times you will have the correct pattern selected in another generator, so you will know which pattern you're after before you start. Its a complete non-issue and a more suspicious man might believe you are deliberately trying to confuse the issue.
That is just making copies. I want a way of working where I don't have to constantly be copying and pasting or dragging 'n' dropping. Why? Because, as I said, 90% of the time I won't end up using any of it, I'll just end up with masses of unused patterns in every song I work on or I'll have to go back and clean everything up manually at some point. It much more elegant to try a pattern form here, then another, then a pattern from somewhere else or try the same pattern on 20 different instruments without having to make even one copy of it. You mentioned that I use a lot fewer generators than you (or most other users), well that's why - I spend hours, sometimes days, finding the one right instrument that works without having to layer it or drown it in effects. That's why it takes me 6 months to finish a song.
Well, you'll need to give them a lot more information because what you've shown doesn't explain where the moved or copied patterns end up, i.e. where you would go to edit them, or what would happen to automation or anything else. e.g. In the first part of the video, you move the pattern from one instrument to another. Does that mean the pattern no longer exists in the first instrument or is it simply removing it from that specific position in the Playlist? None of this is clear.
If you have to do that, you may as well just copy and paste them. Having them in a global pool doesn't make them any more useful if you have to go through a process to get them there. And again, for the 90% of occasions when they won't be useful, I will have wasted my time with it anyway. I don't want to waste my time, I want to use it constructively.
What? Are users on the beta team not permitted to use the Wishlist forum like everyone else? Are our ideas somehow none of the business of those who will ultimately have to use any that are implemented? I'd suggest that no ideas should be discussed on the beta forum that have not already been discussed here. Otherwise it gives the beta team more power than other users, which is totally unfair. Dell G7 (Hexa-Core i7)|Cubase Pro 10||Analog Keys|Ultranova|MicroMonsta|Uno|Skulpt|Craft Synth 2.0|
novakill.com
Re: Shared Patterns
Not at all, although that would be one use for it. I'd use it mostly so that I could more easily experiment, trying out different parts on different instruments. I almost never write a song using the instruments you eventually hear on stage or on an album, in much the same way that some musicians write songs for their rock band on piano or acoustic guitar. When I'm writing, I just want to get the idea out of my head and into Orion. Once I've got it down, I'll start production on it, which will mean trying out lots of different instruments until I'm happy with each part. That has always involved large amounts of copying and pasting patterns. Its even worse when I'm working on my bandmate's songs because I almost never use any of the same instruments he does, so every single pattern needs to be copied and pasted multiple times. Sometimes I'll end up with 20 copies of the same pattern, which is just stupid but is the simplest way to achieve my goal. Of course, Shared patterns would be far less useful here, as patterns would be deleted with instruments, whereas Global patterns would make them persistent, so I could delete every instrument and start from scratch with just the patterns. For me, that would be awesome but apparently it would render Orion completely unusable for others, although they are not quite able to explain how or why. Dell G7 (Hexa-Core i7)|Cubase Pro 10||Analog Keys|Ultranova|MicroMonsta|Uno|Skulpt|Craft Synth 2.0|
novakill.com
Re: Shared Patternsyou can already do that (try patterns with diff instruments) two diff ways
receive midi form clone to do we really need a 3rd way to do the same thing? Windows 11 Home - 12th Gen Intel(R) Core(TM) i5-12400 2.50 GHz -32GB RAM
250GB SSD - 1TB HDD | M-Audio Oxygen 25 V
Re: Shared PatternsReceive MIDI from is very fiddly and cloning only works once you have an arrangement. SHIFT+CTRL+C/CTRL+V is much more efficient than either (which is why I use it). Receive MIDI from would also have to be one of the least known features - how often does a question come up around here where it is the answer? So it is not going to help new users.
Dell G7 (Hexa-Core i7)|Cubase Pro 10||Analog Keys|Ultranova|MicroMonsta|Uno|Skulpt|Craft Synth 2.0|
novakill.com
24 posts
• Page 2 of 2 • 1, 2
Who is onlineUsers browsing this forum: No registered users and 366 guests |
© 2017 Synapse Audio Software. All Rights Reserved. |