|
Room correction with convolution per sample rate
|
|
31-12-2018, 23:16
Post: #32
|
|||
|
|||
|
RE: Room correction with convolution per sample rate
I was able to successfully install "minimstreamer-0.7.10.2."
After restarting the server, the verbose log files indicated: Quote:Convolution file for sample rate 352800 is /mnt/disk1/share/MinimServer/convolution/Cor1S352.wav I tried the following settings: Quote:stream.options: Flac files at 16/44, 24/88, 24/96, 24/176, 24/192, 24/352, 24/384 - performed the convolution, and played without problem (except for the Melco stuttering at 24/352 and 24/384). Flac files at 24./48 still had the error "Converter program ended unexpectedly with exit value 139". I realize you haven't got to this yet. I was able to play a (DSD64) .dsf track, but no convolution operations were performed (the "verbose" logs did not indicate anything, and my DAC reported a DSD file). No problem with the Melco processor serving up unprocessed the DSD file. This is good - if the user does not want to perform any convolution operations on DSD files, then none are performed. Changing stream.transcode to: Quote:flac:wav;, dsf:wav24;352 The same .dsf track played - with stutter (the Melco processor can't transcode in real-time at 352 KHz and above). My DAC also indicated 24/352 KHz track, and the log files showed: Quote:Using convolution file /mnt/disk1/share/MinimServer/convolution/Cor1S352.wav for sample rate 352800 Changing stream.transcode to: Quote:flac:wav;, dsf:wav24;176 The same .dsf track played - still with stutter. My DAC now indicated 24/176 KHz track, while the log files showed: Quote:Using convolution file /mnt/disk1/share/MinimServer/convolution/Cor1S352.wav for sample rate 352800 Odd that the DAC and MinimStreamer disagree on the sample rate - but fortunately no errors were reported (unlike with minimstreamer-0.7.10.1). Maybe I'm doing something wrong. On a related topic: Would it be possible to add a flag to not perform any convolution if there is not a file for the exact sample rate being played? Applying a convolution file of the wrong sample rate may degrade the sound (In JRiver, if there is no convolution file with the same sample rate as the track being played, JRiver resamples the convolution file on the fly - see Automatic Resampling, and this discussion). This also has the advantage that the user can decide what sample rates to perform the convolution on. For me, using the Melco server, I could remove all convolution files for 352 KHz and 384 KHz (the sample rates at which the Melco processor stutters). |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)

Search
Member List
Calendar
Help



