|
|
|
02-11-2020, 02:19 PM
|
#41
|
Human being with feelings
Join Date: Jul 2016
Location: Los Angeles, CA
Posts: 1,701
|
So if this is monthly then I give it a +11110
Really could use some API love. There have been some GREAT API requests the last few months or so.
|
|
|
03-31-2020, 03:25 PM
|
#42
|
Human being with feelings
Join Date: May 2017
Location: Leipzig
Posts: 6,621
|
April Fool's Bump
|
|
|
04-01-2020, 04:12 PM
|
#43
|
Human being with feelings
Join Date: Apr 2014
Posts: 4,171
|
Still in my top 3 wishlist
|
|
|
04-09-2020, 07:27 AM
|
#44
|
Human being with feelings
Join Date: Mar 2019
Posts: 425
|
Bumpity Bump
|
|
|
05-30-2020, 05:59 AM
|
#45
|
Human being with feelings
Join Date: May 2020
Posts: 53
|
BUMP
+ 1000000
Please please. I tried inserting this code for a custom action (special folder-uncollapse-toggle) but its not working. This is not possible still?
reaper.Main_OnCommandEx(reaper.NamedCommandLookup( "something-from-my-action-list"), 0, 0)
function NoUndoPoint() end
reaper.defer(NoUndoPoint)
This is not just annoying, its actually destroying my track layout inversing the hidden tracks in mpc/tcp etc. Can someone confirm this is still not possible to use a "undo-defer-code" for custom actions?
And is the above code correct?
|
|
|
08-27-2020, 10:08 AM
|
#46
|
Human being with feelings
Join Date: Dec 2017
Location: Brazil
Posts: 1,992
|
+1 Bump!
Needing this for my script [Change track height using mouse wheel] to not create undo points, thanks
|
|
|
08-27-2020, 11:00 AM
|
#47
|
Human being with feelings
Join Date: May 2020
Posts: 190
|
+1 please!
|
|
|
08-27-2020, 06:59 PM
|
#48
|
Human being with feelings
Join Date: Feb 2020
Location: Los Angeles
Posts: 463
|
+1 YES PLEASE!!
|
|
|
09-05-2020, 07:04 AM
|
#49
|
Human being with feelings
Join Date: Feb 2017
Location: Kiel
Posts: 974
|
+1 please!
|
|
|
12-13-2020, 10:23 AM
|
#50
|
Human being with feelings
Join Date: Sep 2015
Location: Paris
Posts: 544
|
+ 3,141592653589793238462643383279502884197169399375 10582
|
|
|
02-11-2021, 05:41 AM
|
#51
|
Human being with feelings
Join Date: Dec 2012
Posts: 13,333
|
@Justin is it possible at all? A lot of things are unreal without this feature. Excluding undo entries would open a new world for everyone.
|
|
|
02-12-2021, 04:52 PM
|
#52
|
Human being with feelings
Join Date: Feb 2017
Location: Belgrade, Serbia
Posts: 338
|
+1
YES PLEASE!
|
|
|
02-27-2021, 03:01 PM
|
#53
|
Human being with feelings
Join Date: Apr 2014
Posts: 398
|
I'm gonna add my voice on this subject!
+1 x beaucoup
|
|
|
04-02-2021, 03:53 AM
|
#54
|
Human being with feelings
Join Date: Nov 2015
Location: earth
Posts: 471
|
Please let this be a thing soon.
|
|
|
07-17-2021, 12:19 PM
|
#55
|
Human being with feelings
Join Date: May 2018
Location: Los Angeles
Posts: 1,719
|
+1
I really think this needs to be addressed.
A filter would be a beautiful thing. Maybe a "filter" column in the Actions list where you can opt-out an action with a checkmark from being listed in the Undo list.
The idea is, anything tagged with a filter checkmark would have the script ID logged by reaper and would be omitted from the undo list (or similar).
It's crazy that we have to sift through transport and zoom settings and a plethora of other non-destructive undo items to be able to find an undo that actually changed the project.
Anyway... I love Reaper. I couldn't do my job as well without Reaper. But this has got to be the worst Undo list I have encountered in my 30+ years of being in the music industry. That said, it's better than not haveing a visual undo list.
Fingers crossed.
Cheers,
Andrew K
__________________
Cheers... Andrew K
Reaper v6.80+dev0621 - June 21 2023 • Catalina • Mac Mini 2020 6 core i7 • 64GB RAM • OS: Catalina • 4K monitor • RME RayDAT card with Sync Card and extended Light Pipe.
|
|
|
10-27-2021, 06:08 AM
|
#56
|
Human being with feelings
Join Date: Nov 2010
Posts: 1,721
|
Please please please!
Could we get a comment from the mods to say whether it's even being considered or no?
|
|
|
10-27-2021, 09:04 AM
|
#57
|
Human being with feelings
Join Date: Sep 2020
Posts: 16
|
no undo (option or method) +1
i can really use this as well. i keep the undo history on screen just to undo lists of pitch and volume changes.,.,.,
|
|
|
11-11-2021, 03:12 AM
|
#58
|
Human being with feelings
Join Date: Feb 2017
Location: Belgrade, Serbia
Posts: 338
|
I am again in a situation where I need this for a script.
+ 1000
|
|
|
11-15-2021, 11:47 PM
|
#59
|
Human being with feelings
Join Date: Oct 2019
Location: Moscow / Tbilisi
Posts: 909
|
Yes, please, devs!
These API functions would be awesome!
I understand it's maybe difficult to exclude MainCommands from undo, but other functions should be excludable as a first step.
There are a lot of ideas and space to improve whole undo system, but as a first, maybe temporary, step UndoExclude_Begin() and UndoExclude_End() would be awesome.
|
|
|
11-25-2021, 02:02 PM
|
#60
|
Human being with feelings
Join Date: Feb 2016
Location: Hollyweird
Posts: 2,630
|
Wouldn't implementing this introduce massive logic difficulties in the Reaper UX and even codebase?
It's currently possible to limit scripts of indeterminate length to a single undo step.
|
|
|
11-26-2021, 01:07 AM
|
#61
|
Human being with feelings
Join Date: Oct 2019
Location: Moscow / Tbilisi
Posts: 909
|
Quote:
Originally Posted by MonkeyBars
Wouldn't implementing this introduce massive logic difficulties in the Reaper UX and even codebase?
It's currently possible to limit scripts of indeterminate length to a single undo step.
|
I don't see any difficulties in UX, rather the opposite. In codebase... let the devs judge about it.
Here is a talk about ability to exclude from undo at all, not about limit.
For a defer scripts it is critically, for example.
|
|
|
11-26-2021, 07:20 AM
|
#62
|
Human being with feelings
Join Date: Feb 2016
Location: Hollyweird
Posts: 2,630
|
Quote:
Originally Posted by AZpercussion
I don't see any difficulties in UX
|
It's easy to think of scenarios that cause a complete logic breakdown when excluding from Undo History: - Create item
- Add take envelope to item
- Delete item but exclude from Undo History
- Undo once
What should Reaper do in this scenario? Nothing at all?
|
|
|
11-26-2021, 09:39 AM
|
#63
|
Human being with feelings
Join Date: May 2017
Location: Leipzig
Posts: 6,621
|
It would lead to this, yes, as Reaper would try to apply the undo of step 2&1 to an item, that does not exist and therefore skip these steps.
That would mean, that the devs probably would need to:
A) make every change its own step, not a combined one(afaiu, undo steps are a combination of several ProjectStateChunk-entries into one dif, that replace the current ones, when undoing, though I might be wrong about this. If I'm right, minimizing the undo-steps in their smallest chunks possible could make things more manageable, maybe not)
B) store additional metadata to an individual step like "apply this step only to the item with guid {xyzblabla}"
C) combine multiple of these steps into one undo-point
D) undo only steps of undo-points, whose referenced objects/elements exist.
With that you could get rid of step three undo-step. The undo-steps for 2&1 are still there but can't be applied with the item missing and are therefore skipped.
There are probably other things as well to take care of, as undo-management is probably the fine art of project management in general.
But I think, it might be manageable, as long as the changes and work needed, allows cool other stuff with undo as well.
For instance, when having steps with additional metadata, that references a certain item/take/marker/track/etc, you might be able to filter just all the changes done to track 1 or item 27.
So you could see an changes-history of individual elements only.
Maybe undoing even, but there are probably plenty of dependency-issues coming up.
But more detailed changes-history would be possible, just by the additional metadata stored with each undoable-step, without having to check each undo-point(consisting of several undo-steps) by hand.
Would be awesome for a lot of users.
Again, I might be wrong with my assumptions, though. Undo is complex.
|
|
|
11-26-2021, 10:19 AM
|
#64
|
Human being with feelings
Join Date: Feb 2016
Location: Hollyweird
Posts: 2,630
|
You've only touched on a fraction of the logic that would be needed for such a change.
In fact it may actually be logically impossible (as in, mathematically provably impossible) to cover all the edge cases involved in such an extreme rearchitecture intervention.
Would be interested to hear the perspective of a truly experienced enterprise software dev.
|
|
|
11-26-2021, 11:47 AM
|
#65
|
Human being with feelings
Join Date: Oct 2019
Location: Moscow / Tbilisi
Posts: 909
|
Quote:
Originally Posted by MonkeyBars
It's easy to think of scenarios that cause a complete logic breakdown when excluding from Undo History: - Create item
- Add take envelope to item
- Delete item but exclude from Undo History
- Undo once
What should Reaper do in this scenario? Nothing at all?
|
It's difficult with deleting objects, without those tricks, Mespotine described.
But there are many functions changing existing objects. And even now we can do a trick reaper.defer(function()end).
So there is a lot of space to improve. Let limitations will be.
For an example, if there is deleting action between UndoExclude_begin() and UndoExclude_end() we get error in console.
Right now I can change track info value without undo in simple script, but in deffered script I get undo anyway.
|
|
|
03-12-2022, 06:03 AM
|
#66
|
Human being with feelings
Join Date: Jan 2022
Posts: 3
|
Another solution
+1 for me
I suggest to consolidate inner undo points to the superior one:
run script
- undo begin
- .... code wich can produce its own undo begin and end, but they will be consolidated to the upper undo
- undo end
|
|
|
12-06-2023, 05:06 AM
|
#67
|
Human being with feelings
Join Date: Feb 2016
Location: Paris / France
Posts: 293
|
Upping this thread, because I stumbled on this problem today, while refining the behaviour of a tool.
My case : adding and removing companion JSFX automatically in the input FX chain to listen to midi events to be reported to a lua script. This adds undo points for the add/remove operations whereas I would like to do this in the user's back so he/she wouldn't notice and be parasited.
I guess any serious lua developer for reaper will hit that obstacle one day, at one stage or the other.
So, +1 !
Last edited by Talagan; 12-06-2023 at 05:36 AM.
|
|
|
12-06-2023, 06:12 AM
|
#68
|
Human being with feelings
Join Date: May 2019
Location: Berlin
Posts: 2,163
|
Quote:
Originally Posted by Talagan
Upping this thread, because I stumbled on this problem today, while refining the behaviour of a tool.
My case : adding and removing companion JSFX automatically in the input FX chain to listen to midi events to be reported to a lua script. This adds undo points for the add/remove operations whereas I would like to do this in the user's back so he/she wouldn't notice and be parasited.
I guess any serious lua developer for reaper will hit that obstacle one day, at one stage or the other.
So, +1 !
|
Did you try reaper.MIDI_GetRecentInputEvent?
|
|
|
12-06-2023, 06:33 AM
|
#69
|
Human being with feelings
Join Date: Feb 2016
Location: Paris / France
Posts: 293
|
Quote:
Originally Posted by FeedTheCat
Did you try reaper.MIDI_GetRecentInputEvent?
|
Thanks for your interest ! Unfortunately, I absolutely need the events to go through the track Input FX chain. The whole purpose of my plugin is to build an alternative step input method - Reaper's one is using the MIDI control path and in my workflow it's not usable since I have some channel pre-routing and note transposition in the input FX chain.
I've managed to build a decent POC, where I have two input methods : one that is equivalent to the standard method, adding notes on key release, and another one where you "validate" the currently pressed keys by pushing the sustain pedal. The other cool thing is that it works anywhere in Reaper at the edit cursor position, having the MIDI editor open or not, as long as the track is in record state, the tool is armed and a destination MIDI item/take is present under the cursor.
Last edited by Talagan; 12-06-2023 at 06:53 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 08:38 AM.
|