![]() ![]() I would have expected the device to smooth the movements out internally. I knew this before buying, but I though this would only be a precision issue, not a smoothness issue. That's 128 steps, which is too few for a 100mm course (each step spanning across 0.8mm - supposing the resolution is linear, er I mean logarythmic like the dB scale - well anyway). bit depth : basic MIDI controls only have a 7-bit resolution. This can be due to one of two things I can think of : This renders the motors basically useless in mix automation ! ![]() The problem is way worse on the way up than on the way down. but there is a lot of quantization (multiple tiny starts and stops, which must be what you saw in slomo) making slow movements as noisy as fast ones, which is very noisy. I tried moving a fader from the DAW like you suggested, and noticed two things : Īll in all, I don't regret the purchase, because getting a control surface is still a life changer, and there's no real competition in that price range anyway. Only 6 characters per track name brings me back to 1995. This is the only thing that bugs me a little, so far. The faders align well enough with each other, but they don't align with the markings on the panel. I could have seen that in the promo pictures, so there's no point complaining about it now. There is no "pause" button: only play and stop (and rec, and previous/next marker). I could I dig a little for a way to make that work, but it's not too bad anyway, since the pots are stuck on the pan function by default, which I suppose if the one I'll want most of the time. The first (and only for now) function that doesn't work directly out of the box is the pot assign. I still have to try make them move slowly, to appreciate the noise. Of course, I suppose this is the worst case. I haven't done some proper mix automation yet, but just project changes, when all faders have to abruptly adjust at once, is very noisy. But it's not too flimsy either.Īfter I've worked a few days with the X-Touch, here are a few quirks I stumbled upon: If it does not, I’ll upload some screenshots or something.: Beautiful setup ! : Thanks for the link : The X-Touch doesn't feel like it's built like a tank, on the other hand. I hope this clarifies my previous explanation a bit. When I “get rid” of the effects column (by pressing the - symbol/delete the last effects column) and then add it again (by pressing the +), the problem does not seem to continue. ![]() Today, I think I actually found a bit of a work-around for the problem… or well, it seems to “solve” the problem somewhat. It also changes sliders (often setting them to their lowest setting) and more stuff like that. It even turns off plugins on that particular channel altogether. Whenever I do this and use pitch bend commands, eventually Renoise starts to act them out on other parameters. Could you please explain what you mean with:īasically, the problem starts to occur when you append a note column on a track that has pitch bending. After and before adding new note columns, Renoise only sends out pitch commands to the VST?īut maybe I did not understood you. ![]() I’ve tested this and could not find any “reset all parameters” issues here. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |