oh. so only
ProffieOS.SFX.bgnlock.paired=1
needs to be set and all 3 ( bgn->lock->end ) will “pair” up?
No,
ProffieOS.SFX.bgnlock.paired=1
Will make bgnlock → lock paired.
ProffieOS.SFX.lock.paired=1
Will make lock → endlock paired.
Ok! I’m sure that’s exactly what you said but I get it now. Just wanted to be clear. I have always had both begin and lock set as paired so that’s also why I wasn’t seeing a difference. Compound that with the way font search paths now pull stuff backwards, I was having a hard time figuring out what was happening over here.
@OrangeSockNinja I just saw your post about syncing with music. I did this a ways back and would have to find the code I pulled from Fernando’s library and modified to get it working. Here’s a couple examples. Note that the visuals don’t reflect what’s truly happening in-person due to low frame rate and then uploading to YouTube and them degrading the quality.
The font is Metropolis that was originally pulled by @baconwizard and @nosloppy helped bring it up to speed.
*If you don’t know what font this is I’m ashamed. The rest of the sounds are a free font blend. *I’ve a Beastie Boys one that runs to Brass Monkey I should resurrect.
While I unfortunately have not had the pleasure of seeing Metropolis, I have heard of the movie and had the metropolis font when I first started getting into lightsabers.
If you had the config and documentation, I would love to mess around with it. Unfortunately I’m not nearly an knowledgeable with config, Arduino, or pretty much anything that is frequently discussed here. My extent of Proffie editing consists of basic config editing and copy and pasting Fett263’s bladestyles.
There’s so much to know though, so any info is helpful. And I appreciate the response, the whole concept is fascinating.
O/T* @OrangeSockNinja I’ll message it to you. You’re going to want to make sure that if you got the old Metropolis font set to use the one I linked. That’s the most current version.
So, in the spirit of pushing our luck, do we think pairing a hum to an out.wav would be useful/possible?
No idea if it’s useful, but it’s probably not that hard to do.
I’d vote for definitely useful.
1 Like
Ok, fine, done.
Wow amazing, thanks!
So then would ProffieOS.SFX.out.paired=1 pair out to hum.wavs?
What about boom?
If ProffieOS.armhum.paired=1 currently pairs endarm, is it just smart enough to do the appropriate one whether disarming or booming… ?
Yes.
I did boom at the same time.
But now that I think about it, I realize that boom should probably be paired to the lock_player, not the hum_player…
I see that, and the fix. cool.
However, the question is still the same 
armhum->boom
and
armhum->endarm?
Oh also, will this also require equal numbers of files in sounds?
Typically out sounds outnumber hums, but the special use case for this feature would likely require some pre-planning anyway, so if yes, I’d think that’s ok.
armhum → boom and armhum → endarm should both work now I think.
And yes, pairing always requires the same number of files.
1 Like
ProffieOS.SFX.out.paired=1 does not seem to be working, as the hum chosen is not a match.
I also tried removing ProffieOS.SFX.hum.paired=1 in case it conflicted somehow, (which was set to use the same hum repeatedly instead of choosing a new one randomly)…but it didn’t help.
Oddly, it seems a side effect of having ProffieOS.SFX.hum.paired=1 is that the in.wav is paired to it (expected?)
So while I also have ProffieOS.SFX.in.paired=1 to pair in->postoff, those seem to pick up the hum number.
So here’s a flow example.
ProffieOS.SFX.preon.paired=1
ProffieOS.SFX.out.paired=1
ProffieOS.SFX.hum.paired=1
ProffieOS.SFX.in.paired=1`
played:
preon 2
out 2
hum 4
in 4
postoff 4
I don’t think I was paying a lot of attention.
What I implemented was hum → in pairing, not out → hum pairing.
hum → in is sort of similar to lockup → endlockup, so my brain was fixed on that and didn’t actually read what the request was I think…
Oh well, out → hum pairing isn’t that hard to do either… In fact it should be done now.
Astounding what you can “whip up” when you’re The Maker.
About to test, but now how about that thing where
ProffieOS.SFX.hum.paired=1
is used to have the same hum loop. It now does double duty and also activates the out->hum pairing?
Just so I know how to interpret results / what options are (getting to be sooo many lol)
Yeah, unfortunately it does double duty now.
I may have to re-design how pairing is configured if that turns out to be a problem.
Well it’s working flawlessly. Thanks!