I've been using Pro6.4 for couple years - - for a musician not a geek, the learning curve was huge but now I'm comfortable and have completed many songs with numerous tracks involving audio, midi, including many many virtual tracks and settings, etc. and I'm attracted to upgrading to Pro 7. I hestitate. Here are my Questions: 1) Is the learning curve from 6 to 7 THAT hard? (I realize this is subjective, but given I'm a musician foremost, then a computer geek). I've heard there are new things to learn but it's nothing like the initial learning curve with 6 coming from only working with Word on a computer, and hardware from the old days of recording. 2) Any set-up glitches I should be prepared for? (I have G5, 10.4.1 application, presonus firebox, midi, etc) and all is well with Logic 6. 3) What problems has anyone experienced opening Logic 6 songs into the 7 platform (or can you? Do you lose any virtual sounds?) 4) Is there a way to run both 6 and 7 on the same computer? (For one possible problem: Both require authorization keys) Thanks! I appreciate any replies - - This is a great site - Drleer

Drleer <drleer@yahoo.com> wrote: > I've been using Pro6.4 for couple years - - for a musician not a geek, the > learning curve was huge but now I'm comfortable and have completed > many songs with numerous tracks involving audio, midi, including many > many virtual tracks and settings, etc. and I'm attracted to upgrading > to Pro 7. I hestitate. Here are my > Questions: > 1) Is the learning curve from 6 to 7 THAT hard? (I realize this is > subjective, but given I'm a musician foremost, then a computer geek). > I've heard there are new things to learn but it's nothing like the > initial learning curve with 6 coming from only working with Word on a > computer, and hardware from the old days of recording. While there are many changes and enhancements, learning 7 with a working knowledge of 6 won't be anywhere as demanding as learning Logic from scratch. > 2) Any set-up glitches I should be prepared for? (I have G5, 10.4.1 > application, presonus firebox, midi, etc) and all is well with Logic 6. For the current logic 7.2.3, you need at least OS 10.4.3. The current 10.4.8 works fine here with logic. > 3) What problems has anyone experienced opening Logic 6 songs into the > 7 platform (or can you? Do you lose any virtual sounds?) In theory there shouldn't be any problems. If you were using logic 6 in OSX, any AU plugins you may have been using should open in 7. This was not as simple going from the OS9 or indeed windows versions of Logic with VST plugins. > 4) Is there a way to run both 6 and 7 on the same computer? (For one > possible problem: Both require authorization keys) You can have both logic 6 and 7 installed on the same computer. As your XSkey was authorized for logic 6, you keep and may continue to use this authorisation when you upgrade to 7. HTH, kind regards Mark Cahill

Drleer <drleer@yahoo.com> writes: > 1) Is the learning curve from 6 to 7 THAT hard? No, it's THIS hard. Logic7 is ultimately easier to use than Logic6 and before. Anybody who started Logic with version 7 had a easier time than older users. However, there will no doubt be a few things that you've mastered in Logic6 that have changed in Logic7 that you'll be wondering how it's now done. These are simple to overcome. 2) Any set-up glitches I should be prepared for? (I have G5, 10.4.1 application, presonus firebox, midi, etc) and all is well with Logic 6. You ought to upgrade to 10.4.8, which is a very stable OS with Logic7 and your other stuff. >3) What problems has anyone experienced opening >Logic 6 songs into the 7 platform (or can you? Do you >lose any virtual sounds?) I've never encountered any problems, even loading in ancient Logic 2 files. >4) Is there a way to run both 6 and 7 on the same >computer? (For one possible problem: Both require >authorization keys) Don't bother. By the way, you don't lose the Logic6 authorization when you upgrade your XSKey with Logic7. f-erenc szabo, smarty pants Z+E+R+O+B+E+A+T "NOW POWERED BY THE MIRACLE OF THE TRANSISTOR!" <http://home.goodmedia.com/~zerobeat>

<quotes repositioned and trimmed by admin> --- Mark Cahill <forums@logic-users.org> wrote: > While there are many changes and enhancements, > learning 7 with a > working knowledge of 6 won't be anywhere as > demanding as learning > Logic from scratch. > Mark - - Thanks so much! Very helpful - and encouraging - - Drleer PO Box 4744 Albuquerque, NM 87196 505-256-1019

For what it's worth: I have recently been upgrading from Logic 5.5.1/Win to LogicPro/OSX and have been up and running in no time. There's just some major annoyances in some things that have been changed to the worse (or even way worse), some of them simply driving me nuts. But you may better find out about them yourself, perhaps they don't apply for your way(s) of working. The transition itself however was rather painless. Regards Sascha

