[DrBunsen]

Oh I see what you mean.  And that's right given the audio example.  6 monophonic voices would be 6 different single OSC patches.

Quote

With MIDIbox SID V2 the Volume is available as 8th modulation target column. Although the SID chip only provides a 4bit resolution for this parameter

Could there be (or is there already) an option to route this to an external VCA or DCA? (or indeed an integrated VCF/VCA like the SSM 2045 or CEM 3372)

[TK.]

V2A -> see http://www.ucapps.de...d_manual_e.html

In addition, from the mod matrix, you can route any mod path to any CV out.

Btw.: is there anybody beside of Wilba who already uses the MBSID V2 and can provide really useful suggestions?
I've the impression, that either the firmware has so many bugs, that you've uploaded v1 again, or that the usage is so complicated, that nobody really likes it.

Best Regards, Thorsten.

[QBAS]

It is also about v2 since I tested it only on this version.

Is this possible to set real mono sound from two sids simultaneously?
I have alvays differences between sound from left and right speaker- a specially heared on phones. It`s like pseudo-stereo. Of course it can be usefull sometimes, but when it is always, I would like to ask if you have possibilities to hear real mono (the same sound from left and right side).
Of course when I press "mono" function this effect still is played.

Becouse I`m very noob with electronic audio - I not checked values of capacitors and rezistors (when I built sid modules)- with one excepion: filter caps - I used this spuerb from ebay. So maybe it is reason why I have differrent sound from sids?

[TK.]

The SID has freerunning oscillators, which means, that phases are not in sync so long you don't reset them. The phases can be synchronized manually by setting Phase=1, and they are synchronized automatically while changing a patch.

In addition there could be of course small sound differences, especially for filtered sounds. They especially happen when you are using different SID revisions - and yes, it could also depend on the filter caps.

For real mono, it's better to use a single audio channel and pan it to the middle
The mono flag was intended for people who don't own a second SID...

Best Regards, Thorsten.

[rutgerv]

Nice work TK!

what is the reason for the choice of a 6-note polyphonic mode? Why not 8? Is the PIC's processing power the limiting factor?

The reason I ask is because I've almost finished the design of a single PCB containing 8xMBSid + 8xMoog filter and I was hoping to use this hardware for an 8-voice polyphonic synth (or a 4-voice stereo poly synth). I treat each SID as if it's a single voice with 3 OSC's. So each SID has an independant signal path, through a Moog filter to an output.

Greetings,

Rutger

[TK.]

Hi Rutger,

6 voice polyphony is handled internally by each core seperately for multi engine patches.

You are talking about some kind of global polyphonic mode (I call it "super-poly"), in which one core manages the voices of all SIDs connected to master and slaves.
This mode has been requested multiple times, and I'm sure that I will implement it sooner or later. But it won't be part of the first MBSID V2.0 release, as I have to do some evaluations first (and for these evaluations I need a complete firmware).

I especially have to check, if under full load ECAN messages can be broadcasted to all slaves without handshaking - this is a requirement for fast access to oscillator voices. If this doesn't work stable enough, super poly will propably add a latency of 1..2 mS

I think that this currently isn't a big impact on your configuration. You are already able to do a lot of great things with 8 moog filters connected to the audio output of each SID. Just only the availability for a poly mode with seperated filter handling will be available later (maybe end of this year)

Best Regards, Thorsten.

[Razmo]

Hi again Thorsten! :O)

I just thought; this super-poly thing you're talking about, is this a mode that would work just like any other oldschool analog synth from the 80's with 8 voices?... I mean, that you can play the 8SID monster polyphonically vith dynamic allocation of up to 8 voices? (meaning each SID is considdered a seperate voice)...

I sure hope this will be possible because that is probably the most useful configuration for me B-) ... I've always dreamt about a SID synth with 8 voices.

And about those 1-2 ms... no big deal really is it?... MIDI itself seem to have some latency between noteon messages. In fact such slight variations are what makes analog synths so special... small timing irregularities etc...

and IF you implement the super-poly mode, PLEASE PLEASE PLEASE also include a UNISON mode for this configuration!!!!!! ... UNISON is the total joy of older KORG synths, and the more "latency" between voices fired off only add to the magic... believe me! ;O) 3OSC - 8voice unison = 24 oscillator unison!!!! WOOOOOW! :OP

BTW. I'm hooked up for the 8SID PCB now, so I'll soon be participating in testing and idears again Thorsten :O)

[Razmo]

...and Thorsten: When you have implemented full SysX implementation of controlling the V2, then I'd be happy to make a Sounddiver Adaption for it :O)

[Wilba]

If by "UNISON mode" you mean play each of the four SID engines simultaneously from the same note events, then you can do that now in V1, and do it with even less latency in V2, since all PICs receive the same MIDI In. Just configure each SID engine to the same MIDI channel  ;D This actually sounds awesome when using the Multi engine, as you then get 6-note polyphony and can detune or transpose each SID engine to layer/fatten the sound (i.e. four oscs per note).

[TK.]

Hi Razmo,

yes, super-poly isn't a big deal, but there are about 1000 other features I want to add to the first final release which are also cool, and also easy to implement. Step by step w/o hurry - I'm young, I've the time... ;-)

Full SysEx Implementation is already available for the lead and multi engine.

