MUTON FREE Beta 1 for OSX & Windows

[muzycian]

<deleted post>
My mistake... Too late for me, clearly. I'll go away now
--------
Well, I'll use this to say something useful instead...

I really like the way the audio streams. I wasn't sure what the manual meant when it said that. But the audio side feels really responsive: the sequencer starts and there you go - sound! And no glitches.

Is it playing everything from RAM? (Maybe the error I got was trying to load a file too big - I wasn't paying much attention, to be honest: too much fun )

No, it's not all from RAM. It's really streaming from disk.

Glad to hear it works fine

Thanks for your feedback so far PL.

Gonna break too now.

Have a good night

[Hengy]

Jo,

But the record button IS red when recording no?

I mean: a filled red circle in an orange rectangle button, right?

that's what i expected given the behaviour of the play button, but on my system it stays clear and unfilled

Oh - in playing around to reproduce the vsti scanning issues below i tried the record button again and it works now - but it certaintly didn't the last time, i'll let you know if it does it again.

Anyway, when MUTON would crash while scanning VST plugins, there should be a VstPluginScanLog.txt in your {Muton.exe}/Settings subfolder.
Now when you open it in a text editor, what's the last line saying?
That should tell on which VST plugin it crashed.

yup, i know about that (if you recall i requested it in the alpha's )
my point is on my system the exact vsti seems to be irrelevent - if i take the suspect vsti and put it in a new folder it'll load quite happily.
the last one it crashed on was modelx (one of xoxos's i think) when i moved this plug to a folder with only a few vsts in it scanned perfectly.
interestingly there are 500 lines in the scanned vst text file, including one blank line at the end (so 499 plugins) - a suspiciously round number.
i just removed the modelx entry from the bad plugs list - vstplugins.xml file, and tried again, and it falls over at the same plug, so it is repeatible in that respect.
ok just let it scan after leaving modelx in the bad plug list, and again it falls over at the 499'th plugin. and yes maybe this is all just my fault for having a *lot* more than 500 vsti's.
(btw this is an example of one of the bonus's of replacing notepad with notepad2 as it shows the line count of the file )

[muzycian]

Hengy, what platform are you on?

[Hengy]

Win XP SP2, 1gig ram

[muzycian]

Can you give me an idea how your plugins are organised?

I mean: are they almost all together in 1 big folder, or are they almost all in separate subfolders?

[Hengy]

they are in a number of sub folders, under one main folder, but i have quite a few at the top level of that folder, so i can't escape scanning the whole lot in one go.
i can send you the vstpluginscan file if that'd help

[muzycian]

Well, it surely doesn't hurt Please send to my mutools account.

So, just to be sure i understand: you have the impression that it always crashes at the 500th plugin, right?

(strange, i can't find an immediate reason now, but will search more tomorrow then, now i really go )

[Hengy]

already sent
yes certainly the number of times i've tried it tonight it's crashed on the 499th DLL scanned (just noticed the log file includes dll's that aren't vst's) , i don't know what it failed on in previous alpha's as i didn't have a linecount in notepad, i'll check tomorrow incase it changes.
good night - i'm sure the answer will come in a flash of inspiration while you're asleep

[Bonteburg]

@Jo,
-yes the probs in the automatino lane are happening in the sequence editor.

-by "nudge" I mean move.
You have to move the note you want to edit if it coincides with another note (ie the velocity column thingies are in the same place)

-ook into it is bad typing for "look into it"
ie I tried to change the player in the list editor and it crashed on me.

OK gotta go to bed now..
Marco

PS Found a new weirdness:
As you click on a sequence in the arrange window, it sometimes happens that the little player window says "no player" even if SR202 is playing correctly. Sounds ike a mere Graphic bug to me, but confusing

[muzycian]

by "nudge" I mean move.
You have to move the note you want to edit if it coincides with another note (ie the velocity column thingies are in the same place)

If multiple notes are on the same position, isn't it good then that sliding the velocity beam on that position affects all these notes?

How would you like it?

-ook into it is bad typing for "look into it"
ie I tried to change the player in the list editor and it crashed on me.

Are you sure about this?

Clicking the event's player in the list editor shouldn't do anything.

As you click on a sequence in the arrange window, it sometimes happens that the little player window says "no player" even if SR202 is playing correctly. Sounds ike a mere Graphic bug to me, but confusing

Maybe that part didn't have a Player, but maybe it's events where playing the SR202. Could it have been that?

[Bonteburg]

If multiple notes are on the same position, isn't it good then that sliding the velocity beam on that position affects all these notes?

How would you like it?

You're right Jo, it didn't occur to me that it might actually be a useful feature when working with chords!


On another note, how can I find out if my VSTI are "CFM" or MachO"?
Although i don't think that's the problem, as CM101 seems to load fine on your machine...

Marco

[muzycian]

Well, i don't know myself.

I also found it frustrating that i can't simply see whether a vst plug is macho or cfm.

Any osx specialist here knows how?

[Bonteburg]

--------------------------------
Latest Bug Bulletin
--------------------------------
-Alright so i moved my plugs to a folder within the Mutons folder, now it loads CM101 and SR202 (no other plugs however).
Maybe there is a subfolder issue,along with most of my stuff being "cfm"?

-I created a sequence with CM101, again, there was the disappearing player issue: I click on player and choose my synth, I click on its sequence and it says "no player" in the little black box.

-What happens in the List Editor is that when I choose "insert" , Muton crashes on me.
In addition, the graphics are somewhat garbled (fonts overlapping etc)
It also says "no player" when the part is in fact a SR202 or CM101 part.


Marco


edit: changed layer to player, fuckinig typos!

[muzycian]

Marco, some quick replies:

-> i'm tracing something that could be a reason for the vst loading issue. so let's cross fingers it's that.

-> i'll check the player-display and list-editor-insert issues.

-> about the overlapping fonts: the list editor doesn't initialize its size very well, the very first time. so resize the list editor and drag the verical column splitters around so you see everything well. this is memorized for the next times.

-> When your part has a player assigned, but the events have no player, then you'll hear the part's player, but you see no player in the list edit. This is a bit confusing, and will be improved in beta 2!

[muzycian]

I created a sequence with CM101, again, there was the disappearing player issue: I click on player and choose my synth, I click on its sequence and it says "no player" in the little black box

Bonte, could it be that the "no player" thing is when you lasso select the part? But when really clicking on the part, the player is displayed. Is that correct?

By the way, i might have found an possible issue in the load vst function.

Friday, when beta 2 comes out, then we'll know.

Beta 2 also properly reports when it encounters a CFM plugin in the form of "XYZ is a CFM Vst Plugin; CFM Vst Plugins are not supported".