traverso-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Traverso-devel] Behaviour of mute/solo


From: Remon Sijrier
Subject: [Traverso-devel] Behaviour of mute/solo
Date: Fri, 22 Sep 2006 16:00:32 +0200
User-agent: KMail/1.9.4

Hi list,

Right now, when a Track or AudioClip gets "silenced" either due mute or solo, 
the AudioSource related to the AudioClip no longer syncs it's readbuffer to 
the playposition.
This means that when the AudioClip gets "unsilenced" a sync action will start 
to resync the AudioSources readbuffer to the playposition.
This avoids unneeded reading from the hard disk, and cpu usage, however it 
causes a small "lag" before the AudioClip really starts 'playing' again.
This lag can be avoided by keeping the AudioSources readbuffer continuously in 
sync no matter if the data is used or not. (requires some (small) code 
changes though)

The question however is, what should be prefered?
A (relatively) small optimization by not syncing 'silenced' AudioClips, or a 
slightly better user experience by not having a 'lag' after an unsolo/mute 
before the audioclip is 'audible' again.

The 'pre' buffers size is currently oversized, and will be made significantly 
smaller (~ 0.7 seconds of audio, currenlty ~ 3 seconds @44.1 kHz)
This makes memory usage a lot lower on huge projects, and resyncing/seeking is 
much faster since less data has to be read.
The buffers size will become user configurable btw.

Thanks,

Remon




reply via email to

[Prev in Thread] Current Thread [Next in Thread]