<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Modartt user forum - latency spike]]></title>
		<link>https://forum.modartt.com/viewtopic.php?id=5463</link>
		<description><![CDATA[The most recent posts in latency spike.]]></description>
		<lastBuildDate>Sun, 07 Jan 2018 07:59:48 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: latency spike]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=952223#p952223</link>
			<description><![CDATA[<p>Running a web browser in the background and doing audio processing with intention of low latency is never a good thing. You should try disabling the network on Surface if you wanna run Pianoteq without hitches (like completely, disable device in Device Manager).</p>]]></description>
			<author><![CDATA[null@example.com (EvilDragon)]]></author>
			<pubDate>Sun, 07 Jan 2018 07:59:48 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=952223#p952223</guid>
		</item>
		<item>
			<title><![CDATA[Re: latency spike]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=952218#p952218</link>
			<description><![CDATA[<p>I had been having trouble getting low latencies with Pianoteq while avoiding snaps and crackles on my window surface Pro 4, especially when I am running a web browser or some other program in the background. Up until this change that I made listed below, I had been stuck at running at 29 KHz for sampling, and keeping a fairly large buffer, such as 384. Anything below this would cause pauses, pops, and crackles. Even just setting the battery to &quot;high&quot; did not make that much improvement.</p><p>I then watched sections of a video on a website called Surface Pro Audio, and made the changes that he suggests:</p><p><a href="http://surfaceproaudio.com/surface-pro-2017-audio-performance-reliability-music-production/">http://surfaceproaudio.com/surface-pro-...roduction/</a></p><p>This is a fairly long video, but thankfully, it comes with a table of contents. The heart of the matter starts at seven minutes 37 seconds under &quot;tweaking windows&quot;. He gives some changes to the power settings, and other changes that are only possible after making a modification in the Windows registry.</p><p>After I did what he said, I found a significant improvement. I am now able to run Pianoteq at 48 kHz with a buffer of only 64. Even with the sustain pedal held down, and a five-microphone instrument preset, I rarely push past 40% of the processor as seen on the graph of the performance section of the Pianoteq options. For me, this is fantastic (and I am convinced that it even sounds better and more musical and realistic than what I was getting with the sampling frequency of only 29 kHz – whether it makes any difference to do 44 kHz or 48 kHz is debatable, as CD-quality audio sounds pretty darn good to me, but I was in fact able to push Pianoteq up to 48 kHz without any problems). So far, I have heard no snaps, no pops, and no crackles.</p>]]></description>
			<author><![CDATA[null@example.com (dklein)]]></author>
			<pubDate>Sun, 07 Jan 2018 01:23:06 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=952218#p952218</guid>
		</item>
		<item>
			<title><![CDATA[latency spike]]></title>
			<link>https://forum.modartt.com/viewtopic.php?pid=952209#p952209</link>
			<description><![CDATA[<p>Greetings everyone,</p><p>I just purchased Pianoteq 6 and it sounds great and works fine ( = no latency) most of the time, but when I&#039;m playing a lot of notes at the same time I sometimes have latency spikes - it is especially noticable on the right hand chords (is it the proper english word?) of the chopin etude 12. </p><p>I&#039;m using ASIO4ALL with either the motherboard soundcard or also one in my GPU, with no differences. I tried different buffer sizes (currently 64 samples), different sampling frequencies, enables/disables multicore processing, to no avail. I have a i5-7400 so&nbsp; I don&#039;t think that&#039;s the problem (it&#039;s never used at 100% anyway). <br />Any ideas? Could it be my keyboard who is at fault here? I have a Casio privia Px-135</p><p>Cheers,<br />gus</p>]]></description>
			<author><![CDATA[null@example.com (gus)]]></author>
			<pubDate>Sat, 06 Jan 2018 20:14:07 +0000</pubDate>
			<guid>https://forum.modartt.com/viewtopic.php?pid=952209#p952209</guid>
		</item>
	</channel>
</rss>
