tago

You mean your circle 6 button layout? What's the thinking behind that arrangement? Looking at the photo it seems like you can compare the lower lines, they have the same character count (20). Around 3-4 times smaller then LCD character height. But the OLED has more vertical pixels. Maybe a condensed font is the solution to fill the whole display? Or simulate a 4x10 LCD? What looks the SCS on a 2x40 LCD, is there lots of blank space? I want the SCS mostly for patch selection purposes in an universal synth controller. It would make sense to have a larger font on OLEDs, at least for patches names.

I hope i'm not too obtrusive. The photo could be one of a breadboard/flying setup, i only want to see how the 128x64 displays the menu text. Thank you :)

Do you have a photo showing how the SCS menu will look in that configuration (single OLED)? I've only seen LCD SCS.

@latigid on My question has not directly to do with your board. Will the SCS work with only a single 128x64 OLED? Would you use an original or emulated SCS in this case?

@Hawkeye What is your experience concerning lots of displays and processing power? I count 24 on your Programma. I would have a STM32F4 core.

Can you estimate the needed processing power per display? I wonder how much is needed for 8 displays (7x 128x64 and 1x 256x64).

Nice! Looking forward to it. Do you know if it's possible to have say 4x 128x64 OLEDs and 1x 256x64 OLED all with the same controller chips on it in a MBNG system without customizing the code?

Ok, regarding "MS-20 filter clones x 2 - MIDIbox CV V2" i see 4 OLEDs and one LCD. So its possible to mix displays after all? Is this only available for Midibox CV V2 or custom code?

@Psykhaze Thanks, but i see no SCS in action ;) Is there no video of Hawkeye's Programma v0.1 monster? I would like to see the bottom section in action. For a synth controller a SCS/main menu would be very useful, i think.

I have seen this page, but there are only drafts/wireframes. I wanted to get a real world feel of that thing. :)

How do 4 OLEDs work with one SCS? Is there a photo or video? Edit: i mean a SCS consisting of multiple OLEDs. I've already learned that you can have multiple displays for different purposes.

Here is a SPI 256x64 display with carrier board. http://www.buydisplay.com/default/spi-3-2-inch-oled-module-display-256x64-panel-screen-yellow-on-black What's about SPI and I2C?

Can you mix displays with the same controller chip but different resolutions? (e. g. 128x64 and 256x64 both ssd1322) Would be a reasonably compromise.

Thank you. Its a shame that such infos are fragmented over ucapps, wiki and forums.

In the source i found: src/modules/app_lcd/ssd1322 Would this work? http://www.buydisplay.com/default/2-8-inch-oled-display-256x64-graphic-module-ssd1322-yellow-on-black

I'm not a good coder with much experience, but i'm trying :) Currently i wonder about different types of OLEDs. I often see 0,96" (128x64) and that 2x40 (for the SEQ) here. The 2x40 seems not graphic but character based, so no custom fonts/graphics, right? Whats up with other sizes/formats graphic OLEDs? E. g. 256x64 or 128x32 Is mixing different types (pixel size/denses) of OLEDs possible when they have the same controller chip (SSD1306) on it or can you really only use one type simultaneously? I know that mixing LCDs and OLEDs is not possible. I ask because it should fit perfectly in my frontpanel design. I'm not sure how a tiny a 0,96" OLED will look as a SCS/System display.

Meanwhile i downloaded the code and did look here and there to get an idea. I found the following relevant(?) docs http://www.ucapps.de/mios32_c.html (MIOS32 C Interface) http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F021_glcd%2FREADME.txt (Graphical LCD Output) http://www.midibox.org/mios32/manual/group___m_i_o_s32___l_c_d.html (LCD functions) Since i'll probably use Midibox NG i found this file interesting: apps/controllers/midibox_ng_v1/src/mbng_lcd.c Should contain all implemented LCD code for NG, right? To me it looks like it mostly contains cursor based print to display code. Maybe all i need is to customize bitmap fonts and follow that approach. If not sufficient then look at MIOS32_LCD_BitmapPrint function. In the end i have to get all the hardware stuff to test and play.

@Hawkeye Thanks Peter. Is mios32_lcd.c instantiated as LCD class or is this only helper functions? The var mios32_lcd_device indicates an ID for each LCD. Do you know where these functions get triggered or (if) class gets instantiated? Do you know if it is out of the box possible to have virtual LCDs? E. g. split one physical 128x64 LCD in two 128x32 screens?

Ok, so it works like a oldschool video wall (e. g. 8 single screens == one big screen)? Is it kind of a address (pixel area) for every OLED? I'd like to know how to draw graphics/fonts on the screens or specific areas of the screens. Where do you define all that?

Hi all, i would like to know more about OLED displays and how to connect and use them. It looks like you can connect say 8 OLEDs via J15A on CORE_STM32F4. I assume these wirings are ok for STM32F4. http://www.ucapps.de/mbhp/mbhp_lcd_ssd1306_single_mios32.pdf http://www.ucapps.de/mbhp/mbhp_lcd_ssd1306_multiple_mios32.pdf Every OLED gets it's own CS-Line (CS0-CS7 on J15A) and all other pins are connected in parallel. What does the X = 0..127 or X = 128..255 values mean? Edit: here it is better pictured, should work http://wiki.midibox.org/doku.php?id=oled

I'll need around 40 analog ins, let's say 6x AINSER8 modules. The manual states: I don't understand how much i can connect without much hassle. Do you need one RCX per AINSER8 ?

It's simply too much info and modularity for a beginner and too easy to give up because of that. I for one did learn some basics playing with teensy and built a little midi volume controller with a led ring and two led-buttons directly attached to the controller board. After that success (thanks to teensy) i gone over to look at shift registers/multiplexers and did a little test aiming to build a larger midi controller. But then came doubt if teensy is the best patform to do something larger. And there i am, certainly not the only one. I debated building my own PCBs and started with Kicad. But if you are a beginner in designing and etching PCBs it seems like a project in itself (+ money for equipment). As i'll try to build the housing for my project with no cnc-mill myself, there is plenty to learn and getting tools as well. Something had to be sacrified. Therefor is getting ready made PCBs a good alternative. Maybe i will do the AINs on veroboard distributed over the frontpanel near the pots/slider, in that case no AINSER64 then. Summary: i have no idea/equipment and will do it anyways :) There are good chances to failure.

Looks intresting. Will have a look at MBCV too. Regarding OLEDs in NG manual it says: Sounds good. There should be no problem having a few waveform displays. Have to look into this later.

Absolutely, you're right. I'm trying to get an overview since days and maybe expecting too much. But as i know myself i have to fix a few decisions to move forward. Otherwise there is this ocean of possiblities where you will never arrive anywhere, procrastinating the project forever. (wacky phrasing!?) Sorry, i know i have more questions than reasonable, that's my problem of having no idea what i'm doing ;) I appreciate every info i can get. Maybe other noob's will benefit from all this too.

@Psykhaze Sorry, but i did read about MBProgramma earlier, but don't know how it could help besides portions of the software at later stages. At the moment i have a very different control surface, more oldschool than MBProgramma's spaceship stuff. One thing i would like is to have small OLEDs/LED or LCD displays for showing graphics of waveforms (e. g. oscillator, modulation). Why do you think it's the solution? Please keep my noobness in mind ;)