Create a project like in this photo

One LFO is x Hz, the second is 2x Hz. x must be odd number. Use trigger button to reset both LFO’s phases and watch the oscilloscopes. After a while, they stop being synced as if one is 2 times speed of the other.

BUT if x is even number, they work as expected.

It’s not a visual bug of oscilloscopes, because I discovered it when making a synth and using the LFO’s for filter cutoff and after a while it became audibly unsynced.

I always typed in the exact value of Hz, didn’t use faders to set the value.

I love Drambo. It is the sequencing brain and mixer for my modular. I'm currently building a live set.

I tend to keep my projects running lean, hovering around the 2-3bars of DSP usage <50%, which allows enough headroom for occasional CPU spikes.

Everything was going fine until about one week ago, after I purchased the Visualisation suite (which is amazing btw - great job!).

I now find that if I change the Drambo GUI elements - for example move the clip pane or rename a clip lane when the sequencer is running - the CPU jumps significantly and often chokes, causing a loud zipper noise.

I can 'force' these cpu spikes by re-sizing the clip panel up and down in quick succession. Obviously I won't do this normally, but it might be a pointer to the problem. Perhaps someone else can replicate this?

Now, I am not saying that the Visual suite is the culprit, but I am trying to rule it out as I have stress-tested the AUv3s I am using and they all appears to be OK, cpu-wise.

I am not actually using any visualisation modules in my projects yet, it is just installed.

Is there a way to temporarily uninstall the visual suite so I can test?

Can anyone provide suggestions on how I can test this further and are there any logs I can access and provide, etc.? I am happy to provide clarifications as needed.

I am using a M1 ipad pro 5th Gen. OS version 18.3.

Thanks in advance for any help!

J

Does anyone else get this problem with external sound cards? I really love Drambo and I don’t want to ditch my RME… I think it’s a drambo issue because Cubasis seems to work first time.

Not sure if it's an error on my side, a bug in Drambo or by design.

The MIDI mapping is just not reacting to CC64. I am aware that this is the CC for the sustain pedal but do think that this should not be an issue as Drambos mapping system maps not only CC and Channel but the source device as well.

https://forum.beepstreet.com/discussion/3739/transport-module

The problem is that ADDING the transport module to the patch causes instabilities (MIDI crash when starting transport). If I save the patch, restart Drambo and load the patch with the Transport module again all works fine.

I reported this already in October ‘24, so I suspect a regression bug.

I’ve tested this with both a midi keyboard and with setting the MIDI channel of the notes I’m sending to Koala.

I want to use different channel numbers to use the Pads of my controller sometimes to trigger samples and sometimes as controller info for Drambo overall.

Koala seems to work as expected inside AUM.

Steps to reproduce:

1. Open new project
2. Load the Sequencer module on whichever track you want.
3. Open a new projects (Settings > New > [select whichever template you want]).
4. Observe how Drambo crashes.

Tested on iPhone 11 running iOS 18.7.1 (22H31) and Drambo v2.52(6)

See linked video.

Steps to reproduce:

1. Open new project.
2. Insert the following notes into the sequencer: C2, E2, G2, C3. Insert first note on beat 1, second note on beat 2. etc. Make them all 1 beat long.
3. Insert the Sequencer module (MIDI).
4. Tap the empty clip in the Sequencer module so it becomes active (a red border appears around it).
5. Tap the Record button in Drambo’s transport.
6. Tap the Play button.
7. Wait for the clip to record all incoming notes and then tap the Record button and then the Play button.
8. Swipe down on the clip in the Seqence navigation bar (not the Sequencer module) to clear it.
9. Repeat steps 5 to 8 at least three more times. Each time before clearing the clip (step 8) observe the length of the notes. In the third recording pass the lowest note should get slightly longer, while on the fourth pass it should span the entire length of the clip. Since the underlying sequence, which gets recorded into the Sequencer module, remains unchanged the entire time, this shouldn’t be happening.

Tested on:

• iPad 5th gen. running iPadOS 16.7.11 (20H360) and Drambo v2.51(3)
• iPhone 11 running iOS 18.7.1 (22H31) and Drambo v2.51(2)

Steps to reproduce:

1. Open new project.
2. On any track insert a note (or a chord) into the step sequencer by tapping on a step.
3. Open the piano roll.
4. Activate the Select/Operation button.
5. Select your note(s).
6. Press the Clear/Undo button. The selection will clear but the notes stay.
7. Select your note(s) again.
8. Press the Clear/Undo button again. The notes will disappear from the piano roll but they will still be visible in the Step sequencer, the Multitrack Step Sequencer editor and the Extended step sequencer editor. This should not happen. I expect one of the following options to happen:
   1. The selection should once more clear and the notes stay or
   2. the notes would disappear when the Clear/Undo button was pressed the first time.
