From the original SynthMaker forum (2004–2014), with its members’ names and dates.
rl ·
I'm a bit at the crossroads now. Should I abandon using Synthmaker and go native? Because SM is lacking some features I need (the usual suspects: stable green timing, extensibility, etc). Or is it worth waiting for some features being implemented. One aid in building my decision could be Outsim showing a roadmap of further SM development/features.
What do you think?
stw ·
Though i fear it could be very disillusioning - yes a roadmap would be fine.
MichaelBenjamin ·
even if it would not get developed any further, there are still so many things to explore, it does not matter. and that type of sandbox coding is just at the beginning of evolution so there may come up some other programs where you can apply what you have learnt here. however if synthmaker will be developed further with the crucial improvements it needs then this would be very nice. btw going native is no option for me, i would drown quickly when i delved into that mudhole of a vstshell.
trogluddite ·
I've no plans to move on from SM, but would be nice to have some idea where SM is headed, just to know which projects to pursue and which to put on the back burner. I have no particular 'killer plugin' that I'm aiming at; so in the mean time, I find having a few limitations encourages creative thinking and the mutation of projects into new directions - sometimes being free to do absolutely anything you want can be a curse as much as a blessing.
Anyway, as soon as any of SMs current shortcomings are dealt with, I've no doubt we'll all find plenty of new things to complain about! 😈
MichaelBenjamin ·
trogluddite wrote: I find having a few limitations encourages creative thinking
thats right, and usually this is also more fun, just think of the sid chip and what people did with it in the last 10 years, they made this thing sound awesome in its own special colours. and this is also one of the biggest challenges with computers that offer myriads of possibilities: to constrain oneself to an arbitrary made up ruleset and stick with it for some time.
trogluddite ·
MichaelBenjamin wrote: to constrain oneself to an arbitrary made up ruleset and stick with it for some time.
Interesting - I kind of work the opposite way around, I make many little tiny things almost randomly until I find something which catches my attention - and this iterates whenever I find I have reached a 'blockage'. Inspiration from what I see on the forum, or even things which are not at all DSP/Music related often give me a kick when I am stuck - or even indirect approaches like Eno's 'Oblique Strategies' when my focus is waning.
Sometimes I sure miss the days when I had only a cassette 4-track and a few guitar pedals - I sure made far more music back then.
MichaelBenjamin ·
yes, i think what you describe is the natural other side of this, wading trough the swamp forest at night with just a headlight, looking for other sources of light - you may meet some fairy that tells you something interesting, or you might find out that you followed some irrlicht (~errorlight, fen fire, i like that word) and take another route that looks more promising. then - if you have collected enough tales of the fairies in your bag of fantasy rule blocks you can make a camp and start building something out of it. so synthmaker could be aswell regarded as some obscure sandbox video game.
btw the times where the rulesets were limited by the hardware surely made things easier, but in hindsight also .. also a bit more boring?
Tzarls ·
I would for sure like to have some kind of road map - in fact, I asked for it before, during the times of 1.1.3 betas (in a thread named What to expect once 1.1.3 is out?). Yes, SM can do lots of things the way it is now, but there is one thing that it can´t do which is crucial for me - accurate green timing (or the posibility to delay MIDI events sample accurately). That´s why I´ve started doing some stuff in C++. But SM will remain in my toolset for a long time, I´m sure (I even used it to make it a scripter for building GUIs for my C plugins - if I ever get to finish it, I might post it here).
In the end, I find that SM has been a great learning tool, allowing me to concentrate on the actual DSP instead of also trying to make some obscure DSK to work for me.
If only SM has some "export to C++ code" feature.... 😉
sunsynth ·
Yeah - 100% for a roadmap!
Especially after FL-Version and now "FlowStone"
Latter got DirectSoundIn and the Audio-Selector that i cried 3 years now for... 😈
aliasant ·
No sure I want one. If there aint a "roadmap" I dont want to know.
If there is one, that would be great but if we "demand" one and Malc cant present it, for what ever reason, that puts Malc in a difficult situation and that would make us feel like there isnt any future, even if there is?
trogluddite ·
sunsynth wrote: [flowstone] got DirectSoundIn and the Audio-Selector that i cried 3 years now for
So robot makers are getting new useful audio modules and the sound making nerds aren't? This is very bad news. We have all supported OutSim for years both with our money, and by providing free tuition/documentation on the forum/wiki. While I can perfectly understand them wanting to expand into new markets, it would seem counter-productive and also rather ungrateful to leave behind their exisisting user base. Let's hope that this is not the case, and we will be seeing new Flowstone primitives 'trickle down' into SM.
MegaHurtz ·
too bad these topics dont get much responce from the people we adress them too. They might read em, but..
trogluddite ·
Unfotunate for us - but not surprising. No small company is going to attract new cutomers by admitting what they are NOT going to be doing with their platform. Notice also that the marketing for Flowstone DOESN'T say 'Built on the super-succesful SynthMaker engine' and is a DSProbotics product not an OutSim one - guess they don't want potential cutomers looking on the SM forum and noticing a load of users frustrated at the lack of development!! 😈
infuzion ·
trogluddite wrote: We have all supported OutSim for years both with our money, and by providing free tuition/documentation on the forum/wiki. While I can perfectly understand them wanting to expand into new markets, it would seem counter-productive and also rather ungrateful to leave behind their existing user base.
Well said. BTW, time=money, plus we have to pay for the computers & electricity we use, & are now missing the time we could have done something else, like make music, so nothing really is free.
I feel really burned on SM; I'll never devote so much time/money on a 1 man company again. One never can expect to get the level of support required from a 1-2 man team that is needed for a big project with a wide customer base. Especially if those people don't seem to even use their own creation. Little widgets from a 1 many company like AudioDamage is fine though.
mwvdlee ·
A roadmap would be nice. I fear there isn't one, though. I'd just like to know whether S|M is dead in a defective state. It's been awfully quiet apart from the release of FlowStone, which still has the same old show-stopper bugs as the most recent S|M.
Tzarls ·
Well, the last times things were so quiet around here, good things happened - or at least some things happened. Last time it was FlowStone, before that we had an "avalanche" of updates (from 1.1.3bx to 1.1.7 in a short period of time). So if things are so quiet now, I hope it´s because the guys are preparing something for us.
mwvdlee ·
Tzarls wrote: Well, the last times things were so quiet around here, good things happened - or at least some things happened. Last time it was FlowStone, before that we had an "avalanche" of updates (from 1.1.3bx to 1.1.7 in a short period of time). So if things are so quiet now, I hope it´s because the guys are preparing something for us.
And in the meantime it would be nice if they could release 1.1.7.1 or so with just a few bug fixes. I'd be happy to wait a year for new features, as long as the old ones are working. Heck, I'd be happy to not get any new features ever again as long as the old ones work.
infuzion ·
infuzion wrote: I feel really burned on SM; I'll never devote so much time/money on a 1 man company again. One never can expect to get the level of support required from a 1-2 man team that is needed for a big project with a wide customer base.
BTW, I think Malc did a great job for being a 1-man company. 😇
oddson ·
I almost voted 'meh' because my actual choice: "I'm no longer waiting for SynthMaker to implement the features I need/want and I'm looking elsewhere for that." wasn't listed.
Two years ago I was in the 'roadmap' camp but now it would be too little too late unless there was a clear commitment on short time frames.
I'm getting too old to wait.
If there was at least a Stream to Trigger primitive that would initiate triggers within a reasonable margin of error from a trigger sample (say 5 ms) I'd stay the course but I suspect even that's not possible in the short term.
I'm thinking the Max/Live combo might work for me since I'm not really about developing software for others to use.
I need to do complex and time-sensitive MIDI processing and SynthMaker is not up to it.
Nu Audio Science ·
Well it's been well over a month since anyone from Outsim even visited this forum but not so Flowstone So my thinking now is SM is not going much further as a standalone and as most people thought would just be a FLS add on That doesn't bother me as such but i am a little worried that we aren't being offered some kind of upgrade path yet to Flowstone
NAS
mwvdlee ·
Nu Audio Science wrote: Well it's been well over a month since anyone from Outsim even visited this forum but not so Flowstone So my thinking now is SM is not going much further as a standalone and as most people thought would just be a FLS add on That doesn't bother me as such but i am a little worried that we aren't being offered some kind of upgrade path yet to Flowstone
What bothers me most isn't so much that they have no upgrade path, it's that an upgrade wouldn't solve any of the current bugs. I wouldn't pay a dime for an upgrade right now. Although perhaps the HTTP components would be worth one or two dollar or so. I don't really need them, but it'd be a nice addition to the toyboxes that S|M and FLS currently are. You currently can't take S|M and FLS serious as production-ready tools, but they are fun things to play around with.
rl ·
I've always seen SM as a developer toolkit that relieves me from all that stoopid boilerplate coding needed in VST programming.
The SMX prototype was a promise for further progress, but that was years ago. Seeing the Flowstone thingy I'm feeling a bit deflated. At least it showed clearly there will never ever be some means to extend SM (API, SDK), because that would mean I could (in theory) build the functionality of Flowstone by just extending SM. Well, to be fair, extensibility was never announced.
But at least I want to know where SM stands and what to expect in the future. So I can make up my mind...
sunsynth ·
rl - You Took The Words Right Out of My Mouth!
I mailed malc before about some breadcrumbs (DS In and the Audio-selector) 4 us but never got an answer 🙁
I know it's not a biggie but it would show us we are not on the back burner...
exonerate ·
I'd like to have some idea where SM is headed. I mean we have all been waiting patiently for version 2 and accurate events, and then we get FL SM dropped on us and then flowstone, and version 2 is nowhere in sight. 😝
Now I understand these decisions are business ones, outsim need to make money. I think it's clear that SM on it's own just doesn't sell that well. Hence the need to expand into other markets, we can only hope that this expansion benefits SM.
I'd like to move over to flowstone actually because a lot of the features are very appealing to me. The biggest concern I have is that flowstone still doesn't have accurate events. I don't want to buy it and then have to wait and fork out money again for version 2, to get accurate events.
I don't understand why accurate events is taking so long, this is the biggest and most wanted feature for SM. But it just seems to be ignored and put off. 🙁
MegaHurtz ·
I think a the rush to green timing won`t really be "solved".. And I agree the signalrates are subject to your host at all times. The chalange of introducing string variables and fuller asm would be daunting. Yust becouse you`d be required to manage the io part, so that you can use it as a parser. And if so. the audio io part would probbably suffer the consequence. Sow maybe the "big step" lies in the minds of people who can bring this gap together. It`s a big puzzle to me.. and a puzzle to puzzle with at that.
Nu Audio Science ·
exonerate wrote: Now I understand these decisions are business ones, outsim need to make money. I think it's clear that SM on it's own just doesn't sell that well. Hence the need to expand into other markets, we can only hope that this expansion benefits SM.
The only problem i have with these thoughts is that to be honest flowstone is just SM in a different color with a few extra modules Don't want to jump to conclusions here but when you see this kind of step from a company it is normally last gasp hotel
I think a port to Mac (Never gonna happen i know) would have brought pretty much every single SE developer on board and a bunch of other Mac users who currently don't have a development package like this However this would have involved a lot of work rather than just recoloring and adding some modules that really should have been part of SM
For me now i am starting to think that SM standalone really should just be closed down and SM users made an offer they cant refuse to upgrade to Flowstone (IE very very cheap upgrade path) I mean in terms of business it makes much more sense to only have to develop one package surely ? On top of that the Flowstone community will not be getting the massive knowledge base that has been built up here by various users and then you have a splintered community
NAS
MegaHurtz ·
Besides that, the people here that want the most out of outsim. Are completely addicted. 😕
MichaelBenjamin ·
when i imagine this situation that malc (who _seems_ to be the only one still active who is able to actually code something) now needs to take care of: 1. flowstone 2. sm 3. fl sm which are all based on a similar base but differ slightly - it would be better to get the marketing guy on hold, and instead invest in some additional coder that helps malc to get things done, and then unleash the marketing. since my interpretation of how software gets successful is mainly by actual results and functionality, ease of use, stability, not so much on how its officially marketed. just imagine, if synthmaker would be developed with custom extensibility (module sdk) and a revamped accurate green system plus export options as au/mac vst/standalone with further 64bit support it would simply put all other current systems like max/msp etc behind and be the best development platform for anything dsp, including robots and whatever. but you dont need marketing for that (this would happen by itself) you need actual coding work get done. this is not to ditch the marketing guy personally, but just some thoughts about the procedures involved, so to say an excellent product for a good price is the best marketing there is. then put some initial ads for some time and the rest goes more or less by itself. but also i dont have a clue what the real marketing world looks like and i may be totally wrong. could aswell be some stockholders/investors business where its more about the money and not so much about the product. and sure malc needs to pay the bills and i wish him all the best on his path no matter what happens, but the current price for flowstone doesnt seem justified for me. what i initially thought of was more about 50-120€ for a 2.0 upgrade (sdk, stable green), not 500€ for some additional green com port modules. maybe i am just not anymore in the crosshair of the .. ehm marketing scope.
MegaHurtz ·
I think you made some good points MB, A good product is the key selling point. And it is increddibly future proof. Becouse us rich country`s are going to want and make nothing but quality. We have to.
exonerate ·
MichaelBenjamin wrote: when i imagine this situation that malc (who _seems_ to be the only one still active who is able to actually code something) now needs to take care of: 1. flowstone 2. sm 3. fl sm which are all based on a similar base but differ slightly - it would be better to get the marketing guy on hold, and instead invest in some additional coder that helps malc to get things done, and then unleash the marketing. since my interpretation of how software gets successful is mainly by actual results and functionality, ease of use, stability, not so much on how its officially marketed. .
Don't underestimated the power of marketing often the reason why a product is so successful is because of the marketing. Look at apple hugely successful company but there are much better offerings out there.
Of course the product has to be good, no amount of marketing can make a bad product good. But good product and good marketing should mean good success. SM is a good product but has bad marketing and I think has always been aimed at the wrong market, hence SM has not been successful.
And regarding an additional coder, it's my understanding they have one already who is actively developing Flowstone.
Freerideskier who is a member of this forum updates a blog on flowstones development. Seems he's the low level guy writing all the IO functionality.
Cheers 😉
Exo
MichaelBenjamin ·
apple has some of the best and most disgustingly perfect marketing that i know, and its backed up by reasonably ok products. microsoft on the other side got some of the most clumsy marketing in comparision, also backed up by ok products. and the difference is? 30-50% price. but hard to compare to sm, since its somehow the only app that offers that functionality besides synthedit. i could imagine the most of the "bad image" for these type of "toy apps" comes from the c++ coders which surely are afraid of loosing money and becoming obsolete when there would be a killer development program for all kinds of dsp which takes care of the shell and lets the user care about the code. so its not the marketing, but the changes in programming paradigms that keep being somehow in the way of sm (well plus its usual downsides like no sdk, green system).
bootsy ·
+1 for roadmap
sunsynth ·
damn dudes - wake up - Vote here +++
a really frustrating part is the missing crossgrade offer 😠
trogluddite ·
sunsynth wrote: Vote here +++
Shortly after the annexation of Tibet, the Dalai Lama visited the UK. As he was about to step onto the 'plane to leave, a journalist asked him,"So what do you think of Western democracy?". To which he replied, "I think it would be a good idea".
As a conscientious citizen I naturally cast my vote. But as the old saying goes "No matter who you vote for, the government always wins". Commercial considerations trump democracy - Don't hold your breath waiting for a roadmap.
exonerate ·
I'm not so interested in a roadmap per say, but just a comment from Malc giving a time frame for the release of version 2 and the major enhancements which will be included.
"We are aiming to have version 2 and the new accurate event system in beta stage by the beginning of 2011" would be enough for me, obviously that could be any date. And it wouldn't really matter if they over shoot that by a year. At least we would know it's being worked on. As it stands now version 2 and accurate events seems like a pipe dream, a mere fantasy of what could be.
SM could be a great piece of software but it falls short in so many areas. These shortfalls are also in flowstone, the user of flowstone are going to want accurate events as well . I wouldn't pay £495 for a piece of software that cannot send a trigger exactly when I want to send it.
Cheers 😉
Exo
mwvdlee ·
exonerate wrote: These shortfalls are also in flowstone, the user of flowstone are going to want accurate events as well.
Oh come on now, it's not like robotics and embedded electronics ever need real-time operations 😈
Shifrin ·
Been some time since I've posted on these forums. These days I tend to use S|M to prototype algos, then port to C++ and use the VST SDK (2.4). I'd have loved to have seen some of the often requested features added to S|M. It seems Flowstone is taking development in other directions though..
Shif.
Disco_Steve ·
I think they are holding back release dates to try to keep the cash flow. When you anounce a new product or a new up grade people hold back until that day. By the looks of things outsim has been slowly growing and the cash-flow is steady, there is no doubt some debts to pay, and a good cash flow is most likely vital at this time. The fact they can take on a marketing guy at this time in the economic downturn, shows that outsim are doing well. Not badly. However I too am concerned with the multiple products based on the same thing and thus have similar bugs.which will make updating a hellish task, unless you keep the same base code and add modules (just like they are doing with Flowstone)
The arcetcture of SM in my view means that good timing of green is not possible. And in effect an entire rewrite would be needed to achieve what we all want. And even then we are not using a real time system coded without an OS, so blue is the best we can have so if you need it time critical use that, the need then is for blue versions of the green components we want, but those have been made green due to their computational load, and so achieving what we want is near on impossible.
The fact they have released flowstone, To me shows that the underlying architecture of SM is actually what gives it its highly appealing and intuitive working method, feedback loops for example, try doing that in lab view! And so they are trying to maximise the profitability of the current product which should ensure the finances to develop the next version. I would guess that we are at least a year away from a major upgrade, At the soonest news will come at christmas, with a free upgrade to the next version if you buy this one sticker, everything needs to be rewritten, the amount of reusable code will be small.
I would greatly like to see a roadmap, but we will not be told as they know that it will in the short term reduce cash-flow, as us old gitts who want it arnt paying them any money!
mwvdlee ·
Disco_Steve wrote: However I too am concerned with the multiple products based on the same thing and thus have similar bugs.which will make updating a hellish task, unless you keep the same base code and add modules (just like they are doing with Flowstone)
I'd be surprised if they had seperated the code base. Supporting two nearly identical products is ridiculously easy to do with some C++ preprocessor code and a half-arsed built-script. They'd be utterly, totally and completely stupid not to. I've been working on a code base with four far more diverse targets and it works like a charm. So I'm guessing we'll see bugs and general improvements appearing in parallel for SM|FS.
Then again, FS already has a few generic and audio-specific components and we're not yet seeing them in SM. The fact that we haven't wories me a bit. Since there is really no concievable technical reason why we haven't seen anything new in SM for a while, the only alternative would be a marketing reason, and marketing reasons never benefit the customers.
Disco_Steve wrote: The arcetcture of SM in my view means that good timing of green is not possible.
Even though everybody says they want good timing of green, I think nobody really wants that. What I think most people want is to have a way of accurately triggering MIDI events. A simple MIDI output module with blue inputs is probably going to fix all the issues here.
p.s. One of the reasons I bought SM was actually BECAUSE it had regular updates. It had me convinced that whatever bug was present now would be fixed soon enough. For a few months, this was actually true. Had I known in advance the current reality, I would not have bought SM. Given the choice again, I would not buy SM at this date; it has severe bugs and no sign of them being fixed. I love tinkering with SM, but I bought it with the intention of releasing commercial products and SM is simply unfit for that purpose. So is FS by the way, which is why I have no intention of buying it.
Disco_Steve ·
sounds like you planned things through much better than we did on this one project I was on, a new customer wanted basically the same product, but with a tweek, and then another person with a different tweak, and before we knew it, nothing was compatible enough that updates across all the tweaked products could be made, and dev costs became so high we had to stop supporting the product. we then tried to start again, but we had a twat of a manager (who was then fired) who talked the talked (which got him the job) but in no manner of form walked the walk, so they never got past the basic architectural concept. because they couldn't decide the best way to do it. the end result was lots of money wasted, in an attempt to make the product indefinitely future proof which is impossible. in the end one of the guys in the team got really worried, and wrote a hacked together version in c# in about 3 weeks ('for fun') but was modular enough to work well enough and now that is being 'shipped'. software is crazy, its so hard to plan and get right. I don't envy outsim at all, as each bug must be harder and harder and harder than the last to fix, which is why they haven't been fixed yet!
steve
Mo ·
mwvdlee wrote: Even though everybody says they want good timing of green, I think nobody really wants that. What I think most people want is to have a way of accurately triggering MIDI events. A simple MIDI output module with blue inputs is probably going to fix all the issues here.
+1
mwvdlee ·
Disco_Steve wrote: I don't envy outsim at all, as each bug must be harder and harder and harder than the last to fix
This really depends on the guy that fixes it, or -- sadly in most cases -- the manager that pushes to get the fix in now. If you take some time, each bug fix will only make the code more robust and maintainable. If you don't, it just gets worse and worse. We all know the g****mn 80%/20% rule. (IMHO it's more like 95%/5%). And still people refuse to fix problems but apply band-aids instead.
Disco_Steve wrote: In the end one of the guys in the team got really worried, and wrote a hacked together version in c# in about 3 weeks ('for fun')
That's the way to go. If as a programmer you don't see the fun in coding challenging things, then why would you ever care about any code at all? </rant> (I spent most of the day finding bugs in somebody else's really, really crappy code. Being able to write code != being able to design software)
Tzarls ·
Wow! Please remind me of never ever showing you any of my source code! 😉
I´d really love to have a peek at SM source, BTW - just thinking of how it must be working inside helped me to figure out how to approach programming a plugin using a "standard" language.
attic ·
Hi
I'm considering a purchase of Synthmaker but it seems like you may be getting close to a 2.0 version.. as I'm a very poor college student who is dealing with a huge tuition increase would I be best to wait for the 2.0 version or is that a very long way off?
Thank You
Reply Malc
Hi
My apologies for the delay in responding.
I notice that you just purchased - many thanks for that.
We don't currently have a release timeframe for a second version of SynthMaker so don't worry, you're not about to find yourself out of date any time soon.
As you may have seen, we've been at version 1 for 3 years now. Over that time we've released over 15 updates many of which contained new features and enhancements and that has been and our main focus.
We hope you enjoy using the software.
All the best,
Malc SynthMaker 😈
attic ·
Even though everybody says they want good timing of green, I think nobody really wants that. What I think most people want is to have a way of accurately triggering MIDI events. A simple MIDI output module with blue inputs is probably going to fix all the issues here.
Yes that is what I want. It should have already been there and from looking at the product before I purchased it seemed that it already was. So +1 for me. Sigh!, SM not only needs better timing but also advanced voice management.
If I had known about the midi implementation or the lack off accurate output, I would not have purchased Synthmaker. It seems I was out of date before I even purchased it.
However this program is addictive and there is nothing else like it, not even Synthedit can hold a candle to it so I am glad I purchased it and am addicted. I'm a Synthedit user and it sucks for graphics there is no zoom on the build gui and it also has a very bad storage method for components. It does have an open sdk however and midi as well as sampling is well implemented. I think Malc could make the community happy with a few small tweaks but as with all things programming related it is slow going.
Modern developers should take a page from the Reaper community and allow the users to define the direction of development. Synthedit has set up a voting system for what will be included in the new updates. The last vote made it clear that the community over there wanted oversampling so that is the winner for the next upgrade to synthedit.
A road map would be good but direct involvement by Malc and interaction with the community here on a regular basis would be better.
Jay ·
Attic my sentiments exactly. This has to be the one and only forum based around a piece of software where there is absolutely no interaction from the devs at least not in a long time! i would not expect my customers to return to me if i ran my company like this.
there are no excuses passable for the lack of interaction between a software engineer and his/her user-base! it is a basic requirement of a customer savvy vendor to be in touch with the said customer and MAKE time for the customers concerns/questions and it is also a basic requirement for a successful business to have happy customers or guess what... there is no business.
Hmmm maybe i am wrong,maybe i should say F*%"k it,the next band that walks through my doors will get a badly done recording, half the tracks on their album from what they asked for and i should leave them with an unfinished album then ignore their calls for a while then move on to my next project...I would be dead in the water within 3-6 months.
The big fanfare about the new package was all well and good but since then its been taken as a great kick in the teeth to the SM users with the wealth of silence ever since and the consistent ignoring of the user-bases questions pertaining to the future of SM.
It is time for Outsim to wake up! ans start taking a bit of interest in these long beleaguered fans and its SM product
I have a busy studio to run,a farm to run and a family life to maintain all whilst trying to recover from my op and fight this F%"*ing disease and i have time to post here! So where is the excuse?
Malc? anyone?
anyway i am of to play with my new Reaktor goodies 😀
Best regards Jay
infuzion ·
This seems to further reinforce my hope that SM will be Open Sourced, but I'm betting it won't happen.
Disco_Steve ·
I think that would only happen if outsim died. and I doubt that will happen considering they are taking people on at the mo. but in ten years when version one is compleatly obsoleet mabey!!
Steve
Acrobat ·
MegaHurtz wrote: too bad these topics dont get much responce from the people we adress them too. They might read em, but..
sad but true 🙁
Disco_Steve ·
now that the country knows what the gov spending road map is, SM needs one too 🙂
mayo ·
A roadmap would be nice as we don't know if the 64-bit or OSX or VST 2.4+ support is even on its way (or in plan at least) or should we move to other, technological more advanced framework, offering these features today already...? 😕
Take this as a bump and +1
thanks
rl ·
oh yeah, I almost missed the one year anniversary celebration of this request! Still no roadmap in sight.
I'm using SM less these days. It's still great as a rapid prototyping tool for DSP algorithms, but SM is lacking so many essential features....
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker