Hi guys, new to the forum and looking for some help.

Have been using a cracked version of Logic X coming from Logic 9 for the past few weeks now. Some good points, some bad points.

At the moment whats really annoying is when I duplicate a track using CMD + D I get the spinning wheel for about 10/15 seconds then it loads up the track.

This happens on both audio and MIDI, whether it has 10 plugins or none at all......
When I add a new track using the '+' sign at the top it loads it straight away with no issues.

This is happening in all my projects and have updated through 3/4 different updates and am now on the current 10.2

I've gone through a whole project removing all the plugins individually which made no difference, now as soon as I started deleting the midi and audio off each track it would progressively allow me to duplicate faster. When I finally had no audio or midi anywhere in the project but still had all tracks with plugins the duplication was instant.

So why would having audio/midi in the project effect how quickly it will duplicate a track, regardless of whether that particular track has any audio/midi or 10 plugins or none?

I can open this same project in Logic 9 without removing anything and the duplication is instant.

Im running a hackintosh with the below specs:
Yosemite 10.10.2
Intel i7 4790 CPU, 16GB 1600Mhz RAM, 128GB SSD Main OS/Logic/Plugins Drive, 1TB Audio + Projects Drive, 2TB backup drive
SPL Crimson Audio Interface

and before anyone blames the system.... I'm getting the same issues replicated on my Macbook Pro.

Anyone else experiencing this bug? Any work arounds? Driving me crazy...

I have even considered buying a legit copy of Logic X.... but seem to think this won't solve it.

Thanks

 

CMD + D works instantly here.
But it just duplicates the track here not the events on it ?

Yosemite 10.10.4, Vanilla, Clover
Intel i7 4770k CPU, 32GB, 1TB SSD , RME Multiface II

 

I have my share of issues with Logic Pro X (for example Ultrabeat is simply forgetting the samples I previously loaded from an autosave to another or synths are going back to init or a midi loop triggers Pitch/Mod wheels without altering the respective information) but what are you pointing out is not happening on my setup.

 

Do you have Automap 4 installed on your system?

 

I had once a similar problem in Logic 9 and not awhile ago in Logic Pro X Legit version.

Basically, something went wrong with your Core Audio Driver and the only solution I've found to this problem and I really hope this helps you is to use this software - http://www.audiofile-engineering.com/support/helpdesk/index.php?pg=kb.page&id=563 and use the option repair core audio driver. I'm sure you can find the app somewhere.

After a reboot everything should be back to normal - Fingers Cross

 

Yeah its just the duplication of the track I'm attempting... not copying anything at all. Its just bizarre how when I start deleting any audio or midi from within the arrange window, things progressively start speeding up again when Im duplicating.

Erugh, its so frustrating. I have tried a fresh install with no luck at all. It seems an isolated case with myself.... and always made me think it was my Clover install but having replicated the issue on a Macbook Pro, it can't be.

Ive installed 3 different versions of Logic X too, to try and rule out a dodgy copy.

I don't have automap 4 no, and thanks Santiallana, I will give that a crack now x

 

Ok, There were very limited options in the application you suggested but the closest I found to what you are describing was 'Reset Core Audio Server'... unfortunately it has not made a difference.

If anyone else has any suggestions please advise.

At this rate I'm going to have to revert back to Logic 9, which I really really don't want to have to do after having this AutoSave function on Logic X.... but I use this DAW in a professional capacity and not being able to duplicate tracks without having to wait over 20 seconds every time is killing my creativity process.

Posted on Logic Pro help a few weeks ago and no one seems to have an answer there

 

My experience so far with Logic X, same as I remember it :

Process: Logic Pro X [575]
Path: /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X
Identifier: com.apple.logic10
Version: 10.2.0 (3987.29)
Build Info: MALogic-3987029000000000~2
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Logic Pro X [575]
User ID: 501

Date/Time: 2015-08-28 18:29:04.460 +0200
OS Version: Mac OS X 10.10.4 (14E46)
Report Version: 11
Anonymous UUID: A728G21E-06E4-D27F-0B15-695C36BB7B17


Time Awake Since Boot: 1100 seconds

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000025c

