Any input on the oled front is always greatly received. I think @weasel79 was working on a few things, and had some animations running.
I've always looked at Norns scripts like Orca and Compass and thought they would be awesome on axoloti...compass for example is a looper that is sequenced using key\letter commands which are selected from the screen like this looks like it can go quite complex while remaining fun.
Your menu tree idea looks very useful.
i've been thinking of exactly this issue on the axoctlr (i modded the one from hohum to turn a knob into a encoder)
and i was thinking of something like the thing seen here https://sebiik.github.io/community.axoloti.com.backup/t/multiple-pages-of-parameters-for-axoctrl/6572/5
It's rudimentary but it seems like it works
hey @sebiiksbcs ,
...you mind sharing the modded OLED - object?
I just got myself one,and it's working as a charm thanks to
@SmashedTransistors GREAT objects.
also,I started working on objects to acces multiple parameter pages,
here's where I'm at:
oled.axp (10.8 KB)
...you need to sync libraries...
it's a scroll-down approach for up to 8 parameters.
the patch requires an OLED of course,
and a rotary encoder with a button.(or, another hardware button)
the subpatch top left only makes sense for my setup,
you have wire it up according to your setup.
cheers,
R
ah and here's a little tool for text entry:
...quite minimalistic,extremly limited character-set but with a flashing cursor.
also,I started working on objects to acces multiple parameter pages, here's where I'm at:
oled.axp4 (10.8 KB)
Nice! The patch works on my Axo and I'll check out what's happening code-wise when I have the time.
Meanwhile here's the 'invertLine' OLED object I've made:
OLED_invertLine.axp (51.9 KB)
Note that by now I've also added a fontObject feature which lets you choose your font directly from an object in the patcher. (You have to paste your font data in the array in the object's local data.) It just seems faster to test fonts this way.
The reason I've wanted to change the font is the original font goes all the way vertically and it doesn't look good when the line is inverted. You can compare fonts by changing the fontObject reference on the OLED object (same procedure like with the scope).
thanx a lot!
...looking at @SmashedTransistors OLED-objects I notice that the code is
far beyond my spaghetti-coder capabilities, great you find your way in there..
and I just learned that '~' is bitwise NOT,cool.
BTW I moved my objects to rbrt/string , because they are not strictly OLED-related.
cheers R
Which Resistor needs to be removed? I've the same display, but not really a clue how to prepare it
On many device, it is clearly indicated
for this one
SPI:R17
I2C R15 R13
R18 for CS (chip select)
so remove R17 and add straps on R15 R13 and R18 markings.
Do you have this exact one ?
Do you have some markings on yours ?
my fault, I thought I have to add additional straps apart from the obvious .
Now it's working
UPDATE: Got it working right with 2 independent objects. Now I'm trying to hack into these objects, so I could have 2 bars next to each other on one line so they would better reflect my encoder arrangement here 
Yes you're right,
you should use the "OLED128x64nice" objects (along with a gpio/i2c/config object from the standard lib).
The old OLED128x64Dbl does not implement the horizontal bars.
I added some obsolescence comments in its help patch and object info.
Allright thx!
I have some more questions (also to the oled community here)
could these slightly bigger displays be used as well?
It says SPi but as I recall @SmashedTransistors you have been modding spi displays too right?
Another question is:
can I run the more common oleds in this thread that I'm using as well run on 5v instead of the 3.3?
The reason for this is, that I am embedding two oleds in an existing midi controller and combining the oled and usb data to a custom connector to axoloti. If the oled is running on 5v I could just take the 5v from usb and save one wire running to axo. Or is that extremly stupid for some reason?
No, they won't work.
They cannot be configured to I2C and
they do not work at all like the little monochrome 128x64 oled displays (not the same binary structure and commands to display pixels).
I got two of the displays working, thanks for the great object.
In order to organize my patch, I want to dynamically switch the data sent to the display depending on the context. My object only has one string output per display line.
I made a function in my sub patch in the "local data" tab, copied from "f_c", and I added the local data and init calls as well.
char* f_c(float i, char* prefix) {
char c[7+strlen(prefix)];
char *p=c+strlen(prefix);
strcpy(&c[0],prefix);
float f = i * (1.0f/(1<<21));
if(i > 0) p[0] = '+';
else if(i < 0) {p[0] = '-'; f = -f; }
else p[0] = ' ';
if(f >= 1000){
p[1]=127;p[2]=127;p[3]=0;
} else {
{
int cent=(int)(f/100);
if(cent == 0) p[1]=' '; else p[1]='0' + cent;
f -= cent * 100;
}
{
int diz=(int)(f/10);
if(diz == 0) p[2] = ' '; else p[2]='0' + diz;
f -= diz * 10;
}
{
int un = (int)(f);
p[3] = '0' + un;
f -= un * 1;
p[4] = '.';
}
{
int diz = (int)(f*10);
p[5] = '0'+diz;
f -= diz * 10;
}
p[6]=0;
}
return c;
}If I call it from my k-rate code, the prefix string is displayed, the float is not. I don't understand why.
I tried both strbar and bar mode in the same manner. I get similar results (no bar basically)
I set the c[0] byte according to the mode. they are displayed as "U"
char* stringbar(int i, char* prefix) {
char c[2 + strlen(prefix)];
strcpy(&c[2], prefix);
c[0] = 0; //string bar mode
int32_t v = __SSAT(i,28)>>21;
if(v >= 0)
c[1] = (uint8_t)(v + 1); // must not be zero !
else
c[1] = (uint8_t)(256 + v);
return c;
}
char* barmode(int i){
char c[3];
c[0] = 2; //bar mode
c[2] = '\0';
int32_t v = i >>20;
if(v >= 0)
if(v > 127)
c[1] = 128;
else
c[1] = (uint8_t)(v + 1); //[1 128]
else
if(v < -127)
c[1] = 129;
else
c[1] = (uint8_t)(256 + v); //[255 128]
return c;
}Obviously I'm missing something here, but I do not get it...
Hey ho thanks for the clear answer! Did you have any progress getting 8 lines on a 2,42"? What you posted there above looks quite promisings!
EDIT: Ah I just saw the objects with the 8 lines. Looks very very promising, I wanna get one of these. Do you know if this one would work?
You may have to change it to I2C operation and generate the reset as described in some previous post.
