Latency issue Logic pro 9.1.3.

Hey,
At the same time as upgrading to Logic from Garageband
I bought a Cakewalk Roland UA25EX ext usb soundcard because i was told
i'd have latency issues if i used the caps lock keyboard for midi
or direct input thru the input jack of
my MacBookPro
(5,3 Intel Core 2 Duo 2.8 GHz)
Sometimes i use the caps lock keyboard to sketch in midi ideas and mostly it's ok.
Other times it's delayed and there's no smile on my face.
When recording with guitars/303/generators DI thru the soundcard
I have latency issues that don't seem to be very regular.
Sometimes it's worse than others.
I make sure i have nothing else running on the computer,
just Logic Pro 9.1.3, so it's not like i'm overloading macbrains.
I have tried all the rebooting, i/o buffer size changing (down to 256), headfones from the mac output/headfones from the soundcard/ etc
but still no luck.
I can record with the low latency button on
and it's kind of better, nearly, but that means i don't get to record with the effects on the channel strip
that affects the recording/playing quite a lot, as i'm used to recording with effects/guitar amps if i go DI.
This was the selling point - that i could record DI wthout disturbing Thee Neighbours.
It seems to have gotten worse recently.
I wonder if it's been corrupted somehow because it also has been acting funny when i bounce down -
the play head is set to 1111 and i save - then in the bounce window
the start position says a silly random number and it takes a few attempts of fiddly changes to get it to stay at 1111...frustration!
Is there something i can do or is this normal? -
it seems weird that a Pro app that cost me so much £s wouldn't work in a simple recording/bounce down set up?
or has anyone else had this problem and fixed it?
If i wipe Logic and install again would i have to go from my Logic Express and then up to my Logic Pro upgrade/extension again?
Any pointers would be greatly appreciated.
Thanks in advance

Hey Fox,
Thanks for that info -well umm, yes i installed the correct drivers.
I use just the AU plugins or the basic logic ones on the channel strip
but even when i was going in dry there was still a delay.
I had experimented with the buffer size, as mentioned, but not gone down that low cus
last time i tried that i had other strange things happen!
But i will try again.
Sample rate was at zero, btw. Always says zero.
But today, when i just opened logic, the sample rate had changed. Strange. I need to understand this side of things so i'm gonna read up.
Also, if plugins are involved, i installed some novation bass station and some freeware TAL bass synth
stuff recently but don't have them up when i'm recording.
Maybe they sit there quietly and interfere just by their facial expressions or sumthing!!
I booted Mr MBP just now and i pulled out the USB and he's shining me a big ole red optical light
out of his output jack!!
In SysPrefs it has only optical digital as an output option.
In the last few days as i was playing around trying to correct the latency issue i noticed that the output options had changed to the UA25 and the 'digital optical' options - rather than the UA25 and 'line out'.
I'm off to go and read up on how to get my line out back, and try this buffer thing again.
Thanks again
Gravity

Similar Messages

Line input problem with Logic X, No issues Logic Pro

I use the line input on my 2011 Imac to record audio from my piano keyboard. When using LOGIC X there is no sound coming through the speakers, but with Logic Pro 9 I have no issues. I tested with new projects, ect but was unable to get to work.
In both Logic Pro and Logic X I have made an audio track and made sure input monitoring is on. I made sure volume was sufficient. I have tried to fix this to no avail and was thinking about bringing to apple store, but this appreasrs to be some sort of logic x bug (or I am missing something). Any help is appreciated as this is very frustrating.
Brian

