I might not be up on all the competitors these days. Are there some alternatives that come to mind for you? The new MFB looks great but monotimbral. A bit less screen real estate too but more knob per function so maybe a draw on that front. Are there others? I’d consider a swap for the right box…
Sadly, Multi-timbrality isn’t a focus for most synth manufacturers.
I never got to explore the way the Multi mode was implemented on the Parva. Most manufacturers get it all wrong though. Elektron and Nord seems to have it well figured out for non-destructive multi editing.
To answer your question, I dunno. Prologue is close-ish, but again mono timbral.
2 Likes
Sorry to resurrect an old post but since the official website is broken i dont know where to ask…
Im trying to send program changes from a DN MIDI track to the Parva (v0.70) but i get some strange behaviour. It seems like the bank in the MIDI track controls the bank, the sbank controls the program and the program does some weird shit and nothing starts to work untill i change the value.
I’ve tried to search for the Parva’s midi implementation for program changes but ive got no luck so far. Help? 
1 Like
The manual that seems to still be available on the Futuresonus website does not give information about the Parva’s response to Program Change messages:
https://futureson.us/parva/manual/
I recall a previous topic on Elektronauts where this aspect of the Parva was discussed:
I infer from my post on that topic that you can use BANK (not SBNK) in conjunction with values of PROG on the DN to call up patches in Parva’s banks A to F, but that Program Changes to call up Multis might never have been implemented.
Perhaps a Parva owner like @Analogic can tell us more.
@youmakeme, can you tell us in a little more detail what happens with your setup; start by setting BANK and SBNK to ‘Off’ on the DN and describe what is happening in response to PROG changes only.
2 Likes
I was working through a different program change idea with my Parva (see the thread Peter linked, it was about program change with multis), so I’m not sure if I can be too helpful but I’m happy to try things out on mine if you need. Maybe I’ll learn something! I’m more of a program change follow type user of program change, so some of the more advanced ways of doing things still confuse the heck out of me.
On the multis front, I can see the original Futuresonus forum thread with all the details has gone dark, so from memory I think there was something about the existing program change implementation being set up to, while in multi mode, change programs on a voice by voice basis. (I was looking for it to change on a multi by multi basis.) Brad talked about making a change that would remedy the behaviour (can’t recall exactly) but this conversation was all after the 0.70 firmware release. I thought a simple fix might have been to assign banks A and B to multis instead of M and N.
Hey first of all thanks for the Reply!
If I recall correctly, in previous versions of the Parva firmware it worked like you say (BANK and PROG) but in this version SBNK seems to be the one selecting the correct program.
If i use PROG it seems to change program for a second and then reverts to the first program in the current bank. Maybe its a bug?
I tried monitoring the DN Midi out and it seems like it only starts sending BANK and SBANK messages after I put something in PROG. I also have a Blokas MidiHUB so maybe I could hack a solution…
Multi patches are located on Banks N and M and let you select a midi channel and voice alocation for each individual patch. Then you can send a program change message to each channel to change each patch individually.
Perhaps the implementation was changed to something non-standard?
Make sure that you are not sending Program Change messages whenever the DN’s pattern changes by disabling PROG CH SEND in the DN’s SETTINGS > MIDI CONFIG > SYNC menu.
That is expected behaviour for a MIDI device.
1 Like
