M3 Tests

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

Post

Selected a bunch of notes, hit delete, got asked if I wanted to delete a rack entry... and hit "Y" without really reading it! Oops. Not sure why the rack entry got selected, though.

Post

Hmm. Not sure on this one: I don't seem to be able to find the "(2)" version of a sequence. It's in the pool, but I don't see it in my composition. But "Delete unused" doesn't delete it.

I'd like to be able to delete even used sequences using the Pool tool...

Post

When I add a note to the last tick of the second beat the note does not fill the space all notes at that spot do not draw correctly. I tried to draw it over and it still does the same.

Post

pljones wrote:Selected a bunch of notes, hit delete, got asked if I wanted to delete a rack entry... and hit "Y" without really reading it! Oops. Not sure why the rack entry got selected, though.
That happened to me too.
The part I was deleting was near the bottom of the composer window - ie just above the horizontal scrollbar and the racks. I selected the part by 'drawing' round it (lassoo). While doing so, I accidentally dragged my lassoo below the scroll bar and a little way into the racks area, and it seems that if any part of a rack NAME gets included in the lassoo, then pressing the delete button produces an alert 'Delete Rack ---', etc.
Don't know the technical reason, but maybe this is what happened to you ?

Les J
(my first post on the forums !).
Last edited by Improviser on Mon Jan 11, 2010 3:15 pm, edited 1 time in total.

Post

liquidsound wrote:Moving the tracks into the empty space deletes them and sometime even when moved around in a new position.
The later is not consistent, only here and there.
Fixed in the next version.
Moving the last Mixer's Strip to the right into the empty space = Crash
Fixed in the next version.
The Track Mute/Solo is very small and it is too easy to activate the Choose Target menu.
Yes, i noticed it also. Not comfortable. Will be improved.
The context menu in the Key editor opens up completely and the default choices are far away from the mouse pointer and not ready available as in the Composition Context menu.
It could make you a little dizzy if working with mouse only input tool...
Double click again on the Plugin name on the Mix Strip could be use to close the plugin. A very quick way to check things out.
<Edit>
Added to the whishlist.
</Edit>

There is a little problem with this: When an editor is open but it's hidden behind another editor, then you doubleclick e.g. the rack slot, then it will close the editor but the user will be confused as he/she doesn't see it closing... :?

I love the Double click for adding new notes and parts however you could cover both styles of work by adding, if possible, for example, a modifier key (Shift) to implement One Click action for adding/delete a Note/Parts.
I would like to preserve the modifiers for other things, they're a spare resource, and most combis are already in use.
[Shift] is preserved for selecting purposes.
Last edited by MuTools on Mon Jan 11, 2010 2:21 pm, edited 2 times in total.

Post

liquidsound wrote:Also dragging the last Track down into the empty area crashes MuLab.
Should be fixed in the next version.
Editing a Shortcut makes it go away. Deleted.
Note that the current test version works in Free mode. M3 Free supports up to 16 shortcuts. Does that explain what you encountered?
BTW I love the Shortcuts. I am a grid maniac and now I can just changed and turn it on/off on the fly (and it works while you drawing the note!).
And the 128th.. Thank you. :love:
Yes, that combi works very fine indeed :)

Post

Improviser wrote:Les J
(my first post on the forums !).
Welcome!
Improviser wrote:While doing so, I accidentally dragged my lassoo below the scroll bar and a little way into the racks area, and it seems that if any part of a rack NAME gets included in the lassoo, then pressing the delete button produces an alert 'Delete Rack ---', etc.
Don't know the technical reason, but maybe this is what happened to you ?
Could be... I probably did stray into the rack. I wouldn't expect objects in the two panes to be selected and definitely not in the pane I hadn't clicked in. Hmm, maybe it's to do with where the mouse is released?

Post

pquenin wrote:the per part target thing was a great feature, I want it back !
To be discussed soon.
I have done some more tests with the key shortcut system : I add a new one, I push a controller on my midi keyboard, Mulab detect it, I select a function (I have tried with play/stop, rewind) and close -> the shortcut is in the list but I doesn't work. I have tried the same but with the PC keyboard keys : it doesn't work too.
Please check whether you already have 16 shortcuts, cfr my message more above.
Can I make a request : it will be nice to have a play function and a stop function, not only a play/stop function...
Added to the whishlist.
I have big problems with the Event Graph Editor : as I have said before, if I right click and choose "select all" the event are selected and then if I hit "suppr" nothing happen. Also, when I draw lines, the GUI take 4 or 5 seconds before reflecting what I do, so it's unusable...
I will check the delay issue.

