the code for the change of the default device does work (i verified it with aplay), but psi does still use the internal device for the audio (instead of the headset which has device id 1).
Bummer. I guess that means mediastreamer is programmed to use the first device thenQuote by gst:the code for the change of the default device does work (i verified it with aplay), but psi does still use the internal device for the audio (instead of the headset which has device id 1).
It's not really under our control, but we'll try to see if we can provide a solution for this.
You don't need libjingle, it's shipped with Psi.Quote by zuri:And.. where can I get libjingle and the source (or binaries? yeah right =P) for the PSI that can do this?
<presence from="xxxxxx@amessage.fr/Psiko" to="xxxxxx@amessage.info" >
<priority>5</priority>
<c xmlns="http://jabber.org/protocol/caps" node="http://www.google.com/xmpp/client/caps" ext="voice-v1" ver="jingle-devel-1" />
<x xmlns="jabber:x:delay" from="xxxxxx@amessage.fr/Psiko" stamp="20051219T20:35:29" />
</presence>
If I Remember Correctly, it won't be in 0.11 either will it?Quote by Kev on 12-18-2005, 13:34:It certainly won't be in the next release, 0.10, as that's feature complete and just waiting for graphics. We'll be maintaining the psi-jingle port until it's merged though, as well as providing builds when it's stable enough, so it should be ok for availability.
No, it won't be in Psi-0.11. Psi-0.11 is roughly Psi-0.10 rewritten in Qt4 with QCA(1) replaced with QCA2.Quote by VxJasonxV:If I Remember Correctly, it won't be in 0.11 either will it?
0.11 is squarely for the QT4 migration I thought?
Keep in mind that I'm not on the Psi development team, but I do intend to roll up my sleeves and do what I can to help. I also am not a reliable source for predicting dates, but that's my best guess. I would say before summer for us north of the equator people.