Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Xavier

Pages: 1 [2] 3 4 ... 78
PreenFM2 / Re: PC/Mac Editor version 2.00
« on: July 31, 2017, 11:46:19 AM »

Did you correctly assign the midi out/in in the options/midi settings menu ?

I know it's weird as it's midi only but you also have to select a sample rate supported by your audio hardware.

PreenFM2 / Re: midi channel for combo program change
« on: July 31, 2017, 11:39:38 AM »
Nice to see people digging into the code  :)

I think you're lookging for this :
You could add a MIDI_CHANNEL_ALL that would listen to a specific midi channel a spread the commands to the 4 instruments.

The UI structures is defined here :

Defaults values are here :

And the midi command to instruments is here :



From what i understand with NRPN, the device chose for each of its parameter whether CC38 is required.
Once you know for one parameter whether it must be sent (or not), you have to send it (or not).

The preenfm2 always expect CC38 to be sent. That's simple :)

I don't know what you send to CC 100 and 101, so it's difficult to guess why that makes your preenfm2 slow down.

Any patch are welcome, i don't guarantee i'll put it in the official firmware though ;)

PreenFM2 / Re: NRPN and MIDI documentation questions and issues
« on: July 25, 2017, 10:44:36 PM »
Quote from: feijai
I'm confused by this.  Each of the step sequencers has a gate, which is an available destination for modulation.  But there is also the "Gate" destination.  Where does this go?  How does it differ from the step sequencer gates?  Is it documented somewhere?
Also, what is O*Fh?  It also doesn't appear to be documented.

Both step sequencers has a gate. But the gate effect is a totally different gate.
It an internal effect in serial with the LH/BP... effect.
Try to play with it, you'll understand.

Docs needs to be updated for O*fh : explanation is currently here
New in firmware 2.05

Quote from: feijai
17. All clickable encoders are connected to the same digital in... So they cannot have different behaviour.
:-(  There were many opportunities there.  :-(

PCB/hardware limit.


As you noticed, the preenfm2 it not NRPN proof, sending wrong value can crash it.

7.8. I unlinked the order in the preenfm2 UI and the internal value. preenfm2 had many firmware upgrades which saw new parameters, some parameters needed a new internal value but had to be inserted in the existing list.

9. for freq >= 1.0 the increment/decrement is set to 0.1.

10. agreed.

11. The number of voice is supposed to be the number of voices saved with the preset. Or if the other instruments have voices that prevent this number to be set for the newly loaded preset.

12. Not sure i understand. Saving sysex dump all current instrument parameteres. Combo are the 4 instruments saved at the same time.

But if I send a properly nulled NRPN(+RPN) message, that is, one of the form: 99, 98, 6, 38, 101(127), 100(127)

Then the PreenFM2 cannot parse faster than about 1ms per message, and starts dropping MIDI bytes if I send faster than that.  :-( :-(  That's not good, it should never be dropping any MIDI bytes ever.  And it means I can't send a nulled message.

The preenfm2 expectes NRPN messages (not RPN).
It expects 99 and 98 to be sent.
Then :
. 6 AND 38
. or 96
. or 97
You can see the code here :

Don't hesitate to submit patch if you modify the code and think you improved the behaviour.



PreenFM2 / Re: NRPN and MIDI documentation questions and issues
« on: July 25, 2017, 03:27:18 PM »

10. I don't remember. Easiest way is to try and see.

11. Yes

12. Yes < 16

13. "_" looked clearer than 0 to me on the UI.

14. right... Note scaling was added later, let me know if you find something that can be added to the documentation.

15. OK  :) I'll leave Enveloppe ;)

17. All clickable encoders are connected to the same digital in... So they cannot have different behaviour.

18. In the preenfm2 release level only affects the end of the enveloppe.

19. Do they send any value ? You said Note scaling midi are not documented, maybe that's what is sent.
If you find the solution by looking at the code, please share...

20. Ouch... correct... never realized that before. Difficult to fix now without breaking preset compatibility.



PreenFM2 / Re: NRPN and MIDI documentation questions and issues
« on: July 24, 2017, 10:53:49 PM »

Again, i'm far from my preenfm2 so i write that from memory.

1. 14 voices max instead of 16 because of memory limit and CPU (each voice has its own LFO so 2 voices of 3 operators is heavier on the CPU than 1 voice of 6).

2. sin ^2 : sin*sin.
szer : sin on the first half of the period then zero.
spos : sin always positive.

There were a discussion in the past, showing that these are not the most well chosen shapes  ;)

Off appeared later in the preenfm history. For compatibility it's internal value is 7. For ease of use it's shows up in the first shape slot.

3. I have to double check that but I assume you can set upper value for user waveform.

4. The NRPN conversion is a generic. So most of the time it's 0.01 * NRPN value.
As it's converted into float there's no real max.

5. preenfm2 envelope has level and period for each of the ADSR point, so you can start by silence without problem.

6. Preenfm2 arpegiator is from mutable instrument open source code. So have a look at the manual :

7. Brth i the CC Breath midi input control change.
Seq are from the LFO sequencer.

8. yes DEC* is all decay.
Gate is the gate internal effect. It's an additional effect that is interesting to use with the 2 step sequencers.

9. Read 4 instead of 164. I'll fix that later.

To be continued....

PreenFM2 / Re: pfm2 2016 OLED svg won't download
« on: July 22, 2017, 09:29:50 PM »

Thanks for the update.  :)

PreenFM2 / Re: 2.07 update won't work
« on: July 18, 2017, 04:03:24 PM »
I'm away from my computer so support is limitted during summer.
All preenfm2 files must  be in a /pfm2 folder : firmwares and bank.
Scala files and dx7 bank must be each in a specific subfolder.


PreenFM2 / Re: RV1 10k trimmer- what's it for?
« on: July 13, 2017, 08:36:59 PM »
What PCB revision do you have ?
If R5d, check the OLED resistor is not empty.

Last firmware is 2.0.7 but that won't fix your problem :

PreenFM2 / Re: RV1 10k trimmer- what's it for?
« on: July 13, 2017, 04:43:46 PM »
Hi Tom,

RV1 is the contrast resistor for LCD display. Useless if you have a OLED display.

P1 and P3 are describe at the end of this FAQ  :

Thanks for the Maplin tip. Ebay is also good place to buy low profile pins header if you're patient :
Search for "Single Row Round Pin 2.54mm Pitch Spacing Header"
They're cheap if you buy many.


PreenFM2 / Re: Saving preset into empty Bank/Combo slot
« on: July 09, 2017, 10:02:48 AM »
Thanks for the reminder and for the original suggestion ;) Seems like i missed it.
It's part of the doc now.

PreenFM2 / Re: VST Editor manual or know how with Cubase?
« on: July 05, 2017, 10:07:45 PM »

Not sure how it works in Cubase.
It's not displayed in the list of compatible DAW so i don't even know whether it works.

VST midi out => preenfm2 hardware. As soon as it's plugged, any knob turned on the VST should propagate to the preenfm2 display.
preenfm2 midi NRPN out => VST : turn a preenfm2 knobs, should show up in the VST.

In adition to that, any move on the VST or the hardware should be recordable as a DAW automation.
Any VST Knobs automation should propagate to both the VST and the hardware when played.


PreenFM2 / Re: VST Editor manual or know how with Cubase?
« on: July 02, 2017, 11:23:30 AM »

No, there's no manual.
Configuration should be simple, make midi from Cubase go to the preenfm2 hardware, make midi out from the preenfm2 go to cubase.
Disable midi thru in preenfm2. Make the preenfm2 sends and receives NRPN.
Becarefull to midi loop.

I don't have Cubase so i cannot give more details.


Pages: 1 [2] 3 4 ... 78