• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
New Client Fails with Previously Working Gear Config
#7
I must say that as a strong supporter and advocate on this forum in recent weeks, I am getting pretty frustrated with the JamKazam Windows client. I too am having to uninstall the client, which, by the way, does NOT completely remove the previous configurations. I even cleaned the Windows registry of all JK references. I stopped short of removing the ASIO driver for my last good working audio interface, as I use it for other audio applications, but after reinstalling the client, I am still stuck without a working audio config in JK. I guess I am forced to take this drastic step if I have any hope of JK working again, on a machine where 6 months ago it supported 5 tracks of audio & midi VSTi without a glitch. No other Windows audio app would dare to require the removal and reconfigure of the audio interface "Need a new tennis racket? Step 1: cut off your hand and grow a new one..."
In my opinion, the JK Team's ONLY priority is to develop a stable working software client, one that doesn't hang in "(Not Responding)" state after every mouse click, and crashes every other click. The rush to roll out 3 client updates in as many weeks has caused more harm than good, especially to those of us who have been around since before the pandemic. At this point I cannot recommend this platform to even the most patient of musicians. Focus on the basics, folks, and help your existing client base stay connected and thru your product evolution (or better yet, maintain compatibility thru your lifecycle), or you will lose us all, old guard and newcomers alike...
  Reply


Messages In This Thread
RE: New Client Fails with Previously Working Gear Config - by blandis - 05-15-2020, 06:50 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)