What do you wish you knew when you first started using the OT?

[OHEXOH]

1. To use mono files for most things as they loop better—there’s only 1 zero crossing to worry about on a mono file.
2. That I should use the Midi side of the OT sooner - when I finally got round to that, my mind was blown - P-Locking the Arp FTW!!

[RiddimFernandez]

thanks!
so rytm as sample track1
and analog4 as sample track2
both as through machines.
is this correct that effects will be on everything on track 8?

thanks again, very much appreciated.

[basehead617]

Yes that’s correct. And like I said with THRU machines you can also have separate pair of effects on the rytm vs the analog4 before even hitting the MASTER.

Technically you can have even more than that if you e.g. in that scenario use track3 as a NEIGHBOR machine, the A4 will go through the effects you set on both tracks 2 and 3.

[RiddimFernandez]

wow cool. thanks!

[nuuttipukki]

Page + clear combo (I was turning encoders to default locations for more than year ) … Somehow I forgot or skipped in manual, but when your track behavior is weird, clean the pages and check active scene… Voila, it works.

[umonox]

knowing that i actually CAN copy and paste Scenes for ages i tried to get the next scene close to the prior scene so that i can have a smooth transition between them. while reading the manual one day to find out how Pickup Machines work, i stumbled upon the Scene Chapter and read something like “… copy and paste scenes to a new location …” and i was like: WTF?! i CAN copy and paste scenes???

[Hitachii]

As one ought to, I’ve been preemptively poking through the manual and watching all the walk throughs, reviews and tutorials. Still, the sage wisdom of battle hardened elektronauts can’t be overstated.

Personally developed workflow tips? Anything casually mentioned in one sentence in the manual that you rediscovered later and changed your life? Writing philosophies you’ve found embedded in the hardware?

Anecdotally I just discovered kit/pattern/sequence saving on the DT which wasn’t a priority when I originally read the manual, and all the forum topics about using the same kit across multiple patterns never mentions sequence saving! Looking forward to having parts to get around this anyway.

Mainly looking for positive or neutral things. I’ve read plenty of critique (and seen what it does to threads!) Thanks!

[Gino]

Congrats! (soon )

I’m using mine to record and compose guitar layers, so may not be the same use case but…

I wish someone told me to NOT use record trigs and learn to use the OT without them first.

And to explore and embrace Parts, as they are one of the best things about the OT IMO.

Oh, and to take the time to get familiar with all the places gain is adjusted so that you can achieve unity gain for sampling. It’s worth it

FWIW - I documented my OT experience so far here: OT OTW (on the way)

[darenager]

Learn the structure:

4 parts per bank (of 16 patterns) parts are akin to kits or programs.

8 recorders are always available, independent from tracks and global per project.

128 flex slots and 128 static slots per project

Projects can (but don’t have to) contain multiple songs, within the limitations listed above.

Slots can have different settings per part, for example slot 1 could be different settings for the same sample across your project, but if you change the sample in slot 1 it will be reflected in all parts that use it.

Slice chains are a good way to have lots of shorter samples loaded into 1 slot, if 128 slots is not enough, there are lots if good creative uses for chains as well.

There are probably some other things I have missed but that is a good start.

[AdamJay]

Posts moved to existing thread. Always search the forum for existing discussions before starting a new thread!

[igtheflig]

Sync the project to the card before removing it

Oh yeah. And never get it wet, and never forget, no matter how much he cries, no matter how much he begs, never feed him after midnight

[Prof_lofi]

How to put it into ‘high quality mode’:

OT - sound quality

Hi Kegeratorz, To change to 24bit go into Project>Control>Memeory and change Flex Format to 24 bit and Recorder Format to 24bit. Then in all of your track settings (Flex/Static/Master (if you have that enabled), go into FX slot 1 and select [none] and then copy that page to FX slot 2, and then copy that over to FX slot 1 and 2 of all the remaining tracks. Then go into each track and turned off Time Stretch (double click SRC and TSTR is the time stretch setting) [Apologies if you know this but…

[Supercolor_T-120]

I had it for three years before I picked up a footswitch and fader box to go with it, and I REALLY wish I hadn’t waited so long.

[reeloy]

…only 128 slots to drop samples…!?..ahhhh, sample chains that contain lots of single samples at once per single slot changes the whole game…

parts…!?..ahhhhh…kits…

countless ways to rome…stop bothering…start flowing…

apart from that…huuuuuh…lot’s of muscle memory needed to grasp all the double feature functions all over the swedish ballpark…takes time…but once u got it…
it’s all klak klak zak zak…

[sabana]

Importing my entire sampling collection was pointless as less is definately more on the OT.

[garfield]

I wish I had known that recording buffers arent saved automatically…so I had to train myself to always save a sample to flex before editing

[Supercolor_T-120]

Early on I got in the habit of always saving all my parts before saving my project because I couldn’t remember whether saving the project saved the parts in their current state or their last saved state (if you have unsaved changes in your part when you save your project, they will still be flagged as unsaved) and I didn’t want to break up the flow of working on whatever I was working on to check the manual. So three or four years later I still can’t remember if I need to save the parts before I save a project or if saving the project is enough, even though I’ve checked the manual a couple of times and seen the question answered on here a few times.

I wish I’d just checked the manual about it those first few times when I was still learning the basics so I’d have it properly memorized and maybe save myself a few keypresses.

[randy909]

I wish I would have ignored parts for a while at first. I would have just created a new bank each session and made a new project when I ran out of banks. I would always have part 1 assigned. I would still have been surprised when my changes to pattern 2 showed up in pattern 1 but it would have been easier to reason through if I was only ever using one part. It took a while to get used to. I still have to check part assignment a lot to make sure I’m not going to wreck my other patterns. I really need to start using a template…

[marccc]

i am stll struggling with this. are allparts saved when saving the project?

[forest]

@Clancy

OK I tested and this is what I worked out:

When you power down - your parts (all of them) will be as you left them.

When you change to another project and change back again - your parts will be as you left them.

When you start actively saving projects and parts things get a little more complicated.

If you actively SAVE your project you then have TWO states in stored in OT memory:
1- The SAVED project. (Which is like a snapshot of how your project was when you saved it, including parts)
2- The CURRENT state of your project, which includes any changes made after the save.

If you then also actively SAVE YOUR PARTS you will have THREE states stored in OT memory:
1- The SAVED PROJECT, including the parts
2- The SAVED PARTS, which can be different to the parts saved with the project
3- The CURRENT STATE of the project, including any changes to the parts since the last save

Any time you actively RELOAD using PROJECT > RELOAD or PART > RELOAD (which is different to just turning power on, or changing projects) you will OVERWRITE the CURRENT STATE of your project or part with the saved version.

Counterintuitively, saving parts actually makes your parts both safer AND more vulnerable. This is because the key combination (FUNCTION + CUE) to RELOAD a previously saved part, and overwrite your current part settings, is very easy to make by accident. This can’t happen if you have never saved the part (You just see “SAVE PART FIRST!” message and your part stays intact).

Merlin’s guide details a nice ‘back to base’ creative use for this quick parts reload function, and I’m not saying it’s a bad thing, just that it can be more or less useful depending on how you use the OT. Reloading a project, on the other hand, requires a menu dive. I find it useful as a snapshot backup, but of course I still get into saving parts because it’s good to have them recallable independently from the project.

Another backup method, which is easier to keep track of, is saving renamed versions of your project as you go.

But in answer to your original question - YES, saving a project saves the parts.

There are still loads of ways to mess up (!) but YES, saving a project saves the parts

from another thread