Polyphonic Guitar to MIDI VST/AU "MIDI Guitar"- BETA TEST

[JJunkie]

Are you sure it hits the same VST again?

Now that you ask, I don't think so. My problem was that there are something like 50 separate BlueCat plugins. So scanning and skipping through all of them would take a long time

[JamOrigin]

Ok we will get back soon with some scanner improvements. We also have to find out why some VSTs fail to load.

I noticed the cpu usage seems quite a bit higher (more than double I'd say). Is this something that will improve in later versions?
I am using six mono instances though, so I realise I'm probably more concerned about this than most...

Yes, CPU went up a bit, especially at very small buffersizes. I believe we can take it back again to iOS level later (the engine of 0.6 runs on a single core iPhone4).

[scook]

Yeah, I have been eliminating folders to get the scan to complete (which it is yet to do). It appears to have problems with 32bit plugins (I am running 64bit MIDI-Guitar). It also has issues with plugins that I used in previous MIDI-Guitar versions, for example Rapture.

[JamOrigin]

Yeah, I have been eliminating folders to get the scan to complete (which it is yet to do). It appears to have problems with 32bit plugins (I am running 64bit MIDI-Guitar). It also has issues with plugins that I used in previous MIDI-Guitar versions, for example Rapture.

Ok, thanks for reporting.

We will take a look at the scanner once again in the next few days,

[chucky5p]

Hi to everyone. This is my first post on KVR First, congrats to Jam Origin for such an amazing plugin! Even if it's still in beta, any guitarist can see the enormous potential this Guitar-to-MIDI plugin will bring. After trying version 0.6.1 and then 0.7.0, I was so impressed (and had so much fun) that I decided to buy the plugin yesterday (my only regret is not learning about this plugin when it was on sale at 70$). AFAIC, I'll try to bring as much constructive feedback as I can because I believe this plugin has great potential. Again, thank you J.O.!

Ok... so onto my first feedback; it's the most obvious bug ATM: v0.7.0 as well as v0.7.1 produces this error on my system when trying to scan my VST plugins directories (I have 2 VST dir, one on C drive, the other one on M drive, an SSD disk)



The error specifies the directory ZynAddSubFX on my C drive but such directory does not exist on my system. Also, when the program is searching, it's stuck in a loop and keeps trying to detect the same plugins and I have to cancel the search.

Chuck

[JJunkie]

Hi to everyone. This is my first post on KVR First, congrats to Jam Origin for such an amazing plugin! Even if it's still in beta, any guitarist can see the enormous potential this Guitar-to-MIDI plugin will bring. After trying version 0.6.1 and then 0.7.0, I was so impressed (and had so much fun) that I decided to buy the plugin yesterday (my only regret is not learning about this plugin when it was on sale at 70$). AFAIC, I'll try to bring as much constructive feedback as I can because I believe this plugin has great potential. Again, thank you J.O.!

Ok... so onto my first feedback; it's the most obvious bug ATM: v0.7.0 as well as v0.7.1 produces this error on my system when trying to scan my VST plugins directories (I have 2 VST dir, one on C drive, the other one on M drive, an SSD disk)



The error specifies the directory ZynAddSubFX on my C drive but such directory does not exist on my system. Also, when the program is searching, it's stuck in a loop and keeps trying to detect the same plugins and I have to cancel the search.

Chuck

JO already explained, when it scans a vst that won't load it restarts the scan but blacklists the failed VST. If you have many VSTs that wont load then this process will take a long time to complete

[chucky5p]

JO already explained, when it scans a vst that won't load it restarts the scan but blacklists the failed VST. If you have many VSTs that wont load then this process will take a long time to complete

Thanks for your reply. Yes, that explains the second error I reported (even though in my case the "black listing" never seems to complete and the program keeps restarting the whole scanning process over and over) but this does not explain the first error I reported about the missing cfg file in an nonexistent "ZynAddSubFX" directory (see the screencap included in my first post)

Chuck

[Daggilarr]

Would it not be possible to have a system that first lists all plugins and gives a check or uncheck option of which to load. I have many plugins that are of no relevance to midi guitar. I realise this may not resolve this problem but would be a useful feature.

[StickyWicket]

Would it not be possible to have a system that first lists all plugins and gives a check or uncheck option of which to load. I have many plugins that are of no relevance to midi guitar. I realise this may not resolve this problem but would be a useful feature.

+1

I also like the more simple one of manually choosing which VST to use (i.e. V.6.1).

V.7.1 is more responsive and the feel is so much better (well done!!), but unfortunately, I can't access any of my VST's due to this scan issue. I'm using the Win32 and so have only tried it in standalone. I'm looking forward to the next scan/fix update.

[chucky5p]

JO already explained, when it scans a vst that won't load it restarts the scan but blacklists the failed VST. If you have many VSTs that wont load then this process will take a long time to complete

Update: It seems I owe you an apology! After further debugging my 1st error (ZynAddSubFX) it looks like it is also related to the MIDI Guitar scanning issue. ZynAddSubFX is a soft-synth VST that I rarely use, and I found out that it wasn't properly configured on my PC, thus producing the 1st error. But I never noticed any problems with ZynAddSubFX before starting to use MG v0.7.x because the other programs that use VSTs on my PC "behave" much better than MG when they encounter problems loading VSTs.

Since I don't absolutely need the stand-alone mode of MG, until this issue is fixed I'll simply use my DAW (Reaper) for loading instruments VSTs when using MG v0.7.x.

Chuck

[FrettedSynth]

Late to the party, was going to mention the scan issues but it is being worked on now. Pretty busy this weekend will give more next week.

After about an hour of play it feels much improved compared to v0.6 love it!

Joe

[RunBeerRun]

I'll try to download it, my slow connection limits what I can do.

Is there any way to download only 32 bit, in the future? There's tons of stuff already packed into a single plugin.

[FrettedSynth]

Good stuff!
Latency feel improved to prior versions.
Velocity tracking feels very dynamic.
Tracking not much to say other then your great.
Sustain options love the hold without stacking, Thank you.
Pitch bend feels much improved, still get some glitches.
Dynamics automation is great, might be nice to have a user defined CC# slot.
All in all big improvement IMHO.

Bad stuff
I'm getting double trigger when I release notes on the B or E string, no problems with this in 0.6.1
The tuner does seem slightly off compared to C-tuner96, but the poly is real cool.

Other then that again great update, thank you for giving me the chance to test.
Oh yeah! would it be too hard to make it so I could drag and drop a VST .dll file to the instrument or effects section to load?

Will let you know if I find anything else.
Joe

[ariajazz]

OK Here are my experiences with MG v 0.7.1

I'm having problems scanning for vst and vsti in stand alone mode. It seems that MG cannot scan plugins that are in folders within another folder. In my case I have a general PLUGIN folder located at root in C: partition where I have many other subfolders containing the dll files for the vst an vsti plugins. I also have some dll files that are in that general folder but not in any other subfolder. This general folder is called VST-PLUGINS. The thing is that I have to add all these subfolders one by one with the folder management feature of MG in order to get the plugins recognized by MG. This is tedious considering that I have dozens of plugins in my system. The rare thing is that when I add the general VST-PLUGINS folder and proceed to scan it does not recognize nothing not even those dlls that are alone in the general folder (not inside the subfolders) MG scanning get stuck in many of the plugins requiring me to use the skip button many times, at the end of the proccess none of the plugins are recognized.

Tested v0.7.1 as plugin inside SENSOMUSIC USINE v5.20 as host and tracking was terrible (MG 0.6.1 worked fine). A lot of false notes, noises and artifacts. Pitch bend also worked bad and inaccurate. Sensitivity is now out of control, too many makes any softsynth to have stuck notes being neccessary to press the PANIC button of the synth. I think this parameter iss too sensitive in this new version.

Another problem in stand alone mode is that it is very hard to select the proper input channel due to deficient design of the input selector (those next to the arrows) it is imposible to read the channel numbers, the text field is too short so it only displays a few characters of the name of the sound card (in my case it only shows ESI M... for an ESI MAYA 44 XTe sound card. After clicking randomly on those arrows and circles I got an input signal. But I really dont know what I'm doing.

I'll be tweaking MG some more tomorrow ans see how can I improve on its performance, however I feel that v 0.6.1 permormed better.

[karozas]

OK Here are my experiences with MG v 0.7.1

I'm having problems scanning for vst and vsti in stand alone mode. It seems that MG cannot scan plugins that are in folders within another folder. In my case I have a general PLUGIN folder located at root in C: partition where I have many other subfolders containing the dll files for the vst an vsti plugins. I also have some dll files that are in that general folder but not in any other subfolder. This general folder is called VST-PLUGINS. The thing is that I have to add all these subfolders one by one with the folder management feature of MG in order to get the plugins recognized by MG. This is tedious considering that I have dozens of plugins in my system. The rare thing is that when I add the general VST-PLUGINS folder and proceed to scan it does not recognize nothing not even those dlls that are alone in the general folder (not inside the subfolders) MG scanning get stuck in many of the plugins requiring me to use the skip button many times, at the end of the proccess none of the plugins are recognized.

Tested v0.7.1 as plugin inside SENSOMUSIC USINE v5.20 as host and tracking was terrible (MG 0.6.1 worked fine). A lot of false notes, noises and artifacts. Pitch bend also worked bad and inaccurate. Sensitivity is now out of control, too many makes any softsynth to have stuck notes being neccessary to press the PANIC button of the synth. I think this parameter iss too sensitive in this new version.

Another problem in stand alone mode is that it is very hard to select the proper input channel due to deficient design of the input selector (those next to the arrows) it is imposible to read the channel numbers, the text field is too short so it only displays a few characters of the name of the sound card (in my case it only shows ESI M... for an ESI MAYA 44 XTe sound card. After clicking randomly on those arrows and circles I got an input signal. But I really dont know what I'm doing.

I'll be tweaking MG some more tomorrow ans see how can I improve on its performance, however I feel that v 0.6.1 permormed better.

I agree with all the above