I've been a user of the K'd HCiSO distributions of Gig Performer 5 for sometime now, and not once have I been able to get the 'Recorder' feature to behave properly. Whenever I click the recording button, it'd bring up the 'Recording Options' window (as expected), however upon clicking Start, the record button doesn't even change to a deep red to indicate that a recording session is active. A healthy recorder button from the manual will be provided. Note: none of the visual elements actually appear/change like it's shown here in my case.

While it does technically "record", the bugged (in)ability to properly stop a recording session leaves me with a runaway wav, increasing in size with little to no indication or actionability to stop it, leaving me with technically the desired the result plus a mega f$#!-ton of bloaty silence after incidentally starting yet another wasteful, titanic and silent recording session. Otherwise, I'd have to send the sesh right into the trash just to abort it before it festers any further.

I've gone over several previous update logs as well as forum searches, and not one have made mention of this unusual bug. Is this exclusive to the K'd version of Gig Performer? I am currently using version 5.0.28 as of late. I've even installed GPRelayer out of morbid curiosity, as well as reinstalling GP as a whole. Should I contact Team HCiSO myself about this issue? What can be done to have the recorder work properly? I really wouldn't want to have to get Audio Hijack booted up every time I want to record a little ditty to share with a friend, especially for how prone to clipping AH can be.

Any and all help, once again, is greatly appreciated~!

 

You could pay for the product instead of stealing it!

 

No, thanks. Besides, the sister site, audioz, is dedicated to various warez anyways. Thanks anyways.

 

You might as well just say "thanks for the bug report", or that it is an intentional behavior added to copies which have been incompletely tampered with.

 

And so, Mr. Sanctified-holier-than-thou... What would you be doing on a forum that associates with all us dastardly pirates "stealing" shit all day long? Hmm?

Pfft...

 

I haven't used the most current version of GP on the sister site. I'm still using the version posted there prior. I haven't had the issues you're describing. I use GP, and it's recording thing often and it always works as expected..

GP itself does have a lot of weird things about it, but I think it's from it having that homemade vibe rather than it being buggy. Ugritone stuff is like that too, in fact it's driving me nuts at the moment. Trying to automate KVLT Drums II is a massive pain in the ass.

But maybe it's just me. I use Digital Performer, for the last few years it's been an unbelievably buggy piece of shit on my system, I have non stop problems with it. That's on the sister site but not even k'd, it's just the legit version with a serial. But other people don't seem to have as many problems as I do. So maybe for someone with a...let's say curiosity, in the sister site...maybe that causes problems like these, where other people don't have them.

 

Thanks for your input. Gig Performer works brilliantly as a VST host, better than some others, and I couldn't ask for a better VST host if it weren't for the amazing low CPU usage. If I may ask, are you using a different Mac version? I'm on Ventura using a 2017 Intel iMac. I'm probably going to get the trial version to see if it's simply a side effect of either my system or the cracking process.

 

I'm on an 2021 M1 Max Mac Studio yeah

 

It seems to be an issue with the software... I can confirm this. I decided, "f#£& it", and got the 5.0.40 14-day trial version, and yet I'm exhibiting the same issues. It's very likely an issue with the Intel version, cracked or uncracked.

 

I don't use it, or Mainstage because I do not have reason to try them.

Yes, you can't really immediately say the demo has the same issue as the one which just detected it was tampered with. You would need to make very sure you have cleaned up before installing the demo. Or you need to try it on a different machine that has never had either installed. Otherwise you might just be seeing one carry over into the other.

Plus, we also have developers who are focusing on Intel or Arm versions. Maybe they develop both independently, but I wouldn't assume that. Apple has all the resources in the world and probably would; but maybe not some little "mom and pop shop" developer. MacOS has been whipping through OS versions very quickly, in the greater scheme of things. So there are users on way more different configurations still, and will be for quite some time into the future. Wait until there are PC ARM machines out there, because it is going to be comedy.

I'd still go with an Apple product if it was going to be powering a live gig setup. It may have less features, but it will surely be missing any "random new security features." Just knowing the potential this guy's "funny little subroutine" exists in the application would make it unacceptable for many live performers who would of course, be legit users.

 

Last edited: Feb 23, 2025 at 2:18 AM

I've taken your advice at heart, going as far as removing associated private/var files (don't worry, I didn't single-handedly take a bite out of my Apple, pun intended) may've found the solution... If I recall correctly I never had done anything with regards to the settings file located in my user's 'Application Support' folder. Deleting it, I tried the latest genuine version, let it roll through my plugins, etc. and after going through the activation window (without activating lol), and clicked the record button and began the recording, it began recording properly! Hoping it wasn't merely a fluke, I reinstalled the K version with the newly generated settings file, and lo-n-behold, it works finally.

If I recall correctly, I had used K'd versions of Gig Performer 4, so the older settings may've carried over, effectively screwing up the recorder to begin with.

Update:
It was a matter of wether an audio input was armed or assigned for the recording, which is odd...

 

You should try the Mac app called Find Any File, if you don't already know it. It can easily find files like plists and so on, which can sometimes be a chore to find manually. Sometimes a failed version of something can alter other files it has permissions to. You can always lock them if you figure something like that is going on. They can do stuff like that to even just prevent people installing a demo multiple times.

Cleaning up before new installs can just save yourself time in the long run. "update only" versions being the exception.