I think you're missing something.
http://help.apple.com/logicpro/mac/10/#lgcpbb81aca5
You have to configure each program top to bottom, go to the above link and make sure all your settings are correct. (the won't necessarily match the pic)
Look at your Logic 9 settings Preferences/Audio and then set up Logic X the same way.

Random distortion and latency with logic pro and 2 presonus firepods

Hello,
I was wondering if any one else has had this trouble, about a month and a half ago I bought another Presonus Firepod interface and I also installed Tiger On my mac. Now I get random distortion and have to restart logic and turn the firepods off then turn them on again then restart logic, sometimes I have to do this a couple of times before the distortion goes away. I noticed a lot of times when I use midi (many notes at a time) I hear crakle too. I was wondering if anyone else has had this problem. please let me know if you have any pointers. I'm not sure if it is my computer, the software, or the interface.
Thank oyu for your time
Mike

I hate to be a cynic, but I've been having problems with my (bought in october)
Firebox and I would suggest talking with Presonus. I bought a new one which
exhibited the same issues and spent a month trying to figure out what I was
doing wrong. Well, it wasn't me, but the Firebox. It had a chip and a board replaced. Presonus was pretty lousy at accepting responsibility and slow
at a returning a box. If you went through a dealer see if you can exchange it
for a new one. I wish I had. I'm waiting for an exchange, btw, for this
fixed box because it leaks audio out bypassed outputs. Don't be afraid to insist that you get a working box if you deal with Presonus. The box is great, the support, for me, has been awful.
Good Luck!

Importing audio tracks issue (Logic Pro 8.0.2 - Snow Leopard 10.6.0)

This is a strange one that i've only just noticed since installing Snow Leopard:
In Logic when looking for audio tracks via the media browser, I select a file and drag and drop it into a project. The file plays back in the project as expected, but...
A copy of the file is then placed in the location where i've just dragged the file from???
For example:
I navigate to a track within an album in my iTunes folder (stored on an external drive) and drag the track into an open Logic project. Once imported there is a duplicate of the imported file placed within the album folder. I'm pretty sure this wasn't the behaviour before upgrading.
There are a few weird things happening with this:
If I import a .mp3 file, a .aif file is placed within the album.
If I import a .m4a file, a .ovw file is placed within the album.
Sometimes it shows the copy of the track in the browser and sometimes it doesn't. If I navigate to the album location in finder there is a copy of the file located within the album folder.
Anyone else experiencing this?
Bryan

Cheers Bee Bee, school boy error on my behalf!
I was chopping up a few tracks to put on the mrs phone as ringtones and hadn't actually saved the session which would explain why a copy would have been put in the original location seen as there was nowhere else for it to go.
Bryan

Bus latency issue

I am sure there is a simple solution to this ... I haven't found it on my searches yet.
In Logic 7.2 I am routing BFD auxiliaries to one bus and running some overall compression and eq. Now I have latency on the bus and it is lagging behind the rest of the tracks. What can I do to compensate and pull it back up to speed with the other tracks?

I am sorry no one has seen fit to help you with this problem however help is at hand please take time to read this very carefully. I believe this is your answer you seek, The reason I have gone into such depth is simple so that you will have a grounded understanding of how logic address the problem and also what plugs in Logic have Latency within them by default. Well here goes
Logic Pro 7.1: Full Plug-in Delay Compensation can cause late recordings and increased latency
In Logic Pro 7.1, if you set Plug-in Delay Compensation to All, any new tracks you record will be late and out of sync with previously recorded tracks. You may also experience increased latency when playing Audio Instruments live. Here are some concepts behind the issue and tips for resolving it.
About full delay compensation
One of the new features in Logic Pro 7.1 is full delay compensation across busses, aux channels, and outputs. This means you can place plug-ins that normally induce latency on busses, auxes, or outputs, and the audio routed through these plug-ins will be in sync with everything. Logic achieves this by calculating the amount of delay caused by plug-ins assigned to a bus, aux, or output, and delaying the streams sent to other busses, auxes, or outputs by an appropriate amount to line everything up. This ensures that all tracks will be synced to sample-accuracy.
Example scenario
To give you a better understanding of what's going on here, let's say you have a simple song with a few drum, bass, guitar, and vocal tracks. All the drum tracks are routed to a bus with several plug-ins inserted that together induce 500 ms of latency. The vocals are routed through another bus that has a set of plug-ins that induce 250 ms of latency, and the bass and guitar tracks are routed straight to the main outputs without going through any latency-creating plug-ins. If latency were not corrected, then the bass and guitar tracks would play 500 ms in front of the drums. The vocals would be 250 ms in front of the drums but 250 ms behind the guitar and bass.
With full delay compensation engaged, Logic Pro will delay the streams sent to the outputs for guitar and bass playback by 500 ms to line them up with the drums, and will also delay the bus the vocals are streamed to by 250 ms to line them up with the drums and guitars. The precise calculations are handled for each stream automatically. During playback and mixing, the delay created to compensate for plug-in latency is imperceptible, but it can cause problems if you do any tracking after turning on full plug-in delay compensation. These recordings will be late because of the delay that Logic imposes to compensate for latency. The degree of lateness will vary, depending on which plug-ins are in the signal chain.
Eliminating latency
There are several ways to deal with these latency issues. The best way is to simply avoid setting up any signal routing that involves using plug-ins that create latency on busses, auxes, or outputs until you are done tracking. Once you start mixing, go ahead and set up any routing you like, including setting Plug-in Delay Compensation to "All."
If you can't avoid recording tracks after setting up such a routing scheme, then bypass any plug-ins you have on busses, auxes, or outputs that create latency, and change your delay compensation setting from "All" to "Audio tracks and instruments" while you are recording. You can quickly bypass plug-ins by Option-clicking on their inserts in the Track Mixer. You can toggle the Plug-in Delay Compensation setting by choosing Logic Pro > Preferences > Audio > General, or by setting up a key command for "Plug-In Delay Compensation: All." This key command will toggle the delay compensation setting between "All" and "Audio tracks and instruments." When you finish recording, re-enable the plug-ins on the busses and toggle the delay compensation setting back to "All."
Note: Bypassing plug-ins on Outputs will not eliminate the latency that they create. To eliminate it, you must remove these plug-ins entirely from the Output's insert slots.
If you are recording audio, another strategy would be to choose Audio > Audio Hardware & Drivers, then disable Software Monitoring. You would then need to monitor your recording via an external hardware mixer, or third party software mixing application that may be provided with your audio interface. When Logic is not providing software monitoring of incoming audio, then it can correctly position audio recordings even when full delay compensation is enabled. It is important to note that this technique will not help with recording Audio Instruments.
For the same reasons as described above, you may get increased latency when playing Audio Instrument tracks live if the delay compensation is set to All. As with recording audio tracks, try to complete any Audio Instrument recording for a song before turning on the full delay compensation. If you find it necessary to add a new audio instrument recording after setting up a signal routing that involves latency-causing plug-ins on busses, auxes, or outputs, then follow the same advice stated above for adding recorded audio. You may also notice that the meters on busses, auxes, or outputs that have delay-compensated plug-ins will not be in sync with the tracks that are routed through them—however, the audio will be sample-accurate. Additionally, the Song Position Line's visible position will not be compensated. Unless you are using an exceptionally large set of delay-compensated plug-ins, this should not be particularly noticeable.
Another effect with delay compensation set to All is that MIDI tracks triggering external sound modules will be out of sync. This is because Logic has no direct control over the audio output of external devices. A possible solution for this would be to route the audio outputs from the external MIDI devices to inputs on your audio hardware and monitor them through Logic. This way, the audio streams from the MIDI devices can be compensated during playback. Using Logic's External instrument to route MIDI to your external devices is an ideal way to work in this situation.
Here is a list of Logic plug-ins that cause latency:
Adaptive Limiter
Limiter
Multipressor
Noise Gate
Silver Gate
Linear Phase EQ
Match EQ
EnVerb
Space Designer
Denoiser
Pitch Correction
Pitch Shifter II
Vocal Transformer
Some third-party Audio Unit plug-ins may also cause latency—refer to the user guide for the respective products to see about this. All plug-ins that run from DSP cards such as the PowerCore or UAD card have inherent latency. Logic Pro compensates for the latency of any of these third party plug-ins, but as with Logic's own plug-ins, avoid assigning those that exhibit latency to busses, auxes or outputs until you are finished with tracking.
You may also find that simply bypassing plug-ins that run from DSP cards will not be sufficient to correct the latency they induce. If you are using these plug-ins, there are a couple of ways to deal with this. One would be to remove the plug-in entirely while you are recording tracks, and then re-insert them when you're done recording. Be sure to save your settings for each of these as a preset first, so that you can recover the appropriate settings when you re-insert them. Taking this idea a bit further, you could save the entire channel strip setting for each bus, aux or output that uses plug-ins that cause latency and then easily reassign everything for each channel in one go.
I hope you will get something useful from this good luck

Missing Plug-ins in Logic Pro x

My logic program says that i am missing plug-ins and its not letting me create any new tracks. any help?

Hey Lalo230!
Try using the information in the following article to help you troubleshoot this Logic issue:
Logic Pro X: Troubleshooting basics
http://support.apple.com/kb/HT5859
Thanks for being a part of the Apple Support Communities!
Regards,
Braden

Logic Pro 8 Issues, Error Messages

Hi all.
I've been having a variety of problems with my home recording studio, which i have neglected to post about until now- from what i've read it seems no-one knows how to fix them. I'm turning to the MacTalk community to resolve my woes... First things first, here's the gear:
 MacBook Pro (mid-2008), 2.4GHz C2D, 4GB RAM, OS X 10.5.6.
 I use Logic Pro 8 primarily, and this is where all the errors are popping up. I record to WAV, 24-bit, 48KHz (for the sake of diagnosing errors, I have tried 16-bit, 44.1KHz and noticed no difference).
 All audio-related work is handled on a WD MyStudio External FW800 HDD.
 My audio interfaces are an Apogee Duet, and an M-Audio ProFire 2626 (both running latest drivers).
Now, there are 3 (possibly related) problems i'm having with my setup.
✖ Problem #1
I receive an error message indicating a 'System Overload' at random times during playback and occasionally recording.
It halts the audio, and I need to click play or record again. Sometimes it happens again and again, other times it’s just a one-off. This problem can occur with either the Duet or ProFire interface. Apparently the number of tracks I’m recording or playing is irrelevant, as it happens under many different circumstances.
✖ Problem # 2
I receive an error message telling me that the “Drive is too slow, error -10004”, and this happens only in recording (I think; oh and it looks like the previous dialogue box). As mentioned above, I use a FW800 external HDD, so it shouldn’t be a hardware requirements issue – it SHOULD be fine as far as I know. It was particularly bad when I was recording 5 channels of audio into the ProFire 2626. Like the previous issue, it halts the recording, and sometimes recurs. It may not happen with the Duet.
I may be imagining things, but I think it records fine indefinitely when I’m recording near-silence, i.e. not playing my drums. It almost seems as though the problem is triggered when I get particularly loud. Perhaps it’s clipping, I’ll have to check. Still, it shouldn’t cause an error that halts recording should it?
✖ Problem #3
This one only occurs with the ProFire. I get minor crackles and little bits of distortion and ugly tearing sounds in some channels occasionally. They each only last a fraction of a second, and usually aren’t particularly loud, but they spoil takes. Can occur during silent passages OR loud parts.
For the record, I typically record to WAV, 24-bit, 48KHz, with a 128 or 256 sample buffer, Medium Process Buffer Range, and Software Monitoring enabled. However, I have tried up to 1024 sample buffer, Large Process Buffer Range, 16-bit, 44.1KHz WAV, and turned off Software Monitoring – none of this made a difference.
So, if anyone thinks they can help me out here, please do so! I’ll greatly appreciate any input ☺
Cheers,
Chris

1. http://support.apple.com/kb/TA24535?viewlocale=en_USy
This problem points to a buffer that is set too low. Make it one step bigger, but leave the I/O safety buffer OFF.
also: you can disable the warning message.
2.
CAN also be buffer-related, but it may be the disk. Is it a 5400 or 7200 RPM disk?
It may also be that memory is too full. I would recommend installing Menumeters (freeware) http://www.pure-mac.com/diag.html#menumeters
You can monitor CPU-use, disk activity, memory use, paging activity and network activity with it.
Another thing to consider is to Freeze all Software Instrument tracks before recording. Also freeze heavily 'insert-pluginned' audio tracks. This may free up a lot of CPU power.
3. This problem might benefit from the above tips as well, but I think you can win the most by NOT using software monitoring when recording (for all three issues); it brings extra latency and puts much more strain on the CPU. Through which plugs do you monitor? And why?
I'ld recommend using the direct monitoring capabilities of both your interfaces, and avoid Software Monitoring when recording. Also being aware of what is going on (by using both Menumeters AND Logics' own CPU-meters) can be crucial - especially Paging (when active RAM is written to or read from disk) can disturb Logic, as well as background OS X applications that kick in during a session.
I also recommend turning off Journaling before a recording session. To do that, open *Disk Utility*, select the recording disk from its' list, hold down the ⌥ key and choose the menu *File>Disable Journaling*.
To turn it back on after recording, same actions, only now the menu item will say *Enable Journaling*.
regards, Erik.

