Club VST
Club VST
Home | Profile | Register | Active Topics | Active Polls | Members | Private Messages | Search | FAQ
Username:
Password:
Save Password
Forgot your Password?




 All Forums
 THE NAT Forum !!!
 All Things NAT
 Making NAT programs
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

clubvst
Forum Admin


USA
169 Posts

Posted - 07/15/2010 :  20:06:25  Show Profile  Visit clubvst's Homepage Send clubvst a Private Message  Reply with Quote
Making NAT programs.

The most useful thing I think I can do, and anyone else interested in helping can do, is to provide advice for those already trying to help themselves.

Let's say a user wants to sample presets from their reverb unit. They watch the Velinas video and try to follow, but their reverb tail comes up short, or the program doesn't load, or the volume seems weird, etc. By helping to edit the program, or load it and see what went wrong, or by reading what they did to see if they missed a step- that is hands on helpful.

If that same person listens and listens and listens and there still is something not accurate in their sample, telling them the fine-tuning aspect is going to involve more theory, but in this case at least it will be based on the particular aspect of Giancarlo's design that deals with reverb.
Reverb involves longer decay, more latency, a different set of quotients than eq.

So, it makes sense to help someone fix what is broken, and to teach the person who is making an effort to do for themselves as well.

More on this in next post.

You must be logged in to see this link.
Software, Mastering, Tutorials

Google AdSense

USA
Mountain View


clubvst
Forum Admin



USA
169 Posts

Posted - 07/15/2010 :  20:27:35  Show Profile  Visit clubvst's Homepage Send clubvst a Private Message  Reply with Quote
NAT instructions and NAT templates:

Here is a standard list of commands found in the instruction set for a standard NAT session:

