arjohe

Well, this is strange. Like the problem appeared from nowhere this morning it disappeared in same way. I haven't change any settings from Omnisphere, Apogee or in Logic. I opened the very same project that had this problem and used the very same Omnisphere channels but now the error just don't come.. maybe it will after I work ahead with this project. If it it will come, I will comment into this chain again. But have to say, not very convincing from Logic.

It starts with glitches and scratches type of sounds and in few seconds they grow and then whole audio signal comes distracted and then error pop up appears. Yes, I've tried to change buffer size, doesn't help. But I tested this now by adding Logic own synth ES1 as a new track in my project and played with it. No error, everything works fine. But when switching track back to omnisphere, problem is there again. In Omnisphere I've also checked in system menu master tuning frequency and its 440hz and also changed to 441 hz but didn't solve the problem. In my pro tools is the same setup so 44.1 sample rate in apogee and omnishpere is working perfectly. Clueless...

Hi. No it does not. In fact I use Pro Tools without no problems and have never installed drivers for my key station even earlier in Logic or in any other DAW.

This error just keeps coming even I’ve searched posts for 2 hours on this error and I think I have tried “everything” but still it appears. Yesterday everything was still okey. I have Mac OS 10.9 Maverics and Logic Pro 10.0.7. These I already have done and also see screenshots, they should be attached: 1) Checked that sample rate is 44.1 kHz in Logic Pro project audio and Apogee Duet audio interface 2) Restarted logic and Apgoee and my computer 3) Check Apogee drivers and they are up to date. Even re-installed firmware but didn’t help 4) Have changed sample rate from 44.1 to 48 kHz and back in both Apogee and Logic but didn’t help. In fact When changing this from Logic it automatically changed it correspondingly in Apogee 5) Finally have also tried by using built-in input and built-in output but STILL problem exists. I have just 2 plugins in use: Spectrasonics stylus and omnisphere and only 2 tracks overall. So CPU is not the problem. What next? Exhausted...just started missing my pro tools even its not that good on MIDI If you help me to find solution to this problem I promise to post the solution on this thread. It annoys me when people have spent others time in solving their problems and then not even bother to post solution later...

Hi guys. I've also checked those links before my Logic Pro X purchase and I think there is discussed much also about Avid audio drivers of Mbox. To that part I can still add that yes, even newest 10.3.3 drivers for Maverick **cks a big time. But this is not related to Logic compatibility but core drivers of Mbox 2 Pro for Mavericks by Avid. So if I need to unplug Mbox firewire then firmware of Mbox is not anymore recognized by my MacBook Pro --> I have to restart computer and only then Mbox is recognized. Also computer will crash when I return from sleep mode if Mbox is connected. I'm pretty much 100% annoyed and speechless of how bad drivers Avid has made... But... when Mbox is connected and I don't have to unplug it or use sleep mode (not logic related bugs) and instead just work with it, then Logic itself works like a charm with Mbox 2 Pro. I will update you if I find bugs...

What can I say Thank you a lot! Case is now solved after unplugging MIDI cable and left only USB cable. To me it was new that also midi signals are passed within USB cable, I thought it was only for power supply

It is connected with 2 cables: First cable is USB cable which acts as power source from keyboard to my USB hub connected in my Mac. Second cable is MIDI cable which is connected to only available MIDI connection in keyboard which is "MIDI OUT". And other end of this MIDI cable is connected naturally to my Mbox 2 Pro MIDI IN plug.

Wow thanks for fast and detailed answer! Ok I use just JPG file upload next time, didn't know that it will show directly on post, nice. I also updated my signature as detailed as possible thanks for hint. Anyway, yes you understood it correct (your edit) so those duplicates were generated during recording. And also thanks for your advice, now I can delete duplicates easily, it is like 50% of solution to this problem Other 50% not clear still is that I don't know still why those notes got recorded as duplicates in first place, any idea? You asked me to tell you "how I have things connected". What you exactly like to know? What I did was that I recorded MIDI sequence with my keyboard to empty grid and only once. There was not even loop (yellow top bar). All notes still gets recorded as duplicates, Ive tried this now several times with and without loop.

Thanks for answer Eric! Well, now I've purchased Logic Pro X and so far I have had not any kind of problem with my Mbox 2 Pro after playing with logic few days, also audio recordings work just fine. So this is also to you others who are thinking the same questions I did..

I've recorded MIDI sequence just by playing my Omnisphere plugin synth via my midi keyboard but when I checked recording each note were recorded as duplicates. So when I drag with mouse any of midi note to another location I can see that still another copy of that particular note existed in edit view. Please see from attachment, To demonstrate the duplicate note I've highlighted in red box the duplicated note that I've dragged from the location of note in blue box. How to fix this so that during recording each midi note is recorded only once? This is very annoying "feature"... Could it be some midi setting from Logic I need to change from options etc? Duplicate MIDI notes1.doc

Come on 4GB RAM?! It is a joke. Please upgrade at least to 8 but I strongly advice to update to 16 GB. It is clear the RAM that causes your issues

Hi! I'm Pro Tools 10/11 user who is willing to switch to logic pro x for producing dance music. I have MacBook Pro late 2011, Mbox 2 Pro and Mavericks 10.9.4. Does anyone of you have experience of Mbox 2 Pro and Logic X? How does the setup works, does it have major or minor bugs? I'd like to avoid buying new audio interface which can cost easily around 500 euros so therefore any comments are welcome! As I still found value for Pro Tools as well i.e for mastering with waves etc, in either way audio interface of my choice should support both Pro Tools and Logic X.

Hi There, I have same setup than you except not yet Logic Pro but Pro Tools. Anyway, you need to download latest 10.3.3 Mbox 2 drivers from Avid site, you should find it easy by searching google with mbox 2 pro drivers. Then after install firmware is recognized BUT.. drivers are not working fully ok, for example when you unplug Mbox and plug it back in, system does not recognize it anymore and you need to restart computer again. But however despite of this, actual drivers and mbox are working ok even there is this specific flaw..