View Issue Details

IDProjectCategoryView StatusLast Update
0002436ardourbugspublic2020-04-19 20:13
ReporterSlashsnake Assigned Toseablade  
PrioritynormalSeverityminorReproducibilityrandom
Status closedResolutionnot fixable 
Summary0002436: Ardour 2.5 Osx native - Problems selecting Interface from Audio Setup-> Device
Description(sorry for my english)

FROM http://ardour.org/first_time_osx_native :
"The first thing to do is to open up Applications -> Utilities -> Audio/MIDI Setup. Go to the main menu bar, click on Audio and then select Open aggregate device editor."

I create 2 of them-
1: with line-in + output (called LINEIN)
2: with Mic-in + output (called MICIN)

When I open ardour I go in Audio setup -> device.
Sometime, from interface, I can select only "LINEIN", sometime only "MICIN" and sometime both.
So the problem is..If I want to select LINEIN..quit the program and open with MICIN I can't...because sometime there isn't what I need..

Thanks for all!
TagsNo tags attached.

Activities

seablade

2008-11-24 10:11

manager   ~0005315

Can you do me a favor? Check in the Audio MIDI Setup program, and in the "Properties For:" dropdown box, select either of your aggregate devices, and then the other device. On both of those devices you should have properties for both input and output show up in the bottom of the window you can change. To be honest I don't, and I think this is a bug in Apple's Aggregate device management, but I want to confirm you are having the same issue(Which would in turn explain your problems above as Ardour is looking for duplex devices to use with Jack). Thank you, and feel free to post if this isn't clear.

      Seablade

seablade

2008-11-24 10:14

manager   ~0005316

For the record, one possible way to get around this might be(And I have not tried this yet) to create a single aggregate device with both the MIC in and LINE in on it.

        Seablade

seablade

2009-07-04 04:56

manager   ~0006230

Resolving this out as it has been half a year without feedback requested, and because I storngly suspect that you are runing into a bug with Apple's Aggregate Device editor really, which is part of why we really wish we didn't ahve to use it, but thank Apple for that one.

system

2020-04-19 20:13

developer   ~0021810

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2008-10-28 12:44 Slashsnake New Issue
2008-11-24 10:11 seablade Note Added: 0005315
2008-11-24 10:11 seablade Status new => feedback
2008-11-24 10:14 seablade Note Added: 0005316
2009-07-04 04:56 seablade Note Added: 0006230
2009-07-04 04:57 seablade cost => 0.00
2009-07-04 04:57 seablade Status feedback => resolved
2009-07-04 04:57 seablade Resolution open => not fixable
2009-07-04 04:57 seablade Assigned To => seablade
2010-04-24 10:28 cth103 Category bugs => bugs2
2010-04-24 10:31 cth103 Category bugs2 => bugs
2020-04-19 20:13 system Note Added: 0021810
2020-04-19 20:13 system Status resolved => closed