I’ve figured out why WavLen<> behaves so weird.
I think that should be fixed now.
What I haven’t figured out is why it doesn’t work in the first place.
I kind of suspect that if you re-try now, it won’t work without specifying the effect in WavLen<>. (Or maybe it will just magically work now?)
Sure. It’s pretty straight forward test style.
StylePtr<Layers<
AudioFlicker<RotateColorsX<Variation,Rgb<0,149,255>>,RotateColorsX<Variation,Rgb<0,85,200>>>,
// Accel ignition and retraction
InOutTrL<
TrConcat<TrInstant,Layers<
TransitionEffectL<TrConcat<TrInstant,Black,TrDelay<1950>>,EFFECT_IGNITION>,
AlphaL<AudioFlicker<RotateColorsX<Variation,Rgb<0,149,255>>,RotateColorsX<Variation,Rgb<0,85,200>>>,
SmoothStep<Scale<Trigger<EFFECT_IGNITION,Scale<Trigger<EFFECT_IGNITION,Int<2000>,Int<1>,Int<1>>,Int<300>,Int<2000>>,Int<1>,Int<1>>,Int<-1200>,Int<35000>>,Int<-3000>>>>,TrDelay<5000>>,
TrConcat<TrInstant,Layers<
TransitionEffectL<TrConcat<TrInstant,Black,TrDelay<2000>>,EFFECT_RETRACTION>,
AlphaL<AudioFlicker<RotateColorsX<Variation,Rgb<0,149,255>>,RotateColorsX<Variation,Rgb<0,85,200>>>,
SmoothStep<Scale<Trigger<EFFECT_RETRACTION,Scale<Trigger<EFFECT_RETRACTION,Int<1000>,Int<1000>,Int<1>>,Int<3000>,Int<10>>,Int<1000>,Int<500>>,Int<35000>,Int<-1200>>,Int<-3000>>>>,TrDelay<1000>>>,
// Matching preon sound to blade effect
ColorSelect<WavNum<EFFECT_PREON>,TrInstant,
TransitionEffectL<TrConcat<TrInstant,Red,TrDelayX<WavLen<>>>,EFFECT_PREON>,
TransitionEffectL<TrConcat<TrInstant,Green,TrDelayX<WavLen<>>>,EFFECT_PREON>,
TransitionEffectL<TrConcat<TrInstant,Blue,TrDelayX<WavLen<>>>,EFFECT_PREON>,
TransitionEffectL<TrConcat<TrInstant,Yellow,TrDelayX<WavLen<EFFECT_PREON>>>,EFFECT_PREON>>,
// Matching pstoff sound to blade effect
ColorSelect<WavNum<EFFECT_POSTOFF>,TrInstant,
TransitionEffectL<TrConcat<TrInstant,Red,TrDelayX<WavLen<>>>,EFFECT_POSTOFF>,
TransitionEffectL<TrConcat<TrInstant,Green,TrDelayX<WavLen<>>>,EFFECT_POSTOFF>,
TransitionEffectL<TrConcat<TrInstant,Blue,TrDelayX<WavLen<>>>,EFFECT_POSTOFF>,
TransitionEffectL<TrConcat<TrInstant,Yellow,TrDelayX<WavLen<EFFECT_POSTOFF>>>,EFFECT_POSTOFF>>
>>(),
It magically works!
Using this with the Red specified and the rest just as WavLen<>, Red shows and all seems good. Thanks!
ColorSelect<WavNum<EFFECT_POSTOFF>,TrInstant,
TransitionEffectL<TrConcat<TrInstant,Red,TrDelayX<WavLen<EFFECT_POSTOFF>>>,EFFECT_POSTOFF>,
TransitionEffectL<TrConcat<TrInstant,Green,TrDelayX<WavLen<>>>,EFFECT_POSTOFF>,
TransitionEffectL<TrConcat<TrInstant,Blue,TrDelayX<WavLen<>>>,EFFECT_POSTOFF>,
TransitionEffectL<TrConcat<TrInstant,Yellow,TrDelayX<WavLen<>>>,EFFECT_POSTOFF>>,
But why do you need one of them to have EFFECT_POSTOFF at all?
Oh not at all a need, just a test.
If someone grabs or writes something like this, it could certainly be a mixed bag, no?
That’s how this started. I copied 4 random postoffs from my configs, but only one had the EFFECT specified. When it didn’t show, I started troubleshooting.
1 Like
I tested this and saved 7% of memory.
This worked as well my testing was via serial monitor set the dimming to 50% unplugged the usb and put the battery in, brightness was down by 50 percent. Plugged the usb (no battery) and checked on the ProffieOS Workshop and it retained the valued
Has anyone tested this yet? I would like to test it with my CUSTOM font Bal Venos.
It has been tested insofar that we know that it does something.
We may still need to make sure that it does the right thing.
Also, we should try to establish some good recommendation for the cutoff frequency and filter order.
Thank you, top post updated.
I tested Remap and CenterDistF. Working as expected. Using Stripes as test color, this showed stripes from either end meeting at center of the blade:
Remap<CenterDistF<>,Stripes<1000,1000,Cyan,Magenta,Yellow,Blue>>
I’m setup for multiple speaker tests, the current issue is figuring out how to have RTA software both compensate for the room AND use an external source for sound. It really wants to be the noise generator itself.
REW is currently what I’m trying, and awaiting on an answer from a forum.
Too much low rumble in the environment to use uncalibrated.
Top post updated for Remap<> and CenterDistF<>.
I was just going to download a sine sweep, play it on the saber, record it, then do a frequency analysis. Then do one without playing anything and compare manually. I don’t think we have to do this audiophile-style. Not that I will complain if it’s done right I suppose. 
1 Like
Additionally I threw BladeAngle inside CenterDistF<> and that worked too. fun!
Well, this is SOMEthing. And I am actually a bit dumbfounded.
These speakers (VECO and KR so far) …are reaching down to 40HZ.
Now, that’s on mic, and I doubt there’s enough energy there to actually hear the direct frequency much with the ear, but upper harmonics are audible for sure and they hint at the bass being there. It does not sound bad! NO distortion or ANYTHING I was expecting. I’m shocked.
So here’s a few results (in screenshot form…sorry. There’s no real other way to show this.)
-
Sweep_300-40Hz_20to20kView.jpg (Red is the held peak)
-
Adding in
#define FILTER_CUTOFF_FREQUENCY 100
#define FILTER_ORDER 8
So the filter works great. However, pure tone tests somewhat show it’s not “needed”. But actual font sounds should be tested, as there’ll be a lot of bass energy that will make the speaker much unhappier than a rolling off sine wave.
I need to let it sink in.
Videos of the sweeps here, note the octave harmonics of 300Hz:
Unfiltered.
HighPass Filtered.
This is what you’re listening to:
Sealed enclosure similar to this, with 1.5 inches resonance chamber from speaker cone to pommel opening.
3 Likes
Might be worth getting someone with a direct-out phone jack like Jesse Kirkbride has? Honestly, someone like him would be best placed since not only will he understand frequency dynamics and filtering, he has the facility to record and process it all.
1 Like
where’s the write up for the styles in os6 specifically this one, I may try to build a style around it.
These are part of Edit Mode, the .h file has template info, otherwise the test styles for Edit Mode would be best way to see. They’ve been pretty thoroughly tested already but running Edit Mode you can try out.
1 Like
oh my bad, I was just going through the list of the features and picked something that I might be able to do and didn’t see anyone had their name on the end of the that particular feature. no point doubling on work if it’s already tested.