SynthMakerskOre ·
...Could be used to more dynamically create code. So not just the still requested floats as an input, but whole sections of code built together.
Or is this just a stupid idea?
Possibly a mad idea: code component with a code input
From the original SynthMaker forum (2004–2014), with its members’ names and dates.
jorge ·
skOre wrote: ...Could be used to more dynamically create code. So not just the still requested floats as an input, but whole sections of code built together.
Or is this just a stupid idea?
That's a very interesting idea, I hadnt thought of it. I thought of having global functions that you can call from all code components. Your idea of just passing the code is probably a lot simpler to implement. I'll definitely give it some thought.
skOre ·
Yeah, and you know what? I don't even know what I could do with it at all! I just thought "If you pass poly and mono and in the future posibly even float data in, why not just pass code into it".
I feel like Zaphod Beeblebrox a lot atm...
lalo ·
one of the use that comes to mind can be i.e. share variables and arrays between code components 🙂 lalo
skOre ·
Yeah, I have this feeling, that by this, the code component would no longer be an entity within SM, but something more interweaved, it would be modular somehow...
stefan ·
jorge wrote: skOre wrote: ...Could be used to more dynamically create code. So not just the still requested floats as an input, but whole sections of code built together.
Or is this just a stupid idea?
That's a very interesting idea, I hadnt thought of it. I thought of having global functions that you can call from all code components. Your idea of just passing the code is probably a lot simpler to implement. I'll definitely give it some thought.
FWIW, the "code input" way is the way I always pictured it. Could be good to have a generic ToChild/ToParent for these connections. And a very good way to "spread about" code functions in your schematics.
Nu Audio Science ·
What a dope idea 😀
Tom7777 ·
Nice idea 🙂
Shifrin ·
Yep, just thought I'd chime in and say, what a good idea, too 😉
Shif.
bManic ·
same here.. fantastic idea! 🙂
infuzion ·
a neat idea; kinda like subroutines... would be great for mixing Code with Assembly 😉
Shifrin ·
infuzion wrote: a neat idea; kinda like subroutines... would be great for mixing Code with Assembly 😉
Yep, there are certain things that are only possible to do in the Assembler component (you could do in Code component but would take forever!), but if you want to use that you have to write all the other code in Assembler too - which is harder to do and harder to debug IMHO than writing in the Code component 😉
Shif.
fritzman ·
Old but still great idea. Or did I miss something?
TheAudiophileDutchman ·
One more vote to support this idea 😀
Shifrin ·
While we're at it, maybe there could be some sort of asm{} tag added to the code component, to mix and match code/asm?! Just an idea 🙂
Shif.
lalo ·
Shifrin wrote: While we're at it, maybe there could be some sort of asm{} tag added to the code component, to mix and match code/asm?! Just an idea 🙂
Shif.
i've suggested this some month ago 😉 ..nice idea to me... i'll have to seriously learn ASM 🙂
infuzion ·
Shifrin wrote: While we're at it, maybe there could be some sort of asm{} tag added to the code component, to mix and match code/asm?! Just an idea 🙂
Either or 😀 lalo wrote: i'll have to seriously learn ASM 🙂
I found a few good online book: [old link]
Kingston ·
Just chiming in,
what a great idea. Would be good to implement functions and/or hierarchy with this. (either with another code component or in pure asm)
Wrote something here? To have a post removed or your name hidden, write to [email protected].