ngLeveler
16-channel next generation automation system
The ngLEVELER, also known as the “Next Generation Leveler,” is an advanced analog automation system designed for seamless studio integration. In addition to its automation engine, it provides analog saturation on each channel, giving tracks more presence and depth in the mix.
The ngLEVELER itself has no physical controls and is managed through:
- A DAW plug-in
- A HUI controller
- Or a combination of both
This setup offers easy fader control with full total recall via the DAW plug-in. Designed to be a central tool in the studio, its simple analog connectivity makes it versatile and adaptable to a wide range of applications.
Main Features
ngLEVELER – “Next generation Leveler”
ANALOG SOUND, DIGITAL CONTROL
Regardless its digital control features, ngLeveler is fully analog unit.
Streamlined Analog Signal Automation and Recall through Plugin Control
1. Opposite quad channel link: This functionality links two stereo channels in an opposite way, it means that by pushing level of channel 1 & 2, channel 3 & 4 signal will be lowered by the same amount, perfect solution to drive our stereo analog units maintaining the same signal level.
Read more Read moreTrue tube compression
1. Opposite quad channel link: This functionality links two stereo channels in an opposite way, it means that by pushing level of channel 1 & 2, channel 3 & 4 signal will be lowered by the same amount, perfect solution to drive our stereo analog units maintaining the same signal level.
2. Channel mode: This parameter defines how two neighbor channels will be linked. There are following options:
a. Off – No linking, pure dual-mono operation.
b. Stereo – Channels will share exactly the same settings (absolute linking).
c. Linked – Channels are linked relatively (relative linking) – perfect solution to compensate different channel levels while using dual mono analog devices as stereo pair.
d. Linked Opposite – Channels are linked relatively (relative linking), but in opposite way, it means if channel 1 level will increase, channel 2 will be lowered by the same amount. It is perfect solution if we have mono unit that we would like to drive harder to hear how it performs. In that scenario ngLEVELER channel X OUT should go straight to IN of our device, and channel Y IN of ngLEVELER should receive signal from the OUT of device.
3. THD – toggles THD level, possible steps – OFF (LEDs disabled), MED, HIGH.
4. SOLO/MUTE – Solo and Mute for particular channel.
5. IN metering – signal level for particular channel measured after PAD, however before ngLEVELER main circuit (Leveling, THD, Solo, Mute).
6. Fader – Level control.
7. OUT metering – signal level for particular channel measured after ngLEVELER main circuit.
8. Channel name – assignable and fully user configurable channel name – please note that this name will be also communicated to external controller if in use.
9.Trim / Level value – depend on the mode (Fader/Trim) this field shows current value of: TRIM – When Fader mode is selected / LEVEL – When Trim mode is selected.
10. GROUP – Group asssigned to a particular channel.
11. PAD – Passive 6dB attenuator
Monitoring!
MUTE – channel is muted.
SOLO – Any channel with solo active will pass the signal with full processing
unless it is not explicitly muted. Hitting solo on particular channel will
also mute all other channels unless solo or solo safe is not engaged.
Monitoring!
MUTE – channel is muted.
SOLO – Any channel with solo active will pass the signal with full processing
unless it is not explicitly muted. Hitting solo on particular channel will
also mute all other channels unless solo or solo safe is not engaged.
SOLO SAFE – Channel will pass the signal with full processing
unless it is not explicitly muted – this channel will pass signal,
even if other channels are soloed. Usually this approach is used to mark
summed grouped signal to follow solo of individual tracks.
TRIM MODE!
Trim mode allows us to change level of each channel on top of already setup Faders. Trim faders also work in very high resolution as whole TRIM fader work in limited scale -10dB to +5dB. Such approach gives us few important benefits.
Read more Read moreTRIM MODE!
Trim mode allows us to change level of each channel on top of already setup Faders. Trim faders also work in very high resolution as whole TRIM fader work in limited scale -10dB to +5dB. Such approach gives us few important benefits.
- With fader mode used as our main leveling mechanism, it is still possible to change the balance even if levels in fader mode are already automated. Let’s assume we would like to change level of the kick channel in already automated drums group.
- We can use group automation in fader mode, and still use Trim mode to either:
- Automate differently individual channels of our group,
- Or simply change level between individual tracks of our group.
- Trim mode also maybe very convenient for automation, as whole fader scale on the plug-in or controller is relatively small (15dB) compared to full scale of the fader mode.
CHANNEL GROUPS!
Assign each channel to one of 4 groups which
technically link all parameters in particular group.
Some parameters maybe disabled from groping:
CHANNEL GROUPS!
Assign each channel to one of 4 groups which
technically link all parameters in particular group.
Some parameters maybe disabled from groping:
a) Level (Fader Mode level) / Trim (Trim mode level) / THD / PAD.
b) This approach allows to automate for instance only LEVEL for whole group – keeping exactly same level relations between channels, and all other parameters (Trim/THD/Pad) can be used independently for each channel.
Each group can be also disabled at any time to allow modifications of each parameter for particular channel.
Convinient connectivity!
ANALOG: DB-25
DIGITAL CONTROL: USB or ETHERNET
THD – ADD COLOR TO YOUR MIXES on each channel!
THD stands for “Total harmonic distortion” and it allows to saturate your signal with beautiful analog color.
ANALOG AUTOMATION
I’m sure all of us wanted to use different device settings based on song section. Now it is possible! Just draw automation lines in your DAW and your analog device will follow!
And remember, you can use your HUI controller to record automation TO your DAW
USAGE EXAMPLES
1. Summing stage automation
ngLEVELER can be integrated in any spot in analog chain which requires signal level management or automation. One of such situation is level management or automation of signal which goes out from our outboard gear to the summing stage. This gives us few very important benefits:
POST Compression automation or level management – changing signal level which goes out from our converter (DAW automation) will cause our compressor to behave differently. This makes it impossible to automate, and is quite problematic situation to handle even with simple signal level balance changes. In this setup we can keep our summing stage signal level at same level, and leave automation and signal level management to ngLEVELER so it can be easily recalled upon session load!
OUT signal management and automation – all outboard gear have a sweet spot which usually depends on a signal level which comes in. In most cases we don’t want to automate signal going in, but signal which goes out from the device. With ngLEVELER we can easily manage this signal:
not to clip next analog stage,
Or automate it when needed!
1.1. Example 1 – Summing automation/level management
1.2. Example 2 – Summing mixer/Console insert points automation
1.3. Example 3 – Summing mixer/Console groups insert points automation
2. Any analog outboard automation
In this particular example, ngLEVELER is integrated between each analog outboard process input, and output, of course it can be configured only to output, or only to input if needed. ngLEVELER allows us to work with very hot signals where many audio interfaces can’t deal with. Benefits:
3. Analog outboard drive
In this scenario we can configure our stereo processing before and after outboard gear, and link those channels in an opposite way. So while increasing level on the input of our outboard processor, it will automatically decrease on its output before hitting further stage. So we can easily find a sweet spot of our processor which can be fairly high for some vintage gear.
4. Recording session management
Studios of each size need some centerpiece which will help to manage recording and mixing session. Using ngLeveler in such situations, allows to precisely set levels which will hit A/D converter, add some analog saturation, and using “Solo and Mute” buttons manage our sessions with ease. Benefits:
Main features summary:
APP FOR MAC AND PC
Digital control features for fully analog units.
Specification
ngLeveler specification
THD+N(20Hz-20kHz) | at 0dBu < 0.008% |
Freq response | 0-250kHz (-3dB) |
Input impedance | > 10kohm |
Output impedance | < 50ohm |
Crosstalk | > 100dB |
Max input level | +25dBu |
Max output level | +28dBu |
Dynamic range | > 118dB |
Hardware Digital resolution | ~2500 steps per channel* |
Power consumption (MAX) | 20W |
Unit dimensions | 44x483x260 mm |
Box dimensions | 274x550x382 mm |
Unit weight | 3,6 kgs |
Box weight | 4,6 kgs |
Warranty | 2 years |
*DAW, or HUI controller may support lower resolution, in that case it will translate to lower number of HW steps.
User Manual
Download ngLeveler User Manual
NGLEVELER VIDEO STORIES
Watch the product video
FAQ
Frequently Asked Questions
If the module doesn’t react to any changes to the knobs on the front panel, the first necessary step is to rewrite firmware into the flash memory (Factory reset procedure re-writes firmware into internal flash memory – it doesn’t affect anyhow unit configuration). To proceed with factory reset, please follow below steps:
- Connect unit either:
- Through front panel USB socket,
- Or keep the unit in ng500 chassis – _TITAN, but please note that chassis has to be connected to the PC/MAC either via USB or Ethernet cable.
- POWER OFF your 500 series chassis.
- Depends on the product please press following front panel control:
- _MIMAS – RATIO button,
- _DIONE – RATIO button,
- _RHEA – THD button,
- _PROMETHEUS – HIGH CUT encoder (top-right encoder),
- _HYPERION – LMF GAIN encoder,
- _CALYPSO – MENU encoder.
- While keeping this control (button/encoder) pressed, POWER ON your 500 series chassis.
- LEDs should present a strange pattern.
- Now open GConManager:
- WIN: C:/Program Files (x86)/WesAudio/GConManager.exe
- MAC: /Applications/WesAudio/GConManager.app
- Or click on the WesAudio “Tray” icon, and select “Open GConManager”
- Go to _UPGRADE application.
- Hit start!
If the module doesn’t react to any changes to the knobs on the front panel, the first necessary step is to rewrite firmware into the flash memory (Factory reset procedure re-writes firmware into internal flash memory – it doesn’t affect anyhow unit configuration). To proceed with factory reset, please follow below steps:
- Connect the unit to either USB or Ethernet.
- POWER OFF your unit.
- Depends on the product please press following front panel control:
- ngBusComp – far left Ratio on Channel 1 (Ratio “-”),
- ngTubeEQ – THD encoder on Channel 1,
- ng76 – “IN MODE” button,
- ngLEVELER – use a small screwdriver and press button available on the rear panel via a small hole in the chassis.
- While keeping this control (button/encoder) pressed, POWER ON your unit.
- LEDs should present a strange pattern.
- Now open GConManager:
- WIN: C:/Program Files (x86)/WesAudio/GConManager.exe
- MAC: /Applications/WesAudio/GConManager.app
- Or click on the WesAudio “Tray” icon, and select “Open GConManager”
- Go to _UPGRADE application.
- Hit start!
This is a very common issue and in most cases the root cause lies in the connection of the unit and audio interface. If that happens it should be checked if audio interface input isn’t connected to the chassis input and if audio interface output isn’t connected to chassis output. As this initially would seem to be entirely wrong and shouldn’t work at all, as all our units implement “True Bypass” via relays, the unit will pass a signal when the bypass is engaged. The reason for that is that the relay is in fact hard wiring input to the output, and thus the unit will pass the signal, as it doesn’t go through any active circuit of the unit.
This is actually how it is supposed to work, so after the plug-in instance is created, please use a small triangle button which usually is on the bottom side of the plug-in and select proper HW ID from the drop down menu. If the drop down menu doesn’t list any hardware units, please check Your connectivity and other possible root causes in this FAQ.
This is a wide topic, and there may be at least several root causes, but there are few things that should be checked. However, the first and most important thing is to double check that GConManager doesn’t list this device in the _CONFIG app. If this is the case, it means that WesAudio unit can’t connect on the OS level, and some of the below steps may help:
- First of all double check if module connection is properly executed, this procedure is described here.
- USB specification indicates that USB 2.0 works up to 5 meters. This is however not entirely true, as it strongly depends on the peripherals that unit is connected to. Even if our modules are USB 2.0 compatible, your USB port could support USB 3.0 – USB is a backward compatible protocol, so it may be that USB 3.0 cable length limit should be considered which is 2 meters. We would recommend having a USB cable up to 2 meters to remove those limitations from the equation.
- USB HUB is very common root cause to those problems, if module can’t connect via HUB – just for the sake of the test, it is mandatory to connect unit directly to PC/MAC to verify if the problem isn’t caused by it.
- Please note any system warnings attached to “WesAudio Tray Icon”.
As USB controllers have limited capacity it could be a reason for random unit disconnection. Usually, it happens when a lot of USB devices are plugged into the PC/MAC. The usual behavior would be that the unit works normally, and after reboot it doesn’t, but it strongly depends on the OS implementation so exact reaction could be a little bit different. If this is suspected, just for the test, it would be good to disconnect most of the devices from the USB ports, reboot PC/MAC and double check the connectivity from stability point of view. If it leads to the conclusion that this is the root cause of the problem, we would recommend using a decent USB hub, and ideally a TB/USB dock station which tends to offload a lot of responsibilities from our PC/MAC.
If the unit was working fine, and suddenly it couldn’t connect (it is not visible in the GConManager _CONFIG app) that could lead to the conclusion that some devices were added to our USB line, and we could have problems with the USB controller inside PC/MAC. In that case please check the description in the above “Unit disconnects by itself”.
GConManager in Admin mode enables special functionalities which are used during WesAudio units calibration.
OSX:
- Please open terminal.
- Copy-Paste following command:
open /Applications/WesAudio/GConManager.app --args --admin
WINDOWS:
- Go to “START” and open “Command Line”.
- copy paste this command:
"c:\Program Files (x86)\WesAudio\GConManager.exe" --admin