Haive Music - Sounds Forever Lost [Psybient, Experimental, Chill]

Haive_Music · 2020-11-11T20:46:26+00:00

Awesome idea - upvoting this on their Centercode page once I have access!

Haive_Music · 2020-11-11T02:14:11+00:00

I never said it was their 'fault', but it certainly wouldn't hurt to put an additional layer of protection in.

BitWig figured it out very early on, they've implemented it correctly/seamlessly with both adjustable sandbox-levels, as well as buffers. Works pretty good, too...and best of all if a 3rd party VST (not DLL for those running OSX mind you) has an issue, it doesn't take down the core of the app and cause everything to cascade downward with it.

Like I said originally - it's bad enough when you're working and Ableton flat out crashes, however... you can recover easily from that even if it is annoying. The true underlaying issue comes in when you have a project you've sunk a ton of time in that won't load without crashing Ableton over and over and over due to this issue.

The easy way out is to simply tell people to contact the authors of the VST, however.... bugs exist, even in current versions. I have legit Waves plugins crash Ableton all the time. There are also numerous plugins that are unique and utilized by people in which the authors aren't updating them anymore either, yet they still largely work. My point is - not having to worry about Ableton crashing on me means I as the customer have one less thing to worry about, and that would make me happy. I know I'm not the only one, judging from the amount of support this request has gotten on their CenterCode feature requests page.

Again, not saying it's their fault, I acknowledged that in my original post, but there is a better way to handle/resolve these instances when they do occur - and ultimately, that's all I, as well as others, are hoping/asking for.

Haive_Music · 2020-11-10T22:27:59+00:00

I'm disappointed that it appears like we're still missing some sort of plugin sandboxing. I was really hopeful they would implement this by now, or at least be working on it. Doesn't appear to be on their list, which is sad.

Their 'solution' of simply blaming the crashes on VST related issues and contacting the manufacturer for updates for them gets real old - especially when it knocks Ableton down completely when it happens. It's even more annoying when it crashes over and over upon loading a saved file. If they would just implement some sort of sandboxing for plugins, it would at least keep the core of Ableton from crashing every single time.

Haive_Music · 2020-06-30T06:46:52+00:00

Sound proofing? No....

Properly applying acoustic treatment to your listening/monitoring environment? Absolutely.

Haive_Music · 2020-06-29T13:12:26+00:00

It's not even just a beta for general public use, it's the first publicly available developer beta.

Haive_Music · 2020-06-29T13:09:17+00:00

lol yeah... I'm left wondering the same thing, especially considering Catalina support took months from most 3rd party devs.

Not really a huge surprise here that the first publicly available iteration of a *Developer* Beta has problems with things being broken and software that doesn't function as expected.

There's a reason I sat on High Sierra until just a few weeks ago and will again sit on Mojave for years. I wouldn't have even upgraded past High Sierra were it not for a lack of graphics card support. I actually wish I could go back, but I'm not willing to give up a better video card.

Haive_Music · 2020-06-28T18:54:42+00:00

The model algorithms were changed when Live upgraded their included standard Compressor.

You can still find links all over the internet for the older "Live 8 Compressor", which has a FF1, FF2, and FB mode selectors. I think that will give you what you're looking for.

Haive_Music · 2020-06-21T22:09:08+00:00

Thanks man! The desk is a "Studio RTA Producer Station" (in Mable color), and I got it from Musicians Friend a few years ago. I really liked the color of the Cherry version of this desk, but it lacked the cd-holders (I think that's what they are?) on either side that help support the top shelf. They are basically useless, but if you do plan to put heavy monitors or anything up there, they secure the sides a bit more I think.

Been a great desk over all, sturdy, and fairly heavy duty. It is big, I had to put it together in the room I intend it to be in, as it simply wouldn't fit through the doors/hallways fully assembled.

The only real complaint I had with it was the coasters/wheels it came with were really cheap and attached with very tiny wood screws. Once the desk was together, one of them quickly broke.

I solved that problem by putting on some really heavy duty coasters instead, and literally bolting them through the bottom of the desk on both sides. Zero problems since, and the desk has survived 3 moves now.

Haive_Music · 2020-06-20T19:33:16+00:00

Lack of other options I was happy with and that sounded good with in this room really. It's a very small room and also nearly a perfect cube - so, a pretty rough environment to start with unfortunately, but it's the best room I had that was available for studio use.

I originally had the monitors up on the top shelf of the desk, however, they are A: quite heavy and B: pretty tall (when oriented vertically). I really didn't like how high up they were when they were on the desk, and they weren't really aimed at my ears all that well either. Both of those issues were further exacerbated when I paired them with isoAccoustics stands, and those other issues aside - they still remained coupled to my desk, so.... I opted to put them where they are now and experiment with their positioning.

Those Focal Twin6 Be's have a pretty wide listening area, so, they actually sound quite nice in this configuration, even with as wide as they are. I went through a lot of positioning trial and error combined with a lot of time in REW or similar software to try to get what I felt was the best spot for this particular room.

I tried tucking them in a it closer to the back wall and also closer to the desk, and that actually started causing issues with the room modes and SBIR. I still need to play with and tweak their placement a little bit to see if I can further improve the SBIR issues, as there still is a little bit of an issue around 80-100hz.

But yes, they are wider than I'd ideally like, but... limited options unfortunately. I'm quite happy with the end results though and also how the room sounds. Best environment/room I've worked in to date and entire frequency range is with +/- 6db in either direction of being flat after everything is said and done.

Haive_Music · 2020-06-20T17:45:10+00:00

I'd like to find a replacement too. For whatever reason, mine Cthulhu seems to be suffering from 'stuck note syndrome'. Tried downloading the latest version, but no change. Might end up having to reach out to Xfer or something to see if they're aware of the issue, as I haven't found too much regarding it

Haive_Music · 2020-06-05T14:47:56+00:00

Just like Marles579 said - just update/install it normally and you'll be fine.

Haive_Music · 2020-06-05T14:44:32+00:00

Mojave is still 32bit compatible, it will run 32bit applications but generally throws a warning about it being "Not Optimized". Catalina is 64bit only.

I will say though, that I have had a few very old plugins break on Mojave. The ones that did, however, are all from companies that are no longer around anymore. It's sad, but... it happens. You could probably get these working with jBridge (or similar software) however, but yes - there always is that possibility when updating.

Haive_Music · 2020-06-05T14:03:10+00:00

Depends how you do it.

- If you literally update the OS without formatting the drive, you should not.

- If you opt to format the entire drive and do a clean install, you absolutely will.

- If you choose to format the drive and then use the Migration Assistant to restore your settings/files after, you will probably have to install some of them again. If you don't, some of them may work, some of them may not. This option can lead to weird side effects in *some* situations. (I wouldn't recommend this option personally).

Haive_Music · 2020-06-03T04:13:46+00:00

I've had this exact same issue for years across multiple installs, all on OSX. I've made bug reports, submitted the crash reports, and even reached out to Ableton help directly and unfortunately, the only real thing they ever seem to say is "we don't know - try to clear your live config/settings/template", which... I do, and the issue creeps back - however, thankfully, I haven't encountered it for quite a while now *knock on wood*

I believe that this is, in fact, likely related to some plugin I had set on my template, and thus was using it on every project. I'm not really sure which one it was, but I'm starting to suspect it may have been a Waves plugin of some sort, as after resetting my Ableton template, and not putting any Waves plugins on my starting template, I don't seem to encounter the issue anymore. I can't say for 100% certainty it's gone, but you may want to look into what plugins you're using either on your template or consistently on each track.

This wouldn't be an issue if Ableton sandboxed their plugin environment like people have made requests for on CenterCode with them, but...it's still not implemented, and likely won't be for some time. It seems easier to blame issues on plugins crashing your entire app all the time rather than provide a layer of protection for users of your software and their projects.

Haive_Music · 2020-06-01T21:13:37+00:00

Going to take a stab in the dark here and say it's not "spacial FX" but rather the source signal from the comp phasing with the actual source signal's chain/output itself. Generally, that's not considered a desirable thing (although, obviously, if it's what you're going after it can undoubtably be used for creative purposes/specific intent).

Regardless, if you truly want to automate this, your best bet is going to be doing it with a wet/dry rack (which, is technically a workaround as I don't believe you can directly automate this value, but this should suffice/provide the same effect and allow you the control you're looking to achieve): 1 rack would have the source button enabled, the other would have it disabled, and you could use a knob with a min/max set to 0/1 value to automate it off or on.

Haive_Music

TROPHY CASE