TK.

Hi, you could use ACsensorizer, it's one of the most advanced projects which goes into this direction: http://www.midibox.org/dokuwiki/doku.php?id=acsensorizer_04 If you prefer a small and simple to modify project to implement this by yourself, use analog_toolbox Best Regards, Thorsten.

Thanks for the demo! :) Best Regards, Thorsten.

TODO marker Best Regards, Thorsten.

Beside of the issue mentioned by Nebula, there is another reason why MTC isn't suitable for a "real" step sequencer like MBSEQ: the song position isn't part of the MTC protocol as well. If you select any point of time in your DAW, it's (almost) impossible to determine the new step positions without processing all steps from tick 0 to the new tick derived from the time, especially because tracks could be played backward, or with a progression algorithm... This results into unwanted delays. Best Regards, Thorsten.

Very strange! Currently I've only following explanation for such an effect: Under the assumption, that Notes are played by a sequencer at the same moment where the MBSID Editor sends patches to sammichSID, and under the assumption that you are using a SW based solution to merge the MIDI streams, it could happen that the SysEx data get corrupted during patch uploads. Which operation system are you using, and how do you merge the MIDI streams? (At least I can confirm that there is no problem under MacOS) Best Regards, Thorsten.

Hi Robin, for other readers who don't know the discussed application: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fexamples%2Ffastscan_button_matrix_16x16%2F In this special case, where the SRIOs are not scanned by the 1 mS FreeRTOS Task (like for common MIOS32 applications), but in an endless loop located in TASK_MatrixScan(), only the SPI transfer rate limits the bandwidth. You could increase the transfer rate by writing: MIOS32_SPI_TransferModeInit(MIOS32_SRIO_SPI, MIOS32_SPI_MODE_CLK1_PHASE1, MIOS32_SPI_PRESCALER_64); [/code] at the top of the TASK_MatrixScan() function (before the while-loop is entered) Even PRESCALER_32 or PRESCALER_16 could work, please report which values are working ok for you, this would be interesting! Note: it would be possible to scan at even higher speeds by using a 74HC541 based output buffer for serial signals like I did for the MBHP_CORE_LPC17 module (more infos on this topic if required) Best Regards, Thorsten.

Great idea! Richard is a nice guy, he made my acryl MB808 frontpanel, I can recommend his service! :) Best Regards, Thorsten.

Im Gegensatz zur MBSID V1 kann man bei der MBSID V2 die SID Filter im ENS->FIL Menue getrennt kalibrieren. Die setup_8580.hex bzw. setup_6581.hex Firmware gibt "best guess" Werte vor, doch man kann sie jederzeit aendern. Du kannst also durchaus auf einem Kanal einen 8580, auf dem anderen einen 6581 anschliessen (vorrausgesetzt natuerlich, dass die MBHP_SID Module mit den verschiedenen Spannungsreglern und Filter-Kondensatoren ausgestattet sind). Nachteil: die Stereo-Sounds der Lead Engine kommen nicht mehr sauber rueber. Bei der Bassline und Multi Engine koennen verschiedene SIDs jedoch auch vorteilhaft sein - muss man letztlich selbst wissen. :) Gruss, Thorsten.

Adding the "W+16" (wave at offset +16 resp. 0x10 hexadecimal ;-)) feature was the most simple solution. It's now available in RC38 Note: as long as the MBSID Editor hasn't been updated (maybe tomorrow), the new function can only be used when the patch is directly edited on the CS. Example WT Configuration: Ins Par Spd Key Beg End Lop W16 1 249 12 o 00 01 o * [/code] Wavetable: [code] Pos (hexadecimal) 00 C-7 01 Ky1 ... 10 08 11 04 Best Regards, Thorsten.

RC38 is available now: RC38: o optimized MBNet Handler for fast external access to SID registers o added DEFAULT_CC32_FILTER switch to setup_*.asm - it filters CC#32 for programs which send this CC always together with CC#0 on bank changes o support for "extended SysEx dump" - see also mbsidv2_sysex_implementation.txt o filter mode/channel and waveform flags can now be optionally passed to J5 (configuration has to be done in setup_*.asm file) o (only for Multi Engine): "W+16" flag - waveform can be changed from offset +16 of the wavetable, in combination with another parameter (such as #249), it's possible to control pitch and waveform from a single WT track [/code] Note: due to the new MBNet Handler it's strongly recommended to update the firmware on all cores! Just use the cloning function: press&hold menu while power-on the MBSID and wait until firmware cloning is started. Best Regards, Thorsten.

The application is up&running! :) -> Best Regards, Thorsten.

