Jump to content

xgman

Member
  • Posts

    681
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

xgman's Achievements

  1. Yes, Maybe it's another one of the Sonoma 14.4 audio related bugs. Sometimes just dragging audio tracks in can make it crash and close too. Plus 10.7.7 doesn't have this problem. I also cleaned out all Logic files and started over, but 10.8 and 10.8.1 have the issue and again 10.7.7 doesn't. So hard to diagnose what is going on. Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Codes: 0x0000000000000001, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [37539] VM Region Info: 0 is not in any region. Bytes before following region: 4342648832 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 102d79000-104f3d000 [ 33.8M] r-x/r-x SM=COW /Applications/MULTIMEDIA/Logic Pro X.app/Contents/MacOS/Logic Pro X Error Formulating Crash Report: PC register does not match crashing frame (0x0 vs 0x1147B337D) Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 MAMusicAnalysis 0x1147b337d CMetroJointTimeSigBeatHMM::PostProcessHMMResult(std::__1::vector<std::__1::vector<float, std::__1::allocator<float>>, std::__1::allocator<std::__1::vector<float, std::__1::allocator<float>>>> const&, std::__1::vector<int, std::__1::allocator<int>>&, int) + 237 1 MAMusicAnalysis 0x114812f49 CMetroVariableBeatDetector::ComputeBeatsAndDownbeats(std::__1::vector<float, std::__1::allocator<float>>&, std::__1::vector<float, std::__1::allocator<float>>&, std::__1::vector<float, std::__1::allocator<float>>&, std::__1::pair<int, int>, std::__1::vector<int, std::__1::allocator<int>>, bool, BeatTrackerHints const&) + 3513
  2. seems like since 10.8 and 10.8.1 with latest Sonoma, when dragging in audio files (any format or bit rate) when logic start analyzing using smart tempo, it crashes out Logic. changing bit rate on project doesn't help. 10.7.7 doesn't seem to have this issue for me for instance. empty project, rosetta/or native. any ideas what to try to fix this?
  3. What fixed it (sort of) is the 2nd public beta of sonoma 14.3. It still runs a quick scan, but in about 10 seconds rather than 10+ minutes. very odd.. Thanks for the suggestions!
  4. I guess I don't understand why out of 5 DAW's tested, the only one with this issue is Logic. Why would Logic need to rescan already validated plugins at every startup. This bug has been around in one form or another for years. I guess I'm stuck with it.
  5. If I want to leave the spacebar set to the default play from last position, how exactly in Controller Assignments, do I set a shortcut key sequence for Play from Playhead position, so when the playhead is stopped, I can sometimes keep on playing from there, (but not that as the default spaecbar command). Thx. (I've done this before with OPT Double Space bar somehow, and now completely forgot how and where)
  6. don't have that file anywhere on my mac.
  7. I'll have to remove all UADx plugins. No other choice. What a mess. Thanks for trying to help.
  8. I can try the disable thing again. I wish these were available through the normal UAD update rather than Connect. I had no problem till the UADx updates Connect posted a couple days ago.
  9. yes I disabled all of them and re-enabled and they pass, but yet scan the next Logic launch. Usually this Logic behavior can be fixed with a cleared cache, but not this time.
  10. I cleared the plugin cache and let it validate, restart computer all over again and still problem persists only for UAD x plugins. Now 10 to 15 minutes of scanning only UADx.
  11. The new UADx updates now take forever to scan every time I start Logic. Is there any way to avoid that? They all pass validation, but re-scan in Logic (both ARM and Rosetta modes) every time I start up Logic for about 5-10 minutes now each session. (Latest Logic and Sonoma, Mac M1 Ultra)
  12. Since the last 2 updates, when I try to hold my mouse on the corners of midi notes in the midi editor, I get a jittery effect from the normal resize cursor to the pointer even though without the resize cursor, I can still resize the notes by dragging them. Only happens in the midi editor. Has anyone else seen this or have any ideas how to correct it? Thanks.
  13. Thanks for checking wonshu. Mine shows, but just huge to the point it only shows a small bit of the full graphics inside the boundaries of the Melda window. EDIT: Fixed by editing the GPU.XML file To: <?xml version="1.0" encoding="utf-8"?> <GPU Enable="1" />
×
×
  • Create New...