Small update:
I currently have a build working on both Mac OS X and Windows, but I've yet to redo many GUI items in JUCE. I've done the most difficult parts, so the rest is just time-consuming.
The current build expires December 1st and I'd be surprised if the new build is ready by then. Still, it is progressing quickly.
So I'll repost the previous build with a delayed expiration date so I have a bit more time to complete the JUCE port.
SonicBirth v2 alpha
-
- KVRist
- Topic Starter
- 158 posts since 25 Mar, 2005
-
- KVRist
- 236 posts since 11 Apr, 2007 from Montreal, Canada
Thanks !makira wrote:I'll repost the previous build with a delayed expiration date so I have a bit more time to complete the JUCE port.
-
- KVRist
- 45 posts since 16 Feb, 2012 from Indiana
small glitch. when company name, url or email are left blank, and one attempts to save, the app crashes.
-
- KVRist
- 132 posts since 28 Jan, 2012 from Montreal,Canada
wow this is very interesting!!makira wrote:Small update:
I currently have a build working on both Mac OS X and Windows, but I've yet to redo many GUI items in JUCE.
Hi Antoine are you planning to add a software protection module & Serial Generator module using mac address
for exported plugins?
for the retail version (paid Version)
-
- KVRist
- Topic Starter
- 158 posts since 25 Mar, 2005
You want to sell plugins you create ? I'm still unsure the best way to go about this. If plugins are sold individually, I'll probably setup a store like the Mac App Store and handle distribution, payment, protections (and take my cut).Musik Man wrote:Hi Antoine are you planning to add a software protection module & Serial Generator module using mac address for exported plugins? for the retail version (paid Version)
:D
However, I was more inclined to make SonicBirth a subscription model, giving access to anything and everything under its umbrella, with some sort of revenue sharing for plugin creators based on usage or downloads statistics, à la NetFlix.
It's very tricky, I don't expect to have the perfect business model on the first try. What we are used to and most comfortable with may not be the best solution.
-
- KVRist
- 132 posts since 28 Jan, 2012 from Montreal,Canada
Hi Antoine thank you for the quick reply but i think you should sell a special version "Higher Priced" for creators who want's to sell their plugins ,
to take your cut on the plugins created with you creation tool would not be fair to the creator of the plugin
"it's like if logic or cubase would ask for a cut on songs created whitin there software
or final cut asking for a cut for video edited on it
i think that all other creators would agree! to pay a higher price for the sonic birth tool
but to give a cut on all plugins Not Sure!!
think about it!
to take your cut on the plugins created with you creation tool would not be fair to the creator of the plugin
"it's like if logic or cubase would ask for a cut on songs created whitin there software
or final cut asking for a cut for video edited on it
i think that all other creators would agree! to pay a higher price for the sonic birth tool
but to give a cut on all plugins Not Sure!!
think about it!
-
- KVRist
- Topic Starter
- 158 posts since 25 Mar, 2005
If you want to sell a video or a song via the iTunes Store, Apple takes up to 30% (same for apps, books). Other sites may charge less, but they all take a cut. Selling on your own is unlikely to generate any significant sales volume.
Also, videos/songs made via Apple/Cubase tools do not contain any copyrights related to these tools. An exported audio plugin contains a large portion of copyrighted software code.
If you sell it yourself, you'll have to pay for hosting, bandwidth, and a payment processor (who will take its cut, depending on how much you handle yourself, it will be between 2% and 8%). You'll also have to make your own marketing/visibility which you won't have without a central marketplace.
All of this is very likely to end up costing more than paying a commission, unless you have important volume.
Either way, you either have fixed costs + smaller commission to pay (but non-zero), or no fixed costs and higher commission (but with added value, less work).
I've been selling Mac apps for 10 years. I know from experience that selling by yourself doesn't always maximize revenue.
Anyway, I'll consider it, but a commercial license is likely to be expensive.
Also, videos/songs made via Apple/Cubase tools do not contain any copyrights related to these tools. An exported audio plugin contains a large portion of copyrighted software code.
If you sell it yourself, you'll have to pay for hosting, bandwidth, and a payment processor (who will take its cut, depending on how much you handle yourself, it will be between 2% and 8%). You'll also have to make your own marketing/visibility which you won't have without a central marketplace.
All of this is very likely to end up costing more than paying a commission, unless you have important volume.
Either way, you either have fixed costs + smaller commission to pay (but non-zero), or no fixed costs and higher commission (but with added value, less work).
I've been selling Mac apps for 10 years. I know from experience that selling by yourself doesn't always maximize revenue.
Anyway, I'll consider it, but a commercial license is likely to be expensive.
-
- KVRist
- 236 posts since 11 Apr, 2007 from Montreal, Canada
Personally, I want to make my plug-ins "donationware": offer them as free (as I've done for the past six years for the plug-ins I made with SB1), but now with a PayPal donation option.
Hopefully, that will be compatible with the licensing model you're considering.
Hopefully, that will be compatible with the licensing model you're considering.
-
- KVRist
- Topic Starter
- 158 posts since 25 Mar, 2005
Pretty sure this can be accommodated. Would you see any issue in requiring the end user to have a free SonicBirth account ?Kewl wrote:Personally, I want to make my plug-ins "donationware": offer them as free (as I've done for the past six years for the plug-ins I made with SB1), but now with a PayPal donation option.
Hopefully, that will be compatible with the licensing model you're considering.
The way I see it, every SB user will have an account on the website (either paying or not), and will be able to share plugins and ideas directly there. Non-paying user would only get access to a subset of the available apps/tools/plugins.
By the time SB reaches v1.0, I'll have invested more than 100k$ so at some point it has to bring revenues, otherwise I'll have to cut my losses..
In any case, new build on sonicbirth.com. Same as the old one, expires later.
-
- KVRAF
- 1602 posts since 14 Oct, 2002
yeahhh!!!makira wrote:Small update:
I currently have a build working on both Mac OS X and Windows, but I've yet to redo many GUI items in JUCE. I've done the most difficult parts, so the rest is just time-consuming.
The current build expires December 1st and I'd be surprised if the new build is ready by then. Still, it is progressing quickly.
So I'll repost the previous build with a delayed expiration date so I have a bit more time to complete the JUCE port.
-
- KVRAF
- 1602 posts since 14 Oct, 2002
hi makira,makira wrote:Small update:
I currently have a build working on both Mac OS X and Windows, but I've yet to redo many GUI items in JUCE. I've done the most difficult parts, so the rest is just time-consuming.
The current build expires December 1st and I'd be surprised if the new build is ready by then. Still, it is progressing quickly.
So I'll repost the previous build with a delayed expiration date so I have a bit more time to complete the JUCE port.
can we think about exporting 64 bit Windows VST ?
afaiu the whole SonicBirth will run on Windows!!!
a.
-
- KVRist
- 236 posts since 11 Apr, 2007 from Montreal, Canada
That could probably work. As long as they can use my plug-ins for free, if it's what they choose, I'm fine with a registration process.makira wrote:Pretty sure this can be accommodated. Would you see any issue in requiring the end user to have a free SonicBirth account ?Kewl wrote:Personally, I want to make my plug-ins "donationware": offer them as free (as I've done for the past six years for the plug-ins I made with SB1), but now with a PayPal donation option. Hopefully, that will be compatible with the licensing model you're considering.
The way I see it, every SB user will have an account on the website (either paying or not), and will be able to share plugins and ideas directly there. Non-paying user would only get access to a subset of the available apps/tools/plugins.
-
- KVRist
- Topic Starter
- 158 posts since 25 Mar, 2005
It's on the roadmap, but there's a lot of stuff to do before that.lalo wrote:hi makira,
can we think about exporting 64 bit Windows VST ?
afaiu the whole SonicBirth will run on Windows!!!
a.
-
- KVRist
- 236 posts since 11 Apr, 2007 from Montreal, Canada
I have a problem exporting: I was able to export one plug-in in AU and VST, but none after that because SB will export it, but with the same name as the first patch I exported. The "name" field in properties are different, but SB wants to give them all the same name...makira wrote:new build on sonicbirth.com. Same as the old one, expires later.
-
- KVRist
- Topic Starter
- 158 posts since 25 Mar, 2005
If you relaunch the app before opening another document, does it still have this issue ?Kewl wrote:I have a problem exporting: I was able to export one plug-in in AU and VST, but none after that because SB will export it, but with the same name as the first patch I exported. The "name" field in properties are different, but SB wants to give them all the same name...