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

[cymazic]

Sincere apologies if this has been covered previously but , I seem to be having problems scanning for VST plugins from within MidiGuitar. I keep getting an "Invalid Executable" error when I try to scan for VST's.
I have tried just using the standalone version , and I have also tried from within the plugin version ( which then prompts to open the standalone). Both approaches result in the same "Invalid Executable" error.
I never had this problem in the early versions as far as I recall.
Im dying to check this latest versions' tracking improvements and will definitely be a future buyer once I can solve this scanning prob.

Thanks a lot and apologies again if this has been covered before but its a pretty big thread to go through page by page ( a fitting testament to MIDIGUITAR's popularity )

[RunBeerRun]

It's not bad for creating a wall of noise, but as far as I strum, it's got to be real deliberately for it to pick up all the notes.

[derivative]

*update*

- 0.8.2 is in regard of hammer-ons much more responsive than 0.9.0 (it's almost NOT working!) but was not usable (for me) because it triggers too much other notes.

- version 0.5.3 tops all other versions when it comes to staccato notes on open strings

- for some strange reason version 0.8.2 is not working correctly anymore since i'm using version 0.9.0. v0.6.1 still working fine.

- slightly better responsiveness with fast string runs with version 0.9.X

- problems i got with staccato notes where dependent of my playing style in conjunction with the longer sustain in v0.9.X (which still is a mystery to me why this should affect note recognition in monophonic mode)

[tony_12345]

I downloaded the latest version today, and I'm sorry to say version 0.5.3 is still better. Latency is as good as 0.5.3, but for some reason tracking in 0.5.3 is better.

[Peevy2000]

Using version 0.8.2 in standalone with Logic Pro X is pretty unusable, I'm getting a lot of latency. That's with Midi Guitar at 128 & Logic at 256/128/64 samples. Pity because my bass guitar is out of action & I was gonna buy this to trigger Scarbee to use on an EP I'm working on.

[JamOrigin]

Thanks for the feedback, guys!

First, seems we broke plugin scanning in a last minute change before the release - we will fix that in 0.9.1 today.

But more importantly, we really want to get to the bottom of why some have a better experience of tracking in previous version (version 0.5 and 0.6 especially). We are testing on a vast amount of real user recordings and also synthetic generated recordings and we see that 0.5 cause generally lots of spurious notes whereas 0.6 and 0.9 does not. On the other hand 0.6 has a slightly higher latency than 0.5 and 0.9. 0.9 comes out as a winner on all our recordings. So it looks like we have to improve our methodology as well.

We really want to get to the bottom of this. Please help us by sending a small wav recording of a chord or something very simple where 0.9 it mess up. We will take a serious look at it and try to get to an understanding of how your guitar behaves .

One guess is that those having problems have a low volume input and sensitivity all way up to 100? If this is the case put gain on input and let us know if situation improves.

EDIT: Another - maybe more likely - explanation could be that later versions of MG have generally been taking up more CPU resources and maybe some of you feel that v0.5 and 0.6 are better because they have been within your CPU budget, whereas new version is not? Mind, this is not trivial to measure because CPU usage is spiky and thus you cant see it on your process monitors and MG will skip buffers and thus cause recognition problems if spikes are too high. It would be nice to know if some of you have fast i7 processors to invalidate this point.


Thanks again.


EDIT:
Peaevy2000, some have reported that the virtual midi from MG standalone to logic cause extra latency. We are looking into using the IAC driver instead. Otherwise try to use the MG AU in Logic with only audio outputs and let us know if that helps.

[Peevy2000]

EDIT:
Peaevy2000, some have reported that the virtual midi from MG standalone to logic cause extra latency. We are looking into using the IAC driver instead. Otherwise try to use the MG AU in Logic with only audio outputs and let us know if that helps.

Thanks for the quick reply. Yes the latency & tracking is much better using MG on an audio track (using Kontakt/Scarbee bass within MG) But I'd prefer to have the convenience of being able to record the midi. Glad to see your looking at other options for Logic users

[cymazic]

Thanks for the feedback, guys!

First, seems we broke plugin scanning in a last minute change before the release - we will fix that in 0.9.1 today.

Great , Thanks for the quick reply , I look forward to testing the fix.

[JamOrigin]

Just a quick update with a fix for plugin scanning:

Win: http://jamorigin.com/midi-guitar/MIDI-G ... .1-Win.zip
Mac: http://jamorigin.com/midi-guitar/MIDI-G ... .1-Mac.zip

[Stevie666]

Hi
I'm new to the forum
First off thanks to the JamOrigin guys for making the most exciting software I've seen for a long time.

I tried it a few weeks ago and couldn't resist buying it.

It works surprisingly well but I'm a bit confused by some users reporting far better results than I'm getting.

Latency: I've seen comments that some users are getting no noticible latency. I'm using the stand alone version through a Line6 UX2 into a reasonably recent dual core 2gb PC buffer = 128 and I'm getting pretty noticible latency. I tried Asio4all at 64 buffer but it only improved slightly. Am I doing something wrong?

Response: I don't fully understand how the gain controls and sensitivity interact to get the best response. I'm running a Schecter/EMG81 direct to the UX2 unprocessed into the Midi Guitar software. Can anyone suggest a good setting for sensitivity and gain?

[Stevie666]

One more thing, Sometimes when I play chords or apreggios the notes come out in the wrong order, like its getting stuck for a moment then spews out some notes very late. Is this what other people are calling jitter or is this something else? How can I improve this?

[ariajazz]

I've been testing MG 9.1 for a while this morning. Well, things are getting better and worse at the same time. Tracking has been improved in terms of latency. It feels ok and sensitivity setting is working much better than in previous versions (at least for me). Dynamic playing is also more percetible with a nice response from the synth, someting that I never felt in other versions. Soloing in both poly and mono modes responds very good, not perfect but very playable, and that's enough for now.

The bad things: this version is reacting weird when strumming chords. First, it still being hard to make all notes sound smooth, nice and above everything make all notes sound in a "compact" way, specially performing fingerstyle. In many cases MG is tracking wrong notes, not spurious notes but WRONG ones. For instance: when playing an A13b altered chord MG adds a 9b note after a half a second or so. The funny thing is that this 9b it is an altered tone that can be fitted into the chord and the result is musically aceptable but in other cases the note(s) added are not pleasant and out of harmony.

I haven't tested any other features and characteristics of this version since I'm now focused in the tracking aspect which I think is the most important goal of this project.

I'll be testing this new version more extensively later on and will be back here to post new conclusions.

[ariajazz]

One more thing, Sometimes when I play chords or apreggios the notes come out in the wrong order, like its getting stuck for a moment then spews out some notes very late. Is this what other people are calling jitter or is this something else? How can I improve this?

This is happening to me too...

[jas]

Version 9.2 Beta makes a huge difference on tracking accuracy on notes within the guitar range. However, when triggering bass virtual instruments in Kontakt I get inaccurate or doubled notes playing. I had to slightly (5%) lower the sensitivity setting on my system using the standalone version in front of Reaper and Protools 11.1.

[FrettedSynth]

New versions Cant wait to test