source audio c4

[Dmonweb]

Hey guyz !
I've got a lot of difficulties to use my Hot Hand 3 with the C4.
All seems ok... But it doesn't work.

All products got the lastest firmware, trrs 1/8, green-green status blue (not blinking, ring too) yellow mode on the hot hand receiver.. White dips on the back are off/on/off/on...

I can see knobs in the NeuroApp making weirds things... Moving alone, ring on the table, but nothing affecting the sound...

Controler Inputs parameters in thé C4 are 0/1023 and modulate if I change values, but non direct control with the ring.

Can u help me, please ?
Thx !

 

[Quatschmacher]

Hey guyz !
I've got a lot of difficulties to use my Hot Hand 3 with the C4.
All seems ok... But it doesn't work.

All products got the lastest firmware, trrs 1/8, green-green status blue (not blinking, ring too) yellow mode on the hot hand receiver.. White dips on the back are off/on/off/on...

I can see knobs in the NeuroApp making weirds things... Moving alone, ring on the table, but nothing affecting the sound...

Controler Inputs parameters in thé C4 are 0/1023 and modulate if I change values, but non direct control with the ring.

Can u help me, please ?
Thx !

Answered on your Facebook post of the same.

 

[Dmonweb]

Thanks @Quatschmacher !

I spent my entire afternoon to configure NeuroDesktop, C4 parameters...

Should I try with the NeuroHub ?

 

[arctur]

Did anyone manage to crack this?

I don't know if I cracked it but I just published presets for the C4 and the Aftershock for Sir Psycho Sexy (same user name, patch names are "Sir Psycho Something"). I'd say it's 90% there... I use my Warwick Corvette $$ on the bridge pu because that's the closest thing I have to a Wal.

Maybe someone can take my patch and improve it, I'd love to have a bang-on patch. I worked from the assumption that the original sound was a broken mutron, so I took a mutron patch and broke it

 

[LowWay]

I don't know if I cracked it but I just published presets for the C4 and the Aftershock for Sir Psycho Sexy (same user name, patch names are "Sir Psycho Something"). I'd say it's 90% there... I use my Warwick Corvette $$ on the bridge pu because that's the closest thing I have to a Wal.

Maybe someone can take my patch and improve it, I'd love to have a bang-on patch. I worked from the assumption that the original sound was a broken mutron, so I took a mutron patch and broke it

Will you marry me?

I mean, this is awesome. I can’t wait to check it out.

 

[sunbeast]

I don't know if I cracked it but I just published presets for the C4 and the Aftershock for Sir Psycho Sexy (same user name, patch names are "Sir Psycho Something"). I'd say it's 90% there... I use my Warwick Corvette $$ on the bridge pu because that's the closest thing I have to a Wal.

Maybe someone can take my patch and improve it, I'd love to have a bang-on patch. I worked from the assumption that the original sound was a broken mutron, so I took a mutron patch and broke it

Unfortunately the Wal is probably a big part of the magic of that tone, as they have a pretty unique tone to begin with. Though the pickups on a Wal look close enough to standard bass humbuckers, they are effectively quite a bit different (very low-output and Hi-fi the way they are wired) and paired with a really unique preamp setup. A bass with dual parallel hi-fi resonant filter preamps built in, then run into another dirty sweeping resonant filter in the form of the Mutron! I would guess the best way to emulate it without a Wal or Alembic would be some significant pre-EQ into the filter to make it really pop up top (or even running a peaky static filter on Processor 1 into a Mutron-style wet filter on Processor 2, or a combo of pre-EQ and dual series filters!). I want a Wal damnit, but I will also try your patch!

 

[Modulus 96]

Will you marry me?

I mean, this is awesome. I can’t wait to check it out.

Everyone knows you have to kick the tires before you propose!

 

[bassbrad]

So is anyone else having as much creative electronic music fun with the C4 as I am? I find myself sitting for seemingly endless periods of time creating new sounds then exploring how I can get those to react differently by changing my attack to get Buchla-esque random sounds or glitches. Or stacking or slamming the C4 into another combination of effects for even more morphed out sounds?

Some of these experiments are going on commercial projects while others are for personal records but some is just blissful noise experimentation for me I would never think to impose on others.

Once more I must express my gratitude to the designers, dreamers and brave souls at Source Audio @rsmith601

 

[fivestringgecko]

So is anyone else having as much creative electronic music fun with the C4 as I am?

Most definitely. I've come to realize that I need to have a few hours free if I'm going to sit down and work on a patch. I can tinker endlessly with a patch. I blink and 4 hours have gone by!

5sg.

 

[Real Soon]

So is anyone else having as much creative electronic music fun with the C4 as I am?

I try not to overuse it at jam sessions because I kinda don't need anyone else to do anything while it's on. Esp with things like a Klein Bottle and Count To 5 on hand to help get weird

 

[Modulus 96]

As I browse patches I find some track perfectly and some don't track at all. I'll fiddle with the settings but can never get the tracking to work right. Mono phonic, poly, input level, adjust eq pre c4, etc... No luck. But some track very well without me needing to do anything special at all.

Does anyone know what the magic sauce is to get tracking perfect for a high-output bass? Emg pu's + emg 18volt preamp.

 

[Wretched Banana]

As I browse patches I find some track perfectly and some don't track at all. I'll fiddle with the settings but can never get the tracking to work right. Mono phonic, poly, input level, adjust eq pre c4, etc... No luck. But some track very well without me needing to do anything special at all.

Does anyone know what the magic sauce is to get tracking perfect for a high-output bass? Emg pu's + emg 18volt preamp.

You realize that the tracking and sensitivity related settings at the bottom do not apply globally right? You need to change them to match your bass & playing style every time you download a new patch.

 

[Wretched Banana]

^ Actually that there's a pretty significant usability oversight on Source Audio's part imho. Should be trivial to fix it and override all patches with your global settings too. This is smth I'd like to see in an update.

 

[bassbrad]

@Modulus 96 & @Wretched Banana when browsing sounds you should keep in mind that not all C4 or Spectrum creations are for bass, or were even created with bass in mind. Many of the contributors play guitar or other instruments or have different sound design ideas or needs different than synth bass tones.

 

[sunbeast]

^ Actually that there's a pretty significant usability oversight on Source Audio's part imho. Should be trivial to fix it and override all patches with your global settings too. This is smth I'd like to see in an update.

I think it would be impossible to standardize community presets like that in a way that would work for everyone. While Input Gain could theoretically work as a global setting for whatever particular instrument you are plugging in, if you use any other pedals into the C4 that may affect your signal level at different times (or different pickup settings for different tones) then a global setting becomes problematic pretty quick. Sensitivity isn't really functional as a global setting IMO because it is something I change for each for my patches for different effects (sometimes I want an envelope to trigger with every note and sometimes I want it to be more dynamic for example).

An option to set a fixed standard "Global" Input Gain could be cool for demoing tones, but its also not super hard to just find your standard Gain "value" and input it before demoing a preset. I believe you can actually approximate a "global Input Gain" by demoing presets in the "WYSIWYG" mode, since the "Input Gain" is one of the primary knob settings that should read when switching to a new preset. I haven't tried this, so just speculating based on my understanding. I believe you'd still have to edit the Input Gain parameter to match the knob setting when saving the preset onto your pedal though unless you also always play the pedal in the "WYSIWYG" mode and just optimize your Gain setting every time you play the pedal.

 

[Quatschmacher]

^ Actually that there's a pretty significant usability oversight on Source Audio's part imho. Should be trivial to fix it and override all patches with your global settings too. This is smth I'd like to see in an update.

Upper and lower pitch detection ranges are also parameters available in the MIDI map so it’s easy to program a button on an external controller to switch to (or between) your preferred range(s).

 

[rsmith601]

^ Actually that there's a pretty significant usability oversight on Source Audio's part imho. Should be trivial to fix it and override all patches with your global settings too. This is smth I'd like to see in an update.

The feature set of this pedal was defined by this community working with us.
It's not trivial, unfortunately!

 

[Wretched Banana]

The feature set of this pedal was defined by this community working with us.
It's not trivial, unfortunately!

Sorry but I don't see how this is not trivial. It's matter of adding a toggle to the app to let the user choose whether they want their own sensitivity settings to apply vs. let the patch override it. It won't magically make all patches play beautifully (e.g., those written for guitar will still fail), but it'll give you 2 things: 1) More patches will play correctly than they do now, 2) users will get to control how the system fails on the unhappy path.

 

[Wretched Banana]

I think it would be impossible to standardize community presets like that in a way that would work for everyone.

I agree, but that's not what I meant and it's a much broader concern.

 

[Quatschmacher]

Sorry but I don't see how this is not trivial. It's matter of adding a toggle to the app to let the user choose whether they want their own sensitivity settings to apply vs. let the patch override it. It won't magically make all patches play beautifully (e.g., those written for guitar will still fail), but it'll give you 2 things: 1) More patches will play correctly than they do now, 2) users will get to control how the system fails on the unhappy path.

Just because something may seem trivial as regards a small change to the surface set of controls does not therefore mean that the accompanying changes to the underlying code would be equally trivial to implement. Without knowledge of the code structure, we users are not best placed to know what is and is not trivial from an implementation standpoint.