When will the scriptode rewrite finish?
-
I am sure lot's of people are asking this. When will the scriptode rewrite finish? I have serious scriptnode projects but since the current scriptnode branch has issues I can't use. Also new rewritten version is more proper way to me.
Fingers crossed and we are looking forward to see the new, updated rewritten scriptnode. When will it be finished? @Christoph-Hart
-
Is there any info about the finish date?
-
I can't do an estimate because the task is so huge and the time that I can allocate to this is limited, all I can say is at least two months.
-
@Christoph-Hart Ok, I understand. Thank you
-
@Christoph-Hart so is there any progress? can we say version 3 will come approx. in one month?
-
@harris-rosendahl said in When will the scriptode rewrite finish?:
so is there any progress?
Yes.
can we say version 3 will come approx. in one month?
No :)
-
@Christoph-Hart so if the final version of scriptnode is coming soon. it will show several advantages .. 1 / less update 2 / less downloads 3 / less electricity consumed 4 / polar bears, you have to think about it!
-
@Christoph-Hart said in When will the scriptode rewrite finish?:
can we say version 3 will come approx. in one month?
No :)
If it is not 1 month, I hope it is less than a month then :)
-
@harris-rosendahl What feature are you waiting for?
-
@d-healey Scriptnode, ready to use for commercial plugins.
-
@harris-rosendahl I would estimate we're a minimum of 3 months away at least (but this is mostly a guess - not even Christoph knows the answer). Even once we're able to build and run the new scriptnode stuff there will be a period of debugging/fixes/changes before we'll all be happy it's stable/reliable enough to send to customers.
-
Thanks, yes I see. I hope this time period will be shorter as much as possible...
-
@christoph-hart So it's been 9 months since our last discussion, but we still can't see a working scriptnode here...
I think Hise looks promising but on the other hand, I also think since it's being one guy development tool (only Christoph, maybe rarely Dominik, but as we see it's not enough definitely), it's mind confusing and also disquieting for me!
Why the most important things are still broken or don't work but a LAF or other graphical things are being updated? Why it take so long, and why there are lots of bugs? Why are we still waiting for the proper working M1 support?
I think Hise needs more full time job developers who will make the updates and fixes frequently, I think it can't go like this with such a waste of time. Please do something man, this tool deserves proactivity!
-
@harris-rosendahl said in When will the scriptode rewrite finish?:
can't see a working scriptnode here..
Have you built the latest develop branch?
Why the most important things are still broken or don't work
What's most important to you isn't always what's most important to others - scriptnode for me is of little use (at the moment), but it's actively being worked on.
Why are we still waiting for the proper working M1 support?
M1 works. Christoph uses an M1 system himself.
I think Hise needs more full time job developers who will make the updates and fixes frequently
Because that worked so well for Kontakt :p
HISE has updates almost every day. The last couple of weeks have been a bit slower but it was the holidays. Today there was a whole bunch of updates, not just from Christoph.
-
You can use scriptnode in a commercial product - a few people (including myself) do already. I just can't guarantee 100% backwards compatibility because at this stage I'd rather do breaking changes than stacking up tech debt.
Also it's highly unlikely that there will be more full time C++ developers working on the project in the foreseeable future - making an open source framework is not exactly a money printing machine (against my initial gut feeling) - even JUCE is hardly breaking even and gets passed around like a trophy between different companies that want to improve their image.
So I guess you're stuck with me for a while...
-
@harris-rosendahl I just finished a project containing 3-4 scriptnode modules. You can maybe encounter a few hiccups here and there while developing but it works fine in the finished product.
Take a look at the develop branch commits, Christoph has made a bunch of scriptnode improvements.