Forum comments in chronological order
Disclaimer: I am not responsible for what people (other than myself) write in the forums. Please report any abuse, such as insults, slander, spam and illegal material, and I will take appropriate actions. Don't feed the trolls.
Jag tar inget ansvar för det som skrivs i forumet, förutom mina egna inlägg. Vänligen rapportera alla inlägg som bryter mot reglerna, så ska jag se vad jag kan göra. Som regelbrott räknas till exempel förolämpningar, förtal, spam och olagligt material. Mata inte trålarna.
- Jun 2007
- Aug 2007
- Oct 2007
- Nov 2007
- Dec 2007
- Jan 2008
- Feb 2008
- Mar 2008
- Apr 2008
- May 2008
- Jun 2008
- Jul 2008
- Aug 2008
- Sep 2008
- Oct 2008
- Nov 2008
- Dec 2008
- Jan 2009
- Feb 2009
- Mar 2009
- Apr 2009
- May 2009
- Jun 2009
- Jul 2009
- Aug 2009
- Sep 2009
- Oct 2009
- Nov 2009
- Dec 2009
- Jan 2010
- Feb 2010
- Mar 2010
- Apr 2010
- May 2010
- Jun 2010
- Jul 2010
- Aug 2010
- Sep 2010
- Oct 2010
- Nov 2010
- Dec 2010
- Jan 2011
- Feb 2011
- Mar 2011
- Apr 2011
- May 2011
- Jun 2011
- Jul 2011
- Aug 2011
- Sep 2011
- Oct 2011
- Nov 2011
- Dec 2011
- Jan 2012
- Feb 2012
- Mar 2012
- Apr 2012
- May 2012
- Jun 2012
- Jul 2012
- Aug 2012
- Sep 2012
- Oct 2012
- Nov 2012
- Dec 2012
- Jan 2013
- Feb 2013
- Mar 2013
- Apr 2013
- May 2013
- Jun 2013
- Jul 2013
- Aug 2013
- Sep 2013
- Oct 2013
- Nov 2013
- Dec 2013
- Jan 2014
- Feb 2014
- Mar 2014
- Apr 2014
- May 2014
- Jun 2014
- Jul 2014
- Aug 2014
- Sep 2014
- Oct 2014
- Nov 2014
- Dec 2014
- Jan 2015
- Feb 2015
- Mar 2015
- Apr 2015
- May 2015
- Jun 2015
- Jul 2015
- Aug 2015
- Sep 2015
- Oct 2015
- Nov 2015
- Dec 2015
- Jan 2016
- Feb 2016
- Mar 2016
- Apr 2016
- May 2016
- Jun 2016
- Jul 2016
- Aug 2016
- Sep 2016
- Oct 2016
- Nov 2016
- Dec 2016
- Jan 2017
- Feb 2017
- Mar 2017
- Apr 2017
- May 2017
- Jun 2017
- Jul 2017
- Aug 2017
- Sep 2017
- Oct 2017
- Nov 2017
- Dec 2017
- Jan 2018
- Feb 2018
- Mar 2018
- Apr 2018
- May 2018
- Jun 2018
- Jul 2018
- Aug 2018
- Sep 2018
- Oct 2018
- Nov 2018
- Dec 2018
- Jan 2019
- Feb 2019
- Mar 2019
- Apr 2019
- May 2019
- Jun 2019
- Jul 2019
- Aug 2019
- Sep 2019
- Oct 2019
- Nov 2019
- Dec 2019
- Jan 2020
- Feb 2020
- Mar 2020
- Apr 2020
- May 2020
- Jun 2020
- Jul 2020
- Aug 2020
- Sep 2020
- Oct 2020
- Nov 2020
- Dec 2020
- Jan 2021
- Feb 2021
- Mar 2021
- Apr 2021
- May 2021
- Jun 2021
- Jul 2021
- Aug 2021
- Sep 2021
- Oct 2021
- Nov 2021
- Dec 2021
- Jan 2022
- Feb 2022
- Mar 2022
- Apr 2022
- May 2022
- Jun 2022
- Jul 2022
- Aug 2022
- Sep 2022
- Oct 2022
- Nov 2022
- Dec 2022
- Jan 2023
- Feb 2023
- Mar 2023
- Apr 2023
- May 2023
- Jun 2023
- Jul 2023
- Aug 2023
- Sep 2023
- Oct 2023
- Nov 2023
- Dec 2023
- Jan 2024
- Feb 2024
- Mar 2024
- Apr 2024
- May 2024
- Jun 2024
- Jul 2024
- Aug 2024
- Sep 2024
- Oct 2024
- Nov 2024
- Dec 2024
May 2015
Anonymous
Sun 3-May-2015 02:12
Sun 3-May-2015 02:12
Hi Linus,
I've been asking this a couple of times a year for the past 3 or 4 years now, but I still maintain hope. What are your plans for the bitbuff - do you plan to release source code, etc. sometime? Maybe even do a writeup on how the synthesiser works (a guide to designing your own and the constrains you overcame / little tricks)?
Keep up the excellent and exciting work!
I've been asking this a couple of times a year for the past 3 or 4 years now, but I still maintain hope. What are your plans for the bitbuff - do you plan to release source code, etc. sometime? Maybe even do a writeup on how the synthesiser works (a guide to designing your own and the constrains you overcame / little tricks)?
Keep up the excellent and exciting work!
Anonymous
Sun 3-May-2015 22:27
Sun 3-May-2015 22:27
Hello, Linus! Just wanted to say "hello" and that I'm glad there are some persons out there like you. We pretty have same wide interests and activity. It's hard to find someone like this. Sorry for my not perfect english. Greetings. Long time from Demoscene and found your channel on YouTube... Amazing work! Best wishes and go on the same spirit.
A case against syntax highlighting
Anonymous
Mon 4-May-2015 12:25
Mon 4-May-2015 12:25
I think syntax highlighting for prose may not be such a bad idea after all. If you trained yourself for the colors, it might become much easier to skim through text. Could be useful if you don't need to understand the content too deeply.
Anonymous
Fri 8-May-2015 12:00
Fri 8-May-2015 12:00
The best article about tty ever! no kidding.
Anonymous
Sun 10-May-2015 17:30
Sun 10-May-2015 17:30
Spectacular. Do you mind telling us how the sound is produced? —Thore
Anonymous
Sun 10-May-2015 20:20
Sun 10-May-2015 20:20
Great Work!
lft
Linus Åkesson
Sun 10-May-2015 21:13
Linus Åkesson
Sun 10-May-2015 21:13
With pleasure! I kept the opening of the video quite vague for dramatic effect, but there's no harm in explaining it here. First, we see a Commodore 64 with a 1541 floppy drive, loading a program called "ONE". If you watch the monitors closely, you will see that there are in fact eight different programs running, named ONE through EIGHT. Each program is running on a Commodore 64, producing sound through the SID chip inside. Briefly, this chip provides three independent oscillators, capable of generating pulse, triangle and sawtooth waves at frequencies up to about 4 kHz, as well as white noise. The volume can also be controlled for each voice. So with eight machines, that's 24 voices in total.
The piano part was recorded first. The program code was written in 6502 assembly language, and the data was edited using a custom tool created for this project. In the tool, I could edit all 24 voices in parallel, and pre-listen to the (emulated) synthesised sound along with the recorded piano part, starting from any time offset.
At the beginning of each SID part, before what you see in the video, is a loud click. This allowed me to synchronise the various sound and video parts during the final video editing, since the click also showed up on the oscilloscope.
The piano part was recorded first. The program code was written in 6502 assembly language, and the data was edited using a custom tool created for this project. In the tool, I could edit all 24 voices in parallel, and pre-listen to the (emulated) synthesised sound along with the recorded piano part, starting from any time offset.
At the beginning of each SID part, before what you see in the video, is a loud click. This allowed me to synchronise the various sound and video parts during the final video editing, since the click also showed up on the oscilloscope.
Anonymous
Thu 14-May-2015 09:50
Thu 14-May-2015 09:50
Thank you. (I’ve been programming the C64 SID chip myself, in the Days of Yore.) What role do the oscillators play? Do they just visualise the output of the SID? (All three voices, then?)
Anonymous
Fri 22-May-2015 11:58
Fri 22-May-2015 11:58
Albatross 2000 är ett mästerverk. Fick tag på skivan vid visingen på Panora år 2000 tror jag. Håller än.
Anonymous
Fri 22-May-2015 12:02
Fri 22-May-2015 12:02
Albatross 2000 är ett mästerverk. Fick tag på skivan vid visingen på Panora år 2000 tror jag. Håller än.
Föresten, hittade verket i sin helhet på youtube:
https://youtu.be/gngzXg6I5m0
Anonymous
Thu 28-May-2015 14:18
Thu 28-May-2015 14:18
This is very awesome! I hope you should start a kickstarter campaign for this and get rich.... Just sayin' LOL xD Anyway, it is very impressive! :)
A case against syntax highlighting
Anonymous
Sat 30-May-2015 03:48
Sat 30-May-2015 03:48
I happen to think that syntax is EXTREMELY important. It is what describes semantics to both people and machines. Different syntax highlighting is actually subtly different concrete syntax, just as different stylistic convention is subtly different concrete syntax. So it can (and often does) imply differences in semantics. That the highlighting goes away and is rebuilt differently between different editors and IDEs is the core of the problem. If the typography was precisely communicated in the source code of the program and everyone would see the same thing when they looked at it would not be a problem. But this isn't the case, so it is a problem.
It compounds subjectivity in reading source code. Not only do people simply think different things when they read the code, it is actually presented to them differently; hiding things that are obvious to others, and drawing attention to things that are not.
Rather than syntax highlighting being bad, the fragmentation of source code presentation is bad. Two very different approaches to fixing this are that of something like smalltalk, where the programming environment is 'built in', and everyone who works on the code uses that same interface; or that of something like golang that is packaged with a tool (gofmt) that transforms any valid go source file into one with a canonical layout. Golang also establishes a convention of applying this transformation to all golang source code before sharing it with others.
Where it is not a part of the established tooling for the language, it either amounts to inconsistency or an additional dependency. Neither of which is a good thing in the general case. Removing inconsistency makes the human interpretation of your code more coherent, and removing dependencies gives your software an additional dimension of freedom. It makes your code more portable between readers and allows you to use tools that might not provide the required dependency (syntax highlighting).
It compounds subjectivity in reading source code. Not only do people simply think different things when they read the code, it is actually presented to them differently; hiding things that are obvious to others, and drawing attention to things that are not.
Rather than syntax highlighting being bad, the fragmentation of source code presentation is bad. Two very different approaches to fixing this are that of something like smalltalk, where the programming environment is 'built in', and everyone who works on the code uses that same interface; or that of something like golang that is packaged with a tool (gofmt) that transforms any valid go source file into one with a canonical layout. Golang also establishes a convention of applying this transformation to all golang source code before sharing it with others.
Where it is not a part of the established tooling for the language, it either amounts to inconsistency or an additional dependency. Neither of which is a good thing in the general case. Removing inconsistency makes the human interpretation of your code more coherent, and removing dependencies gives your software an additional dimension of freedom. It makes your code more portable between readers and allows you to use tools that might not provide the required dependency (syntax highlighting).