Jump to content

TK.

Administrators
  • Posts

    15,247
  • Joined

Everything posted by TK.

  1. The collection of problems reported in the last weeks, and the appr. solutions, can now be found here: http://www.ucapps.de/midibox_sid_walkthrough.html This is a living document which will be enhanced in future Please let me know, if an important hint is missing Best Regards, Thorsten.
  2. Did you select the right baudrate for the MIDIbox-to-COM interface? (see http://www.ucapps.de/mios_bootstrap.html) Best Regards, Thorsten.
  3. I just have written a walkthrough which should give you some hints how to get the box running: http://www.ucapps.de/midibox_sid_walkthrough.html My tip: start with the MIOS installation! Best Regards, Thorsten.
  4. + an integrated coffee machine? ;-) Best Regards, Thorsten.
  5. I just have written a walkthrough which should give you some hints how to get the box running: http://www.ucapps.de/midibox_sid_walkthrough.html Best Regards, Thorsten.
  6. Try the C wrapper, the programming effort will be much lower Best Regards, Thorsten.
  7. thanks! :) to the sequencer ideas: I can only say that such a project is feasible with MIOS, but my focus is currently on other stuff :) Best Regards, Thorsten.
  8. MBCV will support the AOUT_LC interface sooner or later. The hardware is final (PCB layout frozen, no changes planned) Best Regards, Thorsten.
  9. Today I made some performance evaluations. It is not a good idea to load the drum sounds directly from BankStick at the time they should be played, because this leads to a latency of 5 mS. Thats the time which passes to load 42 bytes from a BankStick when other tasks are running in background (the software engine which handles the LFOs and ENVs takes ca. 50% of this time) So, the only way to realize a latency much below 500 uS is to preload the whole Drumkit into RAM - thats the way I will go. The RAM data can be compressed, I hope that at least 20 drum sounds will be loadable at once - this should be enough This leads to the side effect, that a MBSID-D master has no RAM anymore to edit the parameters of a MBSID-D slave in realtime. However, this should also be acceptable. It will still be possible to prepare a drumkit on the master, and to dump it to the slave before the use. Maybe the use of MBSID-D as a CS master is a corner case anyhow - I will still use my common MBSID as master Another point which I noticed and which will affect the sound architecture is the damned SID envelope bug. The VCA envelope of the previous sound can affect the envelope of the new sound (hick ups). One measure to compensate this is to clear the envelope registers when the sound is finished (the required delay could be calculated from the ADSR settings). Another possibility is to clear the registers, to wait some time (I don't know how long), and to play the new sound thereafter... this would increase the latency... however, lets see Best Regards, Thorsten.
  10. I explained you, how this can be realized why do you want to use the MIDI Out of these boxes? Just use the MIDI Out of the MBSEQ The MIDIbox Link port works with TTL level, therefore you can connect multiple MIDI Ins to a single MIDI Out, and in addition you can drive a "common" MIDI In with optocoupler. If more "common" MIDI Ins with optocoupler should be driven, then you need a LTC module in addition Best Regards, Thorsten.
  11. Big Jacks, because my ADC (Hammerfall DSP Multiface) has the same ones Best Regards, Thorsten.
  12. With the C wrapper this shouldn't be that much effort... especially, since you only want to control a host application, where MIDI events could be statically defined (I guess that you don't want to change MIDI events directly on the LCD, when you are also able to edit them in your host sequencer?) Best Regards, Thorsten.
  13. This was nothing personal! I just thought, that a discussion about a feature, which is implemented in the MIOS based "normal" MBSID, but not in the old PIC16F "normal" MBSID, has nothing to do with the MBSID-D And the misleading assumption from your side (in short words: patches don't allow filter changes) could only lead to an even more confusing questions from people, who read this thread and could think, that this is a discussion about MBSID-D Best Regards, Thorsten.
  14. Sidenote: the INs are a nice option, but not really useful. Best Regards, Thorsten.
  15. For a 24LC512 you only need to do some small changes in mbsid_bank.inc - search for "SID_BANK_SetBankStickAddress, and replace this function by SID_BANK_SetBankStickAddress movff EEADR, MIOS_PARAMETER1 ; copy address to low-byte movff SID_PATCH, MIOS_PARAMETER2 ; copy patch to high-byte bcf MIOS_PARAMETER2, 7 btfsc SID_BANK, 0 bsf MIOS_PARAMETER2, 7 clrc rrf SID_BANK, W andlw 0x07 iorlw 0x80 ; (disable verify for faster write accesses) goto MIOS_BANKSTICK_CtrlSet [/code] (I never tried this out...) To the MBFM BankStick effect: this is really strange, I don't know how this can happen. A quick & dirty solution: insert a "return" below the SID_BANK_FormatStick function to prevent this action. Thereafter upload a complete sound bank, thereafter remove the return, so that the BankStick will be formated again, but this time with proper background data Best Regards, Thorsten.
  16. Do you have programming skills to implenent this into the application? I mean: MIOS provides the basics to control multiple displays, but the application itself has to send some useful data to the additional displays... unfortunately, the MB64/MB64E is written in assembler, therefore it's not so easy to extend them if you never programmed PIC assembler before. Alternatively you could implement something similar in C - this isn't so difficult, but examples are rare Best Regards, Thorsten.
  17. Thanks guys! :) Well, I wasn't able to eat that much during my birthday, each time I tried I got a phone call ;-) Best Regards, Thorsten.
  18. Hi, yes, you can use the MIDI Link port, but only in one direction. The MIDI Out of the Sequencer (J11:MO) has to be connected to the MIDI In of MBSID and MBFM (J11:MI) - a proper ground connection is also required of course, and the optocouplers of the MBSID and MBFM core modules have to be removed. This setup will still allow you to access MBSID and MBFM thru the MBSEQ MIDI In (you have to enable the Merger in the MIDI menu) Best Regards, Thorsten.
  19. Please send me as much percussion patches as you can! :) Not only the standard patches for Bass/Snare drum, HiHat, Cymbal, etc. are for interest, but especially some "clicks and pops", which sound C64ish. Best Regards, Thorsten.
  20. Yes, this is the maximum configuration. A=0 is the BankStick for Bank 0, A=1 the BankStick for Bank 1, etc... you don't need them all to get a MBSID running, but at least one with the A=0 (all address pins tied to ground) is advantageous Best Regards, Thorsten.
  21. Could you please write down the checksum of each block which has been uploaded? This info is print by MIOS Studio during the upload. It would allow us to doublecheck, if this procedure was really successful. Best Regards, Thorsten.
  22. Could you please write down the checksum of each block which has been uploaded? This info is print by MIOS Studio during the upload. It would allow us to doublecheck, if this procedure was really successful. Best Regards, Thorsten.
  23. Could you please write down the checksum of each block which has been uploaded? This info is print by MIOS Studio during the upload. It would allow us to doublecheck, if this procedure was really successful. Best Regards, Thorsten.
  24. You got it! So long MIOS is not running, you cannot expect that the MIDIbox SID or any other application is doing anything. So, first try to debug this, offe already gave you the link to the debug page, unfortunately you didn't answer him, therefore nobody knows, if you tried this or not, and it's no surprise that you are confused by all the hints which don't work, if you haven't checked the basics Don't give up! But install the software step-by-step please. Best Regards, Thorsten.
  25. Kokoon: now I don't know about what you are talking ;-) If you are refering to the available parameters: check the table again, instead of a single filter value, each voice should provide a global filter control. I think that I will realize this as an cumulative node, which means: each voice can add or subtract something from the global filter values If only one voice is doing this, there is no change compared to the normal MBSID at all. If multiple voices are controling the filter at the same time, you will notice very strange effects... but who knows, maybe interesting effects? Filters can also be modulated (see table) --- also all voices at the same time I'm really not planning to give up filters! Phattline: you are refering to the keyboard zones. No, they are not supported by the old PIC16F firmware. And your assumptions are also not correct... not the master filters the notes, but the internal MIDI In handler. I will split this thread so avoid even more confusion ;-) Best Regards, Thorsten
×
×
  • Create New...