On Dec 5, 2006, at 7:55 AM, Sascha Franck wrote: > For what it's worth: I have recently been upgrading from Logic > 5.5.1/Win to > LogicPro/OSX and have been up and running in no time. > > There's just some major annoyances in some things that have been > changed to > the worse (or even way worse), some of them simply driving me nuts. I cannot think of anything that I feel has gotten worse. If you would specify what is bothering you maybe someone could help.

On Dec 4, 2006, at 12:04 PM, Drleer wrote: > Message posted by Drleer <drleer@yahoo.com>: > > I've been using Pro6.4 for couple years - - for a musician not a > geek, the > learning curve was huge but now I'm comfortable and have completed > many songs with numerous tracks involving audio, midi, including many > many virtual tracks and settings, etc. and I'm attracted to upgrading > to Pro 7. I hestitate. Here are my > Questions: > 1) Is the learning curve from 6 to 7 THAT hard? (I realize this is > subjective, but given I'm a musician foremost, then a computer geek). > I've heard there are new things to learn but it's nothing like the > initial learning curve with 6 coming from only working with Word on a > computer, and hardware from the old days of recording. Having written a tutorial on L6, and used 7, I can safely say that almost all of the stuff you know from 6 is the same in 7, it should be a no brainer, with you only learning the new stuff. > > 2) Any set-up glitches I should be prepared for? (I have G5, 10.4.1 > application, presonus firebox, midi, etc) and all is well with > Logic 6. None that I can think of > > 3) What problems has anyone experienced opening Logic 6 songs into the > 7 platform (or can you? Do you lose any virtual sounds?) Only if you went from L6 OS9 (which I don't think exists). Everything translates fine. > > 4) Is there a way to run both 6 and 7 on the same computer? (For one > possible problem: Both require authorization keys) No problems at all. Infact, L7 will look into your L6 plug-in settings folder and add them to the plug-in settings for 7. Be warned though, don't throw out L6 if you want to keep these, or make sure to tranfer your L6 plug-in setting into you L7 user prefs. > > Thanks! I appreciate any replies - - This is a great site - > > Drleer You are welcome, George Leger III ________________________________________________________ http://www.myspace.com/georgelegeriii http://www.utopiaparkwaymusic.com Mac AND PC: The only way to fly 8-}

dennis gunn wrote: > I cannot think of anything that I feel has gotten worse. > > If you would specify what is bothering you maybe someone could help. The EXS editor. See one of my recent posts for details. It has gotten so bad that I'm using LAWP to help transfering a sample library instead of my Macbook. The plugin "chaining". Now, while some people may like it that plugin GUIs automatically open once you select a track, I usually don't, especially since it's showing the inconsistency between audio and virtual instrument tracks even more. Let's assume I have a compressor and an EQ in all of the topmost insert slots of both my instrument and audio tracks. When I select the instrument track and open the instruments GUI in chaining mode, then switch to an audio track, the compressor GUI will open. Highly illogical. I do of course know about the reasons behind that, it's simply that audio instruments are still dealt with as if they were in the first insert (just as back in the 4.x days), only that they have been moved to the input slots. From a graphical point of view the current behaviour however is simply wrong. Plus, I just like the way it was. Besides, if they think this new behaviour is all so great, I'd prefer to see it as an addition, rather than the only method (the additional yellow-ed chain button comes to mind, doesn't it?). I'd gladly use the new behaviour when working with virtual instruments and the old behaviour for anything else. Part naming. Ridiculously inconsistent. Name an EXS object "Bass" and load an EXS patch. Record. The resulting part will be named as the loaded instrument. Which is making no sense in case I switch the instrument later on. I want my parts to be named "Bass" and not "Boom Bang Boom" when I end up using "Thumb Bass" later on. When using 3rd party instruments, the behaviour is changing again. The part *sometimes* (this must be a bug, because it's changing randomly) gets the name of the object, sometimes it just gets a "(not assigned)" label. Sometimes (even most often), after changing the name of the object, the recorded parts will still get the previous name. This *must* be a bug, but it's obviously related to Apples decision to change something here. In any case, I can't see myself enjoying the different behaviour between Logics internal and 3rd party instruments. And even if someone would like that, please do it optional, rather than the new behaviour being a must. Now, someone may tell me this isn't a biggie, but I don't see myself spending quite some time to label my objects so my recorded parts are exactly representing them, just to see Logic messing around with them. Properly named parts are a key feature for me to work quickly. Longer filenames. Yes, even this has gotten worse. They're still not supported, but in older versions I would at least get an error message, whereas with LP they're just getting truncated automatically. Which is horrible, especially when dealing with the EXS. If they *have* to be supported in that half-baked way, please give me an optional dialog to do the renaming myself, instead of having Logic cut away the most important parts of a filename. Several dialog box issues. Ok, not a biggie if you were using Macs before, because you're already used to it. But when you come from Windows, it's such a step back. In all standard dialog boxes under Windows, I can at least do some rudimentary file operations, such as deleting or renaming them. Imagine this was possible for, say, plugin presets. No need to go to the finder anymore to organize them, you could do everything that's needed straight in the open/save dialog box. As said, perfectly possible under Windows. Further, dialog box positions aren't remembered. Possibly an OSX issue, highly annoying nonetheless. For instance, at home I'm using a 19" monitor as my main working space, the internal Macbook one only serving as a secondary monitor. But, as the Macbook monitor is adressed as the main monitor in OSX (and I have to do it that way because the 19" is shared with my Windows machine through a switch), all dialog boxes will pop up there. Again, under Windows the dialog box positions are opened at the very place I dragged them to the last time. File filtering is another thing. You can for instance tell the EXS editor to not show any samples already in use in the open dialog. But what will it do? It will only grey out the used ones. So, in case I'm dealing with loads of files, I'd still have to scroll like mad, even if almost all files were already used. Under Windows, all files are actually not shown anymore. And talking about scrolling, here's another one: In long puldowns (think sampler instruments, presets, audio object assignments), under Windows, once the maximum screen heigth is exceeded, files will be organized in collumns. Brilliant, as you can almost always see everything at once, without any scrolling. In LP I have to scroll like mad. As said, the last points might be OSX issues, but I still fail to see how they can't at least be partially overwritten when other applications (such as for instance XFolders) can come up with their own file organsation scheme as well. Sometimes, "embedding" an application too deep inside some OS conventions is no good idea at all. There might be some further issues, I haven't hammered LP hard enough yet, plus these were the ones I remembered top of my head right now. Don't get me wrong, there's some improvements I really like, but after all, there's still some longstanding issues, plus some new ones that weren't an issue in earlier versions. And honestly, even if I like Apple Loops, channel strips, MIDI assignments and whatever, I can't see the justification for a +1.7.2 version jump. Regards Sascha

--- In logic-users@yahoogroups.com, George Leger III <george3@...> wrote: > > > On Dec 4, 2006, at 12:04 PM, Drleer wrote: > > > Message posted by Drleer <drleer@...>: > > > > I've been using Pro6.4 for couple years - - for a musician not a > > geek, the > > learning curve was huge but now I'm comfortable and have completed > > many songs with numerous tracks involving audio, midi, including many > > many virtual tracks and settings, etc. and I'm attracted to upgrading > > to Pro 7. I hestitate. Here are my > > Questions: > > 1) Is the learning curve from 6 to 7 THAT hard? (I realize this is > > subjective, but given I'm a musician foremost, then a computer geek). > > I've heard there are new things to learn but it's nothing like the > > initial learning curve with 6 coming from only working with Word on a > > computer, and hardware from the old days of recording. > > Having written a tutorial on L6, and used 7, I can safely say that > almost all of the stuff you know from 6 is the same in 7, it should > be a no brainer, with you only learning the new stuff. > > > > > 2) Any set-up glitches I should be prepared for? (I have G5, 10.4.1 > > application, presonus firebox, midi, etc) and all is well with > > Logic 6. > > None that I can think of > > > > > 3) What problems has anyone experienced opening Logic 6 songs into the > > 7 platform (or can you? Do you lose any virtual sounds?) > > Only if you went from L6 OS9 (which I don't think exists). Everything > translates fine. > > > > > > 4) Is there a way to run both 6 and 7 on the same computer? (For one > > possible problem: Both require authorization keys) > > No problems at all. Infact, L7 will look into your L6 plug-in > settings folder and add them to the plug-in settings for 7. Be warned > though, don't throw out L6 if you want to keep these, or make sure to > tranfer your L6 plug-in setting into you L7 user prefs. > > > > > Thanks! I appreciate any replies - - This is a great site - > > > > Drleer > > You are welcome, > > George Leger III > ________________________________________________________ > > http://www.myspace.com/georgelegeriii > > http://www.utopiaparkwaymusic.com > > Mac AND PC: The only way to fly 8-} > > > > > > Hey guys On this topic: I have been using L6.4 on OS9, it does exist. I have a huge bucketload of plugin settings for my logic native plugs, i think i actually got them off the web years ago, or maybe when a friend got L5 years ago, great presets for bitcrusher, autofilter, all the reverbs, everything really. Sadly the same cannot be said for L7 on osx, there are only a few paltry presets provided for the logic native plugs. So, I tried simply copying the files from my OS9 plug-in settings folder to the new folder in app support... no joy. I guess the old files are unreadable by osx. My question is then - is there somewhere to download settings that are either factory or user created for all the logic plugs? Of course I do know how to make sounds myself, but having a big bag of presets ready to start with has been a huge time saver so far, and I'd love to keep working that way! Josh.