Hive 2.1 public beta 01 revision 10837

[Funkybot's Evil Twin]

GUI lags extreme (especially Izmo) and there is still huge latency added when GUI is open.
Logic 10.6.1, macOS 11.1, macbook pro M1.

See the Mac GUI testing thread. They've done a lot of work on it and are actively looking for testers to try things out and report back. The thread has instructions on what settings you can update to try to improve the graphics response.

Thread is here:

viewtopic.php?f=31&t=559587

[EdSfer]

I have one small "issue" with the updated interface (I mean the original one, not Izmo) : I preferred when the orange modulation dot was on the side, instead of being in the center of a knob. I often find myself moving, for instance, the cutoff knob when I want to adjust modulation depth instead. It feels like it demands more precision when clicking than when it was on the side, and thus can lead to some unwanted modifications.

[snigelx]

...I preferred when the orange modulation dot was on the side...

Agree

[pdxindy]

Fun with Hive 2.1 and the new filters...

https://dandelionaudio.com/sound/hive21-4.mp3

[Dombaeb]

Maybe I'm missing something but I was really surprised that keyboard scale lock feature does not contain scales presets. If it's not there yet, it definitely should be. Looks like now I have to close Hive, watch the scale somewhere and reproduce it in Hive. Scale presets is so obviously useful feature that I am very surprised that it is not included.

Thanks for micro tuning presets though

[Viktor [TUC]]

Hi Dombaeb,

right-click on the keyboard dots for some scale presets.

Cheers
Viktor

[Dombaeb]

Ah, dots! Thank you!

Classic "read the f***ng manual" situation

Hi Dombaeb,

right-click on the keyboard dots for some scale presets.

Cheers
Viktor

[Shiek927]

Just wanna chime in to say how cool are the examples are! these are some very unique sounds I'm hearing!

[PieBerger]

I don't know if it's just me, but the wavetable selection menu/s is/are no longer respecting sub-directory hierarchies i.e. everything is just in the one giant list, which is a bit of a mess. Is this a bug or just how wavetables are being organised now? If it's the former, I can provide more details with screencaps to the support inbox. If it's the latter, I'd prefer to go back to the old way personally, the mega list workflow is clunky and confusing.

[PieBerger]

With regards to the modulation indicators, I don't like the new implementation, it makes it very hard to adjust parameters after assigning any modulation as you can only click on a small area to move the knob position. The old way with the little dot was better imo.

I like some of the other UI enhancements though, particularly in the FX hexagon; all of the different effects and their parameters are more separated/discrete, which is easier on the eyes for me personally.

[Urs]

I don't know if it's just me, but the wavetable selection menu/s is/are no longer respecting sub-directory hierarchies i.e. everything is just in the one giant list, which is a bit of a mess. Is this a bug or just how wavetables are being organised now? If it's the former, I can provide more details with screencaps to the support inbox. If it's the latter, I'd prefer to go back to the old way personally, the mega list workflow is clunky and confusing.

Unfortunately this was the best we could come up with for people with very large collections.

It happens when there's more than 128 folders (maximum number of menus) or more than 8000 wavetable files (maximum number of menu items). So when either maximum is reached, we need to browse separately for folders and wavetables. As we have to assume that the number of folders exceeds the number of menus we can create, we simply put them in a list.

So if you previously used Hive, not all of your wavetable files were accessible by menu. You either had crashes (too many menus), or a lot of files were simply not shown due to the limits (too many files). Now you shouldn't have crashes and at least you're able to reach all files you have.

In the long run we certainly need to come up with a more comprehensive solution for people who have collected very large numbers of wavetable files, but this was the best we could do to address the problem without spending months.

One thing I could look into is to indent sub directories to their level. At least this way the hierarchy would be visible.

If you want to address this from your end, make sure you have fewer than 128 folders and less than a total of 8000 wav/uhm files. I generally think that it's a good idea to merge collections of single cycle waveforms into single wavetable files.

[recursive one]

I don't know if it's just me, but the wavetable selection menu/s is/are no longer respecting sub-directory hierarchies i.e. everything is just in the one giant list, which is a bit of a mess. Is this a bug or just how wavetables are being organised now? If it's the former, I can provide more details with screencaps to the support inbox. If it's the latter, I'd prefer to go back to the old way personally, the mega list workflow is clunky and confusing.

Unfortunately this was the best we could come up with for people with very large collections.

I haven't yet installed Hive 2.1.

I have three folders for the 3rd party wavetables I use in Hive, one of them (the biggest one) having like 10 subfolders organised like "FM wavetables", "vocal wavetables" and such. I don't know how many wavetables are in this big folder but I think much less than 8000 (can't check right now but who on earth needs that many, lol)

So does it mean that when I uprgade to 2.1. all my 3rd party wavetables will be presented as a long list?

That would be quite a disaster, as the wavetables themselves may have arbitrary names, I'll be unable to guess if it was "FM" or "vocal" or something else, not to say dealing with such a long list would be no fun.

Or did I misunderstand something?

Maybe there could be a way to keep the "legacy" behaviour of the wavetable browser for the people who were happy with it?

[Urs]

In 2.1, and only if you reach the limits, you simply pick a directory when you click on the top half of the control, and you browse that directory's wavetables when you click the bottom half.

So on one hand it's an extra click. On the other hand, browsing within a directory is much faster than before because you don't always have to juggle your way through the folder hierarchy.

There is no change at all if you're within the limits of 128 folders, 8000 files.

[recursive one]

There is no change at all if you're within the limits of 128 folders, 8000 files.

Good to know, thanks!

I don't think I'll ever have more folders/files than 128/8000.

[PieBerger]

I don't know if it's just me, but the wavetable selection menu/s is/are no longer respecting sub-directory hierarchies i.e. everything is just in the one giant list, which is a bit of a mess. Is this a bug or just how wavetables are being organised now? If it's the former, I can provide more details with screencaps to the support inbox. If it's the latter, I'd prefer to go back to the old way personally, the mega list workflow is clunky and confusing.

Unfortunately this was the best we could come up with for people with very large collections.

It happens when there's more than 128 folders (maximum number of menus) or more than 8000 wavetable files (maximum number of menu items). So when either maximum is reached, we need to browse separately for folders and wavetables. As we have to assume that the number of folders exceeds the number of menus we can create, we simply put them in a list.

So if you previously used Hive, not all of your wavetable files were accessible by menu. You either had crashes (too many menus), or a lot of files were simply not shown due to the limits (too many files). Now you shouldn't have crashes and at least you're able to reach all files you have.

In the long run we certainly need to come up with a more comprehensive solution for people who have collected very large numbers of wavetable files, but this was the best we could do to address the problem without spending months.

One thing I could look into is to indent sub directories to their level. At least this way the hierarchy would be visible.

If you want to address this from your end, make sure you have fewer than 128 folders and less than a total of 8000 wav/uhm files. I generally think that it's a good idea to merge collections of single cycle waveforms into single wavetable files.

Thanks for the detailed explanation Urs! Sounds like I have all of the motivation I need now, to tidy up my somewhat bloated wavetable library, if this is going to be the new normal. The indents idea would still be handy for this new implementation.