9. Additional observations (not shown in the linked video): If a MIDI monitor module is placed into the track afterward and you press play, it detects the notes. If an instrument rack or an AU instrument is placed into the track and connected the instrument apparently doesn't receive the MIDI data since no sound is produced.

See the video.

There's more bugs I encountered while in the piano roll but I'm still trying to find steps to reproduce them consistently.

Please fix this. Thank you.

Edit: Tested on:

• iPad 5th gen. running iPadOS 16.7.11 (20H360) and Drambo v2.51(3)
• iPhone 11 running iOS 18.7.1 (22H31) and Drambo v2.51(2)

Please see linked videos below for examples:

Drambo inside Drambo (inception style):

Drambo inside AUM:

Drambo inside BM3:

Steps to reproduce:

1. Open Drambo as an AUv3 instance inside any host (I tried only the 3 mentioned above but I presume the effect will be the same elsewhere unless the issue lies with the hosts).
2. Load some MIDI editor or the host's piano roll or sequencer (if it has one) and write the following notes (could be others but I usually use these for the tests) on each beat inside one measure: C2 on beat 1, E2 on beat 2, G2 on beat 3 and C3 on beat 4. Also make all of them one beat long so you'll see the effect of the issue in the piano roll.
3. Connect the Drambo AUv3 instance to the source of MIDI from step 2.
4. Inside Drambo, press the Record button.
5. Inside the host, make sure the playhead is at the beginning of the project (inside AUM and BM3, you'll have to press stop).
6. Press play inside the host and wait for the measure to play through.
7. Stop playback.
8. Go to the hosted Drambo instance and tap the Record button again (probably not essential).
9. Open the piano roll and observe the positions and lengths of the notes. In theory they should all be the same as in the source. In practice they're either off (early) or missing.

Tested on iPad 5th gen. running iPadOS 16.7.11 (20H360) and Drambo v2.52(6)

• There is no visual feedback when tapping on the items in the window. I can only see the 1px wide white lines flashing dark when tapping on something like Cut, Paste or Clear all mappings. Maybe dark mode is not handled properly.
• Clear all mappings should ask for an additional confirmation. Specially as hardware mappings are saved immediately on change.
• The mappings shown on the screen do not update until the modified profile is loaded again. This might be intentional but I find it confusing.

What could be the problem?

See linked video.

Steps to reproduce:

1. Open new project.
2. In the sequencer, insert a chord into step 5 (C major for example)
3. Open the piano roll.
4. Set quantization to ‘Free’ (effectively disabling quantization).
5. Move the lowest note slightly ahead of the beat.
6. Close piano roll.
7. Press play and wait for the clip to play through once, then stop playback.
8. Open the piano roll again.
9. Tap the Select/Operation button.
10. Select all notes in the chord.
11. Drag the selection slightly to the left.
12. Observe how the lowest note snaps one 16th note to the left, while the other two don’t.

Expected behaviour: Since quantization is disabled, there should be no snapping happening.

This happened multiple times in the last week while making music but I struggled to reproduce it reliably until today.

Tested on:

• iPad 5th gen. running iPadOS 16.7.11 (20H360) and Drambo v2.51(3)
• iPhone 11 running iOS 18.7.1 (22H31) and Drambo v2.51(2)

See also this thread: https://forum.beepstreet.com/discussion/3632/flexi-sampler-bug#latest. @giku you we're tagged there more than a month ago and didn't even respond yet. Not cool.

1. bug: Flexi Sampler triggers itself while it's recording.

Steps to reproduce:

1. Open new project.
2. Insert an instrument rack on a track and activate any preset.
3. Add the Flexi sampler module after the instrument rack.
4. Press Flexi sampler's 'Monitor' button to hear yourself playing.
5. Press the REC button and immediately play a few notes (at least 2 to 3 notes) on the pads or the keys.
6. Observe how the playhead in Flexi sampler's waveform view triggers (starts playing) each time you played a pad or key.
7. Observe how after you've already stopped playing, the sampler will trigger and play something again (the audio it's still recording).
8. Now disconnect the gate input on Flexi sampler and repeat steps 5 & 6.
9. Observe how it doesn't get triggered now (desired behaviour).

Having to disconnect the gate to record something in Flexi sampler while monitoring the signal is unintuitive and unnecessary. I don't see how this triggering during recording is useful anywhere. It would be best if the gate input was disabled during recording otherwise the Monitor option becomes kind of useless when recording MIDI instruments (I see how this wouldn't happen when recording external audio since you're not sending any MIDI into the track which triggers the sampler).

