.jpg.518c69c2d9e1581799f3c11301dc2da5.jpg)
Quatschmacher
-
Posts
5,197 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Shop
Articles
Everything posted by Quatschmacher
-
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?
-
Excellent. Glad it’s sorted. I wonder if some power blip caused a memory corruption.
-
Is the instrument mode display still glitching?
-
Have you tried doing a “reset all” in the boot menu? Try that and report back
-
Could you hook it up to one of the other 9V, run the update again and see if anything changes.
-
OK. Are you just powering the pedal on its own supply with no other pedals attached to that power source (including while doing the update)? (What are you using to power it?) have you tried using a completely different supply? I’d suggest doing that and doing the update again using a different supply.
-
Did you replace the patches using the online updater tool, following all instructions to the letter?
-
Also wondering if this issue was caused by your hacking the graphical EQ window on patches with flexi assignments.
-
Just to be clear. Update to v3.60 and download the v3.60 editor (if you aren’t already using it).
-
That’s something I’ve never seen before. However, why you are describing sound wise sounds like what happens when old v2 patches haven’t been correctly flushed. If you have your patches backed up, I’d reinstall the firmware and v3.5 factory sound set via the online updater. Check that all works. If so, then load your own patches back on.
-
Maybe send a screenshot of the patch you’re using.
-
And do you mean it’s only sending clean when engaged? Is this on all patches? Didi you update to v3 recently and not perform the writing of the factory sound set?
-
Did you send CC2 at 0 somehow? That will mute the VCF output.
-
What did you do?
-
-
I think Source Audio allow warranty transfer, if I recall correctly from when I proof-read the UltraWave Manual.
