@griffinboy
@Christoph-Hart

Sorry to bump this again!
Am I the only one experiencing this issue?

@Dan-Korneff

I reload the project and the volume for the hardcoded module is defaulted to -12
In addition to that, the parameter also seems to be acting as a modulator for the 1st parameter in the hardcoded fx slot

I'm on the latest build (updated yesterday)

@hyperphonias

No, it will probably require a bit of code. Learning how to script paint routines for panels is the best route. You'd have to script up each graphic, and animation routine.

If you want to minimize scripting as much as possible, you could use filmstrips.
Essentially you'd have a set of overlapping images which have animation frames baked in.
And you'd switch these images to different frames in order to create movement.
However, depending on what you want the UI to look like, you may end up having to layer lots of different images to create the effect that you want, and you'll have to create some code so that the right frames from each image are chosen depending on the state of the compressor. If your graphic design is particularly complex, this could be a fair amount of logic.

Truly the best option is to learn to use Panel Paint routines.
If you can already script a little in Hise, it's not too big of a step up. Ask for help and examples on this forum. The docs aren't easy to understand for a beginner.

@griffinboy
@Christoph-Hart

Sorry to bother: issue is still persisting for me! I don't know if anyone else is having this issue?

@resonant

I'll have time to look at it tomorrow

@resonant

Thanks for doing an analysis!

The reason I haven't shared this dsp on a proper post, is because it's not quite done.
I'll take a look and find the cause, it's supposed to be flat! Maybe there is a latency after all that I need to compensate for, either that or the math isn't quite right.

Does oversampling it help?

@Christoph-Hart

HiseSnippet 878.3oc0Ws0aSCCE1dsFsV.I.wC6w7.OLPHTSuvEwCL1ZGTAsTsNP7Fx04jUqkXG43LnBw+M9Iw+.vNocIEJkQfMD8gpdtM+4ykOe1HkjAwwREBW+vYQ.BeEx3YB8z8lR4BT+tH7kIGBw5tIggyP6NKhFGCdHLtxyrNfqUEk94KOYWZ.UvfbUHzajbF7RdHWmqczNufGDrO0CNjGVv616zmIE6ICjIFvTgz.EQYGSOBFRstsAA8bZ7TD9NjGAS.VKZi1tM7630tkO.Ma+vV2usamNslzpyCZ1dB0sIEguTOOtVpFqoZHFgqtqza13ox2KxNf2vi4SB.qfKZr4jyTuuLvydEsZQ6MkG3MZQVJFgvjQ44rJY4raRFv83mpOO2csTCN4QTLAh2XY3UYI34VDdMJ.uU.IbAHUMCRWmLlo3Q5bKY0x9BMn7ol5TQnj4KB+YxdRiCB88BoGC6qLBmFv1sZz3tNlut8i8SDLMWJbjhgRM7Jw12t9GqWq9mp678l78WoM6wnjAAfZklssFp0E31hjvIf5tNmPCRfSczb8WNmR944zhkbV1stfiRQeAW+pHP7yZDPySUle859coZpsPLWmwuHPo4VHf6BmXFCxJK0Hcg3i0xHyfvOTyLcKRuj.pd4VH6f1bClbvR0MawQDy0yJNH9Wqu5rBwqSFw0roqFiarBLZxTmGXb9z3UI878AlNGfUI6+1ymQuhGesEonmSUdLogCIkIMEAakqzIUKDyiAk6ZXTQnyHiJBsZFUD56YTGB52KUGaI4GJcDKjprNZR2RRSdoyKZxpmsZ05g2+ASeKwpeZu0XdXT.zSbBDXnXRw3MLbJ9zj.8BsK2UMPJjQSkBNqXqwAfVwO5HPUD6q7B8Ts17PbtlatyAP.PiKzocqcdIW.TkIOAkLW39a+B2JqWaQxfqicTv4Ootcg1lsVFzJmIFz+53s7roWnotMI89fVQc+Uu47OtBOGlM+WAyCjIZt3nATyX+GL6EMLIbr4cAFXfnP.A1ckvaX2pIStgU1BnwfvKU3qlOyM5ZkwyM5tv3ExYDRYJ46XYaAZYF1LUi4dKR++DpQFXkcbQoaFVbhIz7Fy6Xrk+S8CA1rrA1prA1trA1orAd+xF3CJafO7WGncEfmlnkgYDfHzfQ8RWqFi6InlN9TtFz2.DdO26N

