It looks like this might be more relevant on alsa-devel. Some more details on the platform might be useful. -- Arun On 2 July 2015 at 08:35, golden <magic.lixin at gmail.com> wrote: > Hi PulseAudio forks, > > snd_pcm_htimestamp is unstable after change the date time of OS by using > "date -s xxx-xxx-xx", > It is very strange that the time value get from snd_pcm_htimestamp is > always 1420588802151082308 > > and here is what I get when cat the alsa infomation: > > uid=0 gid=0 at nutshell:/ # cat /proc/asound/card0/pcm0p/sub0/status > state: RUNNING > owner_pid : 1339 > trigger_time: 1420591411.800808521 > tstamp : 1420591457.486751372 > delay : 5040 > avail : 3152 > avail_max : 0 > ----- > hw_ptr : 2193408 > appl_ptr : 2198448 > > Does anyone met this problem before ? > > Thanks! > > > > BR, > Lixin > _______________________________________________ > pulseaudio-discuss mailing list > pulseaudio-discuss at lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss