New Layout Bugs (not feature requests)

[A Former User]

@Christoph-Hart Jeezz!!! That's awesome Christoph!!!
EDIT: macOS builds ok... 142 warnings though... But hey, it's Christmas time. Time to light up that XCode tree

[A Former User]

@Christoph-Hart Super handy!! I also love the alt-click preview function you added recently. But know when I am editing ac curve and want to preview with alt, it creates an automation point asap. It'd be perfect if alt was pressed, no automation points are created!

Also, waveform refresh after disabling the curve is only happening on re-engaging it...
And I suppose it is on purpose that you can spawn as many of those automation windows as there are gremlins in a rainstorm!

Forgive my excitement... this is really, really nice!!

[LinuxVst]

@Christoph-Hart

Thank you so Much "Autotune" this is Incredible!

[d.healey]

Yep builds here too :)

[d.healey]

I think this is related to what @UrsBollhalder was saying, when using MIDI selection the waveform view isn't updated when a sample is selected in the mapping editor.

Is it possible to copy the envelope points from one sample to another, either in the GUI or via scripting?

There's a funny interaction with envelopes and loop points. In this example the pitch changes during the loop, this actually causes the very start of the loop to also have a drop in pitch.

The fade in/out starts and ends based on the length of the sample rather than the sample's range. This means the automatic envelope won't do anything (or as much) for samples that have been trimmed inside HISE.

[LinuxVst]

@Christoph-Hart

• Thank You Now it is Fixed with the "new_layout" uploaded Oct 15 3:25 AM

[d.healey]

@LinuxVst Confirmed

[A Former User]

@LinuxVst On my system as well...

[d.healey]

@LinuxVst These errors are something to do with the backend waveform display, for some reason it's trying to include them in the frontend compiled plugin. If you use USE_BACKEND preprocessor definition then the error goes, but you'll get new errors and that's not the correct way to solve it anyway, I was just testing :)

[crd]

The analysis.oscilloscope node crashes Hise when you click on it in the latest new_layout build.

[Natan]

What Commit You guys Built Successfully?
@d-healey One won't build here, windows 10 / VS 2017

Edit:
This One Built Succesfully
https://github.com/christophhart/HISE/tree/8764a2879e8243b9eb6336291e2dc02e79b9d6e6

[Natan]

Trying to Understand Whats Going On :)) HAHA,

I'm In-love With the New Design :)
You did a Gret Job Legend :folded_hands:
@Christoph-Hart

[Natan]

@d-healey @Christoph-Hart I Just tried To Export a Simple Instrument with the latest New Layout Commit, Looks like it is not ready yet, Correct?

There is nothing in Compile Folder and The Output windows Stopped somewhere,

[Christoph Hart]

@d-healey said in New Layout Bugs (not feature requests):

and that's not the correct way to solve it anyway

That's exactly the correct way to solve it :)

[d.healey]

@Christoph-Hart Say whut... we should put USE_BACKEND=1 when exporting our projects?

Oh I see what you did. Yep it works great now thank you!

[LinuxVst]

This post is deleted!

[LinuxVst]

@d-healey
"on Mac OS"
i Tried again changing com.myCompany.product
to com.linuxVst.vdrums

it say's "does not match the required format"

if i Click OK it Reverts to the Default com.myCompany.product

" But if i Click Cancel then it Stores the new bundle identifier"
it just always show that warning no matter what you enter!

[d.healey]

com.linuxVst.vdrums

Works here.

[LinuxVst]

@d-healey
Ok
i Got it!
it's just that i will always Show that
Wrong Input no matter what you write!
just have to click Cancel and it Saves

[d.healey]

@LinuxVst said in New Layout Bugs (not feature requests):

t's just that i will always Show that
Wrong Input no matter what you write!

Not for me