Jump to content

QBAS

Members
  • Posts

    211
  • Joined

  • Last visited

Posts posted by QBAS

  1. Hi,

    My live was change, I skipped from hardware to software, mostly because lack of space at the table. Now it’s my time to ask you about possibility to sell midibox, because I’m no using it at all from years, and need money for software. My friend is interested in one of mine midiboxes that I could sell him. Of course without your permission I will do nothing. I’m rather no interested in get biggest price that is possible, I wonder if my propose of prices is good for you, and if you can give me overall agreement.

    Story:

    I have almost finished (from 2 years not touched) SIDv2 with 8 sids, vfd 2*20 display, ugly panel (custom made) and switching PC PSU (not-so-best-option-but-works) inside. My friend would like to buy it and he ask about price, so here I am with my question:

    Can I sell to my friend in suggested price ~240 euro, one midibox consist from:

    • box 25 euro (custom made, rather ugly, but with all connectors and even fun and PC power supply inside
    • panel on top 62.5 euro (vfd display 2*20 , control surface C, plus 2*DOUT and 3* DIN modules mounted from the bottom)
    • 4* CORE and 8* SID modules 145 euro total
    • Full memory module 4 euro
    • 5 euro for scrubs etc


      I have many ready to use spare modules , and know he need interface MIDI also, he is ineterested in both additional options:

      • additional GM5 USB MIDI for 12.5 euro with montage and connection inside midibox
      • second option is putting inside also FM module with CORE and memory for it , plus change the power supply (there is enough space for it): 30 euro

    Please tell me your opinion. Thank you.

    Best regards,

    QBAS

  2. Hi Thorsten,

    I would like to thank you very much, like usual. Of course you helped a lot giving me an inspiration where to look for source of problem. It was stupid mistake, sorry that I waisted your time. From other side it was nice to hear you speaking directly to me :rolleyes:

    I found that my midi cables was connected in wrong way: ground was connected to wire on the side. :whistle:

    Stupid basic mistake eat my all Sunday.

    Now my GM5 is working correctly.

    I wish all the best for you Thorsten and for other people who are taking care for this forum and site. :sorcerer:

    QBAS

  3. Thank you Thorsten for trying help.

    About Crystal: I cannot read value on it because I see only X8301JT (symbol), but you said that it must be good one since I can receive from real MIDI world.

    About resistors: Probably you mean R55 and R38. Both are 221 ohm (measured before solder, and also directly on the board after soldering). But question: should it be solder both from top and bottom side? I make soldering resistor mostly from bottom side. Can it introduce this problem?

    If this isn't the reason, please try following experiment: put at jumper at J6:I1 and J6:O1 to short the In/Out connection (don't worry, this won't lead to damages) - is the loopback working now?

    I removed MIDI loop cable and installed jumper like you said. With this configuration I see on input monitor software exactly what I sent (good result)!

    I don't know what is next step now but I`m happy that at least GM5 chip is working good.

    p.s. adding solder from top side to both mentioned resistors not improved situation. But I see that most of my part are not soldered from top side (besides GM5 chip of course). Is this wrong?

    QBAS

  4. Hi, long time not posted here, but I`m still using Midiboxed keyboard all the time, occasionally SID or FM.

    Unfortunately I can't find any similar problem to mine at forum so decided to ask.

    Yesterday I tried to use first time soldered many time ago GM5 modules (I have three of them, all has the same problem).

    Problem: MIDI output is sending otjher messages than I want.

    I send messages from GM5 MIDI OUT and receive it on

    - other interface (novation Remote ZERO SL)

    - directly at GM5 (via MIDI loop from MIDI OUT to MIDI IN).

    In both case I receive at MIDI IN garbage messages, not what I sent (it was simply note on/off or CCs).

    For checking MIDI IN ports at GM5 and second interface I send to them messages from my MIDI keyboard, and both interfaces works good.

    But when I send the same simple message (not sysex) via MIDI out in GM5, I receive garbage on both inputs (GM5 and novation interface).

    Example: instead of note on 90 30 64 , I received two Song select messages: F3 76 and F3 02. Other example: sent B0 45 40, received 3 messages: F3 52, FD, F3 01. If it will help I can putt more results.

    Firstly I think it is an error on input side GM5, so I changed 6N138.... and tried others tricks, but finally I recognized that GM5 receive everything properly, even long sysex. So half of GM5 is working good. Problem is that GM5 is outputting other messages that I order in MIDI OX or MIOS Studio.

    Interesting problem, tried to find source, but without any succes.

    Have anybody idea where to look to find solution? Will be grat to use GM5 as interface.

    Strange is that I have the same bad results on all three GM5 modules MIDI output, even on other computer. All computers with XP, GM5 driver installed. Without driver problem is also.

    Please help. Thanks.

  5. Napewno siobie juz jako? poradzi?e? z tym zasilaniem, zreszt? s? przyk?ady zasilania cho?by zasilaczem od C64 na stronie SIDa.

    Ja mam 2 MBSID, jeden zasilam tym samym zasilaczem, który równocze?nie zasila MBFM (s? w tej samej obudowie), a drugi, zawieraj?cy 8 sidów nap?dzam wymontowanym zasilaczem komputerowym. Wiem, ?e to pora?ka i zak?ócenia mog? by?, ale mi nie przeszkadza lub ich nie s?ysz?. Generalnie nie polecam tego rozwi?zania (du?o miejsca zajmuje), ale ja tak zrobi?em i dzia?a. Na szumy nie narzekam.

    Wiem, ?e bywaj? na rynku SIDy z uszkodzonymi oscylatorami lub filtrem. By? mo?e co? takiego Ci si? przytrafi?o i Ci dlatego "sieje" szumem.

    A jak tam ogólne zadowolenie z SIDa i innych midiboxów?

  6. OK I see that you are not limited by hardware matrix since you can build it from scratch.  I can send you code that I actually use, or even more for 3 different matrixes. E-mail just was sent. If one from these newer version files will work for you then maybe better will be to replace hosted version?

    Does code have ability for log, exp etc velocity change?

    No. Unfortunately I don`t know how to put this kind of calculations (it will be nice to smoothly change response by parameter in realtime), but it is possible to switch different tables witch prepared velocity response.

    I not finish polishing my own table for fatar88 keyboard, it mean from over one year I have too soft touch response, but it is nice to playing.

    (I everyday move this job for tomorrow :D)

    I will try to create the main.syx in a 32 bit machine and download to the core.

    The date on main.asm is 6/28/2006. This looks like the newest date. The oldest date is main.syx 6/26/2004.

    Opps I`m sorry that I wasted your time! It can be a key for your troubles because generally 3 years ago I used (linux) hex files with great MIOS Studio (on linux) and I`m not converted files to syx format. BUT unfortunately I not deleted syx. I didnt touch this project from over year, (I everyday move this job for tomorrow  :P)

    (My music adventure with linux was finish about year ago.)

    I apologize for the question on velocity curves. I finally read your plan for the future.

    I apologize that I cannot implement that feature, but limitations are too big for me. Switching tables seems to be good workaround, but since I not finished panel witch joy/bender and have now 0 switches, no lcd... I have no possibility to switch notching. Just play keyboard.

    Roland style is 16 rows by 8 columns parallel
    Great! I know that in some cheaper models of Roland was used fatar keyboard also.

    Mine has n x 8 matrix.

    I did not make schmatics. I attached test layout I created. This is top 13 note octive. There are some errors (mostly which note is which). Single layer board bottom two are input. Top two are ouput. Only using three ouput on top for top 13 notes. Diodes are input and bottom. Dual layer attaches 45 degree from single using 45 degree connectors. Wire is used to connect ouptut to connector blocks. 
      I dont analyze your borad since I trust you that you know what you do. If you will meet problems then I can try to understand it more.
  7. Hi - nice to see the forum again!

    If I can still something help please let me know.

    Maybe you have old version of code, or an error on pcb with switches...

    Code has protection: if you press only first switch without second, note on will not be send. The same is with second switch. But if you press first switch and after this second then (for sure) you will have note on message at MIDI out. So if you get a note always with 127 velocity then probably you have minimal time delay between switches (maybe an short on pcb witch switches?) I`m open to talk about possible errors.

    By almost 3 years I did about 6 different versions for 6 different matrixes. From about 2 years I`m not changing main part of code, but only adjusted matrix to different types of keyboards.

    Like styrd_one said this custom project was never documented, commented, and finished, but I`m using my 88keys keyboard from about two years with great results (excluding not finished box, still not added Roland pitch/mod joy, without standard panel functions like transpose, velocity curves etc. what is planned in future).

    p.s. Great to see that this site is growing constantly.

  8. Gratulacje!

    Te? mam routera i dzia?a dobrze, tzn sygna?y dochodza.

    A mo?e sprawd? co dochodzi pod??czaj?c zamiast do FMa to do portu w kompie i zobacz na midi ox (lub innym monitorze) jaki kana? itd.

  9. Paski s? gdy nie jest wgrany system lub masz b??d po stronie sprz?towej.

    Czy po wsadzeniu pica do core module i w??czeniu zasilania odbierasz od urz?dzenia sysex na komputerze?

    Je?li nie to masz problem ze sprz?tem lub ?le zaprogramowany bootstrap.

    A je?li sysex ju? wskakuje na kompa to ?aduj system, a potem aplikacj?.

    Dla pewno?ci wszelkiej od??cz core od innych modu?ów. Jak ju? zdzia?a to pod??czysz sobie znowu.

    Powodzenia!

  10. Cze??.

    Najpierw ?ci?gasz z dzia?u download mios_update_v* , rozpakowujesz.

    Plik z podkatalogu burner otwierasz w programie do programowania pica (nazwa programu podana na stronie burnera - w zale?no?ci od systemu), ale najpierw musisz poustawia? mu parametry.

    Pod??czasz burnera i programujesz pica.

    Zaprogramowanego pica umieszczasz w core module i uruchamiasz zasilanie.

    Core wysy?a sysex na ??danie którego wysy?asz mu system tak jak jest opisane tu http://www.ucapps.de/mios_bootstrap_newbies.html

    powodzenia

  11. Cze?? LenweTasartir i AndAway!

    Chcia?em si? podzieli? swoimi przemy?leniami na temat budowania klawiatury, poniewa? kolega napisa? o kosztach: ?e mo?na co? tam taniej...

    ...kochani, budowanie klawiatury, cho?by opartej na najta?szej elektronice jest z za?o?enia dro?sz? inwestycj? (nale?y doliczy? czas! robocizny) ni? zakup u?ywanej, a i jako?? zrobionej mo?e by? s?absza. Przecie? 5 oktaw dynamicznych mo?na ju? za 300 z? kupi?!

    Uwa?am ?e je?li powodem robienia klawiaturki jest kaska - to jest to b??d, bo mo?na mie? taniej, szybciej i bez wysi?ku. Natomiast je?li chodzi o przyjemno?? oraz dostosowanie do swoich potrzeb takiego sterownika - wtedy to ju? inna sprawa.

  12. About this code: unfortunatelly I implement resolution for velocity only in range 256.

    Now after your inputs (in another topic) I will for sure go into bigger one.

    Also I will implement correction for black keys, since white keys has less sensitive.

    So code will be change, but I`m very inetersted in improovments, simplifing, adding comments etc. for

    better understable, better possibilities for using by other people.

  13. Yesterday I try to answer you (both) but since you give me an additional ideas, I tried to check this just now, but it was too big task for my one evening.

    First of all I agree that black keys are more sensivite.

    Applying  correction into PIC code is no problem.

    I would like to share my tought.

    This topic is great response for my question:

    http://www.midibox.org/forum/index.php/topic,6386.msg59979.html#msg59979.

    I asked about possibilities of calculate velocity response in PIC, but until today I no receive an idea how to do this. Somebodys suggested me using tables with predefined values of velocity. If we go into tables then it will be easier to generate this tables by using computer`s environment.

    If we go into reltime calculate in PIC – this is best solution, but I  don`t know now how to implement log scale and exponential.

    I think it would be a shame to lose the standalone midi capability of the keyboard and rely upon a PC.

    I agree that keyboard must be separatelly unit from computer.

    I rather think about build (computer based) environment who give me values for build-in-PIC velocity table(s), by simple experiences with simultaneously:

    1. keyboard playing

    2. realtime tweak timer

    3. realtime tweak shape of curve in computer for getting enough good feeling during play (I`m tried this yesterday, but I need more time, so I will inform if you not give me better direction)

    Like I said this outputted tables will be putted in to PIC for standalone using keyboard.

  14. Hi guys,

    I`m interesting in polishing code  of scan matrix with velocity.

    I have idea how to find value(s) of difference between black and white keys:

    Since I don`t know way how to calculate in realtime values of "velocity_curve", only by predefine LU table. So it is no problem to create different table (s) for black and for white keys.

    Earlier I tried to find values for this table (and additional parameters like timer)

    manually, but this is no good way, and now I come back with new idea:

    Creating in pd small enviroment for converting values from keyboard (raw values of time in sysex format) into our note on/off with velocity_table_curve_for_black + the_same_but_for_white.

    Benefit is because we can change parameters in realtime, not in asm file.

    So this way will give us many different pairs (for black and white) of curve_tabeles.

    Of course if we no need different velocity table for black keys, this way (with pd) will help find better (more human) touch feeling of keyboard.

    If somebody have better idea please say it now (if my post is understandable).

    thanks

    QBAS

  15. Czo?em, troszku mnie nie by?o, ale za to uda?o mi si? zapuszkowa? MBFM oraz MBSIDv1 do jednej obudowy. Teraz spróbuj? sko?czy? SIDa v2 (mam ju? panel i obudow? oraz modu?y, pozostaje tylko wkr?ci? wszystko w ?rodku). Mam nadziej?, ?e u Was te? lepiej?

  16. Naj naj naj!

    mam pytanko bo chc? do sida wmontowac 4 switche +enkoder ze switchem jak to spi?c z dinx4 ?

    na samym dole s? pdfy

    http://www.ucapps.de/midibox_sid_manual_hw.html

×
×
  • Create New...