Full Conductor's score with Logic. Is it possible?

I've heard it's possible to create full conductor scores with Logic. Is it truly possible?

hi,
as asher pointed out, making a full conductors score is perfectly possible with logic, but there are issues, little problems, limitations and work arounds that have to be known about to make it a smooth experience.
also, as asher again pointed out, there are many things that are fast on logic than in other dedicated notators, and in general composing the raw material is easier faster and more flexible than a dedicated notator. at least over on this side of the pond, working in logic and exporting to sibelius for the final result is very standard way of operating. now, there is a PDF to XML application which some of us here (not me though - not tried it) have had great success with. i think william levine who does a lot of orchestrating in logic and recommends it.
if err...you can pardon the forwardness...i have on line some sample scores that might demonstrate what is possible in logic.
http://www.rohanstevenson.com/
and go to concert music. 'black ice' or 'devil' are full orchestral scores.
finally, if you do want to get your feet wet with scoring in logic, aside from j prischls tutorial, my mine bit of advice is to understand to concepts thoroughly - everything else will follow from that.
1) score styles. you can have as many as you want on a track/instrument
2) instrument sets. set a KC for their creation. understand what they are and how you can use them to create parts as well as help you edit. incredibly fast and flexible.

Similar Messages

How do you print a Conductor's score

I just started working with an arrange window Symphony Orchestra pallet by Kirk Hunter and now that I have a composition I'd like to see it as a full Conductor's score. How do I get Logic to view and print this score style when it is not a preset style choice.
G5 Dual 2.7 4.5 gb Mac OS X (10.4.8) Logic 7.1.1 motu 828mkII

KC is a key command.
- before you go any further get a cup of coffee and read logics key commands windows thoroughly - esp for the score editor.
- then start assigning things that you think you understand and might be useful and experiment with them. before you know it your understanding of logic will jump around 500%. most of logics functionality is locked up in key commands which you and you alone assign!!!
- once you have midi regions inserted (apple-click in the area next to a track) then you will be able to open the score editor (windows-score editor). if you are going to be using the score editor a lot i would suggest assigning a one-stroke KC to it and a one-stroke KC for closing windows (rather than apple-W).
- the arrange page corresponds to everything you will see in the score page. you can have lots of midi regions with different score styles or quantization levels assigned). logics functionality with regards to scoring really opens up once you use each type of editor to manipulate and edit different kinds of information in different ways.
- the kirk hunter logic templates are not that great in terms of making a score that looks as it should. it is more suited for just making mockups. if you want some tips on how to make you mock-ups and score work together, i have a couple of threads on logicprohelp.com in the 'environments and templates' section which go into more detail as to how to achieve that. you can actually download an orchestral template setup to use program changes to switch articulations (not the only way of doing it!!!) but everything setup so that it will display visually correctly.

The Problems With Logic (as I see them) - PART TWO!

