Overview
The E352 Cloud Terrarium is a 26HP wavetable VCO with two outputs. It replaced Synthesis Technology’s E340 Cloud Generator and E350 Morphing Terrarium, and it still ships with all 192 waves of the E350 as three ROM banks. Around those banks it adds morphing modes with a wavefolder or a phase offset, the Cloud modes that stack 2, 4 or 8 detuned copies of a wave, 2-operator FM, noise, detuning and a sample player. Three CVs called X, Y and Z do different jobs in each mode, and a color screen with a shallow menu sets everything up.
The E370 is the same idea times four: a 54HP module with four independent wavetable VCOs, each set to one of seven modes, with all 16 CV inputs assignable to any VCO and each output a mix of all four. It adds a chord mode driven by text files on the card and 16 patch memories.
Both modules keep up to 26 user banks in internal memory, lettered A to Z. The microSD card is only used to load banks (and firmware). Once a bank is loaded you can take the card out.
Wavetables on the E352 Cloud Terrarium / E370 Quad Morphing VCO
A bank on these modules is 64 waves arranged like a chessboard: 8 rows of 8. In the morph modes X moves along a row, Y moves up and down a column, and Z scans all 64 waves end to end. Wave 0 is the first column of the first row, so the file order is row by row: wave = row × 8 + column. Each wave is 256 samples at 16 bits. That’s the 2D wavetable layout WaveEdit was written for, and it’s why WaveEdit banks travel well between modules.
The modules accept exactly two kinds of WAV. The firmware checks the file length when you load: 256 samples is a single wave, which you drop into one position (1–64) of a user bank, and 64 × 256 samples is a whole bank, which fills a user bank in one go. Anything else is refused, which is why ordinary sample editors don’t work without help. The card has to be FAT32 and 32 GB or smaller. The modules read the root directory (the E370 allows up to 255 files there) and show names in MS-DOS 8.3 style, uppercase. Longer names still load, they just appear shortened on screen.
WaveStack’s E352 / E370 target writes that bank exactly: 64 frames of 256 samples, 16-bit mono. A table of one 256-sample frame is written as a single wave. Other tables are resampled to 64 frames, and an 8 × 8 grid built in WaveStack goes in row by row as it is, so the X and Y you set up on screen match X and Y on the module. If your table is a grid or volume of a different shape, Export warns you before it flattens it.
No file name is required. Keeping names to eight characters just makes them readable on the File page.
Specifications
| Samples per wave | 256 |
|---|---|
| Waves per bank | 64 (8 × 8 grid) |
| Bit depth | 16-bit |
| File types | Single wave (256 samples) or bank (64 × 256), told apart by length |
| User banks | 26 (A–Z), stored internally |
| Card | microSD, FAT32, 32 GB or smaller, root directory |
| File names | Any; shown in 8.3 form |
| Width | E352: 26HP. E370: 54HP |
From WaveStack to the E352 Cloud Terrarium / E370 Quad Morphing VCO
- Build or import a table in WaveStack. For control over X and Y, make it an 8 × 8 grid with Build.
- Open Export and pick E352 / E370 (WaveEdit) as what the table is for.
- Check the summary: 64 frames of 256 samples, 16-bit. If your table had a different shape, read the warning before you go on.
- Save to the root of a FAT32 microSD card, or to a linked SD card folder so Export writes straight into it. A short name like
GLASS.WAVdisplays in full. - Put the card in the module, open the File page, highlight the file and click. The module checks the file and opens the load screen.
- Choose a user bank (A–Z) to fill, or a position 1–64 for a single wave. When the green dot stops showing red, the bank is stored and the card can come out.
Frequently asked questions
Do I need WaveEdit to make banks for the E352 or E370?
No. Synthesis Technology recommends WaveEdit because the modules only accept two exact file lengths, and most audio editors write WAVs of any length with a sample rate attached. Any tool that writes a 16-bit mono WAV of exactly 256 samples (one wave) or 64 × 256 samples (a bank) will load. WaveStack’s E352 / E370 target writes those lengths for you, resampling the table to 64 frames when it needs to.
How are the 64 waves arranged on X and Y?
Row by row. The bank is an 8 × 8 grid, X moves within a row and Y moves within a column, and wave 0 sits at the first row and first column. So the first eight waves in the file are row one, the next eight are row two, and so on. Z mode ignores the grid and scans all 64 in file order. If you build an 8 × 8 grid in WaveStack, it exports in that same order, so positions on screen match positions on the module.
Do user banks stay on the module when I remove the card?
Yes. Loading copies the bank into internal memory, and the card isn’t needed to boot or play. Both modules only read from the card, so you can’t save banks or patches back to it. Patches store which bank they use, not the bank data itself, so if you load a new bank into a slot a patch points at, that patch will play the new waves.
Will the same bank work on other modules?
Often. The WaveEdit bank format is read by several other modules. Qu-Bit’s Chord v2 and Weston’s HV1 both take it, and the Piston Honda Mk III uses the same 64 × 256 file, though it needs eight of them named 1.wav to 8.wav. Each module reads the 64 waves its own way, so the same file can behave differently on each.