mirror of
https://github.com/mbirth/wiki.git
synced 2024-09-19 06:23:25 +01:00
Added more Sandisk Sansa posts.
This commit is contained in:
parent
431393ca54
commit
cad02febbc
@ -0,0 +1,68 @@
|
||||
---
|
||||
title: Feature Bits
|
||||
layout: default
|
||||
created: 2008-12-31 00:32:38 +0200
|
||||
updated: 2008-12-31 00:32:38 +0100
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- hardware
|
||||
- sandisk
|
||||
- sansa
|
||||
- fuze
|
||||
- features
|
||||
- hacking
|
||||
---
|
||||
The Sansa's have different features for different countries/regions. E.g. the Japanese radio frequencies ranging from 76 to 90 MHz
|
||||
are partly used for Police radio and thus it is not allowed to tune to these *forbidden* frequencies.
|
||||
|
||||
SanDisk achieved this by removing the **Japan** region from the Radio region selector. In European models of the FUZE you will
|
||||
only find "USA" and "World" as options in this setting.
|
||||
|
||||
Another example is the missing "Hebrew" language for "Arabic" regions and vice-versa.
|
||||
|
||||
Now the exciting part: If you download firmware files of the same version for different regions (e.g. from [daniel.haxx.se](http://daniel.haxx.se/sansa/v2fw.html))
|
||||
you'll notice that ALL firmware files have the same checksum. So how does the player decide which features to enable and which to leave disabled?
|
||||
|
||||
As the freaks of the [RockBox](http://rockbox.org/) team pointed out in their [forums](http://forums.rockbox.org/index.php?topic=14064.msg113302#msg113302),
|
||||
those feature bits are controlled by the **filename of the firmware file**.
|
||||
|
||||
The *Sansa Updater* of SanDisk seems to download a new firmware and put it into the root of the player named as `fuzp.bin`.
|
||||
This way the firmware gets updated without changing any feature-bit. An European player stays an European player.
|
||||
|
||||
BUT, if you name the file `fuzpA.bin`, the player will set the feature bits for the USA and thus the **Japan** radio region
|
||||
will become available. If you have the European version without FM radio, you might want to try naming the file `fuzpF.bin`
|
||||
to get the FM radio feature. From what I've read, it is only disabled by firmware with the hardware still built-in.
|
||||
|
||||
To get most of your player, you should name the firmware file `fuzpT.bin` so that all feature bits get set.
|
||||
|
||||
|
||||
Feature overview
|
||||
================
|
||||
|
||||
| | F1 | F2 | F3 | F4 | F5 | F6 | F7 | Region |
|
||||
|:------:|:----:|:----:|:----:|:----:|:------:|:----:|:----:|:---------------------|
|
||||
|A (`41`)| X | | | X | | X | | Americas / World |
|
||||
|E (`45`)| | | | X | | | | Europe (no FM radio) |
|
||||
|F (`46`)| X | | | X | | | | Europe |
|
||||
|G (`47`)| | X | | X | `15` | | | Israel (no FM radio) |
|
||||
|H (`48`)| X | X | | X | `15` | | | Israel |
|
||||
|M (`4d`)| | | X | X | `17` | | | Arabic (no FM radio) |
|
||||
|N (`4e`)| X | | X | X | `17` | | | Arabic |
|
||||
|P (`50`)| X | | | X | | X | | ? |
|
||||
|S (`53`)| | | | X | | X | | South America? (no FM) |
|
||||
|T (`54`)| X | X | X | X | | X | X | TEST mode firmware |
|
||||
|
||||
|
||||
**Description of the flags** (taken from the rockbox forums)
|
||||
|
||||
* **Flag 1:** By looking at the way it varies, I'd bet that this flag means whether the radio is enabled or not. This seems consistent with bclick's findings.
|
||||
* **Flag 2** is only 1 for H, G and the test firmware. bclick reported that, in the m300, H and G were Hebrew and Greek respectively.
|
||||
So maybe this is an "allow alternate font" flag or something of the sort. Or, maybe, an option which controls whether Greek/Hebrew are present as options in the language selection dialog.
|
||||
* **Flag 3** is only 1 for M, N and the test firmware. Same as above with "Arabic" (as bclick reported).
|
||||
* **Flag 4** is always 1, so there's no way of knowing what it means.
|
||||
* **Flag 5** is probably the default font/character encoding. I recall bclick reporting that, in the m300, M and N looked "like Arabic" (flag = 17),
|
||||
G Greek, and H Hebrew (both flag = 15). All others use the default font. The fact that this is the only flag that the test mode does not set is also worth noting.
|
||||
* **Flag 6:** I don't really know. Maybe whether the "high" volume option will appear on the menu?
|
||||
*mbirth: might be the "Japan" radio range*
|
||||
* **Flag 7** is (quite probably) whether the "test" option will appear on the menu or not. It is only 01 for T, the test firmware.
|
||||
@ -0,0 +1,25 @@
|
||||
---
|
||||
title: MTP mode
|
||||
layout: default
|
||||
created: 2008-12-31 00:56:58 +0200
|
||||
updated: 2008-12-31 00:56:58 +0100
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- hardware
|
||||
- sandisk
|
||||
- sansa
|
||||
- fuze
|
||||
- mtp
|
||||
---
|
||||
The Sansa differentiates between songs transferred via MTP mode and those transferred via MSC mode.
|
||||
The demo songs are all in the *MTP area* and thus you won't see them when looking at the device in MSC mode.
|
||||
|
||||
But it is possible, to mount the device in MTP mode also. You just have to install the packages [libmtp8](apt://libmtp8), [mtpfs](apt://mtpfs)
|
||||
and maybe [mtp-tools](apt://mtp-tools). Now connect your player in MTP mode and do a
|
||||
|
||||
mtpfs /mnt/sansa
|
||||
|
||||
(make sure, the directory `/mnt/sansa` exists before trying the mount command.)
|
||||
|
||||
Now you should have access to the MTP area of your Sansa where you can delete the demo songs or put new files in.
|
||||
@ -0,0 +1,43 @@
|
||||
---
|
||||
title: Rhythmbox and Sansa
|
||||
layout: default
|
||||
created: 2008-12-31 00:48:23 +0200
|
||||
updated: 2008-12-31 01:32:47 +0100
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- hardware
|
||||
- sandisk
|
||||
- sansa
|
||||
- fuze
|
||||
- rhythmbox
|
||||
---
|
||||
To work with the FUSE in Rhythmbox, you have two choices: **MTP** mode or **MSC** mode. The MTP mode is the *Media Transfer Protocol* which the
|
||||
Windows Media Player uses. There's a plugin for Rhythmbox which lets the player show up and you are able to manage the player from there.
|
||||
|
||||
The MSC mode is *Mass Storage Class* mode which brings up the player like any other USB stick or external harddrive. Rhythmbox won't
|
||||
recognize it as a player in this mode but you can force it by creating a file `.is_audio_player` in the root of your Sansa.
|
||||
|
||||
Make sure to put following contents into that file:
|
||||
|
||||
~~~
|
||||
audio_folders=MUSIC/,PODCASTS/,AUDIOBOOKS/
|
||||
output_formats=application/ogg,audio/mpeg,audio/flac,audio/x-ms-wma,audio/aac,audio/mp4,audio/audible
|
||||
input_formats=application/ogg,audio/mpeg,audio/flac,audio/x-ms-wma,audio/aac,audio/mp4,audio/audible
|
||||
folder_depth=1
|
||||
playlist_path=PLAYLISTS/%File
|
||||
playlist_format=audio/x-iriver-pla
|
||||
~~~
|
||||
|
||||
The `audio_folders` tells Rhythmbox where to put music files. Without that line all songs will be put under the root and thus the player won't recognize them.
|
||||
|
||||
The `output_formats` describes all formats the player can **create**, i.e. by the internal recording feature.
|
||||
|
||||
The `input_formats` describes all formats the player recognizes so that Rhythmbox can decide whether to transcode a file or not.
|
||||
|
||||
`folder_depth` influences the directory structure Rhythmbox creates. A `folder_depth` of **2** creates a `Artist/Album/Song.mp3` structure. A **1** creates a `Artist - Album/Song.mp3` (which is what I prefer) and, I guess, a **0** doesn't create any folder but just puts the files into the `MUSIC/` directory.
|
||||
|
||||
The `playlist_path` and `playlist_format` describe the location for playlists and what format the player supports. (I'm not sure whether the FUZE supports `audio/x-mpegurl` format.)
|
||||
|
||||
|
||||
The file `/usr/share/hal/fdi/information/10freedesktop/10-usb-music-players.fdi` lists the options usually set for FUZE players. Just search for the string "Fuze". But I guess the PnP-ID of the newer models isn't in that XML file.
|
||||
@ -0,0 +1,68 @@
|
||||
---
|
||||
title: Video format
|
||||
layout: default
|
||||
created: 2008-12-31 00:33:58 +0200
|
||||
updated: 2008-12-31 00:33:58 +0100
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- hardware
|
||||
- sandisk
|
||||
- sansa
|
||||
- fuze
|
||||
- video
|
||||
---
|
||||
The Sansa is very picky about what file to play and what not. The demo video has the following format:
|
||||
|
||||
~~~
|
||||
General #0
|
||||
Complete name : WAZ.MineToRemember.SansaPlayer.avi
|
||||
Format : AVI
|
||||
Format/Info : Audio Video Interleave
|
||||
Format/Family : RIFF
|
||||
File size : 20.0 MiB
|
||||
PlayTime : 3mn 26s
|
||||
Bit rate : 812 Kbps
|
||||
Writing application : InterVideo
|
||||
|
||||
Video #0
|
||||
Codec : DivX 5
|
||||
Codec/Family : MPEG-4
|
||||
Codec profile : Unknown
|
||||
Codec settings/Packe : No
|
||||
Codec settings/BVOP : Yes
|
||||
Codec settings/QPel : No
|
||||
Codec settings/GMC : 0
|
||||
Codec settings/Matri : Default
|
||||
PlayTime : 3mn 26s
|
||||
Bit rate : 667 Kbps
|
||||
Width : 224 pixels
|
||||
Height : 176 pixels
|
||||
Display Aspect ratio : 1.273
|
||||
Frame rate : 20.000 fps
|
||||
Resolution : 8 bits
|
||||
Interlacement : Progressive
|
||||
|
||||
Audio #0
|
||||
Codec : MPEG-1 Audio layer 3
|
||||
PlayTime : 3mn 26s
|
||||
Bit rate : 128 Kbps
|
||||
Bit rate mode : CBR
|
||||
Channel(s) : 2 channels
|
||||
Sampling rate : 44.1 KHz
|
||||
Resolution : 16 bits
|
||||
Writing library : Xing (new)
|
||||
~~~
|
||||
|
||||
|
||||
Encoding
|
||||
========
|
||||
|
||||
According to [this post](http://www.anythingbutipod.com/forum/showpost.php?p=307639&postcount=14) the
|
||||
[Any Video Converter](http://www.any-video-converter.com/products/for_video_free/) should be able to convert videos for the FUZE. The Settings are:
|
||||
|
||||
* AVI
|
||||
* 224x176 resolution
|
||||
* with Xvid or Divx5 codec
|
||||
* Video: 134kbps, 20fps
|
||||
* Audio: mp3, 128kbps, 2 channels, 44100khz
|
||||
@ -0,0 +1,51 @@
|
||||
---
|
||||
title: ID3 tagging & Album Art
|
||||
layout: default
|
||||
created: 2008-12-31 16:02:09 +0200
|
||||
updated: 2009-01-01 12:52:05 +0100
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- hardware
|
||||
- sandisk
|
||||
- sansa
|
||||
- fuze
|
||||
- id3
|
||||
- albumart
|
||||
- tagging
|
||||
---
|
||||
The FUZE does **<del>not</del>** (since firmware 1.2.26/2.2.26) support ID3v2.4. But it does support ID3v2.3 and as it appears not only in ISO-8859-1 encoding but also in UTF-16.
|
||||
|
||||
|
||||
Genres
|
||||
======
|
||||
|
||||
The FUZE seems to understand only a few Genres by ID which are listed in the firmware file:
|
||||
*Blues, Classic Rock, Country, Dance, Disco, Funk, Grunge, Hip-Hop, Jazz, Metal, New Age, Oldies, Other, Pop, R&B, Rap,
|
||||
Reggae, Rock, Techno, Industrial, Alternative, Ska, Death Metal, Pranks, Soundtrack, Euro-Techno, Ambient, Trip-Hop, Vocal,
|
||||
Jazz+Funk, Fusion, Trance, Classical, Instrumental, Acid, House, Game, Sound Clip, Gospel, Noise, AlternRock, Bass, Soul,
|
||||
Punk, Space, Meditative, Instrumental Pop, Instrumental Rock, Ethnic, Gothic, Darkwave, Techno-Industrial, Electronic,
|
||||
Pop-Folk, Eurodance, Dream, Southern Rock, Comedy, Cult, Gangsta, Top 40, Christian Rap, Pop/Funk, Jungle, Native American,
|
||||
Cabaret, New Wave, Psychadelic, Rave, Showtunes, Trailer, Lo-Fi, Tribal, Acid Punk, Acid Jazz, Polka, Retro, Musical,
|
||||
Rock & Roll, Hard Rock*
|
||||
|
||||
E.g. EasyTag writes `(127)` for "Drum & Bass". Since the FUZE doesn't know this ID, it get's listed as "Unknown".
|
||||
|
||||
But if you enter "Drum and Bass" as the Genre in EasyTag, it gets written as Plaintext and thus appears on the player.
|
||||
|
||||
|
||||
Album Art
|
||||
=========
|
||||
|
||||
while playing
|
||||
-------------
|
||||
|
||||
To show album art while playing, embed a JPEG-image of about 200x200 pixels and max. around 30 KiB. But these covers won't
|
||||
show up while browsing the album list. If there's a `folder.jpg`, the player will still show the embedded album art.
|
||||
If there's no embedded art but a `folder.jpg`, the latter will be shown.
|
||||
|
||||
|
||||
while browsing Albums
|
||||
---------------------
|
||||
|
||||
To make images appear there, put a file `folder.jpg` or `album art.jpg` in the folder of the specific album. (same constraints as for the embedded cover art)
|
||||
Loading…
Reference in New Issue
Block a user