![]() I always thought plugins were sample accurate in their entirety. I have FL Studio and ReNoise tracker to test with. I'll continue experimenting with other synths and other hosts to see what's really going on. NOTE: You'll need a copy of Spire and FF Twin to open the project. Yeah, it's safe to say that "host synced" LFO's are a joke in Reaper at the moment. and there are some unknown glitches too).Īnd you can get the Reaper project file HERE. the 3 first are completely out of sync while the 4th is somewhat in sync (some weird phasing that shouldn't happen when it's dead on. this all motivated me enough to get a quick and dirty custom FTP thingy running so that you can download the ridiculous examples here. Perhaps this should be moved to technical support forum or the bugs forum?Īnyhow, here is my post from KvR with audio links and a link to the actual Reaper project. I mean, what the hell is the point if it's slightly random every time you render or press play? This makes a lot of carefully programmed rhythmic presets that use LFO's virtually useless in a professional environment. As a sound designer I'm a bit shocked how badly the LFO's perform. I'll have to start investigating these things. It seems also that FF Twin is way tighter in the lfo implementation than Reveal Sound Spire. Interesting that it should be so hard to create a good tempo synced LFO. ![]() I never got it completely out of whack like in Reaper but definitely not sample accurate at all. ![]() Well I've now tried FL Studio and while it is definitely tighter than Reaper I could still get the two synth parts to drift away from each other. Could the problem lie within the computer/OS I'm using? Anybody here own both FF Twin and Spire? I could send the simple test project for you. I'll have to investigate if this is a common problem in other hosts as well. This is such a serious problem that it shook my very beliefs in Reaper as a host. You can even loop a short segment and let two LFO modulated lines play together and listen to the cacophony that happens. or something has happened to the damn LFO due to some Reaper internal clock issues.īottom line is: It seems like any synth with an LFO just became useless in Reaper. Well, duplicating this track or comparing it to a solid audio track like quantized drums you can easily hear that on each playback Reaper has randomized the start of the midi notes enough to put the LFO completely out of sync. ![]() So you get a simple Tatatatatata Tatatatatata rhythm. Here's what I do: Build a very simple patch in FabFilter Twin or Reveal Sound Spire, 1 osc saw wave, low pass filtered where a tempo synced 8th note triol LFO (saw wave shaped) modulates the filter cutoff. Is there something broken in Reaper 4.402? I'm having some serious timing issues with what seems to be all VSTi plugins and built in LFOs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |