Hi,
let’s say you’d have a MIDI Controller with Buttons.
Would it be possible to trigger Samples with it that are NOT attached to the 8 Tracks?
So you’d be able to trigger FX type samples without occupying one of the Tracks
Looking at Appendix C: MIDI CONTROL REFERENCE in the manual, it seems that Track Trigs and Sample Trigs are independent from each other. But Im not sure if it brings you the possibilty which I described above.
Any help apreciated, thanks!
no 
But there is a mode that uses the trig buttons to play samples in the sample slots.
the Slot mode? thats unfortunately too indirect for live 
[quote=““Herr Rausch””]
Hi,
let’s say you’d have a MIDI Controller with Buttons.
Would it be possible to trigger Samples with it that are NOT attached to the 8 Tracks?
So you’d be able to trigger FX type samples without occupying one of the Tracks
[/quote]
Hold shift then press down until “slots”. Now you can do what you said above.
tried it, works not bad actually 
is it possible somehow to quantize the triggering of the samples? so e.g. I have different loops in the slots and I want them to start after the current bar has ended?
Have a read up on trig modes ie, plays free (I think). I only recently tried this , but you will need a track for this.
yeah I figured that out, I hoped that it was possible without a Track
Sounds like you need a second Octatrack. 
lol Ive actually thought about that like a hundred times
the easiest way to do so is with sample chains… then you can play and record them… sadly then on of your tracks is occupied… but on the other hand you can add cool efx or triglocks to them…
would you mind going a bit into detail how you use the sample chains for FX?
The way I use sample chains for effects, is I use the octachainer app in the files section, i usually use blocks of 16. Load the chain and switch to slice mode and you should be able to access each sample in slice mode. You still need to sacrifice a track to play them though, but it’s a better way to organise them than using slots mode. but then they are reusable across projects, and it’s fairly trivial to plock them. I do the same for sound effects, movie samples, drums, chromatic instrument samples, etc. It’s a pretty amazing part of the OT once you start getting creative with it. With the octachainer, make sure your samples are 16 or 24 bit. OT doesn’t like 32 bit, and the chainer isn’t good at handling them on the fly.
I should note though that you can’t trigger slices from external midi. Well, not properly, the selected slice is always one change behind the midi trigger. It’s a bug in the way the OT processes midi notes vs CCs.
I do very much the same, as just described. I have one track dedicated to FX and ambient/noise samples. I created a sample chain with 4x16 elements so that I can trigger the slices in the OT splice mode (FUNCTION+Arrow Down). On the first page I have for the first eight buttons risers, from 9 to 16 matching impacts, on page 2, I have 4 bar loops with risers and impacts in one slice so that the impacts happen after two bars, so that I can launch the slice and have two bars time and my hands free to do something else. Then on the other pages, sweeps etc, and finally also a few continuous ambient 4 bar loops that can be layered to anything else. 64 slices give lots of possibilities and a variety of sounds. The making of the chains is described in my notes HERE (large pdf file)
This is mostly true, certainly for regular Midi controller devices, but it is possible to trigger the correct slice externally via CC at the expense of a little latency, which may be worth the sacrifice, for FX samples … on the proviso you can do what is discussed here somehow
[quote=““avantronica””]
This is mostly true, certainly for regular Midi controller devices, but it is possible to trigger the correct slice externally via CC at the expense of a little latency, which may be worth the sacrifice, for FX samples … on the proviso you can do what is discussed here somehow [/quote]
really? I found that even if i delayed the note by 10ms, i was still seeing the same issue.
edit: ah. has to be at least 80ms.