ixox / preenfm2 Goto Github PK

Hi

I just finished building my Preenfm (PCB R6). I didn't know the USB key was required to work, so I just grabbed the first (and only) one I had in my drawer. It seems to work if I connect it after powering on the unit. But if I turn the Preenfm off and plug it back, sometimes the USB key is not detected and I get the message "Insert Usb Key". If I disconnect it and reconnect it, it is detected and the unit runs fine.

I'm powering it from the USB port. My guess is that the powering sequence of the unit is not happening such my USB key is ready or working by the time the Preenfm reads it. I was wondering if you have seen a similar problem.

I'm going to try to find other USB Key and check it.

in which IDE was the project created?

I've tried to sign up for the forums at https://ixox.fr/forum/index.php but I never get the verification email.

Hey,
I would like to add a midi functionality to the already existing preset randomizer:
CC message that would trigger the randomizer,
CC controls for the amount of randomization (for the ones available in the menu)
CC midi out for the values of params randomized
Please let me know if it's something of interest to you. I have a working prototype for these features in my fork locally.

hello. I was recently jamming to an arpeggio on inst1 and looking for a suiting sound for inst2, but when I loaded or even just selected a sound on inst2 inst1 would stop playing. is there any way around this? tried to find it in the code, but got lost. is it to do with propagateNoteOff?

Hi Xavier, thanks for this awesome project.

I just received the R6.4 PCB and wanted to take a look at the hardware files it. Unfortunately I was not able to find them in the GitHub repository. Are they in this repository? If not, are you planning to open source them?

looks like an awesome project (found it via http://audiocookbook.org/the-most-powerful-tiny-fm-synth-preenfm2/).

however, there is an issue. this repo contains the sourcecode, but what is missing is

• user manual (now separate at http://ixox.fr/preenfm2/manual/, but in fact intimately linked to the firmware!!! imagine you add a feature to the firmware... you would also have to add changes to the manual! and in an ideal world, all those changes are done on a branch...)
• PCB (manual, diagrams, ..., now at https://docs.google.com/spreadsheets/d/1Xt8gQqbJvMSSZ3lOPazCrE3Qu6qT4qbJweNDEm-yr78/edit#gid=0, and http://ixox.fr/preenfm2/build-it/thebuild/, rather linked to the firmware, no? just imagine you replace a encoder knob with more capabilities - it is likely the software would have to be updated too!)
• build manual (now at http://ixox.fr/preenfm2/build-it/, not so linked with the sourcecode, but linked to the PCB, right? and think of the knob that changed... this must also be mentioned in the build manual, right? and I just discover the P3 change, that will have to be documented somewhere, right!)

and maybe also

• alternative banks (http://ixox.fr/preenfm2/download/)
• case design files (with branches containing variants, such as the Eurorack one for example )
• links to interesting sites, such as https://www.youtube.com/watch?v=ZzsBu9vx98Q (which you should put in a playlist, so you can collect all related videos and link to it!)
• FAQ (presently at http://ixox.fr/forum/index.php?topic=63377.0, could easily be a Markdown file that can - again - be shared and updated by everyone!)
• the editor!

and maybe also the compiled artefacts (that are now on http://ixox.fr/preenfm2/download/)! this is undoubtedly open for discussion, as derived artefacts don't really belong in a repo for various reasons; but while you're at concentrating everything, and because the binaries are not that big, why not version them too? then you don't need to update the preenFM2 site or use Dropbox (gah!) any more. (and BTW - there is only one firmware binary, called pfm2 or even pfm, no need to add version numbers!).

and it doesn't matter that soft- and hardware might be designed by several people, the end result is one object that has a history, revisions, of various artefacts that evolve together! those different people should clone the repo and contribute as necessary.

also, by versioning everything, anyone trying to track updates only needs to perform a pull, and presto! (s)he can immediately see everything that has changed since whenever (s)he last made a pull, without having to search on http://ixox.fr/preenfm2/ to find out what changed (and probably miss things): manuals, firmware, ...

now imagine you want to make version 3... new PCB, new firmware, maybe a slightly different case.... you likely won't start from scratch, but tweak a version 2 system (maybe a lot, yet...), right? maybe versions will share code? imagine that someone finds a bug in a model 3, and that bug also appears in model 2, and the correction is almost the same in all models? you will have to juggle with branches, but all information is centralised in one repo. if those were in different repos, owners of different models might not be aware of issues that might be common to all models...
just by looking at your model PreenFM1, I can see version 2 is an evolution (even if much changed), so it belongs in the same project! and a new project would start off as a branch... because your version 2 might continue to evolve long after you've given up on it, think of the owners of a v2 that still want to contribute with forked code... imagine they find things that could also apply to newer versions...

here is another example that everything should live in one repo: http://ixox.fr/forum/index.php?topic=69166.msg71614#msg71614

edit added: meanwhile I discover that you are a SW engineer, so I don't need to explain in so much details...

hi,Xavier. i want build r6 version preenfm2
can you share pcb files for r6 version ?

If the PreenFM2 is set to send CC, and any performance parameter is changed, it doesn't send CC.

This seems to be an oversight in MidiDecoder::newParamValue().

The LFO modulation works on every MIX or PAN except for slot number 4.

I'm using version 2.11 but the same happened on version 2.08