Space convolution impulses

[garnoil]

I am interested in buying Avid's space because it is AAX (I am not getting Altiverb because it is not DSP otherwise I could get Altiverb). For Space I am looking for a large number of impulses specifically for: forest, country, street, lake, etc. really 'realistic outdoor impulses'. I am using this exclusively for post not for music. Are these outdoor impulses available either form Space or another library that I could use in the space plugin?

[tamasdragon]

I haven't tested this myself but heard very good things about it:
http://www.boomlibrary.com/boomlibra...ulse-responses

[garnoil]

Thank you, I will look into the boom library

[Cheesehead]

+1 for the Boom Library Impulses.
There are other good free ones out there on the web, just do a search.
Or you can make your own from gunshots or fireworks etc.

Personally I tried Space for post for the same reason that it is DSP.
I liked it, its flexible and it sounds good, but is sadly lacking in ease of automation. I would try the demo and make sure it can do what you need first.
I also found it has quite a hit on the host cpu, even though it runs on HDX.

[emilano]

Originally Posted by Cheesehead

but is sadly lacking in ease of automation.

They seem to tout their snapshot automation for Space. What is it that's lacking exactly?

"In addition to presets that save both the IR waveform and control settings, Space also enables you to manage a group of settings called snapshots, which you can quickly switch between using a single, automatable control—very useful in audio post production for firing different reverbs at scene changes."

[garnoil]

Originally Posted by Cheesehead

+1 for the Boom Library Impulses.
There are other good free ones out there on the web, just do a search.
Or you can make your own from gunshots or fireworks etc.

Personally I tried Space for post for the same reason that it is DSP.
I liked it, its flexible and it sounds good, but is sadly lacking in ease of automation. I would try the demo and make sure it can do what you need first.
I also found it has quite a hit on the host cpu, even though it runs on HDX.

Interesting that it would hit the CPU hard being DSP, if that is how it works it may not be worth getting. Great heads up, thanks! I will TRY before I buy.

[Cheesehead]

They seem to tout their snapshot automation for Space. What is it that's lacking exactly?

It will do snapshot automation but there are a limited number of slots.
In a big feature you could easily run out of slots and then you're done, apart from using another Space.

Altiverb used to be the same until they allowed all the reverb parameters to be individually automated, getting around the limitation and allowing unlimited scene changes.

As for the cpu hit, I have no idea why. A bit of a shame with all those processors idling away on the HDX card.

[garnoil]

Originally Posted by Cheesehead

It will do snapshot automation but there are a limited number of slots.
In a big feature you could easily run out of slots and then you're done, apart from using another Space.

Altiverb used to be the same until they allowed all the reverb parameters to be individually automated, getting around the limitation and allowing unlimited scene changes.

As for the cpu hit, I have no idea why. A bit of a shame with all those processors idling away on the HDX card.

Bad CPU load for something that is supposed to be DSP HDX + bad automation is a no go for me In that case Altiverb would be a much better choice.

[MIKEROPHONICS]

avoid - and get exponential audio's reverbs

[Frank Kruse]

Originally Posted by MIKEROPHONICS

avoid - and get exponential audio's reverbs

EA sounds good but it's a very different reverb. I have both but EA is not going to replace AV for many things, IMO.

Since PT11 AV's memory hunger is not an issue anymore. And since they got rid of those preset slots and automate all parameters the automation hickups have gone away entirely for me. However, I've seen many people still use the presets slots AND the parameter automation at the same time. This is where the problems start.
You should only use one OR the other. Here's a good explanation from Aram regarding this:

Basically it comes down to this:
the automation preset contains all parameters
when you automate this, but also have all parameters in automation
both get written
when you then change a parameter a conflicting situation arises, the track automation is different from the setting in the automation preset. No one now knows what has priority.
This leads into confusing situations.

That's why I recommend:
do not use automation presets, simply recall you setting/preset and write all to track

If you want to use automation presets, the only enable this parameter for automation and disable all others.

Frank.