"I find it easiest to change the tempo back by tweaking the BPM setting by a notch and then back again." That does not work Ski. I tried it yesterday and just now, and you only have 2 choices if you happen to run over CLO and want to get back to the original tempo: set all steps to 40 or do a program reset. If you didnt save your program before running over CLO, you will waste precious time for nothing. I worked a couples hours with 1.6 yesterday and i found this behavior extremely annoying and time consuming. I really think a reset to the orignal tempo should be done once you have left the CLO destination. on 30/09/03 2:38 AM, ski_ex5tech at ex5tech@... wrote: My sincere apologies, Simon, I misunderstood. Yes, you're right. If you set a sequencer destination to Clock Mod (even if just "running over it") while running the sequencer, it WILL change the tempo of the sequence to something other than the BPM setting, unless all sequencer steps are set to 40. That's what it's supposed to do though, of course. It changes the tempo, and the tempo won't change back until you DO something to change the tempo. I find it easiest to change the tempo back by tweaking the BPM setting by a notch and then back again. Maybe Dave could program the Reset to do this, too. Ski www.ex5tech.com EX5Tech Evolver forum: http://www.ex5tech.com/ex5ubb_cgi/ultimatebb.cgi?ubb=forum&f=23 --- In DSI_Evolver@yahoogroups.com, simon leclerc <Simonvolt@v...> wrote: > 1.6 does not resolve what i'm describing below. > diS / CLO are now seperated, but if run over > CLO it changes all clock settings and the only way > to get it back is to manually put all steps > to 40 or do a program reset. > > > on 29/09/03 11:54 PM, ski_ex5tech at ex5tech@e... wrote: > > As already posted to the group and to EX5Tech, OS beta 1.6 solves > this problem. Check the posts from the past couple days, or go > download beta 1.6 for yourself to give it a try. > > > Ski > www.ex5tech.com > EX5Tech Evolver forum: > http://www.ex5tech.com/ex5ubb_cgi/ultimatebb.cgi?ubb=forum&f=23 > > --- In DSI_Evolver@yahoogroups.com, "Simon " <Simonvolt@v...> wrote: > > Just a note: > > I think modulating the clock is great (diS is great too :)) > > but like i mentionned in OS 1.5, everytime you run over the > > CLO destination, your original clock settings get screwed. You > > either have to manually set all steps to 40 or start over and reset > > the program. > > Would it be possible to get back to the previous clock settings > > when leaving CLO ? > > Cause you'll see that it can be really anoying to reach for diS but > > accidentally run over CLO and scew up your program. > > > > Simon > > > Yahoo! Groups Sponsor ADVERTISEMENT > > To unsubscribe from this group, send an email to: > DSI_Evolver-unsubscribe@yahoogroups.com > > > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service > <http://docs.yahoo.com/info/terms/> . Yahoo! Groups Sponsor ADVERTISEMENT To unsubscribe from this group, send an email to: DSI_Evolver-unsubscribe@yahoogroups.com Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service <http://docs.yahoo.com/info/terms/> .
Message
Re: [Evolver] Re: CLO destination
2003-09-30 by simon leclerc
Attachments
- No local attachments were found for this message.