@bendurso Bump. I think this could be a Feature Request, right?

@Christoph-Hart By default macOS is not, but it's one of the formatting options to enable that. Sometimes Apple gives us the strangest choices, while making other decisions for us, lol.

@jeffd

ok, im so dumb. I had the send container going back into channels 1 and 2 of container 1 and feedbacking on itself. So i added 2 other channels to container 1.

it works now!!

thanks @clevername27 !

@Menzenhofer Depending on your implementation, perhaps you could…

…change the meaning of parameters depending on context.
…combine parameters in JSON objects.
…use OSC or MIDI to communicate with Max.
…shift some of the processing to MAX, so there's less to communicate.

@Lindon @Frankbeat @ustk I realize that embedding the samples isn't useful for most cases. I'm only throwing my hat into the ring here because in my case, it is. 🌈

I'm building prototypes to demonstrate things, not creating products for distribution. And in that case, nobody wants to get involved with downloading samples, remembering where they are, remembering to delete them when they're done, etc. They only run the plugin once—and that one time, it simply needs to "work."

Anyway, if anyone has any motion on this, I'd truly appreciate it.

@pgaudioworksI've amended my suggestion. Yes, you can do this by copying the sample in question to buffer, then writing that buffer to disk as a temporary audio file, and then enabling dragging in a panel. So you have like a button that a user pushes when the user wants to drag a specific sample into the DAW. The DAW should offer the option of copying the file into the DAW project's audio folder, and then you can keep writing to the same temporary file.

@d-healey Good point! Of course, that doesn’t negate the fact that it has multiple known vulns already.

@Mighty23 said in Goniometer and glitches, Windows 10:

@Lindon, plugin doesn't have graphical glitches in JUCE's Audio Plugin Host or in a DAW (Windows 10, Presonus Studio One). Should I just ignore the graphical glitches and proceed?

..unless you can think of something else to do.....

@Dan-Korneff actually it will create a problem for Maize Sampler and Romplur as they are JUCE based and produce binaries. HISE is fine because anyone who sells proprietary HISE plugins needs a JUCE license anyway, so from a legal standpoint HISE is just a glorified build script here.

But I'm almost 100% positive that they will backroll the announcement to some degrees, too bad they don't have a Unity CEO they can fire for this...

@d-healey Oops I overread that it was about compiling the DSP networks. Back to bashing the docs then I guess :)

On the other hand you might get away without compiling the networks in the build process - when it loads a project and can't find the project DLL (like it would in the command line build process of the actual plugin), it will still create a placeholder and then export it correctly (assuming that you've checked in the C++ node for the codes in the AdditionalSourceCode repository).

@djalexx1 Thank you for your availability. Enjoy your vacation at your own pace; upon your return, my email will be waiting for you. Thanks again for your availability.

I finally succeeded, thank you for your help.

@d-healey & @Lindon Thank you very much, both of your responses have really helped me explore the possibilities here. I am pleased to know I can use the text property in this way, and will definitley explore this more in future projects. A lot of this particularly UI is already laid out so I am settling for bypassing any text that is not the exception cases, and employing it for any cases that call for customized value displays.

Example based on Lindon's edits:

const tempos = ["1/1", "1/2D", "1/2", "1/2T", "1/4D", "1/4", "1/4T", "1/8D", "1/8", "1/8T", "1/16D", "1/16", "1/16T", "1/32D", "1/32", "1/32T", "1/64D", "1/64", "1/64T"]; const filterModeLabels = ["Lowpass", "Highpass", "Bandpass"]; const LAF_StandardKnob = Content.createLocalLookAndFeel(); LAF_StandardKnob.registerFunction("drawRotarySlider", function(Style,Widget) //... if (Widget.text.contains("FilterType")) { // For FilterType knob, display the corresponding label displayLabel = filterModeLabels[parseInt(Widget.value)]; //For TempoSync, display tempo sync values }else if (Widget.text.contains("TempoSync")){ displayLabel = tempos[parseInt(Widget.value)]; } else { // For all other knobs, display the value displayLabel = Engine.doubleToString(KnobValue, 2) + Widget.suffix; } Style.drawAlignedText(displayLabel, [Area[STARTX] + LabelOffset, Area[HEIGHT]-Area [HEIGHT] +6, Area [HEIGHT]+LabelOffset, Area[HEIGHT]], "left"); //...

@d-healey Honestly, Now I can't remember why I made that choice. 😕

Thank you for reminding me that option existed. I'll make the change.

@d-healey said in Filter Freq popping on CC Control:

@Lindon Try using a CC mod and connecting the knob to that and see if the issues goes away, if it does then it is almost certainly a lack of smoothing that's the problem - although I would have expected it to work the way you have it...

Well -- I asked him to try changing the audio card buffer size - as that's a classic pops and clicks source, and it fixed it.. so I will save the "add a global MIDI modulator or two.." for another day I think.. thanks tho. it prompted me to go back to think about adding these again - at the same time I will a dd the new global envelope modulators too, so the user gets user-drawn tables...