@aaronventure I requested a proper bug tracker a couple of times, something like Mantis. It would prevent bugs being lost in the ether of the forum, or being lonely on github.

@Christoph-Hart Nice, going to give this a try now.

@clevername27 said in [feature request] Stop specific broadcasters firing at on init:
It's also not always possible to tell if a broadcaster is being called at startup…which doesn't sound right, but there are edge-cases.

Can you make an example?

@d-healey

Proposes the feature. Documents the feature. Codes the feature.

Because that's how @d-healey rolls.

@Chazrox Did you try itemColour1? You can use Console.print(trace(obj)) to see what's available.

Krita is open source and C++, the answer might be there somewhere, surely the colour picker logic could be tinkered with. Not that I would know

@ustk Wow seriously impressive work here! Excited to dig into this.

@d-healey This is the only mention of "linter" on the forum so far :D

I know nothing about how much effort implementing a linter would be, but even the low hanging fruit would save me a lot of development time. Yesterday I spent ages debugging a condition where I accidentally went if (var = 2) instead of if (var == 2).

I assume the ideal solution would be to adapt an existing linter, but maybe there's an easy way to do some basic checks until then?

Hence the feature request :-) fadeComponent has been working very well for me so far, it would just be great to have a quick and easy way to achieve fades to semi-transparent states like this.

@Oli-Ullmann thank - I already have a work around - what Im asking for is a post-init callback - as David did right at the start of this thread.

@Christoph-Hart not sure I follow

9cce4a7f-9ebc-44a8-be68-9835d0325fc3-image.png

I changed the range on the Value parameter to 0-0.1, it still outputs the raw value to minmax value.

Even so, it's still not dynamic.

I think it's just a missing node, what are the odds of using it in a signal path instead of using it to cable things around? Dynamic range adjustment, that's it? It's much more likely to be used in the context of pma, cabletable, inputToggle which are the workhorse nodes for value manipulation when creating modulators.

Overall there's a workaround, so it just depends on how much time this takes you to do. This is just a QoL request.

@Christoph-Hart found the culprit:

// if this is non-zero it means that the buffer coming // from the DAW was split into chunks for processing // so we need to update the playhead to reflect the // "real" position for the given buffer if(offsetWithinProcessBuffer != 0) { newTime.timeInSamples += offsetWithinProcessBuffer; newTime.timeInSeconds += (double)offsetWithinProcessBuffer / processingSampleRate; const auto numSamplesPerQuarter = (double)TempoSyncer::getTempoInSamples(newTime.bpm, processingSampleRate, 1.0f); newTime.ppqPosition += (double)offsetWithinProcessBuffer / numSamplesPerQuarter; }

@d-healey We really need some new samplespeak words for "legato" and "release" that don't have such ridiculously large overlap with other adjacent concepts.

I put forth "glithe" and "fradeaway" for your consideration.

As in

"Let's re-record that C# to D# glithe transition"

"When the user lets go of the key, we play a fradeaway sample"

"Denoising fradeaways is a massive pain"

"We spent five days recording 800 bespoke trombones playing three octaves of bespoke glithe samples"

I expect these will be a massive success, ambiguity when discussing samples will be eliminated, think of the time savings!

@CyberGen While we're at it, typing a string in the Component Browser could reveal components with that ID.