by Discovery » 22 Jan 2017, 11:14
by pietpara » 22 Jan 2017, 12:30
by Discovery » 22 Jan 2017, 12:37
by hondagx35 » 22 Jan 2017, 12:45
If 'performance' means setting CPU to max frequency, then how does this play with the settings suggested by Archimago, underclocking the ARM to reduce jitter,
And then with top I see mpd running on CPU3, but cpu usage is nearly 0.0. I mean that in the process list I see mpd using around 1.6%, but in the cpu list at the top cpu3 remains showing 0.0/0.0 almost all the time.
3) I noticed that Rune frost removed the 'taskset' command dynobot mentions in from the 'common startup' section to assign MPD to a core. Why? And Frank's example places it in the mpd.service file in stead of in the audio profile. Which is better?
The audio profile is the more flexible solution (can be disabled by switching profiles).
by pietpara » 22 Jan 2017, 13:26
by s.k. » 22 Jan 2017, 14:06
by Discovery » 22 Jan 2017, 14:19
by s.k. » 22 Jan 2017, 15:03
by Discovery » 22 Jan 2017, 15:13
by ianhaynes » 22 Jan 2017, 15:28
force_turbo=0
initial_turbo=60
arm_freq=700
sdram_freq=350
core_freq=350
gpu_freq=300
over_voltage=-4
sdram_over_voltage=-4
gpu_mem=16
# HDMI disable
hdmi_blanking=2
support RuneAudio