VM Regions Near 0x25c:
-->
__TEXT 000000010ed27000-000000010ff4a000 [ 18.1M] r-x/rwx SM=COW /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.logic10 0x000000010f9995de void std::__1::vector<std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>, std::__1::allocator<wchar_t> >, std::__1::allocator<std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>, std::__1::allocator<wchar_t> > > >::__push_back_slow_path<std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>, std::__1::allocator<wchar_t> > >(std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>, std::__1::allocator<wchar_t> >&&) + 23518
1 com.apple.logic10 0x000000010f99aa6d void std::__1::vector<std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>, std::__1::allocator<wchar_t> >, std::__1::allocator<std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>, std::__1::allocator<wchar_t> > > >::__push_back_slow_path<std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>, std::__1::allocator<wchar_t> > >(std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>, std::__1::allocator<wchar_t> >&&) + 28781
2 com.apple.logic10 0x000000010f999dca void std::__1::vector<std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>, std::__1::allocator<wchar_t> >, std::__1::allocator<std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>, std::__1::allocator<wchar_t> > > >::__push_back_slow_path<std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>, std::__1::allocator<wchar_t> > >(std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>, std::__1::allocator<wchar_t> >&&) + 25546
3 com.apple.LogicUIKit 0x0000000112eaa4c5 0x112c5d000 + 2413765
4 com.apple.CoreFoundation 0x00007fff8847245c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
5 com.apple.CoreFoundation 0x00007fff88362634 _CFXNotificationPost + 3140
6 com.apple.logic10 0x000000010f7ad355 std::__1::__tree<std::__1::__value_type<TGInstID, TGInstID>, std::__1::__map_value_compare<TGInstID, std::__1::__value_type<TGInstID, TGInstID>, std::__1::less<TGInstID>, true>, std::__1::allocator<std::__1::__value_type<TGInstID, TGInstID> > >::destroy(std::__1::__tree_node<std::__1::__value_type<TGInstID, TGInstID>, void*>*) + 135749
7 com.apple.logic10 0x000000010f7ad54c std::__1::__tree<std::__1::__value_type<TGInstID, TGInstID>, std::__1::__map_value_compare<TGInstID, std::__1::__value_type<TGInstID, TGInstID>, std::__1::less<TGInstID>, true>, std::__1::allocator<std::__1::__value_type<TGInstID, TGInstID> > >::destroy(std::__1::__tree_node<std::__1::__value_type<TGInstID, TGInstID>, void*>*) + 136252
8 com.apple.logic10 0x000000010f3448b1 std::__1::vector<ScSymbolFontID, std::__1::allocator<ScSymbolFontID> >::vector(std::__1::vector<ScSymbolFontID, std::__1::allocator<ScSymbolFontID> > const&) + 34353
9 com.apple.logic10 0x000000010f344765 std::__1::vector<ScSymbolFontID, std::__1::allocator<ScSymbolFontID> >::vector(std::__1::vector<ScSymbolFontID, std::__1::allocator<ScSymbolFontID> > const&) + 34021
10 com.apple.logic10 0x000000010ef0f665 void std::__1::vector<CScalWave::segmentColor_t, std::__1::allocator<CScalWave::segmentColor_t> >::__push_back_slow_path<CScalWave::segmentColor_t const&>(CScalWave::segmentColor_t const&&&) + 212357
11 com.apple.logic10 0x000000010f3e9bd5 void std::__1::vector<CTRow, std::__1::allocator<CTRow> >::__push_back_slow_path<CTRow>(CTRow&&) + 304853
12 com.apple.logic10 0x000000010f3e658e void std::__1::vector<CTRow, std::__1::allocator<CTRow> >::__push_back_slow_path<CTRow>(CTRow&&) + 290958
13 com.apple.Foundation 0x00007fff89106953 __NSFireTimer + 95
14 com.apple.CoreFoundation 0x00007fff884092e4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
15 com.apple.CoreFoundation 0x00007fff88408f73 __CFRunLoopDoTimer + 1059
16 com.apple.CoreFoundation 0x00007fff8847c53d __CFRunLoopDoTimers + 301
17 com.apple.CoreFoundation 0x00007fff883c4608 __CFRunLoopRun + 2024
18 com.apple.CoreFoundation 0x00007fff883c3bd8 CFRunLoopRunSpecific + 296
19 com.apple.HIToolbox 0x00007fff91d2256f RunCurrentEventLoopInMode + 235
20 com.apple.HIToolbox 0x00007fff91d221ee ReceiveNextEventCommon + 179
21 com.apple.HIToolbox 0x00007fff91d2212b _BlockUntilNextEventMatchingListInModeWithFilter + 71
22 com.apple.AppKit 0x00007fff896638ab _DPSNextEvent + 978
23 com.apple.AppKit 0x00007fff89662e58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346
24 com.apple.AppKit 0x00007fff89658af3 -[NSApplication run] + 594
25 com.apple.AppKit 0x00007fff895d5244 NSApplicationMain + 1832
26 com.apple.logic10 0x000000010f3bd01e void std::__1::vector<CTRow, std::__1::allocator<CTRow> >::__push_back_slow_path<CTRow>(CTRow&&) + 121630
27 libdyld.dylib 0x00007fff874345c9 start + 1
...​

 

Last edited: Aug 31, 2015

Without seeing the rest of the crash log, it's hard to say what exactly is causing this crash but it looks like a system config issue based on what you did post.

Did you move any part of Logic or it's content to an external Hard Drive for example. If so don't use aliases but use Symlinks instead to prevent such issues.