Hi,

There are many technical topics I’d like you guys to cover. However, as a musician who got into HISE primarily to develop tools for personal use—and someone still on the fence about releasing anything commercially—I’d like to propose dedicating some time to discussing the state of the audio tools business.

I understand that the main goal of these meetings is to focus on HISE’s technical aspects, and the amazing folks in the forum have been great at answering any questions I’ve had so far. But I’d be very interested in hearing you discuss the business side of things.

Looking at today’s audio tool ads, you’ll often see absurd discounts (70%-80%), even for top brands. This raises the question: is it profitable at all?

Perhaps the more experienced among us could share insights about what it’s really like. Here are some of the questions I’d ask:

• What kind of tools do you release?
• Which ones have sold well, and which haven’t?
• How many units has your top-selling product sold?
• What pitfalls would you warn against?
• I imagine most companies are one-person operations, but do you hire help occasionally?
• What other tools (besides HISE) do you rely on in your workflow to release a product?
• Which services and fees do you pay monthly or yearly to keep things running?
• What kind of copy protection do you use, if any?
• Do you release for mobile platforms?
• What DAWs do you prioritize or release for?
• What back-end servers do you use?
• What is your pricing model: one-time purchase, subscription, or something else?
• How do you advertise? Do you create your own ads or pay "content creators"?
• Which platforms have yielded the best results, and which ones have been a waste of money?

I'm looking forward to the meet.
Cheers!

@Christoph-Hart Tested it, works perfectly here! :folded_hands_light_skin_tone:

@CyberGen New findings update: Even though changing the slices setting had initially yielded positive results, it was not solving the problem 100% of the time for me. After much trial and error I found a better fix by going into the sample editor window and moving the sample end just a few cycles short from the very end. This has been giving me consistent wavetable all the way to the end.

Hope this helps. Cheers.

@d-healey This is really helpful info David. Much appreciated. Thanks.

@clevername27 Yes! Exactly. This is the kind of guidance I believe so many of us are hoping to hear during the group call. Posts like this are not often seen in the forum itself, even though these issues affect all of us who are releasing or considering releasing products. Thank you—more of this, please!

@aaronventure Oh, I see now.

"CONFIRM_PRESET_OVERWRITE=0" no semicolon at the end.
:beaming_face_with_smiling_eyes:

It works now.
Thank You.

@aaronventure trace is more for like properties, I mean something like (see below) but instead of this customized code, the original or default look and feel code. It would be so useful as a starting point reference.

//	ALERT WINDOW
 	laf.registerFunction("drawAlertWindow", function(g, obj)
		{
			Console.print(trace(obj));

			var a = obj.area;
			var mA = [a[3]*0.01, a[3]*0.01, a[2]*0.99, a[3]*0.99];
			g.setColour(Colours.darkgrey);	
		 	g.drawRect(mA, 1);
		});

@d-healey Is pretty straight forward, below an example.

David, thank you again.

I will change all my paths to stings, its going to take me a minute. I'll let you how it goes.

Cheers!

//	GLARE 1
	g.beginLayer(0);
	g.gaussianBlur(a[3]*0.04);
	g.setColour(Colours.withAlpha(Colours.white, 0.9));	
	glarePath.loadFromData(glarePathData);
	g.fillPath(glarePath, glareArea);
	g.endLayer();	

Hello,

I'm moving this from a general question into a feature request.

Kindly requesting a way to change the base octave triggered by the QWERTY keyboard into HISE. This would be very useful for when you don't have a midi keyboard at hand and need to input notes directly from the computer-keyboard. "Z" and "X" are a very popular choice for + and - one octave. I've also seen apps that use the keyboard numbers for direct octave jump.

Below the original topic.
Re: Computer Keyboard Octave

Thank you.

I would like to propose the addition of a "Latch Mode" to the HISE Arpeggiator. This feature would provide users with a unique creative tool, distinct from the existing Hold Mode, to expand their musical possibilities.

