You are not logged in.
Dear visitor, you are currently not logged in. Login or Register as a new user .
You're joking, right? The virus was just an analogy. Who said anything about wanting to find a prob? I noticed it, recorded it and it's there. I'm trying to help making this product as good and as stable as it can be - that's why I am reporting issues. I even send them my soundcard to fix the SP/Dif prob back then. We can just ignore probs like that and we'll be stuck in beta forever. Think about it
Sorry man, I still don't get what it is you're saying.You didn't read what I wrote. Too busy to READ THE POSTS. No-one ever suggested there wasn't a problem. I said people are just wading in without reading the information. Of course we'll never get out of beta if Kemper act like posters here
That's really important right here. So, you went from 1.0.4 to 1.0.6? You skipped 1.0.5. did I get this right? This might be important for support - so they know where to look
I did skip the update as I had several gigs planned and did not what to have issues with the wha cc...
That's really important right here. So, you went from 1.0.4 to 1.0.6? You skipped 1.0.5. did I get this right? This might be important for support - so they know where to look
I did skip the update as I had several gigs planned and did not what to have issues with the wha cc...
Thanks - that should pretty much confirm that 1.0.5. generated the prob.
Yes I have skip 1.05
Do you have a EQ in your rig? Have you tried to bypass it, save the rig and try again to switch between rigs. Perhaps the EQ settings are not recall properly![]()
![]()