If a repeater is placed before a delay (setup as a looper), would you expect the Result of the repeater to be looped in the delay or would you expect the input of the repeater to be looped in the delay.? Because the latter is what appears to be happening.

Both issues are fixed: [Download] Midihub Firmware 1.11.7 :slight_smile:

Good catch, the produced repeated notes should end up within the delay loop. :slight_smile: We’ll look into this.

I just spent 2 hours in trying to find the error in my setup until I realized that this could be a firmware issue :slight_smile: . If dry/wet is set to 100% the looper does not record anything. Observed with firmware 1.11.6 I would expect the input of the delay to be looped, not the output.

Yes, looks like the incorrect velocity values of inputted notes were being used when dry/wet parameter is set to >50%. Both of these issues will be fixed in the next update :slight_smile:

That’s excellent to hear, thanks :slight_smile: I had built a number of patches hoping to use 100% wet delays to create a series of time based generative effects on different midi channels, and this had proven impossible with the last firmware. I shall update tomorrow.

Repeater>>>>delay

Midihub Support

Giedrius August 19, 2020, 12:08pm 5

Both issues are fixed: [Download] Midihub Firmware 1.11.7

Topic		Replies	Views
Using midihub as a midi looper- observations Midihub	1	918	July 3, 2020
Delay pipe not working Support	13	506	January 16, 2023
Delay Looper Drop Outs Support	2	162	December 5, 2023
Setting up a LOOPER from scratch Support	15	804	February 13, 2023
[Download] Midihub Firmware 1.11.7 Releases	25	3911	November 26, 2020
Delay pipe 100% wet Support	5	391	April 19, 2022
[Download] Midihub 1.7.0 Update Releases	3	859	August 15, 2019
[Download] Midihub Editor 1.11.3 & Firmware 1.11.5 Releases	12	1657	August 1, 2020
Delay not respecting note length correctly Support	5	113	May 19, 2025
[Download] Midihub Firmware 1.11.4 Releases	2	2031	July 4, 2020

Repeater>>>>delay

Related topics