MuLab 9.0.59 App + Plugin

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

Post

The exponential curve indeed is not symmetric.

Post

Is it so by design and taken from maths? And how could I match the 2nd marked curve to the 1st one? I managed to achieve good result with the symmetric one, but I'm curious if similar result can be obtained with the exponential curve.

Post

I'll also drop an idea, not really for M9, but I'll leave it here because I don't feel like making another thread: LFO module simplification and improvements:
-instant editor like multi-point envelope (gets rid of extra click as well as another window), it would probably turn it into more of a horizontal module
-display name of the module depending on the chosen MuWaveShape

Post

humanboeing wrote: Mon Jun 27, 2022 4:03 pm Is it so by design and taken from maths?
Yes.
And how could I match the 2nd marked curve to the 1st one? I managed to achieve good result with the symmetric one, but I'm curious if similar result can be obtained with the exponential curve.
That's what the Symmetric curves are for.

The M9 Curve sub-system already is very usable and performant.
But that doesn't mean it will not evolve further towards even more flexibility (eg more options for symmetric curves, options to combine curves, ...). To be continued.

Post

humanboeing wrote: Mon Jun 27, 2022 1:34 pm Exponential curve inconsistency: values 13 vs -13
"Analogue-ised"?

Post

pljones wrote: Mon Jun 27, 2022 4:35 pm
humanboeing wrote: Mon Jun 27, 2022 1:34 pm Exponential curve inconsistency: values 13 vs -13
"Analogue-ised"?
Hm?

Post

I mean the shape is intentional, like Jo says - an analogue synth's exponential curve would never be perfect, although I've not seen a sample of such a waveform to compare.

Post

I prefer to use the wobble generator for analogue-ish magic :)

Post

humanboeing wrote: Tue Jun 28, 2022 6:18 pmI prefer to use the wobble generator for analogue-ish magic :)
Yeah, after I posted, I thought I'd probably add wobble, too...

Post

Would it be possible to have the note action map take its timeline values from the cursor and/or loop markers, instead of defaulting to 1.1.000 every time, when adding a new note action?

Proposal: if I choose "Play Timeline" then it would use the start value of the play cursor. If I choose "Loop Timeline" then it would set the start and end values to match the current loop markers.

That would make it a lot faster / easier to set up new note actions.

Post

Hi Jo,

The AppMovie record is behaving strangely... I get the usual Avi and Wav files but the Wav file looks bad:

Code: Select all

peter@fs-peter:/mnt/content/space/peter/Shared Projects/MuTools 9 User/AppMovies$ hd !$ | head
hd AppMovie-20220709-132136.Wav | head
00000000  f0 27 b7 03 4e 02 00 00  20 40 6a 0d 4e 02 00 00  |.'..N... @j.N...|
00000010  10 00 00 00 01 00 02 00  80 bb 00 00 00 ee 02 00  |................|
00000020  04 00 10 00 64 61 74 61  00 13 e4 0e 00 00 00 00  |....data........|
00000030  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
07db2c20  00 00 00 00 00 00 00 00  00 00 00 00 13 00 0b 00  |................|
07db2c30  29 00 17 00 40 00 24 00  2e 00 1a 00 05 00 03 00  |)...@.$.........|
07db2c40  d0 ff e5 ff 90 ff c2 ff  35 ff 8f ff d5 fe 59 ff  |........5.....Y.|
07db2c50  70 fe 22 ff 03 fe e5 fe  96 fd a8 fe 2f fd 6f fe  |p."........./.o.|
07db2c60  d1 fc 3a fe 79 fc 0a fe  3b fc e7 fd 04 fc c9 fd  |..:.y...;.......|
A good wav file should have a RIFF WAV header before the data chunk. This could be because the movie recorder write failed -- but the header can be written with an indeterminate size and most editors can cope with that.

Code: Select all

