You must register to have access to the complete forum.

Author Topic: Nemesis feature requests  (Read 20042 times)

Markus Krause

  • Tone2.com audiosoftware
  • Administrator
  • Hero Member
  • *****
  • Posts: 3123
    • Tone2.com audiosoftware
Nemesis feature requests
« on: December 10, 2013, 09:18:27 AM »
You can request features for Nemesis withing this thread.

We read and discuss every single request. Some requests will be included in future updates. Please note that there many different people with many different needs and there are technical restrictions.

sagantech

  • Jr. Member
  • **
  • Posts: 90
    • Sagan Technology
    • Email
Re: Nemesis feature requests
« Reply #1 on: January 14, 2014, 08:18:48 PM »
I find nemesis to be a great synth. Very easy to get good sounds out of it. My one gripe is the focus stealing. Imagine if every window jumped to the front when the mouse simply passed over it? Can you please implement an option for either turning it off or automatically turn it off, if the window the UI is in is not floating?

      long style = GetWindowLong(hw, GWL_STYLE);   
      floating = (style & WS_POPUP)

Markus Krause

  • Tone2.com audiosoftware
  • Administrator
  • Hero Member
  • *****
  • Posts: 3123
    • Tone2.com audiosoftware
Re: Nemesis feature requests
« Reply #2 on: January 15, 2014, 02:13:08 PM »
Hi Jeremy,

I sent you a PM with the latest version. In this version focus is only stolen if a the user clicks on a knob within the GUI. Make sure that you're using this one.

Make also sure that there is no file called 'NemesisMouse.cfg' within the plugin directory, since this forces an aggressive focus on the plugin.

Thanks for your great testing and the valueable tech info that you always provide.

Please note that having focus is essantial to make the mousewheel work within the plugin. Sadly microsoft messed up the mouswheel support years ago and did not fix it so far. So all we can do as developers is compromises and dirty tricks.
I will examine your suggestion with the floating window. We will do some additional testing to enhance compatibility with the 'Metro' host. Please note that our experience has shown that hosts behave very differently with focus. If we apply changes it's risky that we break compatibility in other hosts while the situation in Metro would improve.

All The Best,
Markus
« Last Edit: January 15, 2014, 02:16:25 PM by Markus Krause »

sagantech

  • Jr. Member
  • **
  • Posts: 90
    • Sagan Technology
    • Email
Re: Nemesis feature requests
« Reply #3 on: January 15, 2014, 09:15:13 PM »
Hello Markus,

Thank you for implementing my suggestion so quickly and the kind words. Much appreciated.

As I mentioned in another thread, I totally agree that mousewheel focus should be assigned to the hovering window and not the keyboard focused window and in this case Apple does it right and Microsoft does it wrong. However I should note that Microsoft seems to be moving toward agreement to this decision as well... as seen in Visual Studio 2012.

As for my suggestion, and although I haven't tried it, stealing the focus may be good if it is done only within the floating window layer as those windows are expected to be on top.

Jeremy

sagantech

  • Jr. Member
  • **
  • Posts: 90
    • Sagan Technology
    • Email
Re: Nemesis feature requests
« Reply #4 on: January 15, 2014, 10:51:05 PM »
Please note that having focus is essantial to make the mousewheel work within the plugin.

I am a little confused here. I tried your suggestion above and it works. And as you say mousewheel support does not. I am a bit confused why this would be. Do you not receive 'WM_MOUSEWHEEL' messages in your message loop when nemesis has focus?

Markus Krause

  • Tone2.com audiosoftware
  • Administrator
  • Hero Member
  • *****
  • Posts: 3123
    • Tone2.com audiosoftware
Re: Nemesis feature requests
« Reply #5 on: January 20, 2014, 04:30:00 PM »
Is has been a log time ago till i worked on this, but If i remember right, the mousewheel message is only passed, if the window has focus. The other WM messages like mouseclick are always passed correctly. It seems to be some kind of lowleved oddity in windows.
As you said. Apple does it right. At least this time.  :D

sagantech

  • Jr. Member
  • **
  • Posts: 90
    • Sagan Technology
    • Email
Re: Nemesis feature requests
« Reply #6 on: January 20, 2014, 08:05:31 PM »
he mousewheel message is only passed, if the window has focus.

Right. So why does Nemesis not work with the mousewheel messages it receives when it has focus and there is no mouse configure file?

Markus Krause

  • Tone2.com audiosoftware
  • Administrator
  • Hero Member
  • *****
  • Posts: 3123
    • Tone2.com audiosoftware
Re: Nemesis feature requests
« Reply #7 on: January 22, 2014, 04:34:44 PM »
There is a mouse configuration file. To force an aggressive mouse focus make sure that a file called 'NemesisMouse.cfg' is contained within the plugin directory.
Please note that mousewheel behaves slightly different with the latest version called (Nemesis_ilox_fix.zip). I did make focus less aggressive by default, since there was a host that made trouble. However i forgot which one it was.
All i can say is that we have received no compains about the mousewheel behaviour from our customers. This shows that it works for the people or that they don't use the mousewheel a lot.

cambartram

  • Newbie
  • *
  • Posts: 2
Re: Nemesis feature requests
« Reply #8 on: March 04, 2014, 04:43:42 PM »
Hello.  As a very new user of Nemesis and forum member I have a couple of quick suggestions:
  -enable a double-click on knobs to return to a null setting (e.g. bi-polar knobs  would go to vertical)
  -enable a double click on Mod sliders to snap back to null exactly
  -add an general UnDo/ReDo function (e.g. would allow for return to a previous waveform(s) after edit).

Cameron

Markus Krause

  • Tone2.com audiosoftware
  • Administrator
  • Hero Member
  • *****
  • Posts: 3123
    • Tone2.com audiosoftware
Re: Nemesis feature requests
« Reply #9 on: March 05, 2014, 10:01:38 AM »
Hello Cameron,

this is already supported:

Strg/ctrl + left mouse button: reset knob/control to default
shift + left mouse button: finetune knob/control

cambartram

  • Newbie
  • *
  • Posts: 2
Re: Nemesis feature requests
« Reply #10 on: March 05, 2014, 02:29:34 PM »
Thanks Markus for the knob control info.  Is the undo/redo function something that you would consider in the future?  Great synth!  Cameron.

Markus Krause

  • Tone2.com audiosoftware
  • Administrator
  • Hero Member
  • *****
  • Posts: 3123
    • Tone2.com audiosoftware
Re: Nemesis feature requests
« Reply #11 on: March 06, 2014, 08:33:59 AM »
You're welcome.

Undo/redo could be a usefull addition. We'll check out if it's possible from the technical side.

exmatproton

  • Full Member
  • ***
  • Posts: 145
  • Ae
    • exm BC
    • Email
Re: Nemesis feature requests
« Reply #12 on: May 15, 2014, 11:02:38 PM »
The only 2 things i could ask for, a third LFO and a third envelope section.
« Last Edit: May 16, 2014, 12:36:27 AM by exmatproton »
Icarus_Gladiator2/3_RayBlaster2_Nemesis_Saurus2_Electra2(x)_BiFilter2_Filterbank3_Warmverb

-exm-

Markus Krause

  • Tone2.com audiosoftware
  • Administrator
  • Hero Member
  • *****
  • Posts: 3123
    • Tone2.com audiosoftware
Re: Nemesis feature requests
« Reply #13 on: May 16, 2014, 10:08:07 AM »
Here is a hint for sound design:

In the matrix there are additional Envelopes and LFOs availabe:

- As modulation source select "Decay" for simple Decay envelopes
- Select "Keypressed" for a simple hold envelope
- Select "Sine" as additional sine LFO
- Select "WhiteNoise" and "PinkNoise" for noise modulation

exmatproton

  • Full Member
  • ***
  • Posts: 145
  • Ae
    • exm BC
    • Email
Re: Nemesis feature requests
« Reply #14 on: May 16, 2014, 10:50:51 AM »
Here is a hint for sound design:

In the matrix there are additional Envelopes and LFOs availabe:

- As modulation source select "Decay" for simple Decay envelopes
- Select "Keypressed" for a simple hold envelope
- Select "Sine" as additional sine LFO
- Select "WhiteNoise" and "PinkNoise" for noise modulation

True. And i am using those as well.

A really missed a third LFO when i was trying to:

LFO1-->LFO2speed, LFO2-->LFO3speed, LFO3-->LFO1speed

LFO1: SINE
LFO2: Random "curved"
LFO3: SAW

Where LFO1-->FM1, LFO2-->FM2 and LFO3-->Filter C1

This could be done with an additional LFO section, not with the fixed SINE's. Also, the white and pink noise could be used, but those are not controllable "speed-wise". Another thing that should do the trick; an envelope with looping ability (time based)...

Maybe i am asking too much. Not sure  :-[
Icarus_Gladiator2/3_RayBlaster2_Nemesis_Saurus2_Electra2(x)_BiFilter2_Filterbank3_Warmverb

-exm-