Amazon Fire Tablet (7) and Voice Recorder question

Julie_23 · ‎04-10-2010

Hi,

Does anyone have any experience with Amazon Fire Tablets and their Voice Recorder apps?

It's an Amazon Fire 7 tablet, using the "Super Voice Recorder."

It seemed to record what I was wanting it to; however, when going to re-listen to it, there are large spaces of silence.

Is there any way possible to retrieve what was recorded?

Thanks!

gardenman · ‎03-09-2010

"Is there any way to retrieve what was recorded?" Absolutely. It's on a file in there somewhere. Where exactly is the hard part. You would need to do some serious file exploring to find it. And they don't make that easy. It could be in the "Super Voice Recorder" program data files. It could be in the Fire audio files. It could be anywhere.

The good news is Super Voice Recorder (SVR) should know where it put it and once it's found it, you can then use their software to export it to another device for editing if that's your goal. According to the Google Play Store SVR lets you "play, pause, send, share, etc." The "send, and "share" are good options for you. That should allow you to send the audio file to another device where you can do whatever you want with it. I'm guessing you want to edit out the long dead periods.

Fly!!! Eagles!!! Fly!!!

Julie_23 · ‎04-10-2010

Wow, @gardenman, what you wrote is encouraging!! Thank you!!

I will look into everything you suggested. The blank spaces don't matter really -- I just am hoping to try to hear what was recorded. As it is now, the audio completely cuts out after a few minutes and just goes quiet (tho, the time stamp keeps up).

What complicates matters is that, when downloading the app, it said the SVR may have glitches of some sort. It wasn't the preferred app -- would have rather used simply the "Voice Recorder" app (and not the Super version) -- but in the moment that's the one that was used.

Had used it at a doctor's appointment.

My thinking is that the original audio taping has a glitch such that sharing it would possibly produce the same. Perhaps it was a faulty app (not updated version, etc.).

Thanks again for your helpful suggestions!