MuLab 5.0.31 Test

[MuTools]

It does answer it. although you are right. the function should perform a bit better..

Please email me some wave file examples that are analyzed poorly.

[Trancit]

It does answer it. although you are right. the function should perform a bit better..

Please email me some wave file examples that are analyzed poorly.

Not Stephan here, but emailed anyway

[MuTools]

MuLab 5.0.29 is available as an app/exe update in http://www.mutools.com/mulab/everest

What's changed:

• Fixed a potential crash bug when deleting a sequence while previewing it.
• Browser: "Where" popup list now includes the global favorite folders. (managed via the file/folder selector)
• Windows can be dragged above the top of the screen, if you want. This might be necessary when having large editor windows on small screens.
• ASIO setup: When there were more inputs/outputs than could be displayed on the screen, there was a practical prob. Fixed.
• Fixed a scrolling problem in the sequence editor.
• New preference: DragDoubleClickDetectorMoveThreshold. By default that's 5.
• Fixed an issue in the VST plugin manager when renaming VSTs.
• Finetuned graphics.

By only applying the app/exe update there is a little graphical mismatch in the Audio Recording Setup panel, nothing serious though. That will be automatically fixed when the new full package is available. But for now you can fix it by updating the AudioFileRecorderEditor.Xml file in the graphics folder by the one in the zip in the everest webfolder. It's not a necessary action though.

Cheers!

[Stephan326]

Don't know for sure if the problem was supposed to be addressed in this update. so far ok. One thing. When I try to chage the tempo of the project it defaults to default tempo(120) on bar 1.

[torgo]

I disagree. When I bought my first keyboard, an XP-60, I knew nothing about making music, and I do mean NOTHING. I switched Quantise off as I thought it'd be more 'natural' but I quickly learned it's a necessary tool, for beginners especially.

It would be easier for advanced users to create a template than a beginner.

Ummm... I'm guessing you (and the later +1 guy) didn't see or read my earlier post. I never said anything about quantization being bad, that beginners shouldn't use it, or that Jo should remove it from MuLab. You missed the point entirely.

Jo wants to keep MuLab as easy and obvious as possible and occasionally asks for suggestions along those lines. So I'm suggesting that MuLab needs more and higher profile documentation (specifically, a section that you can see in the table of contents) about quantization. I'm also noting that without that documentation, it would be better to start with quantization set to No Grid and have new users turn it on rather than the other way around.

Why would that be a problem for you? You know how to turn it on, change the grid settings, and save a template with your own preferences for quantization, right?



On the other hand, my suggestion is based on a real, current example.

A new user who got his first music computer for Christmas this year found that his first recordings in MuLab 4 Free got messed up while his recordings in Sonar X1 LE came out right.

So now he's watching the Sonar tutorial vids and getting familiar with that program instead of MuLab.

If it had been more obvious in the documentation why MuLab had altered his recordings, or if the auto-quantize had initially been off, he'd likely be spending his time with MuLab rather than Sonar.

And that means Jo has probably lost a sale, as the kid will be getting either the full version of MuLab 5 or a virtual instrument for his birthday, depending on which workstation he prefers. Once he gets comfortable with Sonar, he's not likely to pass up a good VI in favor of a second workstation.

[MuTools]

Don't know for sure if the problem was supposed to be addressed in this update.

Which problem?

When I try to chage the tempo of the project it defaults to default tempo(120) on bar 1.

Could it be that you loaded a MIDI file and have a tempo event on bar 1. Right-click the tempo -> Edit Tempo Changes.

[MuTools]

MuLab 5.0.30 is available as an app/exe update in http://www.mutools.com/mulab/everest

What's changed:

• Fixed a problem with the Where field in the browser.
• Fixed a problem when using < or > as shortcut keys.
• Shortcuts editor -> Specific -> Some groups contained double entries. Tuned.

[sl23]

@ torgo

sorry but you are the one that misunderstands. You suggested mulab by default sets the quantise off. But as i explained its a necessary tool even for beginners. And please dont accuse me of not reading posts properly when its you that doesnt, if you did you'd know that the '+1 guy' you mentioned was in fact Jo!

I also didnt accuse you of saying quantise was bad or it should be removed! Whered you get that from?

I agree more info in the docs is a good idea but not your suggestion of it being switched off by default. Just my opinion thats all.

Its only when we face problems do we learn to overcome them. It forces learning onto us. If a new user faced the problem of quantisation without knowing what it is causing the issue then im sure the forum would help out

For someone to give up on mulab because they couldnt turn quantise off is just plain stupid. Mulab is easy fast and I bet far better than Sonar.

