Ardour 2.3 problems

Thanks for the explanation Paul.

Did you happen to see my query yesterday (about unused
playlists) ?

I guess these are analogous to tapes that are stored away in
the cupboard
(which suggests that there's a way of taking them out of the
cupboard and
putting them on a newly created track).  But is such a
feature implemented -
or are the unused playlists there for an entirely different
reason (such as,
making the undo process simpler?)

John

----- Original Message ----- 
From: "Paul Davis" <paullinuxaudiosystems.com>
To: "John Emmas" <johne53tiscali.co.uk>
Cc: "Ardour Dev" <ardour-devlists.ardour.org>
Sent: 21 February 2008 13:02
Subject: Re: [Ardour-Dev] Playlist ordering (track
ordering)


>
> On Mon, 2008-02-18 at 09:51 +0000, John Emmas wrote:
>> ----- Original Message ----- 
>> From: "Paul Davis" <paullinuxaudiosystems.com>
>> Subject: Re: [Ardour-Dev] Playlist ordering (track
ordering)
>> >
>> > arrangement in what?
>> >
>> In Ardour.  For example, the session state file
might have seven
>> playlists
>> (named Audio1 thru Audio7) ordered Audio1, Audio2,
Audio3 etc.  But
>> when I load them into Ardour, Audio1 is topmost,
then Audio5 is below
>> Audio1, then Audio2 is below Audio5 etc.
>>
>> In other words each time I load a new session, its
playlists always
>> appear
>> in a certain order on Ardour's canvas (reading from
top to bottom) but
>> that
>> isn't necessarily the same order as they appear to
be in if you look at
>> the
>> session state file.  This is something I'd never
noticed before and I
>> just
>> wondered what affects their ordering?
>
> This is another terminology problem, nothing more.
>
> Playlists are not tracks.
>
> Tracks are tape recorders/players.
> Playlists are the tapes.
>
> Clear?
>
> Tracks are the one that have "order" in the
window(s), not playlists.
>
>

_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

