Jump to content

TK.

Administrators
  • Posts

    15,246
  • Joined

Posts posted by TK.

  1. Mir gefaellt der Matrix-maessige Aufbau auch ganz gut - vor allem die beschriftete Folie erleichert die Uebersicht ungemein, ausserdem laesst sie sich nach Bedarf mal schnell austauschen. :)

    Als spezielles Feature moechte ich kurz nochmal Joergs Idee aufbringen: er schlug vor ein paar Monaten vor, die LED-Kraenze durch LED-Balkenanzeigen zu ersetzen, wie bspw. diese hier:

    !RBG1000.jpg.

    ...die waeren vielleicht auch etwas fuer Deine Box :)

    Gruss,

           Thorsten.

  2. Hi Ian,

    it makes no sense to control all available parameters with a MIDIbox64, thats the reason why I want to design a dedicated user interface. Biggest problem are all the flags for the waveform, LFO, ENV, Filter assigments, which must behave like toggle switches... I think that nobody wants to build a big controller box with over 100 buttons, just to have access over 10 of them during the daily work. The main purpose of the hardware user interface will be to provide a more efficient control with an adequate number of pots and buttons (maybe 30 pots and 20 buttons... but I don't want to tie down myself before I have implemented all sound features!), with some LEDs (must) and with messages on a (optional) LCD.

    Temporary usemodels:

    • use any MIDIbox controller for parameters which should be accessed directly (tuning, LFO, ADSR, filters) in conjunction with your sequencer program or MIDI-OX to switch on/off the waveforms and LFO/ENV/filter assigments
    • create a MIDI control interface with your sequencer if it provides such a function - Logic: Environment, Cakewalk: Studioware Panel, Cubase: Studiomap
    • wait for Serge's MIDIbox SID editor :)

    Audio-In: yes, it's a common audio input, you can connect it with any Audio source (another SID module, another synthesizer, a microphone amplifier, ...)

    Best Regards, Thorsten.

  3. Hi Serge,

    I already wrote it in the news, but here again, just for the records: there is a link below the forum index (MIDIbox Forum mainfolder) which leads to an oversight for the 10 most recent articles. Currently it doesn't work correctly because of some inconsistencies caused by the converter script, but this imperfection will be automagically fixed after the first 10 regular posts ;-)

    I fixed the boards subject for the dutch section - I should adjust my Babelfish  :-/

    Best Regards, Thorsten.

  4. Hi TraiZor,

    I never twiddled on a Doepfer Pocket Dial, so I'm not the right person who should give ratings for a Dial and a MIDIbox16E... based on the specs the MIDIbox16E is better  ;D (optional LCD, optional LED-Rings, higher resolution, BankStick, multiple MIDIboxes can be synchronized via Program Change, ...), however, the Dial is just a commercial product with main focus on parts and assembly costs instead of usefull features...

    There are different usemodels for the MIDIbox16E, because every single encoder can be assigned to different modes.

    A normal synthesizer or MIDI program can only handle with "absolute values", so just assign every encoder to the "ABS mode", and the MIDIbox16E will send the same MIDI events like known from a common MIDIbox with pots/faders. The advantage is the bankswitching: if you select another bank, the internal encoder values will be restored to the saved values of the new bank - so that you don't have to readjust the pots. Also the LED-Rings and the messages on the LCD screen will be updated, so that you see the "virtual pot positions" of the bank immediately.

    If your sequencer or synthesizer provides MIDI feedback, the virtual pot positions can also be changed from external. I use this feature in conjunction with Reaktor: when I switch to another snapshot, the program sends all values; the MIDIbox16E collects all parameters which are assigned to the current encoders and updates the "virtual pot positions". Btw: it works on the same way with the MIDIbox SID when it gets a program change event - a very important feature :)

    Now to the different relative modes: if a program or synth supports relative increment/decrement values, you can assign the encoders to these events. The advantage compared to absolute values: no feedback is required (if you don't use the LED-rings) and values greater than 7-bit can be handled with high precision.

    Best Regards, Thorsten.

  5. I don't know an alternative (and already available) oscillator which comes with a sync input, but maybe you will find something similar with http://www.google.com ; my indention was just only to demonstrate how to adapt CV outputs to the analog inputs of a MIDIbox...

    There was also a question in the old forum regarding the frequencies which can be achieved: with the appr. Cap/Resistor combinations the ICL8038 can oscillate with up to 300 kHz, but since the waveform values have to be send over the MIDI line, the maximum MIDI transfer speed limits the maximum frequency.

    A MIDI value requires appr. 1 ms, that means: a sine waveform with 100 Hz will get just only ca. 10 samples (audible result: an automatic sample & hold effect ;-)

    Best Regards, Thorsten.

  6. Yes, there is a link below the forum index (MIDIbox Forum mainfolder) which leads to an oversight for the 10 most recent articles. Currently it doesn't work correctly due to some inconsistencies caused by the converter script, but this imperfection will be automagically fixed after the first 10 regular posts  ;)

    Best Regards, Thorsten.

×
×
  • Create New...