From the README.txt MIDI Force-To-Scale =============================================================================== Copyright (C) 2011 Thorsten Klose (tk@midibox.org) Licensed for personal non-commercial use only. All other rights reserved. =============================================================================== A precompiled binary is already part of this package: o project.hex (can be loaded into MIOS Studio) Following tools are required to recompile the code: o SDCC o gputils The details are described under http://www.midibox.org/dokuwiki/application_development =============================================================================== Required hardware: o one MBHP_CORE module Optional hardware: o DINX1 + 4 buttons o LCD =============================================================================== This application forces incoming MIDI notes to a selectable scale. Scale and Root note can be changed via DIN buttons, each inc/dec function is assigned to two buttons for higher flexibility with existing control surfaces: DIN 0 and 4: Scale Dec DIN 1 and 5: Scale Inc DIN 2 and 6: Root Note Dec DIN 3 and 7: Root Note Inc The Scale can also be changed via CC#16 (0-127) And the root note via CC#17 (0-11) List of Root Notes: CC#17 Note 0 C 1 C# 2 D 3 D# 4 E 5 F 6 F# 7 G 8 G# 9 A 10 A# 11 B List of Scales (they have been provided by StrydOne - thank you!!!) CC#16 Scale 0 No Scale 1 Major 2 Harmonic Minor 3 Melodic Minor 4 Natural Minor 5 Chromatic 6 Whole Tone 7 Pentatonic Major 8 Pentatonic Minor 9 Pentatonic Blues 10 Pentatonic Neutral 11 Octatonic (H-W) 12 Octatonic (W-H) 13 Ionian 14 Dorian 15 Phrygian 16 Lydian 17 Mixolydian 18 Aeolian 19 Locrian 20 Algerian 21 Arabian (A) 22 Arabian (B) 23 Augmented 24 Auxiliary Diminished 25 Auxiliary Augmented 26 Auxiliary Diminished 27 Balinese 28 Blues 29 Byzantine 30 Chinese 31 Chinese Mongolian 32 Diatonic 33 Diminished 34 Diminished, Half 35 Diminished, Whole 36 Diminished WholeTone 37 Dominant 7th 38 Double Harmonic 39 Egyptian 40 Eight Tone Spanish 41 Enigmatic 42 Ethiopian (A raray) 43 Ethiopian Geez Ezel 44 Half Dim (Locrian) 45 Half Dim 2 (Locrian) 46 Hawaiian 47 Hindu 48 Hindustan 49 Hirajoshi 50 Hungarian Major 51 Hungarian Gypsy 52 Hungarian G. Persian 53 Hungarian Minor 54 Japanese (A) 55 Japanese (B) 56 Japan. (Ichikosucho) 57 Japan. (Taishikicho) 58 Javanese 59 Jewish(AdonaiMalakh) 60 Jewish (Ahaba Rabba) 61 Jewish (Magen Abot) 62 Kumoi 63 Leading Whole Tone 64 Lydian Augmented 65 Lydian Minor 66 Lydian Diminished 67 Major Locrian 68 Mohammedan 69 Neopolitan 70 Neoploitan Major 71 Neopolitan Minor 72 Nine Tone Scale 73 Oriental (A) 74 Oriental (B) 75 Overtone 76 Overtone Dominant 77 Pelog 78 Persian 79 Prometheus 80 PrometheusNeopolitan 81 Pure Minor 82 Purvi Theta 83 Roumanian Minor 84 Six Tone Symmetrical 85 Spanish Gypsy 86 Super Locrian 87 Theta, Asavari 88 Theta, Bilaval 89 Theta, Bhairav 90 Theta, Bhairavi 91 Theta, Kafi 92 Theta, Kalyan 93 Theta, Khamaj 94 Theta, Marva 95 Todi Theta 96 M. Bhavapriya 44 97 M. Chakravakam 16 98 M. Chalanata 36 99 M. Charukesi 26 100 M. Chitrambari 66 101 M. Dharmavati 59 102 M. Dhatuvardhani 69 103 M. Dhavalambari 49 104 M. Dhenuka 9 105 M. Dhirasankarabhara 106 M. Divyamani 48 107 M. Gamanasrama 53 108 M. Ganamurti 3 109 M. Gangeyabhusani 33 110 M. Gaurimanohari 23 111 M. Gavambodhi 43 112 M. Gayakapriya 13 113 M. Hanumattodi 8 114 M. Harikambhoji 28 115 M. Hatakambari 18 116 M. Hemavati 58 117 M. Jalarnavam 38 118 M. Jhalavarali 39 119 M. Jhankaradhvani 19 120 M. Jyotisvarupini 68 121 M. Kamavardhani 51 122 M. Kanakangi 1 123 M. Kantamani 61 124 M. Kharaharapriya 22 125 M. Kiravani 21 126 M. Kokilapriya 11 127 M. Kosalam 71 =============================================================================== [/code] Download: http://www.ucapps.de/mios_download.html Source Code for MIOS8: http://svnmios.midibox.org/listing.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fprocessing%2Fmidi_force_to_scale%2F Source Code for MIOS32: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fprocessing%2Fmidi_force_to_scale%2F Have fun! :) Best Regards, Thorsten.

Great case! And I like the variation of my orignal tune (thats progress)! :) Best Regards, Thorsten.

I feel really honored to hear the alien groove in such a great video! Very well done! ++like Best Regards, Thorsten.

