4375aef7-38e1-49d3-8aa2-67876313b26a-image.png

I've finally finished the UI design for the VST.

Instead of going with a traditional interface, I decided to aim for a highly stylized fantasy aesthetic.

The layout is mostly set, featuring the Main, Atmosphere, Tuning and Mix tabs at the top. I've tried to keep the essential performance controls (like Tonal Shift, Lid Position and mechanical noises) easily accessible without cluttering the artwork.

Would love to hear your thoughts on the design and layout.

@TalesOfAudio Press F1 in HISE to view it offline - needs to be downloaded first time.

@David-Healey I have tried it on the latest commit but the problem is still there.

@David-Healey I’m changing the array right away. Thanks a lot and Yeah :D I finally got all the mechanical recordings done in the studio. Since I had already finished the grueling dynamic velocity layers a while ago capturing the mechanical sounds this time around was an absolute breeze in comparison.

By the way, I watched your Ardour video and built my own workflow for sample editing based on it. It is incredibly helpful, thank you so much for putting that out there.

@document-cat Full guide here: https://audiodevschool.com/courses/hise-bootcamp/

@Lindon Thanks so much. I assumed the forking suggestion wasn't the right move. It's so good to have such a great community with people like you and Dave H. providing expert support. I haven't yet communicated with Christoph but the experience using HISE as a newbie, truly shows how a community like this is a formidable asset 🙏
Thanks again.

@pratitghosh

HiseSnippet 1085.3ocsVEtaaaCDlxIJn1asXEXO.b9WJcAF1N1oIYXqI1wY0X0oF0YECXXnflj1hHRjBRzM0an.6waON6MH6Horsbi6Vgwp+iEOd228cGu6HGlpn7rLUJxqx0yS3HuuzezboNraHQHQ8u.48H+AjLMOE6D0YdBIKiyPdd67iFAdk2EY+82OqCIhHo7UhPnWqDT9KDwB8JoCO6mDQQWRX7qEwEzt0Y8oJYWUjZFvmc7qiRHzaHS4WQLpUxG8bRVHx6I9sadHsE6orlMaexQTxQ7SlPlLowgrVsN53SZb3IjVGeDudaj2d8XBsJcjln4YHuc6nXyGEptU5bvqEYhwQbyhFnQfmchuTEwLgnQJpanHhMbQhJCAnLbUZaGWZ6q8GHXhkxWk99J6F3UVTLA5UZc5syZzqQQ5Uu.81.k7JPoccT5w9inohD8pcL74K76KgSyID3bpHUb5hJ0eG+tJPCotVL4F9kovhkVDzrd8CvMpWe+uqRkJBYjPxwSlIoZgRhUxWwyD+NuyLs1bNJ0opn.pJNQIA7N.+VRzL99U9iJkW3hLt94bwzPc..J9acZfeBtswCuGbxBEmx0cW.TP0h9o59FTx8VWRTzXnnIXibwvZnBKSC9IEmf+d7B3IL1PhjGET09WipGfWFnIF7CpdqfoCA4MKJTn4wtBVXG2GY0R4LimrpLDpCzuRMSCYpfEYpfo1jvzZSf9fyihBzghLSHtFf6aRAqS4w.k6ImBXUilxgZlNoJBiZ6OC.DErSwUoVygJP4TNPqJkIoSyNE+qKifpg1Td0eyA+3ZDslPCuVs7bdDj4BpRsPjgc.lUMWYF6EBvgRvkI.XNsxUBPeYPd6A3PabZit6mtFPzg0RIRlJNXe7OfqWqM9YKShiMEBm9A4TGTo7DSVMvkeJT9ckRyeoLv5zJuuB9C2ZxjMtWd0QDDPaZayPpz+MCCjyhGySKVeaTDZDWu61+i2cWb3C0USVPQkruTneYBW9wFIgxKjMSBxYEnp1NG3Q4yAbsBHAyHpX2Axx6hSsQ+b+KHZxBz.fAmkvS0BSb3cA+svTc2Tlx9WvytQqRfAzK6PgX8S02uakeu3r4KW7mmell+NsYdU2HA8F7.92XhxkNXOmCd3hgbl1VK9Ov20BaP12yf0byGL3CaC.3h89q7vbU8nQJBc2ctKnt2rTXJthMKhnWezt4Bv7MfJh0lmZ5kjYB87hWP9+179OUJ9X+gBMMbybrzF3Hbj+4fi42R9P+dSlvo5UDbW+K+kOOWIhbScmBiYRElZgqlEOBNoobynQnBwzQ5Uxz63VWeQ8xHtjYWbG7KeyFl0d4a1XwlnXBMU8FpqiybO7CrR.NIsuYoL73IXMtw86whgmE7FJccntmgM2VCObaMr01ZX6s0vi1VCe51Z3w+2FZd014yzpXWaCBMXXO6LQOudRBTAZqVQ+CnzXxnJ

@amirvinci said in Sliders Interacting:

Should I report it under bugs?

Check github issues, I think it has already been reported but if not make a report and link to this thread. It's definitely been discussed on the forum a few times, it's part of a more major bug with the entire macro system but we have to wait for Christoph to come of his AI phase I think before it is fixed 😁

@Naledi-Leotlela You can use v26.x

@Quemis Enable isPluginParameter in the property editor for the controls

d7f14fe3-1294-4fb1-82dd-6a3016fb6e94-image.png

@David-Healey stash, fetch/pull, then restore stash should do, no?

@Sifres For Faust I had the same issue recently. Is your Faust node in a frameProcessing container by any "non-chance"?
That was my case so I've made a PR to fix it (in fact I made it then it was removed because I was fiddling around because I was trying stupid thing with git because I'm an idiot because... Well, I just re-pushed it)
The export wasn't processing the signal as frame, only as blocks...