Latency Between Outputs After Project Conversion From Logic Pro 9

hiya!
i am experiencing a bizarre kind of latency – between outputs. for example, audio assigned to stereo outs 13-14 will leave my system 120 or so ticks after audio assigned to mono outputs 3 or 4. sometimes mono outputs are out of sync with one another too. there's no apparent rhyme or reason, and the latency itself seems to shift – even with plugins turned off and removed from the channel strips. if i have an aux that's outputting to channels 7-8 and do a send to an aux that outs to 13-14, this audio should be perfectly aligned, but it just isn't.
i experience this problem in sessions converted from logic 9 to logic x, though sometimes it seems to happen within sessions started in logic x. i can't for the life of me figure out why it's happening, but do believe there's some sort of error being introduced in the conversion. i can't find anything anywhere on the internet about it.
one temp fix i found was to insert an I/O plugin into the problematic aux, turn it on with an out assigned, then turn it off. sometimes that's worked, and sometimes it hasn't. i've been able to use delay compensation on certain tracks, but it's not an exact science, and sometimes the compensations themselves need to change in order for the tracks to sound aligned. it's beyond aggravating. in some situations, i've had to re-record entire sessions. not tight!
to be clear, this is not about monitoring latency, or having to slide tracks into alignment after recording, or the waveforms on the screen not matching up with what i'm hearing. this is not about plug-in latency. the situation i'm describing happens when plugins are entirely removed: audio that is supposed to be leaving logic at the same exact time via different outputs is somehow not aligned.
my signal chain:
logic pro x.0.7
mac pro quad core (trash can) into -->
apogee symphony 16x16 -->
neve 5059 16x2x2 -->
api 2500 -->
back into the symphony
i've been assured by both apogee and neve and sweetwater that this is not their issue--it's logic pro x. i'm inclined to agree, since it seems to be happening before the audio leaves logic.
please help! many thanks for anything!