About the keyboard thing -> see below.
another big thing for me (I'm french, my keyboard is AZERTY) : when I type some text, Mulab behave as if I have a English keyboard (QWERTY).
That's very odd. I'm quite sure there is some keyboarding issue that also explains why [suppr] doesn't work.

Do any other users have similar keyboarding issues?

Note that nothing has changed in this field between M2 and M3 so i assume you should have had the same issue in M2 when pressing [suppr]
when you open the editor of a native mulab plugin, the preset name is empty in the plugin editor window.
That field shows the last chosen preset and so after reloading a session it may be empty because no preset has been chosen yet.

The patch name itself is in the title bar.

Post

pljones wrote:Minor display glitch:
I disabled a VST plugin and it greyed in the rack. When I enabled it, it didn't go black in the rack... But it's black now and won't go grey again! I didn't notice when it turned back black, unfortunately.
I found that although the text remains greyed outafter re-enabling the plugin, it seems to return to normal (black) text immediatley after some activity in the racks - such as clicking on any filled rack slot, or even just clicking twice on the little top-left button of the rack to 'close' and then 're-expand' the rack.

For me, however, it only seems to be a display glitch - because the re-enabled plugin works normally while the the text is temporarily greyed out.

Les J.
Last edited by Improviser on Mon Jan 11, 2010 3:10 pm, edited 2 times in total.

Post

liquidsound wrote:I was thinking about the Target/Part issue.
When I work in XT a use (sometime) multiple targets per track (coming from Reason Combinator heavy use) but XT do not have the Part/Targets feature that MuLab HAD.... :roll:

I used to use the MUX to engage multiple plugins for the same Part but then I discovered that I could use the Track's Rack and use a Sends to several Rack for each Plugin that I needed for the part. I hardly use more than 3 Layered Plugins so the 6 mixer slots was enough.

So I was thinking if with your new architecture we could Send a Part through the Track (to keep it the way it is now) to different Racks.
I sound like before but maybe technically it's approachable with your new system.
In other words a Part would have a Send built in or something on these lines.
I am giving numbers here? :nutter:
Independent of the track/part targets topic:

If you want to target mutliple synths at the same time i.e. layered synths, it's the best to use a MUX! :)

Post

pljones wrote:Minor display glitch:
I disabled a VST plugin and it greyed in the rack. When I enabled it, it didn't go black in the rack... But it's black now and won't go grey again! I didn't notice when it turned back black, unfortunately.

<edit>
OK, more than a display glitch. It gets confused. I now can't enable a Fasor plugin. It's greyed. But on the popout it's green and enabled! It's not processing, though.
</edit>
The only problem I get is the Greyout. The Rack needs to be ReFreshed by clicking it again or moving on another Rack.
The Toggle via menu works fine but again it needs Refreshing.
ABEFLGMOPPRRST :phones:

Post

pljones wrote:Minor display glitch:
Edit->VST Manager->Add VST Plug-Ins
After the first time, once I've selected Program Files\VST Plugsins\blahblah, the next time I open the Add screen, the selected folder is always scrolled off the bottom of the display.

Yes, must be improved indeed. Added to the whishlist.
Also, the keyboard focus doesn't seem to be on the listing until I click the scrollbar.
Fixed in the next version.

Post

pljones wrote:Minor display glitch:
I disabled a VST plugin and it greyed in the rack. When I enabled it, it didn't go black in the rack... But it's black now and won't go grey again! I didn't notice when it turned back black, unfortunately.

<edit>
OK, more than a display glitch. It gets confused. I now can't enable a Fasor plugin. It's greyed. But on the popout it's green and enabled! It's not processing, though.
</edit>
Should be fixed in the next version, thanks!

Post

Nielzie wrote:If still possible and needed I would like to volunteer to also beta test M3. I'm a registered M2 user. I have some spare time for it now and hope to come up with some usefull bugs catches/requests :)

Any chance? If not, no problem though :wink:
Please let me know your email address. (pm or email me)

Post

pljones wrote:Really minor glitch:
The "OK" button on the "This is a test version" box doesn't respond to Space or Enter, even though it appears focussed.
It will also respond to Enter and Return in the next version.

Post Reply

Return to “MuTools”