From: Emily B. <kon...@gm...> - 2005-12-14 17:05:20
|
i think the FAQ looks great, and i can't think of anything in particular missing or inaccurate. (in short, being new to iRiver/Linux ownership, i feel like it's answered all my questions.) why not put this FAQ right on the site ? i could HTMLify it in a few minutes. actually, the website could use a nav menu, too. in which the FAQ should figure prominently. maybe i could slightly redesign the site a tiny bit ? em. Geoff Oakham wrote: > Hi Guys, > > An FAQ update is long overdue.. especially with the MTP discussions > we've been having. Below is the latest version.. if you have an > contributions, please email them to me! > > ------------------------------------------------------------------------ > > FAQ for ifp-driver mailing list. December 14th, 2005 > Copyright (C) Geoff Oakham, 2005; <oa...@us...> > > Permission is granted to copy, distribute and/or modify this document under the > terms of the GNU Free Documentation License, Version 1.2 or any later version > published by the Free Software Foundation; with no Invariant Sections, no > Front-Cover Texts, and no Back-Cover Texts. > > 1. What's the difference between "Manager", "UMS" or "MTP" firmware? > > Each firmware supports different hardware drivers. Sometimes iRiver > releases versions for the same firmware, to give users more choice. > > "Manager" is the native protocol used by many iFP models, and requires > "Manager" drivers to access the device. "UMS" firmware causes the > device to behave as a "USB Mass Storage" device, which works on most > operating systems without additional drivers. > > The "Media Transfer Protocol" (MTP)--created by everyone's favouriate > company--is an extension to the "Picture Transfer Protocol" (PTP). > Players from the T10 family are reported to ship with this firmware. > > 2. Should I use the "Manager" or "UMS" firmware? > > This is a matter of personal choice. However, there are some points > to consider: > > * UMS firmware is convient because it allows most computers > to use the device without additional drivers. > > * Uploading files appears much slower with iFP UMS firmware. > > * You can't change FM radio stations or remotely access other > advanced features using UMS firmware. > > * UMS firmware isn't updated as often or as quickly as Manager > firmware. UMS firmware may even be unavailable for newer > models. > > So unless you need the flexiblity of UMS firmware, stick with the > Manager firmware. > > 3. Where can I download new firmware? > > Download firmware from the iriver international website: > > http://www.iriver.com/ > > Regional websites aren't always up-to-date. > > 4. I can't find UMS firmware for my iFP model! Where is it? > > iRiver might be phasing out UMS firmware. Also, there is usually a > delay between the release of new Manager firmware and its equivalent > UMS firmware. > > 5. How do I update the firmware if I currently use UMS firmware? > > See http://www.iriveramerica.com/support/ums.aspx > > After you switch to UMS firmware, you can't use ifp-line or the Windows > Manager driver to access the device. So firmware updates are handled > differently. > > Basically, copy the firmware to your player's root directory (without > changing the filename). Unplug the device and enter the "general" > configuration menu. There should be an option for firmware upgrade. > > (Thanks to Anthony Iano-Fletcher for fielding this question.) > > 6. Does Linux or *BSD support iRiver's "Manager" firmware on flash music players? > > iRiver doesn't officially support Linux, but there are a number of > third-party manager projects. Our list can be found on the website: > http://ifp-driver.sourceforge.net/ > > 7. Which flash players have "Manager" drivers for Linux and *BSD? > > The ifp-line and linux-filesystem drivers have been reported to work > with these models: iFP1xx, 3xx, 5xx, 7xx, 8xx, 9xx and N10. > > The T10, T30 serries appear to use the MTP protocol. Unfortunately, > MTP is a proprietary extension of teh PTP protocol, so it will have to > be reverse-engeniered. If you are interested in helping develop a > driver, please join the discussion on the mailing list. > > 8. Does Linux support iRiver's "UMS" firmware? > > Yes. The latest "USB Mass Storage" device drivers are known to work > with UMS firmware. Contact the linux-usb team if you have trouble > accessing the device. > > (In the past, the Linux USB drivers needed a small fix before they'd > work with iFP's UMS firmware.) > > 9. What settings should I use to encode Ogg Vorbis files? Or what does "ogg > format not supported" mean? > > Keep the bitrate between 96Kbps and 225Kbps. The oggenc flags for this > are "-m 96 -M 225". eg. > > $ oggenc -q3.0 -m 96 -M 225 somemusic.wav > > works well for me. If you want better quality, try -q5 or -q6. (For > more information about the "quality" setting, see > http://www.vorbis.com/faq.psp#quality . Personally, I've found -q3 to > be a reasonable size/quality tradeoff for portable music.) > > There seems to be more to the story. We've noted that: > > * The maximum bitrate varies with your model number. Newer models can > only handle 225Kbps, while iFP3xx and iFP5xx can [apparently] handle > as much as 360Kbps. > (Source: documentation for "The Ogg Bit Converter V1.1" on iRiver's > website.) > > * Some of us have noticed our players can handle files that temporarily > drop below 96Kbps. However, it seems important the average bitrate > be at least 96Kbps. > > * Samuel Sieb has tested his IFP-790 and found it didn't mind 27.Kbps > but couldn't sustain 314.7Kbps. > > 10. What is ifp-driver's relationship with iRiver and its parent company? > > At present, we [ifp-driver developers] have had no contact with iRiver. > > 11. I'm getting the compiler error "usb.h: No such file or directory"; how do I > fix it? > > Many projects discussed on this mailing list use "libusb" and need its > header files to compile properly. The easiest fix is to install the > packages "libusb-dev" and "libusb" distributed by your linux/bsd .. > err.. "vendor". Libusb's source can also be found here: > > http://libusb.sourceforge.net/ > > 12. What's the difference between ifp-line and libifp? > > The differences are historical. ifp-line was the first open source iFP > driver available: created by Pavel Kriz and maintained by Jun Yamshiro. > > libifp was developed later by Geoff Oakham (me!) as a general-purpose > library for accessing iFP devices. It includes a new version of > ifp-line which has ambitions of replacing its parent project. > Currently both projects co-exist happily. > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Ifp-driver-common mailing list > Ifp...@li... > https://lists.sourceforge.net/lists/listinfo/ifp-driver-common > -- Emily Brantley kon...@gm... PGP 0x94207793 |