[Ardour-Users] trouble with retaining microphone connectivity over multiple sessions in Ardou
podeas at gmail.com
Wed Jun 24 10:52:48 PDT 2015
I am using Ardour 3.
re. session-starting, I've done both: I've opened existing sessions and
started brand new sessions.
I have looked at the connections in jack and consulted both
before initially consulting the list over a week ago.
Selecting and routing different sources (within Ardour) did not help in my
That said, I've been pretty focused on the soundcard as the issue. So I'll
be reviewing this information again in the context of the other information
I've learned from the past couple days.
On Wed, Jun 24, 2015 at 12:38 PM, Chris Caudle <chris at chriscaudle.org>
> On Wed, June 24, 2015 10:37 am, Cameron Metcalf wrote:
> > As stated, the very first time I use Ardour, it has no problem seeing the
> > box and recording from the microphone, all input levels are sensitive and
> > can be adjusted. On reboot, it apparently still sees the box (from all
> > other points I've discussed), but the input levels are dead, the
> > microphone
> > is capturing room noise, but Ardour is not showing any input level at
> Are you starting a new session in ardour each time, or just opening an
> existing session?
> When you create a new session I think the defaults are to connect inputs
> to any newly added track. I don't know what happens if you re-open a
> session with a recorded track, not sure whether the inputs get connected
> again or not. I usually turn autoconnection off and explicitly setup
> connections how I want them, and I'm not at a machine with ardour right
> now to check how the autoconnect behaves.
> You have not mentioned any details of how you are configuring the
> connections in jack. You do realize that jack is a patchbay type of
> design, where you have to connect the inputs you want to the destination?
> Sometimes that gets hidden by ardour automatically connecting things for
> you, maybe you need to open either the connection manager in qjackctl or
> the connections window in ardour and verify that the VSL inputs are
> actually connected to a destination port.
> You can also stop jack and use something like audacity which connects
> directly to alsa to verify the interface is working OK. As someone else
> mentioned, perhaps alsamixer is changing the hardware mixer on the device.
> Ardour 4 can also directly use alsa, but I think you said you are using
> ardour 3, correct?
> I don't recall you mentioning how familiar you are with ardour already, do
> you understand the places I'm referencing when I refer to the connection
> manager on qjackctl and the connection manager in ardour?
> Chris Caudle
> Ardour-Users mailing list
> ardour-users at lists.ardour.org
> To unsubscribe or change your mailing preferences please visit:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ardour-Users