summaryrefslogtreecommitdiff
path: root/docs/FAQ
diff options
context:
space:
mode:
Diffstat (limited to 'docs/FAQ')
-rw-r--r--docs/FAQ37
1 files changed, 4 insertions, 33 deletions
diff --git a/docs/FAQ b/docs/FAQ
index d6517c5b90..36f80d2f48 100644
--- a/docs/FAQ
+++ b/docs/FAQ
@@ -394,43 +394,14 @@ A53: We have answered this question numerous times. It is mentioned in the
394 394
395Q54: Okay, I understand your 400 file limit. But why hardcode? Why not 395Q54: Okay, I understand your 400 file limit. But why hardcode? Why not
396 have this be dynamically allocated? 396 have this be dynamically allocated?
397A54: Because it's useless. Dynamic memory is only ever useful if you have 397A54: Newsflash! This limit is now configurable in the daily (post-2.0) builds.
398 memory consumers (tasks) that run at different points in time, and thus
399 can reuse the same memory for different purposes.
400
401 We don't have that. We must be able to show a big dir, index a big
402 playlist and play a big mp3 file, all at the same time. They cannot use
403 the same memory, and thus dynamic memory buys us nothing but extra
404 complexity. If we used dynamic memory for this, we would get all kinds
405 of odd bugs. Playlists that only got half-loaded if placed in certain
406 directories. Parts of the disk you couldn't go to if playing a certain
407 playlist etc.
408
409 We have a number of tasks that consume memory. They can all run at the
410 same time, using all of their allotted memory. Therefore it is much better
411 to allocate that memory to them beforehand and not pretend that anyone
412 else is able to use it. This is standard practice in memory-limited
413 systems.
414
415 Newsflash! This limit is now configurable in the daily (post-2.0) builds.
416 398
417Q55: Why is there a 10,000 song limit on playlists? 399Q55: Why is there a 10,000 song limit on playlists?
418A55: This is another hardcoded limit. We feel that as bigger disks arrive 400A55: Newsflash! This limit is now configurable in the daily (post-2.0) builds.
419 that this limit will increase. Because of the way that playlists are
420 stored, it tends to be a bit more malleable than the directory file limit.
421 For further detail, look at questions 53 and 54 and replace any instances
422 of '400' with '10,000'.
423
424 Newsflash! This limit is now configurable in the daily (post-2.0) builds.
425 401
426Q56: You don't understand! I _really_ need to have more then 400 files 402Q56: You don't understand! I _really_ need to have more then 400 files
427 in a directory! 403 in a directory!
428A56: The use of really big directories was a workaround for the poor playlist 404A56: Newsflash! This limit is now configurable in the daily (post-2.0) builds.
429 capabilities of the original Archos firmware. With Rockbox, you no longer
430 need this workaround. Organize your files in directories, then build
431 playlists for all collections you want to shuffle-play.
432
433 Newsflash! This limit is now configurable in the daily (post-2.0) builds.
434 405
435Q57: How can I make playlists on my PC? 406Q57: How can I make playlists on my PC?
436A57: There are many programs that can create .m3u playlists. WinAmp is one. 407A57: There are many programs that can create .m3u playlists. WinAmp is one.
@@ -739,7 +710,7 @@ A75: The same way you subscribed, but you send an 'unsubscribe' request to the
739 mail unsubscribe requests to the mailing list itself. That will only 710 mail unsubscribe requests to the mailing list itself. That will only
740 annoy more than 400 readers and will have no effect on your subscription. 711 annoy more than 400 readers and will have no effect on your subscription.
741 712
742 In fact, you NEVER unsuscribe to ANY mailing lists by mailing unsubscribe 713 In fact, you NEVER unsubscribe to ANY mailing lists by mailing unsubscribe
743 to the list's address. You might as well take the opportunity to learn 714 to the list's address. You might as well take the opportunity to learn
744 this right away. 715 this right away.
745 716