MuTools

Trancit · Post by **Trancit** » Mon May 01, 2017 9:07 am

Don´t know if it is a bug:

For testing I tried to record a Midi VSTi´s output to the event recorder...
This VSTi needs sequence data input from a track, where I put a 4 bar sequence from Bar 1 to 5 on...

Event recorder seem to miss the first note(s) during recording...

pljones · Post by **pljones** » Mon May 01, 2017 9:51 am

Weird... I'm not a user of the event recorder... What do you see in the Event Monitor -- does the event "missing" appear there?

Trancit · Post by **Trancit** » Mon May 01, 2017 10:11 am

Did some more research... it happens only if grid is set to "No Grid" in the event recorder...

If I set it i.e. to 16th, everything is fine

MuTools · Post by **MuTools** » Mon May 01, 2017 1:10 pm

I can't immediately repeat this. Can you repeat the issue with MU only modules, eg with the Step Sequencer or Piano Keyboard modules? And what about pljones' question: Does inserting a Event Monitor reveal something?

Trancit · Post by **Trancit** » Mon May 01, 2017 2:28 pm

It doesn´t happen with MuLab internals but with every Midi VSTi I have here...

I don´t know, what I shall test with the Event Monitor though???

MuTools · Post by **MuTools** » Mon May 01, 2017 2:49 pm

Trancit wrote:It doesn´t happen with MuLab internals but with every Midi VSTi I have here...

Which VSTs? Please list the free yet stable ones first.

I don´t know, what I shall test with the Event Monitor though?

See which events go into the recorder. That way you can see if it's on the VST side (including the mu VST interface) or on the recorder side.

pljones · Post by **pljones** » Mon May 01, 2017 4:48 pm

Trancit wrote:This VSTi needs sequence data input from a track, where I put a 4 bar sequence from Bar 1 to 5 on...

Oh, and does the timestamp on the notes matter? That is, if the "first note" is at 1.4.09 in the first bar is it any different from if the "first note" is at 1.1.0?

Trancit · Post by **Trancit** » Mon May 01, 2017 5:56 pm

mutools wrote: Which VSTs? Please list the free yet stable ones first.

Tested with:
http://www.codefn42.com/chordz/index.html
http://graywolf2004.net/wp/

Both are very stable and come as a simple zip file...

pljones wrote:Oh, and does the timestamp on the notes matter? That is, if the "first note" is at 1.4.09 in the first bar is it any different from if the "first note" is at 1.1.0?

Yeah, that´s true... I wanted always test this as well and forgot

The missing notes happen only if record starts from bar 1.1.00000

Trancit · Post by **Trancit** » Mon May 01, 2017 6:04 pm

mutools wrote: See which events go into the recorder. That way you can see if it's on the VST side (including the mu VST interface) or on the recorder side.

I inserted 2 Event Monitors one in front and one behind... they listed all events correctly, while the created sequence missed again the first notes...

Trancit · Post by **Trancit** » Mon May 01, 2017 6:08 pm

Found something else:

It only happens, if in the record options (rightclick the main record button) a countdown is given... with countdown = 0, there are no missing notes...

AndreasD · Post by **AndreasD** » Mon May 01, 2017 7:42 pm

I appologize if I misunderstand!
What you say is the correct behaviour. The countdown is the usual count in and waits until it's zero before start recording.

Trancit · Post by **Trancit** » Mon May 01, 2017 7:52 pm

The difference is:

I have a sequence triggering a Midi Vsti, which output should be captured...

If everything is correct, the event recorder captures every note in the new sequence, right???

But if:

- there is a countdown in the record options AND
- the triggering notes start in the composition from bar 1.1.00000 AND
- in the event recorder grid is set to "No Grid"

in the captured new sequence the first note is missing... at least on my side

pljones · Post by **pljones** » Mon May 01, 2017 9:12 pm

Trancit wrote:...
- the triggering notes start in the composition from bar 1.1.00000 AND
...

Did you try 1.1.00001 (i.e. the very, very smallest later event time) but everything else unchanged?

Trancit · Post by **Trancit** » Mon May 01, 2017 9:35 pm

pljones wrote:
Trancit wrote:...
- the triggering notes start in the composition from bar 1.1.00000 AND
...
Did you try 1.1.00001 (i.e. the very, very smallest later event time) but everything else unchanged?

Than it´s easier to turn off the countdown or just set a grid size...

MuTools · Post by **MuTools** » Tue May 02, 2017 9:12 am

Trancit wrote:
mutools wrote: Which VSTs? Please list the free yet stable ones first.
Tested with:
http://www.codefn42.com/chordz/index.html
http://graywolf2004.net/wp/

Both are very stable and come as a simple zip file...

pljones wrote:Oh, and does the timestamp on the notes matter? That is, if the "first note" is at 1.4.09 in the first bar is it any different from if the "first note" is at 1.1.0?
Yeah, that´s true... I wanted always test this as well and forgot

The missing notes happen only if record starts from bar 1.1.00000

Still can't repeat it.

This is what i did:

* New project
* Inserted Chordz before Basic Synth and mapped a chord to C
* Started recording from 1.1.0000 and played a C on the MIDI keyboard, both note down and up in the countdown.
* Stopped recording
* The new part does contain the chord. (be it with a minimum length but that's logical in this case of course)

MuTools

KVR Audio

Bug in Event recorder???