阅读806 返回首页    go iPhone_iPad_Mac_apple

Extremely serious recording issue, Please Help

I have been regularly dealing with a devastating bug in Logic Pro X since at least 10.2.3, now onto 10.3 with the issue still very much present.

 

Logic frequently quits unexpectedly after recording audio, immediately after I press stop or the space bar.  It doesn't save the audio in the Audio Files folder, and the audio isn't in the trash.

 

I've tried removing excess plugins from my session, updated all plugins, updated Logic, kept my OS up to date (although still on El Capitan for "stability").  I'm a media composer that requires 3rd party plugins to work. I would very much rather not have to start reinstall my whole system only for the problem to reappear.

 

Thanks very much!

 

Here is the crashed thread from my latest crash report:   (more can be provided)

 

Process:               Logic Pro X [1648]

Path:                  /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X

Identifier:            com.apple.logic10

Version:               10.3.0 (4661.17)

Build Info:            MALogic-4661017000000000~2

App Item ID:           634148309

App External ID:       818314444

Code Type:             X86-64 (Native)

Parent Process:        ??? [1]

Responsible:           Logic Pro X [1648]

User ID:               501

 

Date/Time:             2017-02-07 14:37:21.621 -0600

OS Version:            Mac OS X 10.11.6 (15G1217)

Report Version:        11

Anonymous UUID:        916A50BE-0A94-6CF4-7083-D1F19617A724

 

Sleep/Wake UUID:       CF511693-9962-4369-B846-099BB891AE22

 

Time Awake Since Boot: 22000 seconds

Time Since Wake:       9900 seconds

 

System Integrity Protection: enabled

 

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

 

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000190530000

Exception Note:        EXC_CORPSE_NOTIFY

 

Breadcrumb Trail (reverse chronological seconds):

1465   gckConnected

1465   connectivity-check-thread-started

1466   gckLaunch (Activity ID: 0x0000000000011af8)

1724   logging-started

 

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

0   com.apple.logic10             0x000000011057e5b0 0x10ff88000 + 6251952

1   com.apple.logic10             0x0000000110e0db7b 0x10ff88000 + 15227771

2   com.apple.logic10             0x0000000110e0ec83 0x10ff88000 + 15232131

3   com.apple.logic10             0x0000000110dffeb9 0x10ff88000 + 15171257

4   com.apple.logic10             0x0000000110e12c72 0x10ff88000 + 15248498

5   com.apple.logic10             0x00000001106712c3 0x10ff88000 + 7246531

6   com.apple.logic10             0x00000001106708bd 0x10ff88000 + 7243965

7   com.apple.logic10             0x000000011066f1de 0x10ff88000 + 7238110

8   com.apple.logic10             0x00000001106761e1 0x10ff88000 + 7266785

9   com.apple.logic10             0x000000011067648c 0x10ff88000 + 7267468

10  com.apple.Foundation          0x00007fff9305ffde __NSThreadPerformPerform + 279

11  com.apple.CoreFoundation      0x00007fff933f47e1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17

12  com.apple.CoreFoundation      0x00007fff933d3f1c __CFRunLoopDoSources0 + 556

13  com.apple.CoreFoundation      0x00007fff933d343f __CFRunLoopRun + 927

14  com.apple.CoreFoundation      0x00007fff933d2e38 CFRunLoopRunSpecific + 296

15  com.apple.HIToolbox           0x00007fff9ef15935 RunCurrentEventLoopInMode + 235

16  com.apple.HIToolbox           0x00007fff9ef1576f ReceiveNextEventCommon + 432

17  com.apple.HIToolbox           0x00007fff9ef155af _BlockUntilNextEventMatchingListInModeWithFilter + 71

18  com.apple.AppKit              0x00007fff9e110df6 _DPSNextEvent + 1067

19  com.apple.AppKit              0x00007fff9e110226 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454

20  com.apple.AppKit              0x00007fff9e104d80 -[NSApplication run] + 682

21  com.apple.AppKit              0x00007fff9e0ce368 NSApplicationMain + 1176

22  com.apple.logic10             0x000000011087616e 0x10ff88000 + 9363822

23  libdyld.dylib                 0x00007fff8d58e5ad start + 1

 

Activity ID:             0x0000000000011af8

Activity Name:           Breadcrumb initiated activity

Activity Breadcrumb:     gckLaunch

Activity Image Path:     /usr/lib/system/libdispatch.dylib

Activity Image UUID:     C7499857-61A5-3D7D-A5EA-65DCC8C3DF92

Activity Offset:         0x0000240b

Activity Running Time:   1466.538524 sec

 

Trace Messages (reverse chronological seconds):

326.533288   libdispatch.dylib         0x0000800029fc4e4d Format not found

