You have the power to stop it using the "lock thread" button (only available to you)harryupbabble wrote:If you sargasmic dudes want to keep this thread going forever, bless you.
Multiple Portable REAPER Installations
-
- KVRAF
- 16855 posts since 8 Mar, 2005 from Utrecht, Holland
We are the KVR collective. Resistance is futile. You will be assimilated. 
My MusicCalc is served over https!!
My MusicCalc is served over https!!
-
- KVRAF
- Topic Starter
- 7001 posts since 20 Mar, 2012 from Babbleon
Thanks Bert. And also thanks for that tip from before, the one about locking files in Windows 7. It saved me time looking for a Windows utility that is suited for that job.BertKoor wrote:You have the power to stop it using the "lock thread" button (only available to you)harryupbabble wrote:If you sargasmic dudes want to keep this thread going forever, bless you.
Anyways, although I have never used KVR's "lock-your-own-thread' function before, I was already aware of its existence.
But no, so far, I haven't had a reason to lock my own thread.
Although the solution to my problem has been found... there might be other solutions later on that could even be better than the current solution. Or not. One never knows.
Yes, based on past experience and/or in my case, I find that never locking a thread is a good thing. Solutions could be found after a thread-lock happens and that would suck.
Besides, I was actually thanking the sarcastic-orgasmic dudes
in the end there hence the "bless you". When this thread was resurrected, I didn't know it was sarcastic-orgasmic dudes that were going to do it till I clicked the thread. I was hoping the resurrecting would be done by people who offer solutions. As stated before, although I already found the solution, an alternate solution might also work? Or not. One never knows.So yeah, thanks again and a lot, sarcastic-orgasmic dudes,
for resurrecting my already dead thread. I would have done it myself but as stated before I already have a solution to the problem... but am still open to other solutions, if they exist.ah böwakawa poussé poussé
-
- KVRAF
- 9578 posts since 6 Jan, 2017 from Outer Space
Problem is, Reaper 5.999 might come in the year 2043... Your estimate of 100 updates per big version might be completely wrong. I guess as long there are enough new users feeding the developers, there is no need to get a big number changing. If that income is declining, they might think about getting old time users support again, which they will do in an instance...
Still, if you buy it in 2043 you will get 2000 updates whereas if you buy it now, you will only get 1894. But you will have no update from 0.999 until the year 2043...
You could have made so much money with 5.9x it would pay for Reaper 100 times...
You simply miss out learning the program in time, even 18 months of not waiting would be a big jump forward...
Btw. you are more talented as you think you are... (this is not the only thread you are active in...)
Not getting Reaper in the moment you need it (and it seems you are hot) is a waiste of talent, which is as bad as using software and not paying for it...
Still, if you buy it in 2043 you will get 2000 updates whereas if you buy it now, you will only get 1894. But you will have no update from 0.999 until the year 2043...
You could have made so much money with 5.9x it would pay for Reaper 100 times...
You simply miss out learning the program in time, even 18 months of not waiting would be a big jump forward...
Btw. you are more talented as you think you are... (this is not the only thread you are active in...)
Not getting Reaper in the moment you need it (and it seems you are hot) is a waiste of talent, which is as bad as using software and not paying for it...
-
- KVRAF
- Topic Starter
- 7001 posts since 20 Mar, 2012 from Babbleon
I think of REAPER 0.999 as an acoustic guitar and I think of REAPER 6.0 as an electric guitar. When Bob Dylan started using the Stratocaster, he didn't become Jimi Hendrix. I can write my simple songs using REAPER 0.999. Buying REAPER now is not going to make me write better simple songs.
You are right, Justin could (and did) start adding a digit to the REAPER versions, like instead of
5.91
5.92
5.93
and so on
it could be like
5.941
5.942
5.943
and so on
and that would increase the guaranteed 100 updates per major version to much more than 100 updates.
But then that would benefit the people who waited and bought REAPER at version 4.0 instead of at 3.9x.
On the other hand, Justin could sell Cockos with REAPER being at, for one example, version 6.12. After all (if my info is not faulty) he sold Nullsoft (maker of WinAmp) to AOL for 80 million dollars.
But I don't know. Maybe REAPER to Justin is nothing like WinAmp was. REAPER might be his proudest and final baby and/or he might stick with REAPER for life. Still, waiting is is a gamble.
As stated before, I only really needed the newer REAPER to do one thing that REAPER 0.999 couldn't do, and that is to process massive amount of MIDI data. But you are kind of right, by demoing the newer REAPER, I have stumbled on a Lua script that may be become super-important to my music-making method. REAPER 0.999 can't load Lua scripts.
Still, even though I'm a hasty person, being a speed scrabble player and all, my instinct is telling me that waiting can end up being beneficial.
But if my instinct ends up being wrong, and you "buy-it-now" advisers end up being right, there are other ways to simulate that Lua script that randomizes MIDI notes. At one point I was using one of these to do all of my randomizing and I might use it again (see picture below).
Obviously that randomizer in the picture below is as real as a randomizer can get and compared to a software pseudo-randomizer, it's better in that respect. But doing it that way was so slooooooooow. So yeah, I'd rather use the much much much faster Lua MIDI note randomizer script.
Anyways, you mentioned "talent". I want to express thanks but I'm not sure what for. What talent? I know for sure I don't have talent at songwriting since having talent, to me, means "doing things effortlessly and/or easily". I may have talent at playing speed scrabble but writing lyrics is extremely hard to me. Maybe writing poetry is easier (I could be wrong about that) compared to writing a song because one is not trying to make the words fit a melody when writing a poem.
I tried writing the lyrics first then the music but that is even more difficult. In my case, writing the music first seem the better way to go... the music inspires the lyrics, sometimes. Besides, Paul McCartney tended to write the music first, then the lyrics. Maybe 90 percent of songwriters do it that way.
You mentioned making money using the newer REAPER. I'm still in the "learn" mode in terms of writing songs. Who is going to donate me money for writing crap songs and tunes that were basically just results of failed music-making methods? Nobody.
Hey speaking of that, are you doing that? Making money from your (I presume not crap) songs I mean. I could use tips when it comes to that. I guess, after one is actually making decent songs, one of the first steps would be to get a PayPal account and activate PayPal's donation function. I know that much. And also, I suspect that signing up to become a YouTube Partner could be a good idea.
But what other things does a songwriter have to know in order to make money from one's own songs? I'm too lazy to Google that. It's not the right time. I have to find the right and/or satisfactory music-making method first. So yeah, apart from having difficulties trying to make the lyrics fit the melodies, I'm still stuck at getting the writing of the music to a satisfactory level. The whole thing is a Mount Everest. But it's great to be busy. Time flies.
You are right, Justin could (and did) start adding a digit to the REAPER versions, like instead of
5.91
5.92
5.93
and so on
it could be like
5.941
5.942
5.943
and so on
and that would increase the guaranteed 100 updates per major version to much more than 100 updates.
But then that would benefit the people who waited and bought REAPER at version 4.0 instead of at 3.9x.
On the other hand, Justin could sell Cockos with REAPER being at, for one example, version 6.12. After all (if my info is not faulty) he sold Nullsoft (maker of WinAmp) to AOL for 80 million dollars.
But I don't know. Maybe REAPER to Justin is nothing like WinAmp was. REAPER might be his proudest and final baby and/or he might stick with REAPER for life. Still, waiting is is a gamble.
As stated before, I only really needed the newer REAPER to do one thing that REAPER 0.999 couldn't do, and that is to process massive amount of MIDI data. But you are kind of right, by demoing the newer REAPER, I have stumbled on a Lua script that may be become super-important to my music-making method. REAPER 0.999 can't load Lua scripts.
Still, even though I'm a hasty person, being a speed scrabble player and all, my instinct is telling me that waiting can end up being beneficial.
But if my instinct ends up being wrong, and you "buy-it-now" advisers end up being right, there are other ways to simulate that Lua script that randomizes MIDI notes. At one point I was using one of these to do all of my randomizing and I might use it again (see picture below).
Obviously that randomizer in the picture below is as real as a randomizer can get and compared to a software pseudo-randomizer, it's better in that respect. But doing it that way was so slooooooooow. So yeah, I'd rather use the much much much faster Lua MIDI note randomizer script.
Anyways, you mentioned "talent". I want to express thanks but I'm not sure what for. What talent? I know for sure I don't have talent at songwriting since having talent, to me, means "doing things effortlessly and/or easily". I may have talent at playing speed scrabble but writing lyrics is extremely hard to me. Maybe writing poetry is easier (I could be wrong about that) compared to writing a song because one is not trying to make the words fit a melody when writing a poem.
I tried writing the lyrics first then the music but that is even more difficult. In my case, writing the music first seem the better way to go... the music inspires the lyrics, sometimes. Besides, Paul McCartney tended to write the music first, then the lyrics. Maybe 90 percent of songwriters do it that way.
You mentioned making money using the newer REAPER. I'm still in the "learn" mode in terms of writing songs. Who is going to donate me money for writing crap songs and tunes that were basically just results of failed music-making methods? Nobody.
Hey speaking of that, are you doing that? Making money from your (I presume not crap) songs I mean. I could use tips when it comes to that. I guess, after one is actually making decent songs, one of the first steps would be to get a PayPal account and activate PayPal's donation function. I know that much. And also, I suspect that signing up to become a YouTube Partner could be a good idea.
But what other things does a songwriter have to know in order to make money from one's own songs? I'm too lazy to Google that. It's not the right time. I have to find the right and/or satisfactory music-making method first. So yeah, apart from having difficulties trying to make the lyrics fit the melodies, I'm still stuck at getting the writing of the music to a satisfactory level. The whole thing is a Mount Everest. But it's great to be busy. Time flies.
You do not have the required permissions to view the files attached to this post.
ah böwakawa poussé poussé
-
- KVRAF
- 1950 posts since 17 Jun, 2005
One detail that leads me to believe a big part of what you are doing is just fishing for reactions: you keep repeating the same points over and over even though you have been told they are very demonstrably not true.harryupbabble wrote:the guaranteed 100 updates per major version
When you ran this stuff at the Reaper forums some months ago, it was pointed out that version numbering doesn't work that way at all. Yet you always bring up the "guaranteed" one hundred updates.
Here are some of the single updates that have increased the Reaper version number by more than 0.01, during the current version 5 lifecycle:
5.04 to 5.10
5.35 to 5.40
5.40 to 5.50
5.52 to 5.60
5.70 to 5.75
5.80 to 5.90
It doesn't say anywhere you get 100 updates per version, and it most certainly isn't "guaranteed."
-
- KVRAF
- Topic Starter
- 7001 posts since 20 Mar, 2012 from Babbleon
@Guenon
Whoa. I don't remember that at all. Can you please give a link of the REAPER forum post where "that" was pointed out to me?
Being not as green as before or knowing more now than what I knew 2 months ago, I would have reacted positively to something like "that" because with the version numbers skipping like that, it would mean that it might take sooner for Version 5.94 to get to version 6.0. But it's possible that even if "that" was pointed out to me... at that time I may have been so green or such a newbie that it wasn't making sense to me.
Instead, I remember the majority of people stating the opposite. Something like "It might take as much as a year for version 5.94 to get to version 6.0."
Hey, I would like REAPER 5.941 to skip 5.95, 5.96, 5.97, 5.98, 5.99 and get to 6.0 already.
But on the other hand, that would suck if skipping like that became the norm because I would prefer to get 100 updates per major point zero version.
Maybe "skipping" of version numbers is not the norm nor is "fractalizing" (the opposite of skipping). Okay sure, maybe 100 updates per major version is not guaranteed but maybe it balances out in the end and the total updates is close to that "100 updates"?
I asked at least twice at the REAPER forum this question or something like it:
"If I buy REAPER at 5.91 why can't my updates be good all the way to 7.91 instead of only up 6.99?"
Nobody answered that question.
It seems to me that it would be simpler to just add "the number 2" to whatever version anybody buys REAPER at. That way people actually get 2 full versions of REAPER (200 updates) at any time and/or at any version number, without having to wait for a point zero version. In my case REAPER 6.0.
I'm not "fishing for reactions". I actually do find REAPER complex and that includes the numbering of the versions. Since my plan is to make REAPER my DAW for life, I have to deal with the complexities of REAPER because the new REAPER is very good at processing massive MIDI data and also I stumble upon useful programs made by other REAPER users, like that Lua MIDI note randomizer script. I'm just asking questions and trying to make REAPER usable. How is that "fishing for reactions"?
Whoa. I don't remember that at all. Can you please give a link of the REAPER forum post where "that" was pointed out to me?
Being not as green as before or knowing more now than what I knew 2 months ago, I would have reacted positively to something like "that" because with the version numbers skipping like that, it would mean that it might take sooner for Version 5.94 to get to version 6.0. But it's possible that even if "that" was pointed out to me... at that time I may have been so green or such a newbie that it wasn't making sense to me.
Instead, I remember the majority of people stating the opposite. Something like "It might take as much as a year for version 5.94 to get to version 6.0."
Hey, I would like REAPER 5.941 to skip 5.95, 5.96, 5.97, 5.98, 5.99 and get to 6.0 already.
But on the other hand, that would suck if skipping like that became the norm because I would prefer to get 100 updates per major point zero version.
Maybe "skipping" of version numbers is not the norm nor is "fractalizing" (the opposite of skipping). Okay sure, maybe 100 updates per major version is not guaranteed but maybe it balances out in the end and the total updates is close to that "100 updates"?
I asked at least twice at the REAPER forum this question or something like it:
"If I buy REAPER at 5.91 why can't my updates be good all the way to 7.91 instead of only up 6.99?"
Nobody answered that question.
It seems to me that it would be simpler to just add "the number 2" to whatever version anybody buys REAPER at. That way people actually get 2 full versions of REAPER (200 updates) at any time and/or at any version number, without having to wait for a point zero version. In my case REAPER 6.0.
I'm not "fishing for reactions". I actually do find REAPER complex and that includes the numbering of the versions. Since my plan is to make REAPER my DAW for life, I have to deal with the complexities of REAPER because the new REAPER is very good at processing massive MIDI data and also I stumble upon useful programs made by other REAPER users, like that Lua MIDI note randomizer script. I'm just asking questions and trying to make REAPER usable. How is that "fishing for reactions"?
ah böwakawa poussé poussé
-
- KVRAF
- 2357 posts since 24 Nov, 2012
harryupbubble there is no pattern to Reaper update numbers other than they increment - they could go 5.94 to 6, or they could go 5.94 to 5.94327 or any other number bigger than 5.94. I have used Reaper since way before v1 and it has always been like this. It is part of the developers sense of humor.
There is no 100 updates per version number, there is no guarantee you will even get 10 updates in a version, there is only the history of how updating has happened and the assumption that it will continue in much the same way.
If you are uncomfortable with the way Justin runs the Reaper updating you should not buy Reaper. Every Reaper user will tell you Reaper is outstanding value for money and that updates are often. But there is no way to guarantee how many or how much stuff goes in to any particular update.
That's the way it has been since the beginning and I doubt it will change
There is no 100 updates per version number, there is no guarantee you will even get 10 updates in a version, there is only the history of how updating has happened and the assumption that it will continue in much the same way.
If you are uncomfortable with the way Justin runs the Reaper updating you should not buy Reaper. Every Reaper user will tell you Reaper is outstanding value for money and that updates are often. But there is no way to guarantee how many or how much stuff goes in to any particular update.
That's the way it has been since the beginning and I doubt it will change
-
- KVRAF
- Topic Starter
- 7001 posts since 20 Mar, 2012 from Babbleon
I would not use the word "uncomfortable". "Baffling" is my better word. But that doesn't stop me from being grateful for what REAPER has already done for me. Mainly, the batch processing of 20,000 MIDI items or drum patterns. That alone is worth S60 already to me. Days of tedious work was bypassed thanks to REAPER.
And thanks to Evil Dragon and Guenon, I can now do massive amount of MIDI editing easily and in only about 12 minutes for 20,000 MIDI items.
Anyways, I did a little bit of hasty "research" by visiting this REAPER website:
https://www.reaper.fm/download-old.php
It seems that when a version makes a big leap, for example, from 5.80 to 5.90, the amount of changes is huuuuuuuuge but proportionate?
Maybe each changes differ in terms of developer's time spent per change, but still, version 5.90 had tons of changes.
REAPER v5.90 - May 24, 2018
If It Breaks, Kenny Broke It
Downloads:
Windows (9MB installer)
Windows x64 (11MB installer)
OS X Intel (14MB DMG)
OS X 64-bit Intel (16MB DMG)
Changes:
API: TrackFX_AddByName/TrackFX_GetByName/etc can take VST2:/VST3:/VST:/AU:/JS:/DX: prefixes
API: add ReorderSelectedTracks()
API: SetEnvelopePointEx() will propagate envelope item changes when not modifying point time and nosort=false
API: SetTrackSelected() notifies various windows of state change
API: Undo_EndBlock() with empty string uses first item in block if available
Actions: fix selection behavior for various "Item edit: item under mouse cursor" actions
Audio Units: improve compatibility by resetting/re-initializing plugins only from main thread
Automation items: allow pasting of points into existing items .
Automation items: avoid setting point shape to square when FX is offlined .
Automation items: improve behavior when copy/pasting overlapping media items .
Automation items: create a new automation item when pasting points in AI-only mode
Dynamic split: fix corner case where audio is muted when the gate should open [p=kenny]
Envelopes: clear old point selection when duplicating points via mouse modifier .
Glue: do not round glued MIDI to audio samples .
Live FX multiprocessing: improve performance with folder tracks that have PDC .
Live FX multiprocessing: process receives similar to folders
Live FX multiprocessing: remove old logic for reducing worker threads when not using anticipative FX processing
MIDI editor: 14-bit CC editing fixes .
MIDI editor: allow screensets to save/load editability of individual media items
MIDI editor: allow scroll-left actions to scroll past item start but not project start
MIDI editor: avoid double-drawing many updates
MIDI editor: change default editor selection link options, may change options in existing installations
MIDI editor: do not include end-of-item all-notes-off in list of channels that contain data .
MIDI editor: faster updating when using hand scrolling
MIDI editor: fix 14-bit CC editing in event properties .
MIDI editor: fix drawing issues at extreme zoom/time combinations
MIDI editor: fix various issues with show only used/named notes
MIDI editor: fix maximize state incorrectly being reset
MIDI editor: fix next/previous note navigation/selection issues .
MIDI editor: fix pasting to secondary editable items that are looped
MIDI editor: fix pasting to secondary items that start before active item
MIDI editor: fix restore of macOS menu after renaming note .
MIDI editor: fix secondary editor zoom inconsistency with different PPQN settings .
MIDI editor: fix zoom-selection with secondary items at earlier time .
MIDI editor: improve behavior with multiple pooled items as secondary editable items
MIDI editor: improve copy/paste behavior with multiple contexts editable on multiple tracks
MIDI editor: improve start position accuracy when quickly painting new notes .
MIDI editor: improve undo messages on various lane edits
MIDI editor: improve behavior when opening multiple items at once
MIDI editor: improve behavior with hidden parent tracks
MIDI editor: when loading note names from recent list, merge with current note names when holding shift key (feature lost in v5.0) .
MIDI editor: properly enable menu option for cut/copy with CCs/Text/SysEx selected .
MIDI editor: fix adjacent note deleted on paste bug .
MIDI editor: prevent event sorting from sometimes destroying notes .
MIDI editor: fix potential deadlock issues with crop/delete active take and MIDI editor open
MIDI recording: auto-add of time-selection length MIDI items obeys new MIDI item looping preference .
Meters: fix incorrect clip indicators with +0dB maximum range .
MusicXML: set doctype correctly on timewise export (which is not supported by many programs) .
Paste: fix paste with more than 32 empty tracks between items (existed since 2005) .
Performance: make automatic worker scheduling mode slightly more aggressive
Performance: reduce underruns when repositioning the edit cursor soon after stop
Preroll: improve position calculation logic
ReaEQ: fix arrange view updating when removing bands that have automated parameters
ReaEQ: fix automated band behavior for first block after stop .
ReaEQ: fix undo when removing bands that have envelopes .
ReaEQ: support NamedConfigParm BANDTYPEx and BANDENABLEDx
ReaSurround: add edit modes to move selected inputs directly towards or away from a specific speaker
ReaSurround: add per-input channel controls to reverse (mirror) edits .
ReaSurround: add relative speaker influence mode
ReaSurround: change default 9.1 channel order to match SMPTE (existing projects are not affected)
ReaSurround: hold down control key to override reverse/mirror edits when moving inputs with the mouse
ReaSurround: hold shift key for faster edit, control key for slower edit
ReaSurround: in relative mode, prevent bleed into speakers at opposite edges of the space
ReaSurround: initialize arrangements with speakers closer to the edge of the space
ReaSurround: restrict edits to the visible space
Render: fix render preset dither when loading all settings .
Ruler: allow mapping double-click to no action .
Snap: improve snap/grid consistency with snap/grid settings linked .
Spectral editing: fix storage/application of very low compression thresholds
Take envelopes: fix snap behaviors when inserting new point via shift+click .
Take envelopes: transform MIDI take envelopes when modifying time map .
Undo: coalesce send volume/pan automation additions via action .
Undo: defer undo point for single-click media item selection
Undo: flush any latent undo states before project save
Undo: improve cursor position undo point behavior
Undo: notify MIDI editor/Project Bay from various item selection change actions when item selection undo is disabled .
VST: add compatibility setting to flush VST3 buffers with hard vs soft reset .
VST: fix state saving for bypassed/take FabFilter VST3 .
VST: when forcing VST3 bus channel count, immediately reinitialize plug-in I/O
VST: improve compatibility by resetting/re-initializing plugins only from main thread
VST: prevent hanging notes when resetting plugins on loop .
Video: re-open peaks when re-enabling audio for video item .
Virtual MIDI keyboard: pass through most shift-modified keys to main window .
REAPER v5.80 - April 25, 2018
Adieu Arsène
Downloads:
Windows (9MB installer)
Windows x64 (11MB installer)
OS X Intel (14MB DMG)
OS X 64-bit Intel (16MB DMG)
Changes:
Glue: fix creation of subsample items when gluing on partial sample boundaries .
Keyboard: add option to allow the space key to be used for navigation in various windows .
Localization: improve MIDI consolidate error messages .
MIDI editor: fix zoom to selected CC/notes with multiple contexts
ReaXcomp: improve text field behavior when automating parameters .
VST3: enabled compatibility option 'Inform plug-in of track channel count', now enabled by default
VST3: added per plug-in instance option to request bus channel count
REAPER v5.79 - April 16, 2018
Mission Accomplished!!!
Downloads:
Windows (9MB installer)
Windows x64 (11MB installer)
OS X Intel (14MB DMG)
OS X 64-bit Intel (16MB DMG)
Changes:
Actions window: refresh after duplicating custom action
Audio Units: improve support for AU that use multiple buses but do not support channel-configuration (e.g. Addictive Drums AUi) . .
Automation items: fix crash when pasting to a track with more than 127 automation items (5.78 regression)
Envelopes: do not clamp written volume envelope automation to visible envelope maximum
Free item positioning: order items by timeline position if they were split from the same original recording
Glue: round start/end times to project samplerate .
Keyboard: pass through spacebar in various windows to main window
Localization: improve routing window organization .
Localization: various fixes . . .
MIDI editor: double/halve note length actions update pre-quantized state
MIDI editor: fix possible crash when closing project tab .
MIDI editor: fix potential hang when text/sysex message list is left out of order by ReaScript .
MIDI editor: improve multi-context grid quantization behavior .
MIDI editor: in source beats piano roll view, show edit cursor position relative to source
Multiprocessing: allow autodetection of up to 32 cores/threads
MusicXML: fix importing voiced notes .
Notation: fix autoscroll issue when opening with out of range zoom levels .
Notation: if auto-zoomed-in when switching to notation view, ensure edit cursor visible
Notation: improve accidental positions on displaced notes and clusters .
Performance meter: optionally show xrun counters
ReaScript: prevent buffer overflow if very long string entered in Python path/libname in preferences
ReaScript: GetTrackEnvelopeByName()/GetTakeEnvelopeByName() search english names before localized names
Solo: improve receive behavior when folder track and child track soloed .
Undo: fix undo history compacting .
VST: support wantsChannelCountNotifications canDo
Video: add presets to invert colors, rotate to normal zoom/pan
Video: add absolute difference and other YUV blend modes to script
Windows: fix potential accessibility related crash .
REAPER v5.78 - March 25, 2018
// todo
Downloads:
Windows (9MB installer)
Windows x64 (11MB installer)
OS X Intel (14MB DMG)
OS X 64-bit Intel (16MB DMG)
Changes:
Envelopes: convert automation items to square points when copy/pasting to mute, tempo, or FX bypass envelope and automation item is not pooled
Envelopes: generally prevent curved envelope segments on FX bypass envelopes
Free item positioning: automatically reposition media items when first setting a track to FIPM
Free item positioning: initial vertical positioning, and action to auto-reposition, follows item creation order, similar to ordering when showing overlapping media items in lanes .
macOS: support third party applications/applescript inserting media with options e.g. "#NOTAB#START:0.5#LENGTH:360.0#/path/to/file"
macOS: update default FX name filtering
Multichannel audio: properly name single-channel items after "explode by channel" action .
Preferences: fix option to create new project tab when inserting media using "open with..." from explorer/finder
ReaScript: allow running scripts with restricted permissions via "ReaScript: Run [Last] ReaScript..." actions
ReaScript: GetLastTouchedFX() and GetFocusedFX() only succeed if FX is in active project .
ReaSurround: fix automation of diffusion bias knob .
Render: increase dither bit width to 1.5 bits .
Take FX: fix take FX automation timing on media items when start in source is not zero and the FX has latency .
Tempo map: fix importing initial time signature from MIDI tempo map
Track manager: fix enabling/disabling track FX via track manager mouse sweep
Track manager: fix selection mirroring when first opening the track manager
Tracks: add track height locking
VST3: fix forcing a plugin to mono if it supports more than 64 output channels .
Windows: support third party applications inserting media with options (WM_COPYDATA with dwData=0x100, data e.g. "#NOTAB#START:0.5#LENGTH:360.0#C:\path\to\filename")
And thanks to Evil Dragon and Guenon, I can now do massive amount of MIDI editing easily and in only about 12 minutes for 20,000 MIDI items.
Anyways, I did a little bit of hasty "research" by visiting this REAPER website:
https://www.reaper.fm/download-old.php
It seems that when a version makes a big leap, for example, from 5.80 to 5.90, the amount of changes is huuuuuuuuge but proportionate?
Maybe each changes differ in terms of developer's time spent per change, but still, version 5.90 had tons of changes.
REAPER v5.90 - May 24, 2018
If It Breaks, Kenny Broke It
Downloads:
Windows (9MB installer)
Windows x64 (11MB installer)
OS X Intel (14MB DMG)
OS X 64-bit Intel (16MB DMG)
Changes:
API: TrackFX_AddByName/TrackFX_GetByName/etc can take VST2:/VST3:/VST:/AU:/JS:/DX: prefixes
API: add ReorderSelectedTracks()
API: SetEnvelopePointEx() will propagate envelope item changes when not modifying point time and nosort=false
API: SetTrackSelected() notifies various windows of state change
API: Undo_EndBlock() with empty string uses first item in block if available
Actions: fix selection behavior for various "Item edit: item under mouse cursor" actions
Audio Units: improve compatibility by resetting/re-initializing plugins only from main thread
Automation items: allow pasting of points into existing items .
Automation items: avoid setting point shape to square when FX is offlined .
Automation items: improve behavior when copy/pasting overlapping media items .
Automation items: create a new automation item when pasting points in AI-only mode
Dynamic split: fix corner case where audio is muted when the gate should open [p=kenny]
Envelopes: clear old point selection when duplicating points via mouse modifier .
Glue: do not round glued MIDI to audio samples .
Live FX multiprocessing: improve performance with folder tracks that have PDC .
Live FX multiprocessing: process receives similar to folders
Live FX multiprocessing: remove old logic for reducing worker threads when not using anticipative FX processing
MIDI editor: 14-bit CC editing fixes .
MIDI editor: allow screensets to save/load editability of individual media items
MIDI editor: allow scroll-left actions to scroll past item start but not project start
MIDI editor: avoid double-drawing many updates
MIDI editor: change default editor selection link options, may change options in existing installations
MIDI editor: do not include end-of-item all-notes-off in list of channels that contain data .
MIDI editor: faster updating when using hand scrolling
MIDI editor: fix 14-bit CC editing in event properties .
MIDI editor: fix drawing issues at extreme zoom/time combinations
MIDI editor: fix various issues with show only used/named notes
MIDI editor: fix maximize state incorrectly being reset
MIDI editor: fix next/previous note navigation/selection issues .
MIDI editor: fix pasting to secondary editable items that are looped
MIDI editor: fix pasting to secondary items that start before active item
MIDI editor: fix restore of macOS menu after renaming note .
MIDI editor: fix secondary editor zoom inconsistency with different PPQN settings .
MIDI editor: fix zoom-selection with secondary items at earlier time .
MIDI editor: improve behavior with multiple pooled items as secondary editable items
MIDI editor: improve copy/paste behavior with multiple contexts editable on multiple tracks
MIDI editor: improve start position accuracy when quickly painting new notes .
MIDI editor: improve undo messages on various lane edits
MIDI editor: improve behavior when opening multiple items at once
MIDI editor: improve behavior with hidden parent tracks
MIDI editor: when loading note names from recent list, merge with current note names when holding shift key (feature lost in v5.0) .
MIDI editor: properly enable menu option for cut/copy with CCs/Text/SysEx selected .
MIDI editor: fix adjacent note deleted on paste bug .
MIDI editor: prevent event sorting from sometimes destroying notes .
MIDI editor: fix potential deadlock issues with crop/delete active take and MIDI editor open
MIDI recording: auto-add of time-selection length MIDI items obeys new MIDI item looping preference .
Meters: fix incorrect clip indicators with +0dB maximum range .
MusicXML: set doctype correctly on timewise export (which is not supported by many programs) .
Paste: fix paste with more than 32 empty tracks between items (existed since 2005) .
Performance: make automatic worker scheduling mode slightly more aggressive
Performance: reduce underruns when repositioning the edit cursor soon after stop
Preroll: improve position calculation logic
ReaEQ: fix arrange view updating when removing bands that have automated parameters
ReaEQ: fix automated band behavior for first block after stop .
ReaEQ: fix undo when removing bands that have envelopes .
ReaEQ: support NamedConfigParm BANDTYPEx and BANDENABLEDx
ReaSurround: add edit modes to move selected inputs directly towards or away from a specific speaker
ReaSurround: add per-input channel controls to reverse (mirror) edits .
ReaSurround: add relative speaker influence mode
ReaSurround: change default 9.1 channel order to match SMPTE (existing projects are not affected)
ReaSurround: hold down control key to override reverse/mirror edits when moving inputs with the mouse
ReaSurround: hold shift key for faster edit, control key for slower edit
ReaSurround: in relative mode, prevent bleed into speakers at opposite edges of the space
ReaSurround: initialize arrangements with speakers closer to the edge of the space
ReaSurround: restrict edits to the visible space
Render: fix render preset dither when loading all settings .
Ruler: allow mapping double-click to no action .
Snap: improve snap/grid consistency with snap/grid settings linked .
Spectral editing: fix storage/application of very low compression thresholds
Take envelopes: fix snap behaviors when inserting new point via shift+click .
Take envelopes: transform MIDI take envelopes when modifying time map .
Undo: coalesce send volume/pan automation additions via action .
Undo: defer undo point for single-click media item selection
Undo: flush any latent undo states before project save
Undo: improve cursor position undo point behavior
Undo: notify MIDI editor/Project Bay from various item selection change actions when item selection undo is disabled .
VST: add compatibility setting to flush VST3 buffers with hard vs soft reset .
VST: fix state saving for bypassed/take FabFilter VST3 .
VST: when forcing VST3 bus channel count, immediately reinitialize plug-in I/O
VST: improve compatibility by resetting/re-initializing plugins only from main thread
VST: prevent hanging notes when resetting plugins on loop .
Video: re-open peaks when re-enabling audio for video item .
Virtual MIDI keyboard: pass through most shift-modified keys to main window .
REAPER v5.80 - April 25, 2018
Adieu Arsène
Downloads:
Windows (9MB installer)
Windows x64 (11MB installer)
OS X Intel (14MB DMG)
OS X 64-bit Intel (16MB DMG)
Changes:
Glue: fix creation of subsample items when gluing on partial sample boundaries .
Keyboard: add option to allow the space key to be used for navigation in various windows .
Localization: improve MIDI consolidate error messages .
MIDI editor: fix zoom to selected CC/notes with multiple contexts
ReaXcomp: improve text field behavior when automating parameters .
VST3: enabled compatibility option 'Inform plug-in of track channel count', now enabled by default
VST3: added per plug-in instance option to request bus channel count
REAPER v5.79 - April 16, 2018
Mission Accomplished!!!
Downloads:
Windows (9MB installer)
Windows x64 (11MB installer)
OS X Intel (14MB DMG)
OS X 64-bit Intel (16MB DMG)
Changes:
Actions window: refresh after duplicating custom action
Audio Units: improve support for AU that use multiple buses but do not support channel-configuration (e.g. Addictive Drums AUi) . .
Automation items: fix crash when pasting to a track with more than 127 automation items (5.78 regression)
Envelopes: do not clamp written volume envelope automation to visible envelope maximum
Free item positioning: order items by timeline position if they were split from the same original recording
Glue: round start/end times to project samplerate .
Keyboard: pass through spacebar in various windows to main window
Localization: improve routing window organization .
Localization: various fixes . . .
MIDI editor: double/halve note length actions update pre-quantized state
MIDI editor: fix possible crash when closing project tab .
MIDI editor: fix potential hang when text/sysex message list is left out of order by ReaScript .
MIDI editor: improve multi-context grid quantization behavior .
MIDI editor: in source beats piano roll view, show edit cursor position relative to source
Multiprocessing: allow autodetection of up to 32 cores/threads
MusicXML: fix importing voiced notes .
Notation: fix autoscroll issue when opening with out of range zoom levels .
Notation: if auto-zoomed-in when switching to notation view, ensure edit cursor visible
Notation: improve accidental positions on displaced notes and clusters .
Performance meter: optionally show xrun counters
ReaScript: prevent buffer overflow if very long string entered in Python path/libname in preferences
ReaScript: GetTrackEnvelopeByName()/GetTakeEnvelopeByName() search english names before localized names
Solo: improve receive behavior when folder track and child track soloed .
Undo: fix undo history compacting .
VST: support wantsChannelCountNotifications canDo
Video: add presets to invert colors, rotate to normal zoom/pan
Video: add absolute difference and other YUV blend modes to script
Windows: fix potential accessibility related crash .
REAPER v5.78 - March 25, 2018
// todo
Downloads:
Windows (9MB installer)
Windows x64 (11MB installer)
OS X Intel (14MB DMG)
OS X 64-bit Intel (16MB DMG)
Changes:
Envelopes: convert automation items to square points when copy/pasting to mute, tempo, or FX bypass envelope and automation item is not pooled
Envelopes: generally prevent curved envelope segments on FX bypass envelopes
Free item positioning: automatically reposition media items when first setting a track to FIPM
Free item positioning: initial vertical positioning, and action to auto-reposition, follows item creation order, similar to ordering when showing overlapping media items in lanes .
macOS: support third party applications/applescript inserting media with options e.g. "#NOTAB#START:0.5#LENGTH:360.0#/path/to/file"
macOS: update default FX name filtering
Multichannel audio: properly name single-channel items after "explode by channel" action .
Preferences: fix option to create new project tab when inserting media using "open with..." from explorer/finder
ReaScript: allow running scripts with restricted permissions via "ReaScript: Run [Last] ReaScript..." actions
ReaScript: GetLastTouchedFX() and GetFocusedFX() only succeed if FX is in active project .
ReaSurround: fix automation of diffusion bias knob .
Render: increase dither bit width to 1.5 bits .
Take FX: fix take FX automation timing on media items when start in source is not zero and the FX has latency .
Tempo map: fix importing initial time signature from MIDI tempo map
Track manager: fix enabling/disabling track FX via track manager mouse sweep
Track manager: fix selection mirroring when first opening the track manager
Tracks: add track height locking
VST3: fix forcing a plugin to mono if it supports more than 64 output channels .
Windows: support third party applications inserting media with options (WM_COPYDATA with dwData=0x100, data e.g. "#NOTAB#START:0.5#LENGTH:360.0#C:\path\to\filename")
ah böwakawa poussé poussé
-
- KVRAF
- 1950 posts since 17 Jun, 2005
Well, here's a couple:harryupbabble wrote:Whoa. I don't remember that at all. Can you please give a link of the REAPER forum post where "that" was pointed out to me?
https://forum.cockos.com/showpost.php?p ... stcount=21
https://forum.cockos.com/showpost.php?p ... stcount=34
You did:harryupbabble wrote:I would have reacted positively to something like "that" because with the version numbers skipping like that, it would mean that it might take sooner for Version 5.94 to get to version 6.0.
https://forum.cockos.com/showpost.php?p ... stcount=29
-
- KVRAF
- Topic Starter
- 7001 posts since 20 Mar, 2012 from Babbleon
Okay. I don't remember reading those. It's possible I started reading the replies but got distracted and didn't finish reading the whole thread's replies. I am a multi-tasker. Sometimes I would be testing my music-making method on my offline Windows 7 computer, while on my online computer I am lurking/reading at KVR or at the REAPER forum, while also watching a downloaded movie from the internet archive (also on my offline Windows 7 computer). Plus, I'm an insomniac and get dizzy all the time.Guenon wrote:Well, here's a couple:harryupbabble wrote:Whoa. I don't remember that at all. Can you please give a link of the REAPER forum post where "that" was pointed out to me?
https://forum.cockos.com/showpost.php?p ... stcount=21
https://forum.cockos.com/showpost.php?p ... stcount=34
You did.harryupbabble wrote:I would have reacted positively to something like "that" because with the version numbers skipping like that, it would mean that it might take sooner for Version 5.94 to get to version 6.0.
I have to make a trip to the loo. Be back in about 5 minutes.
ah böwakawa poussé poussé
-
- KVRAF
- 1950 posts since 17 Jun, 2005
Yet you unknowingly replied?harryupbabble wrote:Okay. I don't remember reading those. It's possible I started reading the replies but got distracted and didn't finish reading the whole thread's replies.Guenon wrote:You did.harryupbabble wrote:I would have reacted positively to something like "that" because with the version numbers skipping like that, it would mean that it might take sooner for Version 5.94 to get to version 6.0.
Anyway. I'm actually off to the loo as well. (Seriously.) And then off to bed. So yeah, take care.
-
- KVRAF
- Topic Starter
- 7001 posts since 20 Mar, 2012 from Babbleon
You are right. I found that thread and my replies:
https://forum.cockos.com/showthread.php ... ost2009484
I seriously do not remember that. Bad memory. But I stand by what I stated there, at that thread.
https://forum.cockos.com/showthread.php ... ost2009484
I seriously do not remember that. Bad memory. But I stand by what I stated there, at that thread.
ah böwakawa poussé poussé
-
- KVRAF
- Topic Starter
- 7001 posts since 20 Mar, 2012 from Babbleon
Okay so, if I buy REAPER at current version 5.941, there's no guarantee I will get 106 updates.
If I buy REAPER at version 6.0, there's no guarantee I'll get 200 updates.
But I like that 200 is almost twice 106.
If I buy REAPER now or if I buy a year later, what difference does it make to Justin anyways?
Either way, Justin gets my 60 USD (equivalent of 80 CAD).
If I buy REAPER at version 6.0, there's no guarantee I'll get 200 updates.
But I like that 200 is almost twice 106.
If I buy REAPER now or if I buy a year later, what difference does it make to Justin anyways?
Either way, Justin gets my 60 USD (equivalent of 80 CAD).
ah böwakawa poussé poussé
-
- KVRAF
- 9578 posts since 6 Jan, 2017 from Outer Space
For Justin it will be a big difference. If he gets it now, he will have resources to enhance Reaper now. Which leads to a better product you will benefit from earlier than if he doesn’t get it now.
Your benefit is even much bigger. You can work now and as you could already work with version 0.999 which you did not pay for, you can work with version 6.99 ‘til the end of your life and you contributed for its developement, maybe put some suggestions into the feature list etc...
Its pointless to try to safe on an under priced product. You got your value of 60$ already for free with the demo...
The only reason to wait could be for the exchange rate between US and Canadien $ to drop another 50%...; - )
I heard that version 7 has no features you would die for, but version 6 has all of them...
Just being grateful will make your life easier than being greedy...
Your benefit is even much bigger. You can work now and as you could already work with version 0.999 which you did not pay for, you can work with version 6.99 ‘til the end of your life and you contributed for its developement, maybe put some suggestions into the feature list etc...
Its pointless to try to safe on an under priced product. You got your value of 60$ already for free with the demo...
The only reason to wait could be for the exchange rate between US and Canadien $ to drop another 50%...; - )
I heard that version 7 has no features you would die for, but version 6 has all of them...
Just being grateful will make your life easier than being greedy...
-
- KVRAF
- Topic Starter
- 7001 posts since 20 Mar, 2012 from Babbleon
Resources? Didn't Justin sell his Nullsoft company to AOL for 80 million dollars?Tj Shredder wrote:For Justin it will be a big difference. If he gets it now, he will have resources to enhance Reaper now. Which leads to a better product you will benefit from earlier than if he doesn’t get it now.
Your benefit is even much bigger. You can work now and as you could already work with version 0.999 which you did not pay for, you can work with version 6.99 ‘til the end of your life and you contributed for its developement, maybe put some suggestions into the feature list etc...
Its pointless to try to safe on an under priced product. You got your value of 60$ already for free with the demo...
The only reason to wait could be for the exchange rate between US and Canadien $ to drop another 50%...; - )
I heard that version 7 has no features you would die for, but version 6 has all of them...
Just being grateful will make your life easier than being greedy...
I have been working and can still work now using REAPER 0.999 as my main DAW. I can also work with Tunafish, Podium Free, Anvil Studio, and many many many other free MIDI sequencers.
I don't really use the A or audio part of DAW. In my case, instead of DAW, DMW would be a better acronym, short for Digital MIDI Workstation.
Okay you call it greedy but I call it frugality. Justin himself might be practicing frugality. I read of him in interviews and Q and A sessions where I get the feeling that he is a frugal guy. In one article, if I recall correctly, he was waiting for a certain brand of camera to go down in price before buying it.
I think you "buy-it-now" advisers are blinded by your extreme loyalty to Justin. But I am of course just guessing when making that assessment.
When people rent a car, don't most people choose rental companies that give them more mileage?
When people buy a house, don't they choose a mortgage company that gouges them less?
Don't most people at KVR's buy and sell forum wait for sales before they buy anything?
Would you call those people "greedy"? I would call those people practitioners of the "get more bang out of your buck" principle. Some people are not born rich nor have jobs that pays 80 dollars an hour and some people have to be penny-pinchers because buying unfrugally piles up.
So when I apply the same frugality when buying REAPER how come it's deemed as illogical and greedy?
No one knows the future. Everyone is guessing just like I am guessing.
No one knows how much irregular updating could affect the total updates per major version. But I still think that the magic number is close to 100. Someone else can do the research, if they want, to see exactly how many updates were there for all the major versions. How many updates did REAPER 2.0 have? And how about versions 3.0 and 4.0?
Also, it seems that when REAPER makes a leap or skip several version numbers, for example, the leap from version 5.80 to 5,90... if you look at the amount of changes made in version 5.90, you might actually be looking at 10 updates compressed into one update. So maybe that argument about REAPER versions skipping several version numbers is not that strong of an argument and the total updates per major version works out to be still about 100?
ah böwakawa poussé poussé