Hive 1.2.1 Randomly Drops Notes in Cubase Pro (11 & 12). What could be causing this? Video example.

[UltimateOutsider]

In a project I originally started in Cubase 9.5 (no longer installed), I've discovered that my three Hive 1.2.1 instances randomly go briefly silent (drop notes). It is truly random at least in the sense that I can loop a section of the track and the dropped notes can happen at different locations on every iteration of the loop.

Here's what I've ruled out:

• it's not Cubase 12 Pro-specific, as it happens on Cubase 11 with the same project
• it's not DAW performance; my computer is not under duress, and the Audio Performance monitor never peaks, and only Hive is affected; the other instruments in the track don't drop notes
• i don't think it's a licensing or installation problem, as the plugin is correctly activated (doesn't ask for my serial number), and i just installed the most recent available build of Hive 1 this morning to see if it fixed the problem; the version I had before was 1.1
• it's not automation (no automation on these tracks, plus the drops happen randomly)
• it's not any FX tracks; the issue occurs even with all FX on tracks/bus/master disabled.

I posted a video that demonstrates the problem:

[zvenx]

Curious to know why you are using Hive 1.2.1 whilst hive is a 2.1.1 or is that a typo?

(oh right Hive 2 had a small upgrade fee).. but I imagine the issue might have been fixed in 2.1.1.. maybe download it as a demo and see if it happens there and if it doesn't time to upgrade?
rsp

[UltimateOutsider]

Curious to know why you are using Hive 1.2.1 whilst hive is a 2.1.1 or is that a typo?
rsp

I haven't bought Hive 2 yet. I was a beta tester for Hive 1 (but used my "production" serial number to activate this instance), but have not yet purchased the 1->2 update. (Curious: Does Hive 2 replace Hive 1 in projects automatically, or does it have a different filename/plugin ID like NI plugins do?)

[zvenx]

Yes it does replace automatically.
If indeed it is a bug in hive 1, i am 99.999% confident there won't be a fix in Hive 1 for obvious reasons.
Rsp

[UltimateOutsider]

Wow, this is really driving me nuts.

• I did upgrade to Hive 2 and the problem remains.
• I figured I would prepare a sample project that I could send to u-He with my support request, so I exported the patches and MIDI and created a new Cubase project with only those 3 Hive parts- and the problem doesn't reproduce. Never glitched once. So it might be a problem with my Cubase project?
• Back in the song I'm trying to finish, I bumped my sample buffer to 1024 samples (at 44.1kHz), and set AsioGuard to High. No change. I ran LatencyMon, just in case there's a bad actor driver in the background that's not registering on Cubase's performance meters. Nothing's going on there.

I guess I'm just gonna have to replace Hive with some other synth in this project. Ugh it's gonna be a pain to find 3 more patches that fill the role Hive's playing in that track.

[zvenx]

sorry... I am using Cubase and haven't experienced that issue in Hive.. They use to have that issue in Diva awhile ago but u-he corrected it sometime last year.

and I use buffer size 64 usually.

can you freeze the track?
rsp

[tasmaniandevil]

If you can send us the problematic project along with some details about your computer setup (Windows version, audio interface, sample rate and buffer size, and so on), we can have a lookt at it. Maybe we can spot the issue.

https://u-he.com/support/#contact

[UltimateOutsider]

If you can send us the problematic project along with some details about your computer setup (Windows version, audio interface, sample rate and buffer size, and so on), we can have a lookt at it. Maybe we can spot the issue.

Thank you for posting that. I was just preparing the project to send to you (freezing tracks to reduce the number of plugins Cubase would try to load) when I discovered that in this project I had some FX plugins inserted in post-fader slots, which were not visible when I was disabling FX plugins last week. I only noticed them in the mix console today- and there were two on my BASS group. When I opened the UI of Voxengo GlissEQ I discovered that the plugin had somehow lost its registration and reverted to DEMO mode which periodically mutes output of the plugin!



So I re-entered the serial number and now the track plays just fine.

I originally started this track in 2018 and the computer's been through many Windows updates and software installs since then. Somewhere along the line all my Voxengo plugins lost their registration info. (My u-He plugins did too, but I updated and re-installed all of them when troubleshooting this problem.)

So it WAS an activation problem- just not with Hive, and the only reason it took so long for me to find it was that this was one of the only projects where I used post-fader inserts. Anyway, thank you!

[zvenx]

Thats great news.
Rsp