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 ... 83 84 [85] 86 87 ... 149
1261
preenfm2 and preenfm3 / Re: OS 2.03: behaviour NOT1/2 ==> IM*
« on: September 04, 2016, 10:01:56 PM »
OK got it.
What is done is  :
Code: [Select]
IM = FIX IM + matrix value
if IM<0 then IM = 0
IM = IM + velocity sensitive IMs.
It's done in different part of the code which is why it was not obvious.

The test is not at the right place and that prevents the Matrix value from diminishing correctly the velocity IM.
I'll try to fix that.

Thanks a lot for the report  :)

Xavier

1262
preenfm2 and preenfm3 / Re: OS 2.03: behaviour NOT1/2 ==> IM*
« on: September 04, 2016, 09:36:59 PM »
Just tried and i agree there is something strange...
I'm trying to indentify the problem.


1264
preenfm2 and preenfm3 / Re: I want one !!
« on: September 03, 2016, 11:15:45 PM »

J'espère que tout sera pret pour le WE prochain. Sinon WE d'après.
Il y aura des Kits sans boitier ni écran... mais pas juste sans boitier.

Xavier

1265
preenfm2 and preenfm3 / Re: I want one !!
« on: September 03, 2016, 11:09:35 PM »
Salut Thierry,

PCB and MCU boards are available in the Shop :
http://ixox.fr/shop/

Full kits will hopefully be available in 7 days.
I'll also have a dozen of kits without box and display.

Xavier

1266
preenfm2 and preenfm3 / Re: OS 2.03: behaviour NOT1/2 ==> IM*
« on: September 03, 2016, 01:25:55 PM »
It seems that setting up "NOT1/2 ==> IM*" in the matrix only adds to all fixed modulation indexes: When setting all fixed IMs to 0.00, and setting the velocity sensitive IMs different from 0.00, the aforementioned matrix entry has no effect at all.
Speaking in simple math, it seems to be implemented similar to this: (fixed IMs * matrix setting) + velocity sensitive IMs
I'd like to see it implemented the following way: (fixed IMs + velocity sensitive IMs) * matrix setting
Does this make sense at all?

Thanks for the feedback, that's interesting.

The formula is : IM = FIX IM + velocity sensitive IMs + matrix value
So it's weird you don't hear any effect when FixIM = 0.
What you hear maybe is that IM<0 in this case it's reset to 0. So it all sounds the same after a certain note number.

1267
preenfm2 and preenfm3 / 2.05B5 available (September 5th)
« on: August 30, 2016, 10:32:52 PM »
See attachment bellow.
Still beta because i didn't test it a lot and there are several important changes, if you test the new features, don't hesitate to let me know if it works as expected for you.

. New matrix target "Dec*" : Decay all
You'll find it between Att* and Rel*.
http://ixox.fr/forum/index.php?topic=69169.msg71645#msg71645

. New matrix target : "o*Fh" (h for 'harmonic' / Located after "o*Fr").
It's harmonic Freqency, required for accurate Pitch Bend.
It's been discussed here : http://ixox.fr/forum/index.php?topic=69162.0
The final solution is a new matrix target that shifts ALL oscillator. The matrix multipler is exactly the number of shifted tone UP and DOWN.

. The test note (left buttons while browsing presets) is not anymore muted when you change patch or trigger a new random preset. So use and abuse.

. Low frequency stuck note finaly fixed
http://ixox.fr/forum/index.php?topic=69170.0

. Last minute matrix source re-order
http://ixox.fr/forum/index.php?topic=69182.0

. Fix a problem that prevent the matrix target IM* from diminishing the velocity IMs.
http://ixox.fr/forum/index.php?topic=69184.0

Thanks everyone for all suggestions and discussions that made this happen,

Xavier

[attachment deleted by admin]

1268
You're right, i'll change that.  :)

1269
I changed the name of your firwmare so that there is no confusion with current beta.

If you change the number of steps, there's a chance the "midi sync" ratio freq does not work anymore.

1270

100Hz is not a problem, it does not add any CPU overhead.
The LFO is updated every 32 samples. 100 Hz would make it updated 12 times per period.

A quick hack would be to modify LfoOsc.cpp line 167.
currentFreq = lfo->freq + this->matrix->getDestination(destination);

Change it to :
currentFreq = lfo->freq * 4.0f + this->matrix->getDestination(destination);
And you'll have the LFO frequencies 4 times the number you see on your display.




1271
preenfm2 and preenfm3 / Re: PC/Mac Editor version 2.00
« on: August 30, 2016, 12:01:58 AM »
PluginParameters is a git submodule.
It's describe in the .gitmodule file, so it's easy to download from the editor forlder.
I don't remember exactly the git command but i quickly found that :
http://stackoverflow.com/questions/8090761/pull-using-git-including-submodule

I also think you must have the steinberg VST headers even for Linux... but i'm not 100%  ;)

You can compile directly the host.

1272
preenfm2 and preenfm3 / Re: Preenfm2 gerber files
« on: August 29, 2016, 11:49:37 PM »
the hole green area is copper.is  it normal ?

Yes it's normal. This is the GND zone.
But it's not the latest version.
If you plan using a LCD display go ahead. If you plan using a yellow OLED, you should wait.
I'll upload the R5d version before the end of the week.

1273
preenfm2 and preenfm3 / Re: PC/Mac Editor version 2.00
« on: August 29, 2016, 10:05:59 PM »
i see now in another post, that you already compiled a linux version. i will try to compile the version from github...

Let me know how it goes.
You'll see the standalone version is more complicated thant what you expect.
It's because it's the pluggin version wrapped in a host and the pluggin version has to deal with the host automation, with the midi I/O and with the hardware. All that without locking the audio main thread.

Anyway, if you have any questions....  ;)

 

1274
I'd be happy to demonstrate.

I'd be happy to hear :)

i compiled a firmware with increades lfo speed, will try tomorrow if it works as expected and will then upload here...

Don't hesitate to share  :D

1275
I understand this, but why do I observe that the encoders move - but the values as well as the sound don't change as usual. The encoders require many more degrees of turning until a value changes ... if this makes any sense.

This happens under heavy load on all preenfm.
When the preenfm2 plays 8 voices of 6 op algo, there's not much CPU left for the display driver which refresh slower, and for the encoder driver which does not poll the encoder values fast enough.

The overclocked firmware has a slighty higher sample rate AND has a little more CPU left for display and encoder in heavy load situation.
If you don't use it aldready, give it a try.


Pages: 1 ... 83 84 [85] 86 87 ... 149