There is no user-friendly documentation, but as you are a programmer:
The SysEx strings are listed in midibox_sid_sysex_implementation.txt
The SysEx structure in app_defines.inc, search for "Patch Record Structure"

Most important for Sound Diver handling is the capability to divide a 8bit value into two 4bit values, because the sysex data part consists of 1024 nibbles for a 512 byte patch

Best Regards, Thorsten.

[Razmo]

Thorsten: hmm... nibbles... well I'm certain that Sounddiver can decode that, just hope it will not pose too much of a hassle... I assume the reason for the format is 8 bit values right?

With regards to the UNISON feature, just remember that having a bit of "sloppiness" in the triggerings can add a lot of fatness to the sound... maybe it's worth experimenting with a parameter that will offset the voices by a set amount? ...

Another thing (don't know if I've asked this before): Will it be possible to control the oscillators of a single SID independently from three different MIDI channels? ... To me this is very important since NO real synth has this capability that I know of... one of the most used features of the SID tunes from the past is when two channels are playing different melodies, and one is either sync'ed or Ringmod'ed to the other... the melodic clangy results are much of the C64's charm from back then, and something I'd really like to be able to doo.

[TK.]

Most of your requests are already implemented! :-)
See the user manual and listen to the sound examples: http://www.ucapps.de...sid_manual.html

Unisono: search for detune. Offset: search for phase offset and delay

Independent control of oscillators is possible with the multi engine. The voices are dynamically allocated, but especially for ring/sync effects I've added an optional static allocation. So: yes you can do this, but the gate of the third oscillator needs to be controlled from a seperate MIDI channel. By enabling GSA, the gate will stay active once it has been triggered the first time.

Best Regards, Thorsten.

[rutgerv]

Hi Thorsten,

thanks for the reply on the super-poly mode!

I've just finished the design of one big PCB in Eagle and sent it to Gold Phoenix PCB for manufacturing. It contains:

-8 SID's (jumpers to select the proper voltage and caps for different chips)
-4 cores
-the master core with 8 banksticks, display connections and step B surface
-4 rows of AOUT_LC's (resulting in 12 CV outputs at 12-bit resolution)
-8 independant Moog filters with CV controlled cutoff and resonance (!) (however to keep the number of AOUT_LC's down the filters share the resonance CV in pairs (no need for differences in resonance between left and right channel))
-Output stage/mixer and headphone amp
-Custom PSU (+12V/-12V/+9V/+5VDigital/+5VAnalog seperate analog and digital grounds)

When the hardware is finished I'll have to do some small modifications to get the AOUT_LC's set to the 12-bit resolution for every output (and not the 2*8 or 1*12/1*4). When I have it working I'll be happy to help out with experimenting and programming the superpoly mode!

Greetings,

Rutger

[Acid303]

Hi Thorsten,

first of all, thanks for the new firmware :) Very nice indeed !

Now I have a little problem with the OSC Waveform button....it doesn't work ...

I have the new PIC18F4685 and the latest BETA...the button is not working...so I uploaded the old firmware again...V1.74685...the same result...

Unfortunately I can't try it with the old PIC because of the 4 cut datalines of the LCD (D0-D3) etc.

I haven't changed anything ,so my question is, if this is a bug in the firmware? I checked all connections but everythings looks just fine...

Thanks for your answers :)

Regards Axel

[TK.]

Hi Axel,

I'm very sure that the waveform button is working - currently there is no known bug in the firmware, only missing features. ;-)

Follow this guide for troubleshooting: http://www.midibox.o...p?id=din_module

Best Regards, Thorsten.

[Acid303]

Thanks for your fast answer...and yes, you are right....sorry ;)

The button works now....It was my mistake....I had just to resolder the OSC Waveform on the back of the PCB...

I was wondering why it had worked before, but nevertheless now itworks fine again...


Go on with your good work ;)

Best regards,

Axel

PS: Before I forget it... will there be a function where you can delete a patch? So you can right start with "nothing" , all parameters "0"?

[TK.]

Quote

Before I forget it... will there be a function where you can delete a patch? So you can right start with "nothing" , all parameters "0"?

Just press the SHIFT button (formerly called LINK button), and then the button below "Init Patch" (it is the fourth select button so far I remember)

Of course, parameters won't be zeroed - but they will be set to useful initial values. Only one oscillator is used, all modulators disabled, etc.. you will see and like it :)

I would propose to go through the "first steps" guide, it gives you some hints about the general use model: http://www.ucapps.de..._manual_fs.html

Best Regards, Thorsten.

[Acid303]

Oh yes :)

Just found it... ok...i did read the whole manual....but there are so many new features :) ...ok, i will study it more intensely ;)

Thanks again,

best regards,

Axel

[Sasha]

I am using Ableton Clips to send program change before clip send notes, but V1 didn`t act quilck enough for gapless play. Is the same delay present on V2 or is this solved because of the new PIC?

[TK.]

The patch initialisation time is mainly limited by the BankStick bandwidth, there is no way to improve this anymore (it's ca. 30 mS for 512 bytes)

But the good news is, that due to the fact that slaves are connected via ECAN, the MIDI bottleneck (200 mS for 512 bytes) doesn't exist anymore - means: a slave is configured within the same time! :)

In both cases "gapless playing" is not guaranteed - the only chance is to use a MIDI sequencer which allows to define a negative delay for program changes - like Logic Audio

Best Regards, Thorsten.