FWIW, I never installed any 32bit version of MIDI guitar. Never had any of the problems either one of you have described.

Hi cecelius2   I still have no joy in 64 bit. If I try to load a vst that I have working in 32 bit it opens the 32 bit MIDI guitar program overtop of
 
the 64 bit version (weird huh). If I then close the 32 bit version the vst in the 64 bit has crashed and not loaded. 

As you said it is beta and I am sure these issues will be worked out. I still think this is a buy.    

Thanks for taking the time to explore this.  I will post back with any other info I can come up with.     Dan

scook

FWIW, I never installed any 32bit version of MIDI guitar. Never had any of the problems either one of you have described.

You know I have been on this forum for a long time (previously under Cecelius andn then I had log in troubles and had to rejoin in 2009).  I have seen many users report serious problems with Sonar, or vst plugins, but I have been very fortunate to have had very few problems and these being far between.  So the fact that I am having some minor troubles does not really bother me.  It will get fixed and bugs will be worked out.  Who knows if it is my MB or brand of memory or MOTU audio card....????  Luckily I have found good workarounds for use as a standalone as just posted and to be used in conjunction with Sonar as posted yesterday.  It's all good as they say.  And it will get better.


      I am really impressed with the tracking speed compared to hardware based midi guitar devices.  I guess it is the fast audio drivers for the sound card.  Since it uses them to input the guitar signal and they are getting faster and faster with less and less latency, this Midi Guitar is a great investment and it will only get better.  


As an aside--
I did notice that I can only set the samples within Midi Guitar down to 128 even though I can run my MOTU 838mkii down to 64 samples.  When I lower the sample below 128 down to 96 or 64 on the audio card, the Midi Guitar does not recogniize that.  Is 128 it's bottom line right now?  Still my latency is showing at 2.9ms--that is what the Midi Guitar is reporting.  That is great.  Just wonder if it will eventually allow 64 sample and even less latency.

The MIDI Guitar documentation on the Jam Origin website http://www.jamorigin.com/...ws-Mac/help/index.html recommends 256 samples, I run at 128. For whatever reason there is no mention of lower settings.

scook

The MIDI Guitar documentation on the Jam Origin website http://www.jamorigin.com/...ws-Mac/help/index.html recommends 256 samples, I run at 128. For whatever reason there is no mention of lower settings.

Thanks.  I had read that but forgot it already.  128 is working fast so this is good.


I think I am going to download all the versions of Midi Guitar since the developer has provided links to them going back to 5.3.  Then I am going to experiment and see if I can just start over from the beginning.  Load 5.3 and see if it works as prescribed in Sonar just as a vst.  Then update successively through 6.1, 7.2, 7.3, 7.4.  Perhaps, and I am just hoping, that by uninstalling and then reinstalling successively that i might get it to work the way that you guys have it working just as a DAW vst within Sonar.  If not, at least I have it working in a way that might be convoluted, but it realy only means that I have to have it running outside of Sonar as standalone and just use loopmidi or LoopBe1 porting it into Sonar to trigger synths and more importantly to record the midi tracks.


Again, thanks for all the info and putting up with this ongoing journey.

It turns out there is a problem installing both the 32bit and 64bit versions. Sounds like the problem is triggered by having them in the same directory. Expect a new release soon to fix. From the kvr thread the dev states:

So it turned out that the scanner problems are caused by the filename "MIDI Guitar 64.exe"...

It turns out that if an app ("MIDI Guitar 64.exe") wants to launch a process (in this case the scanner which is also in "MIDI Guitar 64.exe") - Windows will first try to run "MIDI.exe" and "MIDI Guitar.exe" before the more sane approach of "MIDI Guitar 64.exe". So the scanner launch the 32 bit version if you have it in the folder... and things start to go even more wrong from there because then it might find 32 bit plugins in the 64 version which won't load.

The quick fix is to rename "MIDI Guitar 64.exe" to "MIDIGuitar64.exe".

Woo Hoo  Renaming the 64 bit file worked like a champ!!  It now will scan and load 64 bit vst instruments  Thanks scook!!      Dan

While the problem is going to be addressed in the next release, I would recommend installing the 32bit version somewhere in your "C:\Program Files (x86)" directory tree and the 64 bit version in your "C:\Program Files" tree, just like most software installers would do. Better yet, if you do not need the 32bit version, don't install it. I was unaware of the bug because, like I said above, I only install the 64bit version.

scook


It turns out there is a problem installing both the 32bit and 64bit versions. Sounds like the problem is triggered by having them in the same directory. Expect a new release soon to fix. From the kvr thread the dev states:

So it turned out that the scanner problems are caused by the filename "MIDI Guitar 64.exe"...

It turns out that if an app ("MIDI Guitar 64.exe") wants to launch a process (in this case the scanner which is also in "MIDI Guitar 64.exe") - Windows will first try to run "MIDI.exe" and "MIDI Guitar.exe" before the more sane approach of "MIDI Guitar 64.exe". So the scanner launch the 32 bit version if you have it in the folder... and things start to go even more wrong from there because then it might find 32 bit plugins in the 64 version which won't load.

The quick fix is to rename "MIDI Guitar 64.exe" to "MIDIGuitar64.exe".

Thanks.  This helped with the scanning problems.  I put the different files in 32 bit and 64 bit folders respectively.  Then scanned.  Now I can launch softsynths from Midi Guitar in standalone mode.  It now even loads my GForce MTron Pro 64bit, which previously crashed the program.


I have not tried to run Midi Guitar as a vst (.dll) within Sonar.  Hopefully this might help with that hiccup on my system. 


I read on the KRV site that there is a v7.5 expected tomorrow that will address this and fix this  problem of scanning.


Thanks Scook for posting this.  

Hi Everyone,

I'll be visiting this thread once in a while if you have questions, suggestions or problems with our MIDI Guitar software. 
We generally try to base our developments on real users needs, so we are always happy to get feedback.  

As mentioned we are posting a yet another update tomorrow with more fixes.

As a quick-fix for plugin scanning problems, please rename your exe to something without spaces (ie. "MIDI Guitar 64.exe" to "MIDIGuitar64.exe") and make sure you rescan. 

Best
Jam-O.