VGM export doesn't work

[NUKELEDGE]

I have tried to export as a .VGM file but the file is never created, and I am sure my notes are in the right place.

[Corthax]

Same here. VSTi logging doesnt work for me (logging notes are triggering fast vibrato). Fl plugin logging works, but resulting vgm is pitched down by a whole tone or something, including pcm.

[superjoebob]

This should be fixed in v 1.13, sorry for the trouble!

[crazygoji]

I've been having this problem too, pretty sure I have 1.14

[dancovich]

I'm using version 1.16. Right now I'm using the 64bit VST version with Reaper.

I'm setting note C0 at 1.1.00 with velocity zero and note C#0 at 4.4.99 also with velocity zero, but although I can hear the music just fine the VGM isn't logged.

I tried moving the other notes a little further and also tried changing the channel of the special notes at C0 and C#0 to no avail.

[Corthax]

I'm setting note C0

In Reaper u should use C-1 and C#-1

[dancovich]

In Reaper u should use C-1 and C#-1

Holy cr*.... Thanks man!

Just curiosity but why is that? Does Reaper label the same MIDI note that would be C0 in other DAWs as C-1 or is there some special handling for Reaper by the plugin?

Anyway, thanks, you really saved me there.

[Corthax]

Thats just the different way of naming same midi notes.
https://forum.cockos.com/showthread.php?t=126452

[dancovich]

Thanks for this link. It's one of these things I was completely unaware of even though I do mess with MIDI from time to time.

A tip for the developer: Even though the plugin does mention you should use MIDI note 0 (how did I miss that?) it calls the note C0. Maybe it was just an issue for me but perhaps the dialog should either remove the note name and just say "MIDI note 0", or give a little tip that different DAWs call that note different names.

Ex:

Code: Select all

Once you click OK, VGM logging will begin at MIDI note 0 (either C-2, C-1 or C0 depending on your DAW) and end at MIDI note 1. The looping point will be set by MIDI note 2.