<PROGRAMNAME> name </PROGRAMNAME>
<CATEGORY> EQU </CATEGORY>
<DESCRIPTION> description </DESCRIPTION>
<WAVEFILENAME> C:\Sessions\Samples.wav </WAVEFILENAME>
<PAUSE> NULL </PAUSE>
<TEMPLATENAME> C:\NebulaData\Templates\Template_multi1d_a.xml </TEMPLATENAME>
<TYPE> Dynamic </TYPE>
<WAVEENABLE2> 0 </WAVEENABLE2>
<SYNC> 1 </SYNC>
<DEC64BITS> 1 </DEC64BITS>
<STONE> 0 </STONE>
<STONEPHASELOCK> 0 </STONEPHASELOCK>
<DECNMONO> 1 </DECNMONO>
<DECNNORMALIZE> 0 </DECNNORMALIZE>
<FMOD> 0 </FMOD>
<RATE> 44100 </RATE>
<WAVELENGTH> 60 </WAVELENGTH>
<WAVENUMBER> 1 </WAVENUMBER>
<WAVENUMBER2> 1 </WAVENUMBER2>
<WAVELOWFREQUENCY> 1 </WAVELOWFREQUENCY>
<HDIMMAX> 1 </HDIMMAX>
<WAVEREPEATS> 1 </WAVEREPEATS>
<DECNENHANCED> 1 </DECNENHANCED>
<HDIR1> 0 </HDIR1>
<HFFT1> 100 </HFFT1>
<HDIR2> 0 </HDIR2>
<HFFT2> 50 </HFFT2>
<HDIR3> 0 </HDIR3>
<HFFT3> 50 </HFFT3>
<HDIR4> 0 </HDIR4>
<HFFT4> 0 </HFFT4>
<HDIR5> 0 </HDIR5>
<HFFT5> 0 </HFFT5>
<GAIN> 0 </GAIN>
<WAVELOOP> 24 </WAVELOOP>
<WAVESPACE> 1 </WAVESPACE>
<WAVESTEPS> 1 </WAVESTEPS>
<WAVESTEPS2> 10 </WAVESTEPS2>
<STONEAMOUNT> 1 </STONEAMOUNT>
<STONELINEAR> 0 </STONELINEAR>
<WAVEPERIOD> 80 </WAVEPERIOD>
<MULTIPOSITION> 0 </MULTIPOSITION>
<WAVEEDITORFILENAME> NULL </WAVEEDITORFILENAME>
<MULTI>
<ITEM>
<ORDER> 0 </ORDER>
<LABEL> Gain </LABEL>
<UNIT> dB </UNIT>
<SEQUENCE> 0 </SEQUENCE>
<VALUES>
<VALUE>
<ORDER> 1 </ORDER>
<VCTVALUE> 0 </VCTVALUE>
<BUSVALUE> 0 </BUSVALUE>
<PROMPTMESSAGE> 0 dB </PROMPTMESSAGE>
<FLAT> 0 </FLAT>
</VALUE>
<VALUE>
<ORDER> 0 </ORDER>
<VCTVALUE> -15 </VCTVALUE>
<BUSVALUE> -15 </BUSVALUE>
<PROMPTMESSAGE> -15dB </PROMPTMESSAGE>
<FLAT> 0 </FLAT>
</VALUE>
<VALUE>
<ORDER> 2 </ORDER>
<VCTVALUE> 15 </VCTVALUE>
<BUSVALUE> 15 </BUSVALUE>
<PROMPTMESSAGE> 15 dB </PROMPTMESSAGE>
<FLAT> 0 </FLAT>
</VALUE>
</VALUES>
</ITEM>
</MULTI>
<GUI>
<TREEWIDTH> 127 </TREEWIDTH>
<TREEVISIBLE> 1 </TREEVISIBLE>
<APPLICATION0>
<VISIBLE> 0 </VISIBLE>
<WIDTH> 294 </WIDTH>
<HEIGHT> 165 </HEIGHT>
</APPLICATION0>
<APPLICATION2>
<X> 2 </X>
<Y> 7 </Y>
<VISIBLE> 1 </VISIBLE>
<WIDTH> 359 </WIDTH>
<HEIGHT> 501 </HEIGHT>
</APPLICATION2>
<APPLICATION3>
<VISIBLE> 0 </VISIBLE>
<WIDTH> 366 </WIDTH>
<HEIGHT> 509 </HEIGHT>
</APPLICATION3>
<APPLICATION4>
<VISIBLE> 0 </VISIBLE>
<WIDTH> 359 </WIDTH>
<HEIGHT> 461 </HEIGHT>
</APPLICATION4>
<APPLICATION5>
<X> 372 </X>
<Y> 159 </Y>
<VISIBLE> 1 </VISIBLE>
<WIDTH> 463 </WIDTH>
<HEIGHT> 143 </HEIGHT>
</APPLICATION5>
<APPLICATION6>
<X> 371 </X>
<Y> 9 </Y>
<VISIBLE> 1 </VISIBLE>
<WIDTH> 463 </WIDTH>
<HEIGHT> 143 </HEIGHT>
</APPLICATION6>
<APPLICATION7>
<VISIBLE> 0 </VISIBLE>
<WIDTH> 681 </WIDTH>
<HEIGHT> 290 </HEIGHT>
</APPLICATION7>
<APPLICATION8>
<X> 367 </X>
<Y> 302 </Y>
<VISIBLE> 1 </VISIBLE>
<WIDTH> 500 </WIDTH>
<HEIGHT> 353 </HEIGHT>
</APPLICATION8>
<APPLICATION9>
<VISIBLE> 0 </VISIBLE>
<WIDTH> 396 </WIDTH>
<HEIGHT> 251 </HEIGHT>
</APPLICATION9>
<APPLICATION10>
<VISIBLE> 0 </VISIBLE>
<WIDTH> 960 </WIDTH>
<HEIGHT> 366 </HEIGHT>
</APPLICATION10>
<APPLICATION11>
<VISIBLE> 0 </VISIBLE>
<WIDTH> 456 </WIDTH>
<HEIGHT> 256 </HEIGHT>
</APPLICATION11>
</GUI>

Here's what you should essentially know about this info:

<PROGRAMNAME> name </PROGRAMNAME>

This will be filled out in the session template and is a limited # of characters for your preset program (I think 16 characters but coulbe wrong).

<CATEGORY> EQU </CATEGORY>

Choose the category that your program belongs in. In this case it goes in the EQU for equalizer.

<DESCRIPTION> description </DESCRIPTION>

This field can be used to tell someone about your program like "high shelf eq" or "3 kernels version". It will appear in your program when loaded.

<WAVEFILENAME> C:\Sessions\Samples.wav </WAVEFILENAME>

NAT will use this field for your sampling session. Where you choose the sampling wav file is where it will fill this info.