326.535280   libdispatch.dylib         0x0000800029fc4e4d Format not found

354.315835   libdispatch.dylib         0x0000800029fc4e4d Format not found

354.318225   libdispatch.dylib         0x0000800029fc4e4d Format not found

405.897491   libdispatch.dylib         0x0000800029fc4e4d Format not found

405.899534   libdispatch.dylib         0x0000800029fc4e4d Format not found

462.129117   libdispatch.dylib         0x0000800029fc4e4d Format not found

462.131391   libdispatch.dylib         0x0000800029fc4e4d Format not found

485.100774   libdispatch.dylib         0x0000800029fc4e4d Format not found

485.103163   libdispatch.dylib         0x0000800029fc4e4d Format not found

504.512468   libdispatch.dylib         0x0000800029fc4e4d Format not found

504.514596   libdispatch.dylib         0x0000800029fc4e4d Format not found

567.057925   libdispatch.dylib         0x0000800029fc4e4d Format not found

567.060731   libdispatch.dylib         0x0000800029fc4e4d Format not found

760.974987   libdispatch.dylib         0x0000800029fc4e4d Format not found

760.976553   libdispatch.dylib         0x0000800029fc4e4d Format not found

761.000986   libdispatch.dylib         0x0000800029fc4e4d Format not found

 

Model: iMac15,1, BootROM IM151.0207.B08, 4 processors, Intel Core i7, 4 GHz, 32 GB, SMC 2.23f11

Graphics: AMD Radeon R9 M295X, AMD Radeon R9 M295X, PCIe, 4096 MB

Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x859B, 0x43543130323436344246313630422E433136

Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x859B, 0x43543130323436344246313630422E433136

Memory Module: BANK 0/DIMM1, 8 GB, DDR3, 1600 MHz, 0x859B, 0x43543130323436344246313630422E433136

Memory Module: BANK 1/DIMM1, 8 GB, DDR3, 1600 MHz, 0x859B, 0x43543130323436344246313630422E433136

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x142), Broadcom BCM43xx 1.0 (7.21.95.175.1a6)

Bluetooth: Version 4.4.6f1 17910, 3 services, 27 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en1

PCI Card: pci1ccf,3, Audio, Thunderbolt@195,0,0

Serial ATA Device: APPLE SSD SM0512F, 500.28 GB

USB Device: USB 3.0 Bus

USB Device: Rugged Mini USB 3.0

USB Device: Portable SSD T3

USB Device: BRCM20702 Hub

USB Device: Bluetooth USB Host Controller

USB Device: FaceTime HD Camera (Built-in)

USB Device: KeyLab 49

Thunderbolt Bus: iMac, Apple Inc., 26.1

Thunderbolt Device: TAC-8, ZOOM, 3, 7.1

Turn off your Bluetooth, turn off your WiFi. Shutdown.

 

Unplug your TAC-8 audio interface and your Arturia Keyboard. Boot up your computer and run logic with just the built in Audio. Put a track in record and hit record for 10 seconds. Stop. Does this crash? I'm hoping it does not.

 

Next, make sure your bluetooth and WiFi are still off and plug in your TAC-8 interface. Restart Logic or select the TAC from Logic's Prefs or restart the Mac - whatever one you want to do. Boot Logic. Put a track in record and record 10 seconds. Stop. Does it crash? If it does not, move onto your Rturia keyboard. If it DOES crash, remove the TAC and connect the Arturia and reboot. Record in Logic (this would be with the built in audio) and see if it crashes.

 

All we're trying to do here is to see if any of the kit you are plugging into your Mac is causing the crash.

Thanks for the reply! 

 

I tried what you suggested.  The only issue is that I can't seem to consistently reproduce this problem, it usually happens after a longer take (2mins to 5mins) but apart from that it is completely random when it appears.  Last week I didn't have a single instance of the bug, which I thought meant that 10.3 fixed my issue.  I haven't added any new plugins between now and then, or changed any preferences.  I guess I'll have to try each step for a day or two each time to get it to crash...

 

One thing I should mention is that I'm running a Universal Audio 4-710d from ADAT into the TAC-8.  I thought the issue might be clock related, but I just picked up a BNC connector and the crash happened again. 

 

If this were plugin related, wouldn't it show up in the crash report?  If its the way the TAC-8 is behaving with the 4-710d, wouldn't it be in the form of jitter/crackle sounds?  Not unexpectedly closing the program, losing the audio in the process? 

 

I even ran Rember, the RAM tester the other day, with no faults.  Still very confused with all this.  Thanks for the help so far!

The 4-710d is the clock master, and the Zoom is getting clock from it.

 

I suspect the TAC-8, does the Zoom use proprietary drivers?

 

edit:  Never mind, wordclock

