View Issue Details

IDProjectCategoryView StatusLast Update
0003515ardourbugspublic2020-04-19 20:14
Reporterdeva Assigned Topaul  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
Target Version3.0-beta1 
Summary0003515: "Auto Input" builds up noise signal.
DescriptionIn projects with many (I have tested it with 16) channels, enabling "Auto Input" will make the master channel play a white-noise-like signal louder and louder.
It appears to be some kind of loop, since it can be stopped by turning the level down on the master bus.

Disabling the "Auto Input" button makes it stop immediately.

Creating a project with only a few (I have tried it with 1) tracks does not make the noise.

It can be reproduced by simply creating a new project with 16 channels and enabling "Auto Input". after creation (if it is not on by default)
TagsNo tags attached.

Activities

oofus

2010-10-31 19:48

developer   ~0009330

Last edited: 2010-11-01 10:38

Well, I would say that was a normal and expected thing to happen. I would guess that each of your channels is connected to your soundcard's inputs. These will generate noise (all electronics does). The more inputs you have the more the noise adds up. Then I would guess that your master output is connected to your soundcard's output, then one of its settings is probably set to feed the output back to the inputs for monitoring, hence the gradual increase in the noise level; feedback.

I don't believe this to be a bug.

deva

2010-10-31 21:18

reporter   ~0009331

No. It is not static from the soundcard. I don't even have 16 channels on my soundcard.

Like I wrote it builds up and increases to infinity.

oofus

2010-10-31 21:25

developer   ~0009332

I didn't say it was static, I said it was noise, Johnson noise. ie the self noise generated by the inputs.

You don't need 16 channels, Ardour automatically routes however many inputs you have until they are exhausted then starts again. So if you have 2 inputs you will see ch1=in1, ch2=in2, ch3=in1, ch4=in2 and so on.

What is you're setup ? What soundcard etc

deva

2010-11-03 11:00

reporter   ~0009336

I have an M-Audio Audiophile 192, with 2 channels in and 2 channels out.
The chip shows up in ALSA with many more channels, I never really understood why.
It appears that the noise buildup starts when I create the 11th track with "Auto Input" enabled.
I can stop the noise by either disconnecting the input to the newly created channel, disabling "Auto Input" or by disconnecting the master output channel from the physical outputs on the sound card.
NOTE: I do not have anything connected with the input channels on the soundcard. The loop happens in software.

Futhermore, I noticed that channel 1 and 2 on the soundcard (which are the only physical inputs) are not connected until track 11 and 12 are created. Should the input channel assignment not use these two ports fro track 1 and 2? (Currently they start with sound card channel number 3 and 4 for track 1 and 2).

I am not really sure what or where the issue is here. It might even be in jack or ALSA.
I'll be happy to look more into it if somebody will tell me where to look...

paul

2010-11-04 18:03

administrator   ~0009345

You will need to use other forums/mailing lists to get help with your Audiophile. You probably have the internal hardware mixer set up to create a feedback loop, but without access to one of these cards, its impossible to know what settings to play with.

This is definitely NOT a bug in JACK or Ardour and does not happen to other users with the same h/w or other users with different h/w.

deva

2010-11-04 20:38

reporter   ~0009352

I can confirm that changing the parameters of the hardware monitoring inside the Audiophile did indeed change the behavior of the feedback I have been experiencing. I therefore conclude that the problem somehow lies in ALSA or the control surfaces built on top of that.

system

2020-04-19 20:14

developer   ~0022256

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
2010-10-31 19:17 deva New Issue
2010-10-31 19:48 oofus Note Added: 0009330
2010-10-31 21:18 deva Note Added: 0009331
2010-10-31 21:25 oofus Note Added: 0009332
2010-11-01 09:18 cth103 cost => 0.00
2010-11-01 09:18 cth103 Target Version => 3.0-beta1
2010-11-01 10:38 oofus Note Edited: 0009330
2010-11-03 11:00 deva Note Added: 0009336
2010-11-04 18:03 paul Note Added: 0009345
2010-11-04 18:03 paul Status new => resolved
2010-11-04 18:03 paul Resolution open => no change required
2010-11-04 18:03 paul Assigned To => paul
2010-11-04 20:38 deva Note Added: 0009352
2020-04-19 20:14 system Note Added: 0022256
2020-04-19 20:14 system Status resolved => closed