Separately from this, there was an issue in the Tracker firmware that seems to be marked fixed in one of the 1.3.0 betas, and hence in the final 1.3.0 as well: Polyend Tracker does not sync to midi clock properly As long as youвЂ™re using the same MIDI clock master and the sending nor the receiving end isnвЂ™t completely broken, the clock compensation setting should always be kept the same once you set it once. Only you can hear whether the devices youвЂ™re syncing start the playback in the same phase / at the exact same moment or not, and the amount of positive or negative latency compensation you need can vary from master clock device to another. The delay is dependent on the audio / MIDI latency and synchronization of the other device(s), so it cannot be a fixed value in the receiving end.

To put it other way, thereвЂ™s a positive or negative delay between receiving a MIDI clock tick and the master device actually outputting what should be played on that specific tick. The delay compensation means that depending on what youвЂ™re clocking the Tracker with, there may be an offset in the playback between the master and slave device. Thank you for illuminating your attitude towards your customers who are unable to use advertised features. Cheers!ДЄccusing your customers of being ridiculous is very revealing, along with your previous comments. This is getting somewhat ridiculous so IвЂ™m bowing out for now.

If it was the correct design decision and you are happy with it, why add the feature to not have to power cycle? Or are all Polyend bugs just features that the user doesnt understand? I just thought that it was farcical to claim that being able to exit it without turning off the machine is a вЂњfeatureвЂќ and not a bug, especially as you have now added that feature. I completely understood that was how you had chosen to implement it. What weвЂ™re adding in 1.3.1 is the ability to exit the game selection menu before you decided you want to play a game at all. The game emulator takes over the device because there is no multitasking in the hardware. I was listing the bugs that are being commonly experienced in a вЂњstableвЂќ release which was unusable unless you used the вЂњbleeding edgeвЂќ betasвЂ¦ If youвЂ™re not installing the betas, you wouldnвЂ™t ever see this. What is released are two betas of 1.3.1, and the вЂњnotes in the project being changedвЂќ problem was a regression in a beta release.

IвЂ™m not sure that accusing your customers of a lack of understanding is helpful, especially if you dont know their background and experience. I also understand what alphas and stable releases are for. I actually do understand what beta releases are for, thank you. a Renoise issue, but only a guess.You seem to not understand what beta releases are for. It's hard to say for sure, but if I had to guess it sounds like something on the MIDI end of things vs. That is always how Renoise has worked for me with MIDI. In fact it will add a new column for each note I press while not releasing the others (basically to capture chords). If I press the first key, hold it down, and then continue to press a second MIDI key (on MIDI keyboard), it will create a second column and add the second note.

If I press and release a single MIDI note on my keyboard, it creates the note data in the column, it *does not* create a second note column, and it respects the step length. recording and capture live during playback?ДЇor me, when in record mode and manually entering notes (assuming that's what you're talking about). Do you just mean putting the pattern editor into record mode and entering notes one at a time vs. Does it always jump 2 steps no matter what you set it to or does it double the steps? Also I'm not familiar with the term 'step recording' in regards to Renoise. It sounds like you're maybe getting double MIDI events somehow.

Renoise begginer questions auto seek