Description:
Arpeggiator Latch Mode, although similar to the existing Hold Mode in some aspects, offers a distinct functionality that adds a layer of versatility to HISE's arpeggiator.

One unique aspect of Arpeggiator Latch Mode is that it automatically resets the arpeggio note pattern when the user presses a new set of keys after having released all keys. This behavior ensures that the arpeggio starts fresh with each new chord/note input, allowing for seamless transitions between chords and arpeggio patterns.

Some Benefits:
Enhanced creative possibilities with a unique approach to arpeggio sustain.
Clear differentiation between Hold Mode and Arpeggiator Latch Mode, catering to various musical needs.
A versatile tool for live performance and studio production across genres.

I kindly request the consideration of this feature addition, recognizing its potential to diversify the HISE experience for users across the musical spectrum.

Thank you.

@ulrik So I just realized, what you are saying here is that I should turn off the save in preset mode. That makes the setValue work. But not the default value.

@Dan-Korneff & @ulrik So, enabling "Save in Preset" works, but I didn’t want to rely on that for this, primarily because patches can be edited and that could mess with the initial setup that I'm looking for.

I wasn’t aware of the callAfterDelay() function. That did the trick—thank you for the tip!

I have to say, though, it’s still a convoluted way to achieve this, especially considering how many buttons I’d need to set it up for. I’m still wondering why simply setting the default value doesn’t work with script buttons. It seems to work fine with other components.

@ulrik I'm currently setting the value in oninit. I'd like the button to start in the on position. I had tried the .changed() as well as setting the default value property to 1, but neither of those did the trick.

Hi,

I'm encountering an issue where using setValue(1) on a button component does not visually update the button state, even though getValue() correctly returns 1. Here's a minimal example to replicate the problem:

const var button = Content.getComponent("Button1");
button.setValue(1);
Console.print(button.getValue()); // Prints 1

While the console confirms that the button's value has been set to 1, the button does not visually reflect the change. Is there an additional step required to trigger the visual update for button components?

@clevername27 will there be a youtube upload for those of us who couldn't make it?

@clevername27 said in Next HISE Developer Hang:

@CyberGen Few developers would disclose this information.

True, though I believe it benefits us all. Tho more we share the better. If there is enough interest, maybe we could conduct it using an anonymous form—a developer-sourced audio tool market study? Just a thought.

@d-healey This is really helpful info David. Much appreciated. Thanks.

@clevername27 Yes! Exactly. This is the kind of guidance I believe so many of us are hoping to hear during the group call. Posts like this are not often seen in the forum itself, even though these issues affect all of us who are releasing or considering releasing products. Thank you—more of this, please!

Hi,

There are many technical topics I’d like you guys to cover. However, as a musician who got into HISE primarily to develop tools for personal use—and someone still on the fence about releasing anything commercially—I’d like to propose dedicating some time to discussing the state of the audio tools business.

I understand that the main goal of these meetings is to focus on HISE’s technical aspects, and the amazing folks in the forum have been great at answering any questions I’ve had so far. But I’d be very interested in hearing you discuss the business side of things.

Looking at today’s audio tool ads, you’ll often see absurd discounts (70%-80%), even for top brands. This raises the question: is it profitable at all?

Perhaps the more experienced among us could share insights about what it’s really like. Here are some of the questions I’d ask:

• What kind of tools do you release?
• Which ones have sold well, and which haven’t?
• How many units has your top-selling product sold?
• What pitfalls would you warn against?
• I imagine most companies are one-person operations, but do you hire help occasionally?
• What other tools (besides HISE) do you rely on in your workflow to release a product?
• Which services and fees do you pay monthly or yearly to keep things running?
• What kind of copy protection do you use, if any?
• Do you release for mobile platforms?
• What DAWs do you prioritize or release for?
• What back-end servers do you use?
• What is your pricing model: one-time purchase, subscription, or something else?
• How do you advertise? Do you create your own ads or pay "content creators"?
• Which platforms have yielded the best results, and which ones have been a waste of money?

I'm looking forward to the meet.
Cheers!

@d-healey yes. The project needs at least one expansion.