MachFive 3 unusable with DP8.06 and VE Pro...

[FMiguelez]

Hello.

I'm hosting MachFive 3 in VE Pro, and VE Pro is being hosted in DP8.06 (latest versions of everything).

That setup is unusable for me. I get stuck notes 70% of the time, and the mere action of clicking on MF's Browse Tab crashes everything instantly... DP just vanishes with an option to send a crash log.

This happens every single time.

I've tried repairing permissions, repairing the disk, etc. to no avail.


I should add that MachFive works perfectly directly under DP alone (without VE Pro). This way I don't get stuck notes and no crashes when clicking on the Browse Tab.
This makes me think it's some kind of problem between VE Pro and MachFive, but having it hosted inside DP definitely has something big to do with this.

Is anyone else seeing this?


There you can see the Browse Tab in MF that makes everything crash instantly the second I touch it:




And this is the message I get after DP vanishes:



And this is the crash Log. It reads that thread 0 crashed the system, but I'm not sure how to read the log and discover the cause and solution.
I just post the first 4 threads, otherwise MOTUNation's software won't let me upload so many characters.

Any ideas? Thanks!

Process: Vienna Ensemble Pro [434]
Path: /Applications/Vienna Ensemble Pro/Vienna Ensemble Pro Server (64-bit).app/Contents/MacOS/Vienna Ensemble Pro
Identifier: at.co.vsl.viennaensemblepro
Version: 5.3.13141 (5.3.13141)
Code Type: X86-64 (Native)
Parent Process: launchd [176]
Responsible: Vienna Ensemble Pro [434]
User ID: 501

Date/Time: 2014-04-23 23:58:38.521 -0500
OS Version: Mac OS X 10.9.2 (13C64)
Report Version: 11
Anonymous UUID: 206CA140-303F-30C4-A488-1448542FEE9F


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

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

VM Regions Near 0:
-->
__TEXT 0000000100000000-0000000100c91000 [ 12.6M] r-x/rwx SM=COW /Applications/Vienna Ensemble Pro/Vienna Ensemble Pro Server (64-bit).app/Contents/MacOS/Vienna Ensemble Pro

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.motu.MachFive3AU 0x000000010efe9b50 0x10ed24000 + 2906960
1 com.motu.MachFive3AU 0x000000010efebbc4 0x10ed24000 + 2915268
2 com.motu.MachFive3AU 0x000000010f1b7bbe 0x10ed24000 + 4799422
3 com.motu.MachFive3AU 0x000000010f15efe5 0x10ed24000 + 4435941
4 com.motu.MachFive3AU 0x000000010f15f2f3 0x10ed24000 + 4436723
5 com.motu.MachFive3AU 0x000000010f160e1e 0x10ed24000 + 4443678
6 com.motu.MachFive3AU 0x000000010f130031 0x10ed24000 + 4243505
7 com.motu.MachFive3AU 0x000000010f08b6a0 0x10ed24000 + 3569312
8 com.apple.CoreFoundation 0x00007fff8e7f1731 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
9 com.apple.CoreFoundation 0x00007fff8e7e2ea2 __CFRunLoopDoSources0 + 242
10 com.apple.CoreFoundation 0x00007fff8e7e262f __CFRunLoopRun + 831
11 com.apple.CoreFoundation 0x00007fff8e7e20b5 CFRunLoopRunSpecific + 309
12 com.apple.HIToolbox 0x00007fff8843aa0d RunCurrentEventLoopInMode + 226
13 com.apple.HIToolbox 0x00007fff8843a7b7 ReceiveNextEventCommon + 479
14 com.apple.HIToolbox 0x00007fff8843a5bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
15 com.apple.AppKit 0x00007fff8aef33de _DPSNextEvent + 1434
16 com.apple.AppKit 0x00007fff8aef2a2b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
17 com.apple.AppKit 0x00007fff8aee6b2c -[NSApplication run] + 553
18 QtGui 0x00000001017889a0 QDesktopWidget::resizeEvent(QResizeEvent*) + 13040
19 QtCore 0x000000010143c234 QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 68
20 QtCore 0x000000010143c5e4 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 324
21 QtCore 0x000000010143eccc QCoreApplication::exec() + 188
22 at.co.vsl.viennaensemblepro 0x000000010047954f main + 12095
23 at.co.vsl.viennaensemblepro 0x000000010002f0a8 start + 52

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff8e3b7662 kevent64 + 10
1 libdispatch.dylib 0x00007fff855dd43d _dispatch_mgr_invoke + 239
2 libdispatch.dylib 0x00007fff855dd152 _dispatch_mgr_thread + 52

