I am using Ardour in earnest since version 5.12.0 (year ???) running OpenSuse now on version LEAP 15.6. (AMD Ryzen 5 5600, 28 Gbyt Ram, All drives “ SSD “ (latest upgrade))
Haven’t had any problems with XRUNs for the last 5 Years or so !!!
Started with M-Audio Hardware interface, switched to Behringer 4 channel , 10 channel, 24 channel and now 32 channel. All worked out of the box.
My Wish-list:
A Lyric Track PLEASE !!!
A command to Un-arm all tracks (armed for recording) !
When a new version of Ardour is released, a more detailed description of the new features !
And a question : How do I copy tracks between different session ?
We have very, very limited resources available for work on the Ardour manual and/or videos, though Alexandre Prokoudine is doing a great job doing what he can.
The only way the current situation can improve is if more people step up to document things.
Copying a track in its entirety (settings, processing, data content) between sessions is quite complex. Copying a track without data is just a matter of saving a track template in the first session, and using it in the second, as described here:
Copying the data is notably more complex. You would likely do a stem export of the track from the first session, and then import it to a track you created with a template and then selected in the new session.
Not sure if it’d work for you but as a temporary workaround, could you maybe add some occasional location markers but with each one’s name set to the lyrics you want to see?
Hi Robin
Where I could add value:
Documentation: For new feature releases a more detailed description … as Paul pointed out “there are only limited resources.”
As I found, there are interesting new features which are only high level described.
It never helped me and I am sure I missed out not knowing what it was all about.
“So working myself into the new feature (communicate with the developer,), write a detailed description and or video.” The standard of the description should be as such that it can be immediately integrated in the Documentation.