00:00:00 --- log: started forth/03.08.16 00:10:04 nope, its only 5pm here ;) 00:10:32 my reality says it is exactly 3 am. 00:10:45 your reality is warped. you need to be reformed. 00:11:10 silly me. 00:11:22 re: reform. 00:49:39 Going to bed. 00:49:49 Morning 00:49:49 --- quit: kc5tja ("THX QSO ES 73 DE KC5TJA/6 CL ES QRT AR SK") 01:18:44 --- join: rk (~rk@ca-cmrilo-docsis-cmtsj-b-36.vnnyca.adelphia.net) joined #forth 01:27:17 --- quit: fridge (Read error: 60 (Operation timed out)) 02:01:08 --- join: rk_ (~rk@ca-cmrilo-docsis-cmtsj-b-36.vnnyca.adelphia.net) joined #forth 02:03:33 --- quit: rk (Read error: 104 (Connection reset by peer)) 02:19:44 --- part: gilbertdeb left #forth 02:49:36 --- join: a7r (~a7r@206.72.82.135) joined #forth 04:09:12 --- quit: a7r (Read error: 113 (No route to host)) 04:32:10 --- join: crc (~crc@ACA9EB3E.ipt.aol.com) joined #forth 04:41:38 --- join: rO| (~rO|@pD9545E82.dip.t-dialin.net) joined #forth 04:42:30 hi#. 04:44:46 --- quit: rO| (Client Quit) 04:45:14 --- join: rO| (~rO|@pD9545E82.dip.t-dialin.net) joined #forth 04:45:31 ok 04:46:48 so how are you doing today? 04:54:47 Hello r0| 04:55:19 hi crc :-) 04:57:13 crc, your visualforth idea will probably be on c4th ;-) 04:57:56 i find it more suitable, though less developed 04:59:04 c4th is colorforth? 04:59:21 y 04:59:40 Actually c4th is more developed than RetroForth 05:00:01 ok ;-) 05:00:09 Though the two can share some code due to similar internal designs :) 05:00:22 I've been looking at Map 05:01:49 It's a cool idea, but I'll have to try it before making any real judgments of it 05:02:42 map? 05:03:27 http://www.ynet.com.au/sean/map0.html 05:03:51 A 3d Forth that appears to draw off of ColorForth 05:04:00 enth! 05:04:13 It's different than enth 05:05:49 hmm 05:05:58 Map doesn't run as an OS and uses OpenGL + MySQL 05:06:09 looks like sean stole my idea 05:07:01 wow 05:07:10 thx 4 da news guys ;) 05:13:04 ok i'm not sad :-) crc, when you had a deeper look, plz tell me what you think ;-) 05:13:18 I will 05:13:35 do you know vrml? 05:13:53 Havn't touched it in two or three years... 05:14:18 That might be a decent format for rendering Forth visually though. 05:14:27 unfortunately it's a bit slow 05:14:34 True. 05:14:50 but these are the two poles to balance 05:15:53 compiling c4th out of visual xmltrees is nice 05:16:27 I'm just starting to do work with visual programming 05:17:41 you start getting lazy..? ;-) 05:17:58 No. 05:18:12 Always looking for a new programming challenge though 05:18:39 nm just kidding :-) 05:18:44 I know :) 05:21:12 brb 05:23:53 --- quit: crc ("I was using TinyIRC! Visit http://www.tinyirc.net/ for more information.") 05:27:34 wow 05:27:39 sean also uses rox 06:40:40 --- join: mur (murr@baana-62-165-184-194.phnet.fi) joined #forth 09:15:42 --- nick: rk_ -> rk 10:17:18 --- join: kc5tja (~kc5tja@ip68-8-127-122.sd.sd.cox.net) joined #forth 10:17:18 --- mode: ChanServ set +o kc5tja 10:55:13 --- quit: rk (Read error: 104 (Connection reset by peer)) 10:55:24 --- join: rk (~rk@ca-cmrilo-docsis-cmtsj-b-36.vnnyca.adelphia.net) joined #forth 11:00:02 --- join: wossname (wossname@HSE-QuebecCity-ppp81351.qc.sympatico.ca) joined #forth 12:43:42 --- join: XeF4 (xef4@lowfidelity.org) joined #forth 12:43:59 http://www.pelulamu.net/pwp/vic20/pwp-liberation.zip 12:44:11 http://www.pelulamu.net/pwp/vic20/pwp-liberation.ogg in case you haven't a real VIC-20 12:44:19 viznut++ 12:44:19 viznut++ 12:45:42 mad hax! 12:45:51 a new chippie 12:49:17 oh right, and http://www.pelulamu.net/pwp/ 12:50:37 undergr0und, eh? :) 12:50:49 i mean, c64 ok, but vic-20? my god 12:50:55 XeF4 12:51:06 mur 12:51:16 no tekstiviesti? 12:51:25 too busy :( 12:51:43 i said that if i have free time but i didn't :/ 12:51:52 *nod* 12:52:05 and i still dont have computer in helsinki 12:52:09 nor lights in roof 12:52:10 =( 12:52:18 neither mobile phone :) 12:52:25 school starts monday 12:52:46 urgh 12:53:38 now I'm stuck in Vaasa 12:54:29 how come? 12:54:41 would take too long to explain over this slow ssh link 12:55:25 sailing with Estelle and because everything is broken we had to stop here and now the captain has left 12:57:36 in principle I could go home, but I have no electricity there (which wouldn't be important exceept that I haveto code) 12:58:38 on second thought, this isn't really relevent to forth at all 13:00:11 oh you're sailing again 13:01:36 how do i get ChanServ to always be in a channel? 13:03:51 invite it 13:04:54 rk, ie. /msg chanserv help SET GUARD 13:06:58 XeF4: That song is . . . amazingly . . . 8-bit. :D 13:07:23 I'm so glad the Commodore 64 used the SID chip. :) 13:08:05 Frek: thanks 13:08:18 np 13:10:22 * Suzanne prefered the sound of the AY chips, in particular the SAA-1099 *duck and run* 13:10:58 Frankly, the Paula and Porsche chips are some of my favorites. 13:11:19 in fact, the games console i designed and built at college used an SAA 13:21:12 That is a weird sound chip. 13:21:47 the SAA-1099 ? 13:22:02 iirc, pretty much AY compatible, but organised as 3+1/channel or 6+2/mono 13:22:19 I have no idea what the AY is. 13:22:34 But the SAA-1099 looks pretty cool in one sense, and utterly underfeatured in another. :) 13:22:39 AY-3-8910/2/3/4 13:22:51 SoundBlaster fame, right? 13:22:53 no 13:23:16 you're thinking of the OPL, which while they had an AY specification (when yamaha still allowed second-sourcing) weren't the same series 13:23:46 the Yamaha versions of the AY series were used in the ST, Genesis/Megadrive and several 8bits 13:24:22 (well, the 8bits tended to use the AY version, but they were all pretty much the same) 13:24:32 Atari ST? It must have been embedded in a custom chip then; I don't recall seeing the SAA-1099 in its list of chipsets. :) 13:24:55 no, the ST used a YM version of the AY-3-891x series 13:25:23 the SAA-1099 was used in, umm, MSX2 ? i forget, it was a philips clone of the AY-3-891x series, but stereo 13:25:57 The other thing I notice is missing is waveform selection, and the envelope selections are really limited. :/ 13:25:57 i think the ST was a YM-2149 or something like that, same chip as the AY-3-8910 tho, really 13:26:33 Does the chip just use a square wave for output. 13:26:35 Does the chip just use a square wave for output? 13:26:42 sine, i think 13:27:28 its been like 14 years since i programmed a SAA-1099 :) 13:27:34 Heh 13:27:41 Well, it is a pretty KISS sound chip. 13:27:58 yeah, but you could get decent sound out of it with perseverance 13:28:32 the console i built at college had a 14bit DAC for samples mixed with the SAA-1099 tho 13:28:35 And a lot of CPU attention no doubt. :) 13:28:42 * kc5tja nods 13:28:44 not a whole lot 13:28:58 the usual trick was to reload registers on an interrupt 13:29:06 * kc5tja nods 13:29:26 if you had no choice, you used vblank (50Hz in this case - i was in the UK, remember) but 100Hz was better if you had a timer in your system 13:30:02 i seem to recall it being about 16 registers, so not a whole amount of CPU time to reload them 13:30:19 32 registers exist in the register map, but not all are used. 13:30:24 (assuming you used a prebuilt table of register sets to load) 13:30:37 21 registers total. 13:30:39 well, i'm talking mostly about the AY here, the SAA had similar tricks, but used double the register space 13:30:45 --- quit: wossname ("oh schische") 13:31:10 you could pretty much treat the SAA as two AY's in parallel 13:31:32 Did the original AY have 6 channels or only 3? 13:31:37 3+1 13:31:45 ie, 3 tone generators + a noise channel 13:31:45 I don't understand this +1 thing. 13:31:49 Ahhh gotcha. 13:31:58 So the SAA is totally register incompatible with the AY then. :) 13:32:18 * Suzanne screws up her face 13:32:24 it depends on how you look at it 13:32:29 the registers behaved the same way 13:32:37 but the register space was different 13:32:57 so yes, it was 'incompatible' but you could use the same principles 13:37:09 * kc5tja nods 13:38:43 Well, if I create my own computer, and I end up not using FPGAs for everything, then this chip is certainly a viable solution. 13:38:49 (for sound at least) 13:42:53 --- nick: kc5tja -> kc-shower 13:49:24 --- join: a7r (~a7r@206.72.82.135) joined #forth 13:53:29 --- quit: rk (Read error: 104 (Connection reset by peer)) 13:54:54 --- join: rk (~rk@ca-cmrilo-docsis-cmtsj-b-36.vnnyca.adelphia.net) joined #forth 14:00:28 --- nick: kc-shower -> kc5tja 14:35:34 --- quit: kc5tja ("[x]chat") 14:37:51 --- join: TheBlueWizard (TheBlueWiz@pc7edn1d.ppp.FCC.NET) joined #forth 14:37:51 --- mode: ChanServ set +o TheBlueWizard 14:37:57 hiya all 14:43:39 storm! BBL 14:44:52 ok 15:02:37 --- quit: Suzanne (Read error: 110 (Connection timed out)) 15:16:06 --- join: Suzanne (~suzanne@65-73-212-213.bras01.mdl.ny.frontiernet.net) joined #forth 15:53:20 gotta go...bye all! 15:53:44 --- part: TheBlueWizard left #forth 16:14:26 --- quit: Fractal (niven.freenode.net irc.freenode.net) 16:14:26 --- quit: a7r (niven.freenode.net irc.freenode.net) 16:14:26 --- quit: skylan (niven.freenode.net irc.freenode.net) 16:14:39 --- join: a7r (~a7r@206.72.82.135) joined #forth 16:14:39 --- join: skylan (sjh@vickesh01-4477.tbaytel.net) joined #forth 16:14:39 --- join: Fractal (bron@we.brute.forced.your.pgp.key.at.hcsw.org) joined #forth 16:18:39 --- join: SDO (~beos@co-trinidad1a-42.clspco.adelphia.net) joined #forth 16:23:42 --- quit: mur (Read error: 104 (Connection reset by peer)) 16:34:06 --- quit: SDO (Remote closed the connection) 16:36:52 --- join: SDO (~beos@co-trinidad1a-42.clspco.adelphia.net) joined #forth 16:37:07 --- join: jamc (~user@as3-6-8.asp.s.bonet.se) joined #forth 17:37:06 --- quit: a7r (Read error: 110 (Connection timed out)) 18:03:39 --- join: rO|_ (~rO|@pD9545E82.dip.t-dialin.net) joined #forth 18:04:18 --- quit: rO| (Read error: 104 (Connection reset by peer)) 18:27:56 --- join: a7r (~a7r@206.72.82.135) joined #forth 18:33:18 --- join: jaredj (~jaredj@user112.net362.fl.sprint-hsd.net) joined #forth 18:36:37 --- join: gilbertdeb (gilbert@fl-nken-u2-c3b-118.miamfl.adelphia.net) joined #forth 18:36:46 aloha 18:36:50 hello. :) 18:36:52 evening 18:37:10 hey suzanne. 18:37:17 threading? threaded? what? 18:37:21 how's your autocode doing your forth work ;) 18:37:33 gilbert, lol, dunno, haven't checked 18:37:43 gilbert, when it takes over the world or something, i figure i'll notice 18:37:46 jaredj Direct Threaded code, indirect threaded code. 18:37:51 Suzanne indeed ;) 18:37:57 (mine is 2nd ed.) 18:38:01 um - ? 18:38:11 jaredj its a way of writing the interpreter. 18:38:21 oh, ok 18:38:24 or the virtual machine. the inner forth. 18:38:54 i read about a real machine once 18:39:45 which one? 18:40:01 like one that ran forth. 18:40:15 javastation : java :: this thingy : forth 18:40:27 ah its VM is supposed to be similar. 18:41:10 * jaredj reads up on forth 18:42:14 there is quite a bit to read up on. 19:29:56 --- join: ree (~jwm@ns.fasthost.net) joined #forth 19:30:34 --- part: ree left #forth 19:33:40 --- quit: jamc ("Am I SHOPLIFTING?") 19:48:14 --- quit: a7r (Read error: 110 (Connection timed out)) 20:48:54 --- quit: jaredj (Read error: 104 (Connection reset by peer)) 20:49:03 --- join: jaredj_ (~jaredj@user112.net362.fl.sprint-hsd.net) joined #forth 21:26:00 --- join: kc5tja (~kc5tja@ip68-8-127-122.sd.sd.cox.net) joined #forth 21:26:00 --- mode: ChanServ set +o kc5tja 22:06:12 --- part: jaredj_ left #forth 22:12:07 --- quit: kc5tja ("[x]chat") 23:25:05 --- join: a7r (~a7r@206.72.82.135) joined #forth 23:59:59 --- log: ended forth/03.08.16