Hi, I got the idea from somewhere that Zynthian supports 88.2k, but do not see it on the menu in webconfig (running Oram). Is there any way to run at 88.2k in Oram (or any other version)?
It should be possible to run zynthian at any sample rate that the soundcard supports by setting the jackd options, e.g.-r 88200. Does your soundcard support this rate?
Why do you want to run at this rate? Zynthian and its component parts, including engines are optimised for 48000 fps. You are likely to see a reduction in the capability and quality by running higher than 48000 fps.
Hmm, if I change the jackd line in webconfig and try to save it, my -r 88200 edit just gets replaced with whichever of the 4 options was on the spin control (32, 44.1, 48, 96).
I have usb interfaces that do 88.2, but I think the card in my Zynthian v5 supports it, going by this: Handling non-standard sample rates – HiFiBerry
I want to reduce aliasing, on a multiple of 44.1kHz, for cleanest conversion back to cd format.
If sound design for the Zynthian was generally done through a 48k path, I certainly appreciate that no other rate will be as faithful to what the sound designers were hearing. But if you were thinking of any other potential quality reduction, can you elaborate?
Hi, I suggest you don’t overlook the considerable added processing pressure, exerted on the not-so-muscular Raspberry CPU by almost doubling the reference sample/duty cycle rate.
Lest not forget that, however brilliantly optimised, the whole Zynthian system is generating and mixing in real-time several stereo audio channels. There are various audio post-processing tools available, for adequate 48 Khz to 44.1 Khz conversion with minimal aliasing, probably hard (if not impossible) to detect at a subjective perceptual level.
Due to a whole series of sound technical and mathematical reasons, most contemporary digital audio devices are designed around a 48 Khz (or 96/192, processing power allowing) data pipeline, and I think that it’s generally wise to stick to this by now widespread standard.
Cheers
Some valid points there, but capacity halving is OK for this use case and I meant reduction of aliasing inherent in operation of a synth engine (by doubling the bandwidth), rather than file conversion. Anyway, Grok kindly indicated which file to edit and I’m pleased with the results.
2 Likes
So which file did you have to edit?
Here’s what it said:
"You can edit the config file manually:
# SSH into Zynthian first
ssh root@zynthian.local
# Edit the settings
nano /zynthian/config/zynthian_envars.sh”
As riban suggested, I substituted “-r 88200" for "-r 48000". Would be easier if the spin control didn't override my advanced edit in webconfig, but wasn't hard in the end.
1 Like