MuLab 7.0.47

[MuTools]

I don't understand what you mean, can you pls explain in more words, sorry if i'm missing something obvious.

[MuTools]

PS: To avoid confusion: Of course i understood i must take the Patch Test preset, but i don't see what you mean with "there is a little margin of error in the parameter event generator".

[Taifunk]

OK,Forgive me if I can not explain well,if you connect a constant modulator (with 50% value) to a parameter event generator (with 50% value) and map this to a meta parameter ,finding that there is a small margin of error ,at the end the metaparamer does not correspond perfectly to 50% but 50,01%
I try to make a clearer example and upload in a few minutes.

Edit:
Ok,I try to explain
I have attached the example,when load the patch, I expect to find the value (in the pitch knob)perfectly set to 0% , but I see through the modulation monitor that is not so.
If you reset the knob(alt+ left click)the value back perfectly 0 and the modulation monitor shows no signal.
Which turns on and off the costant modulator,the problem returns.
I can not understand what causes this,I hope you can help me.

[Taifunk]

updated the previous post and added an example

[MuTools]

I still can't follow. If i open that last patch the modulation monitor says 0.0%. Not so on your system? I really don't know what you mean.

[MuTools]

Should i do something with "Patch test" in order to see a 'wrong' value?

[Taifunk]

on my system it seems not to be so when you play a note,and one of two oscillators result slightly detuned.
perhaps before I uploade the wrong patches

[MuTools]

Ah ok i see what you mean now. That's because the parameter event generator resolution is set to an even value which results in the middle value not being 'perfect'. More in detail: If the resolution is set to 4096 then this means there are 4096 values for the whole range from min to max. So that's going from 0 to 4095. So the middle value then is 2047 which is slightly off. Thus solution is to use an odd resolution value. I'll change that default value to 1001 which corresponds to the displayed values from 0.0% to 100.0% = 1001 values. But you don't have to wait for that as you can change the resolution yourself. Set it to 4097 in this case and it will work as expected.

[Taifunk]

ok!
I was really going crazy to find the cause and try to explain the problem,thanks for your patience and for helping me.
I'm trying to improve also my English but it is really tiring.
Thanks a lot Jo, problem solved I can complete my patch

[MuTools]

There is a new MuLab 7.0.31 on http://www.mutools.com/mulab-downloads.html

What's changed wrt M7.0.29:

• Ensured that the main project window fits a 1024 width screen.
• Fixed some issues in the factory library.
• Some other micro improvements.

How to update:
Install the complete M7.0.31 package and copy over your current user settings cfr
http://www.mutools.com/info/docs/mulab/ ... ation.html

[MuTools]

Note wrt the MuLab 7 test version: If you would still have projects or presets using the step sequencer saved with one of the first M7 test versions prior to M7.0.16 (dd 6 april) please make sure you resave them using a recent version (M7.0.16 or up). This is because something changed in the step sequencer file format at that time and there is some temporary upgrade code which i would like to clean up. This has nothing to do with M6, it's only related to the very first M7 test versions up to M7.0.15. Thanks! If any questions about this, just ask.

The new M7.0.31 has a special function that can search for all your project/preset files within a certain version range: Popup the command line (call it via a shortcut) and enter "list mutools files version" without the quotes. Then browse for the top folder you want to search in and set the min version to 7.0.0 and max version 7.0.15. That will give you a list of all *.mu* files in that range. If you don't have such files, then all is ok. Else then please 'upgrade' them by opening them (one by one) and saving them again. That will ensure they have the up to date format. If you have too many such files to comfortably handle this file by file, then email me and i'll give you a trick. If any questions about this, just ask. Again, this is only about project/preset files that use the step sequencer and saved with M7 test versions prior to M7.0.16. I want to make sure all test users are up to date before i clean up a piece of temporary code. Clean code is important for future developments. Thanks.

[fluffy_little_something]

Are those 7.x builds already official releases or still beta versions?

[Michael L]

still beta versions?

M7 test versions prior to M7.0.16

Test=beta

[Taifunk]

Thanks for the update,just finished converting patches and projects

[fluffy_little_something]

One still has to convert things?!