![]() |
|
#1
| |||
| |||
| I've experimented to try and isolate the cause, and I've found that it stops happening if a solo the track in question. When I start bringing the other tracks, in, it starts happening again. Any thoughts? |
|
#2
| |||
| |||
|
Do you have a midi controller connected? It might be sending out stray data.
|
|
#3
| |||
| |||
|
I do have a controller hooked up - how would I figure out if it was sending extraneous data? And why would it only be affecting one parameter on one instrument in this song?
|
|
#4
| |||
| |||
|
Well, unplug the controller, restart Reason and see if it still happens. For example, my Keystation Pro has a loose fader and if I shake my desk a little, it sends out a stray value, which happens to be mapped to the filter frequency. Very annoying. |
|
#5
| |||
| |||
|
Has there been any parameter automation? I had problems a while ago with a deleted automation that kept affecting the track. I solved it by copying everything to a new project file in Reason... |
|
#6
| |||
| |||
|
I turned all the knobs on my midi controller to zero and the problem seems to have stopped. Hopefully that was the solution! Thanks for the help.
|
| Thread Tools | |
| Display Modes | |
|
|
| | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Automation of multiple parameters | themythamnesia | Reason | 0 | November 5th, 2010 12:35 |
| nn-xt automation problem | chernobyl | Reason | 2 | August 24th, 2010 15:45 |
| automation help please | tasdan | Reason | 3 | May 1st, 2010 17:15 |
| Automation from MIDI-controller! | tacen | Reason | 1 | November 19th, 2009 17:58 |
| Modulator Automation? | jayou | Reason | 3 | January 9th, 2008 12:06 |