Jump to content

TK.

Administrators
  • Posts

    15,247
  • Joined

Everything posted by TK.

  1. Hallo, wenn sich die LEDs (DOUTs) nicht ansteuern lassen, dann liegt es wohl am SC, SR oder DO Signal (Kurzschluss?). Mit dem srio_interconnection_test kann man diese Signale testen. Gruss, Thorsten.
  2. Yes, this is possible - you can request a SysEx dump with Serge's MIDIbox Editor, thereafter you can save the bank as .ini file, and edit it like before. To ensure that nothing gets unintentionally lost (e.g. for the case that you click the wrong button), you could create a full backup of the flash and EEPROM contents like described here: http://www.ucapps.de/mios/mios_backup.txt Best Regards, Thorsten.
  3. Here some pictures of Sasa's Traktor Controller. He wrote: What a fantastic work!
  4. TK.

    LCD options

    P.S.: if compatibility does matter, you could write a custom LCD driver instead of switching between the displays via MIOS_LCD_Init A CLCD custom driver is already available, you only need to redirect the enable lines depending on the cursor position Best Regards, Thorsten.
  5. TK.

    LCD options

    LCDs cannot be cascaded, the data and control lines have to be connected in parallel, and the enable lines have to be controlled seperately. By using the MIOS_LCD_Init function with different parameters for IO pin assignment of the enable line, you can select as much LCDs as IO pins are free. Anyhow, you will need to adapt the software... if you build up an application from scratch, this will be easy. If you are trying to consider LCD switching in an existing application, it will be a lot of effort Best Regards, Thorsten.
  6. I second that, 32 buttons/LEDs are very important, the additional LEDs not at least to display the current sequencer position correctly. A roll function (selectable like the accent for each step seperately) would be usefull as well Best Regards, Thorsten.
  7. it's not recommented, especially if you want to use the MBSEQ V3 firmware later, where I won't support other display options than 2*2x40 LCDs anymore - with the advantage, that I have the freedom to totally customize the screen layouts This is, how the V3 screen currently looks like: Best Regards, Thorsten.
  8. This is the new red-blue housing for two SIDs, made by Rio :)
  9. Hi Shum, so far I remember, after the installation of the yamaha driver, there should be a new icon in the system setup directory (where you also setup the display, the soundcard, the network, etc...) - click on this icon, and you should be able to select the COM port. Regardless of the selected COM port, MIOS Studio and MIDI-Ox should already list a new MIDI interface, do you see it? Best Regards, Thorsten.
  10. If Trevor has no problems with this, it's ok. Nevertheless, I would mention the original name in each re-used file, regardless if (small) modifications have been made or not. It's just good style To the CC - in the FAQ http://creativecommons.org/faq#Can_I_use_a_Creative_Commons_license_for_software? you can read: Can I use a Creative Commons license for software? Creative Commons licenses are not intended to apply to software. They should not be used for software. We strongly encourage you to use one of the very good software licenses available today. [/code] either GNUPL if it's ok for you if somebody uses the code commercially (e.g. sells your projects on Ebay for profit), or no "copyleft" license at all, but just something like this hint, which can be found in most of my projects in the meantime: [code] ; Copyright <date> <name> ; Licensed for personal non-commercial use only. ; All other rights reserved. Best Regards, Thorsten.
  11. What I don't like on this project is, that he is using Trevor Page's source code, and replaced the copyright by his own. And he uses a license which is not intended for software. Best Regards, Thorsten.
  12. TK.

    mbSEQv2.4b

    Hi Moxi, yes, this is normal for all newer releases, since it was too difficult to keep this file up-to-date for all the different MPLAB versions (I don't use it) The recommented build process is described here: http://www.ucapps.de/howto_tools_mpasm.html Best Regards, Thorsten.
  13. Still works fine and makes fun - next target is to enhance the track length of MBSEQ to 32 steps, this can take some time, since a lot of code has to be changed... however, I've a new motivation to finish this soon ;-) Best Regards, Thorsten.
  14. Found the solution: the trigger event controls some S&H modules, and they can be bypassed. So, it seems that 4 assignable parameters and the gate can be controlled via MIDI (I haven't tried this under realtime conditions yet), each sample module can be assigned to a seperate MIDI channel - nice toy! Best Regards, Thorsten.
  15. I'm just doing the changes in Massive 1.1 for MIDI control over the sample modules. It isn't so easy like expected, because the voices are using some kind of multiplexing in order to transmit values and events over a single wire (Smpler Macro, G input). I found out how to control the gate and the "yellow" parameter (normaly assigned to velocity or pitch), but the pitch value is only taken when two pulses are sent over the "2trg" line. However, I will keep trying. There is at least the possibility to remove this multiplexing completely (but it's a "Massive" change ;-) MBSEQ V3 will support a configuration, where for example two CCs and one note (gate) with variable length is sent from a single track - this is ideal for controlling the Massive sample modules (I see it now as one of the reference applications) Best Regards, Thorsten.
  16. I haven't read the complete thread, but if you only need an hint how to measure a data rate: just count the ticks within a constant time span, and capture/reset the counter periodically, e.g. from the Timer() function. It's the same approach like discussed here http://www.midibox.org/forum/index.php?topic=3858.0 Best Regards, Thorsten.
  17. Hi Evan, welcome to the forum! I'm a Reaktor user since R3. I don't use it so often (since I'm more busy with MIDIbox development than making music), but it's always big fun to play with it. E.g., for these arpeggiator examples: http://www.ucapps.de/midibox_seq_tutorial4.html I used the Junatik synth. In the first (experimental) MBSEQ demo at my website I used a slightly modified Vierring filter. I replaced the integrated step sequencers by generic CC receivers, and controlled them from the MBSEQ. I think, that a similar approach is possible with Massive Attack - I will try this out this evening (thanks for the inspiration!) I'm currently working on MBSEQ V3, and this is a nice check for all the mods I made today. Best Regards, Thorsten.
  18. Mir ist eingefallen, dass bei der LED Matrix Option die Shift Register ("DEFAULT_TRACK_LEDS_*_CATHODE") falsch zugewiesen waren. Darueber sind schon zwei Leute gestolpert... Du wahrscheinlich ebenfalls. Die Version v2.4b gibt es nun an bekannter Stelle Gruss, Thorsten.
  19. Here my teaching words: successfull scientists are not the guys who only have a detailed knowledge about everything they are doing, but the guys with good social skills. If you would communicate with people in a friendly and respectful way, you could get more useful informations than just demanding for details in a rude way which don't really bring you forward. Some of us have already noticed this, and therefore didn't spent much effort to help you (thanks Moogah and all others for your patience!). If you wouldn't focus too much on details, but if you would start a chatter about a certain topic in a normal way, like you would talk with reallife people, then you would propably already have experienced, that perhaps Traktor doesn't support resolutions higher than 7 bit (this was at least the state in R4), and that this has to be evaluated first with a newer version (R5 or higher?). You would propably also already know, how to determine 14bit capabilities, and where to find ready made programming examples for 14bit MIDI messages, etc... these are the small but important details which cannot be read in any documentation, but which can be easily found out by asking the right questions to the right people at the right time with the right words. Keep up learning! Best Regards, Thorsten.
  20. This is not correct, and I must say: I'm also out of the game; it doesn't make much fun to "discuss" with somebody who ignores most of the previously written stuff. Hope that you at least know, that MIOS is copyrighted and especially not allowed to be sold via Ebay... My last hint: you can easily find out the real behaviour by doing some experiments on a MIDIbox. Best Regards, Thorsten.
  21. I've uploaded the files to this location: http://www.ucapps.de/tmp/mbseqxc.zip Best Regards, Thorsten.,
  22. In this case the distance between a value change (-> USER_AIN_NotifyPin() is called) is 3, 5, 6, 7; accordingly the hook might be called more often then required. Calculation example: a common 7bit CC should be sent, the 10bit conversion result is rightshifted 3 times to get the 7bit value (the same as if the conversion value would be divided by 2^3 = 8 ) lets move a pot from 0 to 25. With a deadband of 6 following values would be propagated to USER_AIN_NotifyChange: 0, 7, 14, 21 The converted 7bit values are: 0, 0, 1, 2 With a deadband of 7 (which is the recommented value for 7bit transformations), USER_AIN_NotifyChange will only be called three times: 0, 8, 16 - and the converted 7bit values are: 0, 1, 2 Best Regards, Thorsten.
  23. Normaly you are using a deadband of 7 for 7bit, 3 for 8 bit, 1 for 9 bit, 0 for 10 bit resolution. There is no need for providing values higher than 255, therefore it's only an unsigned char (this saves memory) did you write this question before or after you've read audiocommander's quotes? Best Regards, Thorsten.
  24. Hallo, den 78xx hast Du richtig angeschlossen; kann es vielleicht sein, dass es ein Problem mit der Massefuehrung gibt? Gegen welchen Masse-Pin hast Du die Spannung denn gemessen? Zu 2) ja, das liegt am grossen Elko, wird sich aber schnell wieder geben, sobald bspw. die Hintergrundbeleuchtung des LCD angeschlossen ist. Gruss, Thorsten.
  25. A promising project! :) I don't use the schematic tool of eagle, because the results are looking ugly and not always understandable for electronic newbies. Instead I'm using xcircuit (a derivative of xfig) - not because it's the best, but because I'm familiar with this program since ca. 10 years and just love it :) Best Regards, Thorsten.
×
×
  • Create New...