@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.

@d-healey in regards to the scripts-disconnected issue, I was able to trace it down to a Engine.setCurrentExpansion() call. It seems that when this is called, it moves all user scripts into a "user" submenu and then the scripts show as disconnected.

Can you please help me confirm this?

• Add the code below to an external script file like the on in the post above.

• Uncomment:

//Engine.setCurrentExpansion(expNames[0]);

• Hit F5.

• Your script menu should now have a "user" stack and the script should appear disconnected.

const expHandler = Engine.createExpansionHandler();
const expList = expHandler.getExpansionList();
const expNames = [];


//Set Default Expansion
inline function setDefaultExpansion()
{
	for (e = 0; e < expList.length; e++)
	{
		local p = expList[e].getProperties();
		local n = p.Name;
		expNames.push(n);
	}
	//Engine.setCurrentExpansion(expNames[0]); 
       // this can also be:
       // expHandler.setCurrentExpansion(expNames[0]);
     
};

setDefaultExpansion();

@d-healey will do. Thank you!

@d-healey @CyberGen said in Console.blink() not blinking?:

I haven't been able to reproduce it.

I take that back... I wasn't doing it correctly... I can reproduce it now.

simple test

Content.makeFrontInterface(600, 600);

Console.clear();
Console.blink();
Console.print("do you see me?");


//Move this to external file.
Console.clear();
Console.blink();
Console.print("do you see me?");

HiseSnippet 687.3ocsUssSaCDDc2PLpw8hJR8CvhmBRHHokBUpO.kboJpMPTCE02PKqmPVk06ZsdMknp9O2+f1YsCXmRDWhZ8CQYtb183YNy3AFMGRRzFBs1ISiAB8YdCmpriaMlITjdsIzW30mkXASPtqCmFyRRfPBktxGcNn0pRxd909GxjLEGJbQHmpEb3yhHgsv6fC9jPJ6xBgSDQkxdmC5w0pVZoNE4yJdMHwL9D1EvQLWZU7HzU6DJrZyPKyBIXNGpCmNbr96p77OUjHNWBNiljg3Ak6lzZrPFN3520DBgVcPwa9J4u4uxquHTbi+hJvKyBDTfnbMfV4tnTyGAknknT0bJsl2PtQDaKh33yS85ovFxHFVpKSk7bIUtf50RiYnraEwl.cMnwMHpuaiFaFf+rw688wzRzRXKtDXl5nmqcbtTnlT1QrQnr0WOTGLUmFj.PPDr+5tyve6s6quDBriEIAVc.bEdSJlLXj.w8O3JFkp3VgVEnUGosvwp5a3+C+Z9+zO3uCMZzBi4pFFsTBlEF1oBM2Ev5pznyAylAWxjovMIhso468q9v5877lSoD0pdJg83XXlcWsLz0Sc++1JExrtK9uu1qMyxbhmY9v7hAiU3nCsMbIN8kKkp40FRlX0w372szYnBWGlJY14k8t46YAv5wbZMmdRkHrSKO++HlEZbmyBOTJtl2.gkOdwbrxB3HVo9evwYaPdtWmQi.tsffU859skccw8b8eQmZEpK5yrFwUDp2QoQCwEmb.uckBj3g6Qq3TK41Mb1tJvPPElY7a7YVvlNa5rfMuNHIhwM5y34SAtcTOIyCxIU1J4Z32FP6fljrIix04Hbk4Yb97G0s.95kE3aVVf6rr.e6xBb2kE3dKKv2c+.ceQ6CoVcT9XCgzePmrUITZGECUfYpUxePQoUzR

@d-healey I haven't been able to reproduce it. I started from a clean project. But I can't get user files to stack in the way the are show in the gif.... Somehow this is al related to the user/docu/etc stack and this particular project.

@d-healey Check out the gif below. I start out in "onInit" with a blink and a print and it works. I switch to my arp.js page, and not only does it not blink or screen print, when I hit F5 it switches the combo box to show the script editor as disconnected. This happens with all other user scripts.

What could be causing this?

@d-healey no, it's not that. Things are working beyond the blinking point, and I moved it to the top for testing.
I just noticed that it works when I'm working on the onInit script but it does not work on any of the includes scripts. Weird.

@d-healey uh yeah, it does

what the?

@clevername27 great alternative when you need a debug hint and you don't need to print out something. But it stopped working for me. Along with the green mini printout that shows up next to the actual line of code.

Anyone one else missing these debug tools?

I'm using version 4.

Hi,

I fear I may have turned something off.

For some reason Console.blink is not doing it's thing. And Console.print() does not display the green mini print-out next to the code. Only prints inside the debug console.

Is there a setting to turn these things off that I might have inadvertently changed?

@CyberGen fortuitously discovered that setting the ignoreNoteOn to 1 acts as a reset signal. Whenever triggered, the LFO goes back to the start of it's cycle without having to play a note. You might sometimes need to set it back to 0 immediately (depending on what's required of the LFO) but it's a good workaround. :clinking_beer_mugs:

Hello,

A feature request, if I may.

Current Way Point (0-1): It would awesome to have access to the LFO's current position in its oscillation cycle. For lack of a better term, I'm going to call it wayPoint. A normalized value 0-1, where 0 represents the start of the oscillation and 1 represents the end, It would allow tracking for customizable visual feedback for the user.

Currently the only way I've found to get around this, is to create a "paired" LFO in saw mode, which runs parallel to the "real" LFO at all times. This trick gets me that 0 -1 position. Needless to say, It's not a great solution, as they fall out of sync from time to time not to mention doubling all my LFOs just for this functionality.

Equally useful would be to have the ability to set the position of the LFO to any point of its oscillation cycle, without playing synth notes or using ignoreNoteOn . This can be used in many ways, including customized step sequencing , multiple LFO syncing, rhythmic sound shaping, etc.

That's all I got.

Thanks for considering it. :folded_hands_light_skin_tone:

Hi,

I need a way to reset an LFO to the starting point of its oscillation, no matter where in the cycle it currently is. Ideally, I would like to do this via a script or control without relying on IgnoreNoteOn.

I was going to request it as a feature, but I’m wondering if there’s already a way to force it back to its initial phase position. My goal is to achieve a clean LFO reset without affecting the rest of the synth or triggering unwanted sound events.

I had posted about this a long time ago, but I can't find the post now.

Has anyone managed to solve this issue or found a workaround to reliably reset the LFO in this manner?

Any insights or suggestions would be greatly appreciated!

Thanks!

@Soundavid Hi,

I'm using the table mode in a similar way, and I was wondering if it's possible to change the button's text with a callback (not in the onInit).
For example, in your table, could you change the text of some buttons in your 'MIDI Learn' column to say 'Unlearn' if certain conditions are met? Or, once I set the text in the onInit, am I pretty much committed to it?

@d-healey awesome! thank you.