In live mode the aboy would have to send a row position per channel.
it coul be great also, for live mode, to send a row number as soon as it it gets cued (but using a differnet cc)
These feature would also handle the loops and would support going back into the song.
two things that cannot be done with midi clock

Yes, that would be great. This would let LSDJ be master for a DAW or other sequencers/gear listening to row number.

On play, LSDJ could send both row number + a message containing the current tempo, and then ticks for a few beats.

The aboy can send midi clock using the tempo message the first beat, and the tick interval after that.
It would be even more awesome if new ticks were sent if tempo is changed during a track, keeping the sync.

Maybe I'm overlooking something.. But this should be possible, shouldnt it?

What delays are you all using? I upped mine to 100 and it got rid of those errant clock messages seemingly.

Wouldn'it be even more simple if lsdj itself would send a CC corresponding (somehow) to the phrase number?, or to the song row number?

Ahh!   that is actually pretty cool

CC range for LSDJ out is 0x00 to 0x6F due to aboy using the first bit as a start bit, 0x70 to 0x7F are used as commands, such as transport start/stop, message type, and sync messages (which were disabled) 0xFF translates to 0x7F because of the one bit being used as a start bit. 0x7F I believe was the sync message command from lsdj.

I've noticed the clock out bits happening whenever.

my device reads a cc and value every LSDJ step (1/16, right?)  counts the time, divides it by 6 and returns 24 sync ticks per 1/4 note.   After i got the rogue stop commands sorted by changing the bit rate delay, it seems to be working really well. Granted, my songs are pretty simple and Im using one channel just for the clock cc's.   It may get bogged down and glitchy if one were using it with some complicated tracks w/ elaborate tables.  Mine ran all evening and seemed to stay in sync (audibly at least).    The sketch is pretty simple... pretty sure it could easily be rolled into the Aboy code, but im not sure where to start.
Ill post the code as soon as I can figure out how to use Github (!!i know)   in the meantime, if anyone really wants to check it out,  you can PM me w/ you email and I'll send an attachment.

One weird thing that i noticed while working on this,   whenever i sent a CC value of FF in LSDJ   (seemed like any CC on any Channel)  arduinoboy would return 0xF8 - midi clock and no cc command.   Not sure what is going on here, but it was totally messing me up for a bit.   happened with both the new and previous versions of Aboy and their respective LSDj releases.

Ive done cc to a tap tempo that worked ok. Your device may vary.

I guess the bug is that it shouldnt send ANY clock byte in midiout? The clock start and stop without ticks wouldnt do anything as well, right?

What about adding a CC command out per beat instead of tick? That way the GB to aboy stream wouldnt be overloaded. Also you could stop sending CC after a few beats.

I actually tried this but couldnt get the sending of midi clock out of the aboy stable enough.

I may have been wrong on Midiout mode. Bit delay is still used.

To the subject, Sync was originally planned but it was not really reliable, the timing was all over the place so I disabled it before it was released because it was useless. Adding a CC command out per tick would be even worse and you'll easily overload the buffer / serial stream.

I wont tell my arduinoboy

Crap, I wasn't going to say anything, but now the code will know he knows!

Might be a placebo effect, according to Tim in the new version "The special bit and byte delays are no longer used. They are hardcoded to stable numbers"

Ahh ... solved it!   Raising the bit rate delay from 80 to 100 in the editor cured this and some other glitchy issues.    thanks anyway.