--- In logic-users@yahoogroups.com, Dennis Gunn <dennis@s...> wrote: > ... > I just do not think that we here are in any position to say > how easy implementing that will be. Oh, I agree that we outsiders aren't in a position to say how easy it /will/ be ... but we can certainly make comments on how easy it /should/ to be, if (as claimed) logic was really designed architecturally from the ground up to be robust and expandable. But perhaps it wasn't. Perhaps logic is a set of nuggets of great "engine" code linked together with code that isn't really very good. Hmmm. The reason why I'd /hope/ that logic was pasting complete objects to the clipboard (at least, in the case of small objects)is partly because you can then reuse the tested code for general import/export, partly because without that your clipboard functions are a bit crippled, and partly because it means that you then need a whole extra set of error-handling stuff to deal with what happens when you paste an object pointer that refers to an object that has since been changed or deleted. But if they only used pointers on the clipboard for copying and pasting mixer objects (temporary references to where target info is stored inside logic, rather than a copy of the info), you wouldn't be able to copy a mixer object via the clipboard from song A to song B unless A and B were both in memory at the same time, with the source object unedited since the copy operation. It could mean that when you copied an object to the clipboard then edited or deleted it, you lost the copy. That would be really crappy. <Tries it, pasting a copy after the original is deleted> <logic promptly goes wierd> Okay. Looks like you might be right. Looks like they haven't written a particularly robust program. Explains a lot. <Tries copying and pasting a mixer object between songs> <Finds that even that doesn't work> Jeez, this is bad. You can't even copy-and-paste these objects between songs that are in memory at the same time? No wonder they tell you to put all your favourite mixer settings inside your autoload song. But of course then when you get logic Control and need to have your "used" channels consecutively numbered, you can't just move a set of useful settings to consecutive channels. Hence the other guy's RSI problem, presumably. <tries drag-dropping an individual plugin object between two open songs via the respective audio configuration windows> <still no dice> Oooh, bad bad bad. So the AC window allows drag and drop of plugins, but only between slots inside one song? They aren't even using pointers that are valid between two songs in memory at the same time under the same instance of logic? This really is a truly lousy implementation of the whole clipboard business. =========== Okay, apologies to everyone for suggesting that adding channel copy- paste should be trivial. In a properly designed program it would be, but it looks as if logic hasn't even been designed to properly support standard actions like reliable copy and paste between open documents inside a single application. And if they don't even have the infrastructure in place to support those sorts of basic building-block functions, then additional development is probably rather difficult (unless someone wants to go back and rewrite and debug all those functions the way they should probably have been from the beginning, which is probably a big job). <sigh> I'm beginning to think that perhaps they need to take logic's engines and objects and embed them in a whole new program that is designed to look like logic and import the same songs, but with the objects tied together with new code, that supports stuff like proper clipboard functions and object tagging and tag import/export, and a notepad, and session info ... Maybe if-and-when they eventually release an OSX-only rewrite, all these things might be fixed. Maybe. Anyone know what's expected to be in version7?