Insert Piz Here

insertpizhere · Post by **insertpizhere** » Sat Mar 28, 2009 4:59 am

another midiMonitor update... now it also internally records a midi file, and saves it if you specify ".mid" as the file extension in the save dialog. any other extension will be a text file.

it records midi for as long as the plugin exists. pressing the "clear" button restarts the recording.

http://thepiz.org/xt/midiMonitor.zip

Optomadic · Post by **Optomadic** » Sat Mar 28, 2009 1:42 pm

insertpizhere wrote:now it also internally records a midi file, and saves it if you specify ".mid" as the file extension in the save dialog. any other extension will be a text file.

it records midi for as long as the plugin exists. pressing the "clear" button restarts the recording.

Wha Huh? Holy shit piz! Very good update..

Hows the ppq sync?

.. Going to try this in a minute..

insertpizhere · Post by **insertpizhere** » Sat Mar 28, 2009 1:59 pm

there is no sync. the timing is based on the tempo and sample rate only, and it just records all the time whether the host is playing or not.

it's meant for testing/diagnosing midi stuff mainly, like if you're watching the monitor and see something weird, you can save the midi file to see exactly what happened. or to see exactly what midi the host is sending from a VST's perspective. but i guess you could leave it on all the time in case you play something good while the sequencer wasn't recording.

Optomadic · Post by **Optomadic** » Sat Mar 28, 2009 2:22 pm

Well the only problem is all the notes get a huge offset as (I guess) the timing of the monitor is always going. This makes it impossible to see/view/edit the notes if the MIDI file is opened in a host with no realignment (XT). Actually, if you scroll way to right you can see the clip in eXT.
For instance opening the file in FL gives the option to Realign Events. This puts the 1st note from the file at 1:01:000 and all subsequent notes after.

Also it does not fully filter C.Change messages and P.Bend recorded in FL. I just used a MIDI note only setup and it they still show up in eXT event list.

insertpizhere · Post by **insertpizhere** » Sat Mar 28, 2009 2:47 pm

it doesn't filter anything yet. when i have a few minutes i'll make it filter the same way as the monitor display. and i'll have it ignore empty space before the first event, but for now if you click "clear" it resets the timing.

Optomadic · Post by **Optomadic** » Sat Mar 28, 2009 5:39 pm

Ahh ok I see.. Makes sense now

insertpizhere · Post by **insertpizhere** » Sun Mar 29, 2009 1:52 am

done

http://thepiz.org/xt/midiMonitor.zip

Optomadic · Post by **Optomadic** » Sun Mar 29, 2009 11:15 am

Got it! Will let you know if I run into any bumps

..

Muchos Gracious hombre..

Optomadic · Post by **Optomadic** » Sun Mar 29, 2009 12:23 pm

Ok got to do a quick test. The offset has been fixed and the filter now carries thru to file output. Great work iph!!!!!!

I renamed the dll (to keep track of all the iterations

) and also figured I'd do the same to the fxp. Unfortunately that made the plugin freeze up (think it was looking for midiMonitor.fxp

). Everything returned to normal after changing back the name though so its not a big deal. Should probably let ppl know this though.

Question: Does pressing clear make the MIDI position start over? WAIT a minute! Forget that for a sec! Just noticed something (doing this as I type)...

If you save a MIDI file, then go back, monitor more MIDI messages and save again it new messages are not saved into the MIDI file (confirmed in eXT event list). The text file sees the changes.

Also just bumped into this. If you accidentally save the file with a wrong extension or no period (for instance I saved a file as midiMonitor,mid) and then manually correct the extension (midiMonitor2.mid), I get this error message in eXT:

If I try to drag the file into FL nothing happens.

Just a couple of things to look at.

Optomadic · Post by **Optomadic** » Sun Mar 29, 2009 12:51 pm

I noticed that the naming error simply makes the file into a text file if anything other than *filename*.mid is typed. JUCE must support filtering extension types in save diags no? Perhaps it would be better just to make a selector for both types to limit possible confusion.

Off the top of my head it should be (*.txt; *.mid) in the filter section (I think this is how you have it already). Cant remember now how to get the dropdown to actually select the file type (auto add extension). Also consider changing prompt section from Save MIDI log... to Save as TEXT or MIDI log... as an added instruction. Just a thought.

insertpizhere · Post by **insertpizhere** » Sun Mar 29, 2009 1:57 pm