godmodeinternet wrote:
thanks for your reply!
to answer some of your answers:
-i have all my channels go through auxes, in all projects, but i did attempt to route audio straight off the channels and encountered the same situation i described above.
-plug-in latency is likely set to ALL at all times, since i often track while in the 'mixing stage'. this is how i've always done everything.
ugh. the worst!
do you think there's anything in environment i might be able to swap around that might have gotten screwed up in the conversion?
thanks again.
I don't think it's an Environment issue, however, quite a few people have reported some corruption when importing Logic 9 projects, it usually takes the form of random Inspector Settings for Delay/Velocity and Preferences/Audio - Recording Delay being set to something other than 0 <zero>. This doesn't sound like your problem. Also sounds like your Plugin Latency setting (ALL) isn't the problem.. although if you're recording while mixing it should be set to Audio & Software instruments.
Have you used your hardware system successfully on an earlier version of OSX and Logic 9? If so then the answer is apparent, especially so if you notice it on projects started in Logic-X (current system) although it my take a certain level of project complexity before it shows up.

Logic Pro Metering Issues

currently working on a song, snare drum channel meter infrequently will not register a snare hit eventhough audio is playing at that moment - this does not happen at the same point in the song each time....kinda weird, hope you may have some insight.
I've copied the audio region in question to another track, and I still get this same behavior
The source of the track was a compilation from a drum comp which was then flattened and merged to become one new track
Running MacBook pro i5 snow leopard
Thanks for any input!

