Mellotronists group photo

Yahoo Groups archive

Mellotronists

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

Message

Re: [Mellotronists] Track Blending Returns

2005-08-23 by kenmerb@aol.com

Martin old pal,
 
How did you achieve this feat without the Mothertron?  Did you and JB break into the museum?
 
I never really had much of a problem with this on my M400, since the selector is kind of continuous and you can put it wherever you want between tracks (or even blend as you play).  However, it's been an issue with my MKII, since there are specific stopping points between the tracks when you push a selector button.  Will this problem go away on the MKII with the new tapes?  If so, quite an accomplishment.  I'm still curious as to how you did it.  No more "suck out" zone between tracks.  I want these new tapes that don't suck.
 
Ken M.
MKII #247 (now a Texas Tron)
 
 
 
-----Original Message-----
From: tronbros@...
To: Mellotronists@yahoogroups.com
Sent: Tue, 23 Aug 2005 11:35:16 EDT
Subject: [Mellotronists] Track Blending Returns


Dear All,
 
Within days, all tapes supplied by Streetly will have proper track blending reinstated just like Streetly tapes of old.  No more suck out zone between A and B, B and C but a nice loud continuous signal.  This unique feature of Les Bradley's tapes died when the Mothertron died nearly 20 years ago.  What better than EMI tape recorded at the correct mellotron azimuth with clear blending of tracks.  You lucky, lucky bastards!
 
Cheerfully,
 
Martin.

STREETLY ELECTRONICS - All things Mellotronic
www.mellotronics.com

US East Coast Agent - Jimmy Moore JMoore6397@...
US West Coast Agent - Paul Cox pjc56@...



YAHOO! GROUPS LINKS 

 Visit your group "Mellotronists" on the web.
  
 To unsubscribe from this group, send an email to:
 Mellotronists-unsubscribe@yahoogroups.com
  
 Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

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.