Optomadic wrote:I renamed the dll (to keep track of all the iterations ) and also figured I'd do the same to the fxp. Unfortunately that made the plugin freeze up (think it was looking for midiMonitor.fxp ). Everything returned to normal after changing back the name though so its not a big deal. Should probably let ppl know this though.

it always looks for "midiMonitor.fxp" no matter what the dll is named. are you sure the freeze wasn't caused by something else?

Question: Does pressing clear make the MIDI position start over?

yes

If you save a MIDI file, then go back, monitor more MIDI messages and save again it new messages are not saved into the MIDI file (confirmed in eXT event list). The text file sees the changes.

works for me. keep in mind that if you played some midi, saved a file, looked at it, then came back a minute later to play more midi and save it again, there will be a minute of blank space before the new stuff. and if you looked at it in energyXT 1.x, it will break it into separate parts, so the new stuff won't be in the event list of the original part. (just my guess of what could be happening...)

Also just bumped into this. If you accidentally save the file with a wrong extension or no period (for instance I saved a file as midiMonitor,mid) and then manually correct the extension (midiMonitor2.mid), I get this error message in eXT:

as i mentioned before, if you don't specify a ".mid" extension, it saves a text file. i'd like to have the dropdown menu to select a file type, but it looks like i might have to hack juce a little to get that.

Optomadic · Post by **Optomadic** » Sun Mar 29, 2009 7:12 pm

insertpizhere wrote:it always looks for "midiMonitor.fxp" no matter what the dll is named. are you sure the freeze wasn't caused by something else?

No no that is exactly what was freezing it up. I just changed the fxp back and all was well.

insertpizhere wrote:...if you played some midi, saved a file, looked at it, then came back a minute later to play more midi and save it again, there will be a minute of blank space before the new stuff. and if you looked at it in energyXT 1.x, it will break it into separate parts, so the new stuff won't be in the event list of the original part. (just my guess of what could be happening...)

Ah ha! Yes this is exactly what is happening.. Gotta love 1.41. Makes it convenient for placing long spaced out midi parts..

insertpizhere wrote:as i mentioned before, if you don't specify a ".mid" extension, it saves a text file. i'd like to have the dropdown menu to select a file type, but it looks like i might have to hack juce a little to get that.

Hmm if JUCE handles GUI control hacks it should be easy. If not you probably have to build the diag yourself (via GUI) which may be a pain. Either way its not that big of a deal I mean its a few clicks and 3 chars right

. Or maybe you could just make the default extension blank (midiMonitor.).

nym · Post by **nym** » Tue Mar 31, 2009 8:33 pm

any plans to create an interpretation of nicfit's curvecontrol?
ive found curvecontrol to be unusably buggy....not only does it occasionally lose its saved settings (throwing random nonsensical lines across the graph curve) but it also does not allow a user to control the curve of a cc that has been converted from another cc.

ie, this doesn't work:

incoming cc: 74
cc2cc: 74=>72
curvecontrol: make 72 logarithmic.

instead, you have to curvecontrol 74 before converting it. this limits greatly the capability here for this reason:

say you want 74 converted to 71, 72 or 73 depending on the position of controller 70 -- but you only want controller 72 to have a logarithmic curve. as it stands, you cannot do this, because you MUST convert the original cc instead of its converted form

man oh man do i covet a piz curve control plugin.

insertpizhere · Post by **insertpizhere** » Sat Apr 04, 2009 3:59 pm

nym wrote:any plans to create an interpretation of nicfit's curvecontrol?

i'm too busy now, but someday... could be a few months.

but i don't understand this:

ie, this doesn't work:

incoming cc: 74
cc2cc: 74=>72
curvecontrol: make 72 logarithmic.

instead, you have to curvecontrol 74 before converting it.

i tested this and it seems to work. i can't see why it wouldn't work, since controlcurve wouldn't shouldn't be able to tell if a CC has been converted from another one or not. what host are you using, and what do you use to convert the CC?

gurulogic · Post by **gurulogic** » Sat Apr 04, 2009 5:23 pm

Hey piz,
a small request for Big Clock, time permitting of course...

It would be very handy for me if I could set loop points in the clock so that I could say have it count to 16 or 32 or 64 bars and then start from zero again. Having a really awfull internal clock myself, and being really bad at on the fly high number division

, it would help me tremendously to have this as a reference option during live performance.

Insert Piz Here

KVR Audio

piz midi plugins (windows/linux/mac)