When playing a FLAC file of Christy Moore's Ride On, I experienced a noticeable increase in resolution. I've heard that Kernel streaming was a thing, and noticed that it was an output option in JRiver. Foobar has been my main FLAC player, but 90% of my listening happens on Spotify Premium out of convenience. This might be an option if using Jack as a virtual patchbay to switch between PA and the app(s) but it's not exactly user-friendly.I recently downloaded JRiver based on recommendation on the PS Audio site in an attempt to gain a little insight on my gear and see if the way I've been hearing it is the best it can sound. You can also create a pair of virtual interfaces with alsaloop. You can create other devices in asoundrc, but I _think_ that has the same limitation on simultaneous connections as the underlying device. I am interested in a better option, but haven't put the time into finding it yet. I'm using it as I have squeezelite as a system level daemon, but firefox demands PA and doesn't work with apulse, and the speakers on this system aren't good enough to worry so much about quality. In my experience it also causes sync problems with PA after apps using it have been playing for a while. You can use ALSA's dmix interface if you want to have multiple things connecting to the ALSA device, but that just resamples to a fixed rate, mixing the sources as the name implies, so I don't think it's what you want. Apps can connect to the ALSA interface directly, or to PA which in turn connects to the ALSA interface, or to Jack which sits in a similar position to PA. Given the false impression that the topic of achieving quality audio playback onĬlick to expand.Just to be clear on the layers here, ALSA provides the logical interface to the sound card. I just wanted to summarize because some users new to GNU/Linux might be Make it convenient to select the desired audio sink.Īppologies for stating the obvious and repeating what others have already said. The only complexity is curating a list of favored audio players that Output is directed at some audio sink other than the one used for critical Let PulseAudio continue to be the default audio muxerįor system sounds and other applications. So, I find the simple solution is to use a player that is ALSA friendly. On which I'm typing this message shows "pulse" and "default" as selectableĪLSA devices that are in fact audio inputs to PulseAudio. It is important to note that PulseAudio does The audio player with which I am performing critical listening goes directly to Or if you prefer, a default graveyard for all audio sources that I don't want to hear.
Basically using PulseAudio in a manner analogous to /dev/null, I then either lower the volume or mute PulseAudio and its currentĪudio sink. PulseAudio with its output directed at an audio sink that I do not use for critical What I do is let all of the usual audio sourcesįlow into the PulseAudio audio bus, as is largely done by default. Then DeadBeef, with a few others auditioned at the transitional junctures. There are several discussed in this topic thread. What I've been doing for quite a few years is using audio players that provideįor the ability to send the audio output directly to the DAC via ALSA, bypassing Fortunately, there's no reason to do this. Thus removing PulseAudio pretty much means gutting some of theĭesktop environments. Implement a given desktop environment often list PulseAudio as a dependent
#Cocina audio bitperfect software
On the distributions I've tried, many of the software packages that collectively One audio source to the exclusion of all others. When performing critical listening, it is almost invariably precisely PulseAudio does its job well, which is to mux a multitude of audio sources PulseAudio in order to achieve bit perfect playback.
I have seen some posts on other forums suggesting the complete removal of
One is the relatively recent addition of theĪvoid_resampling configuration option of PulseAudio. I've learned a few new thingsĪs a result of your generosity.
I wanted to thank the contributors to this thread.
0 kommentar(er)
