Log in
Log in

or

Thread Turn Off Effect in QS8

  • 6 replies
  • 3 participants
  • 5,569 views
  • 0 follower
tileeba

tileeba

4 posts
New AFfiliate
First post
1 Posted on 03/27/2006 at 12:59:56
Hello!

I have an Alesis QS8 conected through MIDI and sound card to my computer, where I sequence with Sonar 3.

Someone told me that when I record the sound of any instrument, I should record without any effects (like reverb) - which I will add later on when I mix.

Call me stupid, but I still can't figure out how to turn off "reverb" on my QS8 while I sample in Sonar 3.

What I want to do is sample instruments from my Alesis QS8 in Sonar 3 (That I already know how to do) - and when I record the instruments as wave, I want the "REVERB" turned off in my Alesis QS8, so I don't record the reverb.

Could someone please guide me through the process? I'd really appreciate it!
thesparrowband

thesparrowband

137 posts
AFfinity Poster
2 Posted on 03/28/2006 at 13:54:35
Ok, i have an alessi qs8.1, and the way i understand what you are doing is this: you have a cable plugged into the MIDI out of the QS8, into the computer, then you have another cable from the computer's MIDI out to the QS8's MIDI IN?

The way i understand this set up is that, correct me if i'm wrong, but when you hit record, Sonar records the MIDI notes, then sends them throught the computer's MIDI out so that the QS8 can play them back.

If that is the case, then you can do a number of things. First off, it doesn't really matter if you record it dry or not because it is a synth, and those effects can be added and removed at any time.

To remove the reverb, try recording in Sonar, then editing the recorded MIDI data, and see if it has effects options. If it does, uncheck reverb. The reverb MIDI channel is also listed in the QS8's manual.

Another way would be to go into the QS8 and do it manually, before recording. If the QS8 is like the QS8.1, then you hit the mix button, and edit parameters from there on... try the manual?

I wouldn't worry about recording w/ reverb, because with MIDI, nothing is permenant, so you have the luxury of figuring it out later.

goodluck
KitC

KitC

243 posts
AFfinity Poster
3 Posted on 03/28/2006 at 20:27:42
Some patches in the QS series do not respond properly to CC#91 (reverb) and CC#93 (chorus); this is true for both program and mix patches. You might have to go into patch edit mode as the sparrowband says and disable the fx from there. Be aware that a lot of the programs and mixes make extensive use of the QS' other fx algorithms in order to achieve that specific sound. Disabling the fx outright might, and usually will, radically change the sound of the patch
tileeba

tileeba

4 posts
New AFfiliate
4 Posted on 03/29/2006 at 05:56:34
Thank you, fellows, for your help! I really appreciate your taking the time!

I did some research and found this way of disabling the effects glabally:

http://alesis.com/support/notes/Keyboard/qsfx_dry.html

KitC, you wrote:

%1$s a écrit Disabling the fx outright might, and usually will, radically change the sound of the patch


What would you do in my case? Should I still disable reverb when I am recording the sound in a mix or not?
tileeba

tileeba

4 posts
New AFfiliate
5 Posted on 03/29/2006 at 05:54:36
Sparrowband, I will look and see if there is a reverb off in Sonar for midi. That would be great! Thanks.
KitC

KitC

243 posts
AFfinity Poster
6 Posted on 03/29/2006 at 07:25:02
tileeba,

I've found out, with my QS6, that the reverb is often controlled either by the mod wheel or the Ctrl A slider. In any event, if it was a light smattering of reverb, it usually does not detract from the mix; I tend to track effected synths to their own audio track anyway so I can control overall balance; I usually end up adding just a touch of ambiance to the overall mix to blend in my different hardware synths. If the reverb becomes obstrusive, I then disable it and just track the synth again. Anyway, I always record midi in conjunction with audio so I can always go back to a particular synth when required.

I always draw the line between bass and reverb because using those 2 together always muddies up a mix. Use your best judgement.
tileeba

