Quatschmacher
-
Posts
5,579 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Shop
Articles
Everything posted by Quatschmacher
-
Where’d you get it from? Perhaps it’d be better for me to buy it from there once it goes back into stock in order to get the warranty.
-
duplicate.
-
I’d particularly like to hear how the envelope follower handles long notes; sounds like it might warble a fair bit. Haven’t found anything that decays as smoothly as my Microtron IV yet.
-
That doesn’t sound much like it. Ironically it (the Mono patch) sounds like one of the original Deep Impact patches. That’s a cool sound on the track.
-
Looking forward to hearing all about it. If you decide to move it on, please drop me a line as I’d like to check one out (unless you plan to just return it).
-
What gauge are these? -
*SOLD*Fender USA 2012 precision standard £750
Quatschmacher replied to bigmuff69's topic in Basses For Sale
Not surprised that went so quickly at that price. -
Re videos, I’m not even sure I have the nous to do screen capture with direct sound and mic. The manager functionality is something I’d been pushing for even before I got involved formally with the project. Took a good two years of being involved before my nagging paid off!😆 In the absence of videos, the tutorials I wrote in the manual are pretty useful for learning the ropes.
-
The FI is a bit of an exception as it can be played with keys. I did a blindfold side-by-side with my Moog Subsequent 37 and most people couldn’t tell the difference and many preferred the FI. If you’re after 80’s stuff then the Korg Volca FM or Yamaha Reface DX are solid choices.
-
I meant complete setups, but yes, saving different smaller chunks at various slot locations as individual files should also work just fine too. There are many approaches that would work and they are all a massive improvement on the old system.
-
If I’d been keeping an eye out, I could’ve done the SW one as I could get down there (though would likely have to take some time off work to do so).
-
The on-pedal adjustments are a legacy thing from the Deep Inpact, where that was the only way to make changes to the sound. Had I been onboard from the outset, I’d have pushed for integration of those with the preset data but I only got involved from the development of v3.00. Sadly I don’t have the video skills to do that sort of stuff from home (been hoping to do this with @GisserDfor about 18 months now but Covid nixed that). If I could get to a bass bash, perhaps someone with video skills could pair with me to record a workshop which could then be shared on here for other FI users to access.
-
Actually, maybe I should try and get to a bass bash somewhere and I could happily do a workshop on the pedal given enough interest.
-
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.
