GPIO rotary volume

[dh04000]

@acris I'm still interested in writing a how-to use this script, but I don't know how to write to the wiki. Can I just send someone a google document with the how-to in it?

EDIT: Also @Substring once I wrote the how-to, would you mind checking it with your system since you also have a rotary encoder?

[acris]

No problem make google docs and a modo add your document on wiki.

[Substring]

@dh04000 mine is not plugged hahaha

the wiki syntax is farily simple, you even have a WYSIWYG bar to edit

[dh04000]

Done: https://docs.google.com/document/d/15gvyNhxF_knimoVxYE0X3E4Fe1n_DSU06Wli_QtnwxE/pub

@Substring @acris @lackyluuk It needs some minor editing work for the wiki. I put comments in blue on what needs to be done.

[dh04000]

I started editing the wiki, but I'm not good at it.... Also, please test those copy/paste instructions. I haven't had a chance to try it on my machine yet.

[dh04000]

https://github.com/recalbox/recalbox-os/wiki/Rotary-Encoder-via-GPIO-(EN)

[acris]

Great !!! thanks a lot @dh04000

[dh04000]

@acris It's not done. I don't know how to add the text box with the script. Also, I want to show how to increase the rate of volume change, and change min and max of the script in the tweaks section. Which I still have to write. Got to test it on my machine first. Also, I need someone to test my instructions and verify that it works as intended.

[Substring]

@dh04000 you add code in 2 ways (wirks the same on the forum :

• either as a "span" lile this between back quotes
• either as a block

Like this

Between a pair of triple back quotes. But beware, you must start a new line after each triplet of back quotes. So my block above looks like :
3 back quotes without spaces
Like this
3 back quotes without spaces
Please note that on github you can specify which language is used in a code block. You just need to add the language name right after the opening triplet, say :
3 back quotes python
Like this
3 back quotes

The wiki langiage nme is known as markdown, and github has an advanced markdown for code

[dh04000]

@Substring

I'm trying to do this --> http://imgur.com/a/C7zRl

Edit modo :

test

test

[Substring]

@dh04000 Added the python code. You can't do as in the source because it's a gist using several files

[dh04000]

@Substring

Thank you! Now all I have to do is to point out, in the Tweaks section, how to change the gpio, volume increments, and volume range in the script, and the guide is complete.

[Substring]

@dh04000 Thank you very much for your contribution

[dh04000]

@Substring No probs. Thank you and the other Recalbox Mods/Devs for the helping make this work! There is still one more issue though, I need independent verification that this guide works as I wrote it. Would you be able to test it with your rotary encoder?

[Substring]

@dh04000 not before a long time, the main focus for now is fixing bugs for the stable 4.1

[dh04000]

@Substring A long time has indeed passed. Congrats on the 4.1 release! I've been successfully using this gpio program on my arcade machine for the last 5 months. Would you be willing to test the guide I wrote up with your rotary encoder and verify it? I want to finalize my guide in-case someone else wants to set up their own rotary encoder.

[Substring]

@dh04000 Hey !

For now, I just can't test, too many support requests with 4.1

[dh04000]

@substring said in GPIO rotary volume:

@dh04000 Hey !

For now, I just can't test, too many support requests with 4.1

I just bought a Raspberry pi 3, so I need to do a fresh install of Recalbox anyway. I'll use my guide as written, and if the encoder works, I'll consider that the "verification" that my guide works. I'll report back later with the result.

[Substring]

@dh04000 let's do it that way ! Enjoy Recalbox 4.1

[dh04000]

@Substring Well I have good news and bad news.

My guide was 95% successful in guide myself to reinstall gpio rotary encoder support. BUT, when I got to step 4), nano refused to save my changes, citing that I didn't have write permission, even though I had used "mount -o remount, rw /boot" in step 2). I changed the mounting in step 2) too "mount -o remount, rw /" and then I preceded as normal. The rest of my guide worked perfectly.

I realize though, its not a good idea to tell users to do "mount -o remount, rw /". Any idea what happened on my recalbox 4.1 install, that didn't happen on my 4.0 install? "mount -o remount, rw /boot" used to work....