New YouTube channel for Amstrad CPC Demos

[Interrupt]

After arnoldemu's suggestion to simply record myself writing some code I had a try tonight at creating a first part of a series writing a very simple intro (I'll eventually focus on minimising the size because the idea is very simple in itself). I enjoyed the process much more than trying to make a tutorial video. I think the chapter headings should allow people to skip bits they aren't interested in.

I'd love to hear your thoughts - does this format work well? anything you'd like to cover? anything I'm doing wrong/missing the point on? do you have any better coding setups I should be using?

[krusty_benediction]

I've just procrastinated a lot and watched your video related to the 4k.
I think I'll take a look at the others, but I need time .
Well done, keep doing them!
It is also interesting to listened at your naive guesses (although they are not always true )

Thanks! The most advanced techniques I've used are relatively simply raster bars for volume meters and basic palette tricks so I've got a lot to learn!

BTW, as a regular contributor to 4k intro,  I consider the 4k INCLUDES  the 128 bytes header. So cat prints 4k, not 4k.

There is no hard rules written somewhere,  parties do whatever they want, but most people I have met and are implied with such productions agree on the definition.

So at least one of the demo you presented is an outlier as when you do cat, we see 5kb

[Interrupt]

I've just procrastinated a lot and watched your video related to the 4k.
I think I'll take a look at the others, but I need time .
Well done, keep doing them!
It is also interesting to listened at your naive guesses (although they are not always true )

Thanks! The most advanced techniques I've used are relatively simply raster bars for volume meters and basic palette tricks so I've got a lot to learn!

BTW, as a regular contributor to 4k intro,  I consider the 4k INCLUDES  the 128 bytes header. So cat prints 4k, not 4k.

There is no hard rules written somewhere,  parties do whatever they want, but most people I have met and are implied with such productions agree on the definition.

So at least one of the demo you presented is an outlier as when you do cat, we see 5kb

I didn't look that closely as these mostly came from pouet and were tagged as 4k. I would have expected the general definition to include the header as it adds extra challenge (and maybe potential to use it cleverly?) but can understand why some people take the other view.

On a different note: is it considered acceptable to use firmware routines? E.g. for clearing the screen and printing text?

[krusty_benediction]

I've just procrastinated a lot and watched your video related to the 4k.
I think I'll take a look at the others, but I need time .
Well done, keep doing them!
It is also interesting to listened at your naive guesses (although they are not always true )

Thanks! The most advanced techniques I've used are relatively simply raster bars for volume meters and basic palette tricks so I've got a lot to learn!

BTW, as a regular contributor to 4k intro,  I consider the 4k INCLUDES  the 128 bytes header. So cat prints 4k, not 4k.

There is no hard rules written somewhere,  parties do whatever they want, but most people I have met and are implied with such productions agree on the definition.

So at least one of the demo you presented is an outlier as when you do cat, we see 5kb

I didn't look that closely as these mostly came from pouet and were tagged as 4k. I would have expected the general definition to include the header as it adds extra challenge (and maybe potential to use it cleverly?) but can understand why some people take the other view.

On a different note: is it considered acceptable to use firmware routines? E.g. for clearing the screen and printing text?

Sure

 for me the hard limitations are:
- exécutable + header = 4k
- no use of roms/hardware not present in a stock machine

Borderline limitations
- must also work on a machine with no standard ram. And here many <4k prods probably fail (i lost 3 bytes in 4dekades to respect this rule)

[krusty_benediction]

I wanted to say "no standard ROM" instead of "no standard RAM"

[Interrupt]

In this coding video I decided to try drawing the characters using the system font with some firmware routines.