e-licktronic Forum

Yeah, totally brilliant. Workflow improvement ideas are among the best things to implement in firmwares.

sebiiksbcs wrote: Brilliant! The old combination was always awkward and I kept forgetting it!

True that, I had many problem with the old combo myself! New combo is very intuitive and so far didn't notice any downside/regression.

I just noticed that starting while in pattern midi sync (from Logic Pro) really behaves weirdly compared to dinsync! (in every firmware version, not a bug I created )
The reason I never noticed before is probably related to me using hardware midi clock (which is a constant-running clock as opposed to most DAWs that actually stop sending clock as soon as playback is stopped). This is quite a common issue with midi hardware, should be fixable. But this does explain why some users are complaining about the midi sync!

Here's another addition: https://github.com/HomoElectromagneticu ... 08/pull/14

Basically this fixes the uber-annoying issue when slaving the Yocto to external clock, in Pattern Edit mode, you stop the external clock and BAM, the yocto resets it's sync mode and reverts to pattern one
also fixes issue with dinsync slave in edit mode not stopping when master clock stops



Annoying slave issue fix:
yocto_firmware_1_0_g_ANNOY_SLAVE.syx



Or better, try a combination firmware of all 3 earlier posted firmwares!
Sysex dump/export + Tap Write + Annoying issue fix:
yocto_firmware_1_0_g_RV0_COMBINED.syx




Basically, together with the 2 other pull requests I made this fulfills my top 3 wishlist of yocto features/fixes.
Besides some possible improvements to the existing patches I made, I'll restrain myself from doing anything new, time to make some music and perhaps improve the prior work

@helectromagneticus, if you are still on this forum and read this, i'm looking forward to code review and possibly future inclusion of my patches into your repo if thats possible..

[quote="rv0"]Here's another addition: https://github.com/HomoElectromagneticu ... 08/pull/14

Basically this fixes the uber-annoying issue when slaving the Yocto to external clock, in Pattern Edit mode, you stop the external clock and BAM, the yocto resets it's sync mode and reverts to pattern one



Or better, try a combination firmware of all 3 earlier posted firmwares!
Sysex dump/export + Tap Write + Annoying issue fix:
[url=https://rv0.be/tmp/yocto_firmware_1_0_g ... MBINED.syx]yocto_firmware_1_0_g_RV0_COMBINED.syx[/url


Dear Rv0, you already have made my day so many times with the great improvements you did, but this time it is incredible.
Yesterday i was jamming whle using the ‘tap’ on the yocto, i love so much that way of programming drum machines and BIM , you do the combo i was hoping.

Thank you so much, you simply make It ALIVE

Laurent

Ethethird wrote: Dear Rv0, you already have made my day so many times with the great improvements you did, but this time it is incredible.
Yesterday i was jamming whle using the ‘tap’ on the yocto, i love so much that way of programming drum machines and BIM , you do the combo i was hoping.

Thank you so much, you simply make It ALIVE

Laurent

Thanks for the kind words, but make no mistake, I only did those last 3 changes, none of this would have been possible without the past work by helectromagneticus (who started this thread and contributed numerous fixes so far) and jvq (who's awesome build tools made it possible for a n00b like me to easily compile the code) ..

Ontopic:
I'm surprised the tap write worked this well because I discovered plenty of mistakes by now in the code of the version I posted earlier.
I've now rewritten the quantisation logic, so that it should also work with other scales. Also made it so that when a note is quantised to the next step, it does not play (as it will already play on the next step). Seemed to make sense.

I'm not 100% happy with it yet though, it may just be my feeling for rhytm or the Yocto's tap button not being very suited for the job, but sometimes I don't get the results I wanted.
I also made a version without any quantise. To compare. Really need to get my hands on a real 808 to do this more accurate :s

TAP-WRITE-only firmware with improved quantisation:
yocto_firmware_1_0_g_TAPWRITE_improved_q.syx
TAP-WRITE-only firmware without any quantisation:
yocto_firmware_1_0_g_TAPWRITE_no_q.syx

FEEDBACK ON HOW TAP WRITE WORKS ON BOTH THESE VERSIONS IS VERY WELCOME

So I spent some time probing the tap write mode on the 606 (due to lack of 808, let us hope it works similar).. And I now fully understand how Roland did it . Once that was done it was easy to adapt my existing code to mimic that behaviour.

As a bonus I also added a new feature in Pattern Edit: Encoder+Tap clears the current instrument.

I made a new combined build containing all my changes so far:
yocto_firmware_1_0_g_RV0_COMBINED_3.syx (= MIDIDUMP+TAPWRITE+ANNOY_SLAVE)
EDIT: UPDATE 8/2: merged with midi slave sync improvements

Individual firmwares:
yocto_firmware_1_0_g_ANNOY_SLAVE_2.syx [info]
EDIT: UPDATE 8/2:
Fixed more issues with the standard firmware in this branch:
- Bugfix: Pattern Midi Sync mode should be a lot more stable now
- Bugfix: Dinsync output in Midi Slave mode was not usable with most old devices


yocto_firmware_1_0_g_MIDIDUMP.syx [info]
yocto_firmware_1_0_g_TAPWRITE_3.syx [info]

you sir, are a scholar and a gent!

Hello all,

It's been a minute, sorry about that. My computer hardware is in a sad state right now, so I haven't been checking in.

rv0 has done some incredible work here. I'm reviewing the code now, but I won't have a way to test the merged code for a couple days while I repair my computer. If anyone has merged the code and can confirm everything works, that would be awesome. At first glance, the features most likely to break from these changes would be the roll mode and MIDI sync when Yocto is acting as master.

helectromagneticus wrote:At first glance, the features most likely to break from these changes would be the roll mode and MIDI sync when Yocto is acting as master.

MIDI sync when Yocto is acting as master is about the only situation that I did not test at all

I mean, I know it still puts out Midisync,
I also know that the midisync it puts out is _very_ stable (Used a MidiGAL MidiCLK clock tester on it earlier)
Doing tap entry (or any other editing) does screw with the clock stability (but still within acceptable bounds, only measured with my clock tester, not audible)
but that's where my testing ends


Also, no need to manually merge to test, you can just use my latest .syx files posted above.

rv0 wrote:So I spent some time probing the tap write mode on the 606 (due to lack of 808, let us hope it works similar).. And I now fully understand how Roland did it . Once that was done it was easy to adapt my existing code to mimic that behaviour.

As a bonus I also added a new feature in Pattern Edit: Encoder+Tap clears the current instrument.

I made a new combined build containing all my changes so far:
yocto_firmware_1_0_g_RV0_COMBINED_3.syx (= MIDIDUMP+TAPWRITE+ANNOY_SLAVE)
EDIT: UPDATE 8/2: merged with midi slave sync improvements

Individual firmwares:
yocto_firmware_1_0_g_ANNOY_SLAVE_2.syx [info]
EDIT: UPDATE 8/2:
Fixed more issues with the standard firmware in this branch:
- Bugfix: Pattern Midi Sync mode should be a lot more stable now
- Bugfix: Dinsync output in Midi Slave mode was not usable with most old devices


yocto_firmware_1_0_g_MIDIDUMP.syx [info]
yocto_firmware_1_0_g_TAPWRITE_3.syx [info]

Hi,

Using the yocto most of the time in expander or midi slave sync and it's all working great now, tap write is great too ! just have to test the midi dump ....

Thx rv0 for the good job

Danny