This is a fucked up feature! I think that IIRC there is page in the documentation bragging about how ardour was designed to get musicians recording. Every time I open ardour 10 mins is wasted playing with the inputs and outputs to remove this light!! There needs to be a clearer solution! No logs to say what is wrong, and even if they are there without it being BLANTANTLY overt the musicians wastes time! time is every thing in music
The no-align light comes on when you change the signal routing to create more than one way for the same signal to arrive at the same place, with different latencies.
If you donât mess with the routing, or if you understand why this sort of routing is a problem, then youâll likely never see it.
For many (most?) users and most (many?) workflows, Ardourâs default routing is all you need, and thereâs no need to adjust it.
Which is why the feature needs an upgrade. The light should be clickable and show the aberrant routing. Having the user search the routing is not ideal. Less things to remember means more creativity and routing should enhance the listeners experience, and it should be easy to use!
Why are you changing the routing?
In many cases, weâve found that users get routing into such a state that we cannot even tell them in any simple way what is wrong.
Ardour is designed like Unix: enough rope to shoot yourself in the foot. Weâre not here to hand-hold people through what they ought to do (and ought not to do), weâd rather make hard things easy and impossible things possible. We do try to choose defaults that will work for most people a lot of the time.
Why wouldnât I change the routing? In most standard mix techniques you establish busses via routing. There isnât anything special about this. It is just supposed to work.
Anyways the point stands that is should be easy to understand when something goes wrong. Isnât that unix philosophy? Do one thing and do it well? I donât understand why having a feature to click on the light to see what the problem is in the routing would particularly diverge from that principle. Maybe I should relabel this thread.
This is a forum, if you know solutions please help. Iâm a human being trying to get stuff done
The culprit was JACK. If ardour could for warn the user via the suggestions Iâve mentioned above it would be a great addition to an already awesome software! Thx for reading
Yes, the overall idea of Ardour automatically doing some kind of âbasicâ route comparing and at least giving the user some basic, initial glimpse at what route(s) might be causing the âNo Alignâ light to be lit is obviously a fine suggestion, and would be a welcome convenience.
Feel free to create a second login, and submit it as a âfeature requestâ using Mantis, here: http://tracker.ardour.org/ ![]()
(What do you mean by âdefaultâ exactly? -Direct connections to the Master? ⌠-Those are too simple!
)
These comments about routing confuse me. The latter (to me) is almost like saying âWhy are you editing audio regions?â : P
Routing is very, very important, and can oftentimes get quite complex based on the signal flow you wish to achieve. Obviously keeping things as âlinearâ, âlogicalâ, and consistent (-from group-to-group as well as project-to-project) is ideal in terms of better understand-ability. But sometimes certain situations âdemandâ pretty damn âoddâ routing.
I for one have spent several weeks honing certain track/bus signal flows/templates, and they typically involve âmany-to-oneâ and âone-to-manyâ connections, and heavy (basically exclusive) Aux Send use. For the record, I have thus far only encountered one project (-out of 16 total projects-) where the âNo Alignâ light was lit. But Iâm confident I can pinpoint why it is, and will get rid of it. ![]()
-J
Maybe some kind of reset option or button that removes the âNo alignâ situation.??
If someone doesnât know what they did to cause a no align, then they were likely not paying attention when the light started flashing. So, maybe an optional pop up window to be clicked away when it is switched on might be a less subtle indicator.