I'm working on V3 updates to the 500 series at the moment - I'll take a look at what we can do regarding the UI dimensions, the issue is actually that *most* DAWs seem to be configured for 'landscape' plug-in UIs, so, for example Presonus Studio One will add padding to the UI of approximately what you have there in the DYN500 screenshot and there's nothing the plug-in can do about it. I can live with more latency playing guitar or bass than drums.Īs for OverTone DSP's plugins and REAPER, the only issue I have is not being able to put multiple 500 series plugs side by side because they have a shaded background on the sides which makes their container in REAPER as wide as it is tall, even though the plugin UI only needs 1/3 of that space horizontally. Just playing a beat to a song it isn't so noticeable but with tight double stroke rolls it feels a lot tighter playing at 64 samples. At the the higher latency, I can feel that I am outrunning the time it takes to receive a midi note, send it to Superior, have Superior render it and send it back out as audio. Playing a tight buzz roll on my V-Drums playing through REAPER to Superior Drummer 2 felt much tighter at 64 samples latency than at 128. The biggest place that difference showed up for me was on digital drums. What I noticed in particular when I built my current machine, was that I could drop to the next lower buffer size and still get reliable performance. The good thing is that anticipative fx allows you to lower the buffer sizes for live monitoring while still allowing fx chains (on played back material) that would normally cause dropouts with such small buffers. When you live monitor a track the latency will be given by the buffer sizes, any additional hardware latency, and any latency induced by plugins on the track and master fx. It's exclusively for the tracks playing back. Note that anticipative fx doesn't apply to live monitored tracks. I can’t edit the track volume via clicking on the volume field on a track in the TCP and MCP (have to confirm that on my windows machine…) For some reason, pressing ESC in the main window tries to close Reaper. This makes it impossible to close both windows via pressing ESC two times. Indirectly this is also a problem with the track FX window: When I open that, Reaper opens the browser (when there are no effects no the track), but closing the browser with ESC now leaves me with the main windows focused (instead of the track FX window). When I open the mixer, the main window is still focused. I can’t open the Media Explorer via Ctrl+Alt+X, stuff like Ctrl+Alt+V for the Navigator works though I can’t correctly map some shortcuts (using a German keyboard layout), for example trying to map Ctrl+Alt+^ gives me Ctrl+Alt+▯ and the shortcut does nothing when pressed in the track FX window, double clicking into the plugin list does nothing (should open up the FX browser) Hey folks, got some minor workflow issues as Reaper seems to behave a little differently from Windows in some respects: My most recent project in REAPER has 28 tracks with 49 FX (47 of which are OverTone DSP plugins) and playing it at 64 samples latency shows me I'm only using 24.96% of my CPU's total capacity. Now that I'm running almost all native Linux plugins, I'm not taxing my CPU at all. While I don't really use virtual amps, I do always monitor through REAPER and frequently do it through 3 to 5 VST plugins.Ħ4 samples latency is how I run all the time, and only on the most complex of projects do I ever have to increase to 128 during the final mixing and mastering phases. Like you're playing through a slap echo or something. If you hit a note on a guitar but the sound for it doesn't come out until 30ms later it's going to feel real sloppy playing. If you monitor through REAPER like I do, then low latency is a big deal. by the time we're talking about 64 or less you could just move closer to the speakers and save the extra CPU usage. I think the issue is that I was running slightly larger buffer settings than most here seem to (I seldom need to drop the buffer size below 256 normally - I certainly wouldn't need to go to 64 in normal usage.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |