Within one bank I created 3 different Arrangements (songs) and used one separate Part for each of them ( Parts 1-3). I played a live show a few months back and during my set I was able to switch between arrangements and they would load and play smoothly with no issues.
Haven’t touched the OT in a few months, but just opened it up to run through my set and now when I switch back and forth between arrangements I’ve noticed the Parts don’t automatically change like they used to, so that means the Arrangements are running sounds from Patterns they aren’t supposed to and are all messed up. When I manually switch the the appropriate Part for an Arrangement, it plays perfectly fine.
I noticed in Part 3 that there is an asterisk telling me a change has been made. I can’t recall doing anything with the OT since my live set, except for opening it up and listening back to what I made a few times. It’s possible I accidentally hit something to Part 3 that would have caused this, but I also don’t hear any actual changes to samples in Part 3, at least not from what I can tell when I play the Arrangement assigned to that Part or any other Pattern (when I’ve switched the Part).
What do I do? I’m worried about hitting Reload in Part 3 but it seems like that might set it straight? Terrified of losing all my work.
Despite that does not really answer all your questions: however you managed to play Parts with arrangements, selecting parts to play is definitely not included in arrangement data. If so we would have a table entry to select which parts to apply. Sadly, really sadly, we have not. Hello Elektron However arrangements play the parts that where selected, which is stored in the pattern itself. So it rather plays what part was preselected (assigned) to the pattern no matter how many arrangements are provided.
Terrified: -> backup that project before doing further work. That might mean in your case not saving intentionally but turning machine off to USB mode and backup manually and make copies of the full set of work files and also strd files, take care the machine is not running the sequencer or recording while turning off. Why? Because as soon you hit “save” you force the work files to be exact copies of the new overwritten strd files which is what you want to avoid right now.
When you load or save the project intentionally you actually read or write .strd files I guess. And when you just let the machine use the last state reloading as is it takes the .work files which it writes constantly in the background. If .work files are missing it takes the .strd files. Knowing that you can take advantage of that behaviour and make changes to listen but/by not saving. Changing parts is a workload applied onto the bank file unless you change sample slot entries which goes into the project.work respective project.strd file.
Another tip: making copies of bank files and renaming them appropriately to the desired bank number you want them to be is working perfectly fine, banks have no information in them which bank they have been, it really is just the fixed filename scheme that sorts them.
next: reloading a part, reloads it from the very same bank file, in case there is a work file, you know it reloads from that work file. Which is meant to be like that cause you figured out you can store a set of 4 parts (as imaginary: 5,6,7,8 to recall) manually in the same bank.
It seems like after a few times of switching arrangements, each time manually changing the part to the appropriate one, the parts now seem to be changing automatically again when changing the arrangements, like they used to.
No clue why this happened, but I just saved the project and hope it doesn’t happen again.
Parts changes require trigs to be effective.
Is it possible that you removed some trigs, are they still there ?
Firstly you can SAVE AS NEW, to keep current state. SAVE after, in order to go back to current state if necessary.
Then go back to previous/original project.
You can RELOAD saved state, eventually RELOAD CURRENT BANK if the problem concerns only a specific bank, and if you’re afraid to reload a too old state.
I think you’re right — I must have accidentally hit something in trig mode, because I also then cleared a parameter lock accidentally (it must be a key stroke I often mistakenly do not knowing what I’m doing). The project had previously been saved. When I saved it again this time (I guess after I cleared that trig?) it went back to normal. Sorry for anyone following this for a solution, I really don’t know what I did, but I do think it had something to do with the trig. Thank you!
the asterisk indicating the part was changed appear as well when different scene A or scene B are assigned to play the active part, changing them back to their former state does not clear the asterisk.
In short: the asteriks 1 * ONE should appear when you perform properly and make use of scenes.
The real deal: selected Scenes are stored in part’s. Reloading a part selects the one that was stored. The arranger can overrule the scenes to be selected as soon you open it or hit play while on.
@NikkiRigatoni
When you turn on the arranger and the selected (or first) row points to another bank & pattern, this bank and pattern will be immediately selected and take the chosen part given by this pattern, following then also chooses the scenes given by the part and then applies overruling of the properties (sceneA/B|Tempo|Mutes|MidiTranspositions) of your selected arranger row. The arranger works like automation but the machine does not care who changed the scenes, the scenes where changed the asterisk must indicate something changed.
Also tells you that for your particular scenario it might be good vision to make use of scenes to keep those properties in a fixed state you want to come back to for sure. Your issue is more you figured out a powerful tool (parts) and want to apply the logic you learned in parametric fashion but exactly this one scenario is not supported (arranger selecting parts of the same pattern) and scenes do not help much when your expected performance relies on different machines / slot entries that only come with different parts. Which furthermore means you will need to have another bank do that for you, nothing wrong with duplicating a bank file and preselect the parts different than in the bank you copied from.
well we know… scenes can store selected SL parameters of a sliced or (default sliced or unsliced 1 of 128 chunks) audio when @NikkiRigatoni uses this method, if practical at all for the user. Plus the arranger does not fade the slider to apply the scenes, you simply set the 2 or 1 scene with ARR or take the one selected from the part to play and apply the interpolation of the values according to the slider position. Knowing that allows to immediate sample changes in example with a dedicated Scene… But that workflow might not fit, depends if slicing is a familiar workflow yet, maybe a bit overwhelming for a new user
@sezare56 I was referring to samples, you were right.
This didn’t have anything to do with scenes – I know that for sure. I think I must have created a trig and changed the Part within one of the patterns somehow.
However arrangements play the parts that where selected, which is stored in the pattern itself. So it rather plays what part was preselected (assigned) to the pattern no matter how many arrangements are provided.