Eventide H8000FW - All about it... please post here.

OF COURSE!
You said "A Reverb w/32 delays"... and now is 2 diffusors (delays in each?) + 2 Hi/Low TONEs... that's very different.
Anyway... check total delay time in the RevD module. Stay below 16000.

 

The reason why a single REV_D w/32 lines doesn't load at 96K is the amount of delay memory used in the module. Lower it and it will run.

96KHz means you have only one DSP on board as high sample frequency cut the power in half.

You can load a 28 dlys REV_D with 2 diffusors in front of it and 2 highcut fiters after it.
Build the UI for the modules... don't just bring them up to the display... so unelegant.
You will be able to use the internal low cut filter, using a knob quantized to 1.0 dB for fine cuts. Works fine.
Custom built UI is also necessary to run the 2 diffusors from common parameters single knobs (Size, Diffusion). Size should never be 0%. Use a minimum of 1%.

The H3000 has plenty of waveforms but several of them are ONLY triggered ones. They won't continuosly run; a trigger needs to be used to make them run once. As it was on the H3000.
If you understand how to build a min/max limiting function with control math modules you could use the Random waveform to do what the Randomizer does with internal min/max values.
Check the presets on board... there's an encyclopedia of functions already made you can use....

 

A square wave will do nothing useful there as delay will either be X or Y. Nothing in between... no glides there.
But... glides are to be applied to the base delay, not to the modulation input... to really unwrap their powers!

 

Here's a GLIDE delay lab.
You can watch/listen to what happens to delays being directly swept, not modulated.
What you see are KNOBS swept by the LFOs.

Finally... the famous Henry Kaiser time/pitch stretch efx (PCM42)... DONE!

Enjoy:

"THE GLIDES"

 

Those are just for my own testing purposes... nothing concerning the user.

 

Study the presets... and the KNOBs.

 

@hydroquebec

Parameters justification...
you don't have a choice like in plain text writing on a computer, so you have to be smart:
-capital letters take space. Avoid them.
-parameters names can be shorter if necessay: dly for delay, dcy for decay, fdbk for feedback, etc.
-use blank spaces to get vertical alignment
-put colons right after parameter name, leave a space after colon, leave a space between parameter value and type:
you don't want to see "dcy:2.5sec" it's ugly. "dcy: 2.5 sec" is nice
Use the above as your compulsory rules for nice UI.
The format syntagm... use X.Y with X=the total number of characters you want to see, including the decimal point. Y=number of decimal figures IF any. Parameters values ARE to be considered in relation to min/max values for them (set in a knob) which make sense for the parameter max. or desired (might be lower than max.) range.
Examples:
for a reverb decay going from 0.100 sec to 100.000 sec => "dcy: %7.3f sec"
for a delay time ranging 0.00 ms to 2000.00 ms -> "dly: %7.2f ms"
for feedback ranging -100 % to 100 % -> (percentknob) "fdbk: %4.0f %%"
for an Lfo rate ranging 0.00 Hz to 500.00 Hz -> "rate: %6.2f Hz"

Often you may move a parameter value far away from its colon to align it to the upper one. Just insert blank spaces between colon and parameter value to move it to the right.
If you look at the factory presets you'll understand what I mean.

A nice UI will *ALWAYS* have:
-all parameters colons vertically aligned
-all parameters types (ms/dB/Hz/sec/%...) vertically aligned

**************************************

96 Khz is nice, I know... but I never use it UNLESS I have a real reason for it. Too heavy of a cost loosing 50% of dsp possibilities. You have used your gear at 48 KHz so far... won't be a disappointment anyway to stay there.

 

Elegant formatting gives the eye information in a much faster way.
Also consistency thru presets (same parameters names, same formatting, etc) helps for that.

This:


vs.

this:


Notice:
-colons/parameter last number/type (Hz, ms, %, etc,) vertically aligned
-only small letters... no capitals. I loved CAPITALS all the way when I STARTED!!!
-shorter names
-first right top line: "params" added to mean you are looking at a specific FX menu of parameters
-correct... depth in ms vs Hz. "db" should be "dB".

-if you sweep parameters values thru their full range their alignment WON'T change. If that changes... it means formatting is wrong.
As in the image below... everything at max... formatting still there!

 

More UI magic!

Some funky ones from the factory presets... BANK 13/ Films - Athmospheres

1312 DON'T GO IN THE CELLAR
Amazing preset with super elegant UI design by Scott Gilfix! This is a magic QUAD preset with those delay taps circling around your head! (Billy... got the 2 extra speakers yet?).
Look at the large graphic UI taking 2/3rd of the display... see those vertical lines circling around in a 3D layout? Those are 50 delay taps.
Cool, uh?



1310 A NICE PLACE !
One of my spooky things... still in quad.
I used a couple of graphic tricks to create a screen saver.
On the left side of the display you see 4 text lines... each one has a set of 8 words, so 32 in all. They change at different speeds... so you get a ton of different RANDOM combinations (vertically).
On the right side you have flying starts... yep... the old asterisk * is moving left to right to left... in 4 lines at different speeds... Here I used LFOs sweeping textmonitors values to create stars animation on the display.




ONLY POSSIBLE ON A ****ING H8000!

 

How about some ANALOG style graphics... like faders, VU monitors, round knobs, on line text help, trigger keys, graphic EQ curves ?

 

-Use my guide on formatting and you'll live happy. The manual may have something on KNOBS formatting...
-LFO frequency goes in Hz and it's called speed or rate, not depth. That's how much the LFO is sweeping a delay in time units, right? It applies to the MODDELAY mod input knob.
In delays modulation:
DEPTH is a knob tied to delays MOD input, specifying how much a delay is being swept from its base value in milliseconds.
RATE is a knob tied to the LFO rate/speed input, specifying how fast the LFO modulates those delays... in Hertzs.

 

Never seen those flags in any preset in my life, Billy.
Do you have a DSP4500 user manual? I think it explains formatting better...

 

Yes... you call an LFO cycle FREQUENCY but it will conflict with eq/filters parameters... so rate/speed are better choices...