don't use PA_STREAM_NOT_MONOTONOUS anymore

This commit is contained in:
Lennart Poettering 2009-02-02 02:02:31 +01:00
parent 390133f2dc
commit fea675724d
2 changed files with 3 additions and 3 deletions

View file

@ -877,7 +877,7 @@ static int create_stream(
PA_CHECK_VALIDITY(s->context, s->direct_on_input == PA_INVALID_INDEX || direction == PA_STREAM_RECORD, PA_ERR_BADSTATE); PA_CHECK_VALIDITY(s->context, s->direct_on_input == PA_INVALID_INDEX || direction == PA_STREAM_RECORD, PA_ERR_BADSTATE);
PA_CHECK_VALIDITY(s->context, !(flags & ~(PA_STREAM_START_CORKED| PA_CHECK_VALIDITY(s->context, !(flags & ~(PA_STREAM_START_CORKED|
PA_STREAM_INTERPOLATE_TIMING| PA_STREAM_INTERPOLATE_TIMING|
PA_STREAM_NOT_MONOTONOUS| PA_STREAM_NOT_MONOTONIC|
PA_STREAM_AUTO_TIMING_UPDATE| PA_STREAM_AUTO_TIMING_UPDATE|
PA_STREAM_NO_REMAP_CHANNELS| PA_STREAM_NO_REMAP_CHANNELS|
PA_STREAM_NO_REMIX_CHANNELS| PA_STREAM_NO_REMIX_CHANNELS|
@ -1902,7 +1902,7 @@ int pa_stream_get_time(pa_stream *s, pa_usec_t *r_usec) {
usec = calc_time(s, FALSE); usec = calc_time(s, FALSE);
/* Make sure the time runs monotonically */ /* Make sure the time runs monotonically */
if (!(s->flags & PA_STREAM_NOT_MONOTONOUS)) { if (!(s->flags & PA_STREAM_NOT_MONOTONIC)) {
if (usec < s->previous_time) if (usec < s->previous_time)
usec = s->previous_time; usec = s->previous_time;
else else

View file

@ -532,7 +532,7 @@ pa_operation* pa_stream_set_name(pa_stream *s, const char *name, pa_stream_succe
* value returned by this function is guaranteed to increase * value returned by this function is guaranteed to increase
* monotonically. (that means: the returned value is always greater or * monotonically. (that means: the returned value is always greater or
* equal to the value returned on the last call) This behaviour can * equal to the value returned on the last call) This behaviour can
* be disabled by using PA_STREAM_NOT_MONOTONOUS. This may be * be disabled by using PA_STREAM_NOT_MONOTONIC. This may be
* desirable to deal better with bad estimations of transport * desirable to deal better with bad estimations of transport
* latencies, but may have strange effects if the application is not * latencies, but may have strange effects if the application is not
* able to deal with time going 'backwards'. */ * able to deal with time going 'backwards'. */