Jump to content

88keys

Member
  • Posts

    98
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

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

88keys's Achievements

Explorer

Explorer (4/14)

  • Reacting Well Rare
  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare

Recent Badges

14

Reputation

  1. So this is really just more of a curiosity of mine as opposed to a useful workflow. And I may try it myself for the heck of it. But, has anyone tried using Mastering Assistant to EQ/Compress/Limit individual tracks? Now you can't put it anywhere except the master out. But say you had a project with a few instruments - let's say drums, bass, piano, and vocals. Working with just the raw tracks, mute 3/4 of them and let MA analyze, say, just the raw vocal after edits/pitch etc. Bounce that out to a new audio file. Now you have a sort-of auto EQ'd and compressed/limited vocal. Maybe set the Width parameter in MA to hard left (0 width) for this and add the exciter. Continue in this manner for every other track. Drums get some Width, bass doesn't etc. Now import all of those new audio files back into your project, turn off MA, and start your mix over from there. I'm not saying this is a good idea. I just wonder. If MA is smart with its analysis, will it see my pseudo vocal-only song as, well, a vocal-only song, and will it behave well with its eq-ing? Or will it boost the hell out of the lows thinking 'hey wait, this song has no significant bass" etc. How smart is that algorithm? Again, this is just a curiosity. Though I wouldn't be surprised at all in the future if we saw a per-track Mixing Assistant in Logic that could intelligently eq/compress certain instruments in a mix, maybe even add spatial effects. Yeah, I know, there are still 10,000 mixing decisions that should be made by human ears. I just wonder.
  2. It's no different for me in Sonoma. Fortunately, the ability to "recover" means that it's just a minor hiccup. And like I mentioned, it's not terribly frequent when I'm actually working on a session. It's more likely to occur when I leave Logic just sitting idle - I think simply because of the length of time involved.
  3. It is the indeed the AUHostingServiceXPC_arrow process.
  4. I too have had similar problems with threads running JUCE Timer ( C++ JUCE Framework). That was a problem for me with Modartt Pianoteq for a long time and that dev confirmed that they build with JUCE. But lately (since 10.7.8 I recall) this has been happening even after I close a project and leave Logic running; and I can't identify a plugin/culprit specifically, although the full crash log certainly contains a data snapshot showing plugins that were loaded with the last opened project. I don't always have a crash log. But here is a recent one (just the crashed thread): Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: AUHostingService [15457] Application Specific Information: abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x185cad11c __pthread_kill + 8 1 libsystem_pthread.dylib 0x185ce4cc0 pthread_kill + 288 2 libsystem_c.dylib 0x185bf4a40 abort + 180 3 libc++abi.dylib 0x185c9c6d8 abort_message + 132 4 libc++abi.dylib 0x185c8c6a0 demangling_terminate_handler() + 52 5 libc++abi.dylib 0x185c9ba9c std::__terminate(void (*)()) + 16 6 libc++abi.dylib 0x185c9ba2c std::terminate() + 36 7 libsystem_c.dylib 0x185ba4f98 __cxa_finalize_ranges + 476 8 libsystem_c.dylib 0x185ba4d20 exit + 44 9 AudioToolboxCore 0x188023818 std::__1::__function::__func<AUHostingService_exit_handler()::$_2, std::__1::allocator<AUHostingService_exit_handler()::$_2>, void ()>::operator()() + 20 10 AudioToolboxCore 0x188023684 __30-[AUHostingService closeHost:]_block_invoke + 652 11 libdispatch.dylib 0x185b35cb8 _dispatch_call_block_and_release + 32 12 libdispatch.dylib 0x185b37910 _dispatch_client_callout + 20 13 libdispatch.dylib 0x185b45fa8 _dispatch_main_queue_drain + 984 14 libdispatch.dylib 0x185b45bc0 _dispatch_main_queue_callback_4CF + 44 15 CoreFoundation 0x185e0315c __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16 16 CoreFoundation 0x185dc0a80 __CFRunLoopRun + 1996 17 CoreFoundation 0x185dbfc5c CFRunLoopRunSpecific + 608 18 HIToolbox 0x190339448 RunCurrentEventLoopInMode + 292 19 HIToolbox 0x190339284 ReceiveNextEventCommon + 648 20 HIToolbox 0x190338fdc _BlockUntilNextEventMatchingListInModeWithFilter + 76 21 AppKit 0x18959ac54 _DPSNextEvent + 660 22 AppKit 0x189d70ebc -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 716 23 ViewBridge 0x18e3e0b50 __77-[NSViewServiceApplication vbNextEventMatchingMask:untilDate:inMode:dequeue:]_block_invoke + 136 24 ViewBridge 0x18e3e08b0 -[NSViewServiceApplication _withToxicEventMonitorPerform:] + 152 25 ViewBridge 0x18e3e0ab0 -[NSViewServiceApplication vbNextEventMatchingMask:untilDate:inMode:dequeue:] + 168 26 ViewBridge 0x18e3cce74 -[NSViewServiceApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 100 27 AppKit 0x18958e100 -[NSApplication run] + 476 28 AppKit 0x1895653cc NSApplicationMain + 880 29 libxpc.dylib 0x185a15cd4 _xpc_objc_main + 800 30 libxpc.dylib 0x185a24904 _xpc_main + 324 31 libxpc.dylib 0x185a1580c xpc_main + 64 32 ViewBridge 0x18e3c7cc8 -[NSXPCSharedListener resume] + 32 33 ViewBridge 0x18e3e3180 NSViewServiceMain + 360 34 AUHostingServiceXPC_arrow 0x100e923b8 0x100e8c000 + 25528 35 dyld 0x1859690e0 start + 2360
  5. Yes. I should have said 'usually' doesn't spawn a log. When it does, for example there is no mention of any plugin and it is usually the main thread that goes down. I'll post in the other thread on this issue - I don't wanna hijack here.
  6. 3 days into this, things are really stable. Recent upgrade from Ventura -> Sonoma 14.1 Logic from 10.7.8 -> 10.8 Original M1 Macbook Pro. All 3rd party plugins are fine: Waves, UAD Spark, PSP, Modartt, AudioModeling/SWAM, Valhalla, DDMF. The only problem is the occasional: "An Audio Unit plug-in reported a problem which might cause the system to become unstable. Please quit and restart Logic Pro" from which I can now always choose to "Recover." Although this has been happening with my system for the last 2.5 years - with varying degrees of 'recoverability' depending on the Logic version. Interestingly enough, it happens lately (for the last 3 months) Without a crash log (in Console app) Mostly NOT when I'm actually working on a project in Logic Usually without even having a project currently open - just having HAD a project open, now closed, but with Logic itself still open Frequently when I wake up the laptop (cover was closed) but Logic was open when it went to sleep All of that being said, this looks to be an exceptionally stable release here.
  7. It sounds much better now as a "fire and forget" solution for natural pitch correction. Much, much better. I guess I hadn't used the plugin since before 10.7.8. Honestly, it might be all I need now for subtle correction here and there, particularly if I use my old technique of automating the response time knob and/or detune slider.
  8. I just saw that the title of Apple's event for Monday is "Scary Fast." Apparently a nod to Halloween AND it's assumed, a new M3 chip. But I think there's a third meaning in there: In the new Logic version the default tempo for all projects will be 240 bpm.
  9. Ten thousand SURROUND SOUND tracks.
  10. I would love a dynamic eq with side chain.
  11. I completely agree. Which is why I wouldn't believe it either if it wasn't happening to me. To be clear, it's ANY new project, not a particular one. I'll post the log of the crash the next time this happens. But this is sort of off topic from the OP who I believe has identified that there is in fact a culprit plugin. I have in the past also had this crash from specific plugins and seen the offending one identified in an AUHostingService process in the crash log. But this is different now. There isn't even an AUHostingService process running.
  12. Yup. "An Audio Unit plug-in reported a problem which might cause the system to become unstable. Please quit and restart Logic Pro." But I have the option to "Recover" which does work.
  13. Well yeah, except that I’m getting this all the time now in 10.7.9 if I create a new project and never instantiate a single plugin. Simply wait about 20 min and and I’ll get this error message. Checking error Log in console shows Logic itself crashing from the main thread - not “AU host” (I can’t remember the exact name of that separate process). I wouldn’t believe it myself if I didn’t see it … daily.
  14. I find it interesting that, in the official release notes, there is a fix for an issue that comes up specifically with Fab Filter Pro Q.
×
×
  • Create New...