Hi Jerome, if you don't have programming knowledge, you would have to use a standard firmware such as MIDIbox64E Yes, it can control up to 64 LEDrings, or 41 LEDrings + 32 LEDs controlled directly from dedicated DOUT pins. If you need more, you would have to control the LEDs from a matrix (such as LEDrings, where LEDs are connected to a matrix as well) BUt it's impossible to add such an option into the existing MB64E application, you would also have to write your own application, which isn't so difficult if you know C Best Regards, Thorsten.

thanks for the feedback. It's a simple change, so it will go into the next release. thats possible with the lead engine. just step the WT with a LFO, start with a slow rate, make it faster than longer the note is played (in other words: control the LFO rate with an envelope) In the tutorial you will find a WT example which demonstrates exactly how to create such a setup. It shows how to apply the effect on a common pitch sequence, but you could also control ringmodulation/sync this way of course. :) And no firmware change is required to realize this ;) This sophisticated control of the WT via trigger matrix won't be available for the multi engine, because I want to keep it simple. Too many people complained about the complex lead engine in the past, but probably they never noticed that with the multi engine a much simpler possibility is available.... In other words: if you want to create special sound effects, it really makes sense to have a deeper look on the lead engine capabilities. Best Regards, Thorsten.

well, thats always an issue to balance the features of a sound engine. Either they are limited but easy to use, or they are so flexible that only experts can realize good sounds with it (especially sounds which can't be created with the simple ones). I know the wavetable approach of many C64 based solutions, but none of them allows to control almost any parameter of the sound, e.g. also modulators like LFO/EG... mostly they only allow to control the pitch and waveform, thats all... I really wanted this, therefore it got so complex. And now I don't really want to reduce the feature set again just that it matches with other implementations... ;) Ok, I've an alternative solution which you maybe like a bit more: an option which enables direct wave control in addition to any other parameter at offset 16 Means: you enter the sequence for any parameter change (for pitch: #249) between position 0..15, and waveform is controlled from position 16..31 if this option is enabled. Are 16 steps enough? (from my experince it should) How many steps do you need if the sound is created with the lead engine? Best Regards, Thorsten.

Hi Tonka, yes, you are right, currently only a single parameter is played in multi mode - i know that this sometimes isn't optimal, but at the time I programmed this I was a bit carefull by allocating resources to have more freedom on additional user requests. Resources are critical here, as the multi engine runs 6 independent wavetable sequencers in parallel... I can't increase the nmber of WT sequencers, and assigning WTs to instruments makes the usage more complicated than it already is, thats the dilemma :-/ I still don't know a simple solution beside of making WTs assignable to the instrument, would this be ok for you, or do you have a better idea? Btw.: does your sound work with the lead engine, or are there other issues? Best Regards, Thorsten.

no, such LEDs are not supported (they would require a different circuit and firmware) Best Regards, Thorsten.

unfortunately Kvetch did a lot of cross-posting, We should merge the articles to avoid that the discussion about the same thing is forked... I will separate the existing force-to-scale algorithm from MBSEQ V4 and provide it as a dedicated MIOS8 and MIOS32 application. There is no need for "correction tables", just have a look into seq_scale.c more than 128 scales are already part of this file, it only has to be adapted to MIOS8 since the C code isn't compatible to the lmited SDCC compiler, In addition an incoming note tracker will be required to ensure that no Note Off gets lost if keys are still played while the root or scale is changed, or when two keys play the same note (important for live situation) I expect ca. 30 minutes work on this app, So just wait till I'm back from vacation ;) Best Reagrds, Thorsten.

My reply in ca. 4 days (currently don't have access to headphones... :-/ ) Best Regards, Thorsten.

As mentioned in another posting, there will be an example soon. A little bit more patience please, we don't have a 24h programming service here. ;) Best Regards, Thorsten.

problem is, that you are impatient and spread new postings over the forum so that it's hard for somebody to determine how to answer your post (since it's hard to determine your background resp. already available knowledge) You tried to use MIOS32 code 1:1 for a MIOS8 project, this won't work without modifications. Maybe next week I will have the time to convert the example that I gave you to MIOS8. Thats a no brainer for me, it will take maybe 10 minutes... I thought that you wanted to do this by yourself, since you haven't mentioned that you never worked with C code before... But please: be patient and try to keep your postings in a single thread! Sidenote for others: the MIOS32 tutorials provide much more examples, e.g. also how to realize MIDI clock timed code for an arpeggiator. They are not compatible to MIOS8 as I think that programming on 32 bit is moe fun anyhow. Best Regards, Thorsten.

ok, i assumed that you are using 6581s since you forgot to mention this, and since 8.7V is in the good range for 8580s. There is probably no problem with the VR, it could just be a measuring error if you are using a low-cost meter (or measured from the wrong ground) Back to your original posting: could you please attach a sample where we can hear different filter modes, just to get an impression about the hum that you mean? Please also turn on/off the Ext. filter input - if enabled, you should hear a loud hum as long as no cable is connected to Audio In - nice comparison! Best Regards, Thorsten.