Search found 9632 matches

by seb@plogue
Wed Feb 21, 2018 10:02 am
Forum: Bidule Bugs and Problems
Topic: Feedback Routing Issue
Replies: 7
Views: 137

Re: Feedback Routing Issue

Is there some under the hood technical tweak to avoid that?


You might want to try wrapping the feedback part of your layout in a group and set it to use the 1-sample dsp adapter. That will let you have a 1-sample buffer for that part. That will come with added cpu usage of course.
by seb@plogue
Tue Feb 20, 2018 11:52 am
Forum: Bidule SDK
Topic: idle() for parameter updates
Replies: 1
Views: 24

Re: idle() for parameter updates

in offline mode, idle will most likely occur less often (that's going with the there's-no-sampling-rate-just-process-as-much-as-the-core/cpu-can). Is there a way to update parameters without updating the GUI (parameter linking gets updated in process() but GUI updates during idle()? Internally, it w...
by seb@plogue
Tue Feb 20, 2018 11:42 am
Forum: Bidule SDK
Topic: Note keeper for PrCh
Replies: 10
Views: 205

Re: Note keeper for PrCh

But, if I use midiOut[i].numEvents = midiIn[i].numEvents; , how is possible to add additional events inside j-loop? for it I need to change j inside loop for additional event? It would probably be better to have another variable initialized at 0 before the j-loop and you would use that inside the l...
by seb@plogue
Fri Feb 16, 2018 10:02 am
Forum: Bidule SDK
Topic: process
Replies: 1
Views: 56

Re: process

process() is called once per buffer, regardless of what type of signal is being processed?


Yes, for spectral data you have to do a for loop on fftOverlapPerBuffer in your process method to cover
all possible values of sample rate+buffer size+fft size+fft overlap.
by seb@plogue
Fri Feb 16, 2018 10:01 am
Forum: Bidule SDK
Topic: Note keeper for PrCh
Replies: 10
Views: 205

Re: Note keeper for PrCh

But how to separate Bufftick of PrCh from NoteOff? If I write Bufftick+1 I have unfinity loop again.. You're referring to midiIn[i].events[j] as the source of the bufTick which might be 0 or be events[1] from the previous process call. The easiest way would be to use the one from the note off and a...
by seb@plogue
Fri Feb 16, 2018 9:48 am
Forum: Bidule Feature Requests
Topic: Spectral Delay
Replies: 5
Views: 97

Re: Spectral Delay

Yes I see the Bin Delay, but a pain to make 4096 parameter links (or draw a ruler straight line in the GUI) to set all bins to equal delay.


You know you can use shift in the target part of the Parameters window to link 1 parameter to 4095 parameters in one click, right?
by seb@plogue
Fri Feb 16, 2018 9:44 am
Forum: Bidule Bugs and Problems
Topic: Poly adapter loses parameter links
Replies: 13
Views: 819

Re: Poly adapter loses parameter links

just noticed all the parameter modulators now get set to Bypass when unPolyphonisising (don't look it up) a group is this expected behaviour or something else? All the terminal bidules inside a "voice" group (i.e. what you use to polyphonize) are set to not process when a a voice is not r...
by seb@plogue
Wed Feb 14, 2018 11:01 am
Forum: Bidule Bugs and Problems
Topic: Mysterious Bidule Crash - Live Usage
Replies: 6
Views: 98

Re: Mysterious Bidule Crash - Live Usage

So here is the little maths I'm doing and it's working perfectly but maybe it's what causes the problem? One thing I've seen before from VSTs is having the UI control for one of its parameters actually doing some value limitation/protection but through the host interface it was possible to cover th...
by seb@plogue
Wed Feb 14, 2018 9:47 am
Forum: Bidule Bugs and Problems
Topic: Mysterious Bidule Crash - Live Usage
Replies: 6
Views: 98

Re: Mysterious Bidule Crash - Live Usage

All 3 crash logs are crashes occurring inside the processing code of Tube-Tech PE 1C VST.

Were you changing parameters for that VST? (simply trying to help pinpoint the cause)
by seb@plogue
Mon Feb 12, 2018 10:11 am
Forum: Bidule SDK
Topic: Note keeper for PrCh
Replies: 10
Views: 205

Re: Note keeper for PrCh

midiOut[i].numEvents = midiIn[i].numEvents + 1 will make it so that for every buffer there will be at least 1 MIDI event on the output, since you write at j+1 this means that when there's 0 in midiIn you will write at [1]. This means that the code in Bidule reading/processing what's coming back from...
by seb@plogue
Thu Feb 08, 2018 10:28 am
Forum: Bidule Bugs and Problems
Topic: HID Data Extractor substitutes other devices if device not present
Replies: 7
Views: 163

Re: HID Data Extractor substitutes other devices if device not present

hey seb, thanks for your reply, though i'm unclear. would you mind elaborating as to whether or not there's anything i can do on my end to confirm which HID is selected upon load? Right now, besides keeping the devices plugged in I'm not sure there's much. There is some extra code inside the HID Da...
by seb@plogue
Wed Feb 07, 2018 9:21 am
Forum: Bidule Bugs and Problems
Topic: Bidule problem with RME FF400
Replies: 5
Views: 124

Re: Bidule problem with RME FF400

Great! If it's easier for your setup/the way you work (especially if you use different apps for different projects), you could turn on the Always use device current sample rate option that is in the DSP tab of Bidule preferences. This way Bidule will simply use the sample rate from the FireFace when...
by seb@plogue
Tue Feb 06, 2018 11:54 am
Forum: Bidule Bugs and Problems
Topic: Bidule crashes LogicX on OSX Sierra - Solved!!
Replies: 4
Views: 110

Re: Bidule crashes LogicX on OSX Sierra

From my username here you can guess my address or you can send to contact.
by seb@plogue
Tue Feb 06, 2018 11:41 am
Forum: Bidule Bugs and Problems
Topic: Bidule crashes LogicX on OSX Sierra - Solved!!
Replies: 4
Views: 110

Re: Bidule crashes LogicX on OSX Sierra

You can send the crash logs by e-mail if you prefer.
by seb@plogue
Tue Feb 06, 2018 10:36 am
Forum: Bidule Bugs and Problems
Topic: Feedback Routing Issue
Replies: 7
Views: 137

Re: Feedback Routing Issue

Tried a couple of times and nothing was changing when connecting gain_3 to gain_1, using Monitor I could see that nothing was coming out of gain_3 when the gain level is at -oo.

Have you checked through the Monitor context menu entry if there was anything coming out of gain_3 ?

Go to advanced search