Alrighty,
Erik, your method work, and I could record perfectly fine when I disabled software monitoring. I started a fresh project, and everything worked fine, and latency was workable with. However, I closed and open the project 30 mins later and back to sqaure one. I disabled software monitoring, and it works fine again.
Do you think my "returning to work" issue is more of Logic Pro been all derpy *****, or its my interface?

Logic Pro 9 issues

I recently had to re-install my LP 9, after having to install a new hard drive. It worked without having to use the serial number. (Because I lost the box). Anyway, today it asked for the serial number. Doesn't Apple usually keep info like that on file?

Alrighty,
Erik, your method work, and I could record perfectly fine when I disabled software monitoring. I started a fresh project, and everything worked fine, and latency was workable with. However, I closed and open the project 30 mins later and back to sqaure one. I disabled software monitoring, and it works fine again.
Do you think my "returning to work" issue is more of Logic Pro been all derpy *****, or its my interface?

Performance issues with Logic Pro 9

Hi,
I'm experiencing quite big performance issues with Logic Pro 9:
bad midi timing and sync, user interface is kinda slowing and less reactive, ...
Mac Pro 2x2.26 Ghz Quad, 4Gb ram, early 2009, shipped with 10.5.6 now upgraded to 10.5.8
Should I upgrade to 10.6.2?
Thanx

