EDIT: actually i do see a few problems. the bar charts aren't scaled properly all the time. but the behaviour is pretty random.

EDIT: actually i do see a few problems. the bar charts aren't scaled properly all the time. but the behaviour is pretty random.

is this normal scale? strange behavior: same scale from 163 to 365 or from 1 to 4.

Edit: if you display a chart like above in a narrow panel it can happen, that the placount numbers disappear (depending on width of the string).
the multiplication ensures that there is enough space even if there are big jumps between PC
that was the reason

all my files are already tagged with LAST_PLAYED FIRST_PLAYED PLAY_COUNTER etc.
is there a way to use those tags, instead of another database?

var offset = 0; //this variable should be added to the y co-ordinate of every text/image/draw element in on_paint

function on_size() {
  ww = window.width;
  wh = window.height;
  offset = 0; //need to reset position when panel is resized
}

function on_paint(gr) {
  gr.drawWhatever(x, y + offset,...........
}

function on_mouse_wheel(delta) {
  offset += -delta;
}

offset += -delta * 15; //15 pixels

yes this is normal - last.fm behave the same way:

Quote from: muzack on

yes this is normal - last.fm behave the same way:

just because they're doing it wrong doesn't mean it's normal. i don't even know how to make it that wrong. doing it right is considerably easier.

@novembre sorry no way to import. because the play_stamp reflect just one date (first/last listen/added/ date - and there is no timeline)
My custom playcount is a local "alternative" to last.fm and track each play with all need (and more) parameters to display a graph...

2009-01-21 19:22:47; 2009-10-10 14:41:51; 2009-12-01 22:59:14; 2010-04-10 14:08:25; 2010-05-06 13:19:50

Quote from: muzack on 2010-07-10 07:51:31

@novembre sorry no way to import. because the play_stamp reflect just one date (first/last listen/added/ date - and there is no timeline)
My custom playcount is a local "alternative" to last.fm and track each play with all need (and more) parameters to display a graph...

Sorry, I should have been more precise in the previous post. PLAY_STAMP tag is created by foo_playback_custom and it has the date/time of every play like this:

Code: [Select]

2009-01-21 19:22:47; 2009-10-10 14:41:51; 2009-12-01 22:59:14; 2010-04-10 14:08:25; 2010-05-06 13:19:50

What about in this case?

$if(%FINGERPRINT_FOOID%,$crc32(%FINGERPRINT_FOOID%),$crc32($lower([%artist%][%album%][%title%])))|[%artist%]|[%album%]|[%title%]|$if(%FOO_ARTIST_ID%,%FOO_ARTIST_ID%,$crc32($lower([%artist%])))|$if(%FOO_ALBUM_ID%,%FOO_ALBUM_ID%,$crc32($lower([%album%])))|
%play_count%|%first_played%|%last_played%|[%PLAY_STAMP%]

$csv = "1234|artist|album...";
// transform csv to array
/*
$csvArr[0]['trackid'] = "1234";
...
$csvArr[0]['play_stamp'] = "date1,date2,date3";
$csvArr[1]['trackid'] = "3456";
...
$csvArr[1]['play_stamp'] = "date1,date2,date3";
*/

// loop over array 
foreach($csvArr as $key => $value)
{
  $playstampArr = explode(",",$csvArr[$key][play_stamp]);
  foreach($playstampArr as $k => $v){
// build correct SQL statement with (name/value pairs)
   $sql[] = "INSERT OR REPLACE INTO playcount(trackid,artist,album...playtime) VALUES (".$csvArr[$key][trackid].",'".$csvArr[$key][artist]."','".$csvArr[$key][album]."','".$v."')"; // $v is the playdate value
}
}

echo implode("\n",$sql);

Awesome! 
Got it working with no SQL or PHP knowledge, I used foo_text_tools, a text editor, a spreadsheet and Firefox SQLite Manager extension. Thanks for the hints, muzack!

It seems fast (less than 1 sec even with artists with over 1K plays) but I've only tested it on a quad-core, tomorrow I'll try on a slower dual-core.
Two things I've noticed, maybe due to an imperfect import:
1) sometimes the graph doesn't reach the full height indicated by the background gray lines, i.e. the max play count per day is 30 and the graph stays in the bottom half of the window because the gray line it's at 97 plays
2) with date range set to overall, the graph always starts at the first played date ever in the database (in my case 26/02/2008) , maybe you could add the possibility to switch from this "global" overall to a "relative" overall, in which the graphs starts from the first played (or added) date of the artist/track/album