Hello,
What is the recommended way to record audio (voice) with mutools 7 while being able to listen to other tracks while recording and check levels?
Thank you,
d.vyd
Recording audio with mutools 7
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
I'm not aware there's anything specific to MuLab. You will, of course, need isolation between your monitoring output and the audio pickup (mic). And of course you need to have the lowest buffer settings you can manage to avoid latency without causing performance issues.
Other than that, add your audio track for recording, hit record and the rest of the project will play whilst recording the incoming audio.
Other than that, add your audio track for recording, hit record and the rest of the project will play whilst recording the incoming audio.
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
-
- KVRist
- Topic Starter
- 219 posts since 3 May, 2016
I'm able to record in audacity, so my USB microphone and driver are working. Here are the steps I'm taking in MuLab 7:
1. open new project
2. MuLab --> Audio Setup --> driver type = MME Audio Output & driver = Microsoft Sound Mapper. Are there better options?
2. add audio track
3. audio track is "armed" by default with the red circle
4. click arrow to get "track 3 recorder" window
5. record from: should I select "direct audio input" or "audio input 1"? I cannot get either to work.
6. mono/left and right inputs show as "none" with no other choices in the pull down -- I'm guessing this is a problem...
7. If, I switch to modular view, what should the correct flow look like? audio input 1 --> track 3 recorder --> rack 3 --> master?
-d.vyd
1. open new project
2. MuLab --> Audio Setup --> driver type = MME Audio Output & driver = Microsoft Sound Mapper. Are there better options?
2. add audio track
3. audio track is "armed" by default with the red circle
4. click arrow to get "track 3 recorder" window
5. record from: should I select "direct audio input" or "audio input 1"? I cannot get either to work.
6. mono/left and right inputs show as "none" with no other choices in the pull down -- I'm guessing this is a problem...
7. If, I switch to modular view, what should the correct flow look like? audio input 1 --> track 3 recorder --> rack 3 --> master?
-d.vyd
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Which specific MuLab version are you using?
Please make sure you have installed M7.0.36
If you already have installed M7.0.32 or up, you can quickly update this way:
http://www.mutools.com/mulab/app-patch/
Please make sure you have installed M7.0.36
If you already have installed M7.0.32 or up, you can quickly update this way:
http://www.mutools.com/mulab/app-patch/
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Does "MME Audio Output" mean input isn't supported with MME?
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
MuLab's MME interface does not support audio input.d.vyd wrote:2. MuLab --> Audio Setup --> driver type = MME Audio Output & driver = Microsoft Sound Mapper.
Cfr the docs: http://www.mutools.com/info/docs/mulab/audio-setup.html
Yes use ASIO.Are there better options?
-
- KVRist
- Topic Starter
- 219 posts since 3 May, 2016
1. I successfully upgraded from M7.0.29 to M7.0.36.
2. I switched from MME to ASIO and mulab.exe immediately stopped working.
3. Thinking whatever ASIO drivers I had were bad, I downloaded and installed Asio4All
4. mulab.exe would not restart
5. I rebooted my computer
5. I copied the original unzipped version M7.0.36 over the active version of the same application
6. mulab,exe will not restart
I cannot start the application. Please advise.
-d.vyd
2. I switched from MME to ASIO and mulab.exe immediately stopped working.
3. Thinking whatever ASIO drivers I had were bad, I downloaded and installed Asio4All
4. mulab.exe would not restart
5. I rebooted my computer
5. I copied the original unzipped version M7.0.36 over the active version of the same application
6. mulab,exe will not restart
I cannot start the application. Please advise.
-d.vyd
-
- KVRian
- 877 posts since 28 Feb, 2015 from Interstella 5555
Try a new clean installation,download the MuLab 7.0.36 package
http://www.mutools.com/mulab-downloads.html
and follow the instructions here
http://www.mutools.com/info/docs/mulab/ ... ation.html
http://www.mutools.com/mulab-downloads.html
and follow the instructions here
http://www.mutools.com/info/docs/mulab/ ... ation.html
-
- KVRist
- Topic Starter
- 219 posts since 3 May, 2016
I followed Taifunk's advice. MuLab would not start until I renamed the user directory to user_backup (instead of deleting entirely). I then re-entered my license. MyLab is running again, but I am still not able to record from my USB Microphone. I'm using Windows 10. Any help would be appreciated.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
If you're using ASIO4ALL, you must ensure the mic is plugged in before starting any ASIO application, in my experience ASIO4ALL is less forgiving about these things. (It won't recognise new devices and may crash.)
Then, check in MuLab Audio Setup and see if you can see ASIO4ALL listed. If not, then you'll need to check whether ASIO4ALL has been installed correctly and supports your hardware.
If you can see ASIO4ALL listed, then you need to select it (of course) and check that you have configured it correctly. Check both the simple and advance settings to ensure that you're only using the USB Microphone for input (assuming that's what you want) and that you've also got your motherboard audio out selected (again, assuming that's what you want).
ASIO4ALL should tell you whether it's happy with the configuration you set but its been known to crash (again, in my experience - I'm not a fan
).
Once that's done, check that MuLab can see the inputs and outputs you selected in ASIO4ALL.
Then, check in MuLab Audio Setup and see if you can see ASIO4ALL listed. If not, then you'll need to check whether ASIO4ALL has been installed correctly and supports your hardware.
If you can see ASIO4ALL listed, then you need to select it (of course) and check that you have configured it correctly. Check both the simple and advance settings to ensure that you're only using the USB Microphone for input (assuming that's what you want) and that you've also got your motherboard audio out selected (again, assuming that's what you want).
ASIO4ALL should tell you whether it's happy with the configuration you set but its been known to crash (again, in my experience - I'm not a fan
).Once that's done, check that MuLab can see the inputs and outputs you selected in ASIO4ALL.
-
- KVRist
- Topic Starter
- 219 posts since 3 May, 2016
Pljones: thank you. I'll follow your advice. Do I have other ASIO driver options? I couldn't find anything specific to my devices. My audio output is a Behringer U-Control UCA202 (USB box with headphone jack). My audio input is a audio-technica AT2005 (USB dynamic microphone).
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
If ASIO4ALL isn't solving the problem, one other option -- not for the faint-hearted -- is to use Jack for Windows to combine the two devices. It's less friendly than ASIO4ALL (and also slightly crashy, though I find it less so, though maybe I'm more patient with it). It comes with an ASIO driver called JackRouter (which is more fun than ASIO4ALL as it lets more than one ASIO application run at once).
ASIO applications generally expect to talk to a single ASIO driver and, after some negotiation, slave themselves to that driver. So you need that driver to combine your inputs and outputs. Now, as low-level hardware service routines are involved to synchronise things, you ideally want the ASIO driver to come from the device manufacturer, as they're likely to know what their hardware does and how best to handle it. But when you have discrete devices, it gets tricky.
ASIO4ALL effectively sits "on top of" lower level device drivers, rather than talking directly to the devices, as does Jack for Windows. The extra layer now also has to try to synchronise the lower level devices but it's not at the low level, so it can find its hands tied and strange things happen (like crashes...).
But unless you get a single device with inputs and outputs and ASIO support, you're basically pushing things beyond their design criteria anyway.
ASIO applications generally expect to talk to a single ASIO driver and, after some negotiation, slave themselves to that driver. So you need that driver to combine your inputs and outputs. Now, as low-level hardware service routines are involved to synchronise things, you ideally want the ASIO driver to come from the device manufacturer, as they're likely to know what their hardware does and how best to handle it. But when you have discrete devices, it gets tricky.
ASIO4ALL effectively sits "on top of" lower level device drivers, rather than talking directly to the devices, as does Jack for Windows. The extra layer now also has to try to synchronise the lower level devices but it's not at the low level, so it can find its hands tied and strange things happen (like crashes...).
But unless you get a single device with inputs and outputs and ASIO support, you're basically pushing things beyond their design criteria anyway.