<PAUSE> NULL </PAUSE>
<TEMPLATENAME> C:\NebulaData\Templates\Template_multi1d_a.xml </TEMPLATENAME>

The all-important template! In this example the multi1d_a is chosen. I writing this at my online machine which is not in the recording studio, so I am working from memory. If I have the particulars wrong dont worry. This is just so you know what is happening. In this example, you are working with a session that is made to create a single knob eq. Variations of this name allow for switching and not switching, which controls variables like fixed gain or frequency points or interpolated. I believe multi2d is the code for two variables. The correct template must be chosen to the type of items you enter in the text fields or the program will act strange or not render.

<TYPE> Dynamic </TYPE>

This is a direct instruction to the Neb engine about what type of program it is. The engine will read it as a dynamic program and will load it with parameters related to a dynamic program. I believe other options are based on time variants.

<WAVEENABLE2> 0 </WAVEENABLE2>
<SYNC> 1 </SYNC>
<DEC64BITS> 1 </DEC64BITS>

number of bit depth

<STONE> 0 </STONE>

Stone is a name for applying frequency correction to a program to make something that is nonlinear more applicable for careful editing like mastering. An example is an optimized analog eq that loses high end.

<STONEPHASELOCK> 0 </STONEPHASELOCK>
<DECNMONO> 1 </DECNMONO>
<DECNNORMALIZE> 0 </DECNNORMALIZE>

I believe this is the NAT instruction to normalize the output of the sampling session to 0dB.

<FMOD> 0 </FMOD>

Frequency Modulation

<RATE> 44100 </RATE>

This is the sample rate for the session sampling. Make sure you choose this first before sampling. Also, it is wise to save a session and reload it to make sure it says the right rate. If you load your session to re-render something later make sure once again the rate is correct.

<WAVELENGTH> 60 </WAVELENGTH>

# of seconds in sample

<WAVENUMBER> 1 </WAVENUMBER>
<WAVENUMBER2> 1 </WAVENUMBER2>

This is a process that will get filled in when you choose your variables in the session. It will post the next sampling instruction automatically when you begin sampling.

<WAVELOWFREQUENCY> 1 </WAVELOWFREQUENCY>
<HDIMMAX> 1 </HDIMMAX>
<WAVEREPEATS> 1 </WAVEREPEATS>

You can choose to repeat sampling instructions and it will compare one sample against the other for accuracy. 1 Repeat means one time sampling.

<DECNENHANCED> 1 </DECNENHANCED>
<HDIR1> 0 </HDIR1>
<HFFT1> 100 </HFFT1>
<HDIR2> 0 </HDIR2>
<HFFT2> 50 </HFFT2>
<HDIR3> 0 </HDIR3>
<HFFT3> 50 </HFFT3>
<HDIR4> 0 </HDIR4>
<HFFT4> 0 </HFFT4>
<HDIR5> 0 </HDIR5>
<HFFT5> 0 </HFFT5>

FFT and Direc are the two related sciences for reproducing spectral-based sound. that is an entirely separate discussion, but I think that these fields are for the information about kernels length regarding fast fourier transform and dirac but I could be wrong.

<GAIN> 0 </GAIN>
<WAVELOOP> 24 </WAVELOOP>

Not sure- may be loop back test for length of latency between input and output of sampling devices dac adc.

<WAVESPACE> 1 </WAVESPACE>

Space in seconds between samples.

<WAVESTEPS> 1 </WAVESTEPS>

How many dynamic volume steps are sampled in the program. In this case 1, because we are setting up an eq and every gain stage is sampled one time. We are essentially manually changing this for the program.

<WAVESTEPS2> 10 </WAVESTEPS2>

Variable 2 may be number of gain settings or number of frequencies. NAT doesn't care what the variable is or what the sample is, just that there is the right number of them and that you sampled something each time.

<STONEAMOUNT> 1 </STONEAMOUNT>
<STONELINEAR> 0 </STONELINEAR>

Instructions for Stone correction process.