Thread 2:
0 libsystem_kernel.dylib 0x00007fff8e3b2a1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8e3b1d18 mach_msg + 64
2 com.apple.CoreFoundation 0x00007fff8e7e3155 __CFRunLoopServiceMachPort + 181
3 com.apple.CoreFoundation 0x00007fff8e7e2779 __CFRunLoopRun + 1161
4 com.apple.CoreFoundation 0x00007fff8e7e20b5 CFRunLoopRunSpecific + 309
5 com.apple.AppKit 0x00007fff8b09316e _NSEventThread + 144
6 libsystem_pthread.dylib 0x00007fff837b3899 _pthread_body + 138
7 libsystem_pthread.dylib 0x00007fff837b372a _pthread_start + 137
8 libsystem_pthread.dylib 0x00007fff837b7fc9 thread_start + 13

Thread 3:: QThread
0 libsystem_kernel.dylib 0x00007fff8e3b794a poll + 10
1 at.co.vsl.viennaensemblepro 0x0000000100569865 ost::Socket::isPending(ost::Socket::Pending, unsigned long) + 101
2 at.co.vsl.viennaensemblepro 0x00000001001dfaaf ServerThread::run() + 335
3 QtCore 0x0000000101322de4 QThread::setPriority(QThread::Priority) + 820
4 libsystem_pthread.dylib 0x00007fff837b3899 _pthread_body + 138
5 libsystem_pthread.dylib 0x00007fff837b372a _pthread_start + 137
6 libsystem_pthread.dylib 0x00007fff837b7fc9 thread_start + 13

Thread 4:: AdvertiseSocketThread
0 libsystem_kernel.dylib 0x00007fff8e3b69aa __select + 10
1 QtCore 0x000000010146e73e qt_safe_select(int, fd_set*, fd_set*, fd_set*, timeval const*) + 142
2 QtNetwork 0x00000001023ad94f QLocalServer::listen(QString const&) + 16703
3 QtNetwork 0x00000001023abdfa QLocalServer::listen(QString const&) + 9706
4 QtNetwork 0x00000001023a436a QAbstractSocket::waitForReadyRead(int) + 250
5 at.co.vsl.viennaensemblepro 0x000000010023a7ab AdvertiseSocketThread::run() + 427
6 QtCore 0x0000000101322de4 QThread::setPriority(QThread::Priority) + 820
7 libsystem_pthread.dylib 0x00007fff837b3899 _pthread_body + 138
8 libsystem_pthread.dylib 0x00007fff837b372a _pthread_start + 137
9 libsystem_pthread.dylib 0x00007fff837b7fc9 thread_start + 13



VM Region Summary:
ReadOnly portion of Libraries: Total=268.2M resident=162.8M(61%) swapped_out_or_unallocated=105.4M(39%)
Writable regions: Total=706.6M written=262.9M(37%) resident=301.1M(43%) swapped_out=0K(0%) unallocated=405.4M(57%)

REGION TYPE VIRTUAL
=========== =======
ATS (font support) 32.1M
ATS (font support) (reserved) 4K reserved VM address space (unallocated)
CG backing stores 7672K
CG image 16K
CG raster data 24K
CG shared images 172K
Kernel Alloc Once 8K
MALLOC 627.8M
MALLOC (admin) 32K
Mach message 4K
Memory Tag 242 12K
Memory Tag 249 156K
STACK GUARD 56.1M
Stack 16.2M
VM_ALLOCATE 16.4M
__DATA 28.6M
__IMAGE 528K
__LINKEDIT 74.1M
__POVERDDATA 4K
__POVERTEXT 4K
__TEXT 194.1M
__UNICODE 544K
dylib 5696K
mapped file 85.2M
shared memory 4K
=========== =======
TOTAL 1.1G
TOTAL, minus reserved VM space 1.1G

Slave Computer, VE Pro hosting MachFive


Model: iMac8,1, BootROM IM81.00C1.B00, 2 processors, Intel Core 2 Duo, 2.4 GHz, 6 GB, SMC 1.29f1
Graphics: ATI Radeon HD 2400 XT, ATI Radeon HD 2400, PCIe, 128 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 800 MHz, 0x2C00000000000000, 0x3136485446323536363448592D3830304731
Memory Module: BANK 1/DIMM1, 4 GB, DDR2 SDRAM, 800 MHz, 0x7F7F7F7F7FF70000, 0x00004B363435315536344536383030460000
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8C), Broadcom BCM43xx 1.0 (5.10.131.36.16)
Bluetooth: Version 4.2.3f10 13477, 3 services, 15 devices, 1 incoming serial ports
Network Service: Wi-Fi 3, AirPort, en1
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: Hitachi HDS721010CLA332, 1 TB
Parallel ATA Device: MATSHITADVD-R UJ-875
USB Device: Built-in iSight
USB Device: Keyboard Hub
USB Device: Apple Optical USB Mouse
USB Device: Apple Keyboard
USB Device: USB2.0 Hub
USB Device: iLok
USB Device: USB2.0 Hub
USB Device: eLicenser
USB Device: IR Receiver
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
FireWire Device: unknown_device, OWC Mercury Elite, Up to 800 Mb/sec
Thunderbolt Bus:

[michkhol]

I have a similar setup, but I'm hosting MachFive 3 directly in DP and routing audio to and from VE Pro (to use MIR).

I had periodic crashes in DP 8.06 with MachFive instantiated there and I had to roll back to 8.05.

Not to solve your problem, but routing audio to and from VE Pro seems to be more stable. I only host Vienna instruments in VE Pro.

[FMiguelez]

I have a similar setup, but I'm hosting MachFive 3 directly in DP and routing audio to and from VE Pro (to use MIR).

I had periodic crashes in DP 8.06 with MachFive instantiated there and I had to roll back to 8.05.

Not to solve your problem, but routing audio to and from VE Pro seems to be more stable. I only host Vienna instruments in VE Pro.

Thank you for your answer, MichKhol.

What you've mentioned is something I have yet to try (the sending audio to VE Pro). I suppose that makes total sense when sending, as you mentioned, stuff to MIR.

But if I tried doing that to solve my current problem, then it would be easier to simply forget about VE Pro and host MachFive directly in DP (my current workaround). This way it works great, BTW.

I hope this is not one of those super complex issues where manufacturers can simply keep blaming each other... Is this a MF thing? A DP thing? Or a VE Pro thing, maybe?

--------
[EDIT UPDATE]

Ok. I think DP8.06 can be taken out of the equation for now, because the exact same thing happens if I host MachFive in VE Pro in a slave computer (running the latest everything).
I get the exact same crash the moment I touch the Browse tab, and I get tons of stuck notes. And this is SO weird, because I can almost swear this didn't happen 2 weeks ago... And I haven't installed anything new since then

[Killahurts]

Ok. I think DP8.06 can be taken out of the equation for now, because the exact same thing happens if I host MachFive in VE Pro in a slave computer (running the latest everything).

I don't know if you can cut DP out of the equation just yet.. I had to go back to 8.05 because 8.06 was absolutely the problem with Mach5. Since I use M5 in every template, I guess I have to wait for the next version to see if it's compatible.

[FMiguelez]

I don't know if you can cut DP out of the equation just yet.. I had to go back to 8.05 because 8.06 was absolutely the problem with Mach5. Since I use M5 in every template, I guess I have to wait for the next version to see if it's compatible.

How is it working in DP 8.05?

I just got word from VSL's tech support. They said that, after seeing my crash logs, they could determine that this is definitely a MachFive issue and there's nothing they can do about it. They suggested I contact MOTU (and I have).

Let's see what MOTU says or does about this...

It's weird that MachFive only crashes here when VE Pro is involved, either with VE Pro stand alone in a slave or VE Pro hosted inside DP in the master. MF appears to be working fine only when used as a regular VI inside DP.

[Killahurts]

How is it working in DP 8.05?It's weird that MachFive only crashes here when VE Pro is involved, either with VE Pro stand alone in a slave or VE Pro hosted inside DP in the master. MF appears to be working fine only when used as a regular VI inside DP.

Well I found out yesterday that MF does indeed act up in 8.05 as well. This is MF as it's own VI in DP, not in VEP host.. although nearly all my templates have multiple VEP plugins that talk to the slave machine.

With my system, MF doesn't crash.. what happens is, everything is fine during playback, then when the wiper approaches MIDI notes for MF, it starts to freak out and get stuck/jump around. It did this yesterday, and although it was painful to watch, everything actually did work and playback correctly. i.e. if I closed my eyes and just listened, all was well. However, I only had one MIDI note for it to play (three times, spaced apart by several seconds). It would bog down before and during each of these, and snap back to "normal" between and after them.

If that's not an indictment, I don't what is.. MF3 is definitely the problem here, not DP or VEP.

[FMiguelez]

I wonder if trying MachFive as VST instead of AU (or is it MAS the default?) would make a difference?

Does anyone know how I can force MachFive to load as VST in a slave computer and/or in the master computer via DP?

How do I know which format I'm currently using?

[toodamnhip]

The last "update" of Mach 5 also gave me various stuck note issues. I also have VE pro. I ended up having to bring Mach 5 directly into DP and it still stuck fro awhile necessitating bouncing a bass to audio. A month or so later, I un froze that bass and Mach 5 has not stuck notes. I have no idea why it works better now. I just know that the last M5 update made it stick notes months ago.

[michkhol]

I have been fortunate so far having MF 3.2 as AU in DP hosting 7 instruments with the VEPro server hosting everything else outside DP.

Does anyone know how I can force MachFive to load as VST in a slave computer and/or in the master computer via DP?

Don't have DP running now, from memory:
Move temporarily the AU plugin from /Library/Audio/Plug-Ins/Components to somewhere else like Desktop and restart DP. Make sure the VST plugin is visible and checked in DP Preferences plugin manager.

How do I know which format I'm currently using?

The plugin manager in DP should show this