tileeba

4 posts
New AFfiliate
7 Posted on 03/30/2006 at 08:48:05
Thank you, KitC, for the suggestions!
cookies
We are using cookies!

Yes, Audiofanzine is using cookies. Since the last thing that we want is disturbing your diet with too much fat or too much sugar, you'll be glad to learn that we made them ourselves with fresh, organic and fair ingredients, and with a perfect nutritional balance. What this means is that the data we store in them is used to enhance your use of our website as well as improve your user experience on our pages and show you personalised ads (learn more). To configure your cookie preferences, click here.

We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

Our cookies
Cookies not subject to consent
These are cookies that guarantee the proper functioning of Audiofanzine and allow its optimization. The website cannot function properly without these cookies. Example: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).
Audience analysis (Google Analytics)
We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it.
Advertising (Google Ads)
This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :) We are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest. We are likely to display advertisements from our own platform, from Google Advertising Products or from Adform.
Marketing (Meta Pixel)

On our websites, we use the Meta Pixel. The Meta Pixel is a remarketing pixel implemented on our websites that allows us to target you directly via the Meta Network by serving ads to visitors of our websites when they visit the social networks Facebook and Instagram. The meta pixel are code snippets which are able to identify your browser type via the browser ID - the individual fingerprint of your browser - and to recognise that you have visited our websites and what exactly you have looked at on our websites. When you visit our websites, the pixel establishes a direct connection to Meta's servers. Meta is able to identify you by your browser ID, as this is linked to other data about you stored by Meta on your Facebook or Instagram user account. Meta then delivers individualised ads from us on Facebook or on Instagram that are tailored to your needs.

We ourselves are not in a position to identify you personally via the meta pixel, as apart from your browser ID no other data is stored with us via the pixel.

For more information about the Meta Pixel, the details of data processing via this service and Meta's privacy policy, please visit Meta Privacy Policy - How Meta collects and uses user data for Facebook and Meta Privacy Policy - How Meta collects and uses user data for Instagram.

Meta Platforms Ireland Ltd. is a subsidiary of Meta Platforms, Inc. based in the USA. It cannot be ruled out that your data collected by Facebook will also be transmitted to the USA.


We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

Our cookies
Cookies not subject to consent

These are cookies that guarantee the proper functioning of Audiofanzine. The website cannot function properly without these cookies. Examples: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).

Audience analysis (Google Analytics)

We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it. When this parameter is activated, no personal information is sent to Google and the IP addresses are anonymized.

Advertising (Google Ads)

This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :) We are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest. We are likely to display advertisements from our own platform, from Google Advertising Products or from Adform.

Marketing (Meta Pixel)

On our websites, we use the Meta Pixel. The Meta Pixel is a remarketing pixel implemented on our websites that allows us to target you directly via the Meta Network by serving ads to visitors of our websites when they visit the social networks Facebook and Instagram. The meta pixel are code snippets which are able to identify your browser type via the browser ID - the individual fingerprint of your browser - and to recognise that you have visited our websites and what exactly you have looked at on our websites. When you visit our websites, the pixel establishes a direct connection to Meta's servers. Meta is able to identify you by your browser ID, as this is linked to other data about you stored by Meta on your Facebook or Instagram user account. Meta then delivers individualised ads from us on Facebook or on Instagram that are tailored to your needs.

We ourselves are not in a position to identify you personally via the meta pixel, as apart from your browser ID no other data is stored with us via the pixel.

For more information about the Meta Pixel, the details of data processing via this service and Meta's privacy policy, please visit Meta Privacy Policy - How Meta collects and uses user data for Facebook and Meta Privacy Policy - How Meta collects and uses user data for Instagram.

Meta Platforms Ireland Ltd. is a subsidiary of Meta Platforms, Inc. based in the USA. It cannot be ruled out that your data collected by Facebook will also be transmitted to the USA.


You can find more details on data protection in our privacy policy.
You can also find information about how Google uses personal data by following this link.