View Single Post
Estel's Avatar
Posts: 5,028 | Thanked: 8,613 times | Joined on Mar 2011
#7
Originally Posted by Copernicus View Post
I'm still working out the details on how audio actually works. I've currently got SPX, AAC, WAV, and FLAC encoding options set up, and they all seem to be working. I dunno if MP3 will work, there are patent encumbrances on it; but there might be a Nokia MP3 plugin available... Is "OGG" actually an audio encoding? I thought it was video. Let me do some research.

EDIT: Ah, yeah, "OGG" is the mechanism used for packaging audio and video together. (Kind of like Matroska.) There are several open source audio formats; I've already got support for Speex (an encoding format optimized for voice data). There's also Vorbis and Opus, which are higher-end encodings for music. Dunno just how much of a load using those would place on the N900, though.
There is some confussions, as OGG is indeed a container, but containers with vorbis audio inside have .ogg file extension, and are called "ogg" or "OGG" literally everywhere. Anyway, it's brillant codec by Xiph.org (the same organization, who gave us FLAC), and leading format of royalty-free, patent-free audio codecs. Furthermore, from technical point of view, it's a whole eternity better codec than mp3, and despite being "lossy" (as opposed to FLAC), it received so-called "transparent" codec mark - i.e., in plentora of blind tests, people were not able to distinguish it from lossless version of same recording (hit/miss ratio comparable to flipping a coin). All of that, while maintaining awesome ratio of decreasing file size.

Add to this fact, that it have pretty neat implementation for Maemo, and it seems like codec of choice for recording FM Radio, etc Of course, for conversations (call recording), speex (also by xipg.org) sounds even better.
---

Feature request - above obvious auto-recording of calls (SIP and GSM alike), which you're already considering for sure, it would be nice to have a (remembered) advanced configuration for codecs in use. IMO, most feasible way would be a text field, where user would put a string of text containing command-line parameters for codec, just passed transparently to used encoder (in addition to normal things defined by our application, like save path, etc).

This would save a 43456765434566 number of different option fields in GUI for every possible codec, while still keeping benefits of using GUI for generic options. It's worth to add, that this is behaviour used in most FOSS advanced recording/ripping/encoding programs even in desktop world - like Exact Audio Copy. For example, this is my "additional command line parameters" field in EAC, for creating best possible quality/size ratio (keeping being "transparently compressed" .ogg files of my music CDs collection:

Code:
--advanced-encode-option lowpass_frequency=20.0
...which doesn't interfere, but adds too, a Q=6 and tag-related settings from GUI. Would be pretty timefconsuming to completely GUI'dise all advanced parameters for all codecs available in Orecch', and keep them updating as new adv. features are added to encoders.

/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
 

The Following 11 Users Say Thank You to Estel For This Useful Post: