Just tried this with a lock trig on BR, OVER, and SRR on the FX page of DTII.
Found the same - for BR and SRR, FUNC plus parameter moves to predefined values. When editing a lock trig, the values change normally i.e. moving up and down by the standard values, not to predefined ones.
@verdurin Thanks for checking! I guess itās not a bug then. Probably an omission, or a deliberate choice.
FYI, thereās a dedicated thread.
Hi Patrik, I communicated with you over support email a while back about this issue and I just wanted to send you a heads up that I submitted a copy of my affected project to you via email. Itās been a while since you requested it and wanted to make sure you receive it. Thanks for the help!
I will link my video posted in elektronauts which shows the issue, so far it has happened once a day for 3 days.
Some amount of recent patterns will have sequencer data on startup but no track data, the pattern has a light, even a name, a full sequence, but is loading my default kit that my project wouldāve had before the previous session working on the track. This has happened to both midi and audio tracks, ive thankfully noticed pretty soon after (next day) and remembered what i was doing and have had to recreate sounds from scratch which obviously will be reaaaaallly fucking annoying at some point, hasnāt been too catastrophic yet.
https://www.facebook.com/share/v/174hSMZU2D/
I might have found a bug, but before making a ticket I want to make sure:
When I select a sample, use the slicer machine, set the slice points, then when I select this very same sample in a different pattern (or even in a different project) with the slicer machine, the previously set slice points should show up, right? I remember reading this somewhere⦠I tried this with one of my samples, but unfortunately the slices appear only on the pattern I originally defined them. If I use the same sample on another pattern, with the slicer machine, they are gone ![]()
I would think that is expected behavior.
Perhaps itās possible to save the slice data with a preset, but I donāt think it would automatically save with the sample.
Apologies if I am misunderstanding the issue.
No, I think you understand it correctly ![]()
It is just that I read this somewhere and it would have been pretty cool since it can save a lot of time. But I will save it as a preset then, that should be fine too.
Another way to think about it is: if you want to slice the same sample in two ways in two different patterns, it would be impossible with the behavior you mentioned above. Iām pretty sure the slice data belongs to the sound, which in turn is saved in preset, kit, etc
Summary
Yes, I was thinking about that as well. I could bring a counter-argument, but still, making it into a preset is the only solution that will fulfill everyoneās needs. ![]()
I seem to be experiencing the same issue of stuck notes when using DT to pass on the midi from an external keyboard to an external synth, but on track 9. Changing each midi config setting one by one and retesting has not helped. Restarting hasnāt helped. Will try replicate on a new empty project and other tracks. May do firmware upgrade as last resort (a real pain since I donāt use a pc).
So just reporting back that the issue does not occur on a new blank project. Big relief as I was thinking I would have to find another midi sequencer. Bit taken back though to encounter buggy behaviour on a hardware sampler that has been around now for a while.
I really wish they would sort out the live midi recording. I constantly get notes that erroneously have either min or max note LEN values. Iām surprised itās not talked about more, itās a massive issue for me.
Does anyone else notice patterns overwriting eachother (like phantom pasting). It sometimes happens when Iām quickly going through patterns, holding PTN + the pattern number + STOP ā PLAY (using those 4 buttons very quickly) . Iām like āhow am i accidently pasting patterns when Iām not even pressing the FUNC buttonā. Iāve lost a few patterns to this now and idk if itās something Iām doing wrong or a bug.
If hold all 3 together, thatās a pattern paste. Iām guessing by ā+ā you mean āfollowed byā (rather than āat the same timeā) and youāre accidentally doing the 3 together ?
ohhhh mb. i didnāt know that
Thereās a bug in 1.15A when using MIDI presets. Letās say you set up a MIDI track to control an external device and save that settings as a preset. When you load that preset to another track the selected MIDI channel shown under SRC is completely ignored. The data is instead sent over channel 1. To make it work youāll first have to select another MIDI channel, then send a PC message and finally select the correct MIDI channel.
Even worse the CCs are also not sent correctly. Instead of the selected ones it sends various others. So you will probably change totally different thing as expected. So far the MIDI presets are totally useless.