Rio

..and again...the application will only work with a C64 keyboard. if you have a plan for connecting serial keyboards to core and knowledge in C, you can try to implement it. It should using the sm_matrix. But i have reached the $7FFF border of 32k with optimizied code(!) ... maybe it could a bit difficult to add bigger changes.

you mean application (not firmware), i'm right? i don't understand it right... which application you mean? MB-6582 or MBSIDV2. I wanna only upgrade a MBSID to MBSIDV2 with an 8x8 matrix. is the application for 8th matrix line precompiled in TK's application? and where i find a connection schematic for DIN and DOUT for TK's MBSIDV2 with included volume for DIN / DOUT?

1. LCD 4bit mode i'm not really sure... is it necessary to connect D0..D3 from LCD to ground or should D0..D3 be opened? 2. 8x8 matrix where i find a documentation for 8x8 matrix connection? mbsid_v2_din_default.pdf and mbsid_v2_dout_default.pdf shows only the standard connection without volume connection. Will precompiled application automatically detect the 8th matrix line...?

mhh... maybe this could paste up later on your fingers :/ you should try it on something other before... test how it looks before you fill it up... it seems all your keys are white... maybe it looks better to have black letter on it... (maybe white on black can confuse you earlier in operation with SEQ... ;)) but it's subjective.

If you wanna change label of keys (like i see on photos)... it would be better to grind off the old label with ultra-fine sandpaper... then you can label keys with out overwritting the old label. Another way is: you can change Keybuttons in special position and in new order. First you have to open the backpanel with that lot of little screws... then open the backpanel. take a bent tool (e.g. a little spanner) and you can remove that keys from backside easily. Beware of the jumping spring ;D. ok, have fun...

@ris8_allo_zen0: great ;) yes, ris8_allo_zen0 converts SEQV3 to a C64keyboard SEQ... i'm tight how it works :) beside of that for those which are fans of C64 Keyboards and those which have built up a MBSEQV3 yet, my K64 application controls MBSEQV3's record and utility functions from outside via midi remote. That is another way to controll SEQ...

i doubt that this could work - i believe it wouldn't work, because: - the matrix of C64 is for 64 keys. so only 64 keys are defined in application - the keys have a special Assignment and a special tag. I've oriented the application to that C64 Keyboard tags.. (e.g. I don't believe that the space key would be the same like PS/2 keyboard space key...) - shortcut hardware problem with C64 keyboard (using more than 3 keys at same time - you could get in trouble... because it will short cut to other keys on C64 keyboard matrix and you would get randomly result in application, but i've solve the problem with implementing some workarounds for problematic key areas and my application reacts only limited to 3 keys at same time. It works in most cases well. So i don't know, if it have something to do with PS/2. i don't think so. ... so i can only say that the application will work correct with a C64 keyboard. I've nothing other tried.

hi and thx, sorry, but it seems it will not work with another keyboard like that commodore keyboards. I used the C64 Keyboard board schematic from Bill and connected it to J8 and J9 like in his description. There is also a special keymap defined for C64 matrix and strictly used in the whole code. It will not work with another connector and i don't how a ps/2 adapter works with the sm-matrix... but another solution: you can buy an old or defected C64-II from second seller market and cut/trim the backside of case. That C64-II case are not so high and useful as keyboardcase too. look what i've done with an old C64-II case: http://www.midibox.org/midibox_gallery/rio5.jpg you can built the keyboard in another cases too..

Hi, Now i've added an additional SEQV3 Record/Remote Mode in K64 application. Besides, i reached the $7FFF border... so no more features are possible. okay, it's time to clear up something: K64 application is fitted out with 2 special modies (SYNTH MODE / TTS MODE) to controll functions of K2-application. Both applications, K64 and K2, communicate only through midi ports. The K64 modul can be used as Midi Keyboard without a speakjet too. Edit: Now i've expanded the RECORD functionality feature in K64 v1.1c. For more information read the doku/tutorial in dokuwiki.

yes english phonemic - but the phonemes can be used for german speech too. Words like "RIO" are easy to speech with a rolling R too ;). In application all letters can be combined in different variations too. So i'm pleased with results. You can listen that little change in the second speech example... I was comparing the spoken results of a letter to german pronunciation (oriantating by my ears). So i added different variations for a letter (max. 9 variations are possible), which can be assigned to a specific letter in a word. So you can generate your pronunciation in combinations like you want. It's correct, that the chips sounds often like german with accent ;) I don't know how that TTS Chip works and i don't have one. My routine sends out every letter (the choosen phoneme) in a bit timing distance, but fast enough to link the letters to a spoken word. So it's possible to do changes in Bend, Speed, Pitch and variation in realtime, while SpeakJet is speaking. Maybe the TTS Chip will store and proceed the whole word or sentence before... I don't know. I use the K64 mainly for robot speech in music controlled by a sequencer.

