Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

Click in the nick column to highlight everything a person has said.
The Logo icon identifies that the person is a core developer (has commit access).

#rockbox log for 2023-10-31

00:01:09 Join jacobk [0] (
00:21:35 Quit jacobk (Ping timeout: 240 seconds)
00:37:17 Quit m01 (Quit: Konversation terminated.)
00:40:06 Join m01 [0] (
00:44:42 Join Jinx [0] (~Jinx@user/jinx)
00:48:11 Join jacobk [0] (~quassel@
01:03:40 Quit jacobk (Ping timeout: 248 seconds)
01:05:49 Join jacobk [0] (~quassel@
01:09:19 Quit jacobk (Excess Flood)
01:09:42 Join jacobk [0] (~quassel@
01:09:53***Saving seen data "./dancer.seen"
01:50:35 Quit jacobk (Ping timeout: 240 seconds)
02:32:26 Join jacobk [0] (~quassel@
03:08:46sporkspeachy: on the main rockbox page, below the latest commits, there is still a link to the rockboxcommits twitter
03:09:57***Saving seen data "./dancer.seen"
04:44:22 Join sch [0] (
04:54:04 Nick gevaerts_ is now known as gevaerts (~fg@user/gevaerts)
05:10:00***No seen item changed, no save performed.
05:42:56 Quit CH23_M (Ping timeout: 255 seconds)
05:43:10 Join CH23_M [0] (~CH23@revspace/participant/ch23)
06:47:25 Quit Moriar (Ping timeout: 255 seconds)
07:10:01***Saving seen data "./dancer.seen"
07:12:55 Quit sch (Ping timeout: 264 seconds)
07:20:28 Join sch [0] (
08:08:21 Quit baltazar (Ping timeout: 260 seconds)
08:10:00 Join baltazar [0] (
08:29:03 Quit bertrik (Remote host closed the connection)
08:53:08speachyspork: thanks! fixed.
09:10:04***Saving seen data "./dancer.seen"
09:24:55 Quit sch (Ping timeout: 264 seconds)
09:47:58 Quit TorC (Ping timeout: 252 seconds)
10:42:47 Join TorC [0] (~Tor@fsf/member/TorC)
10:51:10 Join othello7 [0] (
11:10:07***Saving seen data "./dancer.seen"
11:19:44 Quit jacobk (Ping timeout: 272 seconds)
11:43:45 Join jacobk [0] (
11:48:42 Join zem [0] (
11:50:16 Quit hactar|ant (Ping timeout: 255 seconds)
11:58:22 Quit zem (Ping timeout: 255 seconds)
11:58:54 Join zem [0] (
12:06:48 Join XiaomiRedmi [0] (~XiaomiRed@2402:9d80:310:edb7:5232:9557:f67:4859)
12:07:01 Quit XiaomiRedmi (Client Quit)
12:09:08 Quit jacobk (Ping timeout: 272 seconds)
12:40:10rb-bluebotBuild Server message: New build round started. Revision f377ad3ce7, 304 builds, 9 clients.
12:40:11rb-bluebotRestore clearing resume info for current track in playing_id3_sync by roman.artiukhin
12:49:39rb-bluebotBuild Server message: Build round completed after 570 seconds.
12:49:41rb-bluebotBuild Server message: Revision f377ad3ce7 result: All green
12:49:45rb-bluebotBuild Server message: New build round started. Revision 9c79a4449a, 304 builds, 9 clients.
12:49:45rb-bluebotPlaylist Viewer Track Info: Fix displayed index by Christian Soffke
12:59:38rb-bluebotBuild Server message: Build round completed after 594 seconds.
12:59:40rb-bluebotBuild Server message: Revision 9c79a4449a result: All green
12:59:44rb-bluebotBuild Server message: New build round started. Revision ba62798746, 304 builds, 9 clients.
12:59:44rb-bluebotPlaying Time plugin: Fix calculation for shuffled playlists by Christian Soffke
13:10:09***Saving seen data "./dancer.seen"
13:14:00rb-bluebotBuild Server message: Build round completed after 858 seconds.
13:14:02rb-bluebotBuild Server message: Revision ba62798746 result: All green
13:26:11 Join bertrik [0] (~bertrik@revspace/participant/bertrik)
14:05:59 Join jacobk [0] (~quassel@
14:10:28rb-bluebotBuild Server message: New build round started. Revision 11b8336c64, 304 builds, 9 clients.
14:10:28rb-bluebotFix rewind on resume is applied for skip length across tracks action after auto frequency switch by roman.artiukhin
14:13:42 Join lebellium [0] (
14:27:53rb-bluebotBuild Server message: Build round completed after 1047 seconds.
14:27:54rb-bluebotBuild Server message: Revision 11b8336c64 result: All green
15:03:08 Quit jacobk (Ping timeout: 248 seconds)
15:10:12***Saving seen data "./dancer.seen"
15:19:18 Quit CH23_M (Read error: Connection reset by peer)
15:19:38 Join CH23_M [0] (~CH23@revspace/participant/ch23)
16:05:31 Join jacobk [0] (
16:51:54speachyBTW, I trolled ebay a bit over the weekend and should be getting one of those sony radios with an ipod dock, in response to those bug reports about the dock controls not working
16:57:16 Quit jacobk (Ping timeout: 248 seconds)
16:58:33 Join CH23 [0] (~CH23@revspace/participant/ch23)
17:03:13 Join jacobk [0] (~quassel@
17:10:16***Saving seen data "./dancer.seen"
18:16:35 Quit jacobk (Ping timeout: 240 seconds)
18:17:43 Join jacobk [0] (~quassel@
18:27:52 Quit jacobk (Ping timeout: 272 seconds)
18:51:35 Quit lebellium (Quit: Leaving)
18:55:10 Join Moriar [0] (
18:59:05 Quit CH23 (Read error: Connection reset by peer)
19:10:20***Saving seen data "./dancer.seen"
19:29:31_bilgus_anyone notice long delays (8-10s best case) (15-30s worst case) when using start screen: Resume Playback but much shorter load times when you start to main menu and resume playback manually?
19:30:48_bilgus_I can get to the WPS with a song playing in < 4 seconds manually yet it takes at usually 9 doing it on auto at start-up
19:31:18_bilgus_I even made a plugin to start on start-up and it gets me to the WPS in <7s
19:32:30_bilgus_maybe something to do with thread_wait() causing some issue IDK
19:36:14_bilgus_nope nevermind the plugin is just as slow with a large playlist
19:36:44_bilgus_wonder why the difference between manually and auto though
19:37:07_bilgus_mind you those time include boot up
19:54:21_bilgus_boosting the cpu helped odd though considering the dircache should be boosting too
19:57:51_bilgus_ g#5454
19:57:54rb-bluebotGerrit review #5454 at : boost cpu when resuming playlists by William Wilgus
19:58:18 Join chris_s [0] (
20:13:59 Join massiveH [0] (~massiveH@2600:4040:a982:c800:27f2:68af:c6b:c898)
20:19:03 Quit chris_s ()
20:19:18 Join chris_s [0] (
20:19:33chris_sChecking the official build, I’m not sure I can reproduce a difference between using the “Start Screen” setting or resuming manually.
20:19:41chris_sSomewhat related though, speaking of the dircache:
20:19:46chris_sIs still needed?
20:19:50chris_sI seem to remember we talked about that at some point, and my understanding of the dircache is probably too limited.
20:19:56chris_sBut I haven’t noticed any obvious situation where removing dircache_wait seemed to hurt after only ever running a build without it for more than a year.
20:20:01chris_sIn my case, It’s about 3x slower to get to the WPS if the dircache has to be loaded first. Would be nice if that waiting time could be eliminated for everybody…
20:36:38 Quit chris_s ()
20:55:53 Join chris_s [0] (
20:57:45chris_shaving said that, I haven't really tried to battle-test it, maybe just got lucky
21:02:15 Quit chris_s ()
21:10:21***Saving seen data "./dancer.seen"
22:11:04_bilgus_i'd be very reticent to remove that till I stop seeing >45s resumes because the player truly feels locked up
22:12:01_bilgus_it starts becoming apparent around 10000 song playlists
22:14:16 Join jacobk [0] (
22:16:56 Quit massiveH (Quit: Leaving)
23:10:08 Quit Moriar (Ping timeout: 258 seconds)
23:10:24***Saving seen data "./dancer.seen"
23:44:06 Quit jacobk (Ping timeout: 255 seconds)
23:58:27 Join jacobk [0] (

Previous day | Next day