john909kid

Happy to report no problems at all. My MBP came with Lion, and after i'd updated to ML I began a Logic 9 clean instal from my upgrade DVD'sl. Again I needed the serial number printed on the manual, and then I was asked for either an earlier serial number or the XSkey to be plugged in. I did this (XSkey) , but after the install, the Logic 9 icon was blacked out with a line going across it. A quick software update to Logic 9.1.7, and Logic's opening up fine. So I was able to install Logic 9 on a clean ML system from Logic 9.0 upgrade DVD's. I hope that helps someone else.

That's very helpful info, many thanks. My boxed Logic 9 upgrade was to upgrade from Logic 8 boxed version (which was an upgrade from 7) From what I can remember, to install this version of Logic 9 I needed both a supplied serial number that came in the L9 box, plus my old XSkey inserted during part of the installation. Anyway i'll see what happens when I do try to install, and follow your helpful advice if that fails. I'll also post back here to report.

That would be the easiest thing for people like myself, however from searches on the net it seems not possible to transfer from a DVD copy of an Apple product, to the same version as on the App Store. This was in regards to apps like iLife, iPhoto etc I'm due my new ML MBP tomorrow, so i'll see what happens when I try to install Logic from my current boxed 9.0 DVD install/ upgrade + XSkey required installation set.

Worrying me too. I've just ordered and am waiting delivery of a new MBP, with ML. My copy of Logic is the boxed "Logic Studio" with a black sticker in the corner saying "upgrade from Logic studio or Logic Pro". I can remember having to use my old XSKey as part of the install process when I installed it on my old MBP with SL. Box also has a sticker with "Logic Studio 2.0 UPG-PLT/GLD 5,6,7" on it. Something tells me this is not going to install on my new MBP, with ML Any ideas on what to do if it does not install?

I'm looking to get a new MBP in the next month or so, which will more than likely come with and be firmware locked to ML. Above does not make for good reading. Thanks for the info Nick.

Not tried with Logic ins. Just these two (PPG 3.V and Pro V) picked out at random.

I created an AU/synth track and pasted the midi notes in with the pencil tool, hard quantised, Creating a one bar sequence of crotchets, and in the region parameter set it to loop. Had two methods of recording the AU to audio.... first i sent the AU to a Bus, then created an audio track with the input as the bus. Recorded the audio. Second and quicker method was to select the regions and then to select export region to audio file. Both methods resulting audio files produced the exact same results. Notes coming in early and jittering. No effects anywhere. Created in a new empty Logic project. PDC set to audio and softsynth tracks. Its weird !!!

Glad i made you smile, As i said i was asking out of interest why it's happening? And more interestingly why notes are coming in EARLY??

One of the said big issues where softsynths trump hardware is in their supposed timing accuracy within the host DAW. The is meant to be sample accurate. So out of nothing else better to do i thought i run a few examples on two of my soft synths picked out at random. From two AU tracks, i then created audio files, and checked the timing in the sample editor. However what i've found is not what i expected..... the timing of each note, without fail, is coming in EARLY off the grid. Ok granted it's not by much.. at the most extreme case I found 35 samples early, which is touching the 1ms region. But this offset was not consistent and there was jitter taking place, with each note coming in early off the grid. This was Logic 9, with audio buffer at 32 samples, tested with PPG 3.V and Pro V synths. No effects on the AU tracks, PDC set to audio and software ins tracks. As I said i know it's not by much and i'm being extremely geeky about this, but I found it baffling as to why the notes are not bang on the grid as i'd expected them to be, but jittering and coming in EARLY? What's going on? Here's a few screens: [image too wide removed by moderator - Please keep all screenshots below 800 pixels, thanks. Read Me Before Posting - Forum Guidelines (#8 )]

Having some problems when recording midi data to midi tracks. In the inspector, the quantize value was set to "1/16", but when i tried to set it to "Off 3840" it'd jump back to "1/16" No idea why this is happening, but i seemed to stumble upon a cure by opening a newly midi region in the piano editor and there setting quantize to "off" Other problem im having which i can't cure is i'm trying to disable the "advanced quantization" paramentrs in the inspector. I've looked in the "View" menu to switch "advanced quantize view" off, but that option isn't there. And also when i now quantize a midi region via the inspector, and chose say "1/32" I get a message saying "Do you want to reset the advanced quantization parameters?" How do i get rid of the "Advanced quantization parameters" in the track inspector?

Is there a menu or setting within Logic, that allows me to see how many milliseconds of latency individual plug-ins are causing on a given channel strip? I like to work with hardware synths monitored live through Logic, with software monitoring on. And with effects on both inserts and aux sends. I have the low latency mode set to kick in at 1 millisecond, so plug-ins causing delay above that setting will be bypassed with the LLM switched on. But neither Logic's stereo delay or D16 Syntorus chorus are bypassed with LLM switched on, and even with a test setting of 0 milliseconds for the LLM! Does that mean neither of these effects cause latency? Somehow I can't see that being the case! With LLM switched on, are effects on Aux sends also bypassed?

This is another important fact which is often overlooked. For example early 90's Rolands were especially prone to slow response times to incoming midi data.

So the conclusion would be the actual DAW/ App is the culprit with midi jitter and not the midi driver.....?

Would the Unitor midi driver (latest version 2.5) be used by ALL programs using external midi/Unitor 8 interface, or just exclusive for when running Logic? Its location is Library-->Audio-->midi drivers, which leads me to believe that its a universal driver for all apps when used with the Unitor8? My thinking is i've tested Logic/Unitor8's midi timing and found it be very good, so would I get the same excellent timing if running Live, and if it were to use the same Unitor driver as Logic does?

That's interesting as I was planning on picking up Live to Rewire with Logic... Thats some money you've just saved my Fader