Mockup for floating FeenPhone recorder interface

FeenPhone recorderMock
.
It may be a couple months, but we’ve decided that one of the more important next features in FeenPhone will be recording. Recording will be WAV only, with a choice of 44.1k or 48k; and a choice of Mono (all hosts mixed to one mono WAV file) or Stereo (with sliders to pick how far left or right each host goes in a stereo WAV file.) We’re not including MP3 as a recording option, because that degrades the audio if you’re going to edit later. If you’re not going to edit, there are plenty of free programs to convert a WAV to an MP3. More importantly, having a program output to MP3 actually requires paying a royalty, believe it or not.
.
Files will be automatically named with date and time recording starts. (Or that combined with user names of the hosts connected when recording starts.)
.
And we’re not going to offer a multi-track option (one host to each track for more than two hosts), because, well, that’s a nightmare to mix, not many people could do it. Trust me, I know what I’m doing. I could do it, but I am also an experienced audio engineer. Most podcasters aren’t. And Derrick and I like to keep things simple. Podcasting and radio should be simple and sound great. Put it this way: I could properly mix four tracks of four hosts but I don’t. I get it right on the fly, during the show. People who tweak that much on podcast editing, recording and editing more than two tracks, tend to podfade pretty quickly. Also, adding more than two tracks of recording would increase CPU usage which would increase latency and drop outs, especially combined with more than two hosts.
.
Notes to Derrick:
.
Hey Derrick,
I do like the idea of having the recording interface a moveable pop-up window, like the thing I sent you today. At the top of this post is a quick-n-dirty mockup. From a user standpoint, it’s the right size, has everything it needs, has nothing it doesn’t need, and everything on it is the right size. (Especially the Stop and Start Record buttons.)
.
I don’t think the recording interface will need volume sliders or Vu meters, since the recorder will be recording what you’re hearing in your headphones. The sliders and meters on the front basic interface of FeenPhone will suffice.
.
Controls and stats included in the mockup are based on our discussion last night, your suggestions and mine, and also based on usability from my experience.
.
The user will be able to have FeenPhone minimized or behind a browser or behind a document of their show notes, but still have the record interface visible in a corner of their screen. Or on top of any program. The pop-up interface should stay in front of any other program:
.
FeenPhone-recorder-floating3
.
There should be a thin black border around the recording interface so the interface is easy to see against other programs. Keep in mind this is something people are going to need to access in a hurry while multitasking, possibly several times during a show. (I always recommend saving a file and starting a new one at least every half hour in any recording program. Saves on the heartbreak of crashing and losing data. This will be strongly recommended in the now-to manual section for the recording function when we roll it out.)
.
It’s important from a user standpoint to have a separate Stop and Record button, not one button with two states. And that they be as large as in the mockup so they’re easy to hit with a mouse when you’re multitasking. Doing a live show can be unpredictable and stressful. You don’t want to have to hunt for an important button while doing a show.
.
When not recording, the black and red indicator that says “Recording” should say “Ready.” It should NOT flash. Some programs have an indicator that flashes, but it’s very distracting. The indicator could be less-bold colors when in the Ready state though.
.
The Pan Mixer sliders would not appear in Mono mode. And in Stereo mode, if someone is foolish enough to have more than four hosts on, the overall box would need to automatically scroll wider, or have a scroll bar appear to access all the sliders. (I say that more than four hosts is foolish because it is. That’s always a “bad radio” clusterfark, even if they’re all in the same room, but especially if they’re not.)
.
The Pan Mixer sliders should be accessible while recording, not hidden in a sub-menu. You want to be able to adjust them on the fly.
.
There should be a button on the recording interface that will only show up in Stereo mode called Raw / Mix. It will change what the meters on the program front are metering and what you hear in your headphones. It will only have two states and will switch both the meters and the headphone mix from Raw (post-Vu sliders on the front) to what’s being recorded.
.
The Raw / Mix button should be on the recording interface, not the basic front. Basic front should be simple as possible. And in Stereo Mode you’d likely want to listen to the mix without needing to see the meters more often than vice versa.
.
The whole recording interface box should pop up when you push a button on the main FeenPhone interface in basic mode. The button should probably be just the word “Record” or “Recording” in a little horizontal box. I can’t think of an icon for “Recording” that all people would know and that wouldn’t be archaic.
.
I’m sure you can make the recording interface a lot more pretty, but this is basically the features it needs and how it should behave.
.
Worms!
–MWD
.

Posted in Tech   

Author: MichaelWDean

4 thoughts on “Mockup for floating FeenPhone recorder interface

  1. Why don ‘t you make it Lame DLL aware, so people who want to code mp3 files dowload the lame DLL at http://www.rarewares.org/mp3-lame-libraries.php place it in de feenphone directory and are able to save mp3 files directly.

    You do not have to deliver the DLL so without the DLL tour program can ‘t encode mp3 files so you do not have to pay royalty ‘s for it.

    A lot of app handle it like this.

    Alternatively you van do this for a lot of audio formats, like OGG vorbis, flac, AAC.

    The edcast encoder for audio streaming did the samen.

    Bye
    Dennis

    1. Recording to MP3 is far from best practices for podcasting and radio. We don’t want to encourage crappy audio. Should be recorded WAV, then edited. We’re making FeenPhone as pro audio gear that’s easy to use, not dumbing down quality for people who don’t care enough to have best audio. Those people can use Skype and any of the third-party MP3 recorders for Skype.

      If someone can’t drag a WAV into LameDrop, they aren’t ready for a pro-audio VoIP.

      A lot of the decisions we’re making with FeenPhone are to try to get people more concerned with better audio. We’re making something great, pro-quality, and not compromised. Something better than things people pay for, and we’re giving it away free. We need to do it the right way. It’s part of our software philosophy.

      Plus, we want to keep away from software bloat. We don’t want to add one more function when the lack of that function is actually a feature, not a deficit.

      I like software that’s like aspirin: It does very few things, does them very well, has few side effects, isn’t expensive and is easily available everywhere.

  2. I do not use mp3 anyways, it was just a reaction on :

    having a program output to MP3 actually requires paying a royalty, believe it or not

Leave a Reply to Dennis Cancel reply

Your email address will not be published. Required fields are marked *