Mellotronists group photo

Yahoo Groups archive

Mellotronists

Index last updated: 2026-04-28 23:09 UTC

Message

Re: [Mellotronists] Streetly Web-site

2006-09-24 by Nicklas Barker

And what will be digital in the new Streeltly tron??

/Nick

kinchmusic@... wrote:

> In a message dated 23/09/2006 23:56:08 GMT Standard Time, 
> ken@... writes:
>
>     If you are referring to the M4000, that's been there for quite a
>     while.
>
> Sorry Ken, yes I am.
> It's just that I've not noticed it before, or have I heard anyone here 
> make mention of it's appearance on the web-sites front page, so I 
> thought I would do so.
> Why hasn't there been more reaction from everyone. I know the new 
> Streetly machine is the worst kept secret on this list. But really, I 
> would have thought that the first Mellotron to be built here in the UK 
> by the company that made the original in 30 years would have created 
> more than a passing interest.
> AND from what I hear, this will a Mellotron unlike any that has gone 
> before. This will be no M400 remake. After all, JB and MS have been 
> there, done that, bought the tee shirt. Why would they want to do 
> that? Simply trying to recreate the past would be a waste of 
> resources, when much much more could be achieved.
> The only way forward would be to create a machine that is so awesome 
> in it's power and versatility, whilst retaining the iconic appearance 
> we all know. Yet combining the very best of analogue and digital 
> technology, to breathe new life into the machine we all know and love. 
> Not that I know the full story by any means, but I've a feeling when 
> this thing breaks it's going to be huge. Wouldn't it be a pity if 
> suddenly it was embraced by the world-wide music industry and we were 
> all siting here scratching our heads not knowing the significance of 
> what was going on.
> Brace yourselves.
> Andy K
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.