Messages

61

preenfm2 and preenfm3 / Re: dfu mode issue

« on: January 12, 2021, 08:13:55 AM »

It seems as though both the 5v and 3.3v lines are broken somewhere.
Strange. Can you measure the voltages on the main board again without the controlboard attached?

Bad sdcard could be a display pcb issue, did not work on mine either. I ended up soldering one of those sd to MicroSD adapters to the pins, that works reliably...

62

preenfm2 and preenfm3 / recall mix via program change

« on: January 10, 2021, 11:54:26 PM »

last one for today :-)

it would be great to recall mixes by program change.
so a global menu entry for program change mode. voice or mix recall.

EDIT 1: also recalling voices from different banks via cc0 does not seem to work reliably, is this supposed to work? i thought i could change the bank by cc0 and selecting then via program change which patch to load.

EDIT 2: so program change of mixes does kind of work. do you really want global midi channel to be part of a mixer preset? still it is unclear to me how you decide what program change does, can you elaborate?

63

preenfm2 and preenfm3 / [fixed v0.104] poly aftertouch does not work with note shift value other then 0

« on: January 10, 2021, 11:48:22 PM »

as the title suggests, poly at should take note shift into account :-)

64

preenfm2 and preenfm3 / [fixed in v0.104] mod destination fdbk does not map well

« on: January 10, 2021, 11:29:33 PM »

the fdbk mod destination seems not to map very well, since it only is adjustable between 0 and 1 (unlike IMs) you can only set it to a very low value in the mod matrix. this does not work well when you want to use it together with another destination. maybe divide the mod mult by 10?

65

preenfm2 and preenfm3 / voice volume as mod-destination

« on: January 10, 2021, 11:18:56 PM »

i would like to control a voice volume by aftertouch. somehow i cannot get it to work via the mod matrix. mix * kind of works but only to lower volume on a high aftertouch value. (i need to set mult to a negative value). i would like to make the patch louder when i apply more pressure.

can volume of a voice be added to the mod-destinations?

66

preenfm2 and preenfm3 / Re: compressor per output instead of voice/instrument

« on: January 10, 2021, 05:49:03 PM »

I understand that decision, it is not ideal for mpe, but it is not the normal usecase

67

preenfm2 and preenfm3 / Re: [fixed in v0.102?] Hanging notes...pfm3

« on: January 09, 2021, 11:46:22 PM »

ok, for now i could not wrap my head around it. maybe it will be easier just to add a small buffer (10 notes as you suggest) to the glide part of the code?

68

preenfm2 and preenfm3 / compressor per output instead of voice/instrument

« on: January 09, 2021, 11:44:55 PM »

hi xavier,

it would be great if the compressors could act on the actual outputs, and not on the voices.

if i want to play the preenfm3 as "mpe" synth, the compressors are not so useful. if i set all the voices to output on 1-2 for example, it will still distort. from a menu standpoint i don't really know where to put it, since the mixer is set to work with those 6 voices. maybe a second page in the out section could contain the active combinations and compressor options.

69

preenfm2 and preenfm3 / Re: Operators as source in matrix?

« on: January 08, 2021, 09:51:09 AM »

Lfo would be your best bet, but yeah, they don't go far into audio range. Xavier outlined somewhere in the forums how fast the mod stuff is updated on Preenfm2, I guess it is a bit faster but similar on the preenfm3.

I don't have that Post ready, but you should be able to find it somewhere. This discussion was also relevant for the eurorack version and cv modulation.

70

preenfm2 and preenfm3 / Re: Operators as source in matrix?

« on: January 08, 2021, 07:47:22 AM »

i think this came up before. the matrix is not updated fast enough to make this feasible. (audio range).

what are you trying to modulate with an operator?

but maybe this has changed on preenfm3.

71

preenfm2 and preenfm3 / Re: PreenFM3 skippy encoders ?

« on: January 05, 2021, 05:44:59 PM »

If it only happens on one encoder that would indicate a "bad" encoder, no?

Xavier, you could compile him a firmware with switched encoders so he can see if the faulty encoder moves...

72

preenfm2 and preenfm3 / Re: [fixed in v0.102?] Hanging notes...pfm3

« on: January 05, 2021, 11:38:02 AM »

Just tried v. 0.102.

it is again better, there are only a few missing notes still. they all happen, when there are notes overlapping, never when only one note is held down. I will again try to find a way to reproduce this on PD or similar. Never got a hanging note! Great work...

I will try to make some sense of timbre.cpp to see if I can implement something.

Your solution with a buffer of 10 notes (a 2d array with not pitch and timestamp?) Sounds very reasonable...

73

preenfm2 and preenfm3 / Re: Hanging notes...pfm3

« on: January 02, 2021, 09:38:02 AM »

Yes, I thought about those 6x problem as well. A buffer of 10 notes would already be great!

For the moment I don't have a stlink board. Can I still compile and upload via DFU?

74

preenfm2 and preenfm3 / Re: Hanging notes...pfm3

« on: January 02, 2021, 12:26:48 AM »

ok, i just sent you a PD patch to show one of the problems i am having with lost notes. as it only happens with rather short notes, i guess it comes from your fix to disregard notes that do not yet sound...

here is some code from axoloti (from the object that handles monophonic incoming midi, with the held down keys saved in an array, and simply ordered by a counter (p++) once a key is released, the code scans the whole array and finds the least recently used key (the one with the highest number stored and plays that. i don't want to "lecture" you or something, but i really would like a proper mono handling on preenfm3, since in this state it does not work correctly for me. and since i know for a fact that many synths do it like on axoloti (or very similar) i thought i post it as an example...

Code: [Select]

if ((status == MIDI_NOTE_ON + attr_midichannel) && (data2)) {
  if ((data1 >= attr_startNote)&&(data1 <= attr_endNote)) {
    _velo = data2;
    _note = data1-64;
    _gate = 1<<27;
    _gate2 = 0;
    np[data1-attr_startNote]=p++;
  }
} else if (((status == MIDI_NOTE_ON + attr_midichannel) && (!data2))||
          (status == MIDI_NOTE_OFF + attr_midichannel)) {
if ((data1 >= attr_startNote)&&(data1 <= attr_endNote)) {
   _rvelo = data2;
np[data1-attr_startNote]=0;
int j;
int np2 = 0;
int n2 = 0;
for(j=0;j<attr_endNote-attr_startNote+1;j++){
   if (np[j]>np2) {
      np2=np[j];
      n2 = j;
   }
}
if (n2>0) {
  int nn = n2+attr_startNote-64;
  if (nn != _note) {
    _gate2 = 0;
    _note = nn;
  }
}
else _gate = 0;
}
} else if ((status == attr_midichannel + MIDI_CONTROL_CHANGE)&&(data1 == MIDI_C_ALL_NOTES_OFF)) {
  _gate = 0;
}

those attr_* "variables" are actually constants that you can choose before you compile a program.
_gate is only triggered on non legato playing, _gate2 is always triggered when a new note is played.
_note contains the pitch obviously
np[] is the array that contains the notes played if non zero and also the order in which they were depressed.


is there a "simple" way to implement something like this within the preenfm3 eco-system? if you point me to the right direction i can also have a look myself. will try to install the cube stuff to compile the firmware.

thanks for considering.

75

preenfm2 and preenfm3 / Re: u.i. name entry suggestion

« on: December 27, 2020, 11:07:03 AM »

Funny remark... I got a dab+ radio for Christmas, which also has a menu to enter a password for wireless access..  also with an encoder

So one other suggestion, inspired by the radio. If you move one position right, copy the letter you entered before and use it as a starting point, it irritated me first but it's surprisingly useful and fast. Our brain tends to work that way too it seems... So if you enter Christmas, and go from C to next position, start right at the c