Hello,
If it is possible, I would rather be interested in what kind of latency will remain on the selected components. You can have a great PC configuration, but the latency for realtime applications is terrible. Linux vs Win is also different. In win11 I have a lot of services turned off so that the audio is clean, in linux it’s ok. If possible, run the PC through the latency monitor.
Yeah on Linux you have to know some things to make a good tuning.
In my experience some machines are great right away. The usual kernels are already good, and sometimes you can get much better performance even with lowlatency/realtime kernels. If you know how, you can just disable anything if it impedes your realtime performance. I know that with a good stock kernel and good machine, you can sometimes already have already sub 10ms latency, and with realtime and tweaked optimal interrupts, pci pro audio cards etc. you can tune some machines to like sub 2ms without xruns as long as the software used allows such insane latency. Then you can even use the machine as realtime effects processor, or for guitar amp modelling without any perceivable lag…!
But there can be individual drawbacks, like graphics card/driver problems, hardware NMI/Interrupt issues, or stuff like that…and then you get xruns when going very low with the latency. This can be real mayhem to debug. I even went as far as doing ftrace through the kernel to see what is the source of what jams up the audio threads/interrups. Some hard drive/file system features are vital to disable on some machines. Or a graphics driver makes problems, and needs to be configured or replaced with an alternative. You’ll see when you try to tune the machine. I’d for example expect a workstation device to be more compliant for realtime work than a consumer or office product, but sometimes you get lucky and the machine works just fine.
Renoise I didn’t manage to drive glitch-free in a stable way I think sub 5-8ms (with jack) depending on machine yet, even when other progs would do it. I guess this is a renoise issue.
Vital tunings:
turn off unnecessary devices and programs, use proper sound card able for low latency
realtime priorities set, using proper realtime audio stack (i.e. jack…)
Disable or tweak CPU frequency scaling, i.e. setting to “performance” mode or disable stepping, is akin to setting performance mode in windows
You may have to disable some file system options like journaling
to get even further, you have to tweak interrupt priorities i.e. via the rtirq init script, and using a lowlatency/realtime kernel would be either prerequisite or even necessary (can’r remember RN) - you need to know the hardware and how to priorize your sound card
if there are still too many failures/xruns, you have to debug it as a kernel/hardware/driver issue, good luck…
I got a new Ryzen 9700X with onboard graphic and have Ubuntu 24.02 installed. Everything fine so far. I can load ~ a factor of 10 (!!!) more instances of Diva now. Maye I have to replace the power supply (be quite) which is sometimes rattling a bit.
However when resizing the spectrum analyzer window in the mixer view quickly the CPU load goes dramatically up and the GUI is becoming sluggish. I observed this meanwhile on 4 machines (AMD and Intel, including the laptop I mention in the first post here. I made another test and the issue is also present) all running Debian or Ubuntu with x11 or Wayland optimized for audio. No difference between Pipewire and Jack.
Could the guys on Linux make a test with the attached project? Go to mixer view. Enable the spectrum analyzer window and quickly change its size while the track is playing. What happens? Is it smooth? In the editor view it behaves ok.
I dont have Linux, the 9700X integrated graphics might be the issue. Either, the processor is still slightly too new for the kernel to have caught up or the graphics struggle rendering something that dynamic while resizing. Pretty sure that it only has 2 compute units in terms of the igpu.
Yes, but I have no issues in other apps like Bitwig, Reaper, etc. I mean isn’t it pretty weird that for a tracker that is supposed to run also on older hardware it struggles with the GUI? You can play games with the iGPU (of course not at high fps). It’s not a big deal, but as I have it on 4 machines other people should also realized this.
This is a lot of software…
Notice you have VST, do you have same issue with Samples only?
Notice you have spectrum analyzer-x2, do you have same issue without that loaded?
Yes, the missing VSTs are not crucial and it’s just the number of tracks, especially group tracks I think. On my new installation it’s also sluggish and I don’t have any VSTs installed yet.
Hey, maybe you have a high resolution display? I believe the spec analyzer is just slow, and when you make it big enough it will lag the system and also whole renoise UI. I had the same on every machine I used, no matter what GFX card. Renoise doesn’t really seem to use accelerated graphics at all, anyways.
Doesn’t matter so much what you use, even on HD displays renoise would lag on big analyzer settings. IDK there once already was a thread on this where other users complained about the behavior. The only solution really is to reduce the analyzer (graphical UI window partition) size.
Then most likely it´s not uncommon. In a new project it feels snappy, but what is what makes at worse is adding more and more group tracks. These can even be empty.
I’m on an AMD machine now (amd ryzen 7 7700) running windows 11 and don’t notice any lag when resizing the spectrum analyser view in your project. I do have a graphics card though (radeon rx 7900 gre) instead of an onboard solution.
I thought you got your PC running again… In Windows it was also a bit sloppy, but only in the mixer view. The 7700x was my first option which had the same price as the 7700. I took the 9700x because of the 65W TDP.
for a minute yes, then all of a sudden it wouldn´t boot up anymore , have tried to a/b the problem myself, but need to bring it for repairs to professionals (I suspect the fsu or a motherboard short). Anywho the upgrade was long overdue + I can do some pc gaming now .
Here’s a very simple with just a bunch of group tracks.
When I change the size of the analyzer window in mixer view it’s sluggish as hell. In editor view it’ s ok. CPU usage is of course close to 0% and you don’t even have to start transport…
It certainly seems that resizing and redrawing the group track area delays the redrawing of the entire UI.
Personally, I don’t see much of a problem with this, but it may be inconvenient for certain use cases.