Linux

[bibz1st]

I recently installed linux mint on an older laptop, not really used it in anger yet, it looks nice but reading some facebook groups it seems there is a lot of command line stuff, to do what, I dont know but coming from Windows that sounds a bit off-putting, is that really the case or am I reading it wrong ?
If I am wrong then I will persevere with it.
Thanks

[pljones]

Probably best to look in the Linux DAW thread.

[THinker1987]

I recently installed linux mint on an older laptop, not really used it in anger yet, it looks nice but reading some facebook groups it seems there is a lot of command line stuff, to do what, I dont know but coming from Windows that sounds a bit off-putting, is that really the case or am I reading it wrong ?
If I am wrong then I will persevere with it.
Thanks

How i remember it is not possible to switch audio sample rate to 44100 on latest version of Mutools Mulab

[4u610h346]

How i remember it is not possible to switch audio sample rate to 44100 on latest version of Mutools Mulab

Are you saying this is a Linux issue? Are you using WineASIO? Or just Wine and PulseAudio/Alsa? If you aren't using WineASIO, you probably should. Then Mulab will use whatever sample rate you have set in Jackd or pipewire. It will use 44100, but if you don't have that set in MuLab settings, it will still use 44100 but complain that this isn't what you have set in MuLab's audio configuration.

You can even change the sample rate, without restarting MuLab. Anytime you go to "Audio Settings" it stops the MuLab audio engine. During this state, you can stop/start/restart/reconfigure Jackd/pipewire to whatever you want. Then select the same settings and accept them in MuLab. Once audio settings are accepted, MuLab will start the audio engine and reconnect with Jackd/Pipewire.

I have no problem using 44100, if I want to.

[THinker1987]

How i remember it is not possible to switch audio sample rate to 44100 on latest version of Mutools Mulab

Are you saying this is a Linux issue? Are you using WineASIO? Or just Wine and PulseAudio/Alsa? If you aren't using WineASIO, you probably should. Then Mulab will use whatever sample rate you have set in Jackd or pipewire. It will use 44100, but if you don't have that set in MuLab settings, it will still use 44100 but complain that this isn't what you have set in MuLab's audio configuration.

You can even change the sample rate, without restarting MuLab. Anytime you go to "Audio Settings" it stops the MuLab audio engine. During this state, you can stop/start/restart/reconfigure Jackd/pipewire to whatever you want. Then select the same settings and accept them in MuLab. Once audio settings are accepted, MuLab will start the audio engine and reconnect with Jackd/Pipewire.

I have no problem using 44100, if I want to.

I used WineAsio,Mutools 9 version on Bodhi Linux .I didnot check Mutools Mulab 10th version,so maybe switching 44100 works again

[audiojunkie]

Mulab 10 works better in Linux with WINE. It was specifically tested and improved for Linux. OldCastle and Jo worked on it together.

[4u610h346]

I used WineAsio,Mutools 9 version on Bodhi Linux .I didnot check Mutools Mulab 10th version,so maybe switching 44100 works again

You should test version 10 (at least the demo). If you still can't achieve 44100, then something is wrong somewhere.

I can vouch for Luna and MuLab v1 through v10. They have all achieved 44100.

If you can use 44100 with Jackd/Pipewire, then there should not be an issue with MuLab.

I'm assuming native Linux software has worked, with 44100? You may need to check with your audio device. It may not be "Hardware" capable of 44100. So, when setting applications to 44100, they may work due to software resampling. In this case, that would only work in a non (Wine)ASIO mode.

You could try the other sound engine options (MME maybe/no Jackd or Pipewire), and see that 44100 is possible. It will likely be resampled, by ALSA/(Pulseaudio?), but shows that the issue is elsewhere.

One way to find out what rates your hardware supports, is by opening a terminal.

Code: Select all

#cd /proc/asound/card0
#cat codec#0|grep rates

You may need to adjust card0 and codec#0, for what is available in your folder/system.

Use the ls command in the asound and card[n] folders.

More then likely, the second output will be the telling one.
You can #cat id, in each card[n] folder, if you have more than one audio device in your system. This way you can make sure its the right card.

You can omit the above "|grep rates", if you want the full output. If your terminal does not have a scroll bar, you may need to use SHIFT+PGUP/PGDN to scan through it.

If indeed your PCM output supports 44100, then there is likely a limiting Linux side configuration somewhere.

If v10 does solve your issue, it may be safe to ignore all of this; as v10 is the way forward, anyway. Having tested every "Final" MuLab version, I can say that each iteration is superior to the previous.