Has the “known issue” of Beat Slice mode’s notes not triggering correctly been fixed at all?
It is in the works and should be fixed on the next beta. There will be a Play+ beta released next and then T beta that merges the 2 new features that will be a release candidate if no new big bugs are found.
12 Likes
Great news, I’ve been excited for this fix. Hoping everything goes smoothly this time 
1 Like
I just got my mini back after a fairly lengthy hiatus. note input is a game changer.
Thanks team 
3 Likes
Can’t wait for the merged betas for the Mini. It definitely brings the mini to another level 
1 Like
Awesome, one thing I notice though if I want the base to start from another note but C, it breaks the continuity (for example chosing A, you have A-A#-B then Cis one octave lower… it would make sense to continue the scale
1 Like
Looks like takes longer than expected for the final.
I guess also now with Synth, the new drum and compressor modules, dev teams must have many different products to work on.
Still can’t wait to see this released. On holidays soon and would love to be able to bring with me the mini with me with a merged and final firmware.
Good luck Polyend dev teams 
I noticed another bug with note range selection through NOTE + Arrow keys. When you move to use multiple lines laterally, the selection goes to the row under instead of the opposite.
I installed the beta yesterday, and I believe I’ve encountered the same issue, or perhaps related. This bug significantly limited my use of the feature and I have not yet found a workaround.
Steps to reproduce:
- For this example, “Root note” is set to C3 and “Notes scale” is set to Minor
- Press “1” to enter pattern mode
- Press “Shift + Note” to enter note input mode
- Hold note to select the note range
- Attempt to set the range from C4-C5 and observe that this is not possible
While the bottom row of notes begins with C3 at the leftmost, and ends with G4 at the rightmost, the range cannot slide past the right of the bottom row to cover the next notes within the octave. It is possible to extend the selection beyond the leftmost box of the bottom row, however, resulting in a selection of e.g. A#5, C6, D6, D#6, C3, D3, D#3, F3, which is discontinuous and surprising.
I’m hopeful that this will be fixed in a subsequent build.
Cheers,
Jeremy
Update: I see this bug may have been discovered by a couple others, but I hope that the detailed information proves useful to somebody. I’m excited for this new feature as it has already greatly expanded the usefulness of the device as a portable, musical sketch-pad for me. Onwards and upwards 
4 Likes
I don’t want to sound rude, but when do you plan to release it? Beta is out for 6 months already and merged beta was promised 3 months ago.
1 Like
Guess I’ll have to stop promising things 
Yeah, it will be released sometime soon, but I can’t give you exact dates. We decided to roll up all the Synth firmware updates planned for the year into one big update. Finishing this will help them focus on other devices for the rest of the year.
7 Likes
Those Synth updates were stellar… so thanks for those.
Come on, Mitch. What can we expect? Within 1 month, is that realistic?
1 Like
In software development.. whatever timeframe is given.. most likely double it
3 Likes
Everything in the Q1 announcement has materialized, except for this update. As a customer, I’m patient, but your team set the expectations, not us.
3 Likes
Reading the above I’ll stick to the release version for now - while I’m still getting familiar with the Mini - but would love to try the Note Input in particular soon(ish) 
It’s actually crazy all that they materialized since the beginning of the year.
I can totally understand Polyend prioritizes new products, it’s that what is mainly going to bring them fresh cash.
Though I do also appreciate they keep improving the older ones, which also prolonges their commercial lifecycle hence is also a source of revenue in addition to rewarding their loyal user base.
Not an easy exercise for a company that is neither Roland nor Korg or Yamaha.
1 Like
Heya,
Hold on now! I believe there is some confusion on what the Q1 update is. I said i would post quarterly updates for the community on our plans as more transparancy was requested.
This isn’t a schedule that all of this would be released in Q1 - just an update on what to expect for the roadmap on upcoming things - what we have planned and what we are working on - As I said in the update Play’s would get an update first - which just happened - and then on to Tracker updates. So that will be the next focus. I’ll post an update for Q2 in the next few weeks.
13 Likes
I understand that nothing was promised, and quite frankly if you ceased development and the Tracker remained at 2.0 I’d continue to love it.
I’m pointing out that everything you announced has materialized save for this. While it may not be a roadmap, surely you understand your users wondering when the update is coming? It’s simple deductive reasoning. That’s the double-edged sword of transparency I guess. I personally come here literally every day to check for this update, because again, everything else has materialized, why wouldn’t this be coming.
And I would have kept my mouth shut if an admin didn’t make what I considered to be a snarky comment.
I love my Tracker Mini and with the 2.0 update it became nearly perfect, and the 2.1 update will make it perfect IMO, so I’m (and clearly other users are) looking forward to it. That’s why we want to know when it’s coming.
It’d certainly help my compulsive checking if you shared more details of when this was coming, but I’ll deal.
Have a good one.
3 Likes
If it was my development time comment that came across as snarky, i apologize. That was not the intention. 
It was in jest and a bit of a running gag in the software development world: Whatever time a developer tells you, you better double or triple it.
But this is the reason why Polyend doesn’t want to communicate timeframes. You never know what unexpected problems you run into during development. And there is nothing worse than communicating a timeframe and not being able to uphold it.
3 Likes
Just curious, can you share which language you write the software in? Is the mini based on linux (arch?) or is it a custom OS? As a software developer I’ve always wondered how these things are put together.
1 Like