Please, no more Morse code development!

suggestions & ideas
1

:point_up: Please VOTE here! Thanks! :pray:

I really don’t like this whole Morse code development when it comes to the PTT button, it’s not intuitive at all! It reminds me of entering cheats in old video game consoles. Why do you always press the PTT button X times? r1 can speak, so why shouldn’t you do it all using voice? For example, you could press the PTT button just once and say, I want you to listen to the wake-up word from now on, e.g. “Hello Rabbit” and then this option would be activated in the settings. But please, dear community and dear people responsible at Rabbit, don’t turn r1 into a Morse code device… I think that’s going in the wrong direction, there are much better and much more intuitive solutions…

I think the operation should always follow the same line. For example, to exit a function it should ALWAYS be possible to scroll up and select the back button by pressing the PTT button once and under no circumstances via this fatal Morse code thing (to press the PTT button X times).

R1 was supposed to be the most intuitive computer to use, but when it comes to pressing the PTT button multiple times, I think Rabbit has unfortunately taken a very wrong turn in its development.

One should therefore not cut off the supporting pillars of such a great idea as r1 and try to undo obvious mistakes.

But plwase, BELIEVE ME, NO MORSE CODES! :heart: :otarabbit:

That will 100% not end well!

I think usability should be the top priority for every device; that has always been the recipe for success for every successful device and every good software.

Do you find pressing the PTT button multiple times intuitive?

  • YES!
  • NO!
0 voters
2 Likes
2

Morse codes like these are perhaps nice as Easter eggs, but they are not at all useful as the main operating option and, as I said, they are not intuitive at all.

Who is supposed to remember all of that?

And especially for beginners, I think that is 100% fatal when it comes to intuitive operation.

2 Likes
3

That in the end no one will understand this morse codes anymore…

1 Like
4

Apart from that, this whole Morse code operation can also exclude people with motor problems or disabilities from using r1, because these people, for whom r1 could be particularly useful and helpful, are then simply no longer able to use it fully, precisely because of this Morse code development… I therefore ask everyone here to realize that this cannot be the right way and that much more intuitive ways should at least be considered.

1 Like
5

Multiple presses are more reliable than AI input. Five dots give you a soft reset because you can’t do that by accident, and eight dots turn off the device because it is faster than holding the power button for 60 seconds. Imagine your device freezes because of network failure - you won’t be able to turn it off or reset it. Voice input like “Hello rabbit” requires constant monitoring, which means high energy usage. When voice input freezes, how are you supposed to do anything with your device beyond waiting till the battery discharges and possibly setting the device on fire as a part of freezing the device, including safety protection? I oversimplified, but even with hardware protection, it is not a good idea.

6 Likes
6

Again please… How many times did I have to press it again to restart it, ten times? Or was it only five or eight times? Do you understand the problem? I think there should be a routine, controlled from the cloud, so that the cloud notices that an r1 is no longer working properly and then simply sends it a reset signal. That would be the best solution for users and if that is not possible, then in my opinion it should also be the case that the normal function of a long press on the PTT button is ineffective and r1 can simply be switched off with that. So that there is a routine that prevents switching off during normal operation, but which becomes ineffective in the event of a malfunction or a freeze.

1 Like
7

This could be implemented in such a way that the turn-off function works in the lowest level of the software of r1 but is overridden by the highest level of the software, as long as this level functions error-free.

1 Like
8

Are you complaining about increasing the number of special functions from ONE to TWO? Because there are no more of them and those are used in emergencies for regular usage, you will be directed to the power-off menu for confirmation to turn off the device. What you are asking - turning off by voice already exists; button presses are for convenience.

2 Likes
9

I’m not complaining. I am just warning and i only suggest good improvements.

1 Like
10

Please vote everyone, I am also looking forward to the results. :satellite:

1 Like
11

Thank you for this post and the discussion about this topic, @leahcim.:+1:

At first I have to say that I do not like capslock titles or sentences.

If an idea have good arguments, the idea will be supported. Capslock do not support this.:slightly_smiling_face:

To your suggestion I would like to give an other suggestion with the following intro question:

Why we should decide between an option A and option B?

The rabbit r1 is our personal assistant.
The goal of our rabbit should be on individualization.

Pesonally I like to use my rabbit r1 like a walkie talkie, although I am open minded for new technical features because of my job in the IT sector.

@Tofi has mentioned a very good argument for the case if the rabbit do not react anymore of our voice commands. In the IT you have to always a plan B in this cases. Pressing button is a very good solution.

The individualization is the key the rabbit r1 will be get the personal assistent as we want. Later with the teach-mode in this year, we have a great device compared with other technical devices or smartphones.

So I do not like to decide between two options.
I prefer the compromise to have both options, which we can activate or deactivate in our settings.

What would you say about this compromise which will increase the individualization much more as your option A and option B? :slightly_smiling_face:

3 Likes
12

I would prefer if the official provided three operation methods when turning on the device: one is pure voice, one is touch plus voice, and one is pure touch. This way, different demand problems can be solved.

1 Like
13

If the conversation is too long, it is indeed prone to triggering a shutdown. However, the official must also implement a setting for restarting the device when it gets stuck. It is indeed a problem.

1 Like
14

Basically, I think this compromise is really good, I really have to say, and the idea that it should be stored in the settings is also exactly the same and absolutely essential. There is just one thing though… I think it absolutely has to be possible to switch off these Morse code-like button functions completely. I mean, if you’re into something like that, please do, I don’t want to spoil anyone’s fun, but you can’t exclude people with motor disorders and that’s what happens with functions like this. Just think of people with Parkinson’s, this group of people would find it very difficult to achieve a certain number of clicks in a short space of time exactly. That’s why I’m so critical of it and because it has an incredibly high potential for error. Simply because in the end no one will be able to remember the whole thing if this idea is taken too far, and that’s already happening, at least in my opinion. That’s why I personally find @RaineSilverlock 's solutions very interesting. @BlueNexus9

1 Like
15
1 Like
16

Nevertheless, I ask that you continue to vote here, please just so that at the end we have a clear picture for those responsible at @rabbit.

1 Like
17

If there is no reply from the authorities, it might be because of the rest day. We’ll have to wait until Monday for a reply. So we can only wait and see.

1 Like
18

Now it really happened to me, I want to generate a Suno song, then suddenly Spotify starts playing while I’m giving my prompt for Suno and I want to end it, so I press the PTT button about five times, nothing happens, I press two or three more times or so and my r1 restarts… Great… So I think this Morse code pressing was the worst idea, unfortunately it has become reality. :frowning: But what does it matter, first world problems… :roll_eyes:

A few more great ideas like this from our community and r1 will be realy completely useless, because then only some Army Morse code specialists can operate it… R.I.P. :headstone::otarabbit:

2 Likes
19

This is expressly not a criticism of @rabbit or the developers at Rabbit, who are simply trying to program the jack of all trades for our community.

2 Likes
20

I think if you’re talking to r1 in morse code, something has gone horribly wrong :smile:

2 Likes