MuLab 6.5.29 released
-
- KVRAF
- Topic Starter
- 13868 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- 3207 posts since 17 Apr, 2010 from Slovenia
http://www.beatassist.eu/mantra-evo.html
...just in case you want to confirm this to be true! I'm starting to feel like an idiot here.
...just in case you want to confirm this to be true! I'm starting to feel like an idiot here.
-
- KVRAF
- Topic Starter
- 13868 posts since 24 Jun, 2008 from Europe
What exactly do u want me to confirm?Taron wrote:...just in case you want to confirm this to be true!
-
- KVRAF
- 3207 posts since 17 Apr, 2010 from Slovenia
The phenomenon of using Mantra Evo, which creates a second automation track as you record... in other words: In case you are losing all faith in my feedback, this could be a way for you to regain some faith in me again. 
Naturally, if no faith is lost, it won't matter for you to confirm it. Unless the reason for no loss of faith would be that there was no faith left to begin with, haha...
Naturally, if no faith is lost, it won't matter for you to confirm it. Unless the reason for no loss of faith would be that there was no faith left to begin with, haha...
-
- KVRAF
- Topic Starter
- 13868 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- 3207 posts since 17 Apr, 2010 from Slovenia
-
- KVRAF
- Topic Starter
- 13868 posts since 24 Jun, 2008 from Europe
New MuLab 6.5.15 test version in http://www.mutools.com/forsythia
Latest changes:
OSX: Simply replace the MuLab.app by the new version.
Windows: Simply replace the MuLab.exe + MuLab.ID files by the new versions.
How to upgrade from earlier versions eg M6.4: Make a full new install from the M6.5.7 package cfr the info on
http://www.mutools.com/info/docs/mulab/ ... ation.html
Then apply the new M6.5.8 app patch.
Latest changes:
- Multi-Wave Oscillator: New "Multi-Waveform CPU-RAM Usage" preference which allows you to better balance between CPU and RAM usage. Until now it was internally working with the "Rather CPU Based" setting. Now if you switch it to "Rather RAM Based" it will make a serious difference wrt CPU usage. If you chose for "Rather RAM Based" then best is to set it to "Rather RAM Based 2", it will result in better sound, but will also eat some more RAM. For the very best sound quality, "Rather CPU Based" still is the best choice, though difference with "Rather RAM Based 2" may be small.
- When the "Slider Size" was set to a specific value, and then the parameter type was switched to Maxi or Mini Knob, the knob size was not as intended. Fixed.
- For horizontal sliders the "Slider Size" has been replaced by "Name Size" so that horizontal sliders can be aligned.
- Added "Copy Size" and "Paste Size" functions in the properties panel options menu.
- The common Shape and Wave Back/Fore colors were not properly initialized. Fixed.
- Waveform and LFO shape Back/Fore colors can also be defined per component. If set to none, the respective common front panel color is used. If that's set to none the back color is blackish, the for color is the global user defined "Top Color".
- Fixed a bug that made certain existing front panels to not properly show up.
OSX: Simply replace the MuLab.app by the new version.
Windows: Simply replace the MuLab.exe + MuLab.ID files by the new versions.
How to upgrade from earlier versions eg M6.4: Make a full new install from the M6.5.7 package cfr the info on
http://www.mutools.com/info/docs/mulab/ ... ation.html
Then apply the new M6.5.8 app patch.
-
- KVRAF
- 1925 posts since 29 Mar, 2013
Hi Jo, was wondering if it would be better to have the MFO ram/cpu setting within each MFO individually so one could tailor presets if more than one MFO is used per preset, or is that not possible ?
Im not complaining, just thinking
Thanks
Im not complaining, just thinking
Thanks
Beauty is only skin deep,
Ugliness, however, goes right the way through
Ugliness, however, goes right the way through
-
- KVRAF
- 3207 posts since 17 Apr, 2010 from Slovenia
It's not individual? Oh...ya, sorry, I didn't get to check, yet. and, please, consider this:
+1
+1
-
- KVRAF
- Topic Starter
- 13868 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- 3207 posts since 17 Apr, 2010 from Slovenia
I'd imagine it depends on what you're doing, you know.
Some MFOs may need less iterations and could well just go through RAM, while others might need more steps...
I think, ideally you would set a default and could change it individually, if need be?!
Some MFOs may need less iterations and could well just go through RAM, while others might need more steps...
I think, ideally you would set a default and could change it individually, if need be?!
-
- KVRian
- 1451 posts since 4 Oct, 2012 from Utah
Synthmaster has different render quality settings. It has a default but allows users to select a quality per-preset/instance.
Let's take a bassline into example. You create a nice patch and because it's relatively simple, you want to run it more on CPU as you want high quality and keep your RAM open for other MFOs such as...
A really complex pad that has 3-5 MFO's off being modulated and have unisono applied. Having this on CPU is a terrible idea as you may end up maxing it out with some basic polyphony. Thus you want it more ram based.
It lets users have a better balance on how resources are manages during playback.
-----
A semi-unrelated idea for users who are going to RAM over CPU for running MFO live. While working in the session, have it more on ram. While rendering, have it more on CPU as you don't need live playback. That way your final render is nice, and while you work on the session, you can still work without having to raise your buffer to high degrees
Dakkra
Let's take a bassline into example. You create a nice patch and because it's relatively simple, you want to run it more on CPU as you want high quality and keep your RAM open for other MFOs such as...
A really complex pad that has 3-5 MFO's off being modulated and have unisono applied. Having this on CPU is a terrible idea as you may end up maxing it out with some basic polyphony. Thus you want it more ram based.
It lets users have a better balance on how resources are manages during playback.
-----
A semi-unrelated idea for users who are going to RAM over CPU for running MFO live. While working in the session, have it more on ram. While rendering, have it more on CPU as you don't need live playback. That way your final render is nice, and while you work on the session, you can still work without having to raise your buffer to high degrees
Dakkra
Software portfolio
M.N.I.E - soon to be my musical portfolio
Hey, I'm Eurydice(Izzy for short) - she/her
M.N.I.E - soon to be my musical portfolio
Hey, I'm Eurydice(Izzy for short) - she/her
-
- KVRAF
- Topic Starter
- 13868 posts since 24 Jun, 2008 from Europe
New MuLab 6.5.16 test version in http://www.mutools.com/forsythia
Latest changes:
OSX: Simply replace the MuLab.app by the new version.
Windows: Simply replace the MuLab.exe + MuLab.ID files by the new versions.
How to upgrade from earlier versions eg M6.4: Make a full new install from the M6.5.7 package cfr the info on
http://www.mutools.com/info/docs/mulab/ ... ation.html
Then apply the new M6.5.8 app patch.
Latest changes:
- The "TanH Distortion" module has been expanded to a more flexibel "Amp. Distortion" module.
It now includes a customizable curve display, which also makes it visually more clear how the distortion works. - Fixed a alpha-value related bug in the color picker.
- Fixed an issue in the MultiMode and TF Lowpass filters wrt cutoff frequency and key tracking.
This fix ensures that even low keys get the highest possible cutoff frequency.
OSX: Simply replace the MuLab.app by the new version.
Windows: Simply replace the MuLab.exe + MuLab.ID files by the new versions.
How to upgrade from earlier versions eg M6.4: Make a full new install from the M6.5.7 package cfr the info on
http://www.mutools.com/info/docs/mulab/ ... ation.html
Then apply the new M6.5.8 app patch.
-
- KVRAF
- Topic Starter
- 13868 posts since 24 Jun, 2008 from Europe
Without going into too much detail: A bass sound will use less RAM anyway so it's still ok to choose "Rather RAM based". Anyway, i'll keep the idea of choosing it per patch and/or add more cpu-ram choices on the wishlist.dakkra wrote:Synthmaster has different render quality settings. It has a default but allows users to select a quality per-preset/instance.
Let's take a bassline into example. You create a nice patch and because it's relatively simple, you want to run it more on CPU as you want high quality and keep your RAM open for other MFOs such as...
A really complex pad that has 3-5 MFO's off being modulated and have unisono applied. Having this on CPU is a terrible idea as you may end up maxing it out with some basic polyphony. Thus you want it more ram based.
It lets users have a better balance on how resources are manages during playback.
-
- KVRAF
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
What does this mean for how it effects the sound exactly?mutools wrote: [*]The "TanH Distortion" module has been expanded to a more flexibel "Amp. Distortion" module.
It now includes a customizable curve display, which also makes it visually more clear how the distortion works.