diff options
author | Robert Hak <adiamas@rockbox.org> | 2002-08-27 13:50:00 +0000 |
---|---|---|
committer | Robert Hak <adiamas@rockbox.org> | 2002-08-27 13:50:00 +0000 |
commit | 5d3a0d3a93c40cfd4b9e44a633b10c7b1b269d23 (patch) | |
tree | 5db6f3198779652d964db6b9f0294fbb5cc080f6 /docs | |
parent | 758e8799940b2f7a67f8474254ac9a3b0224078d (diff) | |
download | rockbox-5d3a0d3a93c40cfd4b9e44a633b10c7b1b269d23.tar.gz rockbox-5d3a0d3a93c40cfd4b9e44a633b10c7b1b269d23.zip |
added id3v1/2 question
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@2004 a1c6a512-1295-4272-9138-f99709370657
Diffstat (limited to 'docs')
-rw-r--r-- | docs/FAQ | 22 |
1 files changed, 22 insertions, 0 deletions
@@ -312,3 +312,25 @@ A40: The display on the Players is character cell and not bitmap based. | |||
312 | This means we can only control what characters get displayed, not | 312 | This means we can only control what characters get displayed, not |
313 | what pixels are shown. This makes the prospect of game play very | 313 | what pixels are shown. This makes the prospect of game play very |
314 | slim (at least for anything involving graphics). | 314 | slim (at least for anything involving graphics). |
315 | |||
316 | Q41: When recording is finally implimented in Rockbox, will it be possible to | ||
317 | use custom codecs (like LAME) or is there a built in codec in the Archos? | ||
318 | A41: The MP3 encoder is in the MAS3587F chip, and nothing we can change. | ||
319 | |||
320 | Q42: What are the max/min bitrates for recording on the Recorder's encoder? | ||
321 | A42: The builtin encoder is variable bit rate only with a max of 192kbit/s, | ||
322 | and a min of 32kbit/s. | ||
323 | |||
324 | Q43: I have a question about the id3v1 and id3v2 tags... | ||
325 | A43: Stop! Here is all the information about that (if you still have | ||
326 | questions when done, ask then.) | ||
327 | |||
328 | 1. Rockbox supports both id3v1 and id3v2 | ||
329 | 2. The id3v2 support is limited to the first 300 bytes of the file. Some | ||
330 | ripper programs tend to add very big tags first and then the important | ||
331 | ones Rockbox wants to read end up beyond the first 300 bytes and then | ||
332 | they remain unknown. | ||
333 | 3. If you believe that the tags you don't see *are* within 300 bytes, then | ||
334 | please make the mp3 file available for one of the developers to try | ||
335 | out. | ||
336 | 4. The 300-byte limit is subject to be removed in a future version | ||