Does anybody else have this problem with trimming start/end points of a recorded sample (on the latest firmware) :
I have made a recording of an external synth with some silence in the beginning and in the end. When I zoom in on the beginning of the waveform to find the exact transient, additional (“noisy”) waves appear to the left of my desired start point. If I zoom out again, they disappear. The extra waves that appear don’t make a sound, but they just appear all of a sudden when zooming in tightly enough. They are very distracting when focusing in on start or end points.
Ah, I think I get what you’re saying. On a second try, I see that the noise floor waves turn prominent the moment the actual transient disappears from view when I turn the trim encoder to the left.
So you must be right. A little strange to me that the noise floor is that visible, but I think it makes sense to me now.
Yes, that’s correct. So finding the spot by macro view isn’t a problem. I just got confused by the noise being “amplified” when I’m on complete zoom.
I have similiar problems. seems like midi channels dont correspond to the proper midi channels in a daw . I had serum on channel 1 , and the digitakt sends midi data to all channels regardless … cant turn off
Omni Mode ,
Started having an issue where if I hold down a flashing red trig (p-locks) it changes the trig to a “default” non-flashing trig and my p-locks are lost
Naa, it only happens in one track in a specific project. If I redo the trig with a p-lock in that track it doesn’t happen anymore. Also in a separate track in the project that has a direction p-lock (FWD, REV, etc) the first trig of the pattern shows “ERR” when I hold the trig down. I’m thinking maybe the project is corrupt.
Ran into a bug last night when changing plocks in grid mode, as I was changing parameters then using TRIG+FUNC+YES to audition the plock, it would inconsistently bring up the linear/random trigs menu that comes up when you press FUNC+YES. I understand why this might happen because of the shortcuts but it’s a pretty big problem in grid mode if it wipes all of your trigs while you’re trying to edit.
When the menu came up I would often be already pressing yes again because I didn’t hear the sound and would have to press no before I let go to back out of the menu and not wipe my trigs.
I’m hoping there’s a good simple reason some of my notes/samples I play into the sequencer don’t get recorded.I mean that pad number is there,you can see it’s been placed in the steps but can’t hear in the sequencer.Can hear when tapping the note in tho……
Still getting really bad clicks and pops while using grid machine. I brought in a sample, re-sampled in into a fixed length within DigitaktII. Sliced and set linear trigs to be able to mute without run off, and I get clicks while the sample plays back
Oh shit dude you’re so right. I’ve always used that shortcut but usually am using one shot mode so it isn’t an issue.
Also kind of related, do you know you can press track+no instead of func+no
to revert back to previous save state? I saw it in a vid today and had never known.
Cmon man, no need to RTFM @ me, i’ve got it printed out right next to me. Func+yes previews sounds in many scenarios. Also, func+trig+yes is prioritsed over the func+yes pattern temp save shortcut, and in the scenario of doing this in grid mode, it overlaps with yet another shortuct of randomising trigs and is unsure of which shortcut to active, leading to inconsistent behaviour, even the digitakt is confused.
