Collaborative project!
-
@hisefilo I know @Christoph-Hart is rewriting everything around scriptnode and SNEX, so we might get lucky soon enough.
Imagine the CPU with a bigger graph (with delays)...
In fact, the only way to reduce CPU would be to use frame and oversample only where we need them, but it's not currently possible.At the moment, all my attempts (not to have a global frame) led to a crash, or just didn't work at all (I'm speaking about stk delay only, if you don't use them everything works fine without frame or oversampling).
You have to embed the whole graph in these containers
I don't know if it's normal behaviour or a bug (the fact that it's not working when inserted only where we need)My actual project is very big and still light on CPU because I'm not using delay, so consequently no frame or oversampling. And with maybe more than 300 nodes, the CPU maxes out at 3%... And half of the 3% is due to 4 limiters only...
But the next projects will be delay-based graphs, so it's not looking good for now... Finger crossed!
-
The
framex_block
nodes are not supposed to be used in an actual project (at the end), they are just useful during development, that's why the C++ code generator is part of scriptnode. This snippet should run about 10x times faster if it's compiled as custom node.However Greg is right, I am currently rewriting SNEX to be able to compile the C++ generated code from a scriptnode patch, so the workflow for using frame blocks in almost-native performance might be vastly improved.
If you don't want to wait (it's a really big TODO list here), you might get the CPU down to sensitive levels by using a
fix16_block
instead of a framex_block. -
@Christoph-Hart Cool, that's a thing I have probably read somewhere, but now it makes sense :)
If that can help, it is apparently not possible at the moment to make a custom node with a JIT node inside. XC throws an error when recompiling Hise... -
Yes, the entire SNEX thing is completely broken right now, it's being rebuilt from the ground up and there are many things that XCode (or clang) complains about which compiles on Windows, but I am doing the macOS fixes once every milestone.
-
@Christoph-Hart thanks @Christoph-Hart :)
-
@ustk just compiled the 30 January scriptnode commit on Mac and it does have the fix16_block thing!!!
-
@ustk and CPU looks calm (3%)
HiseSnippet 1425.3oc6X0raaaDDdok2jHE6fzhf1fhdfHHGb.RLjbcbaPO3ejkBDZThfoyO8jwZxwVKL4trjKssZQu2Wg168gnuEEnuA8Zu32f1Y4JYRZQmHqf3DDTdh6r6R9My7M+rauHoKDGKiHVU2dPHPrli5LPn52rOiKHc1jXcCZWVrBhrMh1XPHKNF7HVVUdrVfU0YIoOmr5FLelvExDQHuPxcgmvC3pLo8V66399sYdv17fbqd4053JEMk9xDDOUn0IgL2CX6COkoW1LTh0UZ4wUxHGESAwDqY2P5Mvou7HgY8ufGy20GzCZPbvOjQbaoumFw52IM6y885MRuiIDKZuLqPEiU3VztbO9oxyrF2LcB6rcj2dXMyqCdMxCu5kBuFk.ORNzMqAcHHjdI9LUQjocGCmfKK5o5HTfHlqFj2c8dEteBsGW41ub7NSI3EcTuqw6Pm+7zV6sG3px.6rz1uZZ8zW.hn031tZTG2HdnB++ZfL2vg1seUiB.xHlX86zVh84BXQ2H.g1lwgOETGIiNXg6z3N26as2KQ3ps11gQPHKB1V1ymMXgXVPnOrEti6auquz8.G9OB2q1OUqZsetV9MkhuMzqXA29Lg.7iGeY5fXgJR5ufHIXWH591Gx7Sx9diEGe0Iy7IEcDb0yBggKqfNLRLl0HGJyjdJnxDUBaXKYhhK1uKSEwOFSM7zj.GLcjKzbn1hxrlgn2Z5355wZxoCH7RG7u3yvIanGaMbxFiljnwAHTn7g9lTe+v2w2zNZs5gxjdnQ3ZsYtnwZPOlpuNvASRpPlIDsn6oLzJzkHHVOKJeBZBJH1ph9aNJGqA5MkAAZ7nyvN78Wx8z+Kp08wUX3YagTDc95tw4yXaUAMegPjhCZym9iazlTjeUMzlmtG+3FqrSJuhTPW97b5R9E8tRSl.zdCp7PHxDOr7wEg6syA2Bq58HduJMHwWwImKGwL8kLBmo.BiC8w5+mKBMSeFDZc4XCulFgUod.lAYGVQLNOMVcvhil5Cfnqrhkayh1GTokuXQX2QX+YlBHiFgUN5HPJpxTdnKW7BcJ37kS6xN9Lxt6ZOQdDDcl10HjmGFNlz6tliBB0kIxuRmCfiL1v7MZXXAapMjjwgwYTJc4+BZEIGWpFMP5Yx5UvUcq7D9Qq3RlQMSNF07TYrK1jqtmmFiy7ifEyl+C.lUZmG5QX+VULQDOOFzc5NxegqOYWetq9s2LOrRNdX0KNO7lW.d3MKgGdxpmOO7J5lQgwogjIGxmr53P96KExKuVIP9W9qBP929U8yeT.x0n0Wbokdzip+vzh6Wm1NB9gDP3NV7yIq9VB75kB7SVsLac8KnsdtTbauklpTBvyEubEZHvNSyAW2DnjNwGlIesrFO40bZPzwKeQkScPZwixC9rvSavGTFaSKACa5c34et7xc+fle4+72q7Emier0wXW1ww5CnoMhEyL+VO34c1joXZK4vlhyYxsr1DNj6BF6TUztEefRFV3Da2vL40oNXp+zKtHMf4yRGa+R1gf8iArnfIO74e2E+4jd2EgS7cW7LWE962NhIhCkwEqRBA7skBHtfiJFzQKlfkbxaJYQkN0Iq1FUxR2iCSkDkRKWOPlHJPHrpLUGcs3kKja8kbN1Y++KTIEtUlL39FtIfpivnCWebiVXpAeLHIEieJFUrGC6vejzhj7tRgLruTnqamw.1BvC2t+9Pw70koPqqTL73XmJ4VqsE3Cr3h4cPVHKJsp5zYKZL41hWm+51TCbs0Ql1ebbQXU9H5hvt.P4x3VXtL9GAL2H4Ntl6cRykuVpDTuEoWocUZW8X6FjCMUyoXie0IAXFwcbc0l6Gf1mx2yRSwd9poXOKOE64gSwdVYJ1yWOE64ads6QWLZ8DkLvDJhB50JsEEKqr1ypP9O.U.eI1
-
@ustk @lalalandsynth can uplease give it a try?. Last commit. FIle Hammond-B3-w-leslie.xml
This is far from pro leslie, but @ustk maybe can do some of his magic???? Basic feel is on track for my ears
-
@hisefilo Yes,sure, will try when I get home :)
-
@hisefilo Same here, I'm on it in an hour or two ;)
-
@hisefilo The simulation sounds very good!
So now you want me to add my Leslie again? But why haven't you worked with the commit I've made? -
@ustk I didn't know were to start on yours. I guess it's too much from my limited knowledge of scripnode :) So I basically did a sketch hopping you can add some of the tricks you did on your Leslie commit. (drum and horn split freq split?) don't know. just speaking my mind
-
@ustk @lalalandsynth do you think we are good for a free version already? or should we keep adding stuff? chorus. vibratos. IRs. etc?
-
@hisefilo I see, so I will re-implement mine, but a lighter version... It's too much work adding a ramp for transition, split, woofer and horn behaviour... So I'll just use the same than before, but lighten the filtering stuff
-
@ustk awesome!!! yes.
-
@hisefilo I think it's good for a collaborative project for the moment.
I wouldn't have (it's my opinion at least) a free/open plugin that infringes on people who try to make a living (on the same forum moreover) ;) -
@ustk ohhh. well. ok. I guess we are good to go then. you are right
-
So, should I finalize the GUI ?
What do I download specifically to work on , GIT noob. -
@lalalandsynth I think you can finalise around what we already have
You need to pull/fetch (or clone if you haven't already) the last commit. Tell if you're stuck somewhere so we can help you ;) -
@lalalandsynth :) yeeeeeah!!!