The Neuros MP3 Digital Audio Computer
The Neuros MP3 Digital Audio Computer is a portable digital music player that includes an FM tuner. For penguin users, however, the most interesting capabilities probably are its support for music encoded in the Ogg Vorbis format and its compatibility with Linux computers.
The reviewed product is the 128MB model, which weighs 5.8 ounces and measures 4.3" high, 2.5" wide and 1.3" deep. Neuros currently is shipped only in the US and is expected to reach Europe during the first half of 2004, after certification is achieved. Multivoltage AC/DC adapter and support for European FM frequencies also will be added by that time. The box includes earphones, a 110 volt AC/DC adapter, USB cable, belt clip and 35-page User's Guide, with a mini CD-ROM attached. The Neuros HD 20GB model also has a car power adapter.
The 128MB internal memory holds two hours of music encoded at 128Kbps or up to four hours of recordings, depending on the encoding rate—64, 96, 128 or 160Kbps. Everything can be recorded, not only radio input. The device has a built-in microphone and a line-level input to record from external sources. Because the computer sees it as a USB mass storage device, it also can be used as a portable hard drive to move around or back up any kind of file.
The battery is an internal memory-effect free NiMH and is not replaceable by the user. It is supposed to last for ten hours of continuous playback, and it takes eight hours to charge. Digital Innovations declares the battery lifetime is over two years and offers a replacement that costs less than $10 US if the battery dies.
As far as radio is concerned, the Neuros is more than a passive FM receiver thanks to a couple of patent-pending features, commercially called My-Fi and HiSi. My-Fi refers to Neuros' ability to find a free FM frequency and then transmit the digital music it contains on the frequency, up to a theoretical maximum range of 20 feet. The user must then synchronize his or her tuner to the frequency shown on the Neuros display to listen to it through the system speakers.
The HiSi acronym stands for Hear It! Save It! and allows identifications of songs heard over the radio. Pressing the orange button on the right while an unknown song is received creates a 30-seconds digital fingerprint. The next time the Neuros is connected to the PC, the fingerprint is transmitted to the NeurosAudio Web site, which compares it to a database and returns the current song title and artist.
The HiSi service requires a free registration, which writes a unique key based on the device serial number into the computer registry. This process is different from the Web site registration needed to participate in NeurosAudio Web forums, but the two sets of data are linked by the e-mail address. The key is used for verification purposes. The only user data sent to or logged by the server are that key and the IP address of the computer to which the Neuros is connected. Digital Innovations explained that “HiSi connections and data ARE NOT correlated with user profiles and no information is shared with third parties” and that “if the user lends the Neuros to a friend he would only 'appear' as a different IP address”. HiSi requires TCP ports 4447 and 4405.
Use of HiSi is based on the Neuros Sync Manager client, which runs only on Microsoft Windows. Support for Linux is under consideration. Because the Neuros is seen as a USB mass storage device, the user could copy the OGG files to it, but the songs would not be available in the Neuros menus.
The playback of Ogg Vorbis music in the Neuros and its management from Linux are based on special firmware and on a Python script. The firmware, called Neurosetta, has been developed by Xiph.org programmers (www.xiph.org) and is sponsored by Digital Innovations. Binary, installation instructions and release notes are available at www.xiph.org/neurosetta. Bugs should be reported to bugs.xiph.org. Future binaries also will be signed digitally.
The Python script, Positron, offers a command-line interface to synchronize the music files on the hard drive and those on the Neuros. We tested the RPM package of version 1.0 on Red Hat 9. It requires the pyogg and pyvorbis libraries, whose RPMs for Red Hat 9 are available at www.xiph.org/~volsung. Positron has its home page at www.xiph.org/positron and is distributed under the BSD license.
Positron creates a database of all the songs in the user specified source directory and copies them and the database to the device. The main Positron operations are:
positron config # for configuration positron sync # synchronizes hard disk and Neuros # music repositories positron rebuild # rebuild the internal database
Oddly, the first command configured Ogg support as false, and it was necessary to open $HOME/.positron/config and change it to true. This should be fixed in future releases. It also is possible to add or delete single music tracks.
As of this writing (mid-August 2003) the Neurosetta/Positron combination still is declared as beta. It does not play back MP3 yet, and according to the home page, it may present “possible skipping on high-bit-rate files (over 200kps)”. We never experienced such problems during the review, however. Audio quality was superior to what the above statements had prepared us to expect. On the other hand, we did experience, “database problems [which] frequently cause the unit to freeze [during use], or songs to be missing or misfiled”—something predicted in the Positron troubleshooting guide. In our case, the misfiling corresponded to listing all stored songs correctly but playing back only the first one of the current list.
Articles about Digital Rights and more at http://stop.zona-m.net CV, talks and bio at http://mfioretti.com
|Designing Electronics with Linux||May 22, 2013|
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
- New Products
- Linux Systems Administrator
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- Designing Electronics with Linux
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- Nice article, thanks for the
7 hours 32 min ago
- I once had a better way I
13 hours 18 min ago
- Not only you I too assumed
13 hours 36 min ago
- another very interesting
15 hours 29 min ago
- Reply to comment | Linux Journal
17 hours 22 min ago
- Reply to comment | Linux Journal
1 day 16 min ago
- Reply to comment | Linux Journal
1 day 32 min ago
- Favorite (and easily brute-forced) pw's
1 day 2 hours ago
- Have you tried Boxen? It's a
1 day 8 hours ago
- seo services in india
1 day 12 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?