bones wrote:This seems to be making life more complex again, not easier. Digging into menus can be a PITA. Some simple structure could be handy but making it too complex and forcing people to go into it too often is just robbing Peter to pay Paul, I think. It might keep the Luddites happy but it wouldn't necessarily make things easier for the rest of us.
There are a few reasons why I feel this suggestion makes this 'concept' easily implementable as well as it's implementation a moot point for the people who disagree (and that includes the part of myself that would rather not support the idea in favor of things remaining the same).
You used the term 'modus operandi' in another discuss you and I had, and that term got me thinking a little bit because I'd recently had a random thought on the term and decline in the use of classic Latin phrases in modern this English speaking society and how even I had recently let them slip from my own vocabulary - so the fact that you used one so soon after my contemplating that very topic suggested that perhaps the Universe was screaming at me again and I should turn the volume down to hear what it's trying to say.
I was thinking about the underlying modus operandi and the implementation of features, especially those revolving around the pino roll such as the length option. It's a simple Menu function. Granted I believe this to be an aspect of Orion that is double edged in its wisdom. It keeps the Orion's user environment (and by my logic this extends down into the coding as well making it a part of Orion's smooth operation) but on the other hand they aren't presenting themselves too explicitly and therefore get overlooked; either way all this talk about GUI and virtual folder, pattern pools are all things that make a person envision the feature in the context of its visualization over the ultimate function. The visualization works directly against Orion's MO and this is what I believe to be the cause of about 75% of the disagreement and 80% the cause of the misunderstanding. So for the purpose of cutting out the bullshit, lets pretend it's already there in the program and how it would look if it were a part of the current system.
This is how I believe Richard would have presented this feature based on how I understand Orion as of right now:
In the Piano Roll of the Generator receiving the imported data (can even be set up to include the generator exporting the data and not need to have a specific PR focused) you would click 'Edit' on the Menu Bar.
It drops down the list of options and somewhere between 'Humanize and 'Add Pluck Template' there is something listed 'Pattern Import/Export' and you select it.
A small window pops up in the center of the center of the screen. You select from a list the generator that the piano roll data is to be sent. Then you click the optional data bubbles below a dialog that reads Inclusde: 'Velocity' 'Modulation Data' etc. that will be sent along with the simple notation data to the receiving Piano Roll. Then you select from another list the Generator you want the information sent to.
Then you click 'Ok' and the window disappears and everything is how you commanded.
In other modifications of this you could include a simplified dialog to import all 'bank data' from one generator to another.
This effectively 'pools' all your patterns without having to actually have a physical representation of it anywhere; and even if you add an Import/Export button to the piano rolls GUI pissing off the people who 'would never do such a thing'. I will personally break down and and skin them a new default that does not include the additional button. Unfortunately they will have to learn to accept its existence in the Menu Bar's Edit Tab - but that might be healthy for their mental well being in the long run.
YOU SHOULD ALL PAY ATTENTION HERE RIGHT NOW:
Those pyromaniacs over at KVR have won and have been proved 'right' by this thread. The only difference is that you're not attacking a newbie but rather have cannibalized yourselves by gnawing at each others ankles. A good amount of this is healthy for the strength of the community and the validity of the concept in discussion, but it's gone too far, and I have made at least one or two suggestions in here that I felt were pretty valid and as far as I know the only one to actually entertain them has been Bones, and to a minimum of merely saying 'sorry better luck next time' - but I will check on this and edit accordingly if I am wrong but it really feels like I'm just posting into wind for the entertainment of the evil duck that has been pulling the strings of strife. So I guess all in all, those idiots at KVR have been right and the only reason to pull this into the public view has been to equivocally say
"Yep after nearly 20 pages of bullshit and defending ourselves against this very allegation, we just wanted to let you just how wrong you really were - cause we're bigger assholes than you had actually claimed! SEE! "
When I finally caught up with that fleeing duck from yesterday he told me evil duck would make sure that something like this would happen and I wasn't even going to present his suggestion at all because it seemed that it only existed just so you could keep arguing about it...Then a quick memo from my 'business thinking' department tells me that new functions should not only satisfy the needs of existing customers but attract new ones as well.
So what the hell? I'm already in Samurai Mode might as well give it one more for the sake of futility....so I'm calling evil duck out on this one....