Opened 17 years ago

Closed 17 years ago

#102 closed defect (fixed)

Device is not in proper state - after RC1

Reported by: Yoda Owned by: Paul Smedley
Priority: normal Milestone: Stabilization
Component: UNIAUD32 Version: 1.1.4
Severity: normal Keywords:
Cc:

Description

RC1 does not have this problem - it starts from RC2

From logs for almost all hardware I have seen, from RC2 and on we always seem to have left device in an non proper state. a short example from alsahlp$:

Hardware parameters: sample rate 22050, data type 2, channels 1, period size 1024, periods 32 Device is not in proper state: 1. Calling prepare

All devices seems to play ok - but in RC1 it seems like "prepare" was never called, so something must have been changed, since we now always are in non proper state

Change History (3)

comment:1 by Yoda, 17 years ago

Owner: set to Paul Smedley

comment:2 by Paul Smedley, 17 years ago

Changeset 345 fixes this.

comment:3 by Paul Smedley, 17 years ago

Resolution: → fixed
Status: new → closed
Note: See TracTickets for help on using tickets.