Polyphonic Guitar to MIDI VST/AU "MIDI Guitar"- BETA TEST
-
- KVRist
- Topic Starter
- 155 posts since 10 Jul, 2012
Maruuk,when there is only one buffersize available it is always because your audio driver insist on having full control and has a its own app / control panel where you set its buffersize and other settings.
-
- KVRist
- Topic Starter
- 155 posts since 10 Jul, 2012
The internal buffers used are surely not alone determining latency, its just a small part of the equation, but your latency results sounds like they are not typical.
-
- KVRist
- 45 posts since 7 Jul, 2012
JamOrigin wrote:Thanks everyone for all the feedback!
I've been away for one month in order to finish off version 0.8, which should be announced tomorrow. I just want to quickly answer some of the questions since then.
As for the latency discussion a few pages back. MIDI Guitar has since the beginning processed buffers that are around 6 ms (i.e. 256 @ 44.1), regardless of whatever buffersize you choose. For this reason, at 44.1Khz, 256 and 128 (divisors of 256) will process all samples ready and be are good choices for your soundcard as buffersizes. Its far from optimal, but it has made it easier for us to focus on a single target until now.
Ideally you would be able to use the same low internal buffersizes as the soundcard process, and as some of you request: be free to challenge your CPUs to any extent you want. We have already implemented this, but not thoroughly tested, and it will be a feature in 0.9.
Some of you have notices oddities at non-44.1 samplerates and (as indicated by a warning/tooltip inside MG) version 0.8 makes all samplerates run equally well. Version 0.8 will also some new major features - including our new MIDI Machine - more about that tomorrow.
Ariajazz, thanks for taking the effort to compare those latest versions! - and sorry i didn't notice earlier. Your findings about samplerates and problems with staccato are in line with our own and should be fixed in 0.8. Versions 0.5, 0.6 and 0.7 all have a different feel, and all dependent on the guitar setup and playing style and how sensitive you are to latency. To some extent we have been trying out different technologies, with the pursuit is to find the optimal best settings that works well for all with minimal setup tweaking. I hope you will find time test also 0.8.
I can inform that we have a machine here that analyse guitar sounds 24/7 and to some extent we rely on it to ensure the general quality improve in every major update (not necessary for all setups, but for most). That said, feedback from real users is critical for us.
-
AdmiralQuality AdmiralQuality https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=83902
- Banned
- 6657 posts since 10 Oct, 2005 from Toronto, Canada
256 samples / 44100 Hz = 0.0058049 secMaruuk wrote:But that doesn't explain how 256 results in your experience to a 6ms latency. On my system 256 equates to something like 80ms+.
So about 6 ms. That doesn't mean that's what your latency will be, there can be hidden latencies/buffers that aren't reported. But that's going to be the minimum. 6 ms isn't bad.
-
- KVRer
- 7 posts since 7 Jun, 2013
Given I'm using a late model Intel P4 with stock chipset, etc, and getting at most 10ms, weird-ass latency suggests a PC or driver-related error. As I mentioned, using ASIO4ALL really shaped things up over my interface's stock drivers.Maruuk wrote:But that doesn't explain how 256 results in your experience to a 6ms latency. On my system 256 equates to something like 80ms+.
-
- KVRAF
- 2236 posts since 25 Dec, 2005
unless i'm doing something wrong i still find my axon ax 50 is some milliseconds faster than the midiguitar plugin,for live performance this is crucial.
i'll probably end up buying midiguitar anyway since it is so easy to use.
i'll probably end up buying midiguitar anyway since it is so easy to use.
-
- KVRist
- 31 posts since 13 Feb, 2011
Very excited to try the new version!JamOrigin wrote:Thanks everyone for all the feedback!
I've been away for one month in order to finish off version 0.8, which should be announced tomorrow. I just want to quickly answer some of the questions since then.
As for the latency discussion a few pages back. MIDI Guitar has since the beginning processed buffers that are around 6 ms (i.e. 256 @ 44.1), regardless of whatever buffersize you choose. For this reason, at 44.1Khz, 256 and 128 (divisors of 256) will process all samples ready and be are good choices for your soundcard as buffersizes. Its far from optimal, but it has made it easier for us to focus on a single target until now.
Ideally you would be able to use the same low internal buffersizes as the soundcard process, and as some of you request: be free to challenge your CPUs to any extent you want. We have already implemented this, but not thoroughly tested, and it will be a feature in 0.9.
Some of you have notices oddities at non-44.1 samplerates and (as indicated by a warning/tooltip inside MG) version 0.8 makes all samplerates run equally well. Version 0.8 will also some new major features - including our new MIDI Machine - more about that tomorrow.
Ariajazz, thanks for taking the effort to compare those latest versions! - and sorry i didn't notice earlier. Your findings about samplerates and problems with staccato are in line with our own and should be fixed in 0.8. Versions 0.5, 0.6 and 0.7 all have a different feel, and all dependent on the guitar setup and playing style and how sensitive you are to latency. To some extent we have been trying out different technologies, with the pursuit is to find the optimal best settings that works well for all with minimal setup tweaking. I hope you will find time test also 0.8.
I can inform that we have a machine here that analyse guitar sounds 24/7 and to some extent we rely on it to ensure the general quality improve in every major update (not necessary for all setups, but for most). That said, feedback from real users is critical for us.
- KVRAF
- 5175 posts since 29 Apr, 2006
me too!
-
- KVRist
- Topic Starter
- 155 posts since 10 Jul, 2012
MIDI Guitar 0.8 beta released!
WHAT'S NEW:
http://www.jamorigin.com/midi-guitar/MI ... .2-Win.zip
http://www.jamorigin.com/midi-guitar/MI ... .2-Mac.zip
Please consider to subscribe to news on our website to keep oriented about updates.
WHAT'S NEW:
- Audio Recognition:
General tracking improvements.
Improved tracking of minor seconds.
Improved latency at non-44.1Khz samplerates. All samplerates should now perform identically.
General:
Our new MIDI Machine is now embedded in MIDI Guitar. It allows you to easily create arpeggiators, harmonizers, chord filters, or indeed any imaginable midi effect.
Added project management to make it easier to switch between sound setups. The project stores all parameters including VST instrument and -effect states as well as the MIDI Machine setup.
MIDI Learn functionality.
MIDI Program Change can switch projects at the press of a button.
Added VST/AudioUnit parameters for VST automation.
Basic velocity curve setting.
Settings are now only saved on shutdown.
Bugfixes:
Fixed issues with plugin scanner when used in plugin.
Fixed save of MIDI enable/disable in plugin.
Fixed bug where Test Piano would load after being disabled.
Fixed concurrency issues with multiple instances of MIDI Guitar running.
Fixed issues with disrupted VST plugins preventing MIDI Guitar from launching.
Many other bugfixes.
http://www.jamorigin.com/midi-guitar/MI ... .2-Win.zip
http://www.jamorigin.com/midi-guitar/MI ... .2-Mac.zip
Please consider to subscribe to news on our website to keep oriented about updates.
Last edited by JamOrigin on Thu Jul 11, 2013 1:41 pm, edited 2 times in total.
-
- KVRist
- 125 posts since 23 Aug, 2005
Thanks for the update! I've noticed, when using the standalone version, in OSX Mountain Lion, when Instrument Output is selected to None, Midi is passed onto my DAW (Reaper64). When any plugin is selected at Instrument Output, Midi is sent to that instrument and the new Midi Machine option. It's nice to have this feature (ie. arpeggiator, etc.), and it is passing the MIDI information along the chain! 
-
- KVRist
- Topic Starter
- 155 posts since 10 Jul, 2012
We have silently updated to 0.8.1 with some fixes. The link is above.
jas, yes, it should process all midi, whether its comming from the recognition system, from the host, external midi devices or the note buttons inside MG, all is chained though the MIDI Machine stack and passed in instruments
This way hardware MIDI guitar systems or even keyboard players can also use the MIDI Machine.
jas, yes, it should process all midi, whether its comming from the recognition system, from the host, external midi devices or the note buttons inside MG, all is chained though the MIDI Machine stack and passed in instruments
-
- KVRist
- 120 posts since 12 Mar, 2011
I'm out of town right now for two weeks so I'm unable to test the new versions of MG. I can't wait to get to my studio to do so. However I downloaded both new version into my laptop and am tweeking the new features. i have a few vst plugins in my laptop but no guitar here.
-
- KVRist
- Topic Starter
- 155 posts since 10 Jul, 2012
Thanks Ariajazz! Its certainly a bit quiet around here. Guess its time for holidays.
0.8.2 was just uploaded with very minor fixes. Link is above.
0.8.2 was just uploaded with very minor fixes. Link is above.
-
- KVRist
- 43 posts since 1 Aug, 2005 from On the Rhein
That was quick 
Just out of interest, what is supposed to be saved in the Project file?
Just out of interest, what is supposed to be saved in the Project file?

