SamIAm

Awesome news @rwillett, welcome to the family. If you;ve not already, I can highly recommend joining the MOD forum, loads of info and support there! https://forum.mod.audio/ S'manth x

@Phil Starr ... this looks amazing! Small, light, enough oomph for my needs and possibly powerable from a battery amp ... I love it! It's about time I use my makerspace membership to do some woodwork! lol S'manth x

A bridge you say, 5 string? 🤣 S’manth x

I can confirm Musescore does tabs on an iPad But I hear what you say about the nag nag nag to sign up! S'manth x

On another note (bada boom) I've been using musescore to try to get better at reading music, you can get it seup to show tab in parrallel and also print note names in the ususal musical notation. S'manth x

I use musescore on my macbook to put together basslines, it can display tab notation with timing markups and can play them back quite nicely. I've never tried the iPad version, but I gather it can play back. This app also looks quite funky https://apps.apple.com/us/app/guitar-tabs-x-editor-guitar/id1138809362 S'manth x

Oy @Baloney Balderdash, don't be 🤣 I definately get a different tone from my Ibby 28.6 inch and my Kala 23 inch, the latter is smoother and sounds more like an upright to my ears ... I love them both! IME Sorta. There are different string formulations (and even steel wound) available. The intonation ... challanges ... are partly due to the physics and lack of adjustable string scale lengths, but also technique plays a big part. I used to really struggle with intonation on my Kala 4-str fretted UBASS, anywhere above the 5th fret would start to sound off! A lighter touch (and also tuning at the 3rd fret instead of open) helped a lot. For me the game changer was going fretless, which now that I'm used to it, works really well (and also adds to the tonality I enjoy on the UBASS), tho my fretless 5er has a slightly longer scale length which also helps. S'manth x

I bought a new home for my Ibanez GSRM25 from Dave. It had arrived almost before I blinked with great comms throughout and exactly as he described. 11/10! Thanks Dave! S'manth x

I had a Ashdown Ant driving a Stonefield Mighty Mini. It was an ultralight setup and sounded great! (Sadly lost in a fire) S’manth x

My bass ukes are both Kala and use Hipshot Custom Ultralite, which are fab (But like all Hipshot stuff are not cheap!) https://kalabrand.com/collections/u-bass-parts/products/tuner-u-bass-hipshot-left I see that www.meinlshop.de sell Ortaga UBASS tuners. S'manth x

Oh for the time to do all that we want! Pedalboard change and Snapshot change MIDI messages are the same, but on different MIDI channels. I'm dancing around the edges of building my first LV2 plugin ... but have not yet jumped into the deep end (If you will allow me to mix my metaphors!) S'manth x

So, in case it might be of use to other Dwarf users. I uploaded several backing tracks to my Dwarf. My pedalboard contains the Audio File plugin (AFP). My "workflow" is to turn the AFP off, select one of the tracks and then save a snapshot with a name representing the track; I repeat this for each track. As we are about to perform a song, I load the appropriate snapshot (which is very fast) and when we are ready to start, I turn on the AFP which then starts to play the track. (Both of these are from a MIDI footcontroller). @Woodinblack, I wonder if a similar approach might work for your 12 audio sample scenario. Load all 12 onto the Dwarf. Select each in turn saving it as the name of the sample, but different to my scenario do this with the AFP on. I suspect (hope) that then when you load that snapshot (triggered by your 12 step) it would play that sample. Might be worth a try? S'manth x

First time out for the recently formed Just two songs at a small open mic (and we had not yet learned the words!) but it was well received and a load of fun. I spent the rest of the evening enjoying the other performers and co-running the sound system. S'manth x

I saw your post on the MOD forum about playing samples from your 12 step had a possible solution, but I did not realise that the 12 Step could send PC messages.

"They" actully believe this ... 🤣

First Step - Admit we are powerless over GAS S'manth x

New to the MOD platform, the Neural Amp Modeler plugin https://pedalboards.moddevices.com/plugins/aHR0cDovL2dpdGh1Yi5jb20vbWlrZW9saXBoYW50L25ldXJhbC1hbXAtbW9kZWxlci1sdjI=

Thanks Rob, My button logic already does. In "Instant" mode it only generates press/release events, but with near zero latency - this is aimed at looping or tap tempo type uses. In "tap" mode, it generates single/double tap (It will actually do triple or more taps but I doubt these are of much value), long hold/long hold release and repeat events. It also allows for a shifted long hold, if you tap then long hold. It was combining this sort of stuff into adjacent buttons that got me thinnking and out popped the abstration layer, which will allow generating all of these event types for all of gthe virtual buttons (7 at present) I am still aiming for one OLED per button (tho I might also add an extra one for the whole board as well) ... I've not yet approached the design of the OLED code, but have found an example on the Pico site that I think will fit in nicely. S'manth x

Some important changes have come up. Button detection Currently Tramps runs one thread per physical button; this periodically reads the physical button state (checking and debouncing the I/O pin it is connected to) and then takes the appropriate action. I've been pondering how best to detect pressing of adjacent buttons which I intend to use to switch up. and down configuration banks for instance, but I could not think of a elegant way of expressing this in the design. Then I had a lightbuld moment. I'm going to add a layer of logic just above the physical button I/O that checks (with debounce) ALL the physical button inputs. Once these inputs have stabilised it will update the state of a virtual button and this is what the existing button code will process. So at present, with 4 physical buttons (pB), the code will map to vitural buttons (vB) as follows: pB1 -> vB1 pB2 -> vB2 pB3 -> vB3 pB4 -> vB4 pB1+pB2 -> vB5 pB2+pB3 -> vB6 pB3+pB4 -> vB7 Taking this approach requires but a small change to the code base, but then allows me to treat a virtual button press in the same way as I currently treat a physical button press ... suddenly the functionality of handling adjacent button presses is already there! Storage of settings I had been intending to use an EEPROM chip to add memory for storing configuration of which buttons do what (And I have one in my box of bits) but I've realised it is not a lot better in terms of speeds or number of supported updates than the built in memory the Pico uses to store the firmware. The Pico flash memory is rated at 100,000 write/erase cycles (which would be about 10 updates a day for over 25 years!) totally good enough I think. I've found some example code that allows one to use the tail end of the Pico memory for data storage without erasing the formware program so I'm going to have a go at getting this running. The end result, will be about the same code complexity but lower hardware complexity and cost (Tho only about £5 lower lol). Both of these things are on the back burner these past couple of weeks as I've been focussing on crafting an application for a clinical research nurse role that would be spot on for me ... real world has to take priority at times S'manth x

I think it is the Softstep 2 usb midi pedalboard that claims to be able to survive a 2 story drop onto concrete and being run over by a car. S'manth x

Not sure yet, but I can add extra internal supports. My previous Trampa enclosure was sturdy enough to cope with stomping (tho perhaps not a car!) S'manth x