iPhone XS Max/ Hi-Hat

[Momantai]

As a test I configured a kit using the app. Then I started Garageband (the app still running). All sticking works and Garageband gives good sounds. The kickdrum also works ok.

The hihat pedal seems to work as a “fast close action”, the sound is different from hitting with a stick and is more like what it should do. There is no different stick sound while holding foot up (open hihat) or foot down (closed hihat).

So I think the sensor works “as a stick” but produces another sound, not as an open/close indicator ?

[P-A]

@Momantai

We are actually working on this problem, we never saw it before, so it’s quite difficult to resolve, but we are on it
In Garageband, unfortunately, the opening of the hi-hat is not handled

[Michael]

I still have the problem where when I synchronise the sensors I still have the same problem with the hi hat that it requests that are use drumstick right left right left where the kick drum automatically recognises that sensor can you help

[P-A]

@Michael The hi-hat problem is quite weird, we are not able to reproduce and resolve it at the moment. It is one of our main priorities and our developers are working on it

[Michael]

You seem to have a lot of concentration for updating your firmware for android missing the fact to keep updating iOS.

[P-A]

Hi @Michael,

We are working both on Android and iOS app. A new update for iOS just came out by the way : [IOS] App Update 1.0.3

Another iOS update will follow very soon

[Michael]

Thanks a lot for your update and continuing support

[Babice]

I have exactly the same problem with the HiHat, for 4 long weeks now. It is Impossible to play properly whit these captors on the left foot. (I have 4 different sensors that I’ve tried to configure…).

Je vais continuer en fançais, il est très frustrant de ne pouvoir se servir correctement du pied charleston, en mode ouvert ou fermé, ou semi ouvert le son est exactement le même qu’importe l’approche.(son de frappe sur Charley du dessus fermée). Mais le problème vient certainement je pense de la configuration, comme Michael ou une autre personne dont je ne me souviens plus du nom, lors de la configuration du pied Charley, la logique voudrait qu’Il soit préciser pied levé ou posé pour simuler les diverses ouvertures du charley, mais il est juste demandé de taper avec main droite en premier et main gauche.
J’ai essayé toutes sortes de combinaisons. Pied levé en frappant, puis fermé etc…
J’ai essayé aussi d’appairer à zéro les capteurs, supprimer les 2 app puis les réinstaller etc… et rien n’y fait.
Juste l’impression de perdre mon temps.
Après une expérience livraison des plus lentes, (logistique livraison pas au top, j’ai dû relancer deux fois), je n’arrive toujours pas à apprécier Senstroke qui semble pourtant fantastique sur papier.
Très frustrant comme expérience pour le moment. J’espère sincèrement que des updates arriveront plus rapidement pour profiter du produit.

De plus je souhaite préciser comme j’ai pu lire ici ou là par certain sur le forum, que l’app updater laisse à désirer… comme un sentiment de produit non fini ou ultra bugé. L’update fortement conseillée à été un calvaire, en essayant d’updater le firmware des capteurs un à un, la plupart du temps l’app freezait, le spin loader tournant à l’infini sans aucun changement. Même parfois après avoir relancé plusieurs fois l’app. Avec bcp de patience j’en suis arrivé à bout.
J’attend patiemment une nouvelle update iOS en espérant qu’elle règle les
problèmes de la Charley.

Dernier point qui peut peut être aidé des personnes face aux
Latences : ne pas jouer avec un casque non filaire, les capteurs communiquant avec l’application en Bluetooth, les casques wireless Bluetooth ne suivent pas… perte de rapidité via l’appareil utilisé. La latence se faisant sacrément sentir. Mais ça semble plutôt logique.
Par contre sans casque, via le speaker de l’iPhone pourtant pas des plus récents, c’est très réactif pareil avec un casque ordinaire (fil). Si ça peut aider certains …

cordialement,
Fabrice.

[Jerome]

Bonjour Fabrice,

Je vous remercie pour votre message. Nous sommes tout à fait conscient que le problème du charleston est vraiment gênant car vous ne pouvez pas profiter pleinement de la gestion de la pédale.
Sachez que ce bug est vraiment sur notre liste des priorités. Nous n’arrivons malheureusement pas à le reproduire malgré nos nombreux tests c’est ce qui est problématique. C’est pour cela que nous n’avons pas encore apporté de correctif. Nous travaillons actuellement sur une nouvelle fonctionnalité IOS (changement depuis l’interface des rôles des capteurs) qui devrait par la même occasion corriger ce bug.
Auriez-vous la possibilité de nous faire une capture vidéo de votre application lorsque le bug apparait svp ? Quel est votre modèle de téléphone ?

En ce qui concerne l’application de l’Updater nous travaillons également en ce moment à sa refonte. Nous étions tellement enthousiastes avec les nouveaux firmwares que nous avons proposé la mise à jour malgré une application qui n’est pas très ergonomique je vous l’accorde.

Nous nous nourrissons de tous vos retours et c’est grâce à vous que nous nous améliorons.
J’espère que malgré tout vous êtes satisfait de votre achat et sachez que nos équipes travaillent d’arrache pied pour vous proposer des mises à jours qui amélioreront l’ergonomie, les bugs avec de nouvelles fonctionnalités.

