MIDI sequencer module recording bug
in Known issues
See linked video.
Steps to reproduce:
- Open new project.
- 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.
- Insert the Sequencer module (MIDI).
- Tap the empty clip in the Sequencer module so it becomes active (a red border appears around it).
- Tap the Record button in Drambo’s transport.
- Tap the Play button.
- Wait for the clip to record all incoming notes and then tap the Record button and then the Play button.
- Swipe down on the clip in the Seqence navigation bar (not the Sequencer module) to clear it.
- 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)
Comments
Got it! Thank you!
This bug is still present in v2.52(6). Is there a particular reason why it wasn't considered?
It's still in the queue, I try to set reasonable priorities. I will work on it, probably next week.
The reason? One developer and 400K lines of code :)
(as a counter example: Apple has 166K employees and I still wait for some 2 years old bugs to be fixed)
Anyway, I'm sorry
Thank you for the reply and for considering it. I understand the fact that you're alone in this and I don't mean to belittle your work. Drambo is amazing. Period. You're an amazing developer. Period.
That said I don't understand these priorities. I am not a developer and I'm viewing this from a user's perspective. When I want to use software seriously I expect it to be reliable. For me, Drambo is currently unreliable and there are others who seem to agree with that. I understand the fact that bugs are inevitable but if a user gets tripped up by bugs in their work too often, it gets annoying or even frustrating (occasionally infuriating). That is my experience with Drambo at least 50 % of the time. I start a song or want to explore some concepts and whoops ... something doesn't work or some progress gets deleted because something bugged out etc. (as in the piano roll bugs examples) All of a sudden I have to think whether this is intended behaviour or have to find workarounds or always be mindful that I don't trigger the bug in any project I work on.
From the provided steps to reproduce the bug one might think at first glance that nobody does that in a project. I hope you're not judging the severity of bugs based on that. Of course I don't use those steps in a project. I encountered all of these bugs in real projects and then tried to find some minimal steps.
So, the question is: What is more important to you than making the product stable and reliable? This is me speaking strictly Drambo-related of course. Are you prioritizing new features to entice more users to try Drambo? Are you prioritizing concepts which excite you so you don't get bored and tired of polishing the product? Are you approaching the whole thing leisurely because you're not charging a lot for it so users shouldn't expect too much? Or is there something else that I'm completely missing? I'd really like to know. I'll curb my expectations if it turns out it's one of these reasons. I'll most likely use Drambo less of course. But at least I'll know where I stand, I'll be less frustrated about it and I won't be annoying you any more.
Are you prioritizing new features to entice more users to try Drambo? Are you prioritizing concepts which excite you so you don't get bored and tired of polishing the product? Are you approaching the whole thing leisurely because you're not charging a lot for it so users shouldn't expect too much? Or is there something else that I'm completely missing?
giku: “yes”
(Sorry 😅 it was begging that joke)
It's a legitimate answer so no need to apologize :)
Doesn’t add to the discussion, hence sorry
(Wrong thread for remaining text)
I don't want to dogpile, but just agree. Drambo felt a lot more stable when I first started using it three years ago, and I could only hope it would be more so today.
@oben I’m trying to balance my work between fixing bugs and research, that sometimes takes longer :)
Bug prioritization:
What I think it is: stability first, especially crashes, then whether it affects core or module functionality. And yes, the number of reported cases also matters.
What actually works despite that: pushing me. I know it sounds ridiculous, but don’t hesitate to repeat a request several times.
btw. you’re doing a great job, and I also love the style of your reports.
@Goldiblockz Judging by the TestFlight reports, I see there are far fewer crashes now, though sometimes it strongly depends on a specific use case.
I know it’s probably tedious, but can you tell me which concrete issues annoys you the most?
I collect issues reported on TF, Forum and via emails . My priorities may be wrong, so focused input from a power user means a lot (even when repeated )
Thank you for the response. Honestly, I'm not sure I like it because from my perspective it's "somewhere in between" but let's say I understand.
Regarding pushing: I feel kinda stupid because I think I'm already being too pushy. Of course I could remind you each day of these bugs, but what good would that do? Will you honestly be more motivated to work on them or will you just subconsciously start seeing our reminders as noise and ignore them? And I'm asking that totally seriously. Are weekly reminders what you had in mind? Also, in what format? Like this: "@giku bumping this issue"? Or do you need threats? For legal reasons: That last one was 100 % a joke. 😉
Anyway, I'll try to go along with your style but I won't stick around if addressing issues drags on for too long (for me that means a month or more unless you explicitly note the issue is complex and will require a long time to fix).
I know you posed this question to Goldiblockz but in this spirit of pushing you I'll answer it too: "can you tell me which concrete issues annoys you the most?" For me, curently the most annoying/frustrating bugs/issues are those that I reported and are related to the sequencer (both Drambo's core sequencer and the module) and the piano roll.
@oben 2 of the issues reported by you: PR section move with quantization off and Flexi clip synced recording are already fixed. The other PR issue: that complex UNDO sequence is still in the queue (not a blocker), because I had to fix AUv3 reloading bug (very important), long lasting MIDI mapped p-locking, automation recording tweak, and a rare crash (use case speciffic, but very important) . There were more of them.
In the meantime I released Otoo and work on visuals.
So it's not like nothing is happening. Occasional reminding but also some emphasis on importance (like "this issue blocks me") helps in shifting priorities. Thats all, nothing obsessive.
I hope this multiple re-recording issue reported here doesn't block you and I assume it doesn't.
I feel like you expect all the reported issues to be fixed in the upcoming beta. I can’t guarantee that and it never works this way. Some issues are minor yet need more time to fix.
Fixed on 2.53(1) - in review, should be available within 24h
I know you fixed those 2 and thank you for that :)
I never said nothing is happening. I have trouble with how you're setting priorities but we've already discussed that here so no need to repeat myself any more. You're right that I expected them to be fixed promptly - in one of the beta versions leading up to the public release. That didn't happen for these 2 and that's why I asked. That said, thank you for the candid answers and also for the clarifications. I'll keep all of what you wrote in mind, adjust my responses and curb my expectations.
Thank you. Will test when it's available.
When a serious issue appears, such as a crash, an update is released to the App Store immediately (leaving some other reported bugs in the queue).
I understand your frustration. I'm trying to do my best.
Thank you. Tested 2.53(2) and it works perfectly.