I'm also suspecting the TAC-8 now.  It does use proprietary drivers, and they are up to date.  I reinstalled the drivers a few weeks ago to see if that would change anything.  Last night, I tried changing the clock source from ADAT to Word Clock, with a new BNC cable.  The 4-710d and Tac-8 definitely had the same sample rate of 48kHz, but after a bit of MIDI recording I was given a different error message:


Error while trying to synchronize Audio and MIDI.

Sample Rate 46,450 recognized.

Check conflict between Logic Pro X and external device.

 

So after this, I tried making the TAC-8 the master clock, with the 4-710d as the slave, with 70ohm termination engaged.  Will report back to see what happens!

 

At this point, there's a 0% financing sale at my local music store, I think I'm just going to try a different interface to see if that erases the problem entirely.  Thanks for the help so far everyone, if anybody has anything else I should try I would be very appreciative.

 

Thanks!

After a few tests it appears the bug persists even with the TAC set to internal clock, with 4710d slaved via BNC. I do notice that it is more frequent when running more plugins, but I have still experienced the crash with very few plugins or CPU strain. All of my plugins are up to date,  would reinstalling them make any difference if they don't appear in the crash report?

 

Tomorrow I'm going to try out an Apogee Element, really hoping that the TAC is causing the issue and not something deep within my system.  If the crash happens again, what can I really do going forward?  Wipe my entire computer and start over ?

 

Thanks everyone!

One thing you can do that will help eliminate a system problem.

Create a new User Account, restart and signing as the new user, does the problem still occur.?

 

Try this setup without Wordclock on both your regular account and the new user you created.

 

Set the 4710d to internal clock, just for testing try using 44.1kHz at 24-bit. Set the TAC to slave to the Incoming clock on the ADAT couple. This is the correct setup for using an external digital device with an audio interface, the last device in the chain should be master clock. (or first device depending on how you see it, I would call the 4710d the first device.)

 

Make sure Logic is reading the clock and is showing 44.1.

It seems to have persisted in the new user account as well, I haven't spent the entire day testing yet but when opening a basic project in the new account and running 48kHz I experienced a crash.  Nothing yet when running 44.1 in an empty project, but again this crash isn't very consistent. 

 

Will try swapping out interfaces this afternoon, really hoping that fixes the problem... 

I seriously doubt a clock issue. You'd get bad recordings (as you suspected) and other errors (like the syncing midi and audio error.) It wouldn't trash your machine.

 

I've not had any serious problems with logic till 10.3. As this has been happening for a while I'd be looking at possible plugging issues or the audio interface kext. Hopefully swapping to something else will help diagnose the problem. I once had a DAW that did stuff like this intermittently, it was the power supply.

 

I'd ditch the TAC-8 kext too while testing.

 

Good luck.

Thank you for the advice!  Upon 1 evening's worth of testing, a few interesting discoveries with a new interface swapped out - the Apogee Element 88. 

 

For months now I'd been experiencing some intermittent noise/static garble in my monitors, as soon as I swapped to the Element this went away completely.  To me this is already a sign that something is just wrong with the ZOOM. 

 

I've only tried my regular setup, 48kHz with the 4-710d synced via ADAT, and it seems to be smooth sailing.  I tried running a few CPU intensive plugins and it hasn't crashed yet.  Will update again if I notice anything new, but thank you everyone all for your advice.  I still am wondering what exactly is going wrong with the TAC-8, maybe someone else will see this post and help someone else in need.

 

Thanks again! 

justinlogicx wrote:

 

Will update again if I notice anything new, but thank you everyone all for your advice.  I still am wondering what exactly is going wrong with the TAC-8, maybe someone else will see this post and help someone else in need.

 

Thanks again!

 

It's almost always a case of poorly written drivers, it could be hardware but doubtful, often the latest drivers aren't the best, Tascam products often ran badly with the latest drivers and ran well with a previous drivers install.

 

Good luck, sounds like you have found the problem.

I'm glad to have found a recent thread (2017) regarding the Zoom Tac-8 and audio driver issues. I'm wondering if the Zoom 1.0.3 update released in 2015 needs to be updated again. I seem to have a problem with the Zoom going into sleep mode or something, I sometimes lose MIDI connectivity from my Alesis keyboard controller, and more often than that I lose audio when switching between Logic and other apps that use sound, especially YouTube.

 

Right now I have Logic set to use the Zoom as it's input/output sources. When I lose audio the fix is to go to Logic's Audio Preferences and do anything that activates the "Apply" button. Then I get audio back.

 

Strange... not sure it's a Logic thing or a Zoom driver conflict. Any ideas?

最后更新：2017-10-08 00:44:51

  上一篇：go music library icloud unavailable
  下一篇：go Satellite view no longer on Find My Friends