so, I had two long one shot triggers on two different tracks. One would play out once, but the other would loop. I went to the SRC setup and both had loop on auto. I turned off auto for both, and things did what I wanted them to do (a once played one shot).
Why?
Also in audio editor attributes, there are options for once, loop, and ping pong. How do those relate to the SRC setup choice?
(I have other questions, one is how does length in SRC relate to hold and release in the AMP main page?)
Thank you all.
(I have been reading the past post, sometimes I did not grasp them fully because of the jargon).
When “Auto” is selected in SRC setup menu, the mode you chose in attributes page is used.
You can still override attributes in SRC setup.
So the reason why the sample on one track looped was probaply due to sample attributes and “auto”.
Amp envelope settings determine how long you’ll actually hear a sound. A sample could loop, but a short amp envelope could make only a short click audible.
First of all thank you, Ok… so SRC is the boss. Why are there two options. I believe that I can not use a LFO, or p-lock to change the behavior of the SRC setup menu, so why?
I get the whole length thing now… you have to turn it on in SRC setup and then you can shape the start and end point of the loop/sample… cool and then you can control how long the sample is held for in the AMP main… and all that can be p-locked.
Wow … this changes everything for me. I just did cool things, in five seconds, knowing this. Now samples become much more flexable for me.
(I just want to note, to my knowledge, the manual is not too clear on these… or at least it is not included in the descriptions of the parameter menus).
Static and flex machines load with “Auto” as their default settings, so you could prepare your samples with saved attributes and they will loop or not correctly with the default settings.
You could also load different samples into a track as long as it’s still on auto and they will loop or not according to their attributes.
Could be handy in a live scenario for example.
Crazy eh^^ btw, you also have scenes to cause more havoc. Active scene locks override p-locks.
Btw, If you have trouble with the OT manual, have you read Merlins Guide ?
I just re-read Merlin’s Guide. I read it in the past, but it takes awhile to integrate all the infromation. I also am using the manual. It is a complex machine with nuanced flows.
For example, I watched a you tube vid where, the person was sampling and he would just turn off the record trig before OT would record over it. It works, and that is what I have been doing.
So yesterday I wanted to record a long sample, I could not rember who to do it… after searching around, I came across how to do a single record trig. That worked. I never even thought about how that could change my daily workflow…
until, this morning when I re-read Merlin’s Guide. Learning is so contextual (meaning in this case, I need OT to do x… once x is accomplishing, the task is put aside and I move on) and sometimes it is difficult to see the bigger picture. Peace and Thank You all
and then you can control how long the sample is held for in the AMP main… and all that can be p-locked.
