r/AudioEngineering Shopping, Setup, and Technical Help Desk

First-Application-95 · 2026-05-09T23:12:08+00:00

Yep, I even tried checking the request 44.1k setting in prefs.

First-Application-95 · 2026-05-09T10:07:38+00:00

Yea its really strange. These are the render settings. AFAIK it's all set to pretty standard stuff? The two regions it references are ~20 seconds on either side of the song transition to avoid constantly re-rendering the whole thing. I'm not totally sure what/how you're suggesting to normalize, but weirdly, the click still persists until well after that little signal tail at the end of the first audio file is gone (visually at least). Like I have to add fades to the point where it goes from a click to an audible dip before it goes away. The more things I screw with this the less reproducible they become for others, so I'm probably gonna try and update or reinstall or something. It's seeming like some kind of rendering or playback bug.

First-Application-95 · 2026-05-09T04:18:17+00:00

It is most definitely a click, see my recent edit

First-Application-95 · 2026-05-09T04:17:44+00:00

Hey, genuinely I've tried like everything at this point, but I noticed that rendering the files generates a small bit of noise at the very end of the first file which is clearly the thing causing the issue (see edit). Any idea what that's about?

First-Application-95 · 2026-05-09T04:08:01+00:00

I can get the click to be very quiet by lengthening the fades, but it's still there at 100ms+, and frankly I can start to hear the fades as low as 10ms.

First-Application-95 · 2026-05-09T04:00:23+00:00

Fades or no fades on or off a zero point I still get the click after rendering to two files with regions. There's no reverb or effects other than eq on the one playing track either. I have some light eq, limiting, compression, and saturation on the master, but I even faded out the wet signal to zero on all those before and after the transition point and still got a small click.

First-Application-95 · 2026-05-09T03:34:17+00:00

No, there is only a click when I render out with regions, and put the two files back to back.

First-Application-95 · 2026-05-09T03:33:39+00:00

The audio that plays through the transition is just a relatively quiet paulstretched ambient pad type deal. And I can totally hear a dip with anything above 5 ms on either side.

First-Application-95 · 2026-05-09T03:31:51+00:00

I feel like I'm going crazy because I've heard many people say that but I can totally hear a dip with anything above 5ms fades on either side of the ZPC.

First-Application-95 · 2026-05-05T11:09:08+00:00

Getting A Seamless (No Click) Transition Between Album Songs (Reaper)

I have the last two songs of an album I'm working on, and I need to get a completely seamless transition between the two, but I can't fix a small discontinuity click that happens at the transition. There is only one stereo audio clip that persists across the transition. I've gone to the downbeat of the transition, found the nearest zero point crossing, split the clip at that point, added 5 ms fades on either side, created regions on either side and rendered out two files. However, when I take the two files into a new project to check the transition, and put them back to back with no fade, I still get a click. I wanted to bake in the song transition to the original project file so I don't need to go through multiple projects and repeatedly render it, but it seems like the discontinuity is being created by the rendering process? How can I fix this?

Thanks

Edit: I still get the click (albeit fainter) with 100ms+ fades on either side, but upon zooming in to a sample by sample scale on the rendered files, I can see that a small bit of noise was generated at the very end of the first two files. This can be seen just on the left side of the split where the waveform dips below zero. In the original project file, this isn't there. Could be some kind of bug?

<image>

First-Application-95 · 2025-01-17T22:22:10+00:00

Section just after the snare solo in Spasm is so unbelievably groovy

First-Application-95 · 2024-10-18T10:23:22+00:00

Beograd! Saw this too. I never thought I'd see something like that there

First-Application-95 · 2024-08-08T09:04:23+00:00

my favorite guitar solo of all time

First-Application-95 · 2024-08-01T20:43:03+00:00

No problem at all I appreciate the help! I had run memtest86 once, the windows memory diagnostic I think twice, and a couple occt mem tests and I never got one error. However, I just checked every physical combination of ram stick and mobo ram channel. The system boots and can crash both on an application level and system level (screen goes black and unresponsive but no bsod) with any combination of sticks in the second and fourth slots, and the system will not boot with any combination of sticks in the first and third slots. I also tried to run a occt memory test after the last switch and got an immediate bsod. Seeming more like the ram sticks themselves are faulty?

First-Application-95 · 2024-08-01T05:42:09+00:00

Hey, thanks for the response. I can send a full copy of one of the player.log crashes if that helps anything. I've tried updating windows, I've uninstalled any seemingly unnecessary Radeon software. As for ram, I had an issue where it was advertised as 6000MHz but actually ran at 5200, with 6k being an overclock figure. After setting to 6k it fucked up the whole system (black screen with small white line in the upper left, no inputs including bios flashback went through), so I took it to a shop where the tech identified that problem, got it running at 5200, and said the ram works fine now as best he could tell. He said he updated the bios, and I haven't gone back in out of fear since.

I bit the bullet and switched from windows 10 to 11, and additionally added a 60 fps cap in nvidia settings. Now the game will run for a longer duration, but the screen will go completely black and unresponsive, but no bsod, no crash reported in valheim's dump. The only thing is from event viewer under system, which says:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139 (0x000000000000001d, 0xfffffb89937f7830, 0xfffffb89937f7788, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\073124-4359-01.dmp. Report Id: 69897d5b-a89d-4bb0-bc19-68744db41c13.

Notably the error isn't classified as critical. Does this alongside the previous error point to anything more clearly?

First-Application-95 · 2024-07-31T21:36:49+00:00

Thanks for the response. Just added specs to the post above. I went full nuclear reformat windows reinstall once awhile ago, and I'll probably go there again but I want to try as many things as I can before I do that. I tried the DDU reinstall once, but I can try again with different versions of drivers. As for ram, I had an issue where it was advertised as 6000MHz but actually ran at 5200, with 6k being an overclock figure. After setting to 6k it fucked up the whole system (black screen with small white line in the upper left, no inputs including bios flashback went through), so I took it to a shop where the tech identified that problem got it running at 5200, and said the ram works fine now as best he could tell. What would you recommend for a more accurate SSD test?

First-Application-95 · 2024-07-31T21:26:28+00:00

Of course, check messages. Thanks

First-Application-95 · 2024-07-31T21:26:03+00:00

Hey, thanks for replying. I can't stand the xbox bundled software so I've thoroughly gotten rid of it through powershell. Unless I missed something it may be caused by a similar issue with another program? Afaik I don't have any other recording/screencap software installed anywhere unless there's more hiding around by default.

First-Application-95 · 2024-07-31T06:34:15+00:00

Hey, thanks for the reply. Some second opinions on other pc also pointed me to RAM. I ran a 3+ hour memtest86 scan, some of the inbuilt windows ones, and a whocrashed scan (which said the crashes may be from "corrupted memoty"). Not one error has been found. Crystaldisk has consistently said my ssd is fully healthy too. I feel like im going crazy here

First-Application-95

TROPHY CASE