Hello again,
It seems to be a tradition now that as I compose on a track, I keep a text editor open so that I can jot down all the annoyances and problems that I encounter during my creative process... Anyone who missed the previous edition of this topic, please visit PART ONE, here:
http://discussions.apple.com/message.jspa?messageID=3605456#3605456
That said, here I give you "The Problems With Logic Part II":
1. Logic should clear the playback buffer everytime you play. Quite often you start playing and there is trailing reverb/note events from various audio instruments and plug-ins.
2. The sample edtor "save selection as" has no memory of where you previously were in the file browser.
3. If you double click on a wave form, the sample editor opens up with the wave form you double clicked on... Great.. But now, if you go and double click on another wave form somewhere, it just takes you back to the sample editor with the same previous wave form selected (not great). This is incredibly annoying if you are attempting to save out certain edits-- Quite often you will end up saving 5 or 6 of the same exact waveform, thinking you were saving each individual one. GRR!
4. Key commands.. if you try to assign a key command to something that is already used by another feature, you are presented with a window warning you that it already exists.. If you click cancel, then you can no longer enter any keys in the key field.. You are forced to close the key commands preferences window and start over.
5. Key command window: You should be able to search by command.. For example, if I want to find out what "o" is assigned to, I should be able to search by O-- Further, you should be able to sort the key commands by clicking the column titles "key", "command" -- or "midi"... After all, we can sort by name, date, size, etc in the finder by clicking on these column titles.
6. Tempo Tap feature-- I am quite confused by this. There should be a simple way to tap and define a tempo. When ever i try to do this, the tempo is only temporarily changed until I stop playing, and most of the time I get error alerts about trying to sync audio and midi (mind you, when there are absolutely no parts in the entire arrange window). The manual states that with "tempo recording" checked on the tempo interpreter window, that the taps will record tempo changes, but this does not work. I tried doing this, tapping the key command I defined to tempo tap (ctrl-shift-t), and I was tapping at various speeds-- many taps fast.. and Logic recorded tempos of 99-101bpm.. I was tapping atleast around 175-180bpm. I then tried tapping slowing, and Logic recorded tempos of 99-101 again... so this feature obviously is full of bugs.
7. When loading songs, as soon as various plugins such as Kontakt, exs24 begin loading samples, it brings logic to the front. If you're working in the background in other applications while waiting for your songs to load, you are rudely interrupted from what you're doing (such as, selecting from a menu, typing a document, etc) only to be forced to watch a status bar fill up.. and then all key presses at that point become error beeps.
8. Logic's sample memory easily becomes messed up and crazy. Quite often when using AU instruments such as BFD, Culture, and even Synthogy's Ivory. I will switch to that particular track to play on my keyboard, and each sample will be full of horrible pops and clicks-- the kind that destroy speakers. Other times, in a sample of a string for instance, all of a sudden after one second will be a pop and then the sample will be playing at a completely different pitch... I have to remove the AU instrument and reload it at this point.. This happens quite often. Logic should offer a 'buffer reset' so that you can just flash plugins but they reload whatever preset they were set to.
9. Volume faders resolution are lame! There is no reason why you shouldnt be able to access +1.0, +1.1, +1.2, +1.3, +1.4, +1.5, +1.6, +1.7, +1.8, +1.9... Further the display is only so wide and you can't even read the decimal values for numbers -10 and lower. They just appear as 10.
10. When a movie is open, and you are viewing the video output via FIREWIRE, there is a mini-floating window which contains the smpte, position, and movie start information-- However you cannot modify any of these values. You have to switch video output back to "WINDOW" to change the start position of the movie. This is obviously a bug.
11. Changing the movie's start time is very user unfriendly. There should be a simple way to specify to start at a moment of time relative to SMPTE-- So you can just say "+9:15" for example, and it would take you in 9 minutes and 15 seconds, rather than how it is now where you have to think backwards from SMPTE code and subtract.
12. You cannot view video as a window AND output to firewire. There is no reason why you shouldn't be able to do this. For example, if I wanted to output my video to a monitor in a vocal booth-- I can do this.. but I can't see what the vocalist is seeing on my own screen! This is just nonsense. You should be able to output to the screen (desktop mode or floating window) as well as an external firewire device.
13. Saving a song with a movie open should mean that when you load that song, the movie should be up and exactly as it was prior to saving. As it is now you have to select "open movie again".
14. There is still definitely a bug in track automation-- this was really bad back in version 4, but there is still something not quite right here where starting playback will not always guarantee that the automation data is being read.. And in my experiences it results in volumes being incorrect until you stop and play again, and in some cases it will not work at all unless you plot some automation points. This is an intermittent issue-- but quite often activated by placing an audio region from the audio window on a track (SEE VIDEO).
WATCH VIDEO OF THIS BUG:
http://collinatorstudios.com/www/logicbugs/logicautomationbug.mov
15. In the arrange window, sometimes when zoomed in tightly, all parts on a track are selected, and you think that only the part that you are looking at is selected.. you move this part, and now all of your parts are off. Logic should have some kind of visual aid to let you know when ever you are moving multiple selections... Something like, the parts you are moving will highlight a dfferent color or something... This is a similar problem I have with the loop area of the screen.. You can accidentally turn it on when in the matrix window, and have no idea unless you look down at the transport, but with me for example, my transport is at the very bottom of the screen and I am not looking there most of the time.
16. Automation data, when two points are semi-close to each other, suddenly the value of the data is no longer shown.. I can understand that when you are zoomed out, and there is simply no space for this to visually appear, that's appropriate. But as it is now, it doesn't display this information when there is plenty of space for it to be visible.
17. Logic should let you set audio track inputs to the various outputs (1-2, 3-4, etc) and buses.
18. clicking on a track selects ALL parts. This is so so so annoying. How many times have I been editing voice over, and selecting a track, thinking I am shrinking the length of a part, and to find that ALL parts have been shrunk.. SO ANNOYING!!!! This needs to not happen, and there should be a simple way to right-click a track and it will have an option "select all regions"... also, when you click on a track and all parts are selected, if you horizontally zoom, logic zooms into the beginning of the track, rather than the song locator. I don't know what the LOGIC behind this is, but it's not very helpful, it actually is very frustrating.. Zooming should always move towards the song locator position.
19. EXS 24 should have a "reverse/backwards" button so that samples played are backwards.
20. Logic should offer a way to globally increase or decrease a specific automation type (especially volume) globally for all tracks... So if you have detailed crescendos that start at -3.8 and end at +1.6, you can add 3db to this and it will now be at 0.8 and end at 4.6.
21. If you have multiple tracks of the same track (such as three Audio track #1's)-- say you are recording guitar parts, and just copying the track and muting the previous track as a method of maintaining multiple takes for later auditioning. If you draw automation volume data on this track (it appears on all 3 tracks), and then if you delete the audio from one of the muted tracks and tell logic to KEEP it, suddenly all automation data is gone. GRR!!!
22. Several times I have opened Kontakt, and attempted to load an instrument while outputting a movie via firewire video to my monitor. As soon as I try to load the instrument, the firewire video output on my monitor goes crazy, and then comes back on.. Logic then crashes. This has happened 3 times randomly...
23. UNDO does not work on every function. for example, if you change an output to bus 1 instead of 1-2, you cannot undo this. Undo should undo whatever the last command was, no matter what it was. This is what the word LOGICal is supposed to represent.
24. Floating windows (as in plugin windows) should close with apple-w!!!
25. *BUG* If you are in a part that is say 10 measures long, zoom in horizontally 100% in the matrix window-- You then isolate one specific quarter note pitch in the middle of this measure, and have cycle turned on, looping over this one quarter note, if you are not looking at this note event/loop region when you hit play, the display will jump to the beginning of the part and never show you this note event as it loops. However if you have the note event on screen when you hit play, then it will behave properly. This makes it extremely difficult and frustrating to perform detailed hyper-draw work. (SEE VIDEO)
WATCH VIDEO OF THIS BUG:
http://collinatorstudios.com/www/logicbugs/logicloopbug.mov
26. *BUG* Host Automation is not accurate. I assigned Kontakt's tune knob to C#000, and If I place a dip, the knob begins to move way before the automation data is even present.... So basically what I was trying to do, can't even be accomplished because Logic screws everything up by pitching the instrument too early... Such a shame.. By the way, I previously mentioned the importance of being able to display part data in the arrange window as matrix data (horizontal lines) rather than score data. Someone argued what good this would do-- Well this is a perfect example, if I am attempting to affect a particular section of a note with automation, I can't possible visually see where this is because the length is not described by the current score representation. Having a horizontal representation would solve this problem... (SEE VIDEO)
WATCH VIDEO OF THIS BUG:
http://collinatorstudios.com/www/logicbugs/logicctrlchngbug.mov
27. There should be a way to convert stereo samples to mono in the sample editor.
28. When you view "as text" in the environmentt, you cannot drag an object to the arrange window-- Such as to create a bus track.. Now mind you I don't know why you can't just select "BUS" when editing a track in the arrange window in the first place, however there is no reason why 'view as text' should behave differently than when it's viewed as icons.
29. When you drag a bus from the environment to the arrange window, it replaces whatever track was there. It should ADD a track instead of replace-- atleast there should be a preference for how this behaves.
30. Occasionally when dragging a bus from the environment, there is some visual garbage in the track automation (see screenshot).
31. There should be a way to LOAD and SAVE selections in the arrange window. Quite often when editing audio from a countless number of parts/regions, it becomes painful when you have to select and move 100s of audio files. There should be a way that you can just select a ton of regions and save that selection, and reload it at anytime. There are a few 'select' tools/options under the edit window, however they are song specific-- not track specific. So they are completely usesless for what I need.
32. Logic should offer a feature to collect sysex data from midi devices so that patch names show up and can be selected via program change.
33. When no track or part is selected, and you vertically zoom in, Logic should zoom into the center most track.. It behaves very oddly and zooms in more towards the top. This becomes extremely annoying when dealing with a sequence involving 100 tracks, and a part is selected but you scroll far below where the part is.. When you begin to zoom in, it takes you towards the selected part, yet it's not displayed on the screen and you have no reference for what you are even looking at. The rule should be this: If the part is on the screen, zooming vertically will bring you to it. If it's off the screen, you will zoom into the center track of whatever is currently on the screen.
34. I mentioned this in a thread earlier... http://discussions.apple.com/thread.jspa?threadID=752485&tstart=0
There is a bug when using the transform tool involving the 'position' variable. In my example, I was attempting to reverse the time placement of three chords, that occured in a part somewhere in the middle of my song. By selecting the measure start and end of this part, Logic was unable to select or operate with the transform tool (and I tried a variety of transform options). If I moved this part to the beginning of the song, then the transform tool would suddenly work. After some research, I found online someone had said "Position Time position of the event, referenced to the start of the MIDI Region (not of the song)."--- But if I still doubt this is true, because I then placed the part on a new track with no other data, and placed it in the middle of the sequence and in the transform tool under position I selected '1 1 1 1' to '5 5 5 5' as well i tried setting the position to 'all', and none of this worked. This obviously is a bug... If it's not then it's a very serious design flaw. The position should relate to measure numbers of a song, and nothing else.
WATCH VIDEO OF THIS BUG:
http://collinatorstudios.com/video/transform.mov
That is all for now...
For those who firmly agree with me and all of the points that I have brought up now and in the past, I encourage you to contact Peggie Louie, (the Logic HR department contact) at (408) 996-1010 and suggest that she hire me as a consultant to help eliminate Logic's many annoyances. I have tried to pursue this heavily in the past, but sadly I was completely ignored by her on all levels. Maybe you all can help make a difference?
Fighting the good fight,
Patrick J. Collins
http://collinatorstudios.com

11. Changing the movie's start time is very user
unfriendly. There should be a simple way to specify
to start at a moment of time relative to SMPTE-- So
you can just say "+9:15" for example, and it would
take you in 9 minutes and 15 seconds, rather than how
it is now where you have to think backwards from
SMPTE code and subtract.
For this one I'd suggest getting SMPTE calculator. Entering timecode numbers and having to add and subtract is not so difficult, and AFAIC part of a composer's gig. But what I would add, instead, is that it would be fantastic if Logic provided a timecode calculator (edit: even if it was in the form of a custom Logic widget).
13. Saving a song with a movie open should mean that
when you load that song, the movie should be up and
exactly as it was prior to saving. As it is now you
have to select "open movie again".
This doesn't always happen. I've struggled with this for a long time, and I don't know why sometimes the movie will load and not other times. I would also add here that Logic should show the file pathname to the movie. Somewhere...
18. clicking on a track selects ALL parts. This is
so so so annoying.
You can prevent this from happening if you have cycle turned on and set to a set of locators that "contain" the parts you might want to select en masse. I always work with cycle=on so this is not a problem.
21. If you have multiple tracks of the same track
(such as three Audio track #1's)-- say you are
recording guitar parts, and just copying the track
and muting the previous track as a method of
maintaining multiple takes for later auditioning. If
you draw automation volume data on this track (it
appears on all 3 tracks), and then if you delete the
audio from one of the muted tracks and tell logic to
KEEP it, suddenly all automation data is gone.
GRR!!!
Never had that happen. In my experience, telling Logic to keep the data always works.
23. UNDO does not work on every function. for
example, if you change an output to bus 1 instead of
1-2, you cannot undo this. Undo should undo whatever
the last command was, no matter what it was. This is
what the word LOGICal is supposed to represent.
Undo in Logic is highly problematic for other reasons. Here, I think there should be a specific Environment Undo, just like there's a separate undo for audio edits.
29. When you drag a bus from the environment to the
arrange window, it replaces whatever track was there.
It should ADD a track instead of replace-- atleast
there should be a preference for how this behaves.
Right. This is a matter of personal preference. But still there are other ways to get an object assigned to a track. The "thru tool", for instance. No dragging required.
32. Logic should offer a feature to collect sysex
data from midi devices so that patch names show up
and can be selected via program change.
My guess: considering how much sheer time it takes to write this kind of software, let alone debug it with every conceivable device, it's not likely this is going to happen.
That is all for now...
For those who firmly agree with me and all of the
points that I have brought up now and in the past, I
encourage you to contact Peggie Louie, (the Logic HR
department contact) at (408) 996-1010 and suggest
that she hire me as a consultant to help eliminate
Logic's many annoyances. I have tried to pursue this
heavily in the past, but sadly I was completely
ignored by her on all levels. Maybe you all can help
make a difference?
Wait in line buddy!
(LOL)
I must say, I'm very impressed with your list and attention to detail. And I feel your pain, trust me. But many of the things you've listed are feature requests and not bugs. And some of the behaviors you've described I have yet to run across. So this is typical with Logic, that it can be operated in so many diverse ways that no two people run it in the same way, nor would two people conceive the program's capabilities in the same way. But I digress...
I also think there's a certain amount of Logic convention that I don't think you've adopted yet, hence your wish for behaviors that don't yet exist.
I don't disagree with most of your feature requests, and I'm (quite unfortunately) able to say that I'm familiar with most of these bugs and about 9 dozen more. But again, it's important to distinguish between bug, feature request, time to RTFM, and errant behavior that's experienced by a very limited number of users.
There's no doubt that this program has its problems. In particular, your #1 re the playback buffer. And I'm glad you've brought many of the bugs into the light for people to read. Good work.

The problems with Logic (as I see them)

Hello Everyone,
Please keep in mind that I am writing this with the intention of expressing my frustrations, and what I feel would make Logic a better program. I realize not everyone will agree with the importance of what I say, but I am a firm believer of HAVING THE OPTIONS. Let the users choose what works for them and how they can best accomplish the tasks that they need to with their individual workflow.
That being said, here is my list of Logic's faults and why I often call Logic "Illogic".
General:
* Logic should have a feature to automatically save your song every X number of minutes. Final Cut Pro does this, why doesn't Logic? It should prompt you "Logic can automatically save your project if you save it" (assuming the current file is 'autoload') to remind users that they should create a project name and save their work.
* There should be a preference option for all windows to open as 'float'. Once upon a time holding option while double clicking parts would open them as a float (though having to hold down option every time in my opinion is an inconvenience, because I personally ALWAYS want my windows open as a float), however.. now in 7.2 that does not seem to work anymore. So, theoretically after you set your prefence to 'always float', then the when you hold option or control and click on a particular window, it will bring that window to the foreground...
* The loop region at the top of the screen is larger than the time-line ruler tab. This is the #1 annoying thing about logic. so many times, I click on an area of the ruler tab to start playing at a specific section.. and somehow I ACCIDENTALLY click on the loop area... If I could ask for ANYTHING it would be that there is an option to disable LOOPING turning on and off from clicking up there. My 2nd request would be that the ruler tab be re-sizeable so that it can be larger than the loop area. This is especially the case for the matrix window where it default opens up to a sizing where the actual time line is so tiny, and the loop region is HUGE.... Every time I open a matrix window I have to resize this and again the loop area is 2x as big as the timeline area, so I end up wasting screen space just to avoid the annoying loop feature being trued on. My suggestion is, require that the loop button on the transport be the only way to turn on the loop feature (other than key commands), and only when it's turned on can loop points to be set. Why is the loop area so big anyway?!?!
* Logic should offer a TALK BACK MIC button which will utilize the built-in apple microphone or iSight microphone and allow that to be sent to the audio interface. This would be an extremely useful feature for studio recording setups.
* Starting logic takes approximately 5 minutes for me. It says "scanning exs24 instruments" for the majority of the time, and I admit my sample library is huge. however, my sample library has not changed in over a year. Why does logic have to continuously scan it??? Can it not make a reference of how many files, compare and if its larger-- then scan???
Song Loading:
* When audio files are not found during loading a song, it asks you the first time what you want to do "search", "manual", and "skip"... if you click "skip", and then it finds another missing file, it no longer presents you with the "SKIP" option.. but forces you to either search or skip all.. Let's say you have a project that used 5 audio files that are all missing because you had them on a different hard drive, but have copied the data somewhere else. The first two files it asks for you don't need.. but you know where the 3rd file is.. So your plan is to skip the first two files and then click manually for the 3rd.. but oh.. YOU CAN'T DO THAT! You have to find your first 2 files if you want to even have the option to locate your 3rd file... Unless you are planning to locate the files within the audio window-- but still, Logic should not be so unfriendly.
Further, If you choose "manual", and what you're looking for isn't where you thought it was-- You realize you actually want to search for it.. So you click cancel and guess what.. It assumes you want to skip it, and so you either have to reload your project again, or deal with this in the audio window. Bottom line is this window should always have "Search", "Manual", "Skip", and "Skip All".
* When you open another project, Logic DUMPS all of the audio instrument data in memory. This is one of the worst things about logic. If you are working between multiple files-- such as when scoring a film, and you are using different files for different cues, then this becomes a complete nightmare and a waste of your time. Logic should be assessing "What instruments are in common between these two projects"... And utilizing all audio instruments to the best of the machine's memory capacity. There is no reason for Logic to behave like this.. I've had to revert back to previous versions of the same song because some data was different, and I am just trying to visually compare various settings one from the other.. Just clicking from one project's window to the other requires me to have to wait 3-4 minutes while Logic loads all these audio instruments (WHICH ARE IDENTICAL IN BOTH PROJECTS BY THE WAY!!!).. This is just incredibly dumb, and creatively stifling.
* BUG * -- Mind you, if you have two projects open, and you close one.. Logic begins loading all the audio instruments of the remaining project.. If you close that project as it's loading audio instruments, Logic will crash.
Matrix Stuff:
* BUG * If you have a part with lots of notes, and you begin to make a selection and scroll horizontally through all the content until then entire part is covered in the selection... After you release the mouse button and make this selection, quite often many random notes are unselected. This can be demonstrated by watching the following quicktime move:
http://www.collinatorstudios.com/video/logicbug.mov
* When you select a single note in the matrix window, it sounds.. This is a GREAT feature... However, when you make a selection of multiple of notes, they all sound at the same time.. This is just plain dumb. It once blew up my speakers... There is NO reason why a multiple selection would need to sound.. It's just dumb.. bad for your speakers, bad for your ears. The rule should be, if selection box = yes, then sound = no... else, sound = yes.
* When viewing the matrix window while recording, all note events disappear until after recording stops. This is highly annoying (and illogical) as it causes confusion if you are relying on watching the note events in that part to know where you are supposed to come in.
* The grid cannot be set to divisions other than 2 or 3. Musicians use 5 and 7!!! And also, can logic please offer an option to display the grid as NOTE symbols... It is much more musician friendly to see a 16th note with a 3 over it than "24". 24 means nothing to me as a musician.
* Quantizing should allow custom input for tuplets.. So that users can quantize odd figures such as 13:4 for example.
* If you move the song locator to a specific time location in the arrange window, and then double click a part to open it in the matrix window, the window is not opened to the locator's position. Thus causing annoyance and confusion as far as what the user is even looking at.
* During horizontal scrolling of the window, the locator temporarily disappears, making it difficult to find where the locator is-- which usually is a marker for us to know what we are trying to find-- ESPECIALLY WHEN YOU OPEN A WINDOW AND IT'S NOT EVEN DISPLAYING THE SONG LOCATOR'S POSITION!!!
* If you have two parts on the same arrange track, adjacent to each other and you enter the matrix window of the first part.. (assuming the link/chain icon is lit) When you scroll to the end of the note data, logic automatically takes you to the next part... The problem with this as it is, is that it does not take you to the FIRST note event of the text part, but rather continues to align the song locater with where ever it previously was (so you end up viewing somewhere further down in the next part).. To clarify, say you have a part what begins at MM-7 and ends at MM-14, the 2nd part begins at MM-15 and ends at MM-22.. If you begin scrolling the song locator past measure 15, then suddenly you see measure 22. When you really should be seeing measure 15. This is confusing and weird.
* Every time you enter the matrix window of a part, the chain/link button is on. For me, this is incredibly annoying. There should be a way to set this so that the button's default is OFF...
* When you move the mouse around the matrix window, whatever pitch corresponds to the vertical location of the mouse--- that particular key of the piano keyboard on the left side of the window should highlight so you could clearly see what note you are hovering over.. Logic tries to help with this by offering things like contrast options for C D E, but this clearly would be much more helpful.
* With the velocity tool you can (MOST OFTEN ON ACCIDENT) double click on empty space in the window and cause all note events in all parts to appear on the screen-- Yet once you do this, you can't double click on a particular part's note to only display that part again. You have to switch to the arrow tool to do this. This is inconsistent and ILLOGICAL...
ON A SIDE NOTE: PLEASE ENABLE A FUNCTION TO DISABLE THIS "ALL NOTES OF ALL PARTS APPEAR" when double clicking on empty space feature! I want NOTHING to happen when I double click within the matrix window... Make it a button within the window or just an option in the drop down menu only. * BY THE WAY * When you DO double click the background of the matrix window and multiple parts appear.. If you move notes of one part to match it up with other, it is incredibly slow. there is a 1-2 second pause each time you move a note move.. My g5 fan goes on each time I do this.. I'm sorry, there shouldn't be anything too CPU intensive to accomplish this simple task!!! I am only viewing 2 parts at the same time and it's slowing down my cpu...
* Occasionally when I adjust note lengths, I accidentally double click on an actual note.. This opens the event list editor, and there is an intermittent bug where this note sounds-- and for some reason when the event list opens, the note sounds on top of itself a million times, so the result is a super loud flanged note which again, almost blows up my speakers and hurts my ears... PERSONALLY, I would like an option that DISABLES the note event list from opening by double clicking. Preferences currently has "double clicking a midi region opens: <selectable>"--- why not also have "double clicking a NOTE in matrix window does: <selectable>"-- and please allow "DO NOTHING" to be one of the options.
* Why does the finger tool only change the end position of the note event??? Should this not be replaced with the bracket tool which appears automatically when using the arrow tool on closely zoomed in notes? This finger tool seems like an outdated old logic feature which has been replaced and improved upon. What would be nice is to have this bracket tool where we can be assured we are altering note start and end positions without moving things.
* In the hyper-draw >> note velocity section--- This is highly annoying to work with... It's far from user friendly. first of all, to move a note's velocity position, you have to click on the "ball".. if you click on the line, it does nothing.. Because the ball is so small to begin with, quite often the user is going to miss the ball and somehow begin to "START LINE"-- Which is weird because it's activated by holding the mouse button down briefly. There really should be a "line tool" for this, because "START LINE" is too easily accidentally activated-- this is frustrating for the user. Most important though, these 'velocity markings' should be adjustable by clicking on the line as well-- not just the ball.. there should be a 2-3% area around each ball/line which logic will recognize as part of the ball/line so that it can easily be moved. I also feel that there should be some specific features for this section, such as a way to select multiple note velocities and apply a random pattern to them, or apply a logarithmic curve to the line tool. Yes, you can accomplish this stuff somewhat with the transform tool-- but this way would be more user friendly, and allow a lot more creative flow.
Event list/Tempo list:
* When one event is selected, by moving down X number, holding shift+clicking SHOULD select all events between those two points. However, the shift key for some reason acts as the OPTION key does in the finder-- (meaning it will only add one additional selection at a time).. This is highly inconsistent with the actual behavior of a Mac... Open a finder window and hold shift and click on items that are not vertically next to each other and a group is selected... Now do it in logic, and it causes GREAT frustration and annoyance. What happens if you have a million note events that you want to erase? You have to go page by page and click with shift on each one?? Or drag a selection and wait for logic to scroll you to where you want to go?????????? No thanks.
Arrange stuff:
* "REGIONAL CONTENT" (meaning the visual representation of note events) does not accurately depict the event data as note lengths cannot be visually identified. Everything shows up as a generic quarter note... My #1 suggestion is that regional content should be customizable so that you can view it in a miniature matrix data style. The biggest problem for me is that I cannot see where my notes end-- I can only see where they start, this makes it very difficult to identify what I am looking at.
* Track automation data should only be inputable by the pencil tool. I cannot mention how many times automation data has accidentally altered when using the arrow tool. The pencil tool should allow you to raise and lower the lines reflecting automation data... What is the point using the pencil tool for automation if it's only function is to create "points" yet you can also create points with the arrow tool..??? Pencil tool should act as the arrow tool does in the sense that it raises or lowers automation data.
* Recording preferences do not offer the option to automatically merge new part with existing part when a region is NOT selected. How annoying is it to have to select a part every time you want to record something just so it will be included in that original part!
* Ruler at the top of the screen should also give an option for tuplets. 5, 7, etc.
* When in record mode, if you click on the ruler to another time position, all audio instruments cut out and it takes approximately 3-4 seconds before tracks begin playing audio. This becomes very annoying if you are trying to do a pick up and want to just start 1 measure before hand.
* There should be a way to EASILY (without having to cable two tracks together in the environment) temporarily link multiple tracks together so that automation data will be duplicated. So theoretically you can link 3-4 tracks together, and by adding automation data to one, you are adding it to all 4.
* If a part is soloed, and you hit record. The part stops being soloed and you can no longer hear it. This makes it impossible to record a pick up on a soloed track unless it's locked, but it shouldn't need to be locked.
* When you are zoomed in tightly, and you are trying to align notes within two parts on different tracks (meaning using the PSEUDO NOTATION DATA that appears in the part to align), there needs to be a VERTICAL line that snaps to the note closest to the mouse cursor. When trying to do this in parts that are a far vertical distance apart, it becomes VERY difficult to eye this alignment. Logic does this with automation data.. but for some reason they left it out for actual part alignment...
* There should be a way to force the downbeat of a measure to occur at any given moment... What I mean by this, is composing for film is an absolute PAIN in Logic. Scenes, last for odd amounts of time, and Logic's reference manual claims that you can solve this by using various tempo tricks, however it is ineffective for the most part. What Logic needs is the ability where you can click on a drop down menu item within the arrange window and FORCE that where ever the song locator is, the rest of the measure is eliminated and a new measure downbeat occurs right there. This will allow you to always have new scenes on the downbeat of a measure without having to mess with your tempo and meter.
Hyper Edit Window:
* I can't even begin to comment on this... The hyper edit window is one of the worst things I have ever seen in a music/audio program. It is a horrible interface, you can't get it to do anything correctly without messing everything up. This thing needs a complete overhaul... I mean, just try to create a simple crescendo with note velocity and it will take you all night.. Try to add pitch bend data, and it adds note velocity data as well.. It's a total nightmare, and I would love to hear someone's practical application of this window.
Score Window:
* The method that the song position locator moves along with the notation is very strange. It is not at all how a person's eyes function when reading music. A much more logical approach to this would be for a transparent colored block of some type to highlight an entire measure, and each note head will glow as it sounds. The current way is so strange, it speeds up and slows down-- makes absolutely no sense, and it is more disruptive than anything.
* When the Hyper Draw > note velocity area is exposed, if you use the velocity tool to increase/decrease a particular note's volume, the data in the hyper draw window does not update in real-time as you use the velocity tool. This behavior is inconsistent with the matrix > hyper draw's note velocity section-- where as in that area, the velocity ball/lines do update in realtime.
EXS24:
* when you are in many levels of subdirectories and you are auditioning instruments, it becomes very time consuming and annoying to have to continually trace through all the subdirectory paths. There should be a feature directly under the load instrument window that takes you to the subdirectory of the current instrument.
* Seems when SONG SETTING > MIDI > "chase" is turned on... When starting sequences using audio instruments, (I am using a harp sample within the exs24), there is a latency hiccup upon starting, which is very disruptive when trying to listen to a short isolated moment in a composition. And I do want to chase note events in general-- but this present situation makes it difficult for me to work. I would suggest that you can specify tracks to exclude chasing.. Or fix the latency hiccup issue.
Thank you.
-Patrick
http://collinatorstudios.com

this is excellent patrick. can you number your points so that the thread can be discussed?
1. yes
2. ok
3. great idea
4. even better idea. you could set something up with aggreagate device i suppose but it would be better to have the feature to hand.
5. you need to look into your project manager prefs. scan the paths and the links to the audio files will be saved meaning they will load up in a fraction of the time.
6. yes this is nuts. you can skip all and sort it out with PM but then you shouldn't have to.
7. this exists already. perhaps it ought to be a default but you need to set your esx prefs to 'keep common samples in memeory when switching songs'. then it will do just as you wish it to. you can also use the au lab in the devlopers kit which will allow you to load in au units etc seperately from logic, which logic can then access. this is a good way of getting around the 4 GB memory limit with logic too.
8. ok, don't know about this bug.
9. yep happens here too.
10. doesn't worry me this one. you can turn off midi out.
11. yes this is silly.
12. well, i think this is something we can get used to. i am a musician and i am used to seeing '24'.
13. you can already set up groove templates to allow for quantizing irrational tuplets. i do it all the time. i would like to see step input for irrational tuplets though.
14. yes this is silly. the button for the KC 'content catch' is getting very worn out.
15. ok.
16. not sure i understand this one.
17. yes this drives me nuts too. i have to lock screensets to get this to stay off.
18. you can use KCs for 'go into/out of sequence' - but yeah.
19. ok
20. there are a couple of features that use old technology that cause hangs and poor performance. score is a good example of that. maybe the matrix is too. the score is being updated we assume with newer technology maybe the matrix will too.
21. there are probably better ways of adjusting velocity than using matrix or hperdraw velocity. have you tried holding control-option and click dragging a note in score?
22. as i pointed out in 20, this is an old feature. you could change things to be consistent with modern macs and annoy long term users such as myself, or leave them and let them be inconsistent to confuse newbies. i think depending on what it is we oldies could upgrade our work habits.
23. this one doesn't worry me so much.
24. good point (no pun intended).
25. well, i find the opposite - that merging new parts to objects i have accidentally selected to be annoying. perhaps more detailed prefs?
26. yep.
27. this will be down to your audio settings. you can improve this lag but it will be dependant on the capabilities of your system.
28. i don't know why this feature doesn't work in logic. it is supposed to have ti already and i just don't understand why it doesn't. maybe it will be fixed in the next upgrade.
29. agreed.
30. ok - i have other work flows for this but it would be nice.
31. i don't agree that logic is a pain to score with to film, i do it nearly everyday. but you are discribing an interesting feature which might be worth discussing more. i think you might find yourself getting alarming and unmiscal results doing this that will end up having to be sorted out the conventional way. but its a good idea.
32. oh yes.
33. yeah - this could be improved.
34. ok, well i wouldn't go about it this way, but yeah there is generally sticky spots with regards to updating of information al around logic.
25. very very good idea.
26. there are lots of problems with the chase function. very annoying. i certainly agree with this.
in general, some of these could well be done as their own threads. some of the missing functionality may exist. if you can confirm a bug then you are on stronger ground when you submit feedback. but this list is full of fantastic ideas.

I have Logic Pro 8.0.2 and would like to upgrade. I'm running OS Lion on a 2010 MacB Pro. What is the best option? Logic Pro 9 App or Logic Studio? Can't find upgrade price. Or should I just stay with Logic 8?

I have Logic Pro 8.0.2 and would like to upgrade. I'm running OS Lion on a 2010 MacB Pro. What is the best option? Logic Pro 9 App or Logic Studio? Can't find upgrade price. Or should I just stay with Logic 8?

Same here, I have Logic Studio 8 and wouldn't mind staying with that version, except that the installer won't run on my new Macbook Pro as PowerPC apps are no longer supported. That's the message I get in any case.
I use to run Logic on a 2006 Macbook Pro.
I guess that makes me a very unhappy Apple user! I've been using Logic from the Emagic days, bought every upgrade only to see Apple kill what used to be one of the best Pro Audio application. Imagine if they had done the same to Photoshop, there would be a lot of unhappy designers out there
Paying the full price for years to slowly see your daily app go down in price & efficiency until it's given away at $199 for semi pro users. Well, at least ProTools is stil alive & kicking so I guess that's the way forward now.
This is coming from someone that never ever used a Windows machine to make music! Life is good still!

Problem with Logic Pro and Soft eLicenser on Mountain Lion?

Hi!
I have a bunch of Arturia synths, which requires the Soft eLicenser to work. This has always worked great with Lion, never any problems with eLicenser (never had to open it etc.)
Now - I upgraded to Mountain Lion, and tested my synths to make sure everything was OK, experienced a bunch of problems, and did a full recovery to clean Mountain Lion.
After installing the Arturia synths, and adding my licenses, I installed Logic. Everything worked fine!
BUT!
When I closed an Arturia synth within Logic, or closed Logic after running a project with one of these synths, I couldn't reopen any of these synths within Logic afterwards - In fact, I couldn't open the stand-alones either! And when I tried to open the eLicenser Control Center, it would just say "Reading eLicensers" forever. After a reboot, everything is OK.
I can open and close eLicenser Control Center and standalone synths as many times as I want, as long as I don't open Logic, and then Arturia synths as an AU in Logic.
I found a workaround: Open the eLicenser Control Center, and let in run in the background (cmd+H), and then open Logic. Then I could open Arturia synths and close them, close Logic and reopen etc. without any problems at all. NO PROBLEMS.
Until I close the eLicenser Control Center, then I have to reboot to be able to start it again.
I hope you understand what I mean here. It's a bit hard to explain.
In short terms: Logic makes Soft eLicenser crash when a eLicenser synth has been opened as an AU.
The same problem is when scanning the AU with AU manager. eLicenser window should be open before scanning.
Does ANYBODY have the same problems? Can anyone who has these applications test it out?

So it definitely seems to be a issue with Logic.
I can't force this error in 10.7.X no matter how hard I try, but in 10.8.2 it's definitely Logic messing things up.
Could it be auvaltool which has a bug? Or is that only run with AU manager on validation?
Hopefully this discussion can get some attention, and maybe it could be corrected. I guess a lot of Logic Pro users also has eLicenser Control Center for validation of their products.

The topic of scoring to film with logic...

Hello everyone,
I wanted to get a little discussion started on the topic of scoring to picture and how people here do it with logic.
My experience with this has been quite on the side of frustration, and I've always thought "wow--- is it really this dumb?.. It CAN'T be this dumb.."
So, when I talk about scoring to film, the biggest issue is the scene change-- something might be building and building and tempos increasing and rising and rising, and then suddenly BAM.. scene change, slow ambient music... Then scene change, fast paced intense music... When dealing with creating music notation for something like this, it's especially important to make sure that the note events are strict in time and on the beat (quantized, etc) so that your scores make visual sense and players won't hate you. "Yeah-- umm this 32nd note really is a quarter note happening over here.. But.. You know how Logic is.."
My thought always was-- if Logic just had a "create downbeat" operation, it would solve all of these problems. You could have a section of music that abruplty ends at Measure 175 on beat 2.7431 and force 2.7431 to become measure 176-- and then you could assign a new tempo, a new time signature, etc.
Logic's manual likes to talk about using tempo operations to achieve this, but this is when I ask "is it REALLY that dumb?".. I mean to be required to have a zillion crazy tempo changes in order to bypass beat 2.7432 through the end of beat 4, just seems counter intuitive, non-user friendly, and completely non-musical.
So... I am asking, how do you guys feel about this, and how do you deal with it.. Am I the only one who thinks this is dumb?
-patrick

There has been no improvement or change in automation behavior between 7.x and 8.x, unfortunately. If anything the behavior has gotten buggier/worse in L8. But that's a different story and not related to what I mentioned previously about beat mapping.
Automation data is time-stamped when it's written; but if you change the tempo after the fact, the spacing between notes will either compress or expand. Therefore, automation data (TBA, track-based automation) is "malleable" with respect to tempo changes. This actually makes sense to a certain extent, but it's not a good paradigm for automation to operate under when you've got automation data associated with specific regions. To put it more simply, if you lock a region and there's automation associated with it, the region will be locked but not the automation data.
The workaround, as you hinted at, is to convert your TBA automation data to region-based automation data (RBA) prior to commencing tempo change operations. This is exactly what I do in this case, and it's become a regular part of my routine. It's kind of a PITA process, but absolutely necessary if you want to preserve your automation data prior to commencing any edits to the tempo.
The procedure is to create an additional track for every track in your arrangement. If you're doing big orchestral stuff, for example, you may have dozens if not hundreds of tracks, maybe within folders, etc. That's where the "PITA" part comes in. But anyway, once you have a duplicate of every track in the arrangement, use the pencil tool to create a blank region on once of those tracks. Extend that region to go a little beyond the end of the arrangement. Use the color palette to give it a color that's not used for any of the other regions in your arrangement (you'll see why soon).
Copy that blank region to every single one of those duplicate tracks. Then, with one of those blank regions selected, use the "select similar color" key commands and all of the blank regions will now be selected. Then invoke the command to move all automation data to region data.
Finally, Select-ALL and tjem SMPTE-lock all of the regions in your arrangement. At this point you can change tempo/commence beat mapping with impunity. (For S&G's, if not for safety, check the "protect MIDI" checkbox in beat mapping prior to doing any beat mapping operations).

How to do this with Logic?

Hy!
Any ideas how i can realize this with Logic?:
http://www.youtube.com/watch?v=tE7GHgbmlP0
Are there any (freeware) loop plug ins or something else I could use?

Yea, but what if we want to make our own loops, instead of using what apple is providing?
If you're questioning whether you can make your own music loops in Logic as opposed to just using Apple Loops, then you're totally misunderstanding some of the most basic functioning of Logic. That's like asking whether you car will drive you around the block. Logic is a very complex multi track audio and midi sequencing program. Not only can you make any type of sound or audio or midi sequence and loop it to your heart's delight, you can make multi track sequences, songs, complex orchestral arrangements, movie scores, soundscapes .... shall I go on?
I just got LP8, and I'm just learning it too. Are you really saying that you can't do anything similar to that video with Logic?
Absolutely not!! In fact, SC's post 4th down tells you how to do something similar. Not EXACTY what's in the video, but SIMILAR.
Here's the difference: You can't record a single measure drum beat and then have it automatically loop indefinitely *in real time* while you layer more drum beats onto it, each one being recorded after a single measure and played back without stopping. In Logic, you can record a measure, then tell Logic to loop it, and then create another, loop that one, etc etc. The only difference is you're not doing it in 'real time' without stopping, you're building a sequence of looped sounds manually in the arrange. The OP seems to want to do it live, without the beat stopping. For that you need Ableton or another program with 'real time looping' capabilities. The only reason you'd want to do this would be if you A) want to impress your friends, or B) are trying to create beats in a live situation, like a club or something. If that's what you're after, other programs like Ableton Live are better suited for that.

Anyone using Mac Mini as a DAW with Logic?

Hello Applers',
I am currently using an imac as my DAW ith Logic Pro 9. I am wondering if anyone is using a mini with logic and how does it perform. The one thing that worries me is the 5400 RPM drive and I fear that the Solid State drive, even dualed would not offer enough storage space for the Long Haul as I currently have over a TB filled and an external TB drive 70% full with older files on my Imac. Just looking for opinions here and thanks!
mmarsyada

just activate robust in your airport window

Help with logic pro 8!!

Hi everyone, I just switched from garageband to logic pro 8 and cant seem to get any sound from my monitors. I'm using a lexicon alpha v interface and my monitors are m-audio av30's. I'm also using a m-audio oxygen49 midi keyboard. This setup worked great in garageband but I cant seem to get it to work in logic pro 8. Logic 8 does recognize the keyboard and I also changed the preferences to the lexicon alpha v but still no sound. I'm really new to this so please be gentle! Thanks

I got a good deal on ebay full retail brand new un-opened box with licences. I couldnt afford logic pro 9 so I went with logic pro 8. Plus I'm still learning, when I get better I'll upgrade to logic pro 9.

Help with Logic Pro 7 and Yamaha 01X please!

My friend has purchased an 01X, a 20" G5 iMac with 1.5GB RAM and Logic Pro 7. He is not the 'techiest' of people so was rather hesitant about going this route for his recording purposes. Having used a Yamaha AW4416 to successfully record an album, he figured that the 01X with Logic would be the next step up the ladder of useability & functionality.
Unfortunately, he is having a great deal of difficulty in getting the 01X to talk to Logic. He purchased and installed the Logic 7.1 update in the hope that things would start to work. Unfortunately, that hasn't helped either. All the 01X is able to do is start and stop the 'play head' in Logic. None of its other functions are having any effect. He is also having problems with mLan.
So, before he throws the whole lot out as a bad idea can anybody provide any success stories with Logic and the 01X. I am hoping to visit him this weekend to see if I can help. However, whilst I know a whole lot about Macs, I have no experience with the 01X or Logic (I used Cubase VST in the past on a few projects). Any help or pointers in troubleshooting this would be very gratefully received.
Lol

i've been looking into getting the 01X and been doing some reading. i have no experience with it but i'm interested in hearing more about how you get on. i did find that www.o1xray.com has a forum full of information about setting up logic and the 01X. ElmerJFud seems to be the main dude, his post has a lot of setup information: http://www.01xray.com/forums/showflat.php?Cat=7&Board=01X_Macintosh&Number=19978 0&page=0&view=collapsed&sb=5&o=&fpart=1

EW and VSL with Logic 64 bit

Hey guys,
any news yet on using EW play edition and VSL Ensemble pro with Logic 64?
so far I haven't seen any problems, but I haven't given it a full run yet, what about you guys?
cheers
David

You say this is from a flash memory camcorder? Can you be more specific?
Webbie camcorders, like the Flip, may shoot in hi-def, but they also record to a non-standard codec that can cause some of the problems you're describing.

Has anyone tried M-Audio ProjectMix IO with Logic?

Has anyone tried M-Audio ProjectMix IO with Logic?
I know M-Audio's drivers have had issues, but it looks interesting.

The Fishman Triple Play is simply the best hardware option to date for triggering external MIDI whether hardware sound modules or software instruments.
Having used many MIDI guitar converters since '89, I can say that the FTP tracking is very accurate and velocity dynamics are reasonably wide from soft to loud.
The Triple Play app works in Stand Alone mode in OSX 10.7.5 but not in 10.8.3.
In 10.8.3, you load the Fishman Triple Play plug-into into the I/O of a software instrument track. Open the app and adjust sensitivity, mono vs poly, transposition down or up an octave, etc. Save your set ups as presets which can be scrolled through with the D-Pad control on the converter.
While the GR-55 is an amazing all-in-one solution in a small, light weight package (in relation to the bulk and weight of several actual guitars, basses, amps, fx, etc), it is a poor choice for triggering external sound sources. Whereas I can play "bass" lines on the open E and A strings with my now obsolete Roland GI-20 and RMC piezo equipped guitar without any sense of latency, the GR-55 latency was simply intolerable. Of course one could revert to the old strategy of playing parts an octave higher on the fret board to increase speed and accuracy of tracking. But what about playing "piano" with fretted triads against the open E or A strings???
Think I'm full of hot air? Skim through this: http://www.joness.com/gr300/MIDI_SPEED.htm
I traded my GR-55 towards a JTV-59.
Once set up, you're gonna love the FTP. As I mostly sequence MIDI in Logic, being wireless is incredibly convenient.
Message was edited by: CC#11

Apple Pro Rez Codec with Logic Pro??

Has anyone used or seen the Apple Pro Rez codec (HD quicktime codec I believe?)? I will need to be working with this very soon, and while it's 23.98fps and I know Logic doesn't support that frame rate, I need to know if it can be used via a canpous FW box with Logic? Does it need to be exported? Etc?
Any thoughts or experiences anyone has would be greatly appreciated. thanks so much-
Josh

I presume you will be producing music for picture(?).
I have not used it myself but I know that any movie encoded with it will be very cpu intensive. The codec was developed for video editors, to enable (practical) high quality hi-def editing. Most folk believe a new high-end macpro is the only computer that is capable of using this codec successfully, but that is with regard to video editing.
A movie encoded this way would be definately unsuitable to use alongside logic. There would be just too much CPU power going to the movie playback, leaving very little for logic.
Your best bet is to re-encode the movie with a more efficient codec. You'll see picture quality reduce but this should not be a problem.
Personally I would never use a codec thats any more demanding than DV. And DV is pushing things on lesser computers.
I suggest you get quicktime pro if you haven't got it yet and export the movie with a different codec. I have used the codec Photo-JPEG with great success. It's gentle on CPU resources and provides proper full frames - important if you are doing frame accurate sync.
The other way you could do it is to run the original movie on a second syncronized computer
Your BIG problem is that logic itself will NOT work with 23.98fps properly. From what I recall, this means Logic's timecode will not match the movie's (as it can't be set to 23.98fps). There really is not a fix for this other than getting "production" to allow for it and (somehow) provide movies with an alternative frame rate. To be honest this is one (very good) reason to use a different DAW.
I wish you luck. This is the sort of thing that could prove a nightmare!

Using two monitors with Logic

I've never used two screens before, so can someone please answer these basic questions?
With LE and Logic Pro, can you have whatever window you like on each monitor - for example Arrange window on one and a score editor on the other? Or is it limited to certain combinations?
And if you've got the mouse cursor on one screen, how does the cursor get to the other screen? Key combination or just push the mouse further across?
Hope someoen can help!

Hi Robin
I´ve been using 2 monitors for several years now, and it´s very nice with logic pro. I can´t live without it anymore.
You can use whatever windows in combination to build different screensets. Think of it as it´s one big desktop. When you move the curser near the border off one monitor it pops up on the other. Go for it, you wont regreat it.
nice regards
Henning Flintholm
G5 dual 2.0 Mac OS X (10.4.8)
G5 dual 2.0 Mac OS X (10.4.8)

Full Conductor's score with Logic. Is it possible?

Similar Messages

Maybe you are looking for