MuTools

MuTools · Post by **MuTools** » Wed Nov 16, 2011 6:04 am

pljones wrote:Two more, related:
1) Several of the demo sessions cause me CPU overload. I have an AMD Phenom 9650 Quad-core running at 2.3GHz with 4GB RAM on Windows 7. Should the demos be that demanding?

The MuSynth is more demanding than Synthia, as it has more sub-modules.
But that's one of the items to be done: Optimizations.

2) Quitting with OVERLOAD on the CPU meter doesn't work ("Internal thread timeout error" or similar).

Thanks for reporting, will check.

janamdo · Post by **janamdo** » Wed Nov 16, 2011 9:22 am

pljones wrote:Two more, related:
1) Several of the demo sessions cause me CPU overload. I have an AMD Phenom 9650 Quad-core running at 2.3GHz with 4GB RAM on Windows 7. Should the demos be that demanding?

I use a amd x3 415 e , overclocked and with 4 cores ( motherboard asus )2,5 Ghz, , 4 gb ram, windows 7 ultimate 64 bit with servicepack 1
The windows experience index gives for all parts more dan 7(max 7,9) ( except for the harddisk what gives 5,9 )

All demo's are playable without cpu overload problems ..easy.. max average 40 % and i installed two cpu meters for win 7 and the processors don't work very hard

So it seems to be no problem for the quadcores and Amd 9650 quad core is faster than my quadcore?
I can do a benchmark for this ..

pljones · Post by **pljones** » Wed Nov 16, 2011 10:13 am

Jo, thanks for the replies - makes sense.

Janamdo - similar figures here, except my Graphics, which is 3.2.
Birds of Io: MULAB "Max: 118%" Avg was about 60%; task manager looks like about 60%
Wildinger: not playing, this records "Max: 44%" in MULAB if left a while... playing now gives a Max of 80% -- yesterday it was one of the ones causing overload... strange... Hm, and now I can't find one that does it...

MULAB does seem to agree with Task Manager (and Resource Monitor) in Windows.

MuTools · Post by **MuTools** » Wed Nov 16, 2011 2:08 pm

pljones wrote:but the Stand In piano (in the session) has been saved with its modules turned off. Was that intentional?

Euh, no, i first misunderstood, now i saw what you mean. Will be fixed.

Nielzie · Post by **Nielzie** » Wed Nov 16, 2011 6:18 pm

Jo, on Windows when I close M4.0.63 the GUI exits, but the MULAB.exe process does not shut down. I guess that's perhaps a bug from the GUI Window changes you did?

MuTools · Post by **MuTools** » Wed Nov 16, 2011 7:15 pm

Yes i noticed it too this afternoon.
It's when you close the last session window.
For now, best to use the Quit command instead of closing the last session window. Will be fixed in the next version.

Trancit · Post by **Trancit** » Thu Nov 17, 2011 8:06 am

One suggestion about the Supermodulator...

Could you make the nodes more visible with a different color or a black ring around them???

For example, if I open the first preset (1 bar 16th (Amp)) and want to select and edit a node at the bottom, it's a kind of a blind flight...it works by dragging a marquee around the suggested area and rightclick, where I suggest the point, but it is still only a suggestion

pljones · Post by **pljones** » Thu Nov 17, 2011 8:52 am

Yeah, whilst you can zoom in to get plenty of room and guess where the nodes are, with the full amplitude wave in that preset, the node is push off the top of the display. Either it needs to be drawn in a different colour (which would be preferable for me) or drawn "on top", so it didn't get clipped by the bounds of that part of the display.

Also, you can zoom horizontally. Being able to resize the editor window would be nice, allowing more vertical screen size to be used.

Picky: In the node editor shape drop-down, could the current shape start as selected or highlighted?

Trancit · Post by **Trancit** » Thu Nov 17, 2011 11:15 am

pljones wrote: Picky: In the node editor shape drop-down, could the current shape start as selected or highlighted?

Yes, this I would like to see in every MuLab list, either if you've loaded a sample or preset or whatever, would be very nice to see a marker or highlighted for the current loaded if you open the list again

plutonia · Post by **plutonia** » Thu Nov 17, 2011 2:18 pm

been having a play around with beta of v4 and have following comments:

initial impressions:
the synth sounds are really fantastic;this may well be the best synth i've ever heard. real depth and character to the sounds and lot of time and effort has gone in to programming them. noticed some complaiants about cpu load but i suspect that the high cpu hit is a result of the high quality of the synth sounds and number of modules/oscillators etc used to great such sonically rich synth patches. the effects are diverse and again very high quality and have only scratched the surface so far.....

issues:

1. mu lab using asio4all doesn't close down when use 'close' from 'session' menu. mu lab appears to shut down but if i open task manager i can see that mu lab is still running hence no sound from asio driver second time you load mu lab because driver still being used by first instance of mu lab. this happens if you close from 'session' menu and mu lab quits . if you 'quit' mu lab from 'mu lab' menu it's fine. thought it was just just my system cos i'm using built in soundcard on motherboard but tried on my netbook and same thing produced windows blue screen of death! also i'm not sure about usefulness of having different composition arrangments avaiable within sessions but haven't used it enough to reaslise where jo is coming from with this feature yet.

2. opening mu synth parameters to edit them (e.g oscillators etc) and midi keyboard cuts out and can't hear edits to sound until click on desktop again. sometimes works and sometimes you have to close modules you are working on to hear how edits are affecting sound and then reopen them again to continue edits.

3. the 'split' function should be destructive if required; for instance. i have a 4 bar loop. i only want i bar. i can't cut out 1 bar and copy it without the original notes from the other 3 bars appearing in the note editor. i'm mibbe missing some funtion here but this isn't something i can get on with. i realise this is same as v3 but any advice on the functionally of this would be appreciated.

4. i'm getting old and the quantise grid lines aren't dark enough for me to see unless i lean in closer to computer screen! time to see my optician.....

great upgrade jo;loads of new sounds/effects and functionailty. will keep testing and get back with any other issues or comments

MuTools · Post by **MuTools** » Thu Nov 17, 2011 4:13 pm

plutonia wrote:the synth sounds are really fantastic;this may well be the best synth i've ever heard. real depth and character to the sounds and lot of time and effort has gone in to programming them.

Special thanks to AndreasD!
He made a very nice patch collection, very inspiring to play with

1. mu lab using asio4all doesn't close down when use 'close' from 'session' menu.

Indeed, a known issue, fixed in the next version.
For now, please use MULAB -> Quit.

2. opening mu synth parameters to edit them (e.g oscillators etc) and midi keyboard cuts out and can't hear edits to sound until click on desktop again. sometimes works and sometimes you have to close modules you are working on to hear how edits are affecting sound and then reopen them again to continue edits.

A bug. Fixed in the next version.

3. the 'split' function should be destructive if required; for instance. i have a 4 bar loop. i only want i bar. i can't cut out 1 bar and copy it without the original notes from the other 3 bars appearing in the note editor. i'm mibbe missing some funtion here but this isn't something i can get on with. i realise this is same as v3 but any advice on the functionally of this would be appreciated.

Apply Part -> "Duplicate Sequence" after having split.

4. i'm getting old and the quantise grid lines aren't dark enough for me to see unless i lean in closer to computer screen! time to see my optician.....

MuLab is +-90% skinnable at this point.
I'll do my best to make it 100% skinnable.

great upgrade jo;loads of new sounds/effects and functionailty. will keep testing and get back with any other issues or comments

Thanks!

AndreasD · Post by **AndreasD** » Fri Nov 18, 2011 8:06 pm

@plutonia: Thanks for your fine words about my synth and effect patches

As Jo is busy with the development I am happy to answer questions about some 'how to', although I am currently on a business trip until later next week and not online every day.

Andreas

Trancit · Post by **Trancit** » Fri Nov 18, 2011 11:48 pm

MuLab new version: Cannot use Session>Save as... here!

The command opens the save dialog box, I can choose folder and file name, but nothing happens, it doesn't save, the save as window doesn't close, even not with cancel...

Same happens on the close dialog...

MuTools · Post by **MuTools** » Sat Nov 19, 2011 10:05 am

No probs with saving here. Note that the MuSession file is saved in a separate folder with the same name as the session in order to neatly group all audio files for that session.

Confirming the cancel bug though, that's fixed in the next version.
For now, if you wanna cancel, click browse, and cancel there.

New update coming later today.

Trancit · Post by **Trancit** » Sat Nov 19, 2011 8:26 pm

Ok,

it only works here, if I choose "Browse" to locate directory and "New file"...

It doesn't work here, if I leave the default entries on the "save as" dialog...
It doesn't work here, if I click directly in the text boxes "Folder" and "Name" to change to desired folder and filename...

MuTools

KVR Audio

M4 Test