[Ardour-Users] Painful importing WAV files with constant crashing/segfaulting

Ken Restivo ken at restivo.org
Sat Feb 20 23:15:02 PST 2010

On Thu, Jan 28, 2010 at 07:16:30AM -0500, Paul Davis wrote:
> On Thu, Jan 28, 2010 at 2:08 AM, Ken Restivo <ken at restivo.org> wrote:
> > The only thing I haven't yet figured out is how the id parameter gets determined. It seems like it's just a unique number determined by a counter, but each time Ardour starts, the counter increments by what looks like 100. So the first few files and regions to get created get numbers like 100, 101, 102, and the next time I start Ardour they start at 200, 201, 202. Odd, maybe there was some kind of collision in the past caused by a crashed Ardour not saving the highest ID it had assigned to something before.
> there is a single counter for the session. Lots of objects get unique
> IDs. the counter is incremented every time one of them is created,
> whether or not you realize that they have been created or not.

Cool. How does Ardour know what is the max ID to start with when it opens up a session? In other words, where in the session file is the current or max ID saved? I looked, and couldn't find it.


More information about the Ardour-Users mailing list