New Experimental OS for x0xb0x adds DIN Swing

[phono]

since this is another firmware i guess this deserves a sticky

[pangrus]

I've found that in "pattern sync out" mode the midi clock is not working anymore.
Double checked that in Sokkos 2.0 is working perfecly.
Furthermore, the midi-sync in Sokkos 2.0 is working well, I can't discern any delay or misallignment.
Can someone else test both the firmwares to confim this?

[Omsk411]

I've found that in "pattern sync out" mode the midi clock is not working anymore.

How do you mean? "Pattern (Sync Out)" is the normal mode I use and I find it works great. It takes MIDI Clock input and sends DIN Sync Output. This is what you're referring to, correct?

As things stand currently, I have no x0xb0x to test any of the latest reports. After spending the weekend creating this firmware, my Mode Machines x0xb0x shat the bed (the filter broke) and I had to return it. I'm waiting for a new x0xb0x from x0xsh0p.de and will then be able to get my hands dirty with code again. I never tested the swing with pattern reversing, so there may be an issue there. Someone also stated in an earlier post that the TR-606 and TR-808 seemed to be freaking out at moderate swing levels and I should be able to test that, too. So far, I've only tested the DIN Sync with the TB-303.

I expect at least another week before I have my new x0xb0x in hand, so please be patient -- I'll try to post again once I have some new information/results to report.

[Altitude]

This bug is confirmed. Pattern sync out no longer sends midi clock. It is supposed to send BOTH sync24 and midi clock, you must have accidentally disabled it

[elektrovolt]

Yesterday I played the b0x with your firmware live and it did a good job. only the sync start-stop is not really handy, I would prefer a reset at the next pattern start just like the mungo sync. I really don't know if this would be possible...

[antto]

Pattern (Sync Out) means Internal_Tempo & Sync_Out

otherwise if the x0xb0x is slaved:
MIDI - x0x sync's to incoming midi sync, and converts it to dinsync
DinSync - x0x sync's to it, and converts it to midi sync

[Altitude]

..

DinSync - x0x sync's to it, and converts it to midi sync..

You sure about that?

[pangrus]

Trying to clarify:

Bug#1___When in "Pattern Sync Out" mode, the XoxBox generate both the clocks, the Midi and the Sync24. In the latest version of the new experimantal firmware, the midi clock is delayed by a large time, such 1/2 second, so the external midi machines are starting after the xoxbox and obviously are going out of time.

Bug#2___When in "Patt Midi Sync" mode, the Xoxbox is slaved to the external Midi Clock, and generates the Sync 24 signals. Here there is a very short misallignment (a pulse?).

[aminoacid]

have you tried with other machines and other midi cables to sync with?

[antto]

..

DinSync - x0x sync's to it, and converts it to midi sync..

You sure about that?

that's how it *THINK* it should work, i don't have any dinsync device, so i cannot test it myself
but the point is: when the x0xb0x is not Master (aka it's sync'ed to another device via either midi or dinsync) - the x0xb0x will provide the *other* sync type as an option too
i mean - if you got a TR-606, sync the x0x to it via dinsync - the x0x gives you midi sync additionally, so your midi devices can now be sync'ed from the TR-606 too (which itself doesn't have midi)

and vice-versa (for the case of midisync -> x0x -> dinsync)

i could be wrong tho

[aminoacid]

i have sokkos.

and we tried to sync all our gear for a live gig with a mc202 as master through the xoxbox.

but the xox didnt pass on the sync via midi...

[Altitude]

thats what I remember as well, only midi->sync24, not vice-versa

[antto]

hm..
i think there is no reason for it NOT to do convertion both ways

iirc, the x0x mainly wants dinsync to operate, it converts midisync to dinsync.. yeah, you're right.. but midisync-out can be implemented too
dinsync to midi convertion is easier, since you don't have to deal with the 48 vs 24 ticks

[pangrus]

have you tried with other machines and other midi cables to sync with?

Everything works perfectly with Sokkos 2.0 so it's not a problem of cable or drum machine.
I'm using a Korg electribe ER1 and a TB303, I can use the Electribe or the Xoxbox as master.
I'm very happy with Sokkos 2.0 but the swing and the start-stop on Din Sync are great features.
So I'm available for testing.
An help from Sokkan can be useful, and if Chad (Omsk411) agree they could unite their efforts to give us a stable and final firmware realease (that is now sokkos 2.0 IMHO).

[Omsk411]

Hello everyone,

I'm happy to say that I've got a new, working x0xb0x here lovingly built by banned at x0xsh0p.de so I can finally tackle the firmware issues after a month of downtime.

Thank you all for your reports. They were helpful and I've managed to address two issues so far.

1) MIDI Clock Out now works in PATTERN (SYNC OUT) Mode.

2) I've added a selectable MIDI Clock Sync setting when syncing to incoming MIDI Clock.

About that last issue: When I connected my x0xb0x to my Elektron Octatrack, I found that the x0xb0x was one MIDI Clock tick behind the Octatrack. I "fixed" this problem in my previous firmware versions but never checked it against any other MIDI Clock master devices. After a few of you reported that the x0xb0x seemed to be ahead of the beat, I tried some other devices and found that the results are different depending on what device I use as the MIDI Clock master.

As it turns out, using the Elektron Machinedrum as the MIDI Clock master resulted in my x0xb0x being one MIDI Clock tick ahead of the beat, just like others reported. This points to an issue with the Octatrack since its MIDI Clock output doesn't seem to be exactly the same as the Machinedrum (and likely other devices).

I've therefore made my MIDI Clock "fix" selectable during runtime. By default (on power-up), the fix is not applied. If you find that your x0xb0x syncs properly this way, then you don't need to do anything.

However, if you find that your x0xb0x is behind the beat, turn the Program Selector to the "USER B" position. This will apply my "fix" which makes it run in sync with things like the Octatrack. To turn the "fix" back off, choose "USER A".

NOTE: Keep in mind that, after you choose USER B, you must rotate the Program Selector counter-clockwise to reach your preferred operating mode. If you rotate clockwise, the selector will pass the USER A position which will turn the "fix" off. The same thing is true in the opposite direction: After you choose "USER A", rotate the Program Selector clockwise to reach your preferred operating mode.

I hope everyone finds these fixes beneficial!

-Chad