When I was editing my .json file in OSC Server Editor (not browser editor), I noticed that ctrl+click doesn’t open the drop-down menu. But, if I right-clicked by pressing with two fingers on the trackpad (physically clicking) it would right-click alright. It would also right-click if clicked with the right button of a regular USB mouse (Microsoft Wireless Mouse 1000 - my mouse).
I hope you don’t mind me complaining this much. I just like perfect things
I didn’t know ctrl+click was supposed act as a right click on os x, I’ll check this out.
While I was making a numeric keypad for my MAC (screenshot below), I noticed two more things regarding OSC Browser Editor:
- The editor is much more responsive in a Browser (Google Chrome - Version 79.0.3945.79 (Official Build) (64-bit));
- Ctrl+click still doesn’t work (even here).
My creation of today :
The editor is much more responsive in a Browser
That's a good news, it means the software is not getting slower as it evolves (the built-in client runs on an older version and has not been updated yet for various reasons).
Ctrl+click still doesn’t work
I'm not working on this 24/24 you know
No problem! Actually, I didn't phrase that right. I meant to say that ctrl+click doesn't work at all, no matter where you edited the .json file. Initially, I thought that only the OSC Server Editor has this problem (the lagginess made me think that OSC Server Editor surely must be the problem).
So that is what it's called: a built-in client . In fact, you're right. Because the other window is the server.
I found another problem.
As you can see in the image pasted above, I have two MIDI sessions: SessionKiano and SKiano-A.
When I have two widgets having the same address (/control [1,1] ), but different targets (MIDI devices/sessions), one is affecting the other one's state (just visually).
For instance, here, the MOD WHEEL's value gets to 127 when I press the toggle button labeled "CLICK". What's fortunate is that in my Audio Editing Software the Mod Wheel value doesn't change. It would change only if I moved directly the position of the fader (dragging it downwards or upwards).
This happens because o-s-c doesn’t make any distinction between identical messages from different origins; this usually makes sense in the OSC world where the “connection” concept is not exclusive as in MIDI. This could be improved.
On a side note, it would be nice to avoid using private message to discuss general usage questions that other users might be interested into. [edit: topic made public]
Thanks for pointing that out.
I posted seconds ago my initial message (from this conversation) in the section named "Installation & Configuration/Mac Os X", so that we can make this conversation public. You'll need to copy&paste the replies, one by one (but waiting, so that I also copy&paste my replies). If you don't want this, tell me, so that I can delete the post.
It's so interesting!
Please tell me if you need me to do any test. It's the least I can do (to show my appreciation).
With your permission, the topic is now public.
1 Like