Skyflash36

Try using a low pass filter at around 11khz. I've heard that this helps cut down on the aliasing caused by the crappy myspace player at the highest frequencies. Also for some reason stuff that is over compressed tends to sound the worst through the player,so watch out for your 2 buss or mastering.

I would like to know this too as I've had this same issue before on my Macbook CD 2.0. It's pretty sad when 3rd party plugin can perform better than Logic's own EVB3.

I had an issue when transferring audio/midi data from Pro Tools session. I exported the midi first,then all the audio from the PT session. When I opened Logic and imported everything, the audio was lined up perfectly but for some reason, the midi tracks that I imported were way out of sync with the rest of the session. I even went back and verified the tempo in PT and found that everything was set right in Logic. What is even stranger,is that now the session plays fine. I have only seen this a couple times so far and not enough to warrant a Logic feedback report...yet.

Thanks for replying guys! I'm on a Blackbook Core Duo w/ 2 gig ram. I installed 8.02 and the other night I was in the middle of playback and the audio just completely dropped out using my Project Mix. I still had metering,but the audio was just gone. I tried to re-select the driver and "apply changes" but still no go. I had to quit and restart Logic to fix it. It seems maybe in order to get the new Apple FW driver version, you have to upgrade to Leopard now? I own a Firebox too as a portable solution until I can afford a Duet,so until M Audio releases an update for the PJ Mix FW driver, I could get by for the short term if it means having this stability now.

Other than Seclusions, what are everyone's system specs? This sounds encouraging so far and I may end up with Leopard sooner than I thought if all holds well for everyone. I heard there is a fix for USB audio in 10.5.3 must be FW too?

Mine is flawless,but then again I'm still on 10.4.11. This is one of the reasons I've been holding out on Leopard. I hope you find a fix and/or Maudio cleans up the driver. The other FW drivers are out of beta now,so it shouldn't be too long.

I'm using my Project Mix as MCU in 8.02 10.4.11 Like Krzys, my FF and RW was 'broken' but deleting MCU from the controller prefs and a re-scan fixed the issue. Solo and mute work fine here before/after re-scan. Selecting Aux's works here also,the channels highlight in Logics mixer window but here too, the "SEL" button LED doesn't light up which suggests a minor feedback issue as Fader8 has indicated.

I'm glad to say everything is running fine now. I ran the uninstaller and chucked everything else in the trash cleaned all the Korg stuff out. I re-installed everything and all is forgiven now. Not sure what that was. Maybe the component files got corrupted somehow? I wonder if the AU fixes might have botched something along the way.

Well things seem a little snappier here on 10.4.11.....BUT... Korg Legacy Digital AU instruments don't work at all now. "Failed to load AU. Please Contact the manufacture for an updated version or further assistance" (-10110) This really sucks cause I'm using the Wavestation on 4 different songs at the moment. I guess I'm off to Korguser.net to post this. I guess I should run the AU validater and see what else is lurking.

Using a Blackbook and runs fine here!!. I'm getting lots of work done now. Stuff it full of RAM,get an external FW HD and you'll be rockin.

I had this issue where a single 2 bar midi region I recorded and copied over 20 or so bars,the volume fader kept resetting. It was driving me nuts . I nailed it down to a single verticle stripe that copied on every region and upon opening it in the piano roll editor, I clicked at the bottom to find that midi controller data from my K2000 was recorded by accident when my modulation wheel was left in a forward position. This same single midi event was recorded across every region. I went in, deleted the copies,wiped the controller data and all was forgiven.

I have the KLD pack,but haven't got into the M1 yet. But a quick look at the manual describes it. I have yet to try this,so we'll see. When it's in Multi mode,each of the 8 sounds, or parts can have it's own output destination within the plugin. Each part can have it's own midi channel assigned as well. You first need to select the M1 from the Multi-channel instrument menu in Logics channel insert. So if you have 8 different sounds you want to use as separate 'tracks' all you have to do is assign the outputs for each sound from within the M1 itself. Then assign the midi for each of those sounds. Now, in Logics mixer, the channel strip with the M1 should have the "+" at the bottom. Click on that 7 times and you'll now have 7 aux channels automatically assigned for each of the M1's outputs,in addition to the main outputs.(1+7=8 channels for 8 sounds) Now for your midi routing,theoretically, you should be able to record separate midi parts and route each to the same M1 channel. Not sure exactly how to do this,but I imagine you right click on a new midi track and it should have an option to route it there. You may have to create a multi instrument in the Environment in order to do this,not sure. You could try recording the different parts on the same track but changing the midi channel on your keyboard controller or in Logic's Inspector midi settings. Setting key ranges for each channel,this should work. When I get a chance later, I'll try this and report back myself. -Brian

Anyone using this setup with a Macbook Core Duo 2.0? I just ordered a Project Mix and should be here Tuesday, just wondering what to expect. I have the latest build of M audio's FW driver.

Anyone using this combo? I'm looking at a PM I/O in the next 2 weeks to month and was wondering how it's working for anybody. Are the drivers stable? I don't plan on moving to Leopard anytime soon so thats not a concern. Once I find it stable, I'm gonna get the Black Lion mod for it and hot rod it.

Hello folks I've been having a good deal of success with L8 up until today. I've got an issue with outputting midi that I hope someone can help me with. I have 2 soft. instrument tracks. Both are using an External Instrument plugin. Both external instruments reside on my desktop PC(they are XP VI's only) One is the Taurus bass synth plugin,the other is a pad synth. I'm trying to trigger each from it's own track. The pad synth is set to channel 1, the bass synth track is set to channel 2. I am using a Firebox and I have selected the FB midi output port on both tracks. When I play the sequence, both external synths are triggering off each others tracks. The Taurus synth is being triggered from the pad synth track,and the pad is being triggered from the bass synth track. Both tracks are set to the same midi output port(the Firebox) but are set to their own channels. When I play on my controiller, both external synths are also being triggered as well,regardless of what channel my controller is set to,and which track is selected in Logic. I have environment objects created for each external synth,and again everything is set to the same port,but separate channels. For some reason I can't get each track to trigger it's own external synth. Is there something I have to setup in the environment to get this to work? It seems it should be easy as cake to do....unless this is a bug?