Set the hardcoded synth volume to full.
Save as a project, and close Hise.

When you reopen the project, the volume will be reset to default (bug)
In addition to this, the volume seems to still act as a modulator on the 1st param inside any loaded hardcoded module.

@Christoph-Hart

The issue is still present in the latest build

@Christoph-Hart
I'll get back to you! I'm a version behind

The hardcoded module volume slider seems to be modulating the first parameter in my hardcoded network (c++ node)

In addition to this, the volume slider forgets its value when I save and reload the project, opening at a default -12 every time. This could be tied to the above issue, where it seems this slider has become a modulator.

@d-healey

It pertains to hardcoded modules so I'm not sure a snippet will do

@lijas90

@Christoph-Hart

There is a bug pertaining to volume on synth modules.

When I save and load in my hise project, the volume of the modules seems to get set to default.
It looks to me like the volume slider is also acting like an LFO on parameters... When I move the volume, it modulates the first param in my oscillator

@Ben-Catman

Ah yeah, I didn't include instructions here I see.
Take a look at my other free DSP posts. One will have a video that shows how it's done.

You have to create and compile a blank c++ node first.

Just dropping it in won't work because there are other files that hise needs to autogenerate.

@Lindon

Yeah, the feature request system is quite messy.
Not to mention there are bug fix type requests as well as feature requests. I'm not really sure what would make it easier though!

@Christoph-Hart

free / rand – Google Drive

Google Drive (drive.google.com)

I thought the difference was significant enough for me to want to model it.
Then again, I am a perfectionist when it comes to audio things like this.
It might not be significant to others.

But in some cases I do prefer the free running over random phase. The overtones in the highs have an evolving pattern which your brain can follow in free running, and I find that pleasing. Wheras random phase gives a chaotic and hard to follow pattern.

@Christoph-Hart

It's a big perceived difference in my opinion.
I can make some sound demos if you're not convinced.

@Christoph-Hart

If you wanted vca to act like a gate.

Imagine that you have a saw wave polysynth.
Hold down a chord and keep it held.
Because each voice is a different note, you get the phasing effect, you can hear the held saw chord coming in and out of phase.

Now, play the same chord in a rhythm.
The phasing effect stays continuous and doesn't get reset. The envelope sounds like a gate on the phasing chord. This is the effect you'll experience on an analog polysynth.

Whereas, if it wasn't free running, the phasing pattern would change every time you re trigger the chord.

There is no reason to do this other than analog emulation. Admittedly, free running oscillators make bass sound loose and worse. But it does sound really nice on pads since you get this feeling of continuity.

@modularsamples
@Christoph-Hart

I've done it in c++

I keep a global timer, and for each synth voice I remember the phase when the voice stops.

When the voice starts again, I look at the last phase, and the time that has passed, and I can make the voices start at the phase which it would be as if it had always been playing

It's the only solution I could think of. The reason being that hise voices inherently do no processing at all when they are not active.
This means that you have to resort to keeping track of phase yourself, and doing all the bookkeeping.

@WannaBeGUD

Timestretching like this is generally done via granular synthesis or spectral (FL is granular I think). You'll probably need your own custom solution (c++) unless Christoph codes a new Hise one. Stretching is kind of a difficult DSP, I suspect this is just how the hise one sounds. I think zynaptiq might have a good quality stretcher called elastic, which is open source? But their licenses have conditions.

Either way, you'll need to get your hands a little wet with this one and plug in a custom solution, or get someone else to do it for you.