Quatschmacher
-
Posts
4,998 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Shop
Articles
Everything posted by Quatschmacher
-
This is a good feature, the only problem is that these changes aren’t stored as part of the preset file, rather they are tied to the memory slot number so won’t be taken into account when reading from the pedal and moving those patches to new slots - whenever a slot is overwritten, it’s hardware change settings are reset to default. I did come up with a way to have these changes stored as part of the patch and be displayed and fully adjustable between 0 and 127 (as opposed to the coarse 1-9) but there wasn’t enough code space and it would’ve required a major rewriting of some of the core code. I barely use the onboard controls. You can do more stuff like that with MIDI, either exploiting the NRPN assignments or, perhaps more usefully and reliably, by assigning flexis to parameters you want to manipulate and using the standard filter cutoff mapping on expression. There’s plenty on offer. Still my favourite synth pedal by far.
-
Those are all things I suggested at the time and may or may not be implemented. You can move and swap multiple tiles in chunks, which goes some way towards making reordering quick. Remember also that the files themselves are so small that you can easily save multiple setups and quickly load those back in to the pedal.
-
It’s nothing to do with the pedal at all; it’s about making sure the interface is plugged in to the PC before launching Chrome, otherwise Chrome won’t detect it as it only scans the ports at the point of startup, not dynamically.
-
If you’re trying to simply rearrange ones you already have on the pedal, yes. Otherwise, you assemble your template of 99 patches in the tile window, populating from files on your computer or the cloud and then write that to the pedal. It’s fairly easy.
-
Just to play Devil’s Advocate for a second, was the complainant perhaps referring to the joint I have highlighted in this picture. If so, I can see how he may have mistaken the dark stripe in the wood grain of the outer section for a gap. That being said, looking at it closely and comparing it with the similar stripes in the other sections before throwing around accusations of foul play would have been advisable. Good luck with the sale. -
I wonder if it does similar stuff to the Strymon and ramps the power, potentially starving certain devices for a short while. Some source audio pedals have problems when powered with the Zuma. If it is something like that, you can get around it by powering up the power bank first, then connecting to the pedals afterwards.
-
Did it happen after loading a particular patch? What you’re describing is something I’ve never seen before in this pedal. I just know what happened to my Manta when I accidentally underpowered it - it went nuts and wiped my presets, messed up the LEDs etc. It was fine after a reset but digital pedals do strange things when they don’t get enough juice.
-
Check for diacritics and apostrophes in the titles - the FI doesn’t like them. Rename the tile before uploading. If that works, let me know and I’ll have a look through my uploads and rename the offenders.
-
I’ll PM you. -
I’d suggest reading the manual! You can also load files straight from the cloud.
-
Fair enough. I can’t remember whether the locking out of the graphical interface was in place before v3 was released or whether it was in a subsequent update; I thought it was in place at release. Hmm, a mystery and that bugs me.
-
Ah, that could explain the problems you had. You need to use the editor that is designed for the firmware version you’re running. Lots of stuff was added in v3.5 and, more significantly in your case, one of the instrument modes was removed. I’ve tried it in v3.60 and it always opens at the slider view if flexis are assigned to the EQ, which is as it should be.
-
They would need to be specifically registered to sell in the UK in order for the taxes to be paid by them as opposed to the buyer. Big companies like Bax and Thomann have done this, but for many smaller companies it hasn’t been worth the effort, as @Woodinblackhas said. (Scarbee had to stop selling to the UK for several months until he got registered here.) Having said that, if the taxes were expected to be paid by the buyer upon delivery, I would’ve though that the FI unit price would have been adjusted down accordingly for UK buyers. Not sure if that happened though. It certainly wasn’t a great situation for those buying and not expecting to have to pay any more. At least that has been cleared up for any future buyers now. (I could become an official distributor for the UK if I wanted to but I’m not sure I am up to the headache of all the extra paperwork that this would entail.)
-
@WoodinblackI got a reply from them and it seems the “all taxes included” was a piece of legacy text that they forgot to update after the B word. They’ve removed it now. I can only offer my apologies to you and anyone else who got taxed - I was simply quoting what was on their advertising copy.
-
Then someone has messed up somewhere. Either way, you are owed money. I’ve emailed Andras and Gábor to alert them and to ask what should be done about it.
-
And that can be and should be claimed back if it gets charged as all taxes are meant to be included in the sale price, as stated on the Panda site. If you still haven’t done so, I’d chase up getting your taxes refunded.
-
By the way, FI is on at a sale price again of €269, which may end today.
-
.
-
How did you get the graphical interface to show when loading presets that had Flexi EQ assignments? I tried and can’t get it to do that (which is good as it’s not supposed to be possible). Could you tell me the steps you did so I can replicate it.
-
My best guess is that if you did manage to force the editor to allow you to edit a patch that had an EQ flexi assignment using the graphical interface, then moving the curve did not result in the usual truncating of the offset in the parameter that occurs when the slider hits the upper or lower end. If so, you may have forced a parameter to be fed a value outside of its defined range, which can cause all sorts of weirdness. If this has indeed happened, then it needs to be made so that the patch is forced to show the slider view in the presence of a flexi assignment to an EQ parameter upon loading. During testing, I’d managed to lock the device up by accidentally programming outside the range, but never experienced anything like what happened to you. It almost looked like the device had been forced into synth or ewi mode, which would explain why audio wasn’t triggering the synth portion, though exactly how that might have happened is beyond me. I’ll take a look tomorrow and see what’s what.
-
It is indeed a beauty and it’s an itch I had been wanting to scratch for a long time after missing out on a similar bass about 15 years ago. I’m finding 41mm nuts a bit wide though. I really should’ve kept my Sterling. Or if I could find a SLO Special…
-
Ah, no can do, I thought you may have been on mainland Europe, which would’ve been a possibility for hand delivery.
-
Actually, I’d be tempted to do it again to see if that is what caused it. If so, it could be documented and fixed.
-
Thanks, Nick.
-
I could potentially arrange something, where are you?