Hi,
I'm using the same machine ...
I never get any performance issues
I bought my mac in March 2009 and I was ben ready to work in less that 3 days without issue...
so more details about your setup are required to answare!
4GB ram???
I suggest to check your ram!!!
Ram must be compatible with Xeon Nehalem Try specification!
if you add 1GB of ram from nor clear manufactor.. i suggest to disconnect the addition 1GB RAM
G

Video Latency Issue On The Mac Book Pro 2.4 With Leopard 10.5.5

Gear: Macbook Pro (early 2008 model) - 2.4gigs cpu 2gigs ram - all the latest updates... no other applications running during the test
Hi folks. Currently I am having a latency issue when trying to record directly into iMovie using the built-in microphone and iSight camera. Basically, the video seems 5 - 7 frames late to the audio. I found that a good way to demonstrate this issue was simply doing a few handclaps as a test.
This is a quick handclap test displaying some video latency during recording with the iSight camera in iMovie 08.
- Just download this link — and import it into iMovie 08 - Here is a link to a zip file that you can import into iMovie 08 - It's 2.5meg - .m4v export - Also it was recorded as standard format and audio midi setup app: audio was set to 44.1:
http://www.brainbeast.com/37/clap-1-large.zip
- Play from beginning. As soon as you hear a clap sound — pause with the space bar - then back up before the clap with the left arrows
- Then click the right arrow several times until you hear the beginning of the clap sound ( This is the audio: start frame)
- Now — you will notice the video still has an open hand. At this point click the right arrow, counting as you go several times until you see the hand close. This is the amount of frames that the video is late to the audio. For me it seems to be an average of about 5-7 frames late.
Unfortunately iMovie 06 nor QuickTime will not scrub audio as you go frame by frame with the arrow keys so you cannot test it there. If you have some other application such as final cut Pro, you could test it with that.
! IF YOU WOULD LIKE TO PERFORM THE TEST YOURSELF:
- Just record a new movie in iMovie 08 - using the built-in mic and i-Sight camera — and see if it is also slightly out of sync
Note: to be as fair as possible — I did a slow handclap ( in order to not challenge the frame rates) - also, in order to get the maximum volume I used an open palm ( clap on the palms with your fingers spread out as you can see I did.)
Please let me know if this latency appears to be the same for you as it does for me.
Q: Is it just my machine or does it happen to you too?
Q: Does anyone know a way around this latency issue?
Q: Does anyone know if Apple is aware of this latency issue?

I am experiencing the same incredibly frustrating problem as well. When I record directly into iMovie
'08, the video lags the audio by a fraction of a second.
I have tried shutting down all other applications and having only iMovie up. Same problem.
I tried recording the video into QuickTime instead of iMovie and experienced the same problem. (Which makes me think it is perhaps a hardware or operating system issue.)
I tried the technique suggested here and on other sites of "double-dragging" the clip from the Events pane into a project (one normal drag and one Shift+Cmd drag) so that I had the audio and video as two separate tracks. After muting the audio on the video track, I then attempted to slide the audio over to sync it with the video, but even down at the 1/2 second zoom setting I didn't seem to have enough granularity to move the audio so that it was exactly in sync with the video. I was wishing I could use the arrow keys or something like that to move the audio just one frame at a time.
All I want to do is record a video directly into iMovie '08 - this would seem to be something trivial to do!

"Mouse Over" issues in Logic Pro - Mountain Lion

Hi,
Since I upgraded to Mountain Lion, I spotted an issue with Logic Pro (Logic 9).
In the Arrange window, when pointing the mouse at the end of a region, the pointer icon doesn't change to the looping (upper right corner of the region) or resize (lower right corner) icon.
As a result, those functionalities (looping and resizing regions) are gone.
Anyone having the same issue?
Is there a way to solve this or do we need to wait for a Logic Pro update to get these back?
Thanks in advance,
A nice day everyone,
Vince

