Sweet this thing will pump those sound waves!
You can get to it from the front page, through the user projects section…what’s the problem?
Oops… I’m not sure what I saw.
The new OP MIXER ABC Module is up an running 
did you received the mail with the OP MIXER stuff for the midibox wiki?
It’ll be up in about 15 mins or so
tx
Woot great job man! 
@#&*(@ :o
Correct me if I’m wrong it just affects volume of the channels? :o
Correct me if I’m wrong it just affects volume of the channels?
yes.
the ay 3 8912 chip provide three amplitude regs (R10,11,12 - volume/amplitude register a b c: 0-15 dec. [=>4bits: L0 L1 L2 L3]) for the channel a/b/c.
this is the internal volume handling of the AY 3 8912 chip.
the MIDIBox AY 3 8912 will be equipped with a (user)menu for volume (tone a b c) [volume pre-adjustment 0-15 dec.]. furthermore it’s planned that the volume of tone a/b/c will be controllable via control change and velocity (switchable). the mixer module was just designed for mixing the tone a/b/c and for fine justification of the volume level.
Wow thanks man! This is one of the best designed user projects on here! Very clean and new! ;D
Thank you all for the feedback!
@Sirkit: In my view I’m a raw beginner (my method is trial and error) ;D
Still its way nice ;) oh and how can you control sound parameters with just a keyboard, wouldn’t you need at least 1 encoder, (like the SIDS step A control surface)
how can you control sound parameters with just a keyboard, wouldn’t you need at least 1 encoder
The Menu/Parameter handling is unfinished at the current stage of the Project - but I would like to leave all interaction to the C64 keyboard. Nevertheless I hope the user work flow will be some kind of handy in the end (…it’s because - my first Computer was a Commodore64 - and first love never dies 
)
I get it but still i dont see how you couldn’t change and LFO for instance with just buttons because you couldn’t change it at just the speed you wanted but get close.. oh well
I get it but still i dont see how you couldn’t change and LFO for instance with just buttons because you couldn’t change it at just the speed you wanted but get close.. oh well
buttons, believe it or not, are actually more accurate, encoders are more intuitive maybe… it’s a preference thing not a necessity thing. you are referring to the interval between values that can be achieved and that would be the same with either encoder or buttons. it’s up to the hardware and the guy programming it.
I just got an issue with the sm 8x8 keyboard driver - some keys working fine - but there are some other keys with strange behavior (as F1, F3, F5, arrow up, Q, E, T, U, CTRL… ). They do not only toggle once (on/off) - those keys toggle several times (never-ending - actually with diffident values like key F3). I took another keyboard - same results.
I furthermore made a cross check with http://www.ucapps.de/mios/sm_example2_v1b.zip
It sounds almost like a debounce problem but I notice that the keys you mention are only within a certain section of the keyboard, and are on the same columns in the matrix. I’d be looking for shorts and loose connections, and diodes in backwards.
..I’d be looking for shorts and loose connections, and diodes in backwards.
Yes - perhaps it’s the hardware. I’ll check the MIDIBoxKB interface.
Mea culpa! :-\
I thought it was the SM driver but there was a loose connection (sometimes working sometimes not) in the MIDIBoxKB interface @74HC165
Thank You for pointing me in the right direction stryd!