Possible bug

Ive noticed that the 'pop-up' help menu boxes don't close very well after moving away from them(standalone version). If I go from one item to another and the boxes appear, my screen gets rather full of them. They start to close or fragment as I pass over the boxes themselves, but not the item it descibes. I notice this behavior and/or the inability to even read the help hints in pianoteq pro as well. In the vst3 version of both pianoteq and organteq, the popup hints are not visible, tho a transparent shaded box seems to open in the ui. Small issue, does not prevet me from using the products.

I noticed too some small bugs :
When he has to play the 4 quarter note chords with the MIDI player, he plays these notes as a half note, anyway, we hear the bug if you play this music : https://forum.modartt.com/uploads.php?file=uhjb.mid
When I start the software, it is a bit long to load, I think it can be corrected, it's the same when I change the temperament...
The French translation is not complete, hmm...
I hope we can play with the computer keyboard !

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.

Thanks for the tip.  I checked all of my settings... Sample Rate, Buffer Size, Polyphony, while following the CPU load.

No problems with any of these settings.  I can certainly PRODUCE an audio overload, by disabling multi-core support, but that effect sounds nothing like what I am referring to.  I will be posting further discussion in the "suggestions" thread.

Once a preset is loaded, if we change anything that is on the second line of buttons (diapason, temperament and so on) the preset is marked as modified but not for changes on the stops, combinations and coupling. I understand that a lot of trial goes on there that are not meant to be saved as preset but this is dangerous since we can save unwanted changes without knowing. Every possible modification to a preset should be flagged in my opinion, as it is in Pianoteq.

EDIT: Another thing that bothers me: If I save a preset containing many combinations and reload it later, it starts in the last combination I made but does not light the associate combination button so I don't know what's the initial state.

Mmmm, I've tried this and it seems to work correctly for me on MacOS. There may be a small delay at times though before all knobs are reset, not always. I find though that the hourglass that is supposed to indicate the delay sometimes does not appear and stops move later than expected (quite rare though, usually no hourglass means an instantaneous change). There is probably a lot of small situations where the part of the GUI that was inherited from Pianoteq is not quite in the same conditions (longer adjustments needed).

The live state, i.e. stops switches, couplers switches, pedals, ... is saved in the fxp files (presets). When rendering from the standalone version with Organteq MIDI files, the live state remains coherent. When rendering through a DAW, you have to check that the live state you are starting with is the good one.

That, combined with a long update, might look like a broken preset.

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

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)

I think I discovered a bug with the MIDI player... !

I have the impression that key couplings are not all perfectly synchronized...
And, I have the impression the MIDI player reads badly the notes that are repeated...

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.)

Note that Organteq has to initialize and reserve resources for about 1000 virtual pipes upon instantiation. Pianoteq on the other hand has 5 times less strings to initialize. Sometimes, things just need a bit more time

HI
Maybe I missed something

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)