3phase wrote:1) while being in pitch write mode the back button could just do the going a step back when beeing pressed while the tap button is held.. this way you advance thru the sequence with the tap/next button..but can jump back when you accidently missed an edit .. that safes time and dont interfears with the original 303 conventions.. it appears rather as a bug on the real 303 since the back button just does nothing in pattern write mode.. probably it was originally intended to use it in such a way..
actually, on the 303 it does work in pattern write mode.
And in n0nx0x2 it works too.
Could be further improved by playing the note or allowing to write DUAS while holding back.
3phase wrote:2) when writing pitches the non xox could accept the accent slide and transpose markers ..on the original 303 you need to do that in a second path..but when you know where you want the accent ..why not?
also works in n0nx0x2, but you have to press accent/slide/transpose first, before pressing the note.
could also be improved by allowing any order.
3phase wrote:3) in realtime tap time writing only the tap button works..but maybe one could allow all keys plus the tap button to be used.. again a time safer. But probably too difficult, since the accent and slide info should stick to theire step number as on the real 303.. only the info of the button you use should be over written..
this stuff will be possible in the (now not yet implemented/empty) "pattern record" mode, though this is still a TODO, first the other stuff has to work perfect
3phase wrote:just a bit bad for nonxox users that touch the first time a real 303 than.. would feel a bit limited than *lol*
I already feel like that now when working on my 303s ;)
3phase wrote:Timing on the midiclock is much better now.. before it was over 8 ms late in relation to a din sync clocked 303.. what was ok for a late feeling ..but different to the 303. sometimes the midiclock misses a start.. with ableton as master clock source..when you directly jump on stat again without having stopped before..1 out of 4 times..
this probleem has indeed been reported with the latest OS version. I havent been in my studio for 3 weeks, I'll hope to find some time this weekend to look into this. If you feel adventurous, you can downgrade to 2.08, which should not have this issue
3phase wrote:One other problem with the start handling on dinsync on the nonxox..when the dinsync clock drops for whatever reasons.. you cant go to the settings menu and change the sync mode to internal or midi..it just stucks up to the moment you give i a clock again.. only than you can change the clocksource..with midi that works fine..
just press stop on the x0x and it should be reverting to internal clock.
3phase wrote:so i would say the nonxox is better to be synced with midi..at least that works pretty fine for me right now..
When you use a DAW, you should change the clock setting on the x0x to "fixed width"http://antonsavov.net/cms/projects/n0nx ... .html#sync
"MIDI-to-DinSync CONVERSION METHOD"
This is because a DAW never sends a constant clock (unless its Renoise), so the prediction algo can't work correctly.
Definitely read the manual, there's some cool stuff in there that make it more interesting that a 303 sequencer (imho)