[robenestobenz]

Like Torgo, I was also confused when I first tried MuLab that my MIDI wasn't being recorded as I performed it (auto-quantize being on by default). I see you had the opposite experience, sl23. What are other users' experiences with this?

Browser: "Where" popup list now includes the global favorite folders. (managed via the file/folder selector)

Thanks Jo! Nice little timesaver.

[sl23]

Actually, no, I didn't I was confused too. My point is that quantise is VERY useful and the fact that it wasn't recording how I wanted made me investigate the issue which led to me learning what quantise is. Which is a good thing, isn't it? If it's switched off new users not knowing what it is won't even know it exists.

I'm far from being even an 'intermediate' musician, but I understand the concept of quantise and how to use it. I've only been dabbling with music now and then for the last 10 years, so I'm really very much a novice still. I bought an XP-60 without even knowing what a sequencer was or even a quarter note! I learnt how to program that sequencer and play a little. Anyone wanting to get into music needs to know what these functions are if they've got any hope of making music. If you're new isn't quantise a necessity? Could you play with perfect timing the first time you recorded into a sequencer? I seriously doubt it. And that's why, IMO, quantise should be on by default.

Considering how accessible it is to change it, I don't see the problem it being on by default?

Like I said, it's easier for advanced users to create a template than beginners. Once a template is made there's no problem is there? It's easier for beginners to learn hot to turn off quantise than to learn how to make a template, isn't it?

[pljones]

Actually, no, I didn't I was confused too. My point is that quantise is VERY useful and the fact that it wasn't recording how I wanted made me investigate the issue which led to me learning what quantise is. Which is a good thing, isn't it? If it's switched off new users not knowing what it is won't even know it exists.

If you don't need it, why force knowledge on someone? I don't like software that thinks it knows better than I do. That's just bad manners, in my opinion. I don't like quantise ever... When I needed to learn about it, I went looking. I'd rather work that way: learn when I need the knowledge rather than be forced into a situation and have to fight my way out.

Considering how accessible it is to change it, I don't see the problem it being on by default?

Hopefully the above helps. I'll just add that the problem is that it causes unexpected behaviour. You record something in audio and play it back, it sounds like you played it. You record something in MIDI and play it back and... well, it's sounds completely messed up if your timing isn't great and most likely not like what you played. So your first thought is that the software can't handle MIDI very well. Lost sale.

It's easier for a more advanced user to create a template, if they want quantise on by default. Once a template is made, there's no problem, is there?

[EvilDragon]

I disliked the quantized MIDI recording by default. Not the usual thing that should be enabled by default in a DAW, IMHO.

[sl23]

@pljones

Thanks you made a good point there. But if you're thinking that software thinks it knows better than you, then I think you need get some professional help

I agree sort of about the 'Lost sale', but if that were me, I'd think it was me lacking, not the program. I mean, if you're advanced you simply know, if you're a beginner, then you should have humility to think YOU'RE in error not the program!

Touche!

[pljones]

I mean, if you're advanced you simply know, if you're a beginner, then you should have humility to think YOU'RE in error not the program!

People always think they (a) know more than they do and (b) know better than a machine... So it's up to the programmer to realise this and cater for people who haven't used a computer for a particular task before, if they're aiming for that market. Someone who's recorded almost anything on any medium is going to be confused, at least, when the computer decides - without their instruction - to rearrange what they recorded... That's not about humility. OK, I guess there's a generation that really has no idea how to spell and relies on auto-complete or predictive texting to do it for them - maybe they'll understand what's going on. Unlike auto-complete and predictive text, however, you don't get the interaction -- it's not until after you've experienced yourself do one thing that you find out that the computer has understood you to mean something completely different.

[TheKid]

First start: downloaded the 5.30 version. 1.6 Mb? Is that all? Noone told me I had to download the previous version and update that one. Ok, no problem. Program running, started scanning for VSTs. When finding the dll for my NI Maschine the scanning froze for a moment, then disabled all USB devices. Mouse, keyboard, audio interface... just everything. Well, the internal keyboard and mouse (I'm using a laptop) still worked. The VST scanning was completed. I thought rebooting would be a good idea since replugging the USB-devices didn't work at all. So shutdown, blue-green shutdown screen where that nice windows 7 moving circle appears and nothing happens. After 5 minutes I had to turn it off via 5 sec power button. That's not too nice. Looks like a windows service crashed (for USB devices maybe?) and it couldn't shutdown. This never happened before. After booting again it all seems fine. Going on.