<div dir="ltr">files that end in *.cc are not configuration files. They are part of the source code of the program. If you do not build ardour yourself, their existence and contents is of no importance to you.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 17, 2017 at 12:18 PM, Dr. Michael Kuhlmann <span dir="ltr"><<a href="mailto:RuA.Kuhlmann@t-online.de" target="_blank">RuA.Kuhlmann@t-online.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Toby,<br>
<br>
thank you for your answer on Mantis: <a href="http://tracker.ardour.org/view.php?id=7157" rel="noreferrer" target="_blank">http://tracker.ardour.org/<wbr>view.php?id=7157</a> - and excuse me please for not having answered yet (I just learned a minute ago that you had written in there).<br>
<br>
Your new message in here means that the solution decribed in Mantis (which I will have to check out - since it's my first encounter with Ardour's configuration files) does not work completely...?<br>
<br>
Your message in Mantis means that there is a configuration text file a/libs/ardour/region.cc ? I can't find it on my system, unfortunately...<br>
<br>
Thanks again<br>
Michael<br>
<br>
<br>
--<br>
Dr. Michael Kuhlmann<br>
Wedelstraße 84<br>
47807 Krefeld<br>
Germany<br>
<br>
<br>
-----Original-Nachricht-----<br>
Betreff: Ardour-Dev Digest, Vol 153, Issue 14<br>
Datum: 2017-01-16T22:01:05+0100<br>
Von: "<a href="mailto:ardour-dev-request@lists.ardour.org">ardour-dev-request@lists.<wbr>ardour.org</a>" <<a href="mailto:ardour-dev-request@lists.ardour.org">ardour-dev-request@lists.<wbr>ardour.org</a>><br>
An: "<a href="mailto:ardour-dev@lists.ardour.org">ardour-dev@lists.ardour.org</a>" <<a href="mailto:ardour-dev@lists.ardour.org">ardour-dev@lists.ardour.org</a>><br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Mon, 16 Jan 2017 16:50:40 +0000<br>
From: Tobi Stadelmaier <<a href="mailto:stadeltobi@gmail.com">stadeltobi@gmail.com</a>><br>
To: <a href="mailto:ardour-dev@lists.ardour.org">ardour-dev@lists.ardour.org</a><br>
Subject: [Ardour-Dev] Issue 0007157: Cannot move an automation curve<br>
together with a region<br>
Message-ID:<br>
<CAGGwtJ9VSZh9EBx8BfEF4=<a href="mailto:u6rM2YMWRafSLa2M1MhDizEycmHQ@mail.gmail.com">u6rM2Y<wbr>MWRafSLa2M1MhDizEycmHQ@mail.<wbr>gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi everyone,<br>
<br>
I'd like to make you aware of the issue above, since it bit me personally,<br>
but more importantly, I think it's something that might well break someone<br>
else's workflow.<br>
<br>
Effectively, the checkbox that says "move automation together with regions"<br>
in the preferences is ineffective in recent Ardour versions - it broke just<br>
after 5.0, and has been broken ever since. With a current version, you<br>
can't have Ardour move the automation of one track together with your edits<br>
of the regions any more. No matter if you have that checkbox set or not,<br>
the automation data of a track stays where it is, even when you move a<br>
region (or ripple-delete it, for that matter). Which I think certainly has<br>
the potential to be a major pain for certain users.<br>
<br>
The workaround that did it for me is to consolidate the track _before_ you<br>
move things around, but that's really only a workaround for sure.<br>
<br>
Anyway, I bisected it to a certain commit, and double-checked whether this<br>
really fixed it for me - details are in the bug report.<br>
<br>
Now, while I'm now personally running a patched version of 5.5 that solves<br>
it for me, I am really a bit uncomfortable with the alleged "fix" - the<br>
commit in question clearly tried to fix _another_ thing, which is not a<br>
factor in my personal workflow (since I don't use midi), so I'd be much<br>
more comfortable if someone who knows their way around the region.cc file<br>
could take a look. Quite honestly, I have no idea what the commit in<br>
question tried to do in the first place. But I'd be glad to learn :)<br>
<br>
Of course I'll be happy to help (bear in mind that I'm a Java person,<br>
though, and was basically banging my head against the keyboard until it<br>
worked for me again :)) But I'd certainly be able to help with testing a<br>
real fix, do some more bisection, or whatever. Just let me know.<br>
<br>
Cheers,<br>
Tobi<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.ardour.org/pipermail/ardour-dev-ardour.org/attachments/20170116/50e3d3a7/attachment.html" rel="noreferrer" target="_blank">http://lists.ardour.org/<wbr>pipermail/ardour-dev-ardour.<wbr>org/attachments/20170116/<wbr>50e3d3a7/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
______________________________<wbr>_________________<br>
Ardour-Dev mailing list<br>
<a href="mailto:ardour-dev@lists.ardour.org">ardour-dev@lists.ardour.org</a><br>
<a href="http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org" rel="noreferrer" target="_blank">http://lists.ardour.org/<wbr>listinfo.cgi/ardour-dev-<wbr>ardour.org</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Ardour-Dev Digest, Vol 153, Issue 14<br>
******************************<wbr>*************<br>
<br>
______________________________<wbr>_________________<br>
ardour-dev mailing list<br>
<a href="mailto:ardour-dev@lists.ardour.org">ardour-dev@lists.ardour.org</a><br>
<a href="http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org" rel="noreferrer" target="_blank">http://lists.ardour.org/<wbr>listinfo.cgi/ardour-dev-<wbr>ardour.org</a><br>
</blockquote></div><br></div>