Logic 7.1.1 Timing ...poltergeist??

Hi everyone. I was checking the timing on my system today (dual 1ghz G4 + rme hdsp 9652 + presonus firestation as A/D) and not only is quite out of time (by the way I use an MT4)but it's shifted early!! I program a click track that triggers a rim on a proteus 2000. It's outputs go straight in to the RME's spdif input (and I monitor via the dsp mixer on the card). When I record this input, the audio is actually BEFORE the midi!! I've checked ALL the posible delay settings in logic and the're all set to 0. I've tried turning off track delay compensation, but it doesn´t seem to affect in this case. To get the audio sort of close to the midi, i need to delay all midi outputs (general preferences > midi> sync) round 2ms. I've also tested different ports on the mt4 ...and with different timings aswell!! Do I need a new midi interface? Am I freaking out? Thanks everyone.

I'm having the exact same problem. It's not just MIDI, it's all audio coming into Logic. The audio appears and sounds early, even with no plugins at all running. I have posted a separate thread, didn't see your post originally. But this is really a BIG problem!

Similar Messages

Which is the best MIDI interface to use with Logic 7 ?

Hi folks :o)
Firstly, thanks all for any advice you can give. I'm a pro user, but right in the middle of a major upgrade (G4/OS9/CubaseVST32 >> G5/OSX/CubaseSX3/Logic7) & feel a huge learning curve coming on!
The situation is this:
I have a Steinberg Midex 8 midi interface, plus a MOTU MTPav in the cupboard. The Midex took place of the MTPav because it had much better midi timing under OS9 with Cubase... The Midex8 drivers for OSX, however, are still beta & a pile of rubbish. (It keeps losing communication with the G5.) I'm fed up with how bad Steinberg have been sorting (not!) these problems out (not to mention the fact that Cubase SX3 can't recognise my 'studio' created in Audio Midi Setup either.. arghh!), so I'm considering jumping ship & going entirely to Logic in one hit, plus whichever is the best midi-interface for this software & OSX.
As food for thought, I'm currently thinking of tracking down a 'Unitor 8', having made the (perhaps wrong) assumption that it'd work 'best' with Logic seeing as it was made by Emagic. BUT, despite a lengthy search in Logic 7's manuals & this forum, I can't find any mention of Emagic's 'Active Midi Transmission' protocol & whether or not Logic 7 supports it; AMT is the only reason I'd buy the Unitor. (I've got all the other bases covered with the MTPav.) I'm also concerned about the long-term support issues regarding drivers for the Unitor 8 & OSX; ****, I'm having enough problems with Steinberg & their Midex 8 (which is still a current product in theory!) without throwing Emagic & a midi interface that's no longer manufactured into the pot...
So..... What do you folks feel is the best midi interface to use with Logic 7 as regards tight midi timing & system reliability? Can anyone out there with a big midi setup categorically say "I've got one (or more) of these MIDI interfaces, it works beautifully under OSX & Logic 7, & the MIDI timing is rock-solid, even when put under heavy midi 'duress' " ??
Many thanks again in advance for any feedback!
Your new Logic Pro virgin ;o)
Jason

Thanks for your reply folks. It's good to hear a number of you are having good results with your MTPav - I guess I'll pull mine out of the cupboard in that case!
As an aside, it's been interesting to note how difficult it's been to get a clear answer from companies (be it shops or Apple) as to whether or not Logic 7 supports 'Active Midi Transmission' on the old Unitor 8 MkII..... (The reference manual has one mention of it in the index, yet points to a page that doesn't say anything about AMT at all!)
If anyone here DOES have a clear answer about AMT with Logic 7, I'd be very interested to hear about it... thanks.
Kind regards,
JC

Cubase 4 or Logic 7??

Hi guys,
ok so i know this question has been asked a lot.
but i just need a simple answer, which is better...?
Cubase 4 or Logic 7??
Getting a 20" iMac soon, and need some great software to compliment it so i can set up a little recording studio at my house ASAP.
Some help will be greatly appreciated,
Thanks a lot!

I recently started using Logic Pro 7 over the summer and my results have been good, but I'm having a very hard time trying to get set up like I normally worked in Cubase SX3. For one, there's no satisfactory sampler for Logic/Universal Binary. EXS24 ranks worst among all the samplers I've seen when it comes to loading and dealing with my own samples. It's fine for just playing it's own instrument format. So I'm down a good sampler. None of my usual VST plugins work either but this isn't too bad since Logic Pro provides a wealth of instruments in the box. Other things I miss are the extreme audio manipulating abilities of SX3, simplicity of setting up multi-out instruments and playing them, simplicity with rewire, simplicity in general, and continuous playback without dropouts. Still, I'm getting good results with Logic. Midi performance timing seems to be better and mapping controls on my midi keyboard is grossly easier in Logic. Logic's interface is beautiful and the workflow is excellent with the exception of problems caused by the things I mentioned above. I can't wait to see what Logic Pro 8 will bring. I hope to see the audio side of it get up to the level of at least where Cubase SX3 is right now. Audio handling is currently surprisingly lacking in Logic Pro.

Par failing on EDK 11.4

Dear forum members, I've designed a system on custom board using the spartan-6 lx45t device on EDK 11.4 using the base system builder. Following is the device utilization summary after map:
   Number of LOCed IOBs                  97 out of 97    100%
   Number of SLICEXs                      4521 out of 6822   66%
   Number of Slice Registers             15138 out of 54576 27%
   Number used as Flip Flops          15136
   Number of Slice LUTS                  25539 out of 27288 93%
   Number of Slice LUT-Flip Flop pairs   25636 out of 27288 93% However, after PAR the following error is thrown and bit file is not generated.***************************************************************************************************************************************************************
ERROR:Xflow - Program par returned error code 30. Aborting flow execution...
make:
*** [__xps/system_routed] Error 1  I also get the following warnings during PAR. *************************************************************************************************************************************************************** WARNING:Par:288 - The signal mb_plb/mb_plb/GEN_SHARED.I_PLB_ARBITER_LOGIC/I_ARB_ENCODER/prioencdrOutput_pri<1> has no load. PAR will not
   attempt to route this signal.
Starting Router
Wirelength Stats for nets on all pins. NumPins: 130211
Phase 1 : 136053 unrouted;      REAL time: 2 mins 3 secs
Phase 2 : 125020 unrouted;      REAL time: 2 mins 21 secs
Phase 3 : 86813 unrouted;      REAL time: 7 mins 13 secs
Phase 4 : 98510 unrouted; (Setup:5539693, Hold:6858, Component Switching Limit:0)     REAL time: 19 mins 11 secs ***************************************************************************************************************************************************************
WARNING:Route:441 - The router has detected a very high timing score (5469167) for this design. It is extremely unlikely the router will be
   able to meet your timing requirements. To prevent excessive run time the router will change strategy. The router will now work to
   completely route this design but not to improve timing. This behavior will allow you to use the Static Timing Report and FPGA Editor to
   isolate the paths with timing problems. The cause of this behavior is either overly difficult constraints, or issues with the
   implementation or synthesis of logic in the critical timing path. If you would prefer the router continue trying to meet timing and you
   are willing to accept a long run time set the option "-xe c" to override the present behavior.
Intermediate status: 43159 unrouted;       REAL time: 49 mins 19 secs
Intermediate status: 29897 unrouted;       REAL time: 1 hrs 19 mins 31 secs
Updating file: system.ncd with current partially routed design.***************************************************************************************************************************************************************
WARNING:Route:543 - Because this design is experiencing congestion, we recommend you run SmartXplorer with the "Use built-in SmartXplorer
   strategies for Congestion Reduction" radio button enabled in Project Navigator. For command line users, please run SmartXplorer with the
   -cr switch. This will run algorithms designed to avoid logic congestion. For more information on how to run SmartXplorer, please see the
   ISE Help (Project Navigator Users) or the Command Line Tools Users Guide (Command Line Users).
Phase 5 : 27042 unrouted; (Setup:21963466, Hold:6858, Component Switching Limit:0)     REAL time: 1 hrs 30 mins 19 secs
Total REAL time to Router completion: 1 hrs 30 mins 19 secs
Total CPU time to Router completion: 1 hrs 29 mins 47 secs
*************************************************************************************************************************************************************** WARNING:Par:468 - Your design did not meet timing. The following are some suggestions to assist you to meet timing in your design.
   Review the timing report using Timing Analyzer (In ISE select "Post-Place &
   Route Static Timing Report"). Go to the failing constraint(s) and evaluate the failing paths for each constraint.
   Try the Design Goal and Strategies for Timing Performance(In ISE select Project -> Design Goals & Strategies) to ensure the best options
   are set in the tools for timing closure.
   Use the Xilinx "SmartXplorer" script to try special combinations of
   options known to produce very good results.
   Visit the Xilinx technical support web at http://support.xilinx.com and go to
   either "Troubleshoot->Tech Tips->Timing & Constraints" or "
   TechXclusives->Timing Closure" for tips and suggestions for meeting timing
   in your design.
Number of Timing Constraints that were not applied: 8***************************************************************************************************************************************************************
WARNING:Par:100 - Design is not completely routed.
WARNING:Par:283 - There are 1 loadless signals in this design. This design will cause Bitgen to issue DRC warnings.***************************************************************************************************************************************************************
Total REAL time to PAR completion: 1 hrs 31 mins 3 secs
Total CPU time to PAR completion: 1 hrs 30 mins 24 secs
Peak Memory Usage: 553 MB
Placer: Placement generated during map.
Routing: Completed - errors found.
Timing: Completed - 5587 errors found.
Number of error messages: 0
Number of warning messages: 8
Number of info messages: 1
Writing design to file system.ncd
PAR done!
Few days back the same warnings were thrown, but the bit file got generated, and system behaved as expected. But, since then the RTL of customIP core has changed, but by a very small amount. Please let me know, if someone faced the same problem and is there any workaround for it. Thanks in advance,Sumanth.

I am using the same part and get the same error. I do not believe my design is unbalanced or too highly mapped. It seems very possible that this may be a Spartan-6 LX45 issue, especially considering there are no other forum post about this and any other parts. The fact that both of us have the same problem with the same part and nobody else seems to is suspicious.   Device Utilization Summary:
   Number of BSCANs                          2 out of 4      50%
   Number of BUFGs                          10 out of 16     62%
   Number of BUFIO2s                         3 out of 32      9%
   Number of BUFIO2FBs                       2 out of 32      6%
   Number of BUFPLLs                         2 out of 8      25%
   Number of BUFPLL_MCBs                     1 out of 4      25%
   Number of DCMs                            1 out of 8      12%
   Number of DSP48A1s                       18 out of 58     31%
   Number of ILOGIC2s                        5 out of 376     1%
   Number of External IOBs                  78 out of 218    35%
      Number of LOCed IOBs                  78 out of 78    100%
   Number of External IOBMs                 11 out of 109    10%
      Number of LOCed IOBMs                 11 out of 11    100%
   Number of External IOBSs                 11 out of 109    10%
      Number of LOCed IOBSs                 11 out of 11    100%
   Number of IODELAY2s                       8 out of 376     2%
   Number of IODRP2_MCBs                    22 out of 376     5%
   Number of ISERDES2s                       8 out of 376     2%
   Number of MCBs                            1 out of 2      50%
   Number of OLOGIC2s                       12 out of 376     3%
   Number of OSERDES2s                      50 out of 376    13%
   Number of PLL_ADVs                        3 out of 4      75%
   Number of RAMB16BWERs                    52 out of 116    44%
   Number of RAMB8BWERs                      5 out of 232     2%
   Number of SLICEXs                      4064 out of 6822   59%
      Number of LOCed SLICEXs                1 out of 4064    1%
   Number of Slice Registers             11875 out of 54576 21%
      Number used as Flip Flops          11863
      Number used as Latches                 5
      Number used as LatchThrus              7
   Number of Slice LUTS                  14334 out of 27288 52%
   Number of Slice LUT-Flip Flop pairs   14792 out of 27288 54%
Overall effort level (-ol):   High
Router effort level (-rl):    High     ...  ERROR:Xflow - Program par returned error code 30. Aborting flow execution...
make: *** [__xps/system_routed] Error 1 Message Edited by thirdeye on 03-24-2010 09:28 AM

FIR compiler 5.0 with DCM clock

Hi all,
I have a timing issue that usually goes away based on SmartXplorer cost table but I am curious as to why it even exists in the first place. I basically have a differential 250MHz clock from an ADC that I deskew using a DCM. The CLK0_OUT is then used to clock multiple things in my design, including a low-pass filter. I am confused as to why the reset logic is causing a timing issue to the low-pass filter.
Here is the error in my timing report:
Paths for end point peripherals_i/generate_LPF.LPF_i/LPF_0/blk00000003/blk0000003e (SLICE_X99Y133.CIN), 11 paths
Slack (setup path): -0.679ns (requirement - (data path - clock path skew + uncertainty))
Source: ADC_V8_i/ADC_V8_DCM_i/FDS_INST (FF)
Destination: peripherals_i/generate_LPF.LPF_i/LPF_0/blk00000003/blk0000003e (FF)
Requirement: 4.000ns
Data Path Delay: 2.386ns (Levels of Logic = 3)
Clock Path Skew: -2.138ns (0.523 - 2.661)
Source Clock: ADC_V8_i/ADC_V8_DCM_i/CLKIN_IBUFGDS rising at 0.000ns
Destination Clock: ADC_clk rising at 4.000ns
Clock Uncertainty: 0.155ns
Clock Uncertainty: 0.155ns ((TSJ^2 + TIJ^2)^1/2 + DJ) / 2 + PE
Total System Jitter (TSJ): 0.070ns
Total Input Jitter (TIJ): 0.000ns
Discrete Jitter (DJ): 0.120ns
Phase Error (PE): 0.060ns
Maximum Data Path: ADC_V8_i/ADC_V8_DCM_i/FDS_INST to peripherals_i/generate_LPF.LPF_i/LPF_0/blk00000003/blk0000003e
Location Delay type Delay(ns) Physical Resource
Logical Resource(s)
SLICE_X87Y132.AQ Tcko 0.450 ADC_V8_i/ADC_V8_DCM_i/FDS_Q_OUT
ADC_V8_i/ADC_V8_DCM_i/FDS_INST
SLICE_X93Y132.B6 net (fanout=2) 0.450 ADC_V8_i/ADC_V8_DCM_i/FDS_Q_OUT
SLICE_X93Y132.B Tilo 0.094 peripherals_i/generate_LPF.LPF_i/LPF_180/blk00000003/sig00000052
][11835_3592_INV_0
SLICE_X99Y132.A5 net (fanout=18) 0.755 ][11835_3592
SLICE_X99Y132.COUT Topcya 0.509 peripherals_i/generate_LPF.LPF_i/LPF_0/blk00000003/sig00000056
peripherals_i/generate_LPF.LPF_i/LPF_0/blk00000003/blk000004ae
peripherals_i/generate_LPF.LPF_i/LPF_0/blk00000003/blk0000003a
SLICE_X99Y133.CIN net (fanout=1) 0.000 peripherals_i/generate_LPF.LPF_i/LPF_0/blk00000003/sig00000088
SLICE_X99Y133.CLK Tcinck 0.128 peripherals_i/generate_LPF.LPF_i/LPF_0/blk00000003/sig00000047
peripherals_i/generate_LPF.LPF_i/LPF_0/blk00000003/blk00000037
peripherals_i/generate_LPF.LPF_i/LPF_0/blk00000003/blk0000003e
Total 2.386ns (1.181ns logic, 1.205ns route)
(49.5% logic, 50.5% route)

I actually have the timing report from a 0 timing score cost table on my local machine. Is this helpful?
Slack: 1.778ns (period - min period limit)
Period: 4.000ns
Min period limit: 2.222ns (450.045MHz) (Tdspper_MULP)
Physical resource: peripherals_i/generate_LPF.LPF_i/LPF_0/blk00000003/blk000000d0/CLK
Logical resource: peripherals_i/generate_LPF.LPF_i/LPF_0/blk00000003/blk000000d0/CLK
Location pin: DSP48_X0Y43.CLK
Clock network: ADC_clk

Holy mother of... PDC

ok i just cant get my head round this pdc [plugin delay compensation] thing.
as a test i loaded up an exs24 instrument [mono] with a 4 bar tambourine sample. bounced in real time to audio. duplicated to another track with a gain plugin on and when i hit the phase reverse button it doesn't cancel out? this is with pdc set to audio tracks and instruments..? [logic 7.2.2 & 7.2.3]
can anyone help me get the basic understanding of this down? i mean the manual didn't make any sense to me... i need a real idiots explanation of what this is doing and how to test it is actually doing it.
thanks for your time,
mark

sorry, i couldn't get back earlier: i was delayed with no compensation.
"does the sample buffer delay affect it just because it adds even more delay to the audio playing through logic?" no, they are separate issues.
"does the pdc affect virtual instruments or just plugins on virtual instrument tracks?" just the plug ins. however, with some sample libs and romplers there is dead air at the start of some of the individual samples. this can make it feel sloppy/latent. i generally won't buy any products that can't be used in the exs24 because of this. at least i can edit the individual start times of every sample clip within a given patch this way.
i have just completed an orchestral project where a great deal of re-anchoring was done. it works, and for once i've actually got the orchestra to "rock" properly.
i think where i have been going wrong is there is an adaptive limiter on the main outputs in my autoload [bypassed... but i found out that doesn't help]. i am using h/w monitoring [motu cuemix] and pdc is always left on 'audio tracks and instruments' [i never touch it as i'm afraid it will mess with the audio so bad that i can't correct it] but i think where i have been playing along to the delayed track through the limiter playing it back sounds out of time? does this make any sense? god i am so confused...!
you and me, both!! yes the ad limiter will scr*w up your timing - bypassed or not.
to reduce/minimize latency(using software monitoring):
use the lowest buffer setting that works.
have no plugs being used on said trk or the output bus.
use a separate midi i/o box to the one in the motu, and give it a dedicated input - usb will do, motu make some good ones, although i feel emagic's unitor/amt8 were the best for logic.
i have a unitor and i suspect it's the reason i can get away with high buffer settings on my audio i/o and still play well.
most of the time, after i've play in the part, and then rendered it to audio (sort of a must on ol'grannie) still have to shift the resulting file a little to get it to sit. generally the files anchor point is off, but i do a lot of this on every project anyway - part of my routine editing in logic.
i hate sloppy timing as much as the next guy.

Compiler switches

I am compiling my design for the NI PXIe5641R and saw the following message:
Phase 6: 22211 unrouted; (7335208)      REAL time: 4 mins 13 secs
   the router will be able to meet your timing requirements. To prevent excessive run time the router will change
   strategy. The router will now work to completely route this design but not to improve timing. This behavior will
   allow you to use the Static Timing Report and FPGA Editor to isolate the paths with timing problems. The cause of
   this behavior is either overly difficult constraints, or issues with the implementation or synthesis of logic in the
   critical timing path. If you would prefer the router continue trying to meet timing and you are willing to accept a
   long run time set the option "-xe c" to override the present behavior.
My question is where do I go to set the "-xe c" option for the compiler?
Thanks,
-Chuck

Hi Chuck,
You can access the Xilinx options by right clicking on your FPGA target and selecting properties. I would suggest using the timing performance design strategy.
JaceD
Signal Sources Product Support Engineer
National Instruments

Value Signalling Event Case

Hi Guys,
I am trying to trigger an event using "Value Signalling" and i hit a little bit of snag.
I am reading logic inputs continuously and i wanted to trigger an event if there is a change on logic signals.
What i did is i read the logic signals initially so to get the default state and re-read again the logic signals inside the timed loop in the event case waiting for the signals to change.
However, the event keep triggering even there is no change in signal.
Any advice?
Regards
Ray
Solved!
Go to Solution.
Attachments:
untitled.PNG ‏85 KB

Of course you did not show any actual code (just an image) so we can only guess the overall program architecture and what's in the other cases and events.
Still, you might be over-thinking all this. Since the loop is already spinning it seems overkill to trigger things using signaling events. All you probably need is a small case structure that executes additional code whenever things change. Events are primarily used to handle user interaction from the front panel. You just need to branch depending on the "changed/not_changed" case, which is trivial.
LabVIEW Champion . Do more with less code and in less time .

Improving timing and solving tempo issues in Logic

Hello, I was reading something about the beat mapping in user manual and also I was trying to improve timing of my drums recording but with no result. Is beat mapping the right tool for doing this and if so, what are the right steps to do it? Please, help.

Beatmapping will enable Logic to adapt to subtle or radical tempo changes like they happen in non quantized music or material which wasn't recorded to a click. I think what you are looking for is a way to improve the timing of your recorded drums. Check out the Strip silence function which will slice up your Audio into smaller regions detecting transients and silence. These newly created regions can then be quantized in various ways in the Region event editor.
Also in the sample editor->Factory->quantize engine you'll find some tools which claim to improve timing of Audio files but I wouldn't really advise you to use them.

Timing problems with AU Ivory Piano + ESB and Logic 7.2

I have problems with Ivory and Logic 7.2:
The Ivory (AU version 1.50) plays well in tempo, but when I want to bounce (export track as audio file) the Ivory plays totally out of tempo.
Even when I touch the record button on audio tracks or when I want to record my mix on 2 audiotracks, the Ivory plays out of tempo.
Even freezing the Ivory track gives the same problem.
Then I need to go back to my last saved version.
The same actions with Emagic, Native Instruments and Spectrasonics AU plugins, and everything works fine.
I throwed away already the Ivory prefs, no positive results.
My Ivory sample files are on a separate 400 GB internal disk, and my Audio I'm recording on a external Glyph disk.
I think I have this problem since I've upgraded from Logic 7.1.1 to 7.2 but I'm not sure. I didn't worked long with Logic 7.1.1.
I don't work in Protools, but I use the DAE and Direct TDM (no Core Audio)
It happens in the most simple application: no DAE or AU plug-ins, only one Ivory AU plug-in.
This is my configuration:
Ivory AU (Audio object-Direct TDM-Instr) output ESB 1-2 -> input ESB1 2 (Audio Object-DAE) -> Output 1-2 of my digidesign interfaces
Ivory becomes totally unusable for me this way. Is someone having the same problems?
Suggestions?
Wim Claes
Setup
Logic 7.2
Protools 7.1cs4
192, 2x96i, 1x 96 interface
G5 dual 2,7 Mac OS X (10.4.3) 4 GB RAM

I tried already a lot of things, but it is very clear:
1. Instantiating Ivory as AU- Ivory plays in tempo
2. Record enable an audio track in the arrange window - Ivory plays out of tempo
This happens with the default song of logic, no other plugins or AU-instruments are instanciated.
I can not find a way to convert my Ivory-midi to audio without the timing problems;
Bouncing, freezing, record to audio, export as audio file: all those things result in timing problems.
I tried this all with emagic plugins (ES2...) and Native Instruments plugins and then I don't have the tempo problem

What happened to Emagic's good old AMT = Advanced Midi Timing in Logic 7, 8

I wonder if anybody knows if Apple dropped the AMT-algorithm enabeling Emagic's AMT 8 and Unitor 8 Mk 1 and 2 to be more accurate in Midi timing than ordinary interfaces without AMT are. The last button/check box that was related to AMT (Advanced Midi Timing) I saw was in Logic 6. Steinberg and Motu had their own timing accuracy systems then.
Since in the whole Logic Studio manual AMT is not mentioned a single time I supposed this very useful tool has been sacrificed by Apple's dingy future spirit.
Not to be misunderstood: I know the interfaces can be installed and are supported and be run by the actual machines and systems as normal Midi interfaces .

Just having a random search around:
http://developer.apple.com/audio/pdf/coreaudio.pdf
"The MIDIPacketList are a time-stamped list of packets to or from one endpoint.
All MIDI I/O functions use this structure. The MIDIPacket contains one or
more simultaneous MIDI events."
Also, back when Logic was first going in OSX, emagic had an article about this as well, although that's long since gone.
OSX's time stamping isn't exactly the same as AMT in detail, but is in essence the same thing. AMT works by time stamping events ahead of time, so the interface can fire them off as close to perfectly as the current MIDI stream allows. If you have two events at 1 1 1 1, but on different ports, an AMT interface can fire those events at precisely the same time, which can't happen with a regular (non-timestamped) MIDI stream, as the stream is serial in nature.
Because OSX has time stamping built in to the MIDI server, theoretically all MIDI output operations under OSX should take advantage of this - but at the geeky levels, I haven't been programming with this so I'm not completely up on all the details - it maybe that programs have to be written specifically to take advantage of it.
In any case, it's these reasons why AMT was never supported in Logic under OSX - it was basically redundant.

What is wrong with logics timing and playback and midi

hi all,
i recently bought logic x and there seems to be a lot of problems im having. first off i noticed that when i am editing whilst looping what im working on it doesn't allways register my changes untill i stop and play again. this is especially true when making fades. it makes it very awkward to make changes in realtime and slows me down a lot. is this a new feature of logic lol or is this a problem with previous logics aswell. is anyone else having this problem and does anyone know if apple are working to fix this? its not my computer as its hi spec 12 core. running 10.8.5.
next problem im having is nothing short of insane. i have my mbase 11 being triggered by midi in logic and playing through an audio channel in logic from my apogee duet. this works fine but only when audio track is selected which is annoying. trouble im having though is when i select another track it seems the midi for the mbase is doing something to the selected track. either triggering extra notes or delaying and playing extra notes. im not sure but it is mental and it means i have to open up the fx i want to edit and then deselect the track. anyone have any ideas if this is something i can fix or if apple know ect?
thanks for reading, any help would be most appreciated
Rhys

Fades can't be edited in real time, Logic creates a fade file after you edited the region, then you press start and voila, it's always been like that.

Does logic have automatic timed back up???

hey,
lately logic 7.1 has been crashing at least 4 times aday. the "trying save you're song" message is all but gone and the songs backup file says that the folder has been modified very close to the time of the crash but I can't find any session that has been modified at the same time. automatic back up is active but only seems to backup the verisons of the the songs that i manually saved myself. can logic do auotmastic backups...let say every 5 minutes like whqat you have in pt? if so please tell me how or how the make logic get the "trying to save your song" message back.
thanks in advance,
eric j

Ok, That's a pretty big list. You can search these on the forums if you want to optimize things or see if any give certain problems, removing all and reintroducing 1 at a time. 3rd party plugs have caused at least as many crashes and data loss for me than Logic 7 has... I try to use them sparingly and don't keep them around long anymore. If you want to remove one at a time...I'd start with the RAM hungry ones. I think that alot of the frustration should not be on Logic but on the 3rd party plugs... AUVal doesn't cover everything in it's test. Just some of the really basic stuff that is necessary, and things which show signs of age. It is not 100% comprehensive.
J

Logic 10.0.5 is out! Three new drummers, LOADS of fixes.

I have not yet finished reading the release notes, it is almost 5,000 words...
http://support.apple.com/kb/TS4498
Logic Pro X 10.0.5: Release notes
Symptoms
Logic Pro X 10.0.5 is an update to Logic Pro X. Logic Pro X is a new paid version of Logic Pro.
Resolution
Logic Pro X 10.0.5 update
New features and enhancements
Includes 3 new Drummers and 11 new Drum Kit Designer patches.
Significant enhancements to Channel EQ and Linear Phase EQ plug-ins, including:
Redesigned, easier-to-use interface that's also accessible within the Smart Controls area
Double Precision processing provides more accurate filtering, especially for low frequencies
Oversampling option improves high-frequency clarity
Option to apply EQ only to stereo left, right, middle, or side signals
There is now an option to set the Piano Roll to a light background color.
Selected notes in the Piano Roll are now highlighted by a selection frame.
When Logic is stopped or in Play mode, the glyph on the Metronome button in the control bar now illuminates to indicate that “Click while recording” is enabled.
The Shuffle commands are improved (see Logic Pro X Help for details).
User interface
There is now a command to assign region names to track names.
The waveform size in an audio region now adapts to the value of the region gain parameter.
Loops that belong to the same family can now be selected and changed using a new control in the region header.
Logic Pro X now assigns region and Mixer channel colors that are closer to the original colors when opening a project created in an earlier version of Logic.
Option-clicking a disclosure triangle in the Project Audio window now toggles all disclosure triangles in the window.
The Windows menu again lists all currently open windows.
The Mixer can now be reliably resized when in All mode.
Renaming multiple selected Mixer channels now reliably renames all channel strips in the selection.
When creating a duplicate track, the correct track icon and color are now assigned to the duplicate.
The song title is now automatically populated in the Share to iTunes dialog when sharing a song created in Logic 9 or GarageBand for iOS.
It's once again possible to browse or load patches onto the Output channel strip via the Library.
The View menu items One Track and Selected Regions in the Piano Roll are now disabled when Link mode is disabled.
Performance
Improves processor balancing for multi-output software instrument configurations.
Improves handling of multiple displays on OS X Mavericks v10.9.
Resolves an issue that in some cases might cause audio clicks and pops when scrolling.
Moving an automation line while playing no longer spikes in CPU usages, or clicks and pops in the audio output.
Resolves an issue that could cause clicks and pops in the audio output when adjusting the gain or output level settings during playback in the various plug-ins.
Logic's interface no longer freezes when using the Native Instruments Maschine controller to adjust two macro controls simultaneously.
Fixes an issue in which a warning about not enough memory might be displayed when performing Undo after editing a protected track.
Adjusting the frequency controls while playing audio through the Stereo Spread plug-in no longer causes audible zipper noise.
Improves the performance of scrolling when dragging regions in the Tracks area beyond the currently visible section.
Playing notes live into the Arpeggiator plug-in no longer sometimes leads to spikes in CPU usage.
Fixes an issue that could cause a spike in CPU usage when recording near the end of a project.
Logic 9 projects that contain a macro object in the Environment now behave more reliably when opened into Logic Pro X.
Multiple instances of the Scripter plug-in no longer have the potential to cause stuck notes.
The Scripter plug-in is no longer prone to causing stuck notes when using the Delay Note Until Next Beat preset.
Switching between presets in the Space Designer plug-in no longer sometimes results in noise.
General
Regions copied from a Track Stack can now be muted as expected even when they are within a Track Stack that is muted.
Deleting an audio Track Stack while it was soloed no longer leaves all the remaining tracks muted.
Entering a new crossfade value in the Region inspector for multiple selected regions now works as expected.
Region-based automation data beyond the end of a region is now chased properly even when playback is started after the last automation node within the bounds of the region.
Logic now maintains the correct relative levels when automation on multiple tracks belonging to the same Group are copied by dragging.
Resolves an issue in which track automation might be deleted when switching patches.
The default display setting when showing automation on Track Stacks is now Volume, instead of Display Off.
A track is now created as expected when using a control surface to set the automation mode of a channel strip not previously assigned to a track.
Moving a SMPTE locked region can no longer cause the automation on the track to move.
The position of the automation line no longer jumps unexpectedly when it is selected after creating 4 automation points with a Marquee selection.
Adjacent automation points of the same value are no longer sometimes inadvertently deleted when moving automation points on a grouped track.
The Repeat Section Between Locators command now includes automation on tracks that contain no regions in the repeated section.
When using Touch mode, Logic no longer writes unneeded automation points at the held value when holding a fader at the same position where there is an existing automation ramp.
Writing automation to an Aux not assigned to a track can no longer potentially cause tracks in a Track Stack to be rerouted to that Aux.
Copying multiple regions where only some affected tracks contain automation no longer activates Automation Read mode on the channel strips that have no automation.
Chase now works as expected for MIDI controllers on channels other than channel 1.
Takes are now shortened as expected when the take folder containing them is shortened by an edit operation and No Overlap mode is enabled.
Fixes an issue in which the visible area might jump unexpectedly when comping in a take folder that was not on the selected track.
Fixes an issue that caused some audio regions to be immovable when duplicate regions are packed into a take folder.
Packing regions with names containing non-ASCII characters into a take folder no longer creates garbled take names.
Numbers assigned to MIDI takes now increment reliably.
Expanding a take folder no longer potentially causes the playhead to fall out of sync with the audio output.
When using OS X v10.9, the playhead in the Audio Editor now consistently maintains the correct position when switching from Flex Time to Flex Pitch mode.
It's now possible to set a loop to a length of less than 1/16 note.
The position of beat markers in the Global Beat Mapping track are now updated appropriately when using the various Cut/Insert Time commands.
Inserting a beat marker in the Beat Mapping track no longer creates unexpected tempo events in some circumstances.
Expanding a take folder no longer potentially causes the playhead to fall out of sync with the audio output.
Resolves an issue in which some MIDI notes might unexpectedly change position when Beat Mapping.
Adding a Beat Mapping marker no longer intermittently removes existing tempo events.
Inserting a fade-in using Shift-Control and the Pointer tool now works consistently.
Using the Fade tool to set fade-ins on multiple regions in a set of grouped tracks now works reliably.
Dragging regions on multiple grouped tracks with the Drag Mode set to X-Fade no longer potentially results in crossfades of varying lengths.
The Delete command now works as expected on selected regions that are inside a collapsed Group in the Project Audio window.
It's now possible to add a green Apple MIDI loop to the Tracks area as an audio loop by dragging it from the Loops browser while pressing the Option key.
Logic Pro X no longer creates separate tracks for non-overlapping regions when unpacking folders in projects created by earlier versions of Logic.
Using the menu that appears when pressing the Metronome button in the Control Bar, it's now possible to set the metronome to sound only during count-in.
Improves the reliability of Undo in several areas.
The Mixer window no longer intermittently moves when scrolling past the minimum or maximum value of the fader using a scroll wheel or gesture.
It's now possible to select or open folder tracks in the Mixer.
Right-clicking an Aux or Output channel strip in the Mixer and selecting Create Track now behaves as expected even if the channel strip is not initially selected.
Command-click again works reliably to deselect a Mixer channel within a selected group of channels.
The display of audio waveforms of regions in a track no longer change unexpectedly when enabling or disabling the Groove status on a track.
Looped regions inside a folder now update the point they are supposed to stop playing after extending the length of the folder.
Overwriting an existing project no longer potentially leaves assets from the original project in place.
When creating a new project from a Logic 9 template, the default save path is no longer the location of the template.
Improves the mapping of Smart Controls to channel strip settings created in Logic 9.
The Follow Tempo parameter in the Region inspector is no longer incorrectly disabled for Apple Loops in songs last saved in GarageBand 6 or earlier.
Clicking and holding down on the upper-right corner of a region no longer unexpectedly enables looping in the Region inspector, with a loop length of zero.
The Region Inspector no longer displays a Loop checkbox for selected Track Stack folder regions.
It's once again possible to disable Quantize in the Region Inspector for a region on a track slaved to a Groove Master track.
Saving a song created from a template no longer resets the tempo to 120 BPM.
Text for alert messages now always displays correctly on control surfaces.
Changing Region inspector parameters for MIDI regions on the main track of a Track Stack now behaves as expected.
It's again possible to change the Transpose value in the Region Inspector using the + and - keys.
Logic now consistently responds to Play or Stop key commands when a floating Region inspector window is open.
It's no longer possible to give the same name to more than one project alternative.
MIDI played from the Musical Typing Keyboard and Logic Remote is now routed through the Physical Input object in the Environment, which allows Environment processing of MIDI as it is being played into Logic from these sources.
Logic no longer adds 2 extra frames to the value when entering a SMPTE position in a project set to a non-drop frame rate.
Regions copied by option-dragging in projects with a start position earlier than bar 1 now end at the desired position.
Moving the first arrangement marker in a project no longer inadvertently moves other arrangement markers.
Resolves a rare issue that could cause the timing of a track in a project with many tempo changes to be altered after turning Flex on and then off.
Logic now asks the user to save the project when closing a project immediately after entering text into the Project Notes area.
It's now possible to consistently add, remove, or edit plug-ins on tracks that were frozen in Source Only mode.
Pressing the Control key while dragging a region with the Snap Mode set to Bar now moves the region by beats instead of ticks, as expected.
Editing the left border of an audio region now behaves as expected when the Snap setting is set to “Snap Regions to Relative Value”.
Resizing a region with the Snap setting set to “Snap Regions to Absolute Value” now behaves as expected.
Resolves an issue that caused an event in the Event List to move later than expected when editing its position.
The “Capture as Recording” command now works as expected when multiple MIDI tracks are record-enabled.
It's now possible to preview sections of an audio file outside the current region borders by clicking the area in the Project Audio window.
The tap-to-click option for trackpads now works reliably with all drop down menus.
The “Discard Recording and Return to Last Play Position” key command now reliably discards the recording.
It's again possible to use the Tab key to navigate to the next control while working with plug-ins in Controls view.
The MIDI Activity display now shows chords as they are played when using Musical Typing.
All currently found audio files are now reliably saved with a project when using Save As or Save a Copy As with a project in which one or more audio files are missing.
The name of a project is now correctly updated after saving a project created from a template.
Fixes an issue in which clicking on the level LED in the track header did not select the track.
Resolves an issue in which changes made to the setup for Mackie Control and other MCU-compatible control surfaces were not saved by Logic Pro X.
Setting the Display Time preference to “SMPTE/EBU with Subframes”, “SMPTE/EBU without Subframes,” or “SMPTE/EBU with Quarter frames” can no longer cause the time display to jump unexpectedly.
Saving a project for the first time no longer resets the record path when it was previously set to an external path.
Performing undo in the Piano Roll or after deleting a flex marker no longer has the potential to unfreeze currently frozen tracks in the project.
Sample rate, tempo, and key information is now reliably stored within template files.
Fixes an issue in which the Repeat Regions dialog did not have key focus when opened, making it necessary to click it with the mouse before pressing Return to confirm the operation.
Individual MIDI Draw points in the Piano Roll are now easier to grab.
Deleting a track no longer has the potential to inadvertently delete regions on other tracks.
Cut/Insert Time edits no longer add unexpected tempo changes.
Scrubbing the SMPTE display in the LCD no longer moves the playhead to the wrong position.
Copying an arrangement marker to a position between two other arrangement markers now moves the end-of-song marker to accommodate the new section, as expected.
Audio
Audio regions now appear as expected in the Audio Editor, even when cycle is enabled and there are no audio regions within the cycle area.
Flex Pitch now correctly detects notes for take regions that have manually inserted flex markers.
The timing of notes played during the count-in on EXS24 or Drummer tracks is now more reliable.
Pasting an audio region into a take folder now correctly places the region on the selected take lane.
When saving an EXS instrument, the default save location is now ~/Music/Audio Music Apps/Sampler Instruments.
Editing the start point and anchor in the EXS audio editor now consistently alters playback as expected.
Logic no longer overwrites an existing audio file of the same name when performing a bounce with the option to create a split stereo file enabled.
Audio tracks assigned to output to a bus now consistently maintain that assignment when imported into a different song.
User-defined controller assignments now work as expected to control MIDI plug-in parameters.
The Record Repeat command now deletes the previous recording when used after recording in Cycle mode.
Quantize now operates reliably on takes that are displayed in the Audio Editor.
The Tuner window is no longer affected by the Content Link setting of other plug-in windows.
Audio now plays for multiple cycle iterations when using marquee selection to define the cycle area.
When the Edit command “Analyze Audio for Flex Editing” is used, Logic now properly resets any existing pitch edits on the selected audio files.
Command-clicking a selected note in Flex Pitch mode in the Audio Editor now deselects the note, as expected.
Setting a track to Flex Edit mode with the Slicing algorithm no longer processes the track with Flex if no edits have been applied.
It's again possible to set Software Instruments to mono.
Logic no longer creates an extra audio file when merging or format-converting audio files.
Resolves an issue in which the Mixer did not show the 8th bus send on a channel strip.
Changing the input format of a stereo output channel strip to mono now creates a second mono output channel strip on the Mixer for the other channel in the stereo pair.
Setting an external recording path now reliably resets the Audio Assets setting. Conversely, enabling the Audio Assets setting now disables an externally set recording path.
The compressor meter in the channel strip is now in sync with the meter in the plug-in window.
Drummer
Improves the translation of articulations when an Ultrabeat-based patch is assigned to a Drummer track.
When a project starts on an upbeat, a Drummer region at the project start now automatically creates a fill at the beginning.
Changes to Drummer regions are now reliably applied when the regions are set to follow a flexed audio track.
MIDI editors
The Link mode button is now available for the Piano Roll editor.
The “Limit Dragging to One Direction” setting now works as expected in the Piano Roll.
It's now possible to grab notes shorter than 15 ticks for editing in the Piano Roll.
Double-clicking a region with MIDI Draw enabled now consistently opens or closes a MIDI editor.
Resolves an issue in which recently recorded MIDI notes might disappear from view in the Piano Roll when recording with cycle engaged.
It's again possible to alter the pitch of notes in the Piano Roll via MIDI input.
Using Option-Shift to edit the end points of multiple selected notes to the same position in the Piano Roll Editor now works as expected.
In the Piano Roll, it's again possible to use Option-Shift in conjunction with the Velocity tool to set all selected notes to the same velocity.
An Event Float window that is linked no longer switches unexpectedly to the Region level when using arrow keys to move from note to note in the Piano Roll.
Pasting events in the Piano Roll when the playhead is to the right of the region border will not trigger the error “Illegal Region number”.
It's now possible to copy a note in the Piano Roll to a different pitch at the same position when the note starts before the left edge of the region.
It’s now possible to move notes in the Piano Roll by increments smaller than 13 ticks when the “Limit Dragging to One Direction” setting is enabled.
User-inserted rests no longer incorrectly appear as notes in the Piano Roll.
Copying a muted note in the Piano Roll now creates a muted copy of the note, as expected.
Fixes an issue in which some note events might not be selectable in the Step Editor.
The contents of the Event List are now updated properly when deselecting a region from a multiple selection while Content Link mode is enabled.
The Event List now displays the correct LSB values for 14-bit pitch bend events.
Editing Release Velocity values in the Event List now behaves as expected.
The “Copy selected events” option in the MIDI Transform window now behaves as expected.
Score Editor
Fixes an issue that could cause the menu option for switching between Parts and Score view in the Score Sets window to disappear.
Double-clicking a region with the All Instruments filter setting active now reliably reveals all regions on that track, rather than just the single region.
The contents of the Event List editor are more consistently updated when changing the region selection from the Score window.
Newly inserted key signatures no longer display “xx Major” in some circumstances.
The Chord Grid Editor now correctly names Add 9 chords.
The clef menu no longer disappears for a Mapped Instrument staff style set to “No Clef”.
It's again possible to create a new Chord Grid library that uses an alternate tuning.
It's now possible to adjust the Velocity setting in the MIDI Meanings settings window by scrubbing the value with the mouse.
The length adjustment in the MIDI Meanings settings window can now be adjusted via a pop-up menu.
In the Staff Style window, the check marks indicating that a style is used in the current song now reliably update to reflect changes when Content Link mode is off.
Grace notes now scale properly when the scale setting of a Score Set is less than 100.
Resolves an issue that prevented reassigning instruments assigned to a Score Set after performing certain other edits.
Fixes an issue that prevented naming a floating score Part box set.
Plug-ins
Solo now works as expected on channel strips using an external I/O plug-in
Ultrabeat can now find samples that have been relocated from the default install location.
Ultrabeat now correctly applies the Fine Pitch adjustment to all triggered samples when trigger mode is set to Multi.
It's now possible to halve/double the current rate of the Arpeggiator plug-in by clicking the Slow/Fast buttons.
The ES1 synth plug-in can now be set to offer 32 and 64 voices per instance.
The Scripter plug-in now allows System Realtime MIDI events to pass through.
The Scripter plug-in now offers an option to keep current control values when recompiling a script, rather than resetting all values back to their defaults.
The Scripter MIDI plug-in now includes a Set Parameter function.
Switching between Vintage Electric Piano patches while holding notes no longer potentially results in momentary jumps in level.
The Vintage Electric Piano no longer potentially creates audible pops when switching patches when the Drive is enabled and set to Type II.
It's now possible to continue working with the Scripter editor window when Logic Pro X is not in focus.
The Surround Compressor plug-in now properly shows all the new circuit types available in Logic Pro X.
It's again possible to copy or paste settings in the Space Designer plug-in window.
The order of controls in the Retrosynth Filter Envelope and Amp Envelope sections has been reorganized to improve usability.
The plug-in window no longer appears empty for Waves plug-ins opened in projects created in Logic 9.
Fixes an issue in which inserting a plug-in on multiple stereo Software Instrument channel strips would insert mono versions of the plug-in on some channel strips.
EXS24 or Kontakt settings are no longer removed from a song if the Audio Device buffer size is changed before saving the song.
Resolves an issue in which adjusting parameters on the Channel EQ while playing back might cause minor clicks and pops in the audio signal.
Moving an Amp Designer instance to a different plug-in slot no longer sometimes changes its sound.
“Save as Default” for Audio Unit presets again works as expected.
Video
It's now possible to exchange movie files in a project by dragging a new movie file into the Movie window or the Movie inspector.
Logic Pro X can now work with the following professional video codecs, if OS X Mavericks v10.9 and the codecs are installed: Apple Intermediate Codec, Apple ProRes, AVC-Intra, DVCPRO HD, HDV, XDCAM HD / EX / HD422, MPEG IMX, Uncompressed 4:2:2, XAVC.
There is now a Show/Hide Movie Window command in the View menu when the current project contains a movie.
Resolves an issue in which some movies that were compatible with QuickTime X did not play in Logic Pro X.
Exporting audio to a movie with a portrait orientation no longer causes the movie to rotate 90 degrees.
Logic is now able to export surround AAC audio to a movie even if the original audio in the movie was originally kept.
The visible frame of a movie now updates as note lengths in the Piano Roll are changed.
Import/export fixes and improvements
XML projects imported from Final Cut Pro X now contain volume and pan automation when opened in Logic Pro X.
Exporting a project as an Final Cut Pro/XML file with the “Export as Final Cut Compound Clip” option enabled now behaves as expected.
Includes several improvements to the way Logic handles audio sample-rate conversion when importing Final Cut Pro XML.
Logic now shows a progress bar when importing large Final Cut Pro XML projects.
32-bit float audio files in Final Cut Pro XML projects are now converted to 24-bit files during import so they play properly when imported into Logic.
The start time of imported Final Cut Pro XML projects is now consistently correct.
It's now possible to export Music XML when the Score window is in linear view mode.
Logic no longer shows multiple alerts when importing a Final Cut Pro XML project containing videos in a format not supported by Logic.
Songs created in GarageBand 6 no longer load in Logic Pro X with an extra channel in the Mixer.
Fixes an issue in which audio in a song imported from GarageBand 6 might play back too fast in Logic Pro X.
Logic now offers to include embedded tempo and marker information when using Track Import to bring an audio file into a project that contains no other audio regions.
Simultaneously dragging multiple MIDI files into the Tracks area now behaves as expected when using No Overlap mode.
The default destination path for exported MIDI files is now the project folder instead of ~/Music/Logic.
When importing projects, there is now an Add All button in the Aux import dialog.
The user settings in the Bounce window are now retained after sharing to iTunes.
Split stereo SD2 files no longer incorrectly import as AIFF files when the WAV file option is enabled.
The “Share Song to iTunes” command now creates a playlist with the name entered if there is not already an iTunes playlist with that name.
MIDI events that precede the start point of a region are no longer included when the region is exported as a MIDI file.
Stability and reliability
Includes several fixes related to stability and reliability, including to resolve issues that could cause Logic to quit unexpectedly in these circumstances:
When changing the length of a time-stretched region
When importing tracks from another project
When recording with the color palette open
When bypassing an instance of the Maschine plug-in
When exporting Music XML after applying Enharmonic Shift to some notes
When changing the range on an Environment fader whose style was set to Text
When quitting a project that has a Surround Compressor inserted on a channel strip
When removing a control surface from the Control Surface setup window when the Logic Remote is also present
When changing the range value of a Smart Control during playback.
When reapplying a Time and Pitch operation after undoing a previous one
When dragging an audio region from a take folder to a new song

Thanks Erik,
If nothing else, this huge list of updates and fixes, shows clearly that the Logic Dev team is working hard on fixing and improving LPX to a major degree.... and from the list of fixes done.. show they do read the bug reports submitted!
As an aside....
I recall how all the 'naysayers' prior to LPX (and in some cases, since...) were proclaiming how Logic was dead, the team was being disbanded, we won't see any further development, the Dev team doesn't listen or care... and so on....... I wonder where those people are now?

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

Logic 7.1.1 Timing ...poltergeist??

Similar Messages

Maybe you are looking for