<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[Modartt user forum - Linux custom suitcase controller - alsa subdevices ignored]]></title>
	<link rel="self" href="https://forum.modartt.com/extern.php?action=feed&amp;tid=1796&amp;type=atom"/>
	<updated>2011-01-28T13:09:42Z</updated>
	<generator>PunBB</generator>
	<id>https://forum.modartt.com/viewtopic.php?id=1796</id>
		<entry>
			<title type="html"><![CDATA[Re: Linux custom suitcase controller - alsa subdevices ignored]]></title>
			<link rel="alternate" href="https://forum.modartt.com/viewtopic.php?pid=15316#p15316"/>
			<content type="html"><![CDATA[<div class="quotebox"><cite>pschork wrote:</cite><blockquote><p>I&#039;m building a suitcase controller / live rig using an Atom 550, Ubuntu 10.10 x86_64, Native Instruments Audio2DJ, Fatar TP80 waterfall keyboard.</p></blockquote></div><p>Wow...looks heavy, but nice work!</p><div class="quotebox"><cite>pschork wrote:</cite><blockquote><p>Pianoteq will only list the first available subdevice in the Alsa config, whereas on my MacBook, Pianoteq lists all 4 channels for the Audio2Dj (not a fair audio subsystem comparison, I know).</p></blockquote></div><p>What does any other audio software in Linux show you? If other software shows you the same configuration then it is Linux itself (i.e. recognition of the audio hardware).</p><p>[edit]</p><p>Sorry, I just re-read you post and you mention the ALSA config...</p><p>In terms of the default outputs I believe you have to set that in the ALSA configuration file...it doesn&#039;t remember by just selecting it in the ALSA gui.</p><p>JR</p>]]></content>
			<author>
				<name><![CDATA[johnrule]]></name>
				<uri>https://forum.modartt.com/profile.php?id=714</uri>
			</author>
			<updated>2011-01-28T13:09:42Z</updated>
			<id>https://forum.modartt.com/viewtopic.php?pid=15316#p15316</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Linux custom suitcase controller - alsa subdevices ignored]]></title>
			<link rel="alternate" href="https://forum.modartt.com/viewtopic.php?pid=15311#p15311"/>
			<content type="html"><![CDATA[<p>Nice looking setup.</p><p>I don&#039;t use pianoteq with ALSA due to latency issues so I normally use JACK.&nbsp; However, I just tried using ALSA to select additional channels but ran into some difficulties.</p><p>Alsa shows my sound card with 6 possible outputs and defaults to using channels one and two.&nbsp; If I try to check Channel 3 or Channel 5 then Pianoteq unselects the entire audio device.&nbsp; If I check 4 before trying to check 3 then I can select the four channels and it tends to stick when reloading.&nbsp; Now, I&#039;m not sure if this is a bug in Pianoteq or if this just has to do with my particular card but I figured I would post this here (tested on 3.6.6 20110117)</p><p>Selecting a bunch out of sequence (don&#039;t recall exactly as I was just playing around) and as I selected the final channel it unselected channel 1 which I thought was pretty strange as well so maybe the channel selection with ALSA is actually buggy.&nbsp; Maybe a few other users can check it out.</p>]]></content>
			<author>
				<name><![CDATA[sawtooth]]></name>
				<uri>https://forum.modartt.com/profile.php?id=531</uri>
			</author>
			<updated>2011-01-28T07:07:23Z</updated>
			<id>https://forum.modartt.com/viewtopic.php?pid=15311#p15311</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Linux custom suitcase controller - alsa subdevices ignored]]></title>
			<link rel="alternate" href="https://forum.modartt.com/viewtopic.php?pid=15310#p15310"/>
			<content type="html"><![CDATA[<p>First, let me thank the Pianoteq team for building such and amazing piece of rock solid audio software. I&#039;ve been running Pianoteq on linux x86_64 for a few months now and it has been rock solid! I&#039;ve even left the same instance running for over 2 weeks with no performance problems, memory leaks etc. Absolutely awesome. Thank you.</p><p>I&#039;m building a suitcase controller / live rig using an Atom 550, Ubuntu 10.10 x86_64, Native Instruments Audio2DJ, Fatar TP80 waterfall keyboard. The rig is designed to be used headless (no monitor) and will use midi automation to control Pianoteq.&nbsp; With this setup I&#039;m getting a performance index of 13-14. </p><p><span class="postimg"><img src="http://i.imgur.com/lSqq3.jpg" alt="http://i.imgur.com/lSqq3.jpg" title="http://i.imgur.com/lSqq3.jpg"/></span></p><p><span class="postimg"><img src="http://i.imgur.com/QV9ld.jpg" alt="http://i.imgur.com/QV9ld.jpg" title="http://i.imgur.com/QV9ld.jpg"/></span></p><p>The only issue I&#039;ve run into is in utilizing all 4 channels of the Audio2Dj, a 2 subdevice, low latency usb audio interface. Pianoteq will only list the first available subdevice in the Alsa config, whereas on my MacBook, Pianoteq lists all 4 channels for the Audio2Dj (not a fair audio subsystem comparison, I know).</p><p>Here is what &#039;aplay -l&#039; tells me</p><div class="codebox"><pre><code>card 2: Audio2DJ [Audio 2 DJ], device 0: Audio 2 DJ [Audio 2 DJ]
  Subdevices: 2/2
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1</code></pre></div><p>I&#039;ve tried creating virtual alsa devices that included all 4 channels, but Pianoteq will still only list the first available subdevice.</p><p>I have been able to route to all 4 channels using Jack, but Jack can be unstable and my attempts at automating channel routing post launch of Pianoteq were not rock solid - there are too many things that can go wrong in a headless environment.&nbsp; I&#039;ve also had Jack crash on me many a time - it is not as stable as Pianoteq IMHO.</p><p>Does anyone know of any tricks to get Pianoteq to list all Alsa subdevices? That way I could select all 4 channels, save my configuration and leave it.</p><p>Thanks,<br />Patrick</p>]]></content>
			<author>
				<name><![CDATA[pschork]]></name>
				<uri>https://forum.modartt.com/profile.php?id=1852</uri>
			</author>
			<updated>2011-01-27T22:55:34Z</updated>
			<id>https://forum.modartt.com/viewtopic.php?pid=15310#p15310</id>
		</entry>
</feed>
