M3 Tests

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

Post

sorohanro wrote:
mutools wrote:Still a bit of a weak point, i know. It's on the whishlist. For now it can only be done using automated plugins. Or, you could edit the audio file itself, i.e. apply fade in/out on the audio data, but note that's explicitly changing the audio file.
I'm glad that you understand what I'm talking about :) and if you say it's on the wishlist, then I trust you'll make in the future something that will make me laugh when people will say "I'm using Pro Tools" ;)
Editing the audio file it's what I want to avoid. I try non intrusive actions.
Yes i do know what you mean. In fact i wanted to add this already in M3 but i ran out of time. Normally it will be there in M4 ;)
can you have some notepad/ text writing-reading plugin in the program ? that would be very useful for demo songs (track by XXXX, copyrighted to XXXX), or tutorial files (look at the automation line in bar XXX where is controlled XXX parameter)...
If it's for tutorial reasons, then a bare text editor is insufficient imho.

The best way for tutorials is using flash demonstrations and/or youtube movies, i think. What do you think?

Post

This happened to me using MU.LAB 30.0.11 just now:

http://www.fileden.com/files/2007/5/13/ ... aphics.jpg

It has never happened before. In addition to the redraw issues, I was unable to perform mouse operations in the arranger window for some time (sometimes the arranger blacked out too, but sometimes it was unresponsive though visible.

Closing and reopening MU.LAB fixes it.

I don't know what caused it but it happened when I was clicking on the track area on the left (I believe).

Post

sorohanro wrote:
mutools wrote:
sorohanro wrote:BTW, how do I cross fade audio tracks ?
Using automation, e.g. automation of rack faders.
How I do that in one track ?
situation:
I record a voice and I like a part (vocal 1) until an "aaaa" and after that I want to mix it with another part (vocal 2), so I choose the new part from "aaa" and inside of the "aaa" I cross fade (vocal 1 fade out, vocal 2 fade in, so it sounds natural).
that sounds like a job for an audio editor to me... would be cool to have more audio editing functions in Mu though, but it wouldn't be high in my wish list.
In the future there will be robots!

Post

Often, the first note played by a synth in a newly opened project is very loud. The synth then returns to its normal mixing level.

This could also be happening with a newly loaded synth in an existing project, or when a synth part is played for the first time in a project.

I can't see a pattern yet, but it doesn't seem to happen when playing synths live (just the MIDI parts).

Post

sorohanro wrote:

unrelated feature request:
can you have some notepad/ text writing-reading plugin in the program ? that would be very useful for demo songs (track by XXXX, copyrighted to XXXX), or tutorial files (look at the automation line in bar XXX where is controlled XXX parameter)...
I love it when programs let you take notes in the songfile!!!

+1
In the future there will be robots!

Post

Bonteburg wrote:This happened to me using MU.LAB 30.0.11 just now:

http://www.fileden.com/files/2007/5/13/ ... aphics.jpg

It has never happened before. In addition to the redraw issues, I was unable to perform mouse operations in the arranger window for some time (sometimes the arranger blacked out too, but sometimes it was unresponsive though visible.

Closing and reopening MU.LAB fixes it.

I don't know what caused it but it happened when I was clicking on the track area on the left (I believe).
If you find a pattern in when it happens, please let me know.

And if it happens again, then try minimizing and maximizing the main fundow, and see (and let me know) if that properly refreshes the main window.

Post

theorize wrote:
sorohanro wrote: unrelated feature request:
can you have some notepad/ text writing-reading plugin in the program ? that would be very useful for demo songs (track by XXXX, copyrighted to XXXX), or tutorial files (look at the automation line in bar XXX where is controlled XXX parameter)...
I love it when programs let you take notes in the songfile!!!

+1
If you want to take notes with your song, you can put a text file in the same folder as your MuSession file.

Post

@mutools
I think that YouTube and Flash tutorials are good, but nothing compares with practical work, with a project file that you open in the program and you see "in front of your eyes" how works and where is routed.
For that kind of things a text file would be great to have inside the project, while you can follow it step by step.

A text file is useful also for stupid kids who think that if they bought the program (that comes with demo songs) they own also the demo songs and start posting & selling those on stock audio websites.

Take example from Reason and FL.
It's always useful to state the author of a song :)
Also, we are not having tons of money, so we use a lot of demo plugins that don't save presets, so would be useful to write down (button 3 to 9 o'clock, button 4 to 3 o'clock).

@theorize
I try to avoid editing the original file, so I have more space to "make mistakes" and still be on the safe side.
Also, if you record a band and you have 5 or 6 voice lines, you just can't take all to a sound editor and cut/ paste to have the best take. You need to have the project in front of you and check your work "in the mix".

As for automation, sure, can work like this on small projects but when you have 30+ tracks... gets a bit nasty to control.

Post

Bonteburg wrote:Often, the first note played by a synth in a newly opened project is very loud. The synth then returns to its normal mixing level.

This could also be happening with a newly loaded synth in an existing project, or when a synth part is played for the first time in a project.

I can't see a pattern yet, but it doesn't seem to happen when playing synths live (just the MIDI parts).
I'll keep an eye on it. If you find more pieces of this puzzle, please let me know. Thanks!

Post

sorohanro wrote:As for automation, sure, can work like this on small projects but when you have 30+ tracks... gets a bit nasty to control.
The future plan is to add a Fade In, Fade Out and Volume parameter per audio part. The Fade In/Out are expressed in musical ticks e.g. Fade In = 0.1.0000 => fades in from silence to full volume in 1 beat.

Then it becomes quite easy to make crossfades.

Would that work for you?

Post

mutools wrote:Then it becomes quite easy to make crossfades.

Would that work for you?
I guess so... well, after all the M3 madness is off, take a look on how crossfading goes in Reaper, Cubase and Sequoya and I'm pretty sure you'll come with some awesome ideas.
I think that in Cubase and Sequoya, crossfading is the most complex (so many customizable parameters that I actually get lost... what's the difference between gain, level and energy anyway ???).

I like your way of keeping things simple, understandable and effective.

Post

mutools wrote:
Nielzie wrote:I also get crashes on both of my systems when switching through presets while playing a sequence in Vember Audio SURGE

Something I didn't have in any other DAW I tried (Orion 7, EnergyXT2, REAPER 3)
Yes i also get that crash :?

It's crashing within Surge, i have no idea why.

I'll email Vember Audio about this.
Emailed them. Curious if they'll respond.

Post

Bonteburg wrote:Often, the first note played by a synth in a newly opened project is very loud. The synth then returns to its normal mixing level.

This could also be happening with a newly loaded synth in an existing project, or when a synth part is played for the first time in a project.

I can't see a pattern yet, but it doesn't seem to happen when playing synths live (just the MIDI parts).
Think i found the problem. Will search for a solution.

Edit: Fixed in the next version.

Post

MU.LAB test 3.0.13 is available in http://www.mutools.com/mulab/azalea

This version fixes the "sound too soft/load for a moment after loading a session" bug.

If you did not yet install 3.0.12, then a full install of the package is needed as things in the graphics folder and library have changed. If you want to keep your current settings, then copy all files in Mulab/Settings to the new installation.

If you already installed 3.0.12, then installing the newest application patch is sufficient.

Post

MU.LAB test 3.0.14 is available in http://www.mutools.com/mulab/azalea

If you did not yet install 3.0.12, then a full install of the package is needed as things in the graphics folder and library have changed. If you want to keep your current settings, then copy all files in Mulab/Settings to the new installation.

If you already installed 3.0.12, then installing the newest application patch is sufficient.

Post Reply

Return to “MuTools”