Insert mode selection problem and more.. windows 10 about orca HOT 28 CLOSED

Cannot reproduce on OSX.

from orca.

windows 10

from orca.

ill make a video for you if you like

from orca.

@nobodycarestrue sent me a video, I can see it on other people's computers.
I'll boot on linux and see if I get this problem too :)

from orca.

Oh you're using the build from itch and not the /master!
Okay, I've pushed a build to itch that should fix this issue 👍
Let me know if this problem is gone after updating from the Itch Client.

from orca.

i was using the master that was available from your site ..
latest master

from orca.

available from my site.. I'm not sure I understand.

In any case, is either the github master, or the itchio build still giving you this issue?

from orca.

https://hundredrabbits.itch.io/orca/purchase?popup=1

from orca.

Okay that's the itch builds, and not the /master branch of this repo.
So you're saying that the builds are still giving you this issue.

Gotcha :) I'll investigate this further.

**Also, if you download Orca via the itchio client(it's a bit like Steam) it will automatically download the patch differences. So you don't have to re-download the full build each time there is an update.

from orca.

yeh i downloaded it via the latest available from that link above .. i didnt login to any client to do so .. not really wanting to make any logins if possible .. i just want to download the latest version as released.. of the master.. and of course there is no built exe of this available from the github .. so the only place i can get it is that link .. otherwise i could keep existing folder and manually replace cores and resources..

from orca.

no exe is available from the github .. nd hence no BUILT version is available to users other than the link from the site https://hundredrabbits.itch.io/orca/purchase which is where i got this version for windows..
which i can only assume is updated from the nightly master build..

Several issues exist.. .. in this version.. where orca does not behave as expected..
https://www.dropbox.com/s/iz1vogmczo17ebq/orca%20problems_Trim.mp4?dl=0

1. Shown in the video .. is movement of selection .. using ONLY Alt Up / Down arrows...
   text moves diagonally.. unexpectedly ..
2. Midi output device is NOT activated ALL the time when selected..
3. Slow down on selection of text and cursor move.. still present..

from orca.

Also incidentally as far as i can tell, and i have tried it .. running:..

cd Orca/desktop/
npm install
npm start

does NOT create an executable file..
it does allow a person to run orca from the shell tho ..
but they will have to perform this npm build every time they want to run orca that way...
It is not as a user would expect a prebuilt *exe.. for orca.. which can just be run .. easily

from orca.

Let's have a look, so, in the video, I see that drag glitch in insert mode, that looks like an old build since the bottom left position color does not highlight, this was fixed here, so I'm guessing this might be an older build? I'm not sure why you ended up with this build, I have a feeling that Itch might have had an issue with their cache or something.

So I'm curious, if you launch orca via the terminal using npm start, do you have the drag issue in insert mode?

from orca.

no running "latest" git of orca does NOT replicate the same issue with regard to the Alt move of text..
however the other issues mentioned here do remain

it takes two selections .. to initiate a change of the midi input .. meaning i had to select it twice for it to change

from orca.

i also noticed the lack of the control + space in order to select existing midi outputs..

from orca.

Ah! Amazing :) Thank you so much for your patience to help me debug this cursor thing!

from orca.

i dunno whats up with the Itch repo of "builds" not updating to the latest .. i cant know how that works or why .. but i do know many people will be getting orca from there.. and those who run windows will be encountering these problems i mentioned above ..

from orca.

I'm curious, this is not related to the cursor issue, but in 2), the midi selection bug. Does it give you any warning or error in the console?

from orca.

I'll double check with itch to make sure that the cache has been cleared 👍

from orca.

yeh it does..
Midi Input Device: UC Midi Port 1
C:\Users\Adam Raisbe…core\io\midi.js:142 Midi Output Device: loopMIDI Port
C:\Users\Adam Raisbe…core\io\midi.js:142 Midi Output Device: UC Midi Port 1
C:\Users\Adam Raisbe…core\io\midi.js:153 Midi Input Device: loopMIDI Port


​
but the thing is its just not updating the selection either visually or functionally.. untill after the second press.. even tho it shows in the console that it has..

Also and maybe this is by your desired updated design,, there is no longer an indication at the bottom of the screen in the "commander" section.. where one can see which midi device is active.. as it used to be the case for both midi in and out .. there..

from orca.

Dang, I was hoping for a big red error or something.
I'm not sure why this is messing up, I'll try to poke around at this.

from orca.

also another STRANGE thing i just noticed..
I just changed the tempo in my DAW.. with of course no indication other than the set bpm in orca to tell me that the DAW and ORCA were currently connected..

and i noticed that it slides the tempo down? .. incidentally i went from a DAW tempo of 110 to 20. orca is now at 60 or so by the sounds of it .. definitely not 20

so yeh its clearly updating the tempo via refresh amounts rather than instantly ..
again this might be desired and by design .. but i note it being singificantly different from the functionalty of tempo control before..

from orca.

the orca bpm caps down at 60, and up at 300.

from orca.

yeah there's an issue with the bpm at the moment.
It's a bit tricky to fix, but it's a top of my list.

from orca.

maybe this helps ?

Midi Input Device: UC Midi Port 1
C:\Users\Adam Raisbe…core\io\midi.js:142 Midi Output Device: loopMIDI Port
C:\Users\Adam Raisbe…core\io\midi.js:142 Midi Output Device: UC Midi Port 1
C:\Users\Adam Raisbe…core\io\midi.js:153 Midi Input Device: loopMIDI Port
C:\Users\Adam Raisbe…scripts\clock.js:48 Clock Play
C:\Users\Adam Raisbe…core\io\midi.js:142 Midi Output Device: loopMIDI Port

​

from orca.

these looks good, if it was red, then it would indicate that orca is having trouble understanding a command. It's hard for me to test this one, because I only have 2 midi outputs to test, I'm trying to see if I can get 2-3 extra virtual instruments so I have more to choose from. This issue doesn't seem to happen with just 2 instruments.

from orca.

no they do just seem like warnings or logs of whats going on .. there isnt any specific errors i can find in any of the console logs ..

from orca.

Clock Play
C:\Users\Adam Raisbe…scripts\clock.js:55 Clock Stop
C:\Users\Adam Raisbe…core\io\midi.js:153 Midi Input Device: UC Midi Port 1
C:\Users\Adam Raisbe…scripts\clock.js:48 Clock Play
C:\Users\Adam Raisbe…scripts\clock.js:55 Clock Stop
C:\Users\Adam Raisbe…core\io\midi.js:142 Midi Output Device: UC Midi Port 1
C:\Users\Adam Raisbe…scripts\clock.js:48 Clock Play
C:\Users\Adam Raisbe…scripts\clock.js:55 Clock Stop
C:\Users\Adam Raisbe…core\io\midi.js:153 Midi Input Device: loopMIDI Port
C:\Users\Adam Raisbe…scripts\clock.js:48 Clock Play
C:\Users\Adam Raisbe…scripts\clock.js:55 Clock Stop
C:\Users\Adam Raisbe…scripts\clock.js:48 Clock Play
C:\Users\Adam Raisbe…scripts\clock.js:55 Clock Stop
C:\Users\Adam Raisbe…core\io\midi.js:142 Midi Output Device: loopMIDI Port
C:\Users\Adam Raisbe…scripts\clock.js:48 Clock Play
C:\Users\Adam Raisbe…scripts\clock.js:55 Clock Stop

it only played after the second selection here..

from orca.