

Thanks. I had not one but two bad USB cables. Replaced those. Able to connect. The MS50G box comes up with effects list. The other problem solved too-thank you. I had the G3 connected also. Which is where that midi error message came from. Now I can get the onscreen graphics to launch like he shows in his YT demo of zoomlib.NucleusX wrote: ↑Tue Jan 23, 2018 3:28 pmSome have said that connecting your pedal "after" program launch can resolve this. I also noticed that some pre-existing midi
software's, drivers, and hardware, can interfere with communicating midi to them. Also verify that the cable is not the issue, as
there are standard USB "charging" cables, and USB "data" cables. The data type cables have all the pins connected internally
throughout the cable, where as the charging ones leave a couple pins unconnected, which inhibits proper USB communication.
Thanks Jim. I will give it a test drive!Jim_Fogle wrote: ↑Fri Jan 26, 2018 12:55 pmHave you tried jBridge for your VSTs? As the name implies it is a bit bridge that allows 32 bit VSTs to work in a 64 Bit environment or let a 64 bit VST work in a 32 bit setting.. You can demo for free and should you decide you like it the cost is 14.99€ or about $10 US.
https://jstuff.wordpress.com/jbridge/ NOTE: the paid file is DOUBLE encrypted. It is sent as a 7up compressed file which extracts to a compressed zip file which extracts to an executable file.
MISTAJONAH wrote: ↑Fri Jan 26, 2018 1:20 pmThanks. I had not one but two bad USB cables. Replaced those. Able to connect. The MS50G box comes up with effects list. The other problem solved too-thank you. I had the G3 connected also. Which is where that midi error message came from. Now I can get the onscreen graphics to launch like he shows in his YT demo of zoomlib.NucleusX wrote: ↑Tue Jan 23, 2018 3:28 pmSome have said that connecting your pedal "after" program launch can resolve this. I also noticed that some pre-existing midi
software's, drivers, and hardware, can interfere with communicating midi to them. Also verify that the cable is not the issue, as
there are standard USB "charging" cables, and USB "data" cables. The data type cables have all the pins connected internally
throughout the cable, where as the charging ones leave a couple pins unconnected, which inhibits proper USB communication.
Users browsing this forum: No registered users and 1 guest