A votre dispo

Jérôme

---

In english

Thank you for your message. We are very conscious that the hi-hat problem is really embarrassing because you can’t take full advantage of the pedal features.
Please make sure that this bug is really on our priority list. Unfortunately, we are unable to reproduce it despite our many tests, which is what is problematic. That is why we have not yet made any fix. We are currently working on a new IOS feature (change sensor role into the app) and we hope that should also fix this bug.
Would you have the possibility to make a video capture of your application when the bug appears, please? What is your phone model?

Concerning the updater, we are also currently working on. We were so enthusiastic with the new firmwares that we proposed the update despite an ergonomic application, you true.

We get all your feedback and help us to improve the apps.
I hope that despite these problems you are happy with our company and know that our teams are working hard to offer you updates that will improve ergonomics, bugs and give you new features.

Best Regards

[GEM]

Bonjour Fabrice!

Ton expérience concernant les casques Bluetooth est, j’espère, très utile pour d’autres utilisateurs. Je vais la traduire plus bas pour nos amis anglophones.

Si tes problèmes de son du charleston proviennent effectivement de la configuration, sache que nous travaillons à résoudre ce problème. Sinon, n’hésite pas à ouvrir un autre sujet, de sorte que nous puissions échanger, identifier le problème, et le régler au plus vite pour toi et tout autre utilisateur affecté.

Merci de ta patience et de tes retours.

[GEM]

Hello everyone,

@Babice raises an excellent point in his post, for people who suffer from latency issues.

Senstroke sensors are Bluetooth devices, which means they share the same antenna as Bluetooth audio reproduction systems, whether portable speakers, earbuds or headphones. As he says, using wireless (Bluetooth) audio can therefore cause higher latency. However, the iPhone speaker or a wired audio connection make latency much lower, which might help some people encountering this frustrating issue.

Thank you!

[GEM]

Hello @Michael and @Momantai,

I’m working on the issue you have, but I cannot seem to reproduce it. I’ve been told that @Michael had a video where he demonstrates the issue, and I’d very much like to see it.

Right now, I assume the following:

- the problem exists at least since version 1.02 of the iOS app
- using version 1.03, the problem happens when running in Advanced mode
- only four sensors are turned on in the room where you are playing

I hope to be able to fix this issue within the current sprint for release 1.04, and I’m waiting eagerly for any information that could help us get you a fix asap.

[Momantai]

Your assumptions are correct.

The screen rotates in oth beginner and andvanced mode. When changing mode (click on “Validate”) it rotates and ends upside down. It always turns to “good when the iPad button is on the right side”. It does not turn when I turn the iPad.

I have only 4 sensors turned on. Never any other active bluetooth device in the neighbourhood.

I do not always “Calibrate” my sensors. Should I do that with every update ?

[GEM]

Thanks @Momantai.

There are a few things here, I’ll respond to them in turn.

First off, while the application is currently maintained and tested only on iPhone, we intend to extend it to support of iPad as soon as the most critical bugs that come up are fixed! I believe however that the behavior should be relatively similar. To tell the truth, I’ve added the automatic rotation because when I work on the app, the iPhone is plugged in with a cable and I found it more practical for me. It might be a good idea to let the user choose which orientation (left landscape/right landscape) suits them best, but it’s currently of lower priority to us than fixing the bugs. I’ll get my iPad from home and test the app on it anyway. What’s the iPad version you’re using? Mine is an iPad Air, first gen.

Small semi-technical explanation: the app did not initially rotate, but we had to add that because when the iPhone opens up the App Store dialog, it needs to be in Portrait, while all the application was designed in Landscape. We therefore retrofitted Portrait and forced autorotate for other screens. I’ll have a pass at the whole UI later today and check if I did not forget something egregious, as regards to rotation.

Calibration is now required in Simple Mode, and while not part of the mandatory process, is part of the tutorial in Advanced mode. It’s not necessary to calibrate when the application updates, but you need to do it when you update the Senstroke’ firmware. In any case, calibration should only improve the accuracy, and the first step (gyroscopic calibration) is very fast, so you can do it as often as you please.

[Momantai]

My iPad is an iPad PRO 10.5" model A1709. It has WiFi + cellular.
It runs on the latest IOS version (12.1.4)
I use it mostly with the power connection (and pushbutton) on the left. In this situation the app is upside down.

[GEM]

OK I see your use case.

I’ll have to think about it, since the iPhone is the primary target, and the power button on X is on the bottom if the application runs in LandscapeLeft…

[GEM]

Hi Momantai!
I’ve added in the next release (1.04) a small change that might help you with your rotation issue.

In the Settings for the app, I’ve added an option for setting left or right, which will be what the application rotates to. By default, it’s the iPhone X preference.

[Momantai]

Ok, I’ll try it as soon as version 1.04 is available in the AppStore.

Are you also working on the hihat left/right issue ?

[GEM]

I haven’t yet succeeded in reproducing the issue. I did find a few related small bugs that I fixed while I was hunting for that issue.
I hope @Michael sees the thread and can weigh in…

[Michael]

This is my problem with the hi hat. Should the sensor not ask to be open or closed using my left foot Not the drum sticks. ???