able to set default sink/source even the sink/source name doesn't exist

[hchen59]

Found on version 0.9.13, and 0.9.10

1> able to set default sink with incorrect sink name =>In pacmd, "set-default-sink fakesink", then "info" and check output, found "Default sink name: fakesink". Which means default sink could be changed even it doesn't exist. => using PA API to set default sink.(test app writen) The same result.

2> able to set default source with incorrect source name =>In pacmd, "set-default-source fakesource", then "info" and check output, found "Default source name: fakesource". Which means default source could be changed even it doesn't exist, => using PA API to set default source.(test app writen) The same result.

[hchen59]

Is this problem the same type of ticket #417? ie. would APIs of "set default sink/source" be implemented by future version of PA server, or not?

[coling]

I'm not sure here, but I doubt the two problem (here and #417) are the same in terms of API deprecation etc.

The default sink stuff is possibly just related to a late-binding of the sink names.

e.g. you can set the sink name to something random that doesn't exits, but when you try to use the default sink, it will be noticed that it doesn't exits and module-rescue-streams kicks in and punts it on to a real sink (not sure if it updates the default-sink value or not.. I'd have to look?)

I could be totally wrong here... this could just be a bug plain and simple.

I'll try and debug a little more, but Lennart will be able to answer authoritatively.

[lennart]

This is intended behaviour. It was previously used to support autoloaded sinks properly.