Recording not in Rabbit Hole

I did a recording today for about 1.5 hours 6/5/2024 ~9:20 PST, and it did not show up in the RH. It was indicating on the screen that it was recording the entire time until I ended it by manually. No indication of errors. With as much memory as is available on device, there should be a local copy of recordings on the device for later streaming to the cloud.

Were you using wifi or data for the recording?

I was on T-Mobile WAN, don’t know what coverage was like. My iPhone was on Verizon.

Has the recording issue happened before or on consistent basis?

Had this happen before. Rabbit really needs to use the internal storage for recordings and then upload after. Please make this the ultimate voice recorder!

2 Likes

It has happened before, but it was mostly around testing, so wasn’t super important. Yesterday was actually an important meeting, so a little disappointed to have lost that recording. I kind of regret not turning my phone recording on at the same time.

I’ve reported the recording issue to team this morning. We will try to further improve the stability of all recordings.

1 Like

just curios if there is a reason why the recordings cant be temporarily saved on the device and then uploaded after the recording is complete when there is a stable network connection?

I would be pissed beyond believe if I was relying on the r1 to record an important meeting and the device looses connection for a few seconds at 48 minutes in to an hour long recording and boom its gone.

This has been brought up in the discord channel quite a few times, and it seem seams to be a legitimate request, but whenever this feature is requested rabbit responds with a generic response like above. Not dogging rabbit here but seriously if there is a reason that it can’t be saved locally first as a way to prevent loosing the recording until its safely uploaded to the rabbit hole?

I’m sure it is possible. I’m happy to explain more on how our product feedback process works. We, from the community side, gather all user request, feedback, suggestions and bug reports and share them with product/tech team. They will then analyse and prioritise user requests based on resources and urgency, and assign responsibilities for other team members to work on. From my end, I can’t make a promise on if any feature/suggestion will get worked on or by when, but I can promise that all your voices are heard by our team and this is how we keep improving r1 in every OTA/cloud update. :raised_hands:

4 Likes

I absolutely know you guys are hammering on it hard and doing a great job. My post wasn’t to dog rabbit or imply you weren’t listening to us. but there are some things we users scratch our heads about, like something like this recording issue and it just seems logical to have it stored locally first and uploaded later. I figured there must be a reason why it wasn’t designed that way in the first place and was curios why LOL but once again you guys rock :slight_smile:

2 Likes

Hey guys. Just adding to the notes here on this topic/issue. I tried it again today in a long session for recording. I initially started the recording with 77% batter left. I got nervous after about 5 minutes, so I killed the recording and that session uploaded to the Rabbit Hole. I started another recording, checked it at the 40 minute mark and it was showing 30% battery to go. Unfortunately, I didn’t catch it, but it died. That whole session was lost.

It also might be useful to be able to initiate recordings through terminal. You don’t always want to announce verbally “start recording” in the middle of a symposium.

2 Likes

are you saying you lost 47% of your battery in just 45 minutes? That seems insane. And here I was complaining about loosing 2% per hour LOL

Keep in mind that it was recording the whole time. I think the bigger issue is that it was slow in refreshing what the actual battery % was. But they really do need to focus on what their killer app is, and I think the recording is one of them. So caching locally on device is going to be key here.

I just lost my first attempt (1hr) recording just now too :frowning: so +1 to local recording - and I agree 100% with u on recording as a killer app, as i search for a reason not to send the r1 back i think a rock solid / reliable meeting recorder (and accurate AI summariser and transcripter) that rivals what other tools can do would be it.

I was at a meeting / presentation yesterday. Started a recording, it started. And now I can’t find it. It feels so bad that the recording is lost…

I was using my reliable hotspot. And it was a maximum of 25 minutes i tried to let it record. It stopped by itself and I don’t know what happened.

Big issue.

(At least save the recording on the 128GB available locally)

Currently, the Rabbit team has a relatively limited number of people. In fact, the function of saving data locally should have been realized at the beginning of product sales. For example, taking photos does not require a network, and recording can also be done without a network. When the network is stable, it can be uploaded to the cloud for processing. In this way, it can bring users a more convenient and efficient user experience. :upside_down_face:

Exactly, I understand we want to keep the R1 concept simple and not make it like a smartphone. At the same time a simple way to access and see what you recorded or captured is a essential base.

I know the rabbithole is being worked on…

1 Like