-
Notifications
You must be signed in to change notification settings - Fork 812
[Request] Using headset jack on DS4 v1 #2089
Comments
I have mostly given up hope on that ever getting done. Too many other tasks to worry about and the experimental routine did not work 100% reliably. Haven't messed with that project in a while. |
Finally got a chance to experience real audio streaming from a PS4 last week. It is definitely higher quality audio than what is possible using the SBC approach. |
That was already discussed a bazillions times #1268 |
Okay. This is getting closed now. That same link that has been posted countless times in a number of threads for years. You aren't helping. The following link is a much better resource and it is what I have used when testing this. https://sensepost.com/blog/2020/dual-pod-shock-emotional-abuse-of-a-dualshock/
With the SBC approach, you are pretty much stuck with a fixed audio frequency (32 kHz) or the controller will fail to play it properly and induce audio glitching. I cannot remember how much space is given in the output report for the audio packet but it is not a large amount of bytes. Higher quality audio would only be possible if you could somehow access the Wireless BT audio interface of the controller that is separate from the output report. The output report data was only ever meant to play short audio sounds AFAIK. Sample project: Example SBC conversion command: |
I get that frequency is fixed.. But I find hard to believe bitrate would be too. For instance.. you seem to use a bitpool of 25 in your example (contrarily to the 19 reported by Cristofaro). Couldn't it be at least doubled? |
this could be it! maybe? |
Why do I bother to show the current progress? I have seen that project before and my sample project that I posted earlier is far ahead of that old code. Locking this issue now. |
Are we going to be use a headset on DS4 version one ? What is the problem? Is it impossible or tough? Do you mind If you explain to us? Thanks. You are doing great work.
The text was updated successfully, but these errors were encountered: