After using a cracked version of Boom 2 for awhile, I decided I revert back to the latest K'd release of Boom3D on the sister-site, thinking this one incessant, infuriating issue would've been taken care of in a more later version of the software but to no avail.

Of course, I could easily just leap back into trusty ol' Boom 2 and just forget about it's '3D' successor, but I figured I'd ask here if anyone else has had the issue I'll very shortly describe and the fixes it may entail.

The audio would suddenly just shut off for no particular reason. I have Little Snitch engaged preventing any and all outgoing signals to be pinged from Boom3D itself (as the instructions stated), and yet it arbitrarily goes DEAD silent after some output is played. Yes, I did fiddle with the "sleep when no audio is being played" option, but again- the issue persists.

Is this some strange time-bomb that hasn't yet been properly cracked? Or is this simply shoddy software? Any and all info, insight and/or help would be greatly appreciated!

Thanks~!

 

Timebombs do not require internet connectivity to do stuff like this. That way they are not relying on home-calling alone. You might be getting silence from this plugin, but outputting sound is it's main purpose. Replace "dead silence" with "short audio dropouts" or the relaxing sounds of "white noise" you might expect from any expired demo plugin.

I would try to patch it again. May as well update it first

Keep in mind, you may want to clean up old installations and install from scratch, if that does not work.

 

Fair enough.

If it helps: I've downloaded older versions of Boom3D in the past (often pre-patched, by the TNT group, if memory serves?), and this issue would rear it's ugly head at any given time. Even after uninstalling the audio component for both Boom 2 and 3D respectively, as well as the actual programs themselves, the issues would persist.

Although, iirc, Boom3D apparently shares the same audio component as Boom 2 oddly enough(?), so I'd need to evaluate wether I'd not have to download the newer audio component for Boom 3D.

I appreciate the help, thus far.

 

I have never used either of them, because I almost never use any systemwide anything between the DAW output and the monitors. Only for correction purposes.

re phoning home: Since it is an application, not a plugin; you could also block it at the Mac firewall, and you could also block vendor website/s in your hosts file. Just in case your Little Snitch rules are letting it access the network, if they are at all wrong. After that you can say with all certainty that the program itself is the problem. If anything like these also have an actual .component plugin, the plugin and the DAW application should also be blocked.