Help!
-
- KVRer
- 1 posts since 3 May, 2020
Loving Tracktion, when my brain gets it. Having a weird situation though and have tried to work out whats what but am at a dead end. Am using synth1 vst with a particular preset and recording 'takes' over a loop. Worked well, but for some reason, instead of keeping the same preset it loads another preset at the being of the loop. Looks like a default saved preset within tracktion, that I dont recall ever setting up. Totally cant do takes anymore becuase if it, partly because it swaps to a 'whistle' preset of all things. Is there any training/ tutorials on the midi input presets, because the preset it switches too automatically appears in slot of of bank 1, the rest being empty.
-
- KVRist
- 367 posts since 26 Feb, 2017 from Lituania,Vilnius
turn off the input or with the mouse click on the input, a keyboard will appear and set Program, to choose
to Bank 1 and choose numbers.
to Bank 1 and choose numbers.
Orion, Bitwig, Tracktion, Mixbus 
Win 10, intel i7, ram 20 steinberg UR22mkII
Win 10, intel i7, ram 20 steinberg UR22mkII
-
- KVRAF
- 1603 posts since 9 Jan, 2018
What version are you using? I had this issue quite a bit with T7.
If you turn off the loop, and put a second copy of the clip right next to it, does the problem continue? Or only when the first clip is looped?
If the problem goes away without the loop, try looping the second clip. If the problem doesn't continue, then try deleting the original clip and loop the second one.
If the problem does continue, there's some erroneous control information hidden somewhere in the clip.
Tracktion (older versions) and Waveform can save program information in two places: in the plugin itself to the right, as well as in the clip itself. It's the latter that can be annoying, because it can be an issue with the vst itself, causing program changes mid-playback you just can't get rid of. This seemed to happen to me a lot with older plugins: not sure if a program change command vote mapped to a different controller or what, but it was always limited to the same plugins, project after project.
Never seemed to be a T7 or Waveform problem itself...just the plugin in question. Some could be fixed by the above technique. One I had with Xpaand was so bad, I had to copy and paste the note information into a new clip and delete the old one. Xpaand just wouldn't stop flipping to a different sound, so it was something in the vst itself that was interpreting some aftertouch or mode wheel data as "switch to a different patch."
If you turn off the loop, and put a second copy of the clip right next to it, does the problem continue? Or only when the first clip is looped?
If the problem goes away without the loop, try looping the second clip. If the problem doesn't continue, then try deleting the original clip and loop the second one.
If the problem does continue, there's some erroneous control information hidden somewhere in the clip.
Tracktion (older versions) and Waveform can save program information in two places: in the plugin itself to the right, as well as in the clip itself. It's the latter that can be annoying, because it can be an issue with the vst itself, causing program changes mid-playback you just can't get rid of. This seemed to happen to me a lot with older plugins: not sure if a program change command vote mapped to a different controller or what, but it was always limited to the same plugins, project after project.
Never seemed to be a T7 or Waveform problem itself...just the plugin in question. Some could be fixed by the above technique. One I had with Xpaand was so bad, I had to copy and paste the note information into a new clip and delete the old one. Xpaand just wouldn't stop flipping to a different sound, so it was something in the vst itself that was interpreting some aftertouch or mode wheel data as "switch to a different patch."
Spotify, Apple Music, YouTube, and even Deezer, whatever the hell Deezer is.
More fun at Twitter @watchfulactual
More fun at Twitter @watchfulactual