New Layout Bugs (not feature requests)

[d.healey]

Loving this

[ustk]

@d-healey Was afraid I had to develop my own spectrum, now it's becoming wouaw :smiling_face_with_heart-eyes:

[d.healey]

@ustk This is part of the sample editor, not a component for the UI - but you never know what the future holds :)

[DanH]

@d-healey noice

[Natan]

@d-healey Nice, Where is This Beauty?
Develop Branch?

[d.healey]

@Natan Thread title may give you a clue ;) - https://github.com/christophhart/HISE/tree/new_layout

[Natan]

@d-healey Thank you sir, I Was watching the develop Branch, and Wondering why There Is no New Updates Since 26 Days ago.

is Everything mode to This New Layout?

[d.healey]

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

is Everything mode to This New Layout?

No. The new layout branch is where Christoph is developing the new layout, it will be merged into the develop branch when it's complete, or you can use it now if you want to help test it. In my own repo I've already merged it into the develop branch if you want to have the best of both until Christoph is ready to merge.

[Christoph Hart]

The sampler workspace is getting a overhaul at the moment and I added the spectrograph from the scriptnode test system to the waveform:

The idea is to have a slider to blend between the waveform and the spectrogram (here it's about 50/50).

[Natan]

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

own repo

Thank you so much, and thanks for the link

[d.healey]

@Christoph-Hart said in New Layout Bugs (not feature requests):

workspace is getting a overhaul

Can you add some keyboard shortcuts for shifting the pitch? Also can you prevent focused being lost from the mapping editor when adjusting the start position using the mouse in the waveform view? :D

The idea is to have a slider to blend between the waveform and the spectrogram (here it's about 50/50).

Looks awesome!

[d.healey]

• HISE crashes when loading project with external script files - JUCE Assertion failure in BackendApplicationCommandWindows.cpp:460

[Christoph Hart]

You mean if you use include("SomeFile.js") or if you connect a script to an external file (because I didn't check the latter for years).

[d.healey]

@Christoph-Hart The latter, connecting to an external file. Seems the bug was only introduced in the last few days, trying to narrow down the commit now.

[d.healey]

It's strange. I rolled back to a commit I knew would definitely work and I still had the same issue. So then I removed my .hise folder (that's the one that holds on the config stuff on Debian) then when I opened HISE everything worked, and that issue with the cannot find component with name... error is fixed too.

[d.healey]

Uh I'm narrowing it down by removing one config file at a time. Yesterday I setup pipewire on my system and it seems it's the DeviceSettings.xml file that was causing the trouble, changing the output device to JACK (which is still running through pipewire) solves it!

The component wasn't found issue was resolved by removing projects.xml but since this is recreated by HISE that problem returns on the next load.

[d.healey]

Last update broke the spectrogram slider :( easy come easy go :p But we gained external audio editor button!

[Christoph Hart]

The Lord giveth, and the Lord taketh away.

[d.healey]

• Table colours are broken, as in the table just ignores the colour settings.

HiseSnippet 728.3ocsU0sSSDDEdlRGBsJFIwGfdIjfjsHhl3EhzezFEnwhDuRxvrS6No6NylcmErw3M9x3qguA9H3qf2yE34r6R2BzTfl3dwl472b9N+NciLBYbrIhPqb3nPIg9PVuQZqWCOtRS5zjPeDaOdrUFUKi0tiB4wwRWBktvaQFzJkIoe+806x84ZgrfEgbjQIjePEnrEb6ty6U99s4txCUASn8V6zQXzML9lD.OKvbHgbwP9.49bTsRLBcwVtJqIpmkakwfN6ZbG0yyblNS+iTwpS7kHQcRO3hxXSZ3o7c6dYrFSHzxcKh7Exh7mv1S4pFyuHC73TA0JrXxb.szrfT86AjnS.oxYPZEVOQjJzVHAwyCXczPAoOGR0SBkLcIzewZX.Ez1MB3Cksi.hwFr51NNqWC9s1q5mnEVkQWyn22XkGnWcspeqZkpeuZsqKpe+oJCcSjw2WFMUwX0MZVFtpNI3DYz50Nk6mHGqHD9WMmt3cKmJxh5ITzn6nU1CBk4zsM9tXtBOeyJ.IOsg0hbDBPwlVIVNuRbHGcrBtikXomqSRA+j87tbKOsck7oNMwy42Gb0f6BkQVEFUzlxSggirJcEVSY7PqILU2fPiFABsxs58uRnL5O.uNBO7N3vYJWqGRrMkP7jpAdVj5K.0ICtb5pxhNN+4BDsJqLnf6OufbMtahrI+97yylcuQOJLcXbS741qNxf6FxE.07qzmhMi5Xkczj6NtGyQNybN5tBwUXcUVg2zwXoofQnL9+.i4aeVl0peeovV.vxr1eddW0bKt+ilDqROXOtMRgMP6mDzCJ0BI3csV5GiMLkvIhLZGjFy.8jZ2ThKfubg0QZZtv5WJjDvEQliEYyQ39skR4.XRmtNuB7tBPWa7.Di4rgCI.V0drPfg+SggzoaylygMOaNrYq4vlmOG1r8bXyKlCad4LsAek6MIVSP13.vnaqz8WTZKMtsIsKj7Oz2MsXK

[d.healey]

• Content.addScriptedViewport() is apparently not a function... but Content.addViewport() is, I think the api/docs need updating.
• Double clicking an item in the API browser doesn't add the function to the script as it used to.
• setPropertiesFromJSON() Also not a function. Never mind, this is the answer.

What does this button do?