#13

This is great. It’s awesome to see the work we did in Dronecaster grow into an extended exploration of how to make engines more flexible.

2 Likes
#14

I was wondering if there was any correlation to maggie and sarah’s band. i lived in olympia and knew them when they were first getting started with that band (and going through a lot of drummers).

1 Like
#15

yeah all the dronecaster sc props go to @license!!

really beautiful work on this @zebra.

2 Likes
#17

Just a quick update …

My script pixels is up on the library and this is working beautifully for me. Thank you!

I’m working on adding a way for users to swap engines from inside the app … but I’ve noticed that both exp and lin klang engines are not making any sound. Also, the sinFMLP doesn’t seem to change much when scrolling mod1. I do not currently have a way to scroll mod2 from my app, so there may just need to be some interplay there. Not quite sure.

#18

those sounds work for me when editing the parameters in awake_bangs. lmk if that doesn’t work for you. if it’s only in your script, maybe i can help dbg at a later time. (but ATM i have no time)

#19

Plugging a dummy value (100) in for engine.mod2 makes those engines come alive. It seems as though if the mod2 parameter is not specifically initialized with a value, those klang engines make no sound. Perhaps your version of Awake always sends a value out, whereas other scripts may not, causing a possible issue?

I’m just reporting my findings here, no need for debugging.

Thanks so much for this.

#20

ah i see - you’re right. values of zero for mod2 will be silent on those. (and zero is the default.) any nonzero should be audible. will fix

thanks

#21

I’m still working my way through implementing all of the exposed parameters from your engine into my script “pixels”. I seem to have come across a bug or at least an inconsistent behaviour.

The engines reznoise, klangexo and klanglin do not respond to engine.pan. The other engines seem to respond just fine, but I’m getting some strange stuck results with these. Reznoise seems to respond differently to each left and right field as far as frequency response to mod1, mod2 and hz2 go. I’m actually experiencing some weirdness across the stereo field in the klang engines as well.

I’m looking into it my self and trying to learn supercollider. Just wanted to let you know.

#22

Yep - those produce stereo signals in themselves nd I haven’t made the panning stage smart enough to really handle them

Only had a couple short sessions will the this so far, hence v0.0.x

If you want to try it, my idea would be: a conditional on the number of channels returned by the graph method, in Thebangs wrapper method

We can get away with a lot of silly stuff because arguments are only evaluated once at synthdef creation

If pan were modulated we’d need to be more careful

#23

Eager to try this out. Tonight I installed Pixels (which uses this engine) before installing thebangs itself. After rm -rf of pixels I restarted and now I just get ‘supercollider fail’. Any ideas what went wrong here?

EDIT: I just needed an actual SLEEP rather than a ;restart from Maiden, all is fine now.

#24

The Bangs is bundled into “pixels” itself when it is installed. No need to specifically install the engine itself. Just download “pixels” from the community and sleep the Norns.

Glad you got it rolling.

1 Like
#25

… despite some confusing advice i’ve seen floating around here, this is never recommended except during troubleshooting (to get early output from either the SC or matron component) or development (re-launching a single component to test a specific change.)

if you are trying to get to normal functionality and don’t want to use RESET for some reason, you must issue ;restart twice: first in the “SC” tab, then in the matron tab.

more typically, use SLEEP or SYSTEM > RESET from the norns menu to restart after installing new supercollider classes.

5 Likes
#26

What do I have to do have Thebangs/NewAwake and pixels both installed without getting duplicate engine error? Delete an engine?

#27

delete one, or rename this class and this engine name in pixels

(to something like Engine_Pixelbangs and engine.name = Pixelbangs respectively)

(the Engine_foo pattern is mandatory; the capitalization of foo to Foo is just a convention-so-far)

NB that Thebangs will undergo some breaking changes. support for versioning and dependency spec is a big gap in ecosystem still, so general apologies for that. on the bright side, the manual copy + mangle makes it impossible for my updates to break your script.

2 Likes
#28

Sorry @zebra! I misunderstood your directions a while back when you asked me to rename the class and not the file names. I’ll post an update soon to remedy the issue as described above. I had gone through and renamed the other classes in The Bangs, but not actually The Bangs itself. Uhg!

1 Like
#29

Very interesting! I haven’t looked into it yet, but could this be a way to have multi-timbral synths for norns? I’d been working on an engine a few months ago that would support 6-8 timbres (“voices”) but bumped into what I suspect are hardware limitations as far as number of synth instances and grouping of the “voices” into channels.

#30

i’m working on a voice allocator that supports multitimbral stuff

contributions welcome - this project is definitely giving me some pointers on how to better organize things

(also want to try out my own multi-algoritm nv based synth in the bangs style)

1 Like
#31

The bangs is working for me as a multi-timbral engine in my latest (unreleased) version of “pixels”. I haven’t run into any issues yet, changing the synth type per note on six different sequences.

#32

Cool! Polyphonic or mono sequences?

#33

In “pixels”, you control 6 pixels that move around the display. Each one represents a single mono synth. So … six mono sequences. You can select the MIDI channel on each as well.