@dannytaurus

This is also my recommendation.

(I can't speak for second hand, since I bought my machines new, but I bet it would be fine)

I didn't mention it, because this question was asked by a beginner who might not appreciate the bombardment, but my own personal setup is a lab of 7 physical computers with intentionally different hardware and operating systems (Two for Windows, two for MacOS two for Linux) and each one of these computers also has VMs as well as its native OS.

These are all hooked up to my main PC, and I interact with them through commands, so that I can work on code on my main development computer, and compile and benchmark on the other machines in parallel, almost as if they were remote.

I've found this to be ideal.
But I think there are "levels" to this kind of thing.
And depending on what you are developing, you probably don't need the most complicated version of this setup.

For example, I do choose different optimized DSP kernels depending on what CPU I detect my user has, and the same for GPU acceleration and other features. And so I wouldn't be able to do my work without this kind of setup.
But someone who just wants their plugin to simply work on Windows, Mac, Linux can get by with a more minimal setup.

@dannytaurus said in Anyone running Logic 12.3.1 on MacOS Golden Gate?:

You're unable to recreate the crash, or the config?

Both. I don't have that version of macOS or Logic.

I'm running ventura and an older version of Logic and I don't get the crash and AUVal is happy.

@David-Healey Thanks ,appreciate it!

@cartemtune Thanks, none of these are ai btw 😊
But I get it AI is all over the place...

So in the end is this fixed with HISE_COMPLAIN_ABOUT_ILLEGAL_BUFFER_SIZE=0 or the issue persists?

If this flag becomes mandatory then it should simply be the default behaviour...

Came here trying to learn something about instrument design and somehow ended up learning about decompiling laws and the current state of Claude

@dannytaurus SoundSync can currently receive information related to the product’s operation and the customer journey, including:

When the plugin is opened or connects to SoundSync Activation, validation, restoration, and deactivation activity The installed plugin version The product and license associated with the activation A hashed installation/device identifier for managing activations Interactions with SoundSync-provided areas such as activation, account, store, support, and update interfaces Timestamps showing recent validation or connection activity

This can be combined with information already created elsewhere in SoundSync, such as purchases, products owned, downloads, customer accounts, support activity, email engagement, and marketing consent.

That makes practical things possible. For example, a developer could notify customers using an outdated version, help somebody who purchased but never activated, exclude existing owners from a promotion, or create a re-engagement flow based on meaningful customer activity, cart recovery, etc, etc.

SoundSync does not inspect or collect the customer’s audio, MIDI, presets, parameter changes, DAW projects, filenames, or what they are creating. We are interested in product lifecycle events that help with licensing, updates, support, and relevant communication, not the customer’s creative activity.

We also try to keep the principle fairly simple, collect the minimum information needed for the feature, be clear about how it is used, and give developers the controls they need to handle consent and privacy properly.

Some of this varies by integration. For example, the HISE package can report plugin-open and SoundSync interface events, while licensing integrations naturally generate activation and validation events whenever they communicate with SoundSync.

@lijas90 said in Velocity layers overlapping issue:

I still get quite a noticeable jump between the different samples.

What kind of jump? Volume, tone, pitch, stereo field, something else?

@ustk upcoming as in the base is implemented but there's no real world usage yet which hardens the feature set.

The docs of the current website is nonexistent, but the new website has this covered thoroughly, you can take a sneak peek at the GitHub repo that hosts the new website content:

https://github.com/christoph-hart/hise_api_generator/blob/main/ui_enrichment/pages/components/ScriptDynamicContainer.md

Let me know if you run into problems (which you definitely will as first user)...

Enjoy a free 30-day trial: https://www.knobwebstudio.com/

composition-1789625533424.png

@dannytaurus Including the email marketing is a pretty smooth move. Does the % fluctuate at all based on usage, number of contacts, emails sent, etc.? Or a minimum monthly in sales?

I've seen Gumroad around but never used it. I went straight from the wacky world of Wordpress to developing and using Soundsync.

Is your reason for no licenses just less user friction?

I'd love to see the comparison in price! That's the type of thing that tickles my pickle.

@orange @David-Healey Thank you guys

@duma Try it, only you can do it :)

@dannytaurus This is super helpful thank you! It's pretty much as I understood it but this is a great way of laying it out. We're about to start proper beta testing so once that's wrapped I'll buy a HISE Indie license, already sorted the JUCE 9 EULA etc.
Thanks again!