-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update README.md #75
base: main
Are you sure you want to change the base?
Update README.md #75
Conversation
Corrected FTDI section
Hi @patricecolet , thank you for the PR! May I ask where did you get your WVR? I think it is a very unusual one. |
Hello Andrew, as you predicted in README.md, I've made a boggus firmware and couldn't upload anymore, so I've bought this FTDI module. For having serial communicating with this WVR I have to connect WVR D0 to FTDI TX pin and D1 to RX, with 115200 bauds rate. The WVR I'm using looks as the same as the picture provided in README, and I don't know where it come from because someone gave it to me. I'm planning to build another one with a XIAO and high quality DAC or DSP, and I'm actually implementing Open Sound Communication. |
Adding OSC to WVR sounds like a great project! PCM5102 on WVR is pretty high quality, it can be used at much higher bitrate then the WVR implements. Let me know if I can help in any way. I sell WVRs with XIAO added to the back on my tindie, and on Sparkfun. There is also a WVR discord where you can reach me as well. I don't know much about OSC, but I have been curious for a long time, especially with what it could potentially add to WVR. |
WVR receive OSC packets on pinned core right now, I've just copied the code from midi_in.c and implemented udp. I do use PureData to simply send OSC messages, it's almost there :) We also use OpenStageControl for interfacing OSC and MIDI, the idea is about making a WVR cluster using wifi mesh for playing electroacoustic pieces with a wireless and low energy consumming acousmonium in a first place. We need to build our own version because we would like to be able to plug eventually a samd21 module for adding capacitive pins and use the XIAO firmware we've made for an handdrum interface we've called hexapad. Thank you help proposition, I'll probably need it ^^ |
I couldn't join the discord forum with the link provided in README nor with discord search engine. |
Hmm thats strange. I read this to learn about acousmonium. I am so excited for this project! I googled for hexapad but I could not find any info. I suppose it is not released? |
Thank you, It's just that I'm not used to discord. The esp-now protocol seems really promising, thank you for the tip. The hexapad project is still in dev state, and the documentation needs huge corrections. We are actually trying to find a design for using a piezo without interfering touch pins. Actually there is a wood prototype but we would like to have PCB. |
Interesting. I did this project a long time ago, but still have the code somewhere. It was a challenge. It used atmega32u4 https://hohumdrums.netlify.app/ There are 6 which is hex, so I wonder how similar it is? |
Our hexapad is for playing with hands, hence the Qtouch pins... I'm particulary proud of piezo signal management we have implemented because it prevents velocity errors and double attacks... |
meanwhile we had to indroduce 7ms latency for windowing https://github.com/patricecolet/hexapad/blob/stage-refactoring/piezo.cpp |
I guess the latency could be reduced by finding a good balance between piezo speed and sensitivity |
7ms is good, but there is room for improvement. I can personally detect 5ms when playing drums, others may not. My algorithm was derived by examining a lot of waveforms visually using python graphing, and I found a pattern of peaks that worked well, and the latency was eventually very low. It may have been particular to my hardware etc. Thanks for sharing the GH link, I will take a look! |
It comes from kickstarter |
Corrected FTDI section