|
|
Me too!!
⬛⬛⬛⬛🟩
⬛⬛🟨⬛⬛
⬛🟩⬛⬛🟩
🟩🟩⬛⬛🟩
🟩🟩⬛⬛🟩
🟩🟩⬛⬛🟩
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
Wordle 412 4/6
⬜🟩⬜⬜⬜
🟨⬜⬜⬜⬜
🟩🟩⬜⬜🟩
🟩🟩🟩🟩🟩
Would have got it in 3 but made a mistake
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
Wordle 412 6/6
⬜🟩⬜⬜⬜
⬜🟩⬜⬜⬜
⬜⬜⬜⬜⬜
⬜⬜⬜⬜🟩
⬜🟩⬜⬜🟩
🟩🟩🟩🟩🟩
This should've been an easy one for us
|
|
|
|
|
Wordle 412 6/6
⬛⬛⬛⬛🟩
⬛⬛⬛🟨⬛
⬛🟩⬛⬛🟩
⬛🟩⬛⬛🟩
⬛🟩⬛⬛🟩
🟩🟩🟩🟩🟩
This really strikes close to home for us CPians
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Wordle 412 5/6
⬜⬜⬜⬜⬜
⬜⬜⬜⬜⬜
🟩🟩⬜⬜🟩
🟩🟩⬜⬜🟩
🟩🟩🟩🟩🟩
Not looking good after 2, saved by my 3rd starter.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Wordle 412 5/6
⬛⬛⬛⬛⬛
⬛⬛⬛⬛🟩
⬛🟩⬛⬛🟩
⬛🟩🟩🟩🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 412 5/6
⬛⬛⬛⬛⬛
⬛⬛🟨⬛⬛
⬛🟩⬛⬛⬛
🟩🟩🟩⬛⬛
🟩🟩🟩🟩🟩
Get me coffee and no one gets hurt!
|
|
|
|
|
This one was full of problems
Wordle 412 5/6*
⬜⬜⬜⬜⬜
⬜⬜⬜🟨⬜
🟨⬜🟨⬜⬜
🟩🟩⬜🟩🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 412 5/6
⬛⬛⬛⬛⬛
🟩⬛⬛⬛⬛
🟩⬛⬛⬛⬛
🟩⬛🟨⬛⬛
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 412 6/6
⬜⬜⬜⬜⬜
⬜⬜⬜⬜⬜
⬜⬜🟨⬜⬜
🟩🟩⬜⬜🟩
🟩🟩⬜⬜🟩
🟩🟩🟩🟩🟩
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Wordle 412 4/6*
⬜⬜⬜⬜⬜
⬜⬜⬜⬜⬜
⬜⬜🟨⬜⬜
🟩🟩🟩🟩🟩
Happiness will never come to those who fail to appreciate what they already have. -Anon
|
|
|
|
|
I've been working like mad to get my Prang MIDI device working, and it does. But it lags. I can't stop the lag. It doesn't seem to matter what I do to it. If I run a loop between TX/RX on the breakout the lag is basically gone (more or less - it's still MIDI)
As soon as I include my circuit, running my firmware in the loop the lag goes crazy. Even this yields lag:
while(true) {
int i;
if(-1!=(i=MidiSerial.read())) {
MidiSerial.write(i);
}
}
I think it might be the hardware UART buffers taking too long at 31250 baud.
But at the end of the day it doesn't matter, because I've no way to fix it.
My project is dead in the water. After already writing an article about it prior, and after writing an entire MIDI library that basically is effectively useless now since you can't get anything on or off the device without lag.
*headdesk*
I'm completely bummed out right now. I need a win.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Is the lag constant? This almost sounds like something in the hardware/software can't run TX and RX at the same time. We had that problem with a buggy serial chipset (I2C I think) once that used a single FIFO for both TX and RX. You could send bursts, and receive bursts, but you couldn't do both at the same time.
Software Zen: delete this;
|
|
|
|
|
It is constant and I've already run that down to the degree that I'm confident it's full duplex, but I'm thinking the hardware UART buffering has something to do with it. However, even calling flush all the time doesn't solve the issue.
I may have to move the whole thing to USB. That was my original plan anyway, but I ran into technical challenges. Well, I'm throwing some different hardware at it this time and maybe that will change.
To err is human. Fortune favors the monsters.
|
|
|
|
|
If the UART has a FIFO you may need to set the level down to 1 so you get an interrupt for each character received. Otherwise the UART will not interrupt until the FIFO is full or some time has passed.
|
|
|
|
|
Yep. The problem is I can only set the buffer so small. Fortunately I set to its smallest setting and it improved things a lot. I didn't think it would, because 128 was the minimum and I thought it was bytes but it may be bits, which is much better for me.
To err is human. Fortune favors the monsters.
|
|
|
|
|
At 128 bytes, that is probably the operating system buffer for the UART. Inside some UART there is a FIFO buffer, usually 8 or 16 bytes. There is a threshold level you can set as to when the UART will interrupt the OS to read the buffer. And there is sometimes a way to set the timeout before the buffer is full.
This would be set at the hardware level, which you may not have access to.
|
|
|
|
|
Actually that setting does exist, and you can set it if you use the native API. Unfortunately, doing so requires some fancy footwork you can't do under the Arduino framework, and that's what I'm targeting.
Fortunately, I turned the buffer sizes down and that managed to nearly solve the problem - much better than I thought it would.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Don't worry, future codewitch will come to the rescue soon enough, I would wager!
|
|
|
|
|
You'll fix it.
|
|
|
|
|
while(true) {
int i;
if(-1!=(i=MidiSerial.read())) {
MidiSerial.write(i);
}
}
Did you author these routines? if so, you might want to look at them in detail so be sure handshaking is not the source of lag. Something may be waiting on something else.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
What handshaking?
There are two lines. TX and RX
There are no control lines.
There is nothing to handshake.
It's two wires.
To err is human. Fortune favors the monsters.
|
|
|
|
|
looking at all eight bits? any Control characters?
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Nah, it's just midi protocol over the wire.
The receive buffer was too big by default. I turned it down and it improved things a lot. Unfortunately I can't eliminate it so I may have to switch to USB anyway.
To err is human. Fortune favors the monsters.
|
|
|
|