It is harder for major banks to update their systems for this, so it will take them a while to implement. Smaller more nimble institutions will jump on first.
I find a lot of LLM writing exhausting to read. It is like I have to exert extra energy to attenuate my BS detector to cut through what is actually being said, and why.
I noticed that the strumming seems a bit off on chord changes. A good default is to let strings that don't change on chord change to continue to ring through. Just think about the strings as actual strings and the kinds of things that happen to them when you play.
Also, different songs will have different techniques like bar chords that may have less brightness, palm muting etc.
I'm working on a physical guitar digital luthier kit right now as part of a project at Toronto Metropolitan University working with disabled musicians. Our aim is to release it so anyone can build one.
Now we're taking lessons learned from that and working on robust versions for touring musicians, and variations to adapt to different assistive and artistic needs.
Great to see others doing nifty work with this guitar based music stuff.
Thanks, great input! Letting the shared strings ring through chord changes makes a lot of sense and I will look at it. Song techniques like palm muting are on the list too.
Your project sounds wonderful. Good luck with it, I'd love to see it when it's out.
What is the DAC resolution and sample rate? Delay/jitter? Noise?
What's the cost of something like this? It's just the NUC and the USB Audio Interface? When I play through my Komplete Audio interface and my laptop I (think?) I notice a delay. How would that compare to an off-the-shelf multi-effect modeller? In cost and features/performance.
These have always interested me but not enough to actually do something ;)
DAC resolution is irrelevant if your analog electronics produce noise in the lowest N bits. This is why I advice against using this as a primary comparison metric between audio interfaces.
Any audio interface with 24 bits has a digital dynamic range of 144 dB. Bad interfaces will have a noise floor of -80 dBm, the theoretical best value you can reach (at room temperature, for an audio band of 20kHz¹) is -131 dBm, interfaces for more than a 1000 Euros can reach around -127.
And this all assumes ideally set gain levels. Since this is rarely always the case in the real world 32 bit interfaces can still make sense, IF you have analog electronics that can deal with the signals to give you some extra headroom on top. But I'd still rather get a 24 bit interface with stellar noise figures, than a mediocre one with 32.
Aside from the proper input Impedance (High Z), the noise figures are probably the single most important thing when selecting a audio interface for guitar applications, especially if you plan to add a ton of gain in software. Of course drivers, latency etc. also need to work, but I have found that even cheap interfaces do a decent job at that nowadays.
¹: note that with bigger bandwidth that number gets worse, so if you record at 192kHz and you don't have analog filters before that cut the frequency band down to audible range you pay for that (proven many times to be inaudible) bandwidth with worse noise figures
The NUC was used and just cost me a replacement fan. USB audio interface was cheap from online classified. The touchscreen was just over a $100 on AliExpress, plus a bunch of cables of various sizes and angles to connect it all.
I've done the bare minimum to get this all going and haven't done any optimizations. Sampling at 48kHz. Load is about 5-6% even with a complex effects chain. I don't notice any latency, but I haven't measured it. Latency isn't an issue for the experimental instrument I play. The electroduochord.
Interesting, also sounds great. Any chances it could run on other embedded boards than the Rpi, or it uses some low level hardware stuff not found elsewhere?
Also would be nice to be able to operate it from real knobs and buttons.
Not sure about other boards. I image it could. It specifically is supported on RPi5 (and I think 4) but also Ubuntu on PC. I opted for DietPi to keep it simple and lean.
MIDI controller for mapping to knobs.
What I like is being able to type in digits so I can set very specific modulation rates that are in sync with other parts of the music.
Do you get those nightmares where you're trying to solve some problem but you don't have the right cables, and then the dream evolves into searching for the cables, but they're all wrong, and what was it you were trying to fix in the first place? Maybe this is why every drawer is now overflowing with cables.
I use OSC quite a bit for building experimental musical instruments and controllers. I use it because it is so simple to implement with low cost ESP32 or ESP8266 controllers, and can also quickly build GUI interfaces using TouchOSC.
The problem I have with it is compatibility amongst devices. For performances I bring my own WiFi router and everything is hardcoded with their own IP address. This controller can control this but not that. Everything is rolled custom.
Recently I've been doing a lot more MIDI stuff at a part-time job, and the compatibility is really awesome. I'm able to make things that just connect with different software and other hardware and it just works. You have to get your head around the spec a bit, but having things just work has been awesome.
MIDI2 is still not fully there. There are TinyUSB implementations rolling out now, so hopefully that all gets a lot easier.
There is also a proposed extension of OSC with a discovery layer. O2 and O2lite is an attempt to solve the connectivity and compatibility issues of OSC. I haven't tried it yet. https://www.cs.cmu.edu/~rbd/blog/nime-blog22may2022.html
reply