Hi,I'm an old customer of nebula from begining(I'm using neb3 pro from a long time ago and I bought a lot of commercial libs) and I never tried to use Nat but I recently tried to use it for creating programs of a chain of several instances of neb and other plugs. I found that I'm not able even begining... I read in the forum about a beginners guide or tutorial and some of you gave a link for a vst plugs tutorial in the old forum, but it doesn´t work, it´s a dead link. Would you help me (and I'm sure a lot of us will be so happy) to start? I don´t know how to do anything, please, a "starting tutorial" would be wonderful in order to use that other side of nebula I never tried. Just something like how to create a program using another program.
Hi, enrique, thanks for answering. I do appreciate your help but I'd like you to give any fast start tutorial for starting, just to make a simple vst chain of plugins into a program, not an eq or preamp, just a simple how to convert a single plugin into a program. Is this possible or it´s just oriented to sample hardware? I saw a link to a post in the old forum not working for anymore, do you know if this "vst to program" tutorial is live enywhere? Thanks again
If you are trying to sample a saturation effect then it's quite easy: you should start by downloading the latest NAT sessions (v10 I think). Next, start NAT and navigate to the sessions, go to "offline presets"/preamps and choose "Distorted Pre (7 kernels) - smooth2 - OFFLINE".
Now you need to set a temp data route (on the NAT offline sampling page), give your preset a name and description and finally press on "Generate" to create a test-tone. Next, open the test-tone in your audio-editor, process it the way you want and save under a different name. Navigate in NAT "temp data" to the new (processed) file, select it and then press "Deconvolve".
Next you need to check your preset and use the padin/padout (edit/glob in Nebula) to make fine adjustments to the sound levels and saturation. You can use the "vst plugin analyzer" for visual feedback.
I did try it and create the n2p and n2v files, but when I load the program in nebula it doesn´t do anything to the audio, the effect of the program is zero.
I used the pre session as you told and I took the test tone generated (it's a chain of pieces of "fade out" where the level is decreasing from one to the next one) and I rendered it through an FX (the first experiment was through a plugin of echo and the second time it was through a simple plugin sounding like an old radio, both times creating a 32 bits output file). When the np2 and nv2 files were created(for both experiments) I just put them into neb library folder and I didn´t do anything more.
Am I doing something wrong? It´s strange cos nebula load the program but there is no effect to the audio.
@babiuk- did you use the new (processed) wav for de-convolving? you need to choose it in the "temp data" window.
It sounds like you are doing things properly so I'm not sure why you are not getting a working preset. You can speed up your tests by using less repetitions in the test tone: click on the "Expert" tab and under "Number" change it to 5 (from 30)-should be enough for testing. Press "Offline" to go back to your original work-space. Don't forget to press on "generate" and this time just use this test-tone for processing (re-writing the file) so there is no file confusion possible.
@martinez- it's possible but a bit tricky, because the playback engine sometimes generates a lot of digital junk (depending on the preset) which might be "doubled" with the new preset. Also, the new preset will sound slightly different no matter what you do, but it is possible to get very good results.
You could, for instance, process the first (loudest) repetitions of the test tone with your preset chain at a lower volume (using a gain plugin before & after the chain). Another option is just sample the chain as is and use padin/padout later with your new preset to "skip" any damaged/odd parts of the test-tone.
Last edited by yr on Tue Jun 19, 2012 10:31 am, edited 1 time in total.