12-27-2018, 10:21 PM
Any idea what could cause this?
12-27-2018, 10:21 PM
Any idea what could cause this?
12-27-2018, 10:25 PM
You can also try to use 480p resolution to lower the USB bandwith needed by the projection.
12-27-2018, 10:35 PM
thanks, that actually makes sense. Will try and see if it makes a difference.
12-27-2018, 11:42 PM
12-28-2018, 10:26 AM
12-30-2018, 11:09 PM
I've also taken things one step further with my setup (I love to push my luck I guess), and I managed to integrate every single steering wheel control in my car into AA. My list went from 4 key presses to 17! My car has a commander knob and I got that working. I find I enjoy navigating AA with the knob instead of key presses. Every single one of those buttons and the knob itself is functional Here's what my arduino looks like now. Luckily it sits inside the glovebox! Here's all the buttons I have mapped (every single button is a resistive input) - {80, 83, 2, 201}, //vol up F8 {28, 32, 2, 200}, //vol down F7 {244, 248, 2, 118}, //prev track v {151, 155, 2, 110}, //next track n {704, 707, 2, 109}, //voice m {696, 700, 2, 112}, //answer p {681, 685, 2, 111}, //hang up o {502, 505, 2, 120}, //audio x (play) {509, 513, 2, 99}, //nav c (pause) {556, 560, 2, 177}, //back (esc) {519, 523, 2, 49}, //phone scroll left (1) {534, 538, 2, 50}, //setup scroll right (2) {609, 614, 2, 176}, //joy press (enter) {584, 586, 2, 218}, //joy up {587, 589, 2, 217}, //joy down {593, 596, 2, 216}, //joy left {590, 592, 2, 215}, //joy right Really sweet. Here's my only question... why does AA require 2 separate key presses to play & pause? Is that something that can be updated? It should be a single button to play & pause, and pressing the button just toggles between the two states. Most cars & HUs work this way. Would also save me a precious key press that I could map to something else. Let me know. Loving this thing now!
12-31-2018, 10:22 AM
01-11-2019, 04:38 PM
01-15-2019, 02:20 PM
|
|