Because of compatibility between the two sets, the A/D converter for the expression is only used over a limited range, 0.32 to 0.91, rather than the initial setting 0 to 1. I filled in the actual A/D outputs in Organteq, but see that the expression pedal remains stuck at both ends as if 0 to 1 is still held, as it can be moved further with a mouse. Please help or solve.

Hi Alex,

Thank you for reporting. You can restrict the input range of the MIDI controller: in the MIDI mapping window, click on the controller and choose Enter custom range... in the Restict the value range of Controller # menu.

You have to provide the new range with an integer MIDI value (i.e. in the range [0, 127]). So in your case the new bounds would be 0.32*127 = 40 and 0.91*127 = 116.

Please contact support for further assistance.

Roman

Because of compatibility between the two sets, the A/D converter for the expression is only used over a limited range, 0.32 to 0.91, rather than the initial setting 0 to 1. I filled in the actual A/D outputs in Organteq, but see that the expression pedal remains stuck at both ends as if 0 to 1 is still held, as it can be moved further with a mouse. Please help or solve.

On my PC, I use 2 displays
Qhen I activate the full screen mode on the main display. all is ok

If I try the same operation with Organteq GUI on the second display
The right-click on the stops knobs does not work in full screen mode (but it works in normal mode)

Thanks, Modartt.

Loads in 7 seconds over here.

(Also Java or any drivers in your system in 99.9% of cases have nothing to do with plugin loading time.)

under 4 seconds for pianoteq to open on a blank reaper project, 11 seconds for organteq, blank reaper project.  3 sconds for Kontakt and 6 seconds for 7gb sample load. So I guess Organteq is almost on par with a 7gb sample based instrument. Maybe I'm just so damn eager it seems longer. Maybe a quad core 4.0ghz ssd system isnt what it used to be. Its just obvious when I open a project containing organteq, as the project hangs a bit and its the last to finish. Custom built win7 64 desktop (intel), fwiw.

(Also Java or any drivers in your system in 99.9% of cases have nothing to do with plugin loading time.)

I find I am limited to a bit over 160 voices when using Tutti, does it mean that the maximum 512 voices (on Tutti) is attainable only with over 12 cores (or less with a newer faster cpu than my 3.7 GHz Xeon E5)?

(That seems to be the case since Bruno (bm) reports in another thread 350 polyphony using an i9-9900k which has 8 cores if I'm not mistaken)

My system does fine with 512 polyphony.  Intel Core i7-6900K @ 3.2 GHz, 8 cores.

For some parameters changes, the pipes data have to be updated. That occurs when:

• launching the app the first time

• changing the sound card settings

• changing the global tuning options (diapason, temperament, global note-per-note tuning)

The internal computations of all the pipes (more than 2500) currently takes about 5 sec. on a regular laptop. During that time the engine still works, but the interface is somehow frozen. As long as the hourglass is shown, the internal update is still running. We are working on speeding that part up and on making the user experience smoother.

Note that when you get back to a previous tuning setting, the change is faster as internal computations are cached.

One question about optimization (and max polyphony): On my 2013 quad-core MacPro, Pianoteq uses mostly the first two cores even with complex input and I never get audio overload. I notice Organteq uses all four cores quite evenly, something I find normal given the parallel nature of organ pipes. Does that mean that the more core the better for Organteq, contrary to Pianoteq where it does not really matter?

I find I am limited to a bit over 160 voices when using Tutti, does it mean that the maximum 512 voices (on Tutti) is attainable only with over 12 cores (or less with a newer faster cpu than my 3.7 GHz Xeon E5)?

(That seems to be the case since Bruno (bm) reports in another thread 350 polyphony using an i9-9900k which has 8 cores if I'm not mistaken)

In my configuration (Windows 10), the trial version has a very strange behaviour.
1) The application doesn’t recognise the clicks of my mouse. Only the touch screen allows an action.
2) A right-click on a keyboard doesn’t allow the auto-detect function. It works as a left-click and the note playing during this action stays pressed without any possibility to stop it.
3) Touching a pop-up menu doesn’t work, but when I release my finger the menu appears very briefly.
I’ve uninstalled and reinstalled Organteq 3 times, without any success.

Hi Ludu,
Thanks for reporting. Can you send a support request and mention your config including your screen settings?

In my configuration (Windows 10), the trial version has a very strange behaviour.
1) The application doesn’t recognise the clicks of my mouse. Only the touch screen allows an action.
2) A right-click on a keyboard doesn’t allow the auto-detect function. It works as a left-click and the note playing during this action stays pressed without any possibility to stop it.
3) Touching a pop-up menu doesn’t work, but when I release my finger the menu appears very briefly.
I’ve uninstalled and reinstalled Organteq 3 times, without any success.

Does anyone understand why I can’t run the trial version normally?