|
|
Post by Guitar on Jan 27, 2022 18:17:23 GMT -6
Just following along. I have some ideas about the windows media player. There's a foobar2000 configuration that I really like. But I don't want to set up any wild goose chases, with any suspicions that psychology might be at play here.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Sept 11, 2023 20:55:38 GMT -6
Render online in real time to 24-bit audio with your monitoring dither. The same format most of your interfaces and digital to analog converters are receiving. It’s the only way to make sure what you print is exactly what you hear. Full speed rendering can cause some plugins to misfire including some great limiters. There were some errant peaks in full speed that they were smashing down in online renders. A single misfiring time based plugin in a big session can cause major clarity issues too so you should also freeze and bounce in real-time.
|
|
|
|
Post by the other mark williams on Sept 11, 2023 23:09:23 GMT -6
I’d forgotten all about this thread. Whatever happened here, teejay? |
|
|
|
Post by copperx on Sept 11, 2023 23:29:33 GMT -6
I'm going to go back and state that there is no reason to be doing all the fancy stuff people are suggesting. Reaper should not be outputting something that sounds different than what your monitoring is telling you. I've been working in Reaper since 2006 and I have only come across the "sounds different when rendered" once and it was a setting of some kind that unfortunately I don't remember. Lets not get TeeJay off on tangents here. If the rendered track is different enough to be easily heard, then its not a matter of whether the stock dither is good enough or not, or whatever. It's either a routing issue, or a rendering setting of some type. TeeJay, do you think you can post the files so myself and/or others can take a look and render out on our systems to see if we have the same issues? Also, you might try freezing the tracks that have effects on them and then rendering to see if render is having trouble with one or more plugins. I agree. While I have experienced different rendered sound in other DAWs, the only two times it happened to me in Reaper were problems with the sample rate. 1) I once froze a bunch of tracks, then reopened the project with a different sample rate (Reaper was doing realtime resampling). The output sounded different, and I thought I was going crazy until I realized my error. 2) In another instance, I was rendering the audio at a higher sample rate because of saved render settings, which meant that plugins were running at a different sample rate at render time. The Reaper developers have said that there's no reason fon a render to sound different than what is being monitored, because the audio that goes to disk at render time is the same data that goes to the interface. Plugins in some cases have different settings for rendering. If you have such plugins, make sure the settings are right. Also, make sure the render settings are correct. The render window has many options. |
|
|
|
Post by christopher on Sept 12, 2023 0:01:34 GMT -6
The one thing that slaps me across the face every session in Reaper is panning laws. I set it for 4.5db I think? It does waste a lot of my time. Every stereo source will be quieter. Anytime I make a subgroup, track folder, or import a stereo track first thing is right click on the pan and select 0.0dB, so I can get full scale. This should be an easy fix for them, I haven’t updated lately but last year it was still an issue. Constant issue. I love pan laws though, so I just deal. Just throwing that out there, as loudness is the easiest to screw our perceptions. I doubt this was the issue, probably sample rates offline etc
|
|
|
|
Post by copperx on Sept 12, 2023 0:39:05 GMT -6
The one thing that slaps me across the face every session in Reaper is panning laws. I set it for 4.5db I think? It does waste a lot of my time. Every stereo source will be quieter. Anytime I make a subgroup, track folder, or import a stereo track first thing is right click on the pan and select 0.0dB, so I can get full scale. This should be an easy fix for them, I haven’t updated lately but last year it was still an issue. Constant issue. I love pan laws though, so I just deal. Just throwing that out there, as loudness is the easiest to screw our perceptions. I doubt this was the issue, probably sample rates offline etc This shouldn't be a issue, as far as I know. Pan settings are set in the project settings, and you can have default project settings so that you don't have to manually change the pan law for every new project. Or maybe I'm misunderstanding the issue. |
|
|
|
Post by svart on Sept 12, 2023 6:53:13 GMT -6
The one thing that slaps me across the face every session in Reaper is panning laws. I set it for 4.5db I think? It does waste a lot of my time. Every stereo source will be quieter. Anytime I make a subgroup, track folder, or import a stereo track first thing is right click on the pan and select 0.0dB, so I can get full scale. This should be an easy fix for them, I haven’t updated lately but last year it was still an issue. Constant issue. I love pan laws though, so I just deal. Just throwing that out there, as loudness is the easiest to screw our perceptions. I doubt this was the issue, probably sample rates offline etc Never noticed. I just pan and adjust as needed. |
|
|
|
Post by christopher on Sept 12, 2023 8:47:24 GMT -6
I changed the default to 4.5 dB, I like it a lot. Supposedly that’s SSL law iirc? Anyway. I think that means center panned is -4.5dB. Reaper at least 2021 pans stereo channels center and reduces volume at whatever the pan law is. Other DAWs don’t do this way. So I manually adjust the stereo channels. Really it’s only an issue if I’m trying to keep a mix the same and organizing into folders, or importing references / checking rendered stereo mixdowns.
|
|
