BrainModular

In HH1, if I use the touch screen on a switch, I press it to switch it on, press it again to switch it off, i.e. a finger press acts like a mouse click.
In HH2, mouse clicks still work like this, but when I touch the switch, it pulses briefly to the green "on" colour but then straight back to the "off" colour.
It does this whether "trace gestures names" is selected or not from the global setup screen.
Is this something to do with a change to gesture handling ?
Simon.

Quickly tried here, and it looks like working as it is supposed to (ie., touch on touch off, same as HH1).

Not sure if this is relevant but, it works even when the "enable touchscreen" option is disabled. With only one difference though: when touch screen is enabled, the switch toggles as soon as you touch it; when touch screen is disabled, you need to touch and then remove your finger to toggle the switch.

Do you use a native touch screen came with the computer/monitor or a DIY addon?

Q

Hi.
Using a HP Pavilion touchscreen laptop. It works fine in HH1.
If "enable touchscreen" is off, sliders do not work.
In HH2 when I touch the switch it briefly flicks to ON then back to OFF. I can find no "momentary" settings switched on.
If I touch the switch with two fingers, it does toggle between ON and OFF, but does a strange flicker on the way.

It is a Synaptics ClickPad with various gesture settings, but since Usine has native touchscreen support, I would have thought it
would not be affected by those settings. And of course in HH1 it works fine.
Simon.

question....I don't know but enable touchscreen might be a restart required option to fully enable disable. Dont know but I think I ran into something once in HH1.

Simon,

So one difference in HH2 is the selector which places a white border around to show the selected item.
I could see a slight pulse...maybe what you are saying.
This I saw only when going back and forth between switches...and probably just the refresh because of the selector.
I am running at 5ms refresh, I saw a slight difference with slower refresh.... and honestly functionally there really isn't much difference in what I am seeing beyond
maybe a slight pickiness on the pulsing with the white border.
I am not having any issue here with the switches not displaying the right color.

Can you give more specific details of your setup or possibly upload a patch and I can see if I can verify with your patch?

-S

Screen recording of the problem:
http://www.sensomusic.com/forums/upload ... switch.avi

Hmmm....Yeah I am not running into this problem.

So I see you are using the x86....I have an appt soon, however I can download and see if there are any x86 differences.

I do not see this problem at all...I assume your patch you showed was just a button and a few faders too and no wiring?



-S

sephult wrote:question....I don't know but enable touchscreen might be a restart required option to fully enable disable. Dont know but I think I ran into something once in HH1.

-S

Yes a restart was needed. And again yes I noticed now that the sliders don't respond to touches properly if touchscreen is disabled.

Being that said, I wonder if color is the only problem in sm_jamieson's case and the switch is otherwise working properly . I mean is the switch sending correct ONs and OFFs (ie. 0's and 1's) except the wrong color? Or does it send an ON and an unwanted OFF afterwards?

And if it's not uninstalled can you turn back to HH1 and check if it is still working properly there? Maybe something else has changed out of the HH.

Just tried HH2 2.0.062 64 bit and it has the same problem.
Then tried HH1 and it works fine.
Some bad interaction between the touchscreen driver on my laptop and HH2 ?

That is very odd, I am sitting here trying to reproduce at all and no issue whatsoever.

So this does that on every switch with no wiring at all to it?

-S

sephult wrote:That is very odd, I am sitting here trying to reproduce at all and no issue whatsoever.

So this does that on every switch with no wiring at all to it?

-S

Yes.
I started from an empty workspace, added a rack and then put a switch in the empty patch.
I've just added another switch and they both do the same. No wiring to the switch at all.
Its not just the colours, since I have an on and off caption in the settings, and that would definitely show the state.

Simon.

I've connected the switch to a script parameter to trace every time the value changes.

When I touch the switch, the value changes state, but then changes back, i.e. from OFF, callback values 1 then 0. Or from ON, callback values 0 then 1. The switch back in state does not correspond to when the finger is removed - it does it all on its own.

If I press with two fingers, it changes state, but from OFF, callback values 1 then 0 then 1. Or from ON, callback values 0 then 1 then 0. This shows up as a flicker of the switch colour and caption.