On Wed, 2008-02-20 at 20:07 +0000, John Emmas wrote:
> After some experimentation this afternoon, I've
realised that if I delete a
> route (from Ardour's mixer) thereby deleting the
associated track, any
> playlist that was previously on that track gets moved
into UnusedPlaylists.
> 
> Now suppose I later create a new route (which creates a
new, empty track)
> and I decide that I'd like to assign one of the old
(i.e. unused) playlists
> to my newly created track.  Is there a way to get them
back?

press the "p" button on the track. a dialog
appears that will allow you
to select any of the available playlists. if it doesn't,
shout.


_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

Quentin Harley wrote:
> Daniel James wrote:
>   
>> If you can still reproduce this problem, could you
post that specific 
>> session online so that we can try it?
>>     
>
> I'm going to reinstall my system now.  I had to
complete a recording 
> project, and as of Yesterday 20:00 the master is in the
can...
>
>   

The session is a neat 15.6 gig... Will take me approximately
5 months to 
upload if I donate all my bandwith to it. 

That might be part of the problem, but I don't see why it
should.  The 
data lies dormanr on the drive, when you move stuff on the
timeline, it 
only moves the references to the data, is it not?

Well, I went back to pure 64studio 2.1pre9, and the problem
still 
occurs.  To me it feels that ardour runs into some kind of
limit 
powerwise, and then just gives up.  The last crash came
while editing 
the length of the silences between the pieces of music in my
CD 
project.  I went to the end of the first song, hit
<Ctrl><Shift>E and 
moved the rest back.  Then to the end of the second song,
and did the same.

By the 4th move, ardour slowed down severly, and then
stopped. I waited 
for 5minutes, the screen went white, and then ardour
disappeared without 
even an error message.

When I reloaded the session, I did it in the terminal, and
got this 
warning a few times:

(ardour-2.3:17835): GLib-GObject-WARNING **: value
"nan" of type 
`gdouble' is in valid or out of range for property `y1' of
type `gdouble'

The above warning also comes every time I perform a zoom
change, using 
my mouse wheel with <Ctrl>

The only way to get out of the hanging state the second
time, I pressed 
<ALT><CTRL><Del>, and the only comment on
the command line was:

killed

Ardour surely should be able to perform this task.

My project consists of three 3hr recording sessions, 4ch
24bit 44100Hz.
It is arranged in 12 tracks, allowing me to have different
fader and pan 
settings for each session to match the output.
The final CD length is around 65 minutes




_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

have you checked your ram ? i was doing a large-ish vo job
two weeks ago 
(about6 gig or so- 2 1/2 hr timeline) and after about 2-3
hours of editing 
all my ram was eaten up... wondering if there's a mem leak.


g.
_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

Geoff Beasley wrote:
> have you checked your ram ? i was doing a large-ish vo
job two weeks ago 
> (about6 gig or so- 2 1/2 hr timeline) and after about
2-3 hours of editing 
> all my ram was eaten up... wondering if there's a mem
leak.
>   

I have 2gig ram, 3gig swap.  Checked in TOP while performing
the 
actions, and sure enough, my available memory diminished
with each move, 
until it suddenly consumed all I had...  And sure enough,
ardour froze 
up (only this time I had to reboot my PC)

Hope it's a easy fix...
_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

On Thu, 2008-02-21 at 23:10 +0200, Quentin Harley wrote:
> Geoff Beasley wrote:
> > have you checked your ram ? i was doing a
large-ish vo job two weeks ago 
> > (about6 gig or so- 2 1/2 hr timeline) and after
about 2-3 hours of editing 
> > all my ram was eaten up... wondering if there's a
mem leak.
> >   
> 
> I have 2gig ram, 3gig swap.  Checked in TOP while
performing the 
> actions, and sure enough, my available memory
diminished with each move, 
> until it suddenly consumed all I had...  And sure
enough, ardour froze 
> up (only this time I had to reboot my PC)
> 
> Hope it's a easy fix...

Preferences -> Misc 

set history (saved and in-memory to zero).

try again. let me know.


_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

Am Thu, 21 Feb 2008 13:30:05 +0000 schrieb John Emmas:

> Thanks for the explanation Paul.
> 
> Did you happen to see my query yesterday (about unused
playlists) ?
> 
> I guess these are analogous to tapes that are stored
away in the
> cupboard (which suggests that there's a way of taking
them out of the
> cupboard and putting them on a newly created track). 
But is such a
> feature implemented - or are the unused playlists there
for an entirely
> different reason (such as, making the undo process
simpler?)

In the playlist menu there is an entry "select from
all..." with wich you 
can load playlists from other tracks.

_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

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 

Cheers,
Quentin

_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

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.


_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org

Hi Paul,

I've encountered another one of my strange
"funnies" when building Ardour
and I just wondered if it might make any sense to you. 
Here's what
happened.....

I was previously running Ardour 2.1 on both my laptop &
desktop machines
(both from the 2.0-ongoing branch and both would have been
the same svn
revision but I can't remember what number).  A few days ago
I did a svn
update on the laptop machine, bringing it up to svn 3117. 
This built
perfectly with all the new features.  I then tried doing the
same thing on
my desktop machine.  Although it built, after the install
there was a whole
bunch of stuff missing - notably, no libardour_tranzport.so
and only 5
drop-down menus on the main screen, compared to 10 on my
laptop machine.

I tried various things - Debug build / Release build / svn
--clean /
checking that my installed libs were the same on both
machines etc.  I even
checked that the number of files were the same in my Ardour
project folders
(and that they had the same numbers of bytes) but nothing
would make
Ardour build properly on the desktop machine.  At one stage,
through sheer
desperation, I even copied the entire directory structure
(including all
files) from the working machine to the non-working machine
but it still
wouldn't build correctly - even though in theory, it was now
using exactly
the same files!!

Eventually, I renamed my main 'ardour' branch and did a
fresh svn checkout 
to a new root branch.  This built and installed perfectly. 
I then renamed 
the old branch back to its original name - lo and behold, it
now builds 
okay!!

It's a compete mystery to me but I'd be interested to know
if that makes
sense to anyone else....

Cheers,

John 

_______________________________________________
ardour-dev mailing list
ardour-devlists.ardour.org
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour
.org