Reaper Render Settings

[Tarja Rabito]

Ihad a frustrating experience while doing test renders for the new album. The length of the rendered file was actually shorter then the length of the source material. I ended up playing with a number of different render settings trying to figure out what was going on.

I know this seems simple but it is the simple things like this that will cause you to pull your hair out when you are in the final stages of a project. Posting this here in hopes it saves someone else some frustration.

Just wanted to let you know I found an issue with rendering using Scaler 2 as a VST instrument in reaper DAW. If I render off-line the rendered audio file is out of sync with the rest of the project. The only way to get around this is if I render it online, in real time, and everything works fine but it takes much longer.

@BornFP

Can you be more specific here because I am using it and not having any sync problems bouncing offline. Are you in BIND mode? Are you using an Arp? Expression? What set up and what version? And when you say out of sync what do you mean?

Davide,

Bind, Arp, expression settings make no difference. The problem is not with sending midi to the DAW from Scaler 2.

I am talking about a piece of MIDI that I have on a track in Reaper already. If I then add on scaler 2 as the virtual instrument for this track to play the MIDI, I get the problem. For examle, I may already have a Midi made but I like the instrument sounds from scaler 2 and want to use it just to play the midi. When I have it set up like this and render it anyway other than off-line at one time speed, it becomes out of sync. Meaning sounds that were rendered from the midi file using scaler 2 as a virtual instrument are about a quarter second out of sync from the rest of the sounds in the rendered WAV.

Just to make sure I fully answered your question though, when I was using it last I believe it was set to use expressions. Binding was not on. Dynamic voicing was on. It also does the same thing with these are all set to default settings.

I am on a PC with newest update of windows 10. I get the same issue with the VST3 or VST2. No other effects or delays running on these tracks. Also have no issue with any other virtual instruments. I could switch the virtual instrument on the track to something different than scaler and have no issues with rendering.

A posible explication: It happens that when draging the midi from your Scaler instance to your same Scaler track when playing it back it is then fed into your Scaler instance again and any articulation that could be applied to midi data got applied twice.

When ReaWwise reads the output of the REAPER render settings, the first item it sees to be rendered is the file T:\Footsteps\Footsteps-Dirt-Variation 1-Attack.wav. You can preview the files that ReaWwise uses to generate the preview by clicking the button to the right of the Render To input field of the Render to File dialog in REAPER.

ReaWwise then looks at the hierarchy configured in the Hierarchy Mapping Table (in the Wwise Structures section), along with the configured Import Destination, to build the Wwise object path for the given audio asset.

With this quick tour, you have seen how easy ReaWwise makes moving assets from REAPER to Wwise, as well as how simple it is to configure a Wwise object structure that makes sense for your REAPER session. We look forward to you using ReaWwise to simplify your workflow!

Andrew has been working as software developer building tools for content creators for the last 8 years. He is passionate about software and music production. He was a developer at Audiokinetic in 2021-2023, working as one of the main developers on ReaWwise.

This is fantastic! Thank you to everyone on the team who made this for the game audio community!I tried this out today and noticed the preview stops updating if I change the source type in Reaper. It previews fine with the render at first, but if I go from Items to Regions, or any other change like that, the preview gets stuck on the original type.A temporary fix is to click "dry run output" then quickly cancel. This gets the preview to update to the proper asset list of items, or regions, or whatever else the Reaper render is set to.Mentioning it in case others run into that snag and in hopes that gets fixed up :)

What best describes you? What best describes you? Audio DirectorSound DesignerAudio ProgrammerAudio EngineerRecording EngineerAudio Integration SpecialistComposerProducer / DirectorCEO / Studio DirectorLead Software EngineerSoftware EngineerGame DesignerStudent / InternTeacherITOther

Fran, I was wondering what combination would be the shortest route to a decent audio to use with the flip (or other) video. A good condenser mic recorded into a tascam with memory card, or similar gear? What would you recommend for someone to do for good, rather than top shelf youtube video. I am thinking about borrowing a friend Canon Vixia camera but do not know what quality audio it will have. Any thoughts? Thanks in advance for your opinion. ?

This looks awesome, thanks so much for the tutorial, I used to have cyberlink

power director, which is not bad, I purchased the Q3 from zoom audio is good

but the video is dark, even then you are stuck with the X/Y mics,

This makes me think more about doing it the right way.

I had been pouring over miles of clips trying to get a decent editor

and started getting some results with command line ffmpeg,

and I had the idea what if they wrapped a nice GUI around the FFMPEG libraries?

that would be the shizzle! gotta love the Internet, if you can think of it

someone already may have done the work for you.

Steve, I was kind of in the same place you describe, although I gave up trying to hack things together with FFMPEG and Avidemux and other free tools and resorted to buying Edius Neo. But I still use REAPER to look through long clips and identify the stuff I want to keep.

Initially, I rendered using exactly the same settings you used in your video. However, I found I ended up with some artefacts on the audio. So I switched the audio output to PCM and rendered at full CD quality. This obviously slightly increased the overall file size, but dramatically improved the audio quality.

Hey, I just tried the Zi8 into REAPER and with Microsoft Security Essentials active REAPER locked up. I had to turn off real-time protection to be able to load the Zi8 file into REAPER. So perhaps try turning off your virus protection just to see if that helps? Turn it back on, of course, before you go net-surfing.

p.s. I play drum. I have to say the only complaint I have with Q3HD is the low-end. The bass drum volume is relatively low. I suspect the tiny mics have inherent limitations in picking up low-end sounds. But you are definitely right. The distance makes a big difference.

I just bought a Kodak Playtouch and planned to use it with my Zoom H1. Unfortuantely the background noise and the horrible pumping compression mean that it is still best to sync audio and video later as most other folk have found out also.

I just did my first test record and imported the mp4 (1080p) into Reaper (with updated FFMPEG libraries) and managed to sync everything but I seem to be struggling to retain the smoothness of the video. I cannot find how to render as an MP4, only .mov files, AVI and WMV files. I have tried quite a few settings including 6000Kbps .mov 16bit pcm and when I compare my original with the rendered version the rendered version is always a little jerky and not as smooth.

I shall try rendering down to 720p, or did you mean capture it on the Kodak in 720p? I have had the bit rate up to 10000 as the highest without any luck. The video just looks a little slow and a bit jerky compared to the original.

I do usually choose 720/30 because the file seems easier to process. REAPER video has continued to improve, though, so your 720/60 should work. I do my audio at 44.1/16, normal CD spec, and REAPER has no trouble syncing or rendering.

.MOV files are not decoded by FFmpeg as a rule. Pull the file into REAPER then right-click Source Properties (or Ctrl-F2). This will tell you how the video is being decoded. .MOV files are usually decoded by QuickTime rather than FFmpeg.

Currently you have JavaScript disabled. In order to post comments, please make sure JavaScript and Cookies are enabled, and reload the page. Click here for instructions on how to enable JavaScript in your browser.

My recording philosophy is pragmatic, skeptical, not super critical. After all, the performance is by far the most important component of a track, and every aspect of any recording is a matter of taste.

Two things that did seem to lead to better recordings were experience and room treatment. Getting an appealing sound is the combination of many small details, and learning those details only comes from experience. Amd the sound of the recording space is obviously a big factor.

When I play the file with VLC, there is no black frame. But when I play it in Quicktime, there is. I think the problem must be in the player and not in the video file, potentially a Quicktime glitch with the H264 codec.

If you tend to use the Playhead for marking an Out point in a range, you will add a frame of black. To avoid it: after the last clip in the sequence, move left one frame and then mark Out. You are including one frame of black by not doing so. You now have an export without the black frame.

Now this is where things get interesting. The more I play with my export settings, I'm finding this only happens when I export with as H264. If I export as Quicktime, but with an H264 codec, it's fine.

If the playhead is involved in setting the Out point at the end of any clip, instead of marking Out, move left one frame, then mark Out, then Export. The playhead is not a "needle" It has a head and tail. It also has a duration of 1 frame. If you snap to the end of the clip and mark Out, the tall of it is touching black; the head of the frame hovers over your last visual. That is why you must move back before marking Out.

3a8082e126