But be aware, that there is some synchronisation at work, so be careful. If this, too, is set to 48 kHz, all your audio sample rates match across all your programs. I've just added a 500gb my book ext drive to store my logic files but with the hd connected I get an error 'sample rate of 43064, 43072etc. This, the error withstood the restart, and persisted. Tech support, pro app support, western digital support, and the logic express forums have no idea what the problem is. Both are excellent choices from a quality point of view. It seems to be generating from this Waves plug-in The track was originally a mono track, and I chose the mono to stereo version of the plug-in.
Again, we are talking only about Live Input Mode here. I have installed a third-party fan management app because without it the fan never seems to run fast enough and it's very hot. Check conflict between Logic Pro X and external device. Larry Question: I recently recorded using a Midas M32 console. The system doesn't recognize the device.
Thus, I bounced in place using normalizing on, seeing as it's temporary, and I don't feel like leveling it back out for no red. Provide details and share your research! I thought Mojave would fix the fan issue, but it didn't. I'm using an iMac Pro 2017, and Logic had been opening slower than it does on my 2012 Mac Mini. I get them with Albino, mainly. When getting ready to edit this in Final Cut, I create a new sequence, then drop my clip into it. Thanks, Mark Attachments Screen Shot 2012-06-12 at 5.
Once you've pinpointed the culprit, there are a few ways of dealing with the problem, like reducing the maximum number of voices on the synth, or turning off onboard effects, or, and these are the non-compromising options: freeze the track, or bounce it in place. It's just really confusing that whichever sample rate I set the software to, it gives an error for a different sample rate. What if you change the sample rate, save, then close and reopen Logic? MacPro must have more bandwidth on its FireWire bus. Strive to capture clear recordings that need little processing. Regarding your midi, I didn't see what problem you're having with midi? I'm doing that same thing. It worked fine a few days ago, I'm just trying to figure out what is different. Its more or less a universal driver for most sound devices.
If your still having issues after that resort to the Tech guys! Hope that helps Hello, continue after a breakpoint in processBlock Did you mean breakpoint during debuging? What I discovered is that the Soundtrack Pro sample rate preference setting overrides the sample rate of the Final Cut Pro project, resulting in a slow sync drift that will drive you nuts. I just got the same response on a different strip of Ultrabeat, using a mono Waves plug-in, on a mono track, from the same instance of the multi output Ultrabeat. You check it by looking in the top of the Soundtrack Pro tool bar. I have it at 1024 presently. Now that you are using Logic on your hackintosh would you be able to tell me what version you're using, did you make any fixes, does it open up fine? So overall a step backwards for me, but hopefully a Mojave update will fix everything.
Now in playback the audio naturally is slowed down and lower pitched. Fortunately it looks like - not for sure but seems - the error happens only when I am in debug mode. So I guess that it's just a matter of various plug-ins just aren't meant to be, apparently. I can provide details if someone can help. When Soundtrack opens with your sequence in it, be sure the project sample rate is set to 48 kHz.
Now that you are using Logic on your hackintosh would you be able to tell me what version you're using, did you make any fixes, does it open up fine? I can't even get an answer from the forums. If I try to create or open a 48k session, I get the 88. I know because I did it for several months. There might be other plugins that won't work either. If I use Logic Pro at different sample rates, it has no problem seeing the sample rate from my console and adjusting accordingly. Can you explain that to me? I hate when that happens.
And you could always buy another FireWire bus, but that's the money-spending solution. If I try to create a new session, it shows the selected sample rate on the splash box, but when I try to save the new session name, it gives the sample rate error. I see this most of the times, when I continue after a breakpoint in processBlock. On my MacPro, this works with no problem. Alternative is the word I was looking for, not modified.
When they come in at 48k I have to switch the windows settings over manually. This was a perfectly working environment until this past Sunday, and no software has been modified. Might solve the problem to get some of that bandwidth off the FireWire bus. Once it hits the error, the audio sounds distorted, or plays back slow; or plays back slow with distortion. I have rebooted the console, computer and anything else connected.