[Ardour-Dev] moving meters (issue #2377)

[Quentin Harley]

John Emmas wrote:
> Forgive me guys if this is a different problem - but since upgrading to
> 2.4.1 (and later to 2.5) I've noticed major problems generally, with
> Ardour's timeline.  I reported it here, in Mantis:-
>
> http://tracker.ardour.org/view.php?id=2384

I reported something similar a while back.  I believe it has something 
to do with a memory leak, as my project would crash shortly thereafter...

> Paul Davis wrote:
>   
>> > On Sat, 2008-02-23 at 21:45 +0200, Quentin Harley wrote:
>> >   
>>     
>>> >> Paul Davis wrote:
>>> >>     
>>>       
>>>> >>> Preferences -> Misc 
>>>> >>>
>>>> >>> set history (saved and in-memory to zero).
>>>> >>>
>>>> >>> try again. let me know.
>>>> >>>
>>>> >>>   
>>>> >>>       
>>>>         
>>> >> Now it bombed out directly after the first move...  Blast.  I'll try again.
>>> >>
>>> >> Try 2:  I could make 3 moves, memory not diminishing, but during the 
>>> >> 4th, it crashed and burned again.  I don't think memory is solely to 
>>> >> blame.  If only bugs were not multifaceted monsters lurking behind the 
>>> >> code just waiting to jump an unsuspecting user when he has a deadline 
>>> >> approaching...
>>> >>
>>> >> Ok, what do you want me to do next  ;-) 
>>> >>     
>>>       
>> >
>> > Sit back. I resynthesized your session here. It wouldn't load for me
>> > either. I fixed that, but now I'm working on the cause.
>> >   
>>     
>
> I have compiled 2.4 from source, and it acts in exactly the same fashion 
> with this project.
>
> After using <Ctrl><Shift> E to select all regions behind the edit point, 
> and moving it, the whole lot freezes up, never to recover.
>
> Regards,
> Quentin

Never heard anything since, and I completed the project using a 
workaround I found.

I since never had to cut, mix, master a complete album in ardour - but 
there is a project coming up soon.  We'll see how it behaves now.