The Official Sequential/Oberheim Forum
SEQUENTIAL/DSI => Tempest => Topic started by: Outsider on September 11, 2017, 01:15:52 AM
-
Last I checked, an OS update allowed some limited Glide functionality. Is this still the case with the Final OS and, if so, what exactly is the available functionality?
Thanks
:)
-
It works for me I'm not sure if any limitation but if I dial I some glide the oscillators do exhibit portomento characteristics. Last I tried both modes gave different glide response too if I remember correctly.
I do remember some problems with glide but without trawling through the beta/yorgospatchcomplaintthread I cannot say what it was or if it was fully fixed.
I defo get some glide though seperate for each analog osc.
-
I seem to recall something about the Legato/Glide 'FixRate A' and 'FixTime A' modes being removed. I could be mistaken as I have no access to Tempest at moment. Perhaps someone could clarify?
-
I seem to recall something about the Legato/Glide 'FixRate A' and 'FixTime A' modes being removed. I could be mistaken as I have no access to Tempest at moment. Perhaps someone could clarify?
Seems to work for me, checked that it works on both oscillators and the sub, both modes do give a different response like i already said, for me at least it seems to be fine you would have to ask John The Savage if its working as intended but i think it is at least.
Sounds great too!
-
Well, there used to be 4 glide modes in total, but the secondary "legato" modes - Fixed Rate 'A' and Fixed Time 'A' (documented in the original manual) - have since been removed from the operating system and the U.I. altogether. But they never worked to begin with.
The standard glide modes, on the other hand, are still there and functioning. The one proviso being that glide only works *correctly if you have the sound in question assigned to a voice.
Cheers!
-
Well, there used to be 4 glide modes in total, but the secondary "legato" modes - Fixed Rate 'A' and Fixed Time 'A' (documented in the original manual) - have since been removed from the operating system and the U.I. altogether. But they never worked to begin with.
The standard glide modes, on the other hand, are still there and functioning. The one proviso being that glide only works *correctly if you have the sound in question assigned to a voice.
Cheers!
Thanks for the clarification John! If no one had ever said "it has 4 modes" everyone would be none the wiser and think it works perfectly, which it does, if you assign a voice, i think we'll call that a win ;)
-
Thanks for clarifying, and clearing up the answer John.
-
Thanks to this thread I started messing with glide modes....works great. For my crazy lead perc for upcoming track. Mind you I am not a keyboardist so it's not like I would understand the nuances of the different modes and lost modes...
-
Fixed Rate A and Fixed Time A worked for me when I first bought my Tempest. It was really cool for sequencing a bass line. It was broken around the same time that the "Flam" issue was trying to be fixed. Which was shortly after I purchased my Tempest. It remained on the bug list for years. It was hard to watch it never be fixed while other non-requested features were added. I never understood at the time (and still don't to this day) if it was a technical impossibility or something that never received the needed effort.
-
The 4 glide modes are covered on page 29 of the Tempest manual.
-
The 4 glide modes are covered on page 29 of the Tempest manual.
Can someone explain with presets how to create a simple saw wave bass sound that has legato, so even when I keep my fingers on a key, then press another key, it goes to that one instead of playing a chord ?
-
The 4 glide modes are covered on page 29 of the Tempest manual.
Can someone explain with presets how to create a simple saw wave bass sound that has legato, so even when I keep my fingers on a key, then press another key, it goes to that one instead of playing a chord ?
Assign a voice to the pad your synth is on.
-
Thanks ya'll!
-
The 4 glide modes are covered on page 29 of the Tempest manual.
Can someone explain with presets how to create a simple saw wave bass sound that has legato, so even when I keep my fingers on a key, then press another key, it goes to that one instead of playing a chord ?
Assign a voice to the pad your synth is on.
Um yes. So for example , i have chosen a saw wave in osc 1. I have it set up and midi routed to my prophet 6 to access the notes on the keys. I toggle right until I hit glide mode and turn on fixrate A because it sounds like that's the closest to legato mode I want that allows you to hold a note and when a new note hits it plays that note instead of your last note that you're holding whether it be a higher note priority or lower. Is it possible that the legato I'm thinking of is simply note possible and they the glide mode fix rates are meant to be glide rather than legato ? Because I was explained by support at DSI that the legato is created by glide in the tempest . And I may have misunderstood but some clarification would be awesome .
-
It sounds like you understand the difference between glide and legato, so one last time for the record, the Tempest only does glide. That's why the parameter is called "glide". It does not do legato. The legato functionality, despite being included in the original manual and operating system, never worked properly, was neglected for years, and was eventually removed from the U.I. altogether to avoid confusion. Though, evidently, that hasn't worked —ahem!
At any rate, this was all explained, for the umpteenth time, in this very thread, which is all of ten posts long. Read, folks, for the love of music, read...
I should probably stop answering questions around here (smirk).
Cheers!
-
It sounds like you understand the difference between glide and legato, so one last time for the record, the Tempest only does glide. That's why the parameter is called "glide". It does not do legato. The legato functionality, despite being included in the original manual and operating system, never worked properly, was neglected for years, and was eventually removed from the U.I. altogether to avoid confusion. Though, evidently, that hasn't worked —ahem!
At any rate, this was all explained, for the umpteenth time, in this very thread, which is all of ten posts long. Read, folks, for the love of music, read...
I should probably stop answering questions around here (smirk).
Cheers!
Yes, very cheerful indeed.
-
Deleted from an OS that is no longer in development. Right.
This OS should be OPEN SOURCE! What is there to be afraid of if you're no longer developing the software??
smh
-
Top government DSI secrets ;)
Deleted from an OS that is no longer in development. Right.
This OS should be OPEN SOURCE! What is there to be afraid of if you're no longer developing the software??
smh
-
What does that mean? Do you have insider knowledge? :)
Seriously though, I would like to know. If it goes open source I will be way less likely to sell
-
If that’s the reason you’re keeping it you might sell it as well cause it ain’t happening as stated by DSI stuff..As i’ve told top secret...
What does that mean? Do you have insider knowledge? :)
Seriously though, I would like to know. If it goes open source I will be way less likely to sell
-
I'd hazard a guess that they want to keep the matrix mixer software and their algorithms as secret as they can because no one else really makes polys with this power and ease of use these days. Maybe thats not the reason but i can't really think of many other reasons why they wouldn't make it open source.
-
I'd hazard a guess that they want to keep the matrix mixer software and their algorithms as secret as they can because no one else really makes polys with this power and ease of use these days. Maybe thats not the reason but i can't really think of many other reasons why they wouldn't make it open source.
If the current software has already maxed out the resources of the device, what would be served by open-sourcing the code?
I'd guess, instead, that it's being re-purposed somewhere else, in another product....