@DanH then, I will make vst available in an independent application by bringing it to the daw constructor, as soon as I learn c++
Latest posts made by Maarid Ekimmu
-
RE: creating a multiband gui
-
RE: creating a multiband gui
@DanH of course, ignore, just like you do. understand?
It's a pity all this tripe does not solve the question of why there is no glitch on C++ Juce, but there is on Scriptnode, lasers, piu, piu, piu
-
RE: creating a multiband gui
@Lindon said in creating a multiband gui:
If so please feel free to ignore me, and pursue your solution elsewhere.
Do I understand correctly that the lack of response initiates trolling? Otherwise, why should I ignore anyone when they are diligently trying to help me?
I sincerely assure you, we can kindly exchange subtleties and barbs for any length of time, moreover, I will be sincerely glad to do so.
You're not trying to turn the topic of conversation offtop by ignoring common sense, I hope? -
RE: creating a multiband gui
@Lindon and?
I can't make any obvious sense out of your idiomatic sarcasm.Maybe you can point a finger at a silly boy, where is the compensation for the volume surge, which is missing in this plugin?
#include "CrossoverProcessors.hpp" namespace { void processBand(BandState& band, juce::AudioBuffer<float>& buffer) { if (band.isMuted) { buffer.clear(); } else { float* leftSamples {buffer.getWritePointer(0)}; float* rightSamples {buffer.getWritePointer(1)}; // Do the processing if (!band.isBypassed) { for (size_t index {0}; index < buffer.getNumSamples(); index++) { const double mid {(leftSamples[index] + rightSamples[index]) * 0.5}; const double side {(rightSamples[index] - leftSamples[index]) * (band.width / 2)}; leftSamples[index] = mid - side; rightSamples[index] = mid + side; } } // Update the envelope for (size_t index {0}; index < buffer.getNumSamples(); index++) { band.env.getNextOutput(leftSamples[index] - rightSamples[index]); } } } } namespace CrossoverProcessors { void prepareToPlay(CrossoverState& state, double sampleRate, int samplesPerBlock) { // We don't filter sidechain channels but do copy them to each buffer - so filters may need less channels than the buffers do for (juce::dsp::LinkwitzRileyFilter<float>& filter : state.lowpassFilters) { filter.prepare({sampleRate, static_cast<juce::uint32>(samplesPerBlock), static_cast<juce::uint32>(2)}); } for (juce::dsp::LinkwitzRileyFilter<float>& filter : state.highpassFilters) { filter.prepare({sampleRate, static_cast<juce::uint32>(samplesPerBlock), static_cast<juce::uint32>(2)}); } for (juce::dsp::LinkwitzRileyFilter<float>& filter : state.allpassFilters) { filter.prepare({sampleRate, static_cast<juce::uint32>(samplesPerBlock), static_cast<juce::uint32>(2)}); } for (juce::AudioBuffer<float>& buffer : state.buffers) { buffer.setSize(2, samplesPerBlock); } for (BandState& band : state.bands) { band.env.setSampleRate(sampleRate); } state.sampleRate = sampleRate; state.samplesPerBlock = samplesPerBlock; } void reset(CrossoverState& state) { for (juce::dsp::LinkwitzRileyFilter<float>& filter : state.lowpassFilters) { filter.reset(); } for (juce::dsp::LinkwitzRileyFilter<float>& filter : state.highpassFilters) { filter.reset(); } for (juce::dsp::LinkwitzRileyFilter<float>& filter : state.allpassFilters) { filter.reset(); } for (juce::AudioBuffer<float>& buffer : state.buffers) { buffer.clear(); } for (BandState& band : state.bands) { band.env.reset(); } } void processBlock(CrossoverState& state, juce::AudioBuffer<float>& buffer) { const size_t numCrossovers {state.bands.size() - 1}; // First split everything into bands and apply the processing for (int crossoverNumber {0}; crossoverNumber < numCrossovers; crossoverNumber++) { // We need to make a copy of the input buffer before processing // lowBuffer will be lowpassed, highBuffer will be highpassed juce::AudioBuffer<float>& lowBuffer = crossoverNumber == 0 ? buffer : state.buffers[crossoverNumber - 1]; juce::AudioBuffer<float>& highBuffer = state.buffers[crossoverNumber]; highBuffer.makeCopyOf(lowBuffer); { juce::dsp::AudioBlock<float> block(juce::dsp::AudioBlock<float>(lowBuffer).getSubsetChannelBlock(0, 2)); juce::dsp::ProcessContextReplacing context(block); state.lowpassFilters[crossoverNumber].process(context); // Crop the internal buffer in case the DAW has provided a buffer smaller than the specified block size in prepareToPlay juce::AudioBuffer<float> lowBufferCropped(lowBuffer.getArrayOfWritePointers(), lowBuffer.getNumChannels(), buffer.getNumSamples()); processBand(state.bands[crossoverNumber], lowBufferCropped); } { juce::dsp::AudioBlock<float> block(juce::dsp::AudioBlock<float>(highBuffer).getSubsetChannelBlock(0, 2)); juce::dsp::ProcessContextReplacing context(block); state.highpassFilters[crossoverNumber].process(context); // If this is the last band we need to apply the processing if (crossoverNumber + 1 == numCrossovers) { // Crop the internal buffer in case the DAW has provided a buffer smaller than the specified block size in prepareToPlay juce::AudioBuffer<float> highBufferCropped(highBuffer.getArrayOfWritePointers(), highBuffer.getNumChannels(), buffer.getNumSamples()); processBand(state.bands[crossoverNumber + 1], highBufferCropped); } } } // Finally add the bands back together if (state.numBandsSoloed > 0 && !state.bands[0].isSoloed) { buffer.clear(); } for (int crossoverNumber {0}; crossoverNumber < numCrossovers; crossoverNumber++) { // If there is another crossover after this one, we need to use an allpass to rotate the phase of the lower bands if (crossoverNumber + 1 < numCrossovers) { juce::dsp::AudioBlock<float> block(juce::dsp::AudioBlock<float>(buffer).getSubsetChannelBlock(0, 2)); juce::dsp::ProcessContextReplacing context(block); state.allpassFilters[crossoverNumber].process(context); } if (state.numBandsSoloed == 0 || state.bands[crossoverNumber + 1].isSoloed) { for (int channelNumber {0}; channelNumber < 2; channelNumber++) { buffer.addFrom(channelNumber, 0, state.buffers[crossoverNumber], channelNumber, 0, buffer.getNumSamples()); } } } } }
-
RE: creating a multiband gui
the link to the source of the Monster plugin is above, the name of the plugin is clickable, you can make sure it works and not find a formula for compensating the edge of each selected channel, although maybe we are blind and you will succeed?
We also read about Linkwitz Riley, watched the Juce forums, well, it works for an open source person, without problems, miraclesadded
the only thing that comes to my mind is to contact the developer directly, explain this situation and ask for the formula, if it exists. It will be very funny if he answers the same way the programmer answered me - there is no formula, there is nothing to compensate -
RE: creating a multiband gui
@Straticah said
Hi, I'm offended to remind you, in the hope that Christophe will look this way. The multiband filter is broken in Hise, I could not understand the reason, I will try to consult other programmers working with Juce.
When two segments approach each other, a parasitic burst of the signal appears. This is exactly why Christophe hung a divider on each band of the signal in his examples. Which, as it is not difficult to understand, is effective only in the static position of the segments. Trying to make them manageable, you inevitably get a parasitic spike at the output, the distance of information is unacceptable - depending on the frequency, the higher, the correspondingly greater the distance you need to block.@Christoph-Hart My friend and I recently tried to disassemble the Monster plugin trying to determine the presence of an exponential formula by which the channel could be muted, neither I nor a familiar C++ programmer found it, unfortunately. I will try to contact jd13 directly, it is surprisingly quite responsive, perhaps it will tell you why LinkwitzRaily in C++ does not give a parasitic splash, but in the script it does. Which is very strange in itself.
-
RE: Two filters in a row, how to compensate for the signal
no one is interested in my opinion, but I will add.
The doctor plugin restricts hise, neither the creation nor the loading of script fx work.
Thank God, there is BERTOM AUDIO EQ Curve Analyzer, which allows you to freely test the linear-phase result during the assembly process.
Interestingly, logically, if you embed signal tests as modules into the hise itself, you will get a lego constructor with a professional bias? -
RE: Two filters in a row, how to compensate for the signal
@Christoph-Hart A giant thank you, it worked, although it was confusing that the main signal meter did not show signs of a working state, but as soon as I opened the effects tab, everything fell into place. What would we do without you?
I understand that you can simply specify this in the hi_core module settings by deleting the line from the preprocessor
JucePlugin_PreferredChannelConfigurations={0,2}?
Thank you @d-healey
And enabling the "DON'T CREATE FOLDER" parameters in the same place will disable the creation of folders in the user's profile, making the plugin offline and without presets, right? -
RE: Two filters in a row, how to compensate for the signal
@Christoph-Hart I don't really hope for an answer, but what if you take pity?
Christoph, can you tell me where to fix or what to add in the source code of hise so that the assembled plugin passes sound through itself? I set up channels and studio as an effect in projucer, but hise remains immune to sound.
It would just make it possible to test the build of the project directly in the plugin doctor, saving me from guessing and re-building -
RE: Two filters in a row, how to compensate for the signal
Guys, I compiled only the template, it's better, but with a heavy load on the editor, there is still almost no compensation.
I have definitely met examples of separation in linear-phase mode written in juce, I wish I could in c++, in hise it is impossible to divide linearly-phase? Or is there some other secret that I can't find as a blind man?