Known Issues: Difference between revisions

From kJams Wiki
Jump to navigation Jump to search
No edit summary
2F2A2043757272656E742056657273696F6E202864343229202A2F
Line 2: Line 2:
There are several bugs in the current release.  follow these guidelines to avoid some of them:
There are several bugs in the current release.  follow these guidelines to avoid some of them:


# crash during ripping and/or quicktime export, i know, i know.
# sometimes hang on quit.  Well, force quit for now.
# don't edit meta info while ripping or playing
# don't edit meta info while ripping or playing
# if you want to edit meta info after you rip or play, first STOP the song and clear your cache.  Note: Pause is NOT the same as Stop.  Use the Stop command from the Control menu, or press Escape or cmd-period (⌘-.)
# if you want to edit meta info after you rip or play, first STOP the song and clear your cache.  Note: Pause is NOT the same thing as stop, use the actual command in the Control menu
# <strike>if you're exporting quicktime, don't export more at once than the number of files you allow in the cache, minus one.  eg: if your cache allows 10 songs, only export up to 9 songs at a time with QT Export</strike> Fixed in d41a38
# '''&#191;Is this still an issue?''' a/v not synced: Touch the play head (this will re-sync the a/v)
# Users have reported hang on quit.  Well, force quit for now.
# <strike>Some slower machines exhibit stuttering and pops while songs are "unpacking", and un-synced a/v.  To work around this, for now, turn on the "Pause Between Tracks" preference, and keep the "Tasks" window open.  When a new song starts, it will be paused, but watch the tasks, wait for the song to complete it's "unpacking", there should be only one task left, the one about the ring buffer, and it will be paused (this is the one that feeds data to the speakers).</strike> This has been fixed in d41r39. 
# a/v not synced: Touch the play head (this will re-sync the a/v)
# There's also a mostly harmless assert about "main thread" or something, sorry, but ignore it.
# There's also a mostly harmless assert about "main thread" or something, sorry, but ignore it.



Revision as of 01:09, 1 April 2006

Current Version (d42)

There are several bugs in the current release. follow these guidelines to avoid some of them:

  1. crash during ripping and/or quicktime export, i know, i know.
  2. sometimes hang on quit. Well, force quit for now.
  3. don't edit meta info while ripping or playing
  4. if you want to edit meta info after you rip or play, first STOP the song and clear your cache. Note: Pause is NOT the same thing as stop, use the actual command in the Control menu
  5. ¿Is this still an issue? a/v not synced: Touch the play head (this will re-sync the a/v)
  6. There's also a mostly harmless assert about "main thread" or something, sorry, but ignore it.

You may still run into bugs or crashes. Please always file high quality bug reports, and learn how to manually send me your crash reports and log files.

General Issues

Corrupted zip files: this is common among songs that were compressed using winzip that you may find on the internet. they aren't technically all corrupt, tho some may actually be. most are compressed using a method that is NOT "deflate" (a typical codec that the ZIP format employs), and there is no software on the mac (stuffit, zlib, BOMArchiveHelper) that can decompress these non-deflate zip files. but move it on over to windows and it'll unzip fine, then re-zip it using zlib, you should be good to go. that's what that "make playlist of all bad zips" is eventually gonna be, you'll be able to gather them all in one place, move to windoze, re-compress them, move them back. that feature is not complete, the smart playlist doesn't really work yet. but it will! Click Here for some good tips!

Name Parsing: Read this so you know what I'm talking about. There are still bugs with that, especially around numbers. You may run into this when importing zip files, or when rebuilding your (previously working) library.

No Intel Macs: Currently not compatible, will be fixing this hopefully soon.