[Coco] Including an SSC

Simon Jonassen simon at roust-it.dk
Sat Oct 11 14:08:42 EDT 2014


Another example of the AY chip here:

http://roust-it.dk/coco/AYCHIP/factor6.mp3

Don't knock the beast....

It's *ALMOST* as good as the legendary SID (MOS 6581)

What it *would* do in this case is provide an easy way to produce wound on
the coco withhout the overhead that we have today.....

Again, just my 2c

/Simon :-)
 

-----Oprindelig meddelelse-----
Fra: Coco [mailto:coco-bounces at maltedmedia.com] På vegne af Simon Jonassen
Sendt: 11. oktober 2014 20:05
Til: 'CoCoList for Color Computer Enthusiasts'
Emne: Re: [Coco] Including an SSC

Just my 2c

He who says the AY chip is simple... FAIL !

Far from it !.....

This is the same chip as in the SSC (AY) making incredible sounds on a ZX
spectrum:

http://roust-it.dk/coco/AYCHIP/01-Yerzmyey-Why.mp3

/simon:-)
 

-----Oprindelig meddelelse-----
Fra: Coco [mailto:coco-bounces at maltedmedia.com] På vegne af S Klammer
Sendt: 11. oktober 2014 13:07
Til: CoCoList for Color Computer Enthusiasts
Emne: Re: [Coco] Including an SSC

Waiting to see what Darren's "light bulb moment" will potentially bring to
his CocoSDC.

Five is a small number... does that lessen the usefulness of an added
function?  :)  As one, I have to accept (with no animosity), if it does.

I'd agree an expansion header *would be* nice.

I don't think Darren's work would be exploited for profit - I'd think that
it is too specific to the Coco to make it into a retirement plan... :)
(Although, he would deserve it)... I do not have all the skills, yet, I
would still be interested in seeing/learning the details of Darren's design.

Shain
On Oct 11, 2014 4:17 AM, "Nick Marentes" <nickma2 at optusnet.com.au> wrote:

> On 11/10/2014 12:48 PM, Louis Ciotti wrote:
>
>> Well Darren has said he is going to release all the information to 
>> the public.  So if this really is wanted, maybe someone who wants the 
>> functionality can take the baton and make a variant with the SSC 
>> hitches on it.
>>
>>
>
> I don't know if allowing it out in the wild for anyone to create a 
> variant is such a good idea.
>
> It starts to fragment the "standard" and makes it a royal mess trying 
> to support the new features.
>
> It also leaves it open for someone to exploit Darren's work for profit.
> This has happenned all to often.
>
> I think it needs to stay in Darren's control and modifications and 
> enhancements done by "authorised" developers.
>
> My argument has always been that if only a CoCo bus header is inserted 
> into the PCB layout (*if this is even possible*) then people can build 
> all manner of hardware that can attach to this, no other modification 
> to the CoCoSDC require, no need to have a mulitipak.
>
> Nick
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>

--
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco
-----
Ingen virus fundet i denne meddelelse.
Kontrolleret af AVG - www.avg.com
Version: 2012.0.2247 / Virusdatabase: 4031/7858 - Udgivelsesdato: 10-10-2014


--
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco
-----
Ingen virus fundet i denne meddelelse.
Kontrolleret af AVG - www.avg.com
Version: 2012.0.2247 / Virusdatabase: 4031/7864 - Udgivelsesdato: 11-10-2014



More information about the Coco mailing list