M4L device with nothing but single [plugout~] object crashes Ableton
This is quick enough to reproduce so if someone is very bored and could test/confirm if this crashes for them that would be cool. Either way... I need a way to make this object stop crashing Ableton
Steps to reproduce:
1. Open Ableton, create single audio track in completely empty project (no plugins, no return tracks nothing)
2. Create new M4L audio device w/ nothing in patcher but a single object [plugout~ @chans 16] and save device
3. Save the Ableton audio track with that m4l device loaded (drag track to file browser, so it saves as regular .als)
4. Drag that audio track you saved back into your project
5. Get crash ("Serious program error has occurred bla bla no details, no diagnostic report here etc.")
This happens whether anything is attached to the plugout object's inlets or not . Weird thing is... I can drag just the device itself (not attached to a track) onto an existing track and do not get a crash.
Ableton Version: 10.1.9
Max Version: 8.1.2 (Non bundled or bundled doesnt matter)
OS: Windows 10
Audio Driver/Interface: MOTU Pro Audio/MOTU 828es
I’m not at my computer so I can’t test. But for more diagnostic info I‘d try:
1) Does it reproduce with latest Ableton and Max versions?
2) If you start a different song/project and drag the same .als (of the track with your device) into it do you get the same crash?
Have not updated yet as it's an entirely offline pc and I avoid updating unless necessary. I didnt see anything related in the few patch notes after Live 10.1.9 though. This is reproducible for me in any project, whether it's totally empty project with nothing but a single audio track, or an actual project with more tracks/plugins/etc.
Guess while I'm here, if anyone knows... what's the actual reason behind why we cannot just use the [dac~] object as is? Because I can have both Ableton and standalone max open with a dac object accessing the same outputs at the same time...
Bump because im still having issues
"Because I can have both Ableton and standalone max open with a dac object accessing the same outputs at the same time..."
with the same type of driver...? ;)
I reproduced with current Max and Ableton builds on MacOS 10.15.3. Report the bug/crash to support?
FWIW it also reproduces by:
(a) Defining the [plugout] object as [plugout 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16] (rather than via @chans 16).
(b) Using the "Audio Routing Example.amxd" device (Which uses plugout w/ 8 chans) from the audio routes package. https://cycling74.com/articles/audio-routings-a-new-system-for-multi-channel-routing-in-ableton-live
Given (b) happens you probably just need to stay away from that workflow for now and manually add multi-out M4L devices rather than importing them from .als. :-(
Process: Live [67036]
Path: /Applications/Ableton Live 10 Suite.app/Contents/MacOS/Live
Identifier: com.ableton.live
Version: 10.1.14 [2020-05-12_b749619222] (10.1.14 [2020-05-12_b749619222])
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Live [67036]
User ID: 501
Date/Time: 2020-06-04 14:41:47.680 -0400
OS Version: Mac OS X 10.15.3 (19D76)
Report Version: 12
Anonymous UUID: AA569BE7-6406-ADF0-74A5-D7570A19BEC5
Sleep/Wake UUID: C95F88E2-C59D-4404-8D3F-7F1204047327
Time Awake Since Boot: 2100000 seconds
Time Since Wake: 180000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 MainThread Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000038
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [67036]
VM Regions Near 0x38:
-->
__TEXT 0000000100000000-00000001041d3000 [ 65.8M] r-x/rwx SM=COW /Applications/Ableton Live 10 Suite.app/Contents/MacOS/Live
Thread 0 Crashed:: MainThread Dispatch queue: com.apple.main-thread
0 com.ableton.live 0x0000000100ee949b 0x100000000 + 15635611
1 com.ableton.live 0x00000001024e174d 0x100000000 + 38672205
2 com.ableton.live 0x0000000101a84e1f 0x100000000 + 27807263
3 com.ableton.live 0x0000000101c4a6f7 0x100000000 + 29665015
4 com.ableton.live 0x0000000101ed6133 0x100000000 + 32334131
5 com.ableton.live 0x0000000101c4a5a8 0x100000000 + 29664680
6 com.ableton.live 0x0000000101c4625c 0x100000000 + 29647452
7 com.ableton.live 0x0000000101c45d0f 0x100000000 + 29646095
8 com.ableton.live 0x0000000101c457aa 0x100000000 + 29644714
9 com.ableton.live 0x00000001026e7a29 0x100000000 + 40794665
10 com.ableton.live 0x0000000102afe0f2 0x100000000 + 45080818
11 com.ableton.live 0x0000000102afdf62 0x100000000 + 45080418
12 com.ableton.live 0x000000010115f811 0x100000000 + 18216977
13 com.ableton.live 0x000000010116460d 0x100000000 + 18236941
14 com.ableton.live 0x0000000100ece12e 0x100000000 + 15524142
15 com.ableton.live 0x00000001010be334 0x100000000 + 17556276
16 com.apple.Foundation 0x00007fff2f656af5 __NSFireTimer + 67
17 com.apple.CoreFoundation 0x00007fff2cf70804 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
18 com.apple.CoreFoundation 0x00007fff2cf703be __CFRunLoopDoTimer + 859
19 com.apple.CoreFoundation 0x00007fff2cf6fe9e __CFRunLoopDoTimers + 317
20 com.apple.CoreFoundation 0x00007fff2cf54aed __CFRunLoopRun + 2213
21 com.apple.CoreFoundation 0x00007fff2cf53bd3 CFRunLoopRunSpecific + 499
22 com.apple.HIToolbox 0x00007fff2baa965d RunCurrentEventLoopInMode + 292
23 com.apple.HIToolbox 0x00007fff2baa939d ReceiveNextEventCommon + 600
24 com.apple.HIToolbox 0x00007fff2baa9127 _BlockUntilNextEventMatchingListInModeWithFilter + 64
25 com.apple.AppKit 0x00007fff2a119ba4 _DPSNextEvent + 990
26 com.apple.AppKit 0x00007fff2a118380 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
27 com.apple.AppKit 0x00007fff2a10a09e -[NSApplication run] + 658
28 com.ableton.live 0x00000001010be00c 0x100000000 + 17555468
29 libdyld.dylib 0x00007fff645f97fd start + 1
...... elided to save the forum
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x00000001a4db04a8 rbx: 0x00007ffeefbfccf0 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x00007ffeefbfcc90 rsi: 0x0000000000000001 rbp: 0x00007ffeefbfcca0 rsp: 0x00007ffeefbfcc90
r8: 0x0000000000000010 r9: 0x0000000000000000 r10: 0x0000000000000017 r11: 0x0000000000000017
r12: 0x00007ffeefbfccf0 r13: 0x00007ffeefbfcd10 r14: 0x0000000000000001 r15: 0x000000011b161000
rip: 0x0000000100ee949b rfl: 0x0000000000010246 cr2: 0x0000000000000038
Logical CPU: 0
Error Code: 0x00000004 (no mapping for user data write)
Trap Number: 14
...... elided to save the forum
I guess I am comforted by the fact that I am not alone lol