Several feature requests (and one bug?)

[Reincke]

Mentioned a long time ago here are several further feature requests (and btw one minor bug report).

MuLab:
- Event editor: editing curves similar to automation parts
- Minimize rack desk and virtual MIDI keyboard to MuLab's "task bar"
- Usability in dialogs: switch to next input field with tab key
- Mixdown: mixdown also (!) between 2 configurable locators instead of loop start/end.
(http://www.kvraudio.com/forum/viewtopic.php?t=379239)
- Sample player: second loop locator (sample start - loop start - loop end - sample end)
- Sample player: round-robin-scheduler
- or alternatively: support of sfz-files (without separate vst)
- Event editor: switch from curve to bar mode for all parameters / controllers
(http://www.kvraudio.com/forum/viewtopic.php?t=359873)
- Preset: any kind of indicator showing that a preset has been changed since preset load
- Modular Editor: easier delete of several modules (via multiple selection)
- More support for backward played samples (start of sample playing could be calculated for percussive samples)
(http://www.kvraudio.com/forum/viewtopic.php?t=311533)
- Dialog "Show Preset Info": window should be resizeable and minimizeable (to task bar)
- Improved reverb module (sometimes it sounds like a "ton" reverb)

Doku:
- Mulab-docs as PDF document
- Detailled reference doc of all modules

I recently noticed a possible bug:
- Virtual MIDI Keyboard: function of "AZERTY" and "QWERTY" buttons is swapped.

JR

[MuTools]

More support for backward played samples (start of sample playing could be calculated for percussive samples)

You can play samples backward by using a start locator that is beyond the end locator. Did you know that? Or do you mean something else?

Improved reverb module (sometimes it sounds like a "ton" reverb)

When? Which preset?

Detailled reference doc of all modules

See http://www.mutools.com/info/docs/mux/mu ... dules.html

I recently noticed a possible bug: Virtual MIDI Keyboard: function of "AZERTY" and "QWERTY" buttons is swapped.

I don't see anything wrong. Note that when choosing eg AZERTY, then white keys are on the Q row, black keys on the A row.

About your other requests, i'm sure you know about this info page. FYI: Many of your FRs are on the wishlist indeed.

[Reincke]

Hi Jo,

thank you for your reply.

You can play samples backward by using a start locator that is beyond the end locator. Did you know that? Or do you mean something else?

Maybe you know this effect from some psychedelic songs of the sixties (Rolling Stones: 2000 Light Years; Beatles: Strawberry Fields Forever). It will mostly be used for drums/percussions, piano and solo guitar.

At the moment MuLab cuts off the (essential) rear part of a reverse played sample (which is in fact the front part of the sample), if the note length is shorter than the sample.

Let's consider a reverse played cymbal sample, that should end (=be loudest) at a given beat. I would like to draw the note end event at that beat. The correspondent note start event must (of course) be drawed anywhere left from that beat. Now MuLab could calculate (That's what computers are made for, aren't they? the start of sample playing. If the note is shorter than the sample, MuLab should start playing the sample at the distance from the sample's end equal to the note length (sorry for this muddled english). Otherwise if the note is longer than the sample, MuLab should wait playing the sample for the distance between sample an note. Summarized it should simply be the reversed behaviour relating to normal sample playing.
What do you think: Could MuLab behave like this?

Improved reverb module (sometimes it sounds like a "ton" reverb)

When? Which preset?

I took the samples "RockSnare1" to "Rocksnare3" and fed them into some reverb presets. Try factory preset "Giant Hall", reduce the leftpre-delay to 35 ms and listen to the fade out of the reverb. Call me a nitpicker, but to me it sounds with a resonance, like a large, steely (empty) cistern, not like a giant hall or cathedral. Anyway, this is a prio Z feature.

Detailled reference doc of all modules

See http://www.mutools.com/info/docs/mux/mu ... dules.html

I should have written "More detailled". From my point of view the modules are the core of MuLab. This feature is really great. It's nearly a complete studio on my lap.
With "Detailled" I meant a complete description of each module, in particular the inputs and outputs, knobs and fields etc., and of the purpose of the module itself, or rather the intended use. Of course I have read the module documentation - more than once. And tested some features. Let me show you a few examples of what I miss:

Module "Oscillator": What does the unnamed number field right from "pitch" field do? (Yes, I know there is at least one forum post relating to this, but that's not the place where you'll find it when you're offline.)

Module "Allpass Filter": What is the typical use for it? Which is an exemplary factory preset, showing the essentials?

Module "Multi Mode Filter": What is the calculative impact of "key tracking" to the frequency?

Modules "Monophonic Note Tracker", "Note Key Ranger": What is a typical use for it?

Module "Ringmodulator": What about a hint that we can add nice overtones to an audio signal by connecting the same signal to both inputs (doubling the sine signal).

Let me stop here. I think you know what I mean.

I recently noticed a possible bug: Virtual MIDI Keyboard: function of "AZERTY" and "QWERTY" buttons is swapped.

I don't see anything wrong. Note that when choosing eg AZERTY, then white keys are on the Q row, black keys on the A row.

OK, I see. You're right. My fault, sorry. A bit difficult to map it with a german keyboard layout.

About your other requests, i'm sure you know about this info page.
FYI: Many of your FRs are on the wishlist indeed.

Of course I know this ubiquitous topic.

There is another new FR i forgot in my first post:

- A (classic) "Distortion" module. User interface and functionality could be similar to the the "compressor" module, but affecting the audio signal curve despite from affecting the envelope curve (attack / release is not necessary then). The tanh distortion is suitable for synth sounds, but it sounds scratchy for real or virtual guitars. For guitars a "soft clipping" model would be great.

I'm curious about the new pitch bend automation feature. You're doing a great job. BTW: I recently added a link to "mutools.com" at my soundcloud page. I hope it's ok.
JR

[MuTools]

Let's consider a reverse played cymbal sample, that should end (=be loudest) at a given beat. ... Could MuLab behave like this?

Nice feature request. Not planned on short term i'm afraid. Luckily a calculator can give you the perfect position of the note start, so it's possible already. Tip: Right-click sample -> Show Info gives you the length of a sample in ms. From there, using the tempo, you can get the length in number of beats:

NumBeats=SampleLengthInSeconds*Tempo/60

Hope this helps.

Improved reverb module (sometimes it sounds like a "ton" reverb)

When? Which preset?

I took the samples "RockSnare1" to "Rocksnare3" and fed them into some reverb presets. Try factory preset "Giant Hall", reduce the leftpre-delay to 35 ms and listen to the fade out of the reverb. Call me a nitpicker, but to me it sounds with a resonance, like a large, steely (empty) cistern, not like a giant hall or cathedral.

This is the result:

http://www.mutools.com/audio/MuverbedSnare20131101.mp3

Sounds good to me. Not to you? If it's not the perfect reverb you want, you can tweak the MuVerb further, or use another (VST) reverb.

Note: You can even build your own reverbs with the MUX, using Allpass filters, echos, filters, lfos, ... though i admit that's not done in 123.

Detailled reference doc of all modules

See http://www.mutools.com/info/docs/mux/mu ... dules.html

I should have written "More detailled".

I won't document 'the obvious' because that costs too much time and almost no one reads it. I know there is a gray zone arout 'the obvious' so i'm doing my best to further detail the docs where necessary. I too note of some of your feedback on the docs and will extend them soon.

There is another new FR i forgot in my first post:
A (classic) "Distortion" module. User interface and functionality could be similar to the the "compressor" module...

Yes i know what you mean and got that one on the (short term) wishlist. Possibly short term, but no promise.

I'm curious about the new pitch bend automation feature. You're doing a great job. BTW: I recently added a link to "mutools.com" at my soundcloud page. I hope it's ok.

Of course! Thanks! The more MuLab and MUX get known the better for their further development!

[Reincke]

Now we have automation parts for pitch bends etc., which is really great. Did I mention that already?

I forgot another FR in this post ("I gave them an inch and they'll take an ell"), which is really on top of my personal wishlist:

- A next consequent step in my workflow would be the ability to edit sequence & the relevant automation part in a combined way, possibly in one window similar to the envelope editor embedded into the sequence editor as today. I know about the paste zoom feature, an I have to admit it's only a workaround. The connection of note events and the related automation envelopes should alway be present. Zooming and scrolling should affect both views in the same way. A combinded editing would be big step.

I'm not sure if this is on the wishlist.
JR

[DHR53]

I'm adding a question fyi in here since I saw this post... On the Mac version, I've noticed that when I switch apps to the foreground and go back to MuLab, if I have(had) a Plugin interface open, the interface goes white and I have to close the plugin and reopen to view the interface. I have to do this all the time, as I work with this computer and have MuLab running with other stuff often. Is that a bug? Or a Mac thing...

Thanks.

may have mentioned this before

[Reincke]

In addition to my previous post above I think displaying sequence and automation part in a single window could be just ONE solution. A coupling of both views could be another, e.g. by a "super window" for (at least) two part editors (like "swim lanes") with a common navigation. There may be more approaches.

The request behind all this is to keep the relation between the views whenever one of the views will be horizontally scrolled or zoomed.
JR

[Reincke]

Besides my "combined view" feature request above - here yet another FR:

- Composer: Often I select a bunch of parts over all tracks and shift them right to make space for new parts. Then it would be nice to select related locators and tempo changes in the same manner and shift them together with the parts. So what if locators and tempo changes would be selectable and "clipboardable"?
JR

[MuTools]

In addition to my previous post above I think displaying sequence and automation part in a single window could be just ONE solution. A coupling of both views could be another, e.g. by a "super window" for (at least) two part editors (like "swim lanes") with a common navigation. There may be more approaches.

The request behind all this is to keep the relation between the views whenever one of the views will be horizontally scrolled or zoomed.
JR

Nice suggestion, taken note on the wishlist.