peter@fs-peter:/mnt/content/space/peter/Shared Projects$ hd 'MuTools 9 User/Mux/Instruments/Reincke/VibraphoneJR/samples/VibraphoneJR_E3.wav' | head
00000000  52 49 46 46 a8 51 02 00  57 41 56 45 66 6d 74 20  |RIFF.Q..WAVEfmt |
00000010  10 00 00 00 01 00 01 00  44 ac 00 00 cc 04 02 00  |........D.......|
00000020  03 00 18 00 64 61 74 61  68 50 02 00 be 00 00 2b  |....datahP.....+|
00000030  00 00 19 00 00 77 fe ff  a8 fb ff cf fa ff e8 f9  |.....w..........|
00000040  ff c1 f8 ff b6 f8 ff 6e  fa ff e5 fd ff 44 01 00  |.......n.....D..|
00000050  92 03 00 54 05 00 40 06  00 26 08 00 be 0a 00 da  |...T..@..&......|
00000060  0b 00 30 0d 00 36 0f 00  7c 11 00 2c 14 00 73 17  |..0..6..|..,..s.|
00000070  00 88 1e 00 e3 29 00 86  36 00 ce 44 00 b9 54 00  |.....)..6..D..T.|
00000080  1b 64 00 13 71 00 e9 7d  00 e0 88 00 c9 8f 00 05  |.d..q..}........|
00000090  94 00 72 96 00 40 99 00  54 99 00 69 93 00 24 92  |..r..@..T..i..$.|
The AVI seems corrupt, too -- whilst the header is intact, it doesn't play. I couldn't immediately recreate the problem (it was a long, rather intricate movie... that'll teach me to record each action as a separate one and allow time for stitching things together smoothly...).

App logs attached. Nothing for the time period in Windows Event Viewer. Still looking for any crash dumps.
You do not have the required permissions to view the files attached to this post.

Post

OK, just something "untidy" I spotted whilst using the app. This doesn't happen in MuLab 8.

Dragging the right-hand edge leftwards until the window controls slide behind the "fixed" MuLab controls. In MuLab 8, the window controls are what take precedence.
You do not have the required permissions to view the files attached to this post.

Post

pljones wrote: Sat Jul 09, 2022 12:58 pm Hi Jo,

The AppMovie record is behaving strangely... I get the usual Avi and Wav files but the Wav file looks bad:

Code: Select all

peter@fs-peter:/mnt/content/space/peter/Shared Projects/MuTools 9 User/AppMovies$ hd !$ | head
hd AppMovie-20220709-132136.Wav | head
00000000  f0 27 b7 03 4e 02 00 00  20 40 6a 0d 4e 02 00 00  |.'..N... @j.N...|
00000010  10 00 00 00 01 00 02 00  80 bb 00 00 00 ee 02 00  |................|
00000020  04 00 10 00 64 61 74 61  00 13 e4 0e 00 00 00 00  |....data........|
00000030  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
07db2c20  00 00 00 00 00 00 00 00  00 00 00 00 13 00 0b 00  |................|
07db2c30  29 00 17 00 40 00 24 00  2e 00 1a 00 05 00 03 00  |)...@.$.........|
07db2c40  d0 ff e5 ff 90 ff c2 ff  35 ff 8f ff d5 fe 59 ff  |........5.....Y.|
07db2c50  70 fe 22 ff 03 fe e5 fe  96 fd a8 fe 2f fd 6f fe  |p."........./.o.|
07db2c60  d1 fc 3a fe 79 fc 0a fe  3b fc e7 fd 04 fc c9 fd  |..:.y...;.......|
A good wav file should have a RIFF WAV header before the data chunk. This could be because the movie recorder write failed -- but the header can be written with an indeterminate size and most editors can cope with that.

Code: Select all

peter@fs-peter:/mnt/content/space/peter/Shared Projects$ hd 'MuTools 9 User/Mux/Instruments/Reincke/VibraphoneJR/samples/VibraphoneJR_E3.wav' | head
00000000  52 49 46 46 a8 51 02 00  57 41 56 45 66 6d 74 20  |RIFF.Q..WAVEfmt |
00000010  10 00 00 00 01 00 01 00  44 ac 00 00 cc 04 02 00  |........D.......|
00000020  03 00 18 00 64 61 74 61  68 50 02 00 be 00 00 2b  |....datahP.....+|
00000030  00 00 19 00 00 77 fe ff  a8 fb ff cf fa ff e8 f9  |.....w..........|
00000040  ff c1 f8 ff b6 f8 ff 6e  fa ff e5 fd ff 44 01 00  |.......n.....D..|
00000050  92 03 00 54 05 00 40 06  00 26 08 00 be 0a 00 da  |...T..@..&......|
00000060  0b 00 30 0d 00 36 0f 00  7c 11 00 2c 14 00 73 17  |..0..6..|..,..s.|
00000070  00 88 1e 00 e3 29 00 86  36 00 ce 44 00 b9 54 00  |.....)..6..D..T.|
00000080  1b 64 00 13 71 00 e9 7d  00 e0 88 00 c9 8f 00 05  |.d..q..}........|
00000090  94 00 72 96 00 40 99 00  54 99 00 69 93 00 24 92  |..r..@..T..i..$.|
The AVI seems corrupt, too -- whilst the header is intact, it doesn't play. I couldn't immediately recreate the problem (it was a long, rather intricate movie... that'll teach me to record each action as a separate one and allow time for stitching things together smoothly...).

App logs attached. Nothing for the time period in Windows Event Viewer. Still looking for any crash dumps.
I checked the internal screen video recorder in both M9.0.42 32 bit and 64 bit and all works as expected here.

Post

pljones wrote: Sat Jul 09, 2022 2:11 pm OK, just something "untidy" I spotted whilst using the app. This doesn't happen in MuLab 8.

Dragging the right-hand edge leftwards until the window controls slide behind the "fixed" MuLab controls. In MuLab 8, the window controls are what take precedence.
Practical solution for now: Right-click the window border as all the window functions like close, maximize, edit size etc are also available via right-click window border.

Post

mutools wrote: Sat Jul 09, 2022 2:22 pmPractical solution for now: Right-click the window border as all the window functions like close, maximize, edit size etc are also available via right-click window border.
It's not generally a problem (just when I was trying to get this video done).

Post Reply

Return to “MuTools”