Muton Beta 2

[muzycian]

Hi Jo,
>>Yeah let's do some Bonte specific tests!
I'm not so sure it's an issue really, or just my computer being oldish and running OSX, so don't lose sleep over it.

What machine are you using? CPU speed?

[muzycian]

Major bug: When you drag a midi sequence on top of an audio part, you cannot select the midi sequence. You have to move the underlying object first before

you can get to the overlayed object, even though it appears 'at the front'

Fixed in beta 3.

I found a problem with the visual tracking of a parameter sequence. I imported one of my audio tracks into a composition. I decided to record the parameters

of a VST effect for that audio track in real time as it played (in this case a reverb, but I've checked and it's the same for other effects). I opened the

recorded sequence, which correctly showed the changes I made to the effect's parameters. However, when you play the song, the position bar moves left to

right then disappears, without the screen scrolling to the next section of the song. Zooming out will find the current location, but this isn't ideal. The

song plays perfectly, but the screen does not follow the current song's position. This means that you can't really monitor effects parameters in detail while

the song plays. This is different to the other problem I found, as this doesn't track the song even if you start with the current position on the screen.

Will be improved.

When manually entering midi notes into a sequence, move the cursor to the 'all notes' value 2 window. The cursor shows a normal arrow cursor. OK so far. But

when you click -then move- the mouse, the cursor changes to the pencil tool, but with no functionality. i.e. it looks like the pencil tool but it isn't. It

isn't really the pencil tool, it's really the 'arrow' tool but when you click the mouse for some reason it's mouse-down state changes to look like the pencil

tool. Clicking the pencil tool corrects this (it changes to the real pencil tool), but this is a bug that could cause confusion. To correct this bug, the

cursor should not change shape under 'mouse down' condition unless a tool is chosen in the value2 window.

Fixed in beta 3.

When a seqence or audio object is pasted from a copy, both the souce object and the newly pasted object are highlighted. Usually, you will need to move the

pasted object as it is rare it gets created in exactly the right place. But as both souce and copy are highlighted, grabbing and moving the new sequence also

moves the original. I think that the source object should lose focus as I can't think of a situation where you would want to move source and destination

objects imediately after pasting.

You're right, will be improved lateron.

I've just worked out the official way of copying and pasting objects. But... it doesn't seem logical to select objects, then click *away* from the obejct(s)

onto an empty part of the composition screen to get to the 'cut/copy/paste parts' options. I think it's best if these options appear within the 'right-click'

menu of an object or mulitple selections of objects. Just my opinion - you're the boss!

The logic of a right-click is: popup menu with specific functions for the "thing" you right-clicked on.

If you right-click a part, you cannot past parts into that part.

If you right-click the composition (i.e. "the background"), then you can paste parts.

But i'll keep an eye on this, so to check if this logic is intuitive.

Copying objects doesn't seem to make independent copies of objects. So editing a copy of an object also edits the source objects and all other copies of the

object. Suppose you had a basic drum sequence, and needed to make a copy to add a drum fill, or just an extra cymbal crash. You could make a copy of the

basic drum sequence and add, say, a cymbal crash, into this copy and use this part where needed. But at the moment, it doesn't seem possible to do this. The

extra cymbal would appear in the original drum loop as well as the basic drum part.

Am I doing something wrong?

No, you're right.

Lateron a function will be added to "Duplicate Sequence".

Edit sequence name: should start with the whole name highlighted, so any typing replaces the highlighted text.

This is how it currently works:

HOME: to go at start of text.
END: to go at end of text.
Shift+HOME or END to erase all text.

But i agree that it should be more standard.

Save as: Not prompted to save work before closing program.

Added in beta 3.

Opening MIDI file opens into new composition. Would like to import a MIDI file as a new track in the current composition.

A midi file could contain multiple tracks...

This is what you can do:

->import midi file (into new composition)
->copy-paste the imported midi parts you want into the composition of your dreams

Within the composition screen, change the function of the escape key to change from the pencil tool to the arrow/selector tool instead of close application.

But what then in the Note Key Editor?

There should be analog behaviour i.e. changing tools in composer or sequence editor should be the same.

Anyway, i'm also not yet 100% convinced of how it is now, and will think about other solutions.

Drawing a midi sequence with the pencil tool requires you to change to the arrow tool to open it in the editor (you could right-click and choose edit

sequence) but would prefer to be able to double-click the part with any tool to open editor.

