Woodinblack

Hardly a tribute to Jeff Beck then - he had quite bad tinitus which he found quite depressing so wore IEMs

See - I have never seen anyone denying good experience here, only the opposite. Most people who have had bad service have also had good service - 9/10 of orders with even the dodgiest shop are going to be smooth - pay the money get the item things.

yes that is what I have been doing for over a year now, never any interference if you are not using the internal Wi-Fi of the x18 - you can't use them together

why odd? All this "I like the sound of passive" that is trying to emulate that

I would say don’t daisy chain the dwarf (hard to do as it’s 12v anyway) as there is no chance the noise wouldn’t be an issue with that

it says it needs (and comes with a terrible) 12v 2A adapter, it actually uses 320ma flat out. I have mine on a 12v 500mA output

sorry away atm so I missed this, remember the dwarf psu requirements are a lot less than the power listed on the back, a CIOKS 4 should be fine

The last guitarist in my band got grumpy when I didn't play in the verse.

Just off the M3 I think

Well, we did a local coronation party yesterday. I think it would have been better if we had gone on at 6 rather than 8, as by 8 a lot of people from the afternoon had gone, but the main issue is that by 9:30 it was dark, I only have a couple of little lights to light up the area, and we were playing to an area of blackness. We knew the crowd were out there, as they clapped etc, but we couldn't see them. After a few songs in the second half we turned one light to the audience, so at least we could see their shadowy figures and tell that they were dancing, but it was kind of weird. It was getting a bit chilly towards the end though, but not complaining as both saturday and monday would have been much worse, at least it was dry and warmer. A local event over the hill had fireworks that managed to sync nicely with one of our songs Afterwards we had lots of nice comments and people seemed happy.

I am sure it is - I haven't done it much before though. The Spector isn't any hotter than any of the others (I would say the ibanez is), just seems to react differently, but responds well to the volume. Guess I can put a switchable front end profile in for different basses.

I think it may be an either / or - when I do my pedalboard it will just be CC, as I am not worried about controlling anything else, and that way I can set it up from the mod.

You can go very far off the beaten track, the only constraint is your imagination here, and maybe some CPU limit, but not something I have got to. I was using pitch to CV and then using the CV to modulate the delay time of an echo, and it didn't go as you would think as obviously the cv moves around a bit, and if you are using an analogue echo, turning the delay value pushes through the signal, which actually raises or lowers the output pitch, so it came up with some rather interesting effects. Not sure I can sneak that into mustang sally yet, but for my own home stuff it is fantastic!

By default it doesn't, other than on the CC interface, but the beauty of it is that you can do anything you want in your own patches, so you can have a midi generator that just sends a message when you switch to a patch. It does mean knowing what is on the patch and setting the button to the same as the patch, but that was mentioned at the beginning of this

As people said these things aren't exact, but it would be a fair bit less. 500W into 2R means that the voltage is 31.6V and the current is 15.8A. In a transistor based amp (a/b/d - doesn't matter), the amplifier is providing the voltage and the current is just a function of the resistance, so for 2.67R that means you are using 11.8A which gives you a power output of 374.5W In a valve amp, it would be the same power output, due to the transformer

Gigged mine again tonight - it does react differently to different basses, I took the spector and it was much more raunchy than the Maruszczyk that I gigged with last time, but got the levels working well. Still love that I can use it for bass and keys at the same time. I am beginning to get the idea of what I would like for additional footpedals for it - it is a bit of a pain changing patches and items within a patch, so need to work out the best way of doing that. Also, if you have quite a big patch but you are only using a few controls, it is still worth assigning the other controls in case you need to change them live, seeing as they are easy enough to set.

Have one of those later today - its amazing how almost every village poster advertising every village party is almost exactly interchangeable!

Indeed - that is the sort of timings that seems reasonable and in the ballpark of 'that isn't going to cause me any problems'.

Almost certainly could be a cache issue on that - we have a problem when we do an update that the buttons and menus don't work as the templates are replaced, and our stylesheets interfere - the cached elements have to be dumped and recreated (and I always forget to do that and panic!). I don't know if you can clear your cache for just basschat elements on your phone, but if you can, do that.

Big change now, if you see problems, please call them out

Indeed - sample all the buttons, adc etc every milisecond, and then when you have decided that the switch is not bouncing (and it doesn't need to be anything like 20ms) report any state changes. The worst latency you would have would be the time you have given for the button stabilisation + a max of just less than 1ms.

Unless you are an eskimo. But then in you are, what else is there to talk about?

Not sure why you would be taking 20ms for a detection event on a button, I would be very worried about my code if it was taking more than 100us to scan all the buttons, although I haven't done any timings on this.

Indeed - there is no time advantage doing a hardware debounce, you still need to wait for a stable state however it is done.

Huge reply snipped as this isn't a design meeting, its your project and I have finished work for the rest of the month!! For me, i wouldn't consider most of those things decoupled, just 'operating system tasks' (the button state, screen state, midi monitoring and expression pedal) which I would all be doing just on a schedule with a few queues as a low level thing. The HTTPD stuff, obviously whole different ball game and that certainly needs its own world - as far as i see that is where 90% of the complication will be. But as you say you have a whole operating system now so you can just do them as a series of different objects and abstract it away and that is probably the easiest way to do it. It is however checking how much worry you have to put into buttons and switches (and also expression pedals) to debounce as sometimes it is far less of an issue than you think, especially these days. Going to be fun though, and also good to have some milestones along the way.