Vlvl wrote:
As it's the only problem I have noticed since the upgrade, and as I mentioned in my last post, looking like a minor problem to me, I will keep Mountain Lion.
But anyway, thanks for the advice, Ivan.
Vince
No problem, as a professional musician using Logic I learned that lesson the hard way first time around. Hard as it was to not have the toys I soon learned that stability ruled the day....

Logic Pro X and Yosemite issues

It seems I have some very basic issues with Logic Pro X 10.0.7 after upgrading to Yosemite OS on my MacBook Air:
1. Zooming the main window by swiping two fingers apart or together on the mouse pad does not work anymore.
2. Adjusting the length of audio regions in the main window does not work anymore. It works as usual on midi tracks, but when I hover the end of an audio region the brackets just do not appear. I have now used automation to silence the bit that I wanted to shorten, but that is more of a hassle.
I have tried restarting Logic Pro X, restarting the MacBook and looked for any settings that may have been changed, but to no avail.
Do these issues sound familiar to anyone? Any thought on how to fix?

1) Zooming
the zooming with the swipe gesture was always problematic, but it is now only happening in the Audio FIles Editor and to some extend in the Score Editor. All the other windows work fine on my machine.
2) Resize Tool
Works fine without a problem in the Main Window and the Editor windows. Of course, you can resize in the Audio FIles Editor.
Hope that helps
Edgar Rothermich
http://DingDingMusic.com/Manuals/
'I may receive some form of compensation, financial or otherwise, from my recommendation or link.'

Logic Pro 9.1.1 AU third-party plug-ins ongoing issue for many

Where is the Logic development team on this? Nearly all third-party AU plug-ins produce random pops and clicks at the beginning of playback and on occasion randomly during playback but before audio regions in tracks with these plug-ins installed. These pops and clicks are even visible in the track's meter. http://www.gearslutz.com/board/music-computers/482381-logic-3rd-party-plugs-pop- click-nightmare-how-does-rest-world-do.html How many people need to complain? Is Logic Pro considered production software?

I can't imagine a more textbook and apple-friendly environment than what I have. 32-bit is not the problem. I don't believe logic runs at 64 until you're on os 10.6 and I'm still on 10.5.8. My entire rig is what you'd see in an apple store logic demo. I've tried nearly everything:
1) All standard optimization tips including but not limited to no date/time updates, no airport/wi-fi, no bluetooth
2) I have a ultra high-quality external fw drive by G-drive
3) Standard issue ensemble with updated firmware
4) Moving AU component files from system library to user library
If you look at the number of people commenting on the GS thread as well as other forums – the problem is common and needs to be fixed. I'm not the only logic user plagued by this issue:
http://www.logicprohelp.com/viewtopic.php?t=43306
http://www.logicprohelp.com/viewtopic.php?t=50030
I really believe it has something to do with how many third-party plug-ins handle AU's reset or initialize callbacks; somewhere in between. This bug is clearly affecting many users and I'm coming close to starting a petition and devoting some serious time to making a big dorky stink about it on youtube.
Either the AU spec needs to be updated to clarify some tricks (or hacks) specific to Logic's on-demand DSP usage or the logic team needs to publish a notice to all "Logic" AU developers. Optionally, if Logic had a preference to turn OFF on-demand AU DSP (so that plug-ins are always-on like in every other DAW or...ugh...outboard gear). Logic's on-demand AU DSP handling is outdated considering the processing power available in ANY apple computer made within the last 3 years. My CPU meter in Logic barely even lights up. On-demand DSP is overkill and antiquated and the least Logic can do is provide production or mission-critical users the ability to opt-out if they have the CPU power to do so.
Having said all that; I hope I'm wrong about something and can come back here to eat my words and feel very embarrassed about my rant. I'm going to keep digging for solutions – hopefully, I'll find out the secret to whatever it is the few of you are doing to keep your third-party AU plugs quiet before an audio region starts.
Also; Scott at Stillwell Audio has graciously begun trying to track down this very issue and is one of the few DSPers who has taken interest in helping Logic folk.

Latency issue Logic pro 9.1.3.

Similar Messages

Maybe you are looking for