Is there another place to discuss this besides the pre-release thread?
I use this regularly, but it's barely functional without creating a bunch of problems. Notice how the Ableton paste is a perfect duplicate and doesn't interrupt anything around it? The Reaper paste is quirky right off the bat, creating a ramp between the end of the previous item and the paste. Try that same copy/paste, but delete some of the items and leave the automation -- the automation won't copy unless it's attached to items! Now try cutting little pieces out of the items and doing the copy/paste -- you'll get weird edgepoints between the cuts that screw up any smooth automation curves.
My whole point here -- Ableton paste creates an exact duplicate of the area in every single way. Literally identical. Reaper's (because it's item-based) is marred with issues and quirks and is barely usable without extreme caution.
I use this regularly, but it's barely functional without creating a bunch of problems. Notice how the Ableton paste is a perfect duplicate and doesn't interrupt anything around it? The Reaper paste is quirky right off the bat, creating a ramp between the end of the previous item and the paste. Try that same copy/paste, but delete some of the items and leave the automation -- the automation won't copy unless it's attached to items! Now try cutting little pieces out of the items and doing the copy/paste -- you'll get weird edgepoints between the cuts that screw up any smooth automation curves.
My whole point here -- Ableton paste creates an exact duplicate of the area in every single way. Literally identical. Reaper's (because it's item-based) is marred with issues and quirks and is barely usable without extreme caution.
Area selection has been discussed many times, it's a separate request to AI. If you search feature requests you'll fine it
Area selection has been discussed many times, it's a separate request to AI. If you search feature requests you'll fine it
Thanks Travesty, I realize - but this came from the idea of adding the option to "Encapsulate entire envelope track in AI". Like, make the whole thing into an automation item, that way it'll behave like the other items, and we're 3/4 of the way to proper area duplication
On OS/X I've been seeing it a lot without knowing what it was. [No audio clicks or perceptible troubles in my sessions.] Using a pre-release, I just assumed it was a graphics glitch since it did not coincide with anything perceptibly wrong with any of my day to day music work.
Thanx dadek, for chiming in on the yellow flashing issue.
I am "glad" i am not the only OSX user that experiences alot of flashing for no appearant, audible, reason.
am aware (@my last line).
i was doing just that squire and thought of new users having to do yet another 'set things up-themselves' routine when it's not really necessary..
plus atm saving and loading isn't to a specific folder and is generally 'high friction' unnecessarily.
i appreciate getting AI's funtional is the priority but the suggestion was a user friendly consideration when the time comes to polish.
am aware (@my last line).
i was doing just that squire and thought of new users having to do yet another 'set things up-themselves' routine when it's not really necessary..
plus atm saving and loading isn't to a specific folder and is generally 'high friction' unnecessarily.
i appreciate getting AI's funtional is the priority but the suggestion was a user friendly consideration when the time comes to polish.
Perhaps instead it would make more sense to have actions that create the available shaped LFOs instantly as an AI. Maybe ones with the first point set to a specific default shape (but that's already very easy).
Fade-in/out is really just 2 clicks to make the AI then fade, I don't know how you could make that simpler.
thats certainly an idea, tho fade was but one example, to draw one/anything is a mouse move eye strain time user (hitpoints are small tbh anyone over 40 which will be me soon wants to avoid that!), to have 1 bar or 2bar fade or common shapes handy for pan or anything else ready to roll for all users is well within the realms of a sensible suggestion i thought.
i'm happy to create my own or nab someone elses, but that wasn't the point.
This is my first post of this sort here.
I guess I found a little bug. It's a really really basic one and actually it surprises me quite a lot. Hope this is the place to report it.
I have created a few track templates and I've stored them in their default directory. The problem is that they don't show up in the "Insert track from template" submenu when you right click a track. I see an item "(track template list)" right where my track templates should be. The same submenu in the main track menu (the one on the main menu bar) works just fine. I hope I'm not crazy. 😊
I don't know about other builds, but this bug is definitely present in the 64-bit version of 5.40.
I apologize for not testing the latest development build, but I'm still a beginner and thus I'm avoiding unstable builds - due to my limited skills I wouldn't be much of a tester anyway. ☺
This is my first post of this sort here.
I guess I found a little bug. It's a really really basic one and actually it surprises me quite a lot. Hope this is the place to report it.
I have created a few track templates and I've stored them in their default directory. The problem is that they don't show up in the "Insert track from template" submenu when you right click a track. I see an item "(track template list)" right where my track templates should be. The same submenu in the main track menu (the one on the main menu bar) works just fine. I hope I'm not crazy.
I don't know about other builds, but this bug is definitely present in the 64-bit version of 5.40.
I apologize for not testing the latest development build, but I'm still a beginner and thus I'm avoiding unstable builds - due to my limited skills I wouldn't be much of a tester anyway. ☺
The pre-release forum is strictly for beta releases and issues directly related to what the devs are addressing in those beta releases.
Many thanks, now I know. I should have looked better.
I'll post it in the correct forum as well just to report it just like I should have.
All the best and thanks again.
Regarding yellow flashing, what kind of latencies are you guys using?
On linux it seems much more prevalent on 64/128 samples buffer. I think there are occasions where there are some latency spikes in reaper's processing, still have isolate the circumstances where it happens. With 256 samples buffer the latency spikes seem small enough (normally 4-5ms) to not exceed the deadline.
__________________ Reaper for Linux Documentation (WIP). Software: Archlinux/KDE, Fabfilter FX, Komplete 8, Nebula, Schwa/Stillwell, T-racks Max/Amplitube/SVX, etc. Gear: i7-2600k/4700HQ/16GB, RME Multiface/Babyface, Behringer X32, Genelec 8040, etc. :)
Regarding yellow flashing, what kind of latencies are you guys using?
On linux it seems much more prevalent on 64/128 samples buffer. I think there are occasions where there are some latency spikes in reaper's processing, still have isolate the circumstances where it happens. With 256 samples buffer the latency spikes seem small enough (normally 4-5ms) to not exceed the deadline.
The buffer-size is irrelevant. If my project can play and record without any dropouts, then I don't need to know if there's a dropout otherwise.
I don't want to increase my overall latency when it's not needed, just to avoid getting a migraine because Reaper decides to flash wildly when I insert a plug-in (or any number of non-critical actions).
The buffer-size is irrelevant. If my project can play and record without any dropouts, then I don't need to know if there's a dropout otherwise.
I don't want to increase my overall latency when it's not needed, just to avoid getting a migraine because Reaper decides to flash wildly when I insert a plug-in (or any number of non-critical actions).
That wasn't really the point! FWIW, the latest reaper for linux has an option to turn it on, so I'm pretty sure the next pre will solve your problem.
What I'm getting at is collecting some information from the people that see a lot of flashing, in order to figure out what goes wrong. Most likely these are bugs and ought to be squashed, even if you don't normally notice them, there is the possibility that they might show up at other occasions. IMO best to find them and to get rid of them completely..
__________________ Reaper for Linux Documentation (WIP). Software: Archlinux/KDE, Fabfilter FX, Komplete 8, Nebula, Schwa/Stillwell, T-racks Max/Amplitube/SVX, etc. Gear: i7-2600k/4700HQ/16GB, RME Multiface/Babyface, Behringer X32, Genelec 8040, etc. :)
That wasn't really the point! FWIW, the latest reaper for linux has an option to turn it on, so I'm pretty sure the next pre will solve your problem.
What I'm getting at is collecting some information from the people that see a lot of flashing, in order to figure out what goes wrong. Most likely these are bugs and ought to be squashed, even if you don't normally notice them, there is the possibility that they might show up at other occasions. IMO best to find them and to get rid of them completely..
My point is that I think it's working as intended and there's nothing to fix. It seems like the flashing indicator is working as designed.
The problem is that not everyone cares about all dropouts, but some people might! For instance, if I'm working live then I absolutely care about dropouts inserting a plugin. If I'm mixing then I don't care at all.
It'd be insane to have a panel (and the associate code happening real-time) to optionally check off when dropouts should be monitored. It's basically an all-or-nothing sort of preference.
My point is that I think it's working as intended and there's nothing to fix. It seems like the flashing indicator is working as designed.
The problem is that not everyone cares about all dropouts, but some people might! For instance, if I'm working live then I absolutely care about dropouts inserting a plugin. If I'm mixing then I don't care at all.
Yes it does work as intended, but that it flashes a lot all the time, probably indicates that something else isn't working as intended. What I'm interested in finding out if it's reaper being broken and in what way.
But probably a moot point now, since there is a report with it happening on os/x with 512/1024 samples buffer, so it's not only at low buffer sizes. I'd say barring some problem in that particular os/x install/hardware, there is definitely something off, unless it's could all be traced back to some broken plugins.
__________________ Reaper for Linux Documentation (WIP). Software: Archlinux/KDE, Fabfilter FX, Komplete 8, Nebula, Schwa/Stillwell, T-racks Max/Amplitube/SVX, etc. Gear: i7-2600k/4700HQ/16GB, RME Multiface/Babyface, Behringer X32, Genelec 8040, etc. :)
duplicating or copying Automation item produces unexpected results.
I'm not sure what a preferable behavior would be. Here is what currently happens:
We could add an option for automation items to replace instead of layer, which would be similar to the existing option to trim content behind media items when editing.
I'm not sure what a preferable behavior would be. Here is what currently happens:
We could add an option for automation items to replace instead of layer, which would be similar to the existing option to trim content behind media items when editing.
if they are layering, that actually gets sent to the plugin? top layer or the sum of all?
__________________
REAPER Video Tutorials, Tips & Tricks and more at The REAPER Blog
I support this as the default behaviour... as long as there's an action/mouse-modifier to override it quickly when necessary.
I can't think of any times when I want the envelope to not be overwritten, but with AIs I can think of a few cases that I do.
I agree with this.
There are definitely a lot of uses for all these AIs overlapping and adding together though so as long as that doesn't disappear and can be accessed easily that's great.
Or, what if we had the "mix behaviour" option for AIs (like we do for normal items) so we can decide what overlapping items should do?
Also, as long as the overlapping stuff is obvious to people new to reaper as it's quite useful for a lot of different areas of audio and would be a shame for it to be forgotten about
__________________ subproject FRs click here note: don't search for my pseudonym on the web. The "musicbynumbers" you find is not me or the name I use for my own music.