Ok when you click on Support Forum from within the Hive 2 gui it sends you here so I'll post this then send the issue to support...again.
This has been going on for quite some time. If I set Hive to Fixed Sized Buffers in FL Studio the timing of Arp/Seq patches is broken. They are way out of sync. Doesn't matter which option of Fixed Size Buffers is selected, maximum or buffer from host.
But if I don't select Fix Sized Buffers I get hard crashes in FL when browsing patches. Like I said this has gone on for quite some time over various versions of both Hive and FL Studio. The response in the past on the crashes is to use Fixed Size Buffers but that's not a solution for the timing issue.
It's still occurring in Hive 12092 and FL Studio 21.0.3 [3517]. The tests are run at 44.1K
It occurs with both the VST 2 and 3 versions.
This does not occur with any of the other dozens of synths I own and use.
Win 10 22H2 Focusrite ASIO drivers, everything 64 bit.
Hive 2 Crashes and Timing Issues in FL Studio
-
- KVRAF
- 19818 posts since 16 Sep, 2001 from Las Vegas,USA
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe
-
MirkoVanHauten MirkoVanHauten https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=376111
- KVRist
- 453 posts since 12 Mar, 2016
I can confirm the arp being out of sync or even going completely wild with respect to tempo, when fixed size buffers are selected. Cannot confirm any crashes when browsing presets without fixed size buffers though.
-
- u-he
- 30204 posts since 8 Aug, 2002 from Berlin
Yes, we know,
it's been reported here: viewtopic.php?t=591348
And it's not that we forgot it, but we have not been able to release a fix yet (we said "probably in 2023", which isn't even half way through yet).
On that note, there is no need to post sequels to the thread, our internal project management system reminds us daily about just how much work we need to do before we can release an update.
it's been reported here: viewtopic.php?t=591348
And it's not that we forgot it, but we have not been able to release a fix yet (we said "probably in 2023", which isn't even half way through yet).
On that note, there is no need to post sequels to the thread, our internal project management system reminds us daily about just how much work we need to do before we can release an update.