We create a feature list for the next update fee?

[DigitalWhiteByte]

Requests relating to the essential features to eliminate the known limits of SYNTHMAKER.

In my opinion this is the case, but without repeating the things said by other people,
so as to develop a serious list of known bugs and features to implement,
but as I say essential, not progressive .... for now.

[MichaelBenjamin]

~ stream to midi module
~ sqrt, pow, abs, sgn for the codebox
~ double precision floats in code

[infuzion]

+ better green timing, or tighter triggering to Stream
+ VST2.4 support, or better yet VST3.1 SDK which is automatically backwards compatible
+ SSE3 & 4; needed for some effects, better to use 64bit audio for some other effects than oversampling. At least add to ASM primitive & a few key primitives, then we can make modules to do the rest.
+ reduced GUI CPU usage. There are many workarounds, but not easy for a SM novice.

[kirkagur]

+mem input + mem output from code.
+deactivate parts of code to free some cpu inside the code module!(like a selector).
+more poly voice access.
+improve the buses.
+wav,mp3,flac file read & write (32bit files).

[aliasant]

+Green Code primitive
+Bugfree triggers that dont get lost.
+All the new Audio related primitives that Flowstone now has.
+Double, Quad etc Mono to Graph/Float primitives. (same as Flowstone has)
+New Improved or better, redesigned Toolbox

[Tom7777]

+Sub folders in the toolbox

[exonerate]

Improvement to the code component (sqrt ,pow, exp,abs ect...) Flowstone has sqrt now so I'm certain we'll see that in next release. I think the synthmaker team should spend a good few hours just on the code component getting all these basic functions implemented for the next release.

Improvements to the Assembler component (Basically all the sse opcodes implemented)

These I think are attainable for the next release and I would be more than happy to pay an update fee to see them implemented.

Of course then I want the usual "green code component" and accurate events. But I'm not expecting anything like that until version 2.

Cheers

Exo

[trogluddite]

Just a few that I think are realistic in the short term (in no particular order of preference)...

-Assembler syntax to check variable names & labels like the code prim does.
-mono4 as an explicit input/output type for code/asm
-mono4 boolean data type.
-Real-time disk streaming.
-exe export support for multichannel audio
-Schematic search for modules, wireless links etc. by name/type
-Dockable palette or drop list showing currently available wireless links
-Read system variable primitive
-Test Probe window - choose links anywhere in a schematic to have their values/trigger-count shown in real time for bug tracing etc.
-Signal Trace - input a trigger at any point in a schematic, and see exactly where it goes by highlighting links.
-'Global' wireless links - have the option to send/receive regardless of module parent/child relationships
-User definable shortcut keys.

Ok, so I got greedy! - but looking again at my list, these would all add to FlowStone too. IMO some 'debugging tools' are a real necessity if it's to be taken seriously as a graphical programming environment.

[nix]

-exe export support for multichannel audio

This is vital.
So nice that SM is going to continue!

[tor]

I would love to be able to search through a schematic. Standard F3 to walk through the matching items. I find it strange that this feature is not yet implemented as it is standard in most aplications. Would be great to go directly to a primitive or module with a sertain name or find a type primitive. The search would be best if it was narrowed down in the hierarchy.

[Mo]

-Default preset manager bug fix.
-Disc streaming.
-Midi event stream trigger.
-Improve image rescaling/resampling if possible, as images gets very blurry at higher zoom levels than default.
-Improve search function.
-Open last saved.

[aliasant]

I got a couple more that came to mind.

+Wireless In icon on modules. Same as it now has an icon that tells us if the module has wireless going out and if its active or not.

+Restart Schematic for trigger/bug tracking. Now I have to save, close and then open a schematic to see what actually happens when it is first launched. A simple button that does that for us would be nice.

+Option to save/not save the file/s contained in eg. the Wavefile primitive. Now the osm. gets uneccessary big. A simple bool to turn that of/primitive would work well.

A note. Try not to list what others already has. Maybe the topic starter can make a clean list of what we got so far?

[Disco_Steve]

mem in + out in the code.
tick100 that gives still gives equiverlent to 100 ticks when running in greater than real time ie durring bounce.
currently lots of my things work fine in real time, the green not being exact is fine thanks to the existance of blue, but durring bounce downs, it all goes tits up
all audio and video related flowstone newbies moved over to SM too

[aliasant]

Another thing that is high on my list:

+ Windows Phone 7 export. Should be fairly easy atleast compared to Android and iPhone export.

[rl]

(ok, there are doubles, but..)

- sample precise timing

- FOR loops and branches (if, then, else) in C code module (i've no problem if there would be a non-sse code module)

- full support for double

- Float Array or Memory input/output for code module !!!!!

- Code module for green and V-data (like the uber-great lua module from the 2.0 prototype). Do it in Lua, in Ruby or whatever, but DO it.

- voice management!!! create and access indiv. channels

- read/write and process binary files!!!

- basic support for multitouch windows events (yes, I have a multitouch-able computer now). Should at least support more than one mouse drag at the same time and basic swipe gestures

- some sort of library system: export schematic or part of schematic as a module to a ascii readable format that can be included in other schematics. If I change the module, the other schematics will get updated too.

- and last but not least: a software development kit. As an easy start, a non-realtime SDK that runs in the GUI thread would be sufficient

?how much does a sourcecode license of synthmaker cost?