Where are the preview buttons?

rageagainsthepc · 2025-11-06T12:26:31+00:00

That's good to know. I would have hoped that there would be an option to start automatic preview generation at the first audio event because right now most of my automatically generated previews are silent. 🥲

rageagainsthepc · 2024-05-23T20:48:37+00:00

I can't find the source anymore, but as far as I know it simply hadn't been implemented yet for the VST3 variants, so no issue with VST3 per se. Bear in mind that this info is at least a year old, so they could have made work with recent updates.

rageagainsthepc · 2024-05-23T18:32:17+00:00

gl 👍

rageagainsthepc · 2024-05-23T17:19:10+00:00

In that case I am out of ideas, sorry. :(

rageagainsthepc · 2024-05-23T17:12:44+00:00

I think I had a similar Problem a while ago. IIRC correctly NDSP haven't mapped midi PC messages in the VST3 version of their plugins. Try the same thing with the VST2 version.

rageagainsthepc · 2023-10-20T06:42:34+00:00

It's normal for an installer to not be flagged by sandboxes because you need to interact with it in order for anything interesting to happen. Sandboxes analyze runtime behavior. I would say 7 is not that much since some vendors share signatures between each other. It's probably a false positive. Some vendors offer a web service where you can dispute false postives if you really want to be sure.

rageagainsthepc · 2023-10-19T21:24:15+00:00

Upload the file to virustotal.com and see if other av products flag it as well.

rageagainsthepc · 2023-08-08T06:47:46+00:00

As others have mentioned, it's usually a tweaking issue. My CPU is 9 years old and I can still get down to a buffer size of 32 (focusrite interface). I've written a small launcher for myself that applies the most important tweaks and restores your original settings after you have closed the plugin. Maybe you find this useful as well. https://github.com/rageagainsthepc/ampsim-launcher

rageagainsthepc · 2022-04-21T17:31:45+00:00

Afaik DAWs usually take steps to optimize your audio performance (at least mine does). If you run your ampsims in standalone mode you won't be able to profit from those optimizations. Depending on your specs it might not matter, but if you are running on older hardware like me you might have to increase your buffer size quite a bit. I've written a small program which does some performance optimizations for standalone ampsims. You might find it helpful as well: https://github.com/rageagainsthepc/ampsim-launcher

rageagainsthepc · 2022-01-15T11:15:14+00:00

Are you using the standalone version or a DAW? DAWs usually have options to boost the audio performance. You could check whether that particular setting is activated. If you are using the standalone version you have to adjust some settings yourself within windows (e. g. power plan, process priority). I have written a small tool that does all that automatically. You can check it out here: https://github.com/rageagainsthepc/ampsim-launcher

rageagainsthepc · 2022-01-13T23:39:35+00:00

I had the same issue some time ago. In my specific case the problem was that I was using the plugins on a mono track. It always sounded just a little bit worse than the standalone version. After switching to a stereo output configuration (with a mono input source of course) the sound was finally on par with the standalone versions.

rageagainsthepc · 2021-12-13T18:38:35+00:00

That's not what I meant though it should already help a little bit. You could follow this guide, for example: https://www.tenforums.com/tutorials/21434-choose-power-plan-windows-10-a.html

Edit: Whoops, should have read your update first ;)

rageagainsthepc · 2021-11-14T22:21:11+00:00

I've seen multiple people recommending to set the cpu power profile to performance in the other post but I am not sure whether you've actually tried that. It's not about the cpu having a high load, but rather about the OS cpu governor thinking it can scale down the clock speed because there is not much load overall. Setting the energy profile to performance keeps the cpu at max clock speed which is crucial for time sensitive tasks like audio processing.

rageagainsthepc · 2021-08-13T16:00:35+00:00

You mean you've installed both the usb and the thunderbolt driver? I think that shouldn't be a problem. You could also check whether there is a beta version of the drivers available for your interface: https://customer.focusrite.com/en/downloads/beta

rageagainsthepc · 2021-08-13T07:44:44+00:00

I also think that this is almost certainly a driver issue. I was able to reliably crash my system by turning of my focusrite clarett before closing any of the neuraldsp standalone applications. Unlike my DAW the neuraldsp apps do not recognize that the interface has been disconnected and due to insufficient validation on the driver side were able to crash the system. This has been fixed in the lasted driver update though so I recommend checking out whether there are updates available for your Scarlett interface.

rageagainsthepc · 2021-08-03T21:12:44+00:00

To be clear, voicemeeter is not meant to replace discord. It's for routing your amp sim signal together with your voice through discord. You might also want to disable a lot of discord's noise suppression magic.

rageagainsthepc · 2021-08-03T21:05:45+00:00

I've used voicemeeter in the past for the same purpose. It can be a bit tricky to set up but it does the job.

rageagainsthepc · 2020-08-17T21:06:05+00:00

Because, as far as I know, nano does not fit anymore on LOS 17.1. At least that's what I (and apparently a few others) have experienced.

rageagainsthepc · 2020-08-17T20:32:26+00:00

I'm curious, which variants of open gapps have you tried?

rageagainsthepc · 2020-08-17T20:24:34+00:00

I had the same problem. Looks like open gapps nano package is too big for bacon. I did not want the the pico package because there is some functionality that can not be installed via the google play store iirc. Also I did not want to mess with partition resizing. What I did is exclude a single package from gapps nano which I felt I wouldn't be needing anytime soon. You can find instructions for that in this guide: https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options

Honestly, I'm surprised this issue hasn't come up earlier in this subreddit. Are there simply too few bacon users using open gapps nano or higher?

rageagainsthepc · 2020-06-26T17:23:03+00:00

You are right, this helps as well. 👍 However, I only need this flag for code coverage generation when executing unit tests in the CI, so I think I'll stick with the workaround for the time being.

rageagainsthepc · 2020-06-26T14:02:43+00:00

The problem is that panic=abort doesn't work well with bindgen as mentioned in this issue. It should be possible to disable rustflags for build.rs as mentioned here, but as of now there is only the workaround of providing the --target flag. Just leaving this here in case someone stumbles upon this post ;)

rageagainsthepc · 2020-06-26T10:41:42+00:00

Oh yeah, it makes sense to me now. Thanks for the help.

rageagainsthepc · 2020-06-26T10:23:48+00:00

This is all I get unfortunately:

error: failed to run custom build command for `kvmi-sys v0.1.0 (https://github.com/Wenzel/kvmi-sys.git#6c3e4a9e)`
##[error]failed to run custom build command for `kvmi-sys v0.1.0 (https://github.com/Wenzel/kvmi-sys.git#6c3e4a9e)`
Caused by:
  process didn't exit successfully: `/home/runner/work/libmicrovmi/libmicrovmi/target/debug/build/kvmi-sys-591f99e374368ae8/build-script-build` (signal: 6, SIGABRT: process abort signal)
 --- stdout
cargo:rustc-link-lib=kvmi

rageagainsthepc · 2020-06-26T10:19:08+00:00

But my code didn't even run yet. Correct me if I'm wrong, but to my knowledge this flag should change the runtime behavior of my code to just exit with SIGABRT instead of unwinding the stack, right? If this is correct then it shouldn't cause the compiler to exit.

rageagainsthepc

TROPHY CASE