|
|
|
02-11-2019, 02:53 PM
|
#321
|
Human being with feelings
Join Date: Jul 2009
Posts: 3,714
|
Quote:
Originally Posted by JamesPeters
I tried the compress script as well as the two warp scripts. They both crash Reaper. To reproduce, run the script and have it be active (don't commit the changes by clicking a mouse button); press ESC. Reaper crashes without warning. The system I'm using is in my sig. Thanks!
|
To which action is ESC assigned in your configuration?
|
|
|
02-11-2019, 03:06 PM
|
#322
|
Human being with feelings
Join Date: Aug 2011
Location: Near a big lake
Posts: 3,943
|
Quote:
Originally Posted by juliansader
To which action is ESC assigned in your configuration?
|
Default is "time selection : remove time selection and loop points". It doesn't do that in the MIDI editor however (it normally closes the MIDI editor window). I unassigned the ESC key and tried again. The crash still happens even if ESC isn't assigned to an action.
It's not a key I'd normally use in the MIDI editor but I was initially unsure how to commit the changes of the script. When learning new stuff, ESC is usually a relatively safe key to hit, so I just tried it. Instead of closing the MIDI editor window it "closed" Reaper instantly.
|
|
|
02-11-2019, 03:29 PM
|
#323
|
Human being with feelings
Join Date: Nov 2007
Location: Lucas, TX, USA (via Luleå, Sweden)
Posts: 2,008
|
Quote:
Originally Posted by JamesPeters
I was initially unsure how to commit the changes of the script. When learning new stuff, ESC is usually a relatively safe key to hit
|
Yes, I do that, too. Using ESC is kind of a default "I'm done with this window/tool -- please close it now" reflex for me.
I can confirm that it DOES NOT crash for me, and I DO have the ESC key assigned to an action in the MIDI editor (Reset all MIDI devices).
I wonder if maybe trying to close the MIDI editor window while the script was running is the culprit.
__________________
Best Regards, Ernie "lunker" Lundqvist
BDSM (Bad Dog Studio Musicians)
Windows 10 running on Z390 + i7-8700
|
|
|
02-11-2019, 04:09 PM
|
#324
|
Human being with feelings
Join Date: Aug 2011
Location: Near a big lake
Posts: 3,943
|
I read your post and then I realized ESC was bound to a "close window" action for the MIDI editor section of the action list (I'd only looked at the "section: main" before). So I removed that binding. Even after restarting Reaper, hitting ESC would still close the MIDI editor window. (And it would crash Reaper if those scripts were active.) I then removed the binding of the ESC key for all "sections" of the action list just in case. The MIDI editor would still close when hitting ESC, and that crash would still happen if the scripts were running when I did that.
So I assigned ESC to "reset all MIDI devices" in "section: MIDI editor" as you did (a good choice for that key, in my opinion). Now ESC no longer closes the MIDI editor window, and it no longer crashes Reaper if the scripts are running when I hit ESC in the MIDI editor.
|
|
|
02-12-2019, 11:03 AM
|
#325
|
Human being with feelings
Join Date: Jan 2010
Location: Kalispell
Posts: 14,745
|
@Julian, I updated my scripts today, including the js_ReaScriptAPI. When I tried to run the older script:
"Script: js_Draw linear or curved ramps in real time.lua"
I got a message that it was replaced by this script:
"Script: js_Mouse editing - Draw ramp.lua"
When I run the new script "Draw ramp" it's very erratic. What am I doing wrong.
|
|
|
02-12-2019, 11:19 AM
|
#326
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
There's definitely something not right. Let's see.
Are you by chance holding the hotkey, that you executed the script with?
|
|
|
02-12-2019, 12:06 PM
|
#327
|
Human being with feelings
Join Date: Nov 2007
Location: Lucas, TX, USA (via Luleå, Sweden)
Posts: 2,008
|
Just a guess -- are you perhaps left-clicking while you draw the ramp?
I'm not totally used to the new scripts yet, but I think left-clicking terminates all of these scripts. So depending on how you are triggering the script you might accidentally be stop/starting it over and over while you try to draw one ramp. (I guess kind of like what _stevie_ was suggesting)
__________________
Best Regards, Ernie "lunker" Lundqvist
BDSM (Bad Dog Studio Musicians)
Windows 10 running on Z390 + i7-8700
Last edited by lunker; 02-12-2019 at 12:48 PM.
|
|
|
02-12-2019, 12:42 PM
|
#328
|
Human being with feelings
Join Date: Jan 2010
Location: Kalispell
Posts: 14,745
|
Quote:
Originally Posted by _Stevie_
There's definitely something not right. Let's see.
Are you by chance holding the hotkey, that you executed the script with?
|
Thanks Stevie, and yes, I thought I had to, because if let go of the hotkey, the script would stop.
But going back and testing now, I see if I quickly let go of the hotkey, then I can draw the ramp and also use the mouse wheel
to fashion the curve. Also I see right click changes the vertical start position, great.
I'm going to like this script much better then the old one.
Also thanks lunker, yes I was also left clicking because I was trying to find some way to make it work better.
|
|
|
02-12-2019, 02:58 PM
|
#329
|
Human being with feelings
Join Date: Oct 2017
Location: Larisa, Greece
Posts: 3,797
|
Wow..Tremendous work,absolutely fantastic tools! Man I think you should be hired to work for Cockos on the development of Automation Items and the Midi editor.
Most of the "famous" Daws, if not all, would kill to have these features.
Thanks for making Reaper even more unique!
|
|
|
02-13-2019, 12:52 PM
|
#330
|
Human being with feelings
Join Date: Jul 2009
Posts: 3,714
|
Quote:
Originally Posted by JamesPeters
I tried the compress script as well as the two warp scripts. They both crash Reaper. To reproduce, run the script and have it be active (don't commit the changes by clicking a mouse button); press ESC. Reaper crashes without warning. The system I'm using is in my sig.
|
Thanks for the report -- I've been able to replicate it: On Linux, REAPER crashes if the editor is closed while the script is running. I will include a safety check for this situation in the next update.
(P.S. I have updated the GIFs for Connect nodes and Slice notes.)
Last edited by juliansader; 02-13-2019 at 04:13 PM.
|
|
|
02-13-2019, 01:11 PM
|
#331
|
Human being with feelings
Join Date: Jan 2010
Location: Kalispell
Posts: 14,745
|
Hi Julian, I was following your your list under " Midi editing tools" and Found some of them had
different names and functionality now. I'm just mentioning it because it took me some time to figure
out what was going on.
|
|
|
02-14-2019, 09:28 AM
|
#332
|
Human being with feelings
Join Date: Jun 2012
Posts: 348
|
While using the new " js_Mouse editing - Draw_ramp" script, I see that it draws plenty of redundant CC messages by default. I also understand there is a script " js_Option - Toggle skip redundant events when inserting CCs" to toggle that but how long does the toggle state survive? Will it keep it's state through all projects and after I shut down and restart Reaper?
If I want to never draw redundant CC messages, how do I do that? Inside the script I see this variable:
Code:
local skipRedundantCCs
I've tried setting it to true, I've also tried setting it to 1 (then saved/recompiled the script - I even shut down and reloaded Reaper to ensure the changes were loaded). It seems to have no effect.
p.s. Thanks for these scripts. They are awesome.
|
|
|
02-14-2019, 09:31 AM
|
#333
|
Human being with feelings
Join Date: Jun 2009
Location: Croatia
Posts: 24,790
|
The redundant CC draw toggle is global forever, it's written in reaper-extstate.ini.
|
|
|
02-14-2019, 10:08 AM
|
#334
|
Human being with feelings
Join Date: Oct 2017
Location: Larisa, Greece
Posts: 3,797
|
I armed an action from the toolbar accidentally but now i can't disarm it even if i arm a different action from the keyboard.
I tried to disarm it from the actions menu too but no luck..
Now when i arm another action from the keyboard it's messed up because they are both actions armed.
Any help would be much appreciated.
Last edited by Vagelis; 02-14-2019 at 10:25 AM.
|
|
|
02-14-2019, 11:57 AM
|
#335
|
Human being with feelings
Join Date: Jul 2009
Posts: 3,714
|
Quote:
Originally Posted by Vagelis
I armed an action from the toolbar accidentally but now i can't disarm it even if i arm a different action from the keyboard.
I tried to disarm it from the actions menu too but no luck..
Now when i arm another action from the keyboard it's messed up because they are both actions armed.
Any help would be much appreciated.
|
Could you please give some more information? (How did you arm it: left-click or right-click on toolbar button? Screenshot of toolbar? Which action did you arm? How did you try to disarm it? What do you mean by "both actions armed"? Which two actions are now both armed?)
|
|
|
02-14-2019, 12:06 PM
|
#336
|
Human being with feelings
Join Date: Jan 2010
Location: Kalispell
Posts: 14,745
|
Quote:
Originally Posted by EvilDragon
The redundant CC draw toggle is global forever, it's written in reaper-extstate.ini.
|
Can you explain ED, I don't find it in my reaper-extstate.ini. It would be great if redundant CCs would be constantly eliminated.
This is all I find that seems to apply to the "js_" script stuff. I do have an icon setup to delete redundant CCs in selected CCs.
[js_Draw linear]
Last power=5.0544702849929
[js_Insert ramps (use mouse)]
Last tip version=3.30
[js_Draw ramp]
Last shape=linear,0.0585,false
|
|
|
02-14-2019, 12:10 PM
|
#337
|
Human being with feelings
Join Date: Jun 2012
Posts: 348
|
Quote:
Originally Posted by EvilDragon
The redundant CC draw toggle is global forever, it's written in reaper-extstate.ini.
|
That's good news! Thanks.
|
|
|
02-14-2019, 12:13 PM
|
#338
|
Human being with feelings
Join Date: Jun 2012
Posts: 348
|
Quote:
Originally Posted by Tod
Can you explain ED, I don't find it in my reaper-extstate.ini. It would be great if redundant CCs would be constantly eliminated
|
I just ran the script (from within the MIDI editor) and I find this in my reaper-exstate.ini file
Code:
[js_Mouse actions]
skipRedundantCCs=true
[LFO generator]
skipRedundantCCs=true
|
|
|
02-14-2019, 12:31 PM
|
#339
|
Human being with feelings
Join Date: Jan 2010
Location: Kalispell
Posts: 14,745
|
Quote:
Originally Posted by pbattersby
I just ran the script (from within the MIDI editor) and I find this in my reaper-exstate.ini file
Code:
[js_Mouse actions]
skipRedundantCCs=true
[LFO generator]
skipRedundantCCs=true
|
Aah okay, I'll have to check it after I've run a script. Just shows my ignorance about some of this stuff.
|
|
|
02-14-2019, 01:14 PM
|
#340
|
Human being with feelings
Join Date: Dec 2015
Posts: 476
|
js_MIDI Inspector - how to change text color from yellow
Quote:
Originally Posted by juliansader
js_MIDI Inspector ...
The default colors of the GUI can be customized in the script's USER AREA.
|
Hi. Pixie utility shows that the yellow text color is
60,100,100 HSV (255,255,0 RGB).
I haven't found those numbers in the script (regarding colors).
So, how do I change this yellow to, say,
0,0,75 HSV (192,192,192 RGB) or to
0,0,78 HSV (199,199,199 RGB)?
Thanks.
|
|
|
02-14-2019, 01:47 PM
|
#341
|
Human being with feelings
Join Date: Jul 2009
Posts: 3,714
|
Quote:
Originally Posted by Tod
Aah okay, I'll have to check it after I've run a script. Just shows my ignorance about some of this stuff.
|
Users that are interested in the technical stuff can check ini files, but other users don't need to -- simply run the Toggle script, like any of REAPER's own toggle actions, and that's it!
|
|
|
02-14-2019, 01:50 PM
|
#342
|
Human being with feelings
Join Date: Jul 2009
Posts: 3,714
|
Quote:
Originally Posted by AugerJ
Quote:
Originally Posted by juliansader
js_MIDI Inspector ...
The default colors of the GUI can be customized in the script's USER AREA.
|
Hi. Pixie utility shows that the yellow text color is
60,100,100 HSV (255,255,0 RGB).
I haven't found those numbers in the script (regarding colors).
So, how do I change this yellow to, say,
0,0,75 HSV (192,192,192 RGB) or to
0,0,78 HSV (199,199,199 RGB)?
Thanks.
|
Go to the script's user area, and look for these lines:
Code:
fontFace = "Ariel"
fontSize = 14
textColor = {1,1,1,0.7}
highlightColor = {1,1,0,1}
backgroundColor = {0.18, 0.18, 0.18, 1}
shadowColor = {0,0,0,1}
The values range from 0 to 1, and are RGBA, IIRC.
|
|
|
02-14-2019, 02:35 PM
|
#343
|
Human being with feelings
Join Date: Dec 2015
Posts: 476
|
Thanks. Adjusted.
|
|
|
02-14-2019, 02:40 PM
|
#344
|
Human being with feelings
Join Date: Oct 2017
Location: Larisa, Greece
Posts: 3,797
|
Quote:
Originally Posted by juliansader
Could you please give some more information? (How did you arm it: left-click or right-click on toolbar button? Screenshot of toolbar? Which action did you arm? How did you try to disarm it? What do you mean by "both actions armed"? Which two actions are now both armed?)
|
I armed it with left click on the toolbar,the action Draw Lfo or 2-sided Warp,i tried to disarm it from the toolbar or from the actions menu with right click-disarm actions.
About both actions armed, i mean that the action on the toolbar was always armed(highlighted) even if i was arming another action from the keyboard.
E.g armed 2-sided Warp om toolbar and then Draw lfo from keyboard.
By the way i restarted Reaper now and it seems the action that was armed on the toolbar is no longer armed.(nor highlighted)
But now when i use the action Draw Lfo, with keyboard shortcut only, drag the mouse and then move the mousewheel up, i get this message:check the link https://gifyu.com/image/wPQI
P.s I get also this message even when i move the mousewheel down, but only after i scroll down 3-4 times where it reaches the last shape of the lfo.
|
|
|
02-14-2019, 03:17 PM
|
#345
|
Human being with feelings
Join Date: Jul 2009
Posts: 3,714
|
Quote:
Originally Posted by Vagelis
I armed it with left click on the toolbar,the action Draw Lfo or 2-sided Warp,i tried to disarm it from the toolbar or from the actions menu with right click-disarm actions.
|
The left-click arming method (an older scripted feature) and the right-click arming method (REAPER's recent native feature) are two distinct methods that won't affect each other. [EDIT: Hmmm... I just noticed there *is* an interaction: scripts with states set to "off" can somehow not be right-click armed. I will try to find a solution tomorrow.]
Right-click-armed actions can be disarmed -- and *need* to be disarmed -- since they temporarily override the default left-click mouse modifier.
Left-click-armed actions do not need to be disarmed, since the arming doesn't affect anything else: it simply indicates which action will be called by the "Run script that is armed in toolbar" script. You can still run any other Mouse editing script from its own shortcut.
Quote:
Originally Posted by Vagelis
About both actions armed, i mean that the action on the toolbar was always armed(highlighted) even if i was arming another action from the keyboard.
E.g armed 2-sided Warp om toolbar and then Draw lfo from keyboard.
|
When you arm an action, its button will light up and remain lit. If you run another Mouse editing action from its own shortcut (that is, not from the "Run script that is armed" script), that action's button will also light up temporarily while it is running. So you will temporarily see two button lit.
Quote:
Originally Posted by Vagelis
But now when i use the action Draw Lfo, with keyboard shortcut only, drag the mouse and then move the mousewheel up, i get this message:check the link https://gifyu.com/image/wPQI
|
I do not see a message in the screenshot - could you please upload it again?
Last edited by juliansader; 02-14-2019 at 03:37 PM.
|
|
|
02-14-2019, 03:45 PM
|
#346
|
Human being with feelings
Join Date: Jan 2010
Location: Kalispell
Posts: 14,745
|
Quote:
Originally Posted by juliansader
I do not see a message in the screenshot - could you please upload it again?
|
This is the message I see Julian.
|
|
|
02-14-2019, 04:00 PM
|
#347
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Yes, this happened to me a couple of times. For example, when the grid is set to 1/1 (or was it 1/4?). I'll have to check.
|
|
|
02-14-2019, 04:02 PM
|
#348
|
Human being with feelings
Join Date: Jun 2009
Location: Croatia
Posts: 24,790
|
Quote:
Originally Posted by juliansader
Users that are interested in the technical stuff can check ini files, but other users don't need to -- simply run the Toggle script, like any of REAPER's own toggle actions, and that's it!
|
Scripts cannot report toggle state in the Actions list, right?
|
|
|
02-14-2019, 04:05 PM
|
#349
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
|
|
|
02-14-2019, 05:02 PM
|
#350
|
Human being with feelings
Join Date: Jun 2009
Location: Croatia
Posts: 24,790
|
So perhaps that script to toggle skipping redundant CCs should report its toggle state, then
|
|
|
02-14-2019, 05:02 PM
|
#351
|
Human being with feelings
Join Date: Jul 2009
Posts: 3,714
|
Quote:
Originally Posted by Tod
This is the message I see Julian.
|
Quote:
Originally Posted by _Stevie_
Yes, this happened to me a couple of times. For example, when the grid is set to 1/1 (or was it 1/4?). I'll have to check.
|
Please copy the error text from the console and send it to me.
|
|
|
02-14-2019, 05:15 PM
|
#352
|
Human being with feelings
Join Date: Jul 2009
Posts: 3,714
|
Quote:
Originally Posted by EvilDragon
So perhaps that script to toggle skipping redundant CCs should report its toggle state, then
|
It does indeed report its toggle state in the Actions list, and you can even link it to a button. For example, in this GIF the "Skip redun" button is visible above measure 3:
One inconvenience of scripts' toggle states is that REAPER doesn't automatically update the state at startup, so you have to run the action once before you can check the state.
Last edited by juliansader; 02-17-2019 at 12:10 PM.
|
|
|
02-14-2019, 06:07 PM
|
#353
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Quote:
Originally Posted by juliansader
Please copy the error text from the console and send it to me.
|
Damn, it must have been something else in conjunction with the grid setting. I'll post it here, as soon as it happens again!
|
|
|
02-14-2019, 11:23 PM
|
#354
|
Human being with feelings
Join Date: Jun 2009
Location: Croatia
Posts: 24,790
|
Quote:
Originally Posted by juliansader
One inconvenience of scripts' toggle states is that REAPER doesn't automatically update the state at startup, so you have to run the action once before you can check the state.
|
That must be what's tripping me up. Bummer.
|
|
|
02-15-2019, 01:24 AM
|
#355
|
Human being with feelings
Join Date: Oct 2017
Location: Larisa, Greece
Posts: 3,797
|
Julian i tried again and as Stevie mentioned propably it has something to do with the grid settings.Yesterday i was trying the action while the grid was 1/128.
Today i tried with other grid settings and it worked like a charm
So the problem appears to be when the grid is at 1/128.
Last edited by Vagelis; 02-15-2019 at 01:42 AM.
|
|
|
02-17-2019, 04:09 AM
|
#356
|
Human being with feelings
Join Date: Jul 2009
Posts: 3,714
|
Quote:
Originally Posted by Vagelis
So the problem appears to be when the grid is at 1/128.
|
Thanks for letting me know. I uploaded new versions that should fix this bug (and the two other issues mentioned in previous posts).
The MIDI Inspector has also been revamped. Users sometimes complain that the region/marker area above the ruler is wasted space, particularly if the MIDI editor is docked below the arrange view. The MIDI Inspector can now be 'docked' inside this space:
Last edited by juliansader; 02-17-2019 at 12:11 PM.
|
|
|
02-17-2019, 04:19 AM
|
#357
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Wow, very unexpected, thanks Julian. Didn't even know this was possible!
Just a thought for the trim script. Do you think it would be possible to additionally incorporate a "trim start"?
|
|
|
02-17-2019, 11:05 AM
|
#358
|
Human being with feelings
Join Date: Nov 2007
Location: Lucas, TX, USA (via Luleå, Sweden)
Posts: 2,008
|
Quote:
Originally Posted by _Stevie_
Do you think it would be possible to additionally incorporate a "trim start"?
|
Yeah, I vote for that. That would enable creating "strum" chords with this tool. (although there are plenty of other ways to do that in Reaper already)
__________________
Best Regards, Ernie "lunker" Lundqvist
BDSM (Bad Dog Studio Musicians)
Windows 10 running on Z390 + i7-8700
|
|
|
02-17-2019, 11:35 AM
|
#359
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,054
|
Yep, the arpeggio tool is indeed great for that.
Julian, this is only if it's not too much work. Would just be great to have
everything in one toolset.
|
|
|
02-17-2019, 11:38 AM
|
#360
|
Human being with feelings
Join Date: Oct 2017
Location: Larisa, Greece
Posts: 3,797
|
Quote:
Originally Posted by juliansader
I uploaded new versions that should fix this bug (and the two other issues mentioned in previous posts).
|
Thank you,i synchronised reapack to test the new version but i still see this message when i scroll the mousewheel and the grid is 1/128 - straight.But i don't see it when it's 1/128 dotted or tripplets.To be honest i 'd never use so small divisions for the lfo script,i just happened to spot it.
Edit:Also here's another message that might help.
Last edited by Vagelis; 02-17-2019 at 11:45 AM.
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 12:55 AM.
|