And I really don't want to have to buy and learn another DAW/Interface/iMac. But I need my interface to record without it bugging out. It only does that with the interface, as audio plays back perfectly through the iMacs speakers. I AM able to open MuLab with Terminal but it slowly begins to do this nasty bit reduction thing to any audio playback from digital instruments OR stuff i record through my interface after a few seconds. It opened from the app icon and worked perfectly on my old Macbook Pro. Tried starting with Admin, uninstalled, re-installed, tried the /var/folder then delete everything but xx thing, run an analyser and a cleaner. In case of using direct audio inputs, this results in mono recording when only the. I've used the Quarantine Remover on the entire MuLab folder to no avail. Squenceur gnraliste Mutools MuLab 7 : 13 photos, 8 vidos, 6 news. And through hours of fruitless searching in order to remedy the situation, Im putting my trust in this forum. It tells me it can't be opened because it is damaged or incomplete. The app has your typical cancel sign on the desktop icon. Flexible tracks and sub-tracks support audio, MIDI and automation parts. Highlights Create, record, edit and play multi-track audio & music.

I love using MuLab, its a DAW, and I just bought an iMac (2009 running on 10.13.3 High Sierra) MuLab is an easy and rock-solid tool designed to create, record, edit and finalize your music MuLab exists as stand-alone app and as plugin for use in other host DAWs.

In MuLab 7, when splitting an audio part, no new marker is created. I have two problems, that may or may not be related. When using multi-timbral instruments, the live MIDI input channel was not properly. I've posted this on a Mulab forum but I still haven't solved this.

Mulab 7 recording no inputs available