The Mellotron Group group photo

Yahoo Groups archive

The Mellotron Group

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

Message

Re: [newmellotrongroup] M4000 D

2011-09-01 by Hessel Herder

Can you tell more about the M1 Frank?
Is it the ebay one demonstrated by that lady with 
the hairy arms? 



Op 1 sep. 2011 om 19:35 heeft lsf5275@aol.com het volgende geschreven:

> I won't. It's the best of the lot. I'd love to have one just to have. It's not a Mellotron, but it has cool sounds in it, and lots of them. It has Mellotron sounds and Chamberlin sounds. It had friendly software and it does cool stuff. It isn't a Mellotron but it does as good an imitation of one as you're likely to find anywhere.
>  
> If you have both you're all the better for it. I was thinking of buying one and sometime soon I might. I am fortunate because I have a real M4000 Mellotron and I love playing it and having others play and record it. I also have acquired a real Chamberlin M1.
>  
> Frank
>  
> In a message dated 9/1/2011 12:13:33 P.M. Eastern Daylight Time, gabru@comsec.net writes:
>  
> In a live or studio mix you would never hear the difference especially after the reverb and
> 
> other processing that is commonly used on Mellotron tracks.  It will almost certainly out
> 
> sell the tape machines but most on this list will hate it no matter what it sounds like. 
> 
> Fire away…. J
> 
> 
> From: newmellotrongroup@yahoogroups.com [mailto:newmellotrongroup@yahoogroups.com] On Behalf Of mellotronmadness
> Sent: Wednesday, August 31, 2011 8:56 PM
> To: newmellotrongroup@yahoogroups.com
> Subject: [newmellotrongroup] M4000 D
> 
> 
>  
> 
> I hadn't seen this before, I think I can just tell the difference between the M4000D and the Mark VI. I don't suppose anybody on the list has been tempted?
> 
> 
> 
> http://www.youtube.com/watch?v=JYKe7a7lc-E&feature=related
> 
> < /div>
> 
> Mark
> 
> 
>

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.