Jump to content

TK.

Administrators
  • Posts

    15,247
  • Joined

Everything posted by TK.

  1. Hi, it doesn't work because the SysEx configuration in mb64e_dump will overwrite this setting. Normaly the merger mode is changed from the menu, or via SysEx (either use mk_syx or the MB64E editor GUI) Best Regards, Thorsten.
  2. Hi, 1) I remember that the PSU of my old C128 didn't start when the power consumption was too low. So, it will propably not work with the core module 2) you could do this, but it's better to use different device IDs and the same MIDI channel. SIDs assigned to the same channel will load the same patch, they will receive the same parameter changes, but the sounds will be slightly different (-> FAT STEREO SOUND) due to "analog" live inside the SID (and the virtual stuff inside the mighty MIDIbox SID sound engine) This is the only way how it makes sense. If you would like to hear EXACTLY the same, you could also double the volume of a single SID ;-) The control surface allows you to select multiple SIDs at once and to do the changes at the same time. When I want to have some nice stereo Fx, I normaly select the same pach for all SIDs first, thereafter I'm doing slight variations (e.g. LFO rates, portamento rate, finetune, EG parameters) on each SID seperately, then I ensure that the MIDI channel is the same for all SIDs and start grooving :) 3) there are so many board revisions... just check what you have 4) it depends, I own some 6581 from different years, and each one has it's own filter characteristic. I've some 8580 from a single batch and which all sound similar. My personal favourite is the 8580 5) already answered 6) check the "Step B" page, yes you can select multiple SIDs at once and do your patch/parameter changes at the same time. This is especially for stereo effects. Pan: this requires the AOUT module (very expensive!!!) and an external VCA. It's normaly easier to do the panning effects with an external Fx or a VST Best Regards, Thorsten.
  3. Hi Stefano, 36 EUR are far too much for the community (I don't want to affort this), and ADSL is not practicable. I already own an ADSL "flatrate", ok, I've 100 kb/s download rate, but only 16 kb/s upload rate. Now image that ca. 100 people or more around the world are accessing my PC at the same time... do you see the problem? ;-) We need a professional solution... Best Regards, Thorsten.
  4. Hi, MIOS is only the operating system, which application do you mean exactly? Best Regards, Thorsten.
  5. I'm very happy that you found the reason, I was about to include some debug code into the source code :) Best Regards, Thorsten.
  6. Hi oszilla, yes, the 7805 can get very hot if it is powered with a too high voltage (the difference between the input voltge and 5V is transfered into heat). It is ok so long the backlight of your LCD doesn't start to flicker (unstable 5V voltage). If this happens, then you can either use a seperate power supply for the core module (with a much lower output voltage) or just the C64 PSU (which is the best solution) Changing value on the display via MIDI: the changes will only be visible in edit mode (press the edit button). You could test a program change event to the core, this should always change the patch The only explanation I have for the random values is, that you either forgot to stuff R9 or R2 of the core module. R2 is required to prevent "random patches" if no BankStick is connected to the core. It's also required for the BankStick itself (open-drain output) R9 is required to prevent random toggles on the DIN input Please check this first (especially reg. bad solderings) it could explain everything. Two useful applications: - with the MIDImon you can check if MIDI data is received correctly - with MIDIO128 you can check each button/rotary encoder Best Regards, Thorsten.
  7. Hi, maybe you've already noticed that some content of midibox.org is sometimes not accessible due to "capacitance problems". Today I got a message from my provider that these fails are caused by a disproportionate usage of midibox.org - in short: too many people are accessing the site at the same time. If I'm not able to lower the traffic in the next days, the account will be (temporary) closed to reduce the hit rate. I must say that this doesn't astonish me, since the price for this webpage is very low: 5 EUR per month for 500 MB and "unlimited" traffic. This cannot work over the long term. So, I feel that it's time to change the provider! In the meantime a lot of new offers should be available which guarantee a better server performance for affortable prices. Therefore I'm asking for your suggestions - I don't rely on offers from germany, especially since most accesses are from outside europe. Constraints: at least 500 MB webspace, CGI/PHP/SQL, traffic/month > 20GB (!) (can be higher once the server runs faster) Best Regards, Thorsten.
  8. Hallo, Jitterprobleme kommen (wenn sie existieren) von der 5V Versorgung. Dominik: 1) nein, das Netzteil liefert u.a. 5V und 12V, das V- steht fuer Gleichstrom 2) einer zusaetzliche Sicherung macht bei einem DIY Projekt immer Sinn, auch LEDs sind sehr hilfreich (damit Du auf einen Blick siehst, ob die Sicherung evtl. durchgebrannt ist, wenn nichts funktioniert) 3) Du koenntest den Jittertest aufladen und den Jitter ausmessen. Wenn er < 3 betraegt, dann ist alles ok. Gruss, Thorsten.
  9. But an additional bankstick is not required when you are using a 24LC512 -- do you see the problem? There are too much options ;-) Should I really write down all the configuration variations? This would lead to a page which so much informations that nobody knows anymore, which one is relevant for himself. And the result would be the same: people asking in the forum for their personal configuration. The effect (and effort) would be the same. Best Regards, Thorsten.
  10. Hi, you don't need a special account, just press the edit button Best Regards, Thorsten.
  11. Hi, I never stated that a MB64 could bring any advantage for controlling the MBFM, and I must say that it's not clear to me why this rumor exist. In the meantime I think that the user interface is maybe so unusual, so advanced, that people cannot imagine how ergonomic the usage is without trying it out (note: more than 500 parameters are controllable --- there is no parameter which cannot be modified from the inbuilt user interface) Or do I miss something? Which advantage do you expect from additional knobs? Best Regards, Thorsten.
  12. Another reason could be that an "empty" bank is selected for the slave SID - in this case you will hear the default patch. Does the master send a SysEx dump when you change the patch for SID2? Best Regards, Thorsten.
  13. Hallo, ich habe lange Zeit von Schaltnetzteilen abgeraten, da die Leute hauptsaechlich PC Netzteile ausprobiert hatten, und nur schlechte Erfahrungen gemacht haben. Doch dann kam ich auf die Idee, bei Pollin ein Billig-Netzteil zu bestellen, und war selbst ueberrascht, wie stabil und rauschfrei die Spannungen sind (kein Jitter an den Fadern). Doch das richtige Netzteil zu erwischen ist Glueckssache. Wenn Pollin gerade eins fuer <5 EUR hat, dann KAUFEN und AUSPROBIEREN. Es ist die einfachste und guenstigste Loesung. "Schaltnetzteil DSA-0283A" sieht bspw. ganz brauchbar aus, es kostet 3.95 EUR (+Versand, deshalb ist man gezwungen, nach anderen brauchbaren Sachen zu stoebern, damit es sich auch lohnt. Das ist der Pollin-Trick) EDIT: es hat sich herausgestellt, dass dieses Netzteil *NICHT* brauchbar ist! Gruss, Thorsten.
  14. Thats strange. Maybe the MIDI channel of your slave is out-of-sync to the control surface. How does it react when you change the MIDI channel of the slave from the CFG menu? Best Regards, Thorsten.
  15. Hi oszilla, first please check if you took the changes for MIOS V1.7 into account: http://www.ucapps.de/mios_v1_7_hardware_mods.html if these connections are already according to the new wiring, then you could check your SID module with the mbsid_interconnection_test_b.zip application (test instructions can be found in main.asm) The random value changes could come from a bad junction at your CORE/DINX4 module, I don't think that it is the SID Best Regards, Thorsten.
  16. Hi Rambinator, did you change the LC_EMULATION_ID to 0x14 in main.asm? Otherwise the application behaves like Logic Control, but you want Mackie Control Best Regards, Thorsten.
  17. Hi Julian, in this page: http://www.ucapps.de/midibox_seq_options.html it is clearly stated "Multiple BankSticks for more than 128 patterns and 16 songs are not supported yet, but planned." Best Regards, Thorsten.
  18. Hi js, how do you change the patch? (there are several ways: from the main page, from the CFG menu, via patch change, via SysEx...) Best Regards, Thorsten.
  19. Hi, w/o the C64 PSU it's better to use seperate power supplies. One for the SID module (15V/100 mA should be ok), another for the digital modules (7V/500 mA are possibly enough) It can work with a single PSU (I used this configuration at the beginning), but the 7805 of the core will get very hot, especially when additional consumers (esp. backlit LCD) are connected. Hope that it's clear now. Best Regards, Thorsten.
  20. Hi Wise, I haven't tried this out (currently I don't have access to my hardware), but I can give you four suggestions: 1) use "unsigned char" instead of "unsigned int" -- 8 bit are enough for your calculations 2) you should prevent an overrun in the Timer() function to avoid unexpected results. Just write "if( timer_counter < 64) ++timer_counter;" this obsoletes also the additional check in ENC_NotifyChange() 3) the MIOS driver already provides some kind of deviation function. It doesn't help in your case, since you need a higher resolution. But something which is important to know for you is, that the incrementer can be higher than 1 if the encoder is turned fast. So, don't check "if( incrementer == 1 ), but check "if( incrementer < 128 )" Maybe I will change the type of the incrementer from "unsigned char" to "char" in order to simplify such checks, because "if( incrementer > 0 ) would be easier to use 4) if the results are still bad, try to reduce the LCD messages. Especially the MIOS_LCD_Clear() can take some time, depending on the display you are using (sometimes it can take more than 20..40 mS!) Please let me know if this helps Best Regards, Thorsten.
  21. Super! :) Endlich mal wieder ein Posting, auf das man verweisen kann, wenn mir jemand nicht glaubt, dass mehrmaliges uebererpruefen der Loetstellen durchaus Sinn macht :) Gruss, Thorsten.
  22. thats a good idea what I can assure is, that this behaviour cannot be related to a software bug. I've tested a lot of rotary encoders (also the ones from Voti) and all are working. Encoders are scanned by MIOS itself (and not by the application), therefore everybody who is using rotary encoders, uses the same software routines. The reason why the LCD output of Mandingo sequencer was garbled can only be a assembling or upload problem, which can be sorted out by trying the whole procedure again based on the HOWTOs I think that there are three main reasons for such an encoder behaviour: the encoder type is wrong (DETENTED2 is mostly the correct one, there is only a small number of encoders which require DETENTED), the pins are not connected correctly (try out all combinations), or the encoder has a mechanical defect (in this case check if other encoders have the same problem on the same inputs). Best Regards, Thorsten. Addendum: one encoder of my MIDIbox FM showed a similar behaviour - values were incremented/decremented randomly. The reason was a mechanical defect, I replaced it by a new one, thereafter everything was ok again
  23. Fine - I'm still open to new patches. In the meantime I found the patches of js in my spamfolder (unfortunately this can happen from time to time). I will upload an incomplete second bank soon which will have enough slots for your future contributions Best Regards, Thorsten.
  24. Hi Wise, I will open a new section once the C wrapper is officially released. In the meantime you can ask in a seperate thread. Btw. - the current status: in the last weeks some changes were included into SDCC which makes it incompatible to the wrapper. In the meantime I was able to adapt it to the changes, but there are still some open issues which have to be solved. Issues means here: bugs in the compiler. From time to time I'm submitting bug reports to the SDCC bug database, they were always fixed immediately. So, there is hope that we get the things sorted in 2-3 weeks. Best Regards, Thorsten.
  25. Hi Nick, "is it possible" is not the right question, I guess you mean "is it much effort". My answer: yes, it is. Just use the MIDIbox SID (or MIDIbox FM) firmware instead - they can also be used without the soundchips just to drive the AOUTs. And the internal resolution is much higher than the resolution which is provided by the DAC itself Best Regards, Thorsten.
×
×
  • Create New...