Topics created by MikeB

@virtuscapeaudio said in Forget sampling!:

Do you guys think that this will indeed get rid of us all? Or is there still a way to stand out and maintain sales? I can't tell if these comments are sarcasm or everyone is indeed worried about the sampling business at large.

Yes, old technologies may not have changed much. But the story of artificial intelligence is much more than this. With today's computers, a person's ability to complete a task that would take months or even years in a very short time, using another previously trained software with its own intelligence, is a unique situation in human history.

To be frank, it would be wrong to be too optimistic. In my opinion, within 10 years at most, at least more than half of the work (business) currently done by humans with computers will be destroyed by artificial intelligence. And unfortunately, software development comes first among the tasks related to computers.

We are now witnessing the infancy of artificial intelligence. We will also see this technology stand up and start doing real work instead of people.

There is no escape from this 😊

@Christoph-Hart @d-healey any updates or workarounds for this?

@DanH super - thank you.

@orange Hmmm.... Exactly.

@MikeB

SliderPack1.setSliderAtIndex(i, valuesIWant[Math.randInt(0, valuesIWant.length)]);

@MikeB said in A few questions of understanding:

If I have almost 100 knobs (in different panels) that should all look the same, a global LAF is better, isn't it?

If they all look the same and all have the same colours then it doesn't matter. I'd still go with local so that I had control over individual knobs and so it didn't make the HISE UI knobs look weird, but it really doesn't matter.

With a local LAF, I would need an additional 5-10 scripts for each knob for the individual LAF.

You can use the same local LAF object for multiple controls. I put almost all my laf in a single file. See this as an example.

all declarations in one script?
Does it make sense to collect all component declarations in an external script "declarations.js" or better in different scripts at the beginning of the respective function?

As I mentioned I put almost all my laf functions in a single file. I put component declarations into separate files, each with their own namespace. So if I have a set of controls all relating to a mic mixer, then they go in Mixer.js with the namespace Mixer.

@Lindon Thank you - it's already taken care of.
Both errors disappeared with the new build.

@d-healey I will find it - thank you

@MikeB maybe look at the sample loaded callback?

@MikeB Nein.

@MikeB said in inline function:

@Lindon
Funny, somehow I sent you to Australia :-)
But you are both in Great Britain.

...and it's tea time there and coffee and cake here in Germany.

Well I did live in Australia for 25 years...so maybe I seem Australian....

@MikeB said in Own Presetbrowser:

how do I bypass the preset browser?
Can I load presets via combo box?

Engine.getUserPresetList()
Engine.loadUserPreset(var relativePathOrFileObject)

You must be able to switch this off somewhere in Juce!

@MikeB I think the Preset system in hise will always kill all the notes when a preset is called, maybe you need to create your own preset system instead of a custom sequencer.

I'll bump the UI version counter then it will force-reset the workspaces.

@Christoph-Hart thanks for explaining!

You can also use Engine.saveUserPreset() Give it a file object (you can use the file browser to get this).

@Sounddiy - i remember - thanks

If you get stuck - Dave has a video :-)