yes... thanks. Besides, big thank for audiocommander's and Bill's pre work too. Without that nothing would be possible. A big advantage is that you can use two of your older PIC18f4520 from MBSID for that project. German pronunciation sounds in most ways well. All in all, every letter can be vary. so your request after an english TextToSpeech isn't so easy to use, but it's maybe possible: You change the preselected phonics in array of letters to english phonic in my code and you have to compile it again... e.g. you insert all combinations for english "e" + a pause phonic, because there is often the case that the "e" will not be spoken at end of a word. I think such little algorithm can be implemented for a preselection. But every word you write down in application, have to be combined first in the correct pronunciation by variations (in german the pronunciation sound is often the same for every letter). It's still possible to combine variations in application. At least, you are able to store your modificated english phrase on eeprom. The most problem of english pronunciation: Many vowels change extremly from one word to another (o or oo --> u, a --> e, e --> i, ea --> i), some letters will not be spoken (maybe "e" at end of word) and so on... so for an english TextToSpeech many combinations have to be preselected maybe by hand in application itselfs or by algorithms. Here are some informations about english vowel rules: http://pluto.huji.ac.il/~msyfalk/WordStructure/Vowels.pdf oh my god! With a last feature - implementing Remote Control for SEQV3, the application reached $7FFF so there's no space left to implement english algorithm (maybe only some few cases). But if you have skills in C, you can try too implement that on a bigger chip or you use some parts from synth section in application. But one of my goals was to implement the whole application on a PIC 18f4520, so that people can use that chips from older applications (which are upgraded now).

Nice ;)

the application is only available for PIC18F4620, so you need a PIC18F4620.

wonderful :o

I've added a tutorial for whole application. Greets Rio.

thxs for both comments :) i'll add a tutorial "how to create synth patches" and "how to create german text patches" with several options and listening examples in august... What you hear is a tuned chord of that 5 OSC with a very low ENV Sin frequency in sample 9. So the ENV Frequency works as an own LFO too. Greets Rio.

@polosid: use that example: http://jambonbill.free.fr/midibox-kb/c/c64-keyboard-test-v2.zip everything you need for kb input device should shown on LCD. I used that matrix for my project too and the answer of a notemap is the defined const array in variables.h Greets Rio

K64 reached 1.0 release state. It's an additional controller application for a K2 (modified v1) from AC. You will found last version here: http://powerhuhn.net/rio/SpeakJet/K64_v11d.zip (currently down...back soon) [img width=400]http://www.midibox.org/dokuwiki/lib/exe/fetch.php?w=400&cache=cache&media=http%3A%2F%2Fpowerhuhn.net%2Frio%2FSpeakJet%2FImages%2Fblackwhite.gif What is that? It's C64 keyboard controller unit for: - using box as midi keyboard with additional SEQV3 remote / record support - using box as SpeakJet Synth Controller - using box as SpeakJet TextToSpeech Controller features: - playing notes on 2 keyfields (UPPER, LOWER) for seperate channels / transpose - recording / editing SEQv3 tracks via remote - trigger spoken text on the basis of incoming midi notes - seperate adjust of 5 OSCs of SpeakJet - 1 triangle LFO for CC Values - graphical interface for Speakjet Synth - graphical interface for Speakjet Text Input (realtime variations in speech) - store your synth and speech patches on bankstick (32k or 64k), max. 8x condition: - for PIC18F452 - only for C64 Keyboard - only for 2x40 LCD - texttospeech for "german" language only All infos about are here: http://www.midibox.org/dokuwiki/doku.php?id=midibox_speakjet_k64_modul Dokumentation, tutorial, screenshots, examples are added in tutorial... Hardware: [img width=590]http://www.midibox.org/dokuwiki/lib/exe/fetch.php?w=590&cache=cache&media=http%3A%2F%2Fpowerhuhn.net%2Frio%2FSpeakJet%2FImages%2FK64-hardware.gif At time K2mod (a modification of k2 application from audiocommander) is needed instead K2. AC will try to add that features in his application in further version. Thanks to AudioCommander for his great preparatory work and support. Thanks to Bill for his C64 Keyboard implementation.

Is SDCC 2.70 functional for mios projects? I've readen that the wrapper only works with 2.50 correct. ..from your description in WIKI

MIOS_LCD_PrintCString works only for const char arrays

..and back to the theme: @tk: Can you tell us, which parts (trimpots, capacitor types, etc?) you used in detail for a CEM3378 Schematic (Maybe you can open your Behringer Case again :-\). Would it be meaningful to connect 2 external Potentiometer (as control knob) for Filter and Resonance additional - which type should then be possible? I want to buy all parts at reichelt at end of the week. Best Greets, Rio.

Do you sleep beside this place :o

Die LCDs von MTE sind wirklich top qualität ;) Kann ich nur empfehlen.

So, apparently it works. :) ok my last questions so far: 1. you are always use only the CH.A input of CEM3378, i'm right? 2. To use the second AOUT_LC, i only need to chain the 2. AOUT_LC to J2 of first AOUT_LC, or? 3. You mean trimpots for filter and resonance? Do i need to adjust Gain or Balance on CEM3378 in any way?

who said that??? please calm down a bit too... i want to know, whether a solution with 2xAOUT_LC is possible for MBSIDV2 stereo feature (1Core -> 2SID) too. (if not, i have to change to a newer solution too, of course).. Maybe only TK can give us a statement about that. And don't understand me wrong, i appreciate every better solution. ;)