MuLab 8.0.66

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Been playing around with the beta some more. It's really fun to use the new audio stuff. For example, I turned a microwave beep loop sample into a three-part arrangement. :D

I also used some kind of computer-game-audio-drone-thingy sample as a basis for a new song. ...so it's very creative!

It still takes me a while to accomplish want I want with the easy stuff, such as dragging the end of an audio clip to just make it longer but not having the audio sample repeating (since I would need to make it longer if I want a copied sample in the second lane to be longer than the original). Maybe it's just me (?) since I normally only do sequencing and not loop-based music? Perhaps there could be right-click options in the Compose window to make these things easier - I don't know since I don't know exactly what is supposed to happen at any given instant.

For the microwave beep audio file, I wanted to loop only part of the sample. Since I'm not exactly sure of the process, I just de-activated loop snapping and set my looping markers to exactly enclose the passage in question (like at 4.144.4233 for loop start). Then I realized there is no easy way of recalling the loop start and end points, if I want to loop another part of the song and then go back to the 4.144.... point. So: perhaps an option would be handy: When right-clicking a loop start or end handle, perhaps it would make sense to have a "Insert marker at this position". (What I did now was to go to Edit and copied the values for the loop markers , created new markers, and set their values to the copied values.)

Still no bugs or crashes with the beta on my HP laptop (Win 10 64 bit). Built like a tank! :D

Keep up the great work, Jo!
Thu Oct 01, 2020 1:15 pm Passing Bye wrote:
"look at SparkySpark's post 4 posts up, let that sink in for a moment"
Go MuLab!

Post

It still takes me a while to accomplish want I want with the easy stuff, such as dragging the end of an audio clip to just make it longer but not having the audio sample repeating (since I would need to make it longer if I want a copied sample in the second lane to be longer than the original). Maybe it's just me (?) since I normally only do sequencing and not loop-based music? Perhaps there could be right-click options in the Compose window to make these things easier - I don't know since I don't know exactly what is supposed to happen at any given instant.
Pls see http://www.mutools.com/mulab/m8/docs/mu ... ences.html

Then what exactly is unclear?
For the microwave beep audio file, I wanted to loop only part of the sample. Since I'm not exactly sure of the process, I just de-activated loop snapping and set my looping markers to exactly enclose the passage in question (like at 4.144.4233 for loop start). Then I realized there is no easy way of recalling the loop start and end points, if I want to loop another part of the song and then go back to the 4.144.... point. So: perhaps an option would be handy: When right-clicking a loop start or end handle, perhaps it would make sense to have a "Insert marker at this position". (What I did now was to go to Edit and copied the values for the loop markers , created new markers, and set their values to the copied values.)
I'm not sure if i understand this description but maybe you're looking for the "Attach To Marker" context function in the Start-Loop-End value displays?
Note that the Start-Loop-End position can be defined in 2 different ways: Using a straight sample index or using a marker. For all details please see this doc page: http://www.mutools.com/mulab/m8/docs/co ... -positions

Does this help?

Post

Thanks, away from MuLab now but I am sure the docs will help! :)
Thu Oct 01, 2020 1:15 pm Passing Bye wrote:
"look at SparkySpark's post 4 posts up, let that sink in for a moment"
Go MuLab!

Post

I don't know whether it's been mentioned already, but I can't seem to find the sample event specific context menu functions. Am I being completely stupid or is this a bug?Image

Thanks, love what you're doing.

Post

Right-click a sample event instead of the editor background.

Post

M8.0.51 is available in http://www.mutools.com/mulab/m8/

What's changed:
  • Fixed a bug that could cause numeric values to go up/down when pressing keys other than plus/minus.
  • Audio Sequence Editor -> Right-click fade in/out point: Reset Fade now also resets the fade curve.
  • Upon startup MuLab now checks whether it's installed in a writable folder, if not a message is shown and MuLab quits.
  • Clicking a on-screen piano keyboard now accurately plays the very note you click on ie. improved the white <> black keys separation.
  • Upon removing a sequence part from a composition, or undoing a split, there could be hanging notes. Fixed.
  • Sequence Player module: Upon changing the tempo factor there could be hanging notes. Fixed.
  • In menus and tree lists, pressing the Arrow Left key now also closes the current sub-group even for non group items. This makes it more easy to navigate a tree list using keys only.
  • The Top Panel Display Color preference was not working anymore. Fixed.
  • Other small improvements.
How to update:
Windows: Replace the current MuLab.exe and MuLab.ID by the new versions.
MacOS: Replace the current MuLab.app by the new version.

Note: In the Step Sequencer the Tempo Factor has been removed. If you would have saved M8 projects that use a Step Sequencer with a Tempo Factor different from 100% then please use M8.0.50 to set this back to 100% and resave the project.

Post

M8.0.52 is available in http://www.mutools.com/mulab/m8/

What's changed:
  • Fixed a bug in M8's multi-core processing engine which caused that multi-core processing was not always optimal resulting in possible higher cpu usage than expected / than M7.
  • The loop button in the transport panel was not properly updated when doing eg. "Loop Selected Parts".
How to update:
Windows: Replace the current MuLab.exe and MuLab.ID by the new versions.
MacOS: Replace the current MuLab.app by the new version.

Post

Thanks :tu:

Post

mutools wrote: Sun Mar 24, 2019 7:45 pm Right-click a sample event instead of the editor background.
Ah, ok. I had right click to delete notes on, is there a way of accessing this menu with that functionality enabled at the moment? That would be handy.

Post

No such way. A right-click can only do one thing. Maybe that preference should be changed in "Right-click start/end of notes = Delete notes". That way right-clicking the start/end of a note will delete it, right-clicking the body of a note pops up its context menu. What do you think?

Post

Can you guys please do this test wrt the cpu usage of M7.7.4 vs M8.0.52:

1) Make sure you have a M7.7.4 installation folder and a M8.0.52 installation folder.
2) Make sure both these installations use the exact same audio setup and with multi-core enabled.
3) Open the "Pure" demo and play bars 33 -> 49 ie. the last 16 bars before the break.
4) Click the cpu meter so it shows "Avg=...%" and watch the average cpu usage.

Post the average cpu weight for M7 and for M8.

It's essential to use the exact same audio setup: That's same audio device + same samplerate + same blocksize + same Num Audio Processor Threads!

It's important to use the latest M8.0.52 as it contains a fix wrt multi-core processing.

I'm curious if there are still systems where M8 clearly use more cpu than M7.
It's not about 1% more or less, but a clear difference of many %.

Thanks.

Post

Both run between 30% and 40% average.
(Asio4All 512/44.1K, 2 threads(auto))

Post

Thx SQ4! So no real difference between M7 and M8, right?

Post

mutools wrote: Wed Mar 27, 2019 11:55 am Thx SQ4! So no real difference between M7 and M8, right?
Indeed, both run equally smooth.

Btw, fantastic job wrt timestretch/pitchshift/audio sequences. Top quality, like usual! :clap:

Post

Thanks man!

Post Reply

Return to “MuTools”