I understand your request, it's not yet streamlined enough now...

But double-clicking a part with e.g. the gum to edit that part... i don't really like that picture.

Also here: i have to breed on this.

Editing a sequence opens one bar of the sequence. This usually means you have to zoom out to see the whole sequence or the bit you need to change. Suggest

setting the zoom range to view the entire midi sequence when the editor window opens.

OK, will do.

When a sequence or audio object is muted, how about a red 'X' drawn through the object to indicate that it won't be heard? Much like the mute symbol.

When a part is muted, it's displayed more grey-ish.

But you're right: it's currently not very visible. (i.e. not grey enough)

In beta 3, this will be better.

MISSING!
I've just realised there's something important missing. A "master" strip in the mixing desk. Suppose you wanted to apply a finaliser plug-in (maybe multiband

compressor or whatever) to the whole mix - you need to do this to the master strip, otherwise you have to apply it to all strips.

If you want a master strip, then add a send strip, and send all relevant audio to that strip. Then you can apply whatever master effect to all the audio!

Oh, but wait: what's missing is: a mixers strip should be able to have "no output" then.

Coming soon.

Cheers,

Jo

[muzycian]

Also, adding a new track doesn't create a default track name (e.g. "Track 5")

Will be improved.

[muzycian]

Another suggestion:
Perhaps a double-click could also return the level to 0db.

Let's use a right-click.

Will be done in beta 3.

[muzycian]

Jo, I think you're going to hate me
Any chance that a 'glue' tool can be added which would allow you to join parts together?
Along with the chooser, pencil, eraser and split tool, these should form the complete set of editing tools.

Will be added soon; only for sequence parts though.

[muzycian]

Muton still refuses to mix down to anything other than so much silence

Found it (stupid bug )

Will be fixed in beta 3.

[Bonteburg]

Hi Jo,
>>Yeah let's do some Bonte specific tests!
I'm not so sure it's an issue really, or just my computer being oldish and running OSX, so don't lose sleep over it.

What machine are you using? CPU speed?

G4, (2000 build) 400 Mhz, 320 Megs SDRAM, MacOSX 10.3, Delta Audiophile 2496, Logic Express, Mutools Beta 2.

[muzycian]

And how is logic running on that machine?

[Bonteburg]

Logic is running reasonably well, (i'm probably not as demanding a user as some other people though).
I need to mix down frequently of course. RMIV gives the odd popping noise, i think those are cpu spikes.
redraw works fine!
Hm..what else..
loading samples during playback is a bit of a bother with playback sometimes stopping and an error message popping up when i rummage around a directory too long.

As I was saying, Muton doesn't run badly or anything, it's just that the position line and redraw in general is a bit "jumpy" , it's all a bit stop-motion if you know what I mean. Logic has a smoother feel.

[Bonteburg]

oh..Jo while I'm at it:

How's about:

-an option to start with a new project, or even something like "Template.IMS"
Cos right now it loads up the latest project as per default, which isn't always comfortable.


And is there a way to change the Audio Buffer Size settings?
In Logic I'm using a plugin that has some timing issues so I changed the buffersize from 512 to 256 from within a Logic dialog, so more access to general settings would be cool, a la "Muzys.set"


Marco

[> DiGiT <]

jo how do you do all the programming AND respond at length to all this? LOL!

[Bonteburg]

yay kudos...best not pay attention to the more spoilt-brat ones (like my latest one )

Seriously though it's just a slight stutter in the gfx, it's not like Muton is unstable for it or anythnig. I

Marco

[muzycian]

I need to mix down frequently of course.

Try mixdown but with NOTHING selected. That should work, right?

FYI: Beta 3 (coming soon) fixes a bug that causes silent files when something is selected.

RMIV gives the odd popping noise, i think those are cpu spikes.

Checking out the RMIV...

[jinnan_tonnix]

Hey Jo! Good to hear from you. Hope you're well now.

I've got a few suggestions for the audio lab. I'm not sure if this is the time to bring them up as you must be pretty close to getting Beta 3 out. If you're aiming for the end of the month to get the first release, realistically, how much time do you think you'll get to develop the audio lab?

The most important thing is stability and reliablity, and anything than compromises this will just have to wait.

Cheers,
Paul.

[muzycian]

jo how do you do all the programming AND respond at length to all this? LOL!

Yes;

So be welcome to help with testing muton, and feedback any bugs or annoying workflow bottlenecks.

So we get muton rock solid asap

Cheers!