<WAVEPERIOD> 80 </WAVEPERIOD>
<MULTIPOSITION> 0 </MULTIPOSITION>
<WAVEEDITORFILENAME> NULL </WAVEEDITORFILENAME>
<MULTI>
<ITEM>
<ORDER> 0 </ORDER>
<LABEL> Gain </LABEL>
<UNIT> dB </UNIT>
<SEQUENCE> 0 </SEQUENCE>
<VALUES>
<VALUE>
<ORDER> 1 </ORDER>
<VCTVALUE> 0 </VCTVALUE>
<BUSVALUE> 0 </BUSVALUE>
<PROMPTMESSAGE> 0 dB </PROMPTMESSAGE>
<FLAT> 0 </FLAT>
</VALUE>
<VALUE>
<ORDER> 0 </ORDER>
<VCTVALUE> -15 </VCTVALUE>
<BUSVALUE> -15 </BUSVALUE>
<PROMPTMESSAGE> -15dB </PROMPTMESSAGE>
<FLAT> 0 </FLAT>
</VALUE>
<VALUE>
<ORDER> 2 </ORDER>
<VCTVALUE> 15 </VCTVALUE>
<BUSVALUE> 15 </BUSVALUE>
<PROMPTMESSAGE> 15 dB </PROMPTMESSAGE>

These are all of your values for the fields that are filled in, including what the variable is named, what the function number is, what your units are defined as, and what label or number will be in each field tab. These then become the appropriate bus values inside the engine and the engine can play them back according the samples that go along with the field names.

<FLAT> 0 </FLAT>
</VALUE>
</VALUES>
</ITEM>
</MULTI>
<GUI>
<TREEWIDTH> 127 </TREEWIDTH>
<TREEVISIBLE> 1 </TREEVISIBLE>
<APPLICATION0>
<VISIBLE> 0 </VISIBLE>
<WIDTH> 294 </WIDTH>
<HEIGHT> 165 </HEIGHT>
</APPLICATION0>
<APPLICATION2>
<X> 2 </X>
<Y> 7 </Y>
<VISIBLE> 1 </VISIBLE>
<WIDTH> 359 </WIDTH>
<HEIGHT> 501 </HEIGHT>
</APPLICATION2>
<APPLICATION3>
<VISIBLE> 0 </VISIBLE>
<WIDTH> 366 </WIDTH>
<HEIGHT> 509 </HEIGHT>
</APPLICATION3>
<APPLICATION4>
<VISIBLE> 0 </VISIBLE>
<WIDTH> 359 </WIDTH>
<HEIGHT> 461 </HEIGHT>
</APPLICATION4>
<APPLICATION5>
<X> 372 </X>
<Y> 159 </Y>
<VISIBLE> 1 </VISIBLE>
<WIDTH> 463 </WIDTH>
<HEIGHT> 143 </HEIGHT>
</APPLICATION5>
<APPLICATION6>
<X> 371 </X>
<Y> 9 </Y>
<VISIBLE> 1 </VISIBLE>
<WIDTH> 463 </WIDTH>
<HEIGHT> 143 </HEIGHT>
</APPLICATION6>
<APPLICATION7>
<VISIBLE> 0 </VISIBLE>
<WIDTH> 681 </WIDTH>
<HEIGHT> 290 </HEIGHT>
</APPLICATION7>
<APPLICATION8>
<X> 367 </X>
<Y> 302 </Y>
<VISIBLE> 1 </VISIBLE>
<WIDTH> 500 </WIDTH>
<HEIGHT> 353 </HEIGHT>
</APPLICATION8>
<APPLICATION9>
<VISIBLE> 0 </VISIBLE>
<WIDTH> 396 </WIDTH>
<HEIGHT> 251 </HEIGHT>
</APPLICATION9>
<APPLICATION10>
<VISIBLE> 0 </VISIBLE>
<WIDTH> 960 </WIDTH>
<HEIGHT> 366 </HEIGHT>
</APPLICATION10>
<APPLICATION11>
<VISIBLE> 0 </VISIBLE>
<WIDTH> 456 </WIDTH>
<HEIGHT> 256 </HEIGHT>
</APPLICATION11>
</GUI>

You must be logged in to see this link.
Software, Mastering, Tutorials
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
Club VST © 2008-2016 CDSoundMaster.com Go To Top Of Page
This page was generated in 0.3 seconds. Snitz Forums 2000
RSS Feed 1 RSS Feed 2
Powered by ForumCo 2000-2008
TOS - AUP - URA - Privacy Policy
ForumCo Free Blogs and Galleries
Signup for a free forum or Go Banner Free