@kamil thanks! Note that I care more about the original reset problem than the button behaviour (but that is just me, with my egoistic hat on 
Hi Kamil, any findings or progress?
Yes, so far I’ve fixed a few quantizer-related issues and also have fixed settings being loaded at startup. Hoping to tackle a few more bugs today and then have a beta available tomorrow for people to test.
1 Like
I haven’t been able to reproduce the run button problem here though. Even with an external clock at extremely high speeds (sequencer is a motorboat…) it still responds as normal.
Hmm, then I will do more test under what conditions the run button responds bad and when ok. Maybe my unit is having any special problem.
How about the other buttons, could you reproduce unresponsive behaviour with reset, load and save?
Unfortunately not. I’ve tried several units now and have no problems with button responsiveness even under a very fast external clock… definitely strange!
Thanks for taking care… Then I will flash 1.30 again or do you have any other thing I can do or check?
My Metropolis is also experiencing occasionally unresponsive buttons after the 1.30 update.
1 Like
Ok so based on some feedback from other users, it seems that the “unresponsive buttons” thing may be due to people holding down the buttons for too long. Since the buttons need to differentiate between clicks and holds, after a certain time of being held down they act as in the “hold” state and so won’t trigger the click event when released. For the people who are having trouble with button responsiveness, can you try a shorter click on the buttons?
I may just need to tweak the amount of time before a push down on the button is considered a hold instead of a click.
Thanks for the feedback. I flashed again today and buttons seem ok at the moment…curios thing …
I’m thinking a little bit that unresponsive buttons may start to happen after some time running the unit. I will report when strange behaviour occurs again. Unluckily
I can not test so much since I go for vacation tomorrow.
However I will make noise when there is something to report.
kamil, quick button pushing seems to be working. Thank you.
Great. For 1.31 I have increased the timeout so longer button presses (up to a point) will also work. Still a few things I want to tweak but should have a beta out early next week.
2 Likes
I’ve posted a beta of 1.31 in another thread. Please give it a try and leave feedback there:
is this fixing the reset problem?
Unfortunately not. I’ve looked into it but haven’t been able to determine a reliable fix yet. I’m going vacation this Friday afternoon so it will have to wait till I get back.
thx for the headsup. have a good vacation kamil
Hey @kamil, can you share your views on the reset problem? Is there still something in the pipeline, or is it unlikely this will be fixed soon?
Thanks!
Hi @Kamil, would it be possible to add an unquantized mode where the Metropolis puts out a straight unquantized CV? It would unlock a ton of possibilities with my Phonogene and Granpa, and also let me use the Metropolis with an external quantizer.
I was wondering why it’s not already there; is there a technical restriction or is it a design decision?
Anyways, will be updating the firmware to the latest version tonight (USB thingy is in the mail) and looking forward to the “run” reset mode that’ll let the metropolis play nice with my Minibrute 2’s sequencer.
Keep up the good work!
If it was there it would have to be pretty low resolution, there is a fair bit of noise on the ADC uses to read the sliders that’s eliminated by filtering and quantizing. Also the way the module software is designed it’s not straightforward to add an unquantized mode.
Ok — thanks for the info.
By the way, I got my usb thingy yesterday and updated my Metropolis to the latest version. The new « run » reset mode works perfectly with my Minibrute 2. Good work!
Oh and the 1v/octave on the aux is awesome. Love it.
Thanks for the lollipops and stickers! It’s a real nice touch!
1 Like