<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>DataLooper | TenType | Activity</title>
	<link>https://www.datalooperpedal.com/members/tentype/activity/</link>
	<atom:link href="https://www.datalooperpedal.com/members/tentype/activity/feed/" rel="self" type="application/rss+xml" />
	<description>Activity feed for TenType.</description>
	<lastBuildDate>Thu, 12 Mar 2026 15:35:55 +0000</lastBuildDate>
	<generator>https://buddypress.org/?v=10.3.0</generator>
	<language>en-US</language>
	<ttl>30</ttl>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>2</sy:updateFrequency>
	
						<item>
				<guid isPermaLink="false">c43a2ab576d7e6b65114018b05eb1e5a</guid>
				<title>TenType replied to the topic DataLooper and Push 2 - *MIDI* clip looping issues in the forum Bugs/Issues</title>
				<link>https://datalooperpedal.com/forums/topic/datalooper-and-push-2-midi-clip-looping-issues/#post-13649</link>
				<pubDate>Fri, 23 Aug 2019 15:36:01 +0000</pubDate>

									<content:encoded><![CDATA[<p>Wondering if any more progress has been made here. I had to set new gear aside for a while to focus on getting some projects completed.</p>
<p>I&#8217;d like to start using the Datalooper, but this issue with it not triggering CL track clip recording when they are the currently selected track by Push 2 makes the Datalooper useless for my current setup.</p>
<p>Also,&hellip;<span class="activity-read-more" id="activity-read-more-299"><a href="https://datalooperpedal.com/forums/topic/datalooper-and-push-2-midi-clip-looping-issues/#post-13649" rel="nofollow ugc">[Read more]</a></span></p>
]]></content:encoded>
				
				
							</item>
					<item>
				<guid isPermaLink="false">dadba8e57d6e8ed771547206284388ca</guid>
				<title>TenType replied to the topic DataLooper and Push 2 - *MIDI* clip looping issues in the forum Bugs/Issues</title>
				<link>https://datalooperpedal.com/forums/topic/datalooper-and-push-2-midi-clip-looping-issues/#post-13413</link>
				<pubDate>Mon, 27 May 2019 18:43:59 +0000</pubDate>

									<content:encoded><![CDATA[<p>Hello? Any ideas? Anyone else use Push too?</p>
]]></content:encoded>
				
				
							</item>
					<item>
				<guid isPermaLink="false">28a6be0738deede022b824dce3363cd0</guid>
				<title>TenType&#039;s profile was updated</title>
				<link>https://www.datalooperpedal.com/activity/p/138/</link>
				<pubDate>Tue, 21 May 2019 19:00:47 +0000</pubDate>

				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">f27bc55d8d80871f2125d93b01fa91ee</guid>
				<title>TenType started the topic DataLooper and Push 2 - *MIDI* clip looping issues in the forum Bugs/Issues</title>
				<link>https://datalooperpedal.com/forums/topic/datalooper-and-push-2-midi-clip-looping-issues/</link>
				<pubDate>Tue, 21 May 2019 18:29:12 +0000</pubDate>

									<content:encoded><![CDATA[<p>So I have the Push 2 controller and I&#8217;m testing the compatibility.</p>
<p>Midi clip recording with CL# tracks has an issue and maybe there&#8217;s a fix I can&#8217;t find.</p>
<p>Currently, the DataLooper will not trigger clip recording on a Midi track if the track is SELECTED. It works fine if the track is an armed Midi track that is not currently selected. This is an&hellip;<span class="activity-read-more" id="activity-read-more-137"><a href="https://datalooperpedal.com/forums/topic/datalooper-and-push-2-midi-clip-looping-issues/" rel="nofollow ugc">[Read more]</a></span></p>
]]></content:encoded>
				
				
							</item>
					<item>
				<guid isPermaLink="false">91defdd74994270fbf61be6a18d9ca69</guid>
				<title>TenType became a registered member</title>
				<link>https://www.datalooperpedal.com/activity/p/112/</link>
				<pubDate>Mon, 06 May 2019 22:36:52 +0000</pubDate>

				
									<slash:comments>0</slash:comments>
				
							</item>
		
	</channel>
</rss>