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 2021-12-01

00:17:02 Quit kugel (Ping timeout: 256 seconds)
00:48:45 Quit braewoods (Quit: WeeChat 2.8)
00:52:44 Join braewoods [0] (~braewoods@user/braewoods)
01:00
01:05:18***Saving seen data "./dancer.seen"
02:00
02:13:09tertuthe v3s sounds pretty reasonable
02:48:30 Join ufdm__ [0] (~ufdm@c-73-164-63-214.hsd1.mn.comcast.net)
02:50:17 Quit ufdm__ (Client Quit)
02:50:58 Quit ufdm_ (Read error: Connection reset by peer)
03:00
03:00:10 Join ufdm [0] (~ufdm@c-73-164-63-214.hsd1.mn.comcast.net)
03:05:21***Saving seen data "./dancer.seen"
04:00
04:50:05 Quit Romster (Ping timeout: 252 seconds)
04:51:45 Join Romster [0] (~romster@user/romster)
05:00
05:05:25***Saving seen data "./dancer.seen"
06:00
06:34:33speachythe v3 is actually a better choice due to a smaller BGA package.
06:35:11speachybut yeah, the v3/v3s is pretty much ideal for our needs from a feature perspective.
06:35:38speachyits predecessors (fc100/fc200) are also pretty good, just not as much cpu oomph
06:36:04speachyand of course the various ingenic parts too.
06:38:25speachyfor a cheap-ish player all we'd need is the SoC, PMIC, and the pile of necessary passives.
06:39:24speachya more expensive (and capable) player would add an external audio codec (& amp if necessary)
06:39:45PaulFertserbtw, I had a rather odd discussion with pine64 community members
06:40:18speachycase, display, buttons, etc are about the same either way, though additional components need a larger case, all else being equal.
06:40:23PaulFertserThey were telling me they're sending "suggestions to the factory". There's no ECNs, no EE review, no anything. The magic factory somehow does the design and manufacture and everything.
06:40:51speachy"factory" is often an euphamism for the engineering team
06:41:28speachy(eg $dayjob's Xilinx sales/customer reps refer to their support/engineering staff as 'the factory')
06:41:53PaulFertserThey told me they talk to pine64-the-company but that company doesn't have EEs. So it's all like some magic.
06:42:42speachyPerhaps Pine64 contracts out the actual design work to external contractors
06:42:50speachypretty common
06:43:06speachyobviously manufacturing is external too
06:43:15PaulFertserAll in all it's all apparently rather obscure to the community.
06:46:44PaulFertserSo my idea about collaborating with them on creating a real life design seems to be absolutely out of place.
07:00
07:03:54speachyno, it's not a bad idea; we've actually gone back and forth with them at least twice
07:04:46speachyit's just that what they've propsoed doesn't really map well with what we want.
07:05:28***No seen item changed, no save performed.
07:07:03speachythe proposal from round one was essentially the pinephone minus the phone part; analagous to what apple did with the ipod touch
07:07:44speachyround two was a hardware platform that was essentially a high-end bluetooth chipset (meant for noise-canceling headphones)
07:08:18speachywhich went too far in the other direction; ie half the RAM we'd need to still be recognizable as rockbox
07:09:02speachythere's no shortage of primarily-touch DAPs out there; that's what most high-end units out of China are these days.
07:09:50speachyand on the other end, having to kneecap our feature set wouldn't really result in something our userbase would want (vs just buying secondhand ipods or whatever)
07:10:54speachyin my mind, a "rockbox-branded" DAP needs to be operable entirely without looking at it, which means it can't rely on a touchscreen for primary interaction.
07:11:51speachythat way it can continue to utilize the one true killer feature we have over the rest of the market (to this day) −− accessibility.
07:32:53 Quit Romster (Ping timeout: 252 seconds)
07:34:03 Join Romster [0] (~romster@user/romster)
08:00
08:08:05LongclawThe proliferation of touchscreen DAPs has always confused me a bit, a touchscreen means bulk and it means you always have to look at the screen to do anything
08:09:12LongclawI guess it must sell, I can't suppose there'd be so many if they didn't
08:54:28paulcarrotyI love pine folks, they aren't so super successfull but still pushing open source producs
08:55:31atsI've occasionally wondered if Olimex could be persuaded into doing a Rockbox device - they have design experience with lots of embedded CPUs and seem to have figured out how to sell affordable dev boards...
09:00
09:02:15sporkfeels like finding some OEM with capable complete music player, putting rockbox on it and rebranding it seems more feasible
09:03:14sporksimilar how all those aigo eros q/k devices are cloned
09:05:30***Saving seen data "./dancer.seen"
09:05:48sporkperhaps a little less fancy example than that though
09:45:17 Join massiveH [0] (~massiveH@ool-4a5862ee.dyn.optonline.net)
10:00
10:51:08 Quit massiveH (Quit: Leaving)
11:00
11:05:31***Saving seen data "./dancer.seen"
12:00
12:06:23tertuyeah i was going to say
12:10:54speachyspork: that would be ideal. The closest we've come is the AGPTek Rocker, but even that was little more than a few players tossed over the wall to us.
12:12:10speachyLongclaw: they're cheap to make, and obviously they sell in their target markets. Though I just don't really see the value proposition over, say, a typical smartphone.
12:12:46speachy(well, aside from the oxygen depleted gold plated optical connector audiophile market)
12:13:21Longclawgold plated fibre optics, for superior sound!
12:15:34speachyplaying over bluetooth
12:16:14speachyLongclaw: they do think they can monetize the player via "apps" and streaming services
12:49:58tertui mean i think like, my dad is a reasonable target market
12:51:03tertuwell i guess you could use a smartphone for that too but then you have to deal with all the nonsense smartphones do
12:51:16tertulike randomly killing apps for no apparent reason
12:52:01tertu(i mean for me it's mostly that i like the way rockbox works at this point)
13:00
13:05:34***No seen item changed, no save performed.
13:10:25 Join ZincAlloy [0] (~Adium@2a02:8108:943f:d824:8c6f:573:a:1f03)
13:31:21 Quit michaelni (Ping timeout: 250 seconds)
13:36:53 Join petur [0] (~petur@78-21-55-218.access.telenet.be)
13:37:02 Join michaelni [0] (~michael@213-47-68-29.cable.dynamic.surfer.at)
13:41:23 Quit michaelni (Ping timeout: 252 seconds)
13:42:14 Join michaelni [0] (~michael@213-47-68-29.cable.dynamic.surfer.at)
13:43:14 Join lebellium [0] (~lebellium@2a01cb04012c0900711120efbaadbc7c.ipv6.abo.wanadoo.fr)
14:00
14:18:18 Join cockroach [0] (~blattodea@user/cockroach)
15:00
15:05:37***Saving seen data "./dancer.seen"
16:00
16:28:48 Join kugel [0] (~kugel@ip5f59a293.dynamic.kabel-deutschland.de)
17:00
17:05:40***No seen item changed, no save performed.
17:20:02 Quit _bilgus (Remote host closed the connection)
17:22:06 Join _bilgus [0] (~bilgus@162.154.213.134)
17:36:17 Quit cockroach (Quit: leaving)
17:43:10 Quit amiconn (Read error: Connection reset by peer)
17:43:42 Join amiconn [0] (jens@p200300ea871de700305e95fffec66ff3.dip0.t-ipconnect.de)
17:54:50 Join advcomp2019 [0] (~advcomp20@user/advcomp2019)
17:57:51 Quit advcomp2019__ (Ping timeout: 256 seconds)
18:00
18:10:52 Quit lebellium (Quit: Leaving)
18:27:59 Quit petur (Quit: Leaving)
18:29:14 Quit _bilgus (Remote host closed the connection)
18:31:07 Join _bilgus [0] (~bilgus@162.154.213.134)
18:51:56 Quit ZincAlloy (Quit: Leaving.)
19:00
19:05:41***Saving seen data "./dancer.seen"
21:00
21:05:43***No seen item changed, no save performed.
22:00
22:49:15 Quit amiconn (Read error: Connection reset by peer)
22:49:28 Join amiconn [0] (jens@p200300ea871de700305e95fffec66ff3.dip0.t-ipconnect.de)
23:00
23:05:47***Saving seen data "./dancer.seen"

Previous day | Next day