Very strange.
Simon.

Does almost sound like a driver conflict like a single press is getting two presses from the touch screen.
What is your laptop with touchscreen model #

Maybe someone around here has something similar. I am using a Samsung AIO7 for my touch input, just using windows drivers via USB over Ethernet to a second computer.

-S

Maybe check your manufacturer drivers, and possibly if you can uninstall the manufacturer drivers if they are present and try to use default Windows drivers.

At least if you were using same driver set as I we could eliminate that possibility.

-S

sm_jamieson wrote:Just tried HH2 2.0.062 64 bit and it has the same problem.
Then tried HH1 and it works fine.
Some bad interaction between the touchscreen driver on my laptop and HH2 ?

What about the other elements, like checkboxes in settings panel etc.? I mean the ones which normally toggles upon a single touch.

good one question, it would give a little more information to try similar controls.
This would be at least more elimination.

-S

Faders work fine.
A button only produces a single trigger when pressed.
The switch only produces a single "mouse down" output followed by the double state change as described above.
I also get the trace message "W004 edition disabled on this control" on a switch or button when I double-click it (2 fast clicks or 2 fast touches), if that is relevent.

Windows 8 driver:
HID-compliant touch screen
Driver Provider: Microsoft
Driver Date: 21/06/2006
Driver version: 6.3.9600.17041

If you click on Driver Details, it says "No driver files are required or have been loaded for this device."

Thanks,
Simon.

Okay sm_jamieson,

I have the same drivers. Using an Ilitek touch screen.
I've seen in earlier builds if you click stuff too fast before they respond that the w004 pops up.
So probably indicates that for some reason you are getting double input.

Are you importing your previous configuration from HH1?
I would suggest possibly as well wiping your default-settings.ini in your config folder.
Restart Usine as it was new, and then recreate your setup and see if the touch-screen reacts the same way.
Maybe there is a corruption/compatibility between your previous HH1 and HH2 settings. Maybe a bug?


Have you tried to recalibrate your touch screen as well?
Swipe the charm bar and go to search and...do a search for touch screen.Calibrate the screen for pen or touch input.
I know this probably is not it, but couldn't hurt to eliminate as well.


-S

I only get the W004 message when I do two fast clicks to produce an equivalent of a mouse double-click. When I double-click the mouse, I get the same message.
I do not get the message when doing a single touch - so a single touch is not giving double input.
Also, I did not import anything from HH1, created from scratch on HH2.

If I create an simple patch with just a switch in HH1, it works fine. Something is different between HH1 and HH2 with the processing of touchscreen input.

Thanks,
Simon.

Question wrote:Hmm interesting. Looks like your swithces are edit disabled by default : )

This might be something related to a corrupt "Default-settings.ini" file (located in ...Usine/Config folder) which governs some default mouse etc behaviour along with other things. And default mouse mode related to that object might have been changed into something else in there.

I might suggest temporarily removing that file elsewhere or just renaming it to see if this solves the problem. Usine will create a fresh one when started.

I will check this later, but it does not sound like something that would affect the touchscreen but not the mouse ?

The other thing I was going to try was copying the switch module from HH1 to see if it was a problem just with that module, but all I find in the Modules directories are 1K sized "plg" files which look like they might just be pointers into a DLL somewhere. There does not seem to be an individual "switch" module file to copy.

The other thing I can try is switching off any gestures in the touchscreen settings (two-finger scroll etc.) to see if that has any effect.

But it is starting to sound like a bug report. The developers might have some type of debug version or trace options in HH2 that could be used to find out what is happening in my particular situation.

I will certainly buy a license for HH2, but I need this issue sorted out first !

Simon.

Well I cannot see any Windows parameters to alter, so nothing else to try really.
I will put in a support ticket and point to this thread if that is possible.
Simon.

I have raised a support ticket.
Simon.

The issue has been resolved in version 2.0.064
HH2 had been changed to have a shorter protection timer against multiple presses, which apparently always happen with touchscreens.
Thanks to Senso for the great support !
Simon.

Glad to hear your problem was fixed!