Bugs / uninteded behaviours of 'Clip' Sync recording mode:

Preliminary steps (for all bugs / unintuitive behaviours described below):

1. Open new project.
2. Insert an instrument rack on a track and activate any preset.
3. Add the Flexi sampler module after the instrument rack
4. Press the 'v Rec' button in Flexi sampler's module header.
5. Change Sync mode to 'Clip'.
6. Press Flexi sampler's 'Monitor' button to hear yourself playing.

1. bug / unintuitive behaviour: If you first press the 'REC' button in Flexi sampler and then press the Play button, Flexi sampler's recording starts only after the clip played through 1 or 2 times (depending on the buffer size -> that's definitely a bug). It should record immediately when you press the Play button because we can already have it record later by pressing the REC button while the clip is already playing. Sometimes you don't want to wait the length of the entire clip (or multiple clips - see 2nd scenario) for it to start recording but you want it synced to the length of the clip - imagine a clip that is 8 or 16 bars long ... it's just wasting time.

1st Scenario: recording starts after the clip has played through 1 time:

Steps to reproduce:

1. Don't add any bars to the clip. Leave the clip 1 bar long.
2. Set buffer size to and of the following: 128, 256 or 1024.
3. Press the 'REC' button in Flexi sampler.
4. Press the Play button.
5. Press the pads or keys to play the instrument you picked.
6. Observe how the sampler doesn't start recording only until the clip has played through once already.

2nd Scenario (100 % a bug):

Steps to reproduce:

1. Don't add any bars to the clip. Leave the clip 1 bar long.
2. Set buffer size to 512.
3. Follow steps 2 - 4 from the 1st scenario.
4. Observe how the sampler doesn't start recording only until the clip has played through TWICE.
5. Ask yourself: What the hell is going on? Why should this particular buffer size have any effect on when recording starts?

3rd scenario:

Steps to reproduce:

1. This time make the clip 2 bars long.
2. Set buffer size to 512.
3. Follow steps 2 - 4 from the 1st scenario.
4. Observe how the sampler starts recording after the clip (2 bars) has played through once. That is more in line with the behaviour at buffer sizes 128, 256 and 1024 but it still isn't intuitive.

Continued in next post ...

Also notice that the takeover mode is also producing the same behavior when doing p-locks.

it works until you switch tracks to another and back, then the arrows wont respond anymore. I have to remove the condition to get it working again. Anyone else can confirm this?

Say I set up my controller for midi feedback and then I select a step to change. This works perfectly with playback stopped but if playback is going the feedback makes my parameter jump with each step that plays because feedback is being sent from each step. But while that step is selected all other steps should stop sending their feedback until the step is no longer selected. Thats the way it works when you’re using Drambo standalone with no controller; if you select a step the parameter you see on the screen stays whatever it is set for that step until you stop selecting the step. Basically it boils down to when a step is selected I only want midi feedback for that step. All other steps should stop sending feedback until the step is unselected.

Sometimes it's really hard to select a single module by clicking and holding on it's header when it is placed within a rack. Instead, all modules in the rack are being highlighted in green, which makes it kind of tricky to copy, cut or paste modules.

It happens pretty randomly, so it might work with some of the modules in the rack, while others are impossible to select. Also, sometimes it seems to work better right after having restarted the app, but after a while the behavior returns.

I've had this problem both in the Ipad and Mac version of Drambo, but it happens most frequently on the Mac.

@giku, have you had other reports of this issue and do you think it can be fixed?

is it a bug? Am I the only one? It is a pity because the madrid gadget is almost always my bass of choice.

thanks!

I am really enjoying Drambo and it is inspiring. However, I found a bug regarding setting any time signature with a divider other then /4. So with 6/8, I found that the MIDI note end is delayed, the note releases later then it should, the cursor is way past the end, in the piano roll, when it finally releases. This is highlighted with long notes, longer than a bar. If I set it back to 4/4, it works perfectly. Also, in 6/8, the cursor line of the effect automation is completely out of sync with what is happening in steps, the cursor is faster than the step sequencer, and goes out of bounds. If the end of the note is close to the end of the clip, it never releases.

Everything can be reproduced by opening an empty project and setting the pattern time signature to 6/8,I used 3 steps per beat, the issue shows without any instruments, just record a midi note longer than a bar, and add effect automation.

If i use 16steps it disables the next 16 correctly.

Although if i want to duplicate the 16 steps by holding midi mapped Select button, it will enable steps 17-32 then will be duplicated. So this way i get 16 steps sequenced beats then a blank 16, the copied 16 and an other blank 16 steps et the end.