Yes, this is the curse for small developers:
Windows will warn until the installer has been used more broadly. It’s very helpful if anybody will “report this file as safe” after downloading it.
Here I just had to select “keep it” in downloads.
windows 10 22H2 / 19045.4651
no problems with download. all ms virus.- scanning processes are on.
starting the installer says ‘unknown company’ cause there is no sig or wrong sig. (i abort the installer cause later i will work with mg2)
downloaded with mozilla firefox.
mh think to install. loosing MG2?
I know the windows users are just now getting access, but are we going to see a new Mac beta version soon? Trying not to be too impatient… 
Yes, Mac 3.0.50 is ready to go, but lets just wait a day or two to see if there are any general problems.
1 Like
Thanks, yes. As mentioned Windows is currently cautious and will warn about the download. It will get better as more people download and report it as safe. We’ll also look into signing it with Azure or something.
From the Linux world… getting closer it installed with no issue except it will not load the standalone (still need some time looking at that issue, can not find the install file)
Only loads one of the vsts… since yabridge won’t load it I assume it was the vst3.
Steve
1 Like
initial checks and confirmations:
licence activated automatically (see “buy”)
MG3 window perfectly adapted to screen size
Plugin scan:
default locations 157
custom folder “C:\Program Files” +385
other custom folders +450
(Scuffham Amps S-Gear in default folder still does not work but works fine in custom folder “C:\Program Files\Scuffham Amps\S-Gear”)
Total scanned plugins: 992 in a relatively short space of time. 
Where are they?
1 Like
Downloaded reaper for windows.
Vst works
Haven’t checked the stand alone yet.
Maybe 
I will need to humble myself to run it in 
Wine.
Looks a lot different
Thanks
Steve
2 Likes
Did some preliminary testing of preset changes in the live host Cantabile 4 and it’s working great so far. I wasn’t successful with MG2 and am pleased that MG3 now works for this host. More testing to come but looks promising.
1 Like
MG2 has been working for years in Gig Performer but I don’t think I’ll be replacing it with MG3 in the hundred or so Gig files currently in existence.
I’ll only be switching to MG3 in new files to come, as MG2’s tracking suits me perfectly. 
1 Like
I tried to follow the Mac video which was posted to configure MG3 in Studio One on a PC. For some reason it’s not showing up in the External Devices list to add as a New Keyboard. It does show up as an input device in the song. Bug or suggested different process to add?
Right, only AUs on Mac will create an external midi device. VSTs (Mac and PC) will send MIDI out directly, so you need to route that MIDI from the MG3 VST audio track to an instrument track.
We have yet to make windows specific guides where they differ from Mac versions.
Makes sense now. Thx
The setup that should work for PC (the VST one, that is) start at 3:14
Studio One is problematic however, as it doesn’t allow for MPE to be sent directly from the AUDIO channel (when you are using the VST plugin). But it is a Sudio One thing unfortunately.
2 Likes
I’ve been using Studio One Pro since v2, but just picked up Bitwig Studio 5, which has great MPE support. Copacetic! 
Well, all DAWs seem to have their own peculiarities when it comes to MPE handling and BITWIG is no exception. They have this to say about their DAW and MPE:
"The way MPE works in Bitwig Studio is that MPE from a midi controller gets translated to Bitwig’s per note expressions, and those are being recorded in clips and used to play the internal Bitwig instruments. When playing back recorded notes with note expressions to VSTs, it converts it back to Midi MPE before sending it to the VSTs.
But if you generate MPE Midi within a device chain and then send it directly to our internal devices, there is no translation to the note expressions and the devices are currently not completely optimised to receive pure MPE Midi date instead of note expressions. This is something we might improve on in the future."
And MG3 is most likely a case where we generate MIDI within a device chain and send it directly to the internal devices, so however great BITWIG is for external MPE controllers, we still have a problem here. It remains to see when (if) it gets sorted out.
2 Likes
From the Linux corner,
Haven’t got the standalone to load in wine yet…check that later at least it tried to load in a terminal.
Was testing the vst and the lic nag was on fast time.
Would not take email…or so I thought.
But after I put it away I found a email from support with a nice 1980s lic code in it !
Thanks and good to know it got though even tho it crashed reaper many times.
Code didn’t take… awaiting next update.
Steve
I upgraded to V3.0.50 and all working great, just one anomaly I found with the VST3 plugin, when using in Cakewalk DAW, Plugin working great until I noticed that it was in MPE mode, working fine. I selected legacy and MG3 stopped output, at least from sending midi notes. MG3 still was showing it was getting input, just no output. So I changed the mode back to MPE thinking it would start working again, but it didn’t. The only way I could get it working again was exiting out and restarting MG3
That allowed everything to start working great. So for now I’m just leaving in MPE mode.
Windows 10
Cakewalk by Bandlab (2024.07 - build 108 64 bit)
Midi Guitar 3 - V3.0.50
Thanks, Great work !
1 Like
