Next HISE Developer Hang
-
@griffinboy said in Next HISE Developer Hang:
broadcasters / AI
I can help with the theory on publish and subscribe (broadcasters) and AI. If you tell me what you're looking to do, I can prepare something for the Hang.
-
@Oli-Ullmann Is there another day you suggest I replace it with?
-
@Oli-Ullmann I'm thinking one thing we could do is, as a group, create a list of technical questions for @Christoph-Hart that haven't been answered on the forum. Given the specificity and focus of your question, perhaps that would address it?
-
@HISEnberg I'm happy to help you one-on-one with package installers and HISE graphics over Zoom. We could also trouble-shoot the audio. DM me if interested.
-
@d-healey said in Next HISE Developer Hang:
I agree, at least for all the topics mentioned here.
Maybe it would be better to do a show and tell type thing since Christoph can't attend.
Certainly helpful, tho consider perhaps @griffinboy is helping @HISEnberg with ring buffers. I can help him with package installers and graphics processing. You were able to help @Oli-Ullmann with Father Christmas. Idea: If we establish what we're going to discuss before-hand, we can establish what we have the necessary expertise for, as a group. @Christoph-Hart is kind and generous—my read from him on our last meeting was that we shouldn't wait for him, and he mentioned something about February. If there is anything I can do to make the event more meaningful for you, consider it done. (Just my $0.02.)
-
Maybe you could add two more days in the week from December 9 to 15? At least here in Germany, that's a normal working week.
A list of questions for Christoph is a great idea! :-)
-
@ustk said in Next HISE Developer Hang:
Advanced graphics rendering, past the poorly supported OpenGL shader on mac, what comes next?
I can help you with this, either on the forum, DM, or we can chat on Zoom.
@ustk said in Next HISE Developer Hang:
Many of the questions that will be raised can be answered quickly without us discussing the piece of meet endlessly.
That's a good point (and likewise raised by @d-healey). If we sketch out what is to be discussed before-hand, and identify who has the necessary expertise, we can have a nearly-commensurate level of efficiency. At various times, I've seen you and everyone else answer complex questions in just a few sentences. (I'm bad at HISE and a mediocre programmer, so perhaps not a good example, lol). Perhaps a way forward is for us, at the meeting, to compose a specific list of questions for @Christoph-Hart that only he can answer, which I also think he'll appreciate and be proactive on. (Just my $0.02.) I also think that if we ply @d-healey with drinks and exotic chocolates, he can take us all to school.
-
-
@HISEnberg said in Next HISE Developer Hang:
@Lindon 's method
I've seen his installer and it's dope. If you hit him on the forum, or over DM, I'm sure he'll give you a demo.
-
@Oli-Ullmann Tell me a specific time and day, and I'll add it.
-
@clevername27
Ok, then I would suggest Friday, December 13th from 5pm to 6:30pm. -
Libre Wave - Freedom respecting instruments and effects
My Patreon - HISE tutorials
YouTube Channel - Public HISE tutorials -
@d-healey
Ah sorry, I was referring to Germany, i.e. Berlin. The previous Doodel vote also showed me this time, which is why I adopted it. -
@clevername27 said in Next HISE Developer Hang:
@HISEnberg said in Next HISE Developer Hang:
@Lindon 's method
I've seen his installer and it's dope. If you hit him on the forum, or over DM, I'm sure he'll give you a demo.
I'd be happy to do a walk thru for everyone in the
meetup but I m away from 16th to 20th inclusive...HISE Development for hire.
www.channelrobot.com -
@Lindon Can't do evening of 11th 12th or 13th either... sorry --- family's who'd have em...
-
@Oli-Ullmann I've added it.
-
Unfortunately all those dates don't look good here, maybe I can join spontaneously but I'd suggest you plan the dates and topics without relying on my presence this time.
-
@Lindon Next time. :)
-
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! -
@CyberGen These all sound like important and helpful questions. I'm not a vendor myself, but can share what I generally tell clients.
What pitfalls would you warn against?
Plan ahead.
Don't create a plugin, and then figure out how to market it.
Start with product idea, and then determine if and how you can sell and promote it. Ask yourself if you have the infrastructure to support customers and provide development. What are the possible technical problems (e.g. relying on OpenGL, and then macOS drops it), and how agile can you be in dealing with them?
Only after you have solid answers there should you consider development. Don't be afraid to kill an amazing plugin idea if it turns out not to be an amazing business one.
People use plugins, but they buy products. The hard truth is that the industry is full of incredible plugins that no one has, and ever will, hear of. And many leading products have poor quality over multiple domains.
Acknowledge your competition.
Know them. Foresee what's coming. But don't necessarily be dissuaded or intimidated. Being first, and being best, are often not the most important factors for success.
Have a plan.
As with musical groups, failure ends them—but so does success.
Be effective.
Focus on the areas of development that are critical for your product. Don't get bogged down in details that only you will care about. That's a hobby, not a business.
Focus.
Avoid casting too wide a net—as an independent developer, it's often better to serve a small segment of the market well. Likewise, if there's something that a small part of your customer base clamours for, don't be afraid to let it (and them) go.
Support Your customers, not your plugin.
I often recount to clients the story of a technical support rep I used to work with. He knew nothing about the product, and was incapable of diagnosing even simple issues. But he was consistently rated highly by customers. One reason was because he was essentially handing off the problem to a more knowledgeable rep. But the other was that he understood his goal was to make customers feel better about problems, not solve them. Listening—acknowledging the customer's frustration—is often the most important effective thing.
Contextualise bugs as a constant to be managed, not problems to be fixed.
As developers, we often have a strong motivation for our code to be elegant, clean, efficient, and bug-free. But none of these things are necessarily important, in and of themselves—only what their tangible results imply. Prioritise. There's a wonderful scene in a Microsoft/Apple biopic where Jobs laments to Gates, "But we're better!" And Gates correctly replies, "Nobody cares."
Keep your eyes on the prize.
At the end of the day, your goal isn't making cool plugins. It's building a sustainable business with the security and work/life balance you need to feel safe, secure and satisfied.
You can be competitive without having the coolest interface, the best features or superior sound.
Nobody can have the best plugin—but you can have the best product.
