Quite often I find myself losing precious time (getting RSI) because I want several channels with the same channel settings (same effects, routings, sends, I/O's, whatever). So, I have to do it one by one, which is a big hassle. An option te be able to copy/paste these settings per channel would be great. Remco

At 16:23 Uhr +0100 28.10.2003, Remco Muntz wrote: >Quite often I find myself losing precious time (getting RSI) because I >want several channels with the same channel settings (same effects, >routings, sends, I/O's, whatever). Yes, yes, yes, I've written this to support a couple of times. Let's send it to them all the time. This is one of the big time savers. Just add a customizable Menu to the New in the Environment where I can save my own channel strips. Cheers Hans

>At 16:23 Uhr +0100 28.10.2003, Remco Muntz wrote: >>Quite often I find myself losing precious time (getting RSI) because I >>want several channels with the same channel settings (same effects, >>routings, sends, I/O's, whatever). > >Yes, yes, yes, I've written this to support a couple of times. Let's >send it to them all the time. This is one of the big time savers. > >Just add a customizable Menu to the New in the Environment where I >can save my own channel strips. And a further big YES YES from me too. Environment window...<Options> menu....<Save channel strip> Please!!!!!!! Regards - Colin

--- In logic-users@yahoogroups.com, Remco Muntz <rmuntz@g...> wrote: > Quite often I find myself losing precious time (getting RSI) because I > want several channels with the same channel settings (same effects, > routings, sends, I/O's, whatever). So, I have to do it one by one, > which is a big hassle. An option te be able to copy/paste these > settings per channel would be great. Well, if we copy a mixer object and paste it onto another, we are already prompted to select either "paste new" (add duplicate of source object) or "paste replace" (replace destination object with copy of source object) ... so I guess we just need a third option on the prompt "paste overwrite", which would overwrite the settings of the source object into the destination object (apart from channel number!) Should be easy-peasy, all they'd have to do as far as the user interface is concerned is change that one "do you want to replace?" dialog box. The additional back-code would probably just be a clone of the replace code, but with the channel number preserved. Sounds like an afternoon's work for someone. ============= It's wierd, logic does all sorts of desperately impressive advaned technical things, but there's all sorts of simple little petty things that it can't do,which makes it still feel like a v1.x program in some ways. Silly oversights and omissions, and friendly touches that aren't there. We could probably sit down and come up with twenty or thirty or forty of these little niggles that would be similarly easy to fix ... individually, some of them might seem petty, but cumulatively, they must be causing a hell of a lot of stress to a hell of a lot of people. I think that's where they should be spending their development efforts, turning logic into a more mature inuitive application and sorting out the oversights and inconsistencies rather than starting lots of new exiting projects and ignoring the more mundane housekeeping jobs. I mean, the emagc softsynths are very nice, but at the end of the day, if emagic had not produced an electric piano or organ or vocoder plugin it wouldn't have been a disaster for logic users, because we could always have filled that gap by buying a third- party softsynth or effects plugin. What we Ên't= buy in from third-party companies is workarounds to problems with the basic logic user interface or architecture -- those are things where we are really dependent on the emagic guys.

>Well, if we copy a mixer object and paste it onto another, we are >already prompted to select either "paste new" (add duplicate of >source object) or "paste replace" (replace destination object with >copy of source object) ... so I guess we just need a third option on >the prompt "paste overwrite", which would overwrite the settings of >the source object into the destination object (apart from channel >number!) > >Should be easy-peasy, all they'd have to do as far as the user >interface is concerned is change that one "do you want to replace?" >dialog box. The additional back-code would probably just be a clone >of the replace code, but with the channel number preserved. > >Sounds like an afternoon's work for someone. I really wish we could copy channels too and it is something I have lobbied for for a long time but We who are not writing this stuff are on very shaky ground when we begin to speculate on what is going to be easy for those writing it to implement.

At 16:39 +0900 31/10/03, Dennis Gunn wrote: > > > >>Sounds like an afternoon's work for someone. > >I really wish we could copy channels too and it is something I have >lobbied for for a long time but We who are not writing this stuff are >on very shaky ground when we begin to speculate on what is going to >be easy for those writing it to implement. and (more importantly?) what Marketing decide is worth spending money on :-) -- Best Regards, Gareth Jones http://www.garethjones.com

--- In logic-users@yahoogroups.com, Dennis Gunn <dennis@s...> wrote: > > .. > >Sounds like an afternoon's work for someone. > > I really wish we could copy channels too and it is something I have > lobbied for for a long time but We who are not writing this stuff are > on very shaky ground when we begin to speculate on what is going to > be easy for those writing it to implement. The reason why it ought to be easy is that you can already copy and paste and paste-replace mixer objects via the clipboard. So if the clipboard is holding entire self-contained objects rather than just pointers (pointers on the clipboard for this would be flaky IMO), then it /ought/ to be simple. I mean, if that really is how it works, you could probably even write a simple third-party helper application to do it. ==example=Select Mixer object. Press Ctrl-C to copy the object to the clipboard. Use the helper app to identify and read the self-contained clipboard object (clipboard objects have helpful ID labels), alter the channel number (checksumming, if necessary), and paste it back. Press Ctrl-V to paste the modified mixer object (with its new channel number) back into logic, either as a new object or to overwrite another selected object. And the Ctrl-C and Ctrl-V stuff could probably be automated by the helper app by sending logic the appropriate key commands (and waiting for the clipboard to respond, in the case of Ctrl-C), so you could open the helper window and click a "copy object" button, and a "paste to" button, and have a display textbox holding the number that the object was going to be pasted as. And while you had the helper app running, you might as well also give it the ability to load and save those clipboard data blocks to disk with a short friendly descriptive header (probably in RIFF format), and an appropriate filename suffix (".LMX"?). = So if logic's method of accessing the clipboard is straightforward, it ought to be easy. Obviously its going to be better if the function is built into logic rather us having to use a third party program to do it, but if emagic really aren't interested, we might have other options.

>--- In logic-users@yahoogroups.com, Dennis Gunn <dennis@s...> wrote: >> > .. >> >Sounds like an afternoon's work for someone. >> >> I really wish we could copy channels too and it is something I have >> lobbied for for a long time but We who are not writing this stuff >are >> on very shaky ground when we begin to speculate on what is going to >> be easy for those writing it to implement. > > >The reason why it ought to be easy is that you can already copy and >paste and paste-replace mixer objects via the clipboard. >So if the clipboard is holding entire self-contained objects rather >than just pointers (pointers on the clipboard for this would be flaky >IMO), then it /ought/ to be simple. Ummmm. When you copy paste an environment object all you do is create a new GUI unit for accessing a given track (I prefer call them "channels" as I believe the term "track" as emagic use it is misleading). In other words you are not copy pasting the settings of the track you are just creating a new window through which to view the status of what is going on on that track. If this is what you mean by creating pointers then that is ideed what is going on. Like I said I absolutely agree that it should be possible to copy paste the settings including all the plugins from one channel (as indicated by the track number on the environment object) to another. I just do not think that we here are in any position to say how easy implementing that will be.

--- 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?

Hi List I'm using reason with Logic through rewire; Is there a way to improve the midi latency? Cause right now its pretty bad. Thanks Diego __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/