I’ve recently bought one of the tutorials and found that it’s looking for the RevolVerb vst. So I went and downloaded it (seeing as its free) and when I try to open up the project file again it’s giving me an error message: “Failed to create file.” then Ableton 8 crashes and dies… Am I doing something wrong here? Or is there a particular RevolVerb I should be using?
It seems like a nice plugin and I want to get it working.
Note: It works in ableton 8 fine, but when I try to open the project file with it already in it, it crashes only then.
The convolution presets for revolverb should be included in the tutorial you downloaded.
As long as the asio buffers are cool (and they have to be for revolverb) everything should be ok.
so first start a new project and load revolverb and point it to your convolution presets that the project uses. do this once for every preset in the project to be safe.
the next project you load (inc the tutorial project that use them) should automatically load those presets or at least give you the chance to point to the presets without a crash.
Tried this today. Still no joy. When I load the impulse (GateVerb from the DUBFIRE/HTSL No8 project) it still doesn’t work when I try to open the project.
What’s really annoying is it sounds great! I will defo use it in my own productions, but its just annoying me i can’t use it in the project to see how it works/behaves. It also means i need to delete the .dll file and re-paste it every time.
I just tried the dubfire htsl tutorial using ableton 8.4 and sure enough it crashed just the same as Adams.
The problem is revolverb and its path related.
Here’s how to resolve the issue for users who have ableton 8
Step 1:
First move the revolverb.dll out of your plugin scan path.
This is to ensure the project can load within ableton 8 without crashing.
load the dubfire project which will warn you that revolverb failed to load. click ok twice.
You should notice once the project has loaded that Ableton still assigns a placeholder for the revolverb plugin but it will show as disabled.
Keep the project open.
minimize Ableton
Step 2:
Create a directory inside your vstplugins directory
Name it revolverb and inside that put the original revolverb.dll
c:\program files\vstplugins\revolverb
Also place the project impulses (largehall and gateverb) inside the same directory.
Step 3:
Return back to the Ableton project and right click on your vst plugin folder and rescan. Revolverb should now show in the list if not go to the options/preferences/file folder and rescan your plugins.
revolverb should now show in the plugin list
click on send A and drag revolverb back into the A return chain after the disabled revolverb.
delete the disabled version.
click on the revolverb interface and load the largehall impulse which should be located in:
c:\program files\vstplugins\revolverb
Step 4:
click on send B and drag another revolverb into its chain.
delete the disabled version of revolverb.
click on the revolverb interface and load the gateverb impulse which should be located in:
c:\program files\vstplugins\revolverb
finally save the project.
I am sure there’s a more elegant way but the above works ok.
Bry It may be worth updating the dubfire project with another version specifically for Ableton 8 users. Perhaps without revolverb?
Just to let you know I am using a pc running xp and ableton 8.4.
The above method also works for other SA projects that have minor revolverb issues.
just as long as the asio buffers are set to:128, 256, 512, 1024, 2048 samples.
Final note: Since revolverb has problems locating the paths I’d advise placing all future impulses and impulse directories inside:
c:\program files\vstplugins\revolverb
Any attempt to shunt the directories or impulses around after you’ve saved a project will probably result in a nasty crash which is obviously something to be avoided
Talking of impulses here’s some links to beef up your collection.
Actually I managed to figure this out last night. I did pretty much the same thing you advised, except all I did was after deleting the .dll, I opened the Dubfire project and then re-installed the reverb vst, then threw them onto the sends after deleting, then saved the new project.
However I never thought of throwing all the verb wav’s into one place. This is a good idea. I’ll also have a look at the links you put up for reverb impulses.
On the point, how does this plug-in work exactly? I’ve never used a reverb plugin that requires a .wav to activate… And obviously putting in different .wav’s will give you a different reverb I presume?
I am sure there are more users here who have come across the problem but at least now we have a blag/workaround. So i’ll leave the post as is but I’ve re-optimized the tutorial cutting out several steps after reading your reply.
It never occurred to me that Ableton could rescan without quitting
As for the reverb impulses I am not really sure how it all works.
I am sure there’s been a topic here in the forums about it although it could have been in another forum?
As interesting as it all sounded I didn’t attempt to commit it to long term memory
I have enough on my plate right now without filling up my head with even more tech head stuff lol
hey im trying the HTSL justice tutorial and i was getting the same problem…i can get past the crashes and but it just seems like the reverb doesnt work at all…i put in on send a Load JimpulseRroom.wav and turn the sends up and nothing happens…if i move the settings around (the tutorial says not to) i see audio coming through the send but only hear minor difference…any help is appreciated thanks
[quote]djcyph1 (26/05/2010)[hr]hey im trying the HTSL justice tutorial and i was getting the same problem…i can get past the crashes and but it just seems like the reverb doesnt work at all…i put in on send a Load JimpulseRroom.wav and turn the sends up and nothing happens…if i move the settings around (the tutorial says not to) i see audio coming through the send but only hear minor difference…any help is appreciated thanks[/quote]
hi, it sounds like you are just having a problem getting revolverb to work on your computer? there is documentation on their site regarding installation and usage, as some computer behave differently.
can you get it working from a brand new live set?
did you previously buy this course from our old site?
