Wavetable waveform view

[Lindon]

@Christoph-Hart said in Wavetable waveform view:

Hmm, works here too. Don't load a sampler or anything into HISE, just open the converter dialog, does it crash then too?

Also you might want to run it in a debugger, this will directly point you to the issue.

Clearly I'm doing something wrong - what converter dialog?

I opened the Wavetable Synth project - its got a sampler in it already... and a wavetable...

I tried running:

Tools>Convert samplemap to Wavetable Bank

• HISE crashes immediately...

I reloaded it, and deleted the sampler

Tools>Convert samplemap to Wavetable Bank

• HISE crashes immediately...

I loaded HISE and DIDNT load the project...(so empty HISE)

Tools>Convert samplemap to Wavetable Bank

• HISE crashes immediately...

[Christoph Hart]

Yes, but can you debug HISE, since it is a super trivial crash but it doesn't do it here, so I need to know where to look.

[UD AUDIO]

Same crash here. I also tried to convert the sample map in the tutorial project without success.

[LinuxVst]

Hi Christoph
here a re My Findings about Wavetables

first the Hise Stand Alone builds were done on a
Mac Pro 3.1 with Mojave 10.14.6 with Xcode 10
and Mac Pro 5.1 with Big Sur 11.2.3 with Xcode 12.5

When we Use Either the Develop or new-layout Branch
we can Export the Wave tables
after we export the wave tables we have to close Hise and re-open
to be able to play the wavetables

with Develop and new-layout we do not have the Wavetable Preview

When we use the Master Branch to Export wavetables the Hise App Crashes

if i open the project containing the wavetables created with
Develop or new-layout in Hise Master Branch
i am able to get the Wavetable Preview

i Found another Difference in Develop & New-layout Branch the LFO Wave has Steps option

but in Master Branch the LFO Wave has no Steps option!

Hope This Helps to Fix Everything!

[Matt_SF]

@BWSounds @LinuxVst Hi folks, I'm testing some things with wavetable synths. Everything's working fine but when I build my plugin (or the standalone version), it doesn't produce any sound.

The standalone build asked for the sample file, so I gave it to it but it still doesn't output any sound.

Did you manage to get it to work ?

[Matt_SF]

@Matt_SF Nevermind, it's just that the wavetable file wasn't been properly installed to the {APP_DATA} folder. Do it manually and everything will work fine.

[DanH]

@Matt_SF Are there any fun modulations you can do to the wavetables? Like position or warping etc?

[Matt_SF]

@DanH you can 'only' modulate the position of the wavetable - but you can apply all existing modulators (env, lfo, etc...)

[DanH]

@Matt_SF that’s the table index correct? I did stick a lfo on it but couldn’t hear any change to the sound…

[Matt_SF]

@DanH yes it's the index. But did you convert your samplemap successfully ? You have to spread your waveforms across the velocity range of the sampler and convert the samplemap to a wavetable using HISE's converter tool (default options should be fine).

[DanH]

@Matt_SF oh right - I just spread it across the keyboard lol

How do you spread across the velocity range?

[ustk]

What is the advantage of using a WaveTable over a Sampler?
Because if you can only modulate the position then a sampler can do it if you spread your waves in the samplemap.
Maybe it is an efficiency difference?
I'm asking because I began a kind of wavetable based on a sampler and I don't know if I better have to switch to a real wavetable module, I'm not familiar with all of those...

[Matt_SF]

@DanH just define the min-max values for each 'velocity' layer, define the LoKey/HiKey numbers, and run the wavetable converter.

@ustk the main advatage of using wavetables is that the transitions between the different waves are interpolated, hence modulating the position will be smoothed.
With a sampler you have 2 options if you want to do the same. Let say you want to go from sine to square :
Either you layer your samples like on the picture above, but when modulating the position, you'll get abrupt changes between sine-tri-saw-square (but maybe that's what you want / you don't care).
Or you can layer your samples so each one 'crosses' the previous and the next but this is like dry/wetting a signal, there's no "morphing" between the waveforms.
Try for yourself ! I personally like wavetable synths :) .
Christoph put an example project in his repo.

[DanH]

@Matt_SF right, how many velocity layers do I want?

[Matt_SF]

@DanH that's up to you . It depends on your project and what you want to achieve...
For an oscillator which goes simply from sine to saw, then 2 waves should be enough but for complex wavetables you should use as many samples as needed.
Your samples are the 'key-frames' you want to go through. HISE converter then creates the middle frames.

[ustk]

@Matt_SF Thanks, you can do a smooth interpolation from sampler group XFade too, hence my question

[Christoph Hart]

@ustk You can use up to 128 different wavetables for each note. If you're doing this with a sampler the voice count will rise up ridiculously.

[ustk]

@Christoph-Hart Ok I see. In my case I need only 4 waveforms, monophonic, so I don't think it is as bad.

[ustk]

@Christoph-Hart Oh, and I forgot to mention the user should be able to select whatever wave he needs between this group of 4 dynamically from a browser and even create his own shapes. So I think I better have to stick with a sampler...

[Matt_SF]

@ustk said in Wavetable waveform view:

@Matt_SF Thanks, you can do a smooth interpolation from sampler group XFade too, hence my question

oh ok, I'm aware of groupXFading but I never tried it. Guess I'm up for some A/B testing this evening :)