00:00:00 --- log: started forth/20.01.11 00:33:36 --- join: Labu joined #forth 00:34:25 --- quit: jn__ (Ping timeout: 240 seconds) 00:34:51 --- join: jn__ joined #forth 01:08:14 --- join: gravicappa joined #forth 01:32:46 --- join: crab1 joined #forth 01:44:52 --- join: dys joined #forth 01:59:16 --- quit: smokeink (Remote host closed the connection) 02:00:55 --- join: smokeink joined #forth 02:00:58 --- quit: smokeink (Remote host closed the connection) 03:25:18 --- join: dddddd joined #forth 03:44:53 --- join: dave0 joined #forth 03:55:17 A happy dappy weekend to you all, forth Wizards 05:45:33 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in) 06:44:28 --- quit: proteusguy (Remote host closed the connection) 06:45:25 --- join: proteusguy joined #forth 06:45:25 --- mode: ChanServ set +v proteusguy 08:51:49 --- join: X-Scale` joined #forth 08:53:35 --- quit: X-Scale (Ping timeout: 260 seconds) 08:53:36 --- nick: X-Scale` -> X-Scale 09:27:06 --- quit: gravicappa (Read error: Connection reset by peer) 09:31:26 --- join: gravicappa joined #forth 09:36:03 --- quit: dave0 (Quit: dave's not here) 10:31:20 --- quit: dys (Ping timeout: 258 seconds) 10:55:13 --- quit: Keshl (Ping timeout: 240 seconds) 10:55:33 --- join: Keshl joined #forth 11:18:41 --- quit: jedb_ (Remote host closed the connection) 11:18:51 --- quit: xek__ (Remote host closed the connection) 11:22:07 --- join: jedb__ joined #forth 11:22:08 --- join: xek_ joined #forth 11:32:19 --- join: X-Scale` joined #forth 11:33:12 --- quit: X-Scale (Ping timeout: 268 seconds) 11:33:13 --- nick: X-Scale` -> X-Scale 11:58:20 --- join: dys joined #forth 13:44:59 --- quit: gravicappa (Ping timeout: 260 seconds) 14:21:31 --- join: ryke joined #forth 14:39:10 --- join: WickedShell joined #forth 16:02:58 --- quit: Labu (Ping timeout: 265 seconds) 16:08:40 --- quit: crab1 (Ping timeout: 258 seconds) 16:33:52 --- join: dave0 joined #forth 17:43:47 --- join: Tony_Sidaway joined #forth 17:46:18 --- quit: WickedShell (Remote host closed the connection) 17:48:03 Looks like my instincts were right about Eurorack. The difference between the component costs and the finished module are often obscene, rails are unnecessary and if you're going to DIY you're better off building a bigger format. Eurorack patch cables and knobs are too small and delicate. 17:49:27 This fellow is pretty good: https://www.lookmumnocomputer.com/modular 17:52:04 I spent a couple of days in the Eurorack section of a popular analogue modular forum called Muff Wigglers. It was full of people collecting modules and showing them off. That is, posting photographs of the hardware. I even saw one poster being told off for posting a SoundCloud file! 17:54:05 If you have 18 synth modules maybe you're not really that into music. 17:54:41 Or electronics (unless you built them all yourself). 17:57:37 --- join: iyzsong joined #forth 17:58:31 So for now I'm considering just aiming at bigger cabinets, wooden rails and proper big patch cables like The Lord Bob Moog ordained. 18:01:49 Couldn't sleep last night (I care for an autistic adult relative) so I had this really long creative streak, designing a microcontroller-driven patch matrix to facilitate (among other things) rapid patch switching in live performance. 18:03:19 The main problem is accommodating all the patch cables. Once you have them plugged in, modern analogue mux technology takes care of the patching. 18:04:09 I got the idea from the old VCS3's patch matrix. 18:04:19 --- join: crab1 joined #forth 18:05:38 Obviously at this level my work on porting Retro (if I ever get it done) could be handy. 18:06:21 But to be fair, an Arduino sketch would be enough for this job. 18:11:51 The touch screen interface for this project is an item that sells for £8. The clever chip that does the multiplexing is about five times more expensive. There are also quite a lot of op amps for signal conditioning, but the main problem is finding a way to shoehorn as many as 32 patch sockets into the front panel, while keeping a clear visual relationship with the touch screen. 18:13:15 Maybe a scaled down version would still be useful. I'm tempted to go for 16x16 matrix, though, if only because that was the format used by the VCS3 18:14:06 https://en.wikipedia.org/wiki/EMS_VCS_3 18:18:11 To fit 32 patch sockets vertically into Eurorack you'd have to arrange them as two staggered rows. Similar limitation applies to larger formats that use the big jacks. 18:22:43 Because, ironically, in order to make a subset of your module inputs and outputs available to the patch matrix, you must first patch them into the patch matrix module. Basically you're trading setup time in the pre-performance period for ease of switching during performance. 18:26:03 I could provide a kind of backplane, but that would go against the modular principle. 18:26:16 --- quit: Tony_Sidaway (Quit: Tony_Sidaway) 18:56:23 --- join: smokeink joined #forth 20:09:05 --- quit: dddddd (Ping timeout: 260 seconds) 20:26:46 --- join: gravicappa joined #forth 20:33:57 --- join: jedb_ joined #forth 20:36:25 --- quit: jedb__ (Ping timeout: 240 seconds) 20:36:30 --- quit: mstevens (Ping timeout: 245 seconds) 20:37:20 --- quit: rann (Ping timeout: 245 seconds) 20:41:41 --- quit: jedb_ (Remote host closed the connection) 20:42:35 --- join: rann joined #forth 20:44:32 --- join: jedb joined #forth 20:45:11 --- join: Blue_flame joined #forth 20:49:00 --- join: mstevens joined #forth 21:47:20 crc, I'm getting the "ERROR (nga/file_get_size): Invalid file handle" in http://forth.works/examples/ which you said is a result of your recent server issues 22:08:49 --- quit: proteus-guy (Ping timeout: 240 seconds) 22:09:36 --- join: proteus-guy joined #forth 22:18:20 --- join: Green_flame joined #forth 22:19:58 --- join: Red_lizzard joined #forth 22:20:34 --- quit: Red_lizzard (Client Quit) 22:20:42 --- quit: Blue_flame (Ping timeout: 248 seconds) 22:23:16 tpbsd: if you refresh it should work again 22:23:34 --- quit: Green_flame (Ping timeout: 260 seconds) 22:24:33 crc, fixed~! 22:24:38 :) 22:24:55 crc, thank you sir! 22:26:20 crc, I should have had a good look at retro long go if only because youre the *only* other Forth Fossil user I've met online 22:29:51 kc5tja also uses fossil for his kestrel project: http://chiselapp.com/user/kc5tja/repository/kestrel-3/index 22:30:13 http://chiselapp.com/user/kc5tja/repository/kestrel-3/dir?ci=02c01ec8d4bb1010&name=firmware/dxforth/src 22:31:58 i recognise a fossil UI when I see one :) 22:39:01 crc, are you using the kestrel system ? 22:40:26 not currently, though I plan to do a riscv implementation to run on it the some point 22:41:24 it's quite interesting, tho I used slow computers from that era and dont wish to relive it myself 22:42:04 I only seek full control over small embedded machines in my designs, I don't really care whats in my PC as long as it's fast and does what I want 23:01:24 --- quit: ryke (Ping timeout: 268 seconds) 23:27:38 20 2 $1FFFF7E0 memstats 23:27:38 Memory stats in bytes: 23:27:38 Total Flash:131072 Free:27336 Used:103736 23:27:38 Total Ram:20480 Free:18824 Used:1656 23:27:38 ok. 23:28:10 finally refactored the worlds worst cortex-m forth memstats utility 23:54:37 --- quit: dys (Ping timeout: 268 seconds) 23:59:59 --- log: ended forth/20.01.11