FX-Sabers.com

The S.A.B.E.R. GUILD: Saber Manufacturers => Plecter Labs => Topic started by: erv on May 05, 2017, 07:45:06 AM

Title: Please Welcome the PRIZM v5 sound board
Post by: erv on May 05, 2017, 07:45:06 AM
Please Welcome the PRIZM v5 sound board

(https://www.plecterlabs.com/shop/images/PrizmV5-WEB.jpg)

The manual is in good shape too but not fully finished, it should be there by the end of the week.
As for availability, we have already manufactured some (USA) so they will be for sale "soon". Like for the NB, I've been busy with this release, so EU manufacturing will start during May


(disclaimer : you'll read similar text and statements if you compare with the Nano Biscotte V4 annoucement thread from yesterday. I'm guilty of copy / paste again but to my defense, that's because some features and new implementations are identical between the 2 boards ! :angel: )






SPECS
- [NEW] dimensions : 40.5 x 23.5 x 5 mm - thinner with smaller yellow capacitor with better placement for easier hilt integration
- [NEW] Dual Digital Sensor motion detection. Identical to CF MotionFusion™, very high swing sensitivity and vibration / battery ripple immune
- [NEW] Mute during power off. Optional silenced power-off sound when MOTG is engaged
- [NEW] Reverse polarity & over voltage protection
- [NEW] Enhanced deep sleep with 0.1 mA consumption (12 months of shelf time with a 14500, 36 months with a 18650), no kill key really needed.
- [NEW] 3 channel color "mixing" with FlexiBlend™ - 4A per channel
- [NEW] Pulse Fx
- [NEW] RGB Neopixel / WS2812 (and alike) support with power saving, adjustable timings and dedicated data pad and resistor footprint
- [NEW] Ledstrip power saving StripOff™
- [NEW] Ledstrip data output/line with onboard resistor (aka LS pad)
- [NEW] Ledstrip localized & Accurate Blaster Bolt deflection AccuBolt™ and MultiBolt™
- [NEW] Omnisabers™ support / Omnisabers™ Ready



Legacy FEATURES
- Up to 10 color profiles allowing the real time color change within a font. The use of a momentary is preferred as more natural to switch color, but I've added support for latching too.
- Up to 6 sound fonts. Now with automatic font amount detection, board ships with the PC3 usual set of 3 fonts, but you can have only 2 or 6 if you like - Comes with Lightmeat, Greymeat and Darkmeat
- Up to 16 swing and 16 clash sounds
- Multiple boot sounds
- Force Fx
- True 16 bit audio
- Designed for single li-ion cell
- FoC Mixing Techniques allowins mixed color FoC as well as traditional and popular "On-top" type Flash on Clash
- clash and swing motion flow limiters
- momentary and latching switch support
- off delay APOP and Legacy "NovaStyle" Anti power off (using Aux switch)
- progressive ignition / retraction (of course)
- quick on / quick off
- flicker / shimmer / pulse
- R.I.C.E. configuration system (wired or wireless)
- adjustable drive to remove the resistor in some (rare) cases
- changeable sound fonts, drop in support of CF/PC fonts, extra sound files are ignored.
- Override master file + individual configuration files for font specific settings



[MuteOff™]
The Mute-on-the-go™ has become highly popular especially with saber classes (and was an idea and request from Novastar, for his saber & fencing lessons back in like 2007?). When implementing this, I left the power off sound playing to indicate the saber sound was still "ok", especially when it was being tested for a show.
Then we got recurrent requests from people with bad WAF ;-) especially when playing at night with their saber and after being threaten of divorce several times. I think Saber League teachers were in the same boat too. I personally like to sometimes hear the power off sound to be SURE the saber is still "ok" when leaving the MOTG mode (and because silent sabers have now become daunting but it's also cool to allow the saber to be silent on demand, especially when you have 25 students in the dojo or studio turning their saber off at the same time :-)


[4 AMPs / channel HUMF FAP OMFG yumnomnomnom what an upgrade !!!!]
Well not really. Over the past years I've been fighting some lack of common sense with direct driven LEDs, in particular the fact most people don't measure their LED and don't calculate resistors and just expect it to work. Based on this, I tried to keep LED driving "reasonable" for beginners and rated the PRIZM (and NB) output up to 2A. Heck, as someone posted yesterday during this current discussion (pun intended), the plague "I just use 1ohm and it works" is still plastered everywhere on Facebook, so it's legitimate (IMO) to question this disinformation.
First of all, as a precision, the PRIZM doesn't "output" 2A or 4A, just like with Watt ratings of speakers, a lot of people think that it's forced out while it's "requested" by the load and the board would drive *up to xxx A*
Second, the driver part (that has been used for like 4 years now at least) has its maximum current rating at 6.5A and it's safe to use it 4A.
Overall, if someone wanted to use a BBB tri-cree on a PRIZM, I would however suggest to maybe split the load between a BB pair and the last B die or even all split on the 3 channels but it should be fine to handle all 3 on a single channel.


[New motion sensor]
It's been a while since I wanted to harmonize the boards all together and it's been mentioned during the release of CF7. The real difficulty was finding a proper time slot to accommodate the board production (EU / USA), distribution (EU / USA) and overall growing demand (worldwide). While it's a cool update which brings the former super accurate motion detection brought to you via CF7 2 years and a half ago, I don't call it an innovation per say, and I'm happy to provide it to the whole range of board (planned for Pico Crumble too).
It also brings a very good immunity to power supply noise and infamous errant swings, but this shouldn't be an excuse for not measuring your leds nor verifying what your battery drain is (and not just from the "datasheet"). To be noted that some manufacturers use binning for both voltage and hue and reading the bin code is much more accurate than just using the typical value from the datasheet (which is just a ballpark).
The motion detection uses the simplified parameters from CF, a motion "gate" that we usually set between 50 and 70 (not critical), no more general sensitivity to mess up with, and a swing threshold separated from the clash threshold.


[Omnisabers ?]
I've been using our former multi-saber wireless stage performance system for some year with Saberproject and during the period they designed their own wireless transmitter, I worked with them to enhanced the possibilities of wireless live performance with lightsabers. This has been achieved in the Crystal Focus firmware and is now progressively ported to other boards.
There's both a known demand for this for quite a while (saber leagues, saber groups, stage demo, booth demo, conventions, artistic fencing) and personal interest to pursue that work, I just couldn't address that so far but be sure I haven't ignored it :-)
How does it work ? Basically, as I consider trying to stream the sensor or the digital audio from the saber is a bad idea (mainly for latency issues but not only), I rather chose (in 2006) to send saber actions to the computer to control a polyphonic sampler.
I'm currently working on my new omnisaber "dongle" to revive both hardware and software initially designed 10 years ago but in the meanwhile, I'm ensuring the new gen of boards can be "omnisabers-ready". The saber actions are exported on the board serial port / RICE port, just like any of the diagnostic information and remote configuration.


[Neopixel (and alike) support]
The NB allows to drive a WS2812 (and compatible) blade up to 150 pixels. The strip data line is handled by the pad L3 when the board is configured for using a ledstrip. We spend quite some time to build a neopixel driver that uses zero CPU along with an abstraction layer in the firmware so that the blade output / update is not different between high-power LEDs and a strip.
That means the strip gets the same exact refresh rate, flicker look & feel.
The driver has also adjustable timings, as some compatible pixels use a different chip (APA106, SK6812) have different timings, we therefore provide adjustable params in the override.txt file to define the strip protocol timing with a resolution of 25.2 nanosecond.

The board *addresses* 150 pixels max. With 2 strips you could have 300 leds.
So yes you can wire 3 strips NP. The current is crazy and there's more shadowing than expected but it's been tested by Alex Gordon.
I think you all got the point, I tried to separate the question of the addressed pixels vs the total number of pixels in the blade, which are 2 different things.

* To be noted that one significant difference between high-power LEDs and a LED strip when using the FlexiBlend™ engine is that the latter has a 10 bit resolution (0-1023) to define color with a significantly high resolution (billions of colors).
The strip uses only 8 bits to define color, therefore there's a much more noticeable quantification (ie "step") effect on smooth effects like pulse. Conversely, subtle effects like shy flicker become less visible or "obvious" due to the lower resolution of the strip. As a result, certain effects will need to be exagerated when using a ledstrip. Color remains defined on 10 bit just like our other direct drive boards however expect no visible color change by tuning channels with only 1 or 2 steps. The strip resolution being 4 times lower, steps of 4 are required to obtain a color change on the strip. For Pulse Fx (now on NB too) afficionados, the low brightness side of the ledstrip is also 4 times less smoother, hence digging too hard with the flicker depth will produce some stepped flicker. A depth of about 60-70% remains ok to the look (basically avoid the lower quarter).

* Neopixels & Power saving
In the global effort to reduce the need of a kill-key (would it be during a convention or for some shelf time) we wanted to preserve our super efficient deep-sleep mode that uses only 0.1mA of current, and which allow more than 1 year of shelf time with a charged 18650 (tested).
The pixel chips use some current even when off, about .9mA each. With a trimmed blade using for instance 2 strips of 140 pixels, we have a good 250mA of current draw when the blade is off, which we found ridiculous to not address for deep-sleep.
As a result, we provide a "remote power control" over the strip by hooking the strip(s) negative to 2 of the on-board LED drivers (aka on-board PEx). Both channel 1 and 2 are enabled at the same time to split the load of the strip when the blade is on. Once the blade goes off, channel 1 and 2 will keep providing the idle current to the blade until deep-sleep is reached, then the blade will be disconnected.
We call this feature StripOff™, a naming that has received quite a positive response, for some reason :-D

* Obviously, a more radical solution is always possible, by removing the blade from the emitter socket to prevent any current to be used, however it's great for component blade sabers to stay with their blade in and secured when used often, especially for duelling (the blade being heavier) and we think it's great to have such a saber always ready to strike without disassembling it just for the sake to save on runtime when there's a smarter way to do it.

* Neopixels LS pad (data line output)
For Prizm we had the room to implement a specific data line output to control the ledstrip. As required per the datasheet, a resistor is required between the output of the controller (sound board) and the strip to reducing ringing and keep the signal with clean edges & states. We added a 0603 footprint on the board to include the resistor on-board and save space in the hilt. The resistor is preferred to be "as close as possible" from the strip but it's definitely not critical with the scale of a saber hilt and we experienced no issue with on-board + 20cm of wires or thru-hole resistor next to the strip.


* Neopixel Special Fx
Based on our former CF-LS design, we combine a spatial scrolling with the fade effect of the high-power LED for a more dramatic scrolling effect. Two parameters lsfadeon and lsfadeoff define if you use the fade effect during ignition or retraction.
I've also added a parameter called lightstick that illuminates the blade all the pixels at once (no spatial scrolling) and which can be combined with the lsfadeon and lsfadeoff parameters.
That feature might sound a little "off" compared to the lightsaber but can be useful for some other pikes or staff, and I got a few request in the past for my electronics to go in devil sticks for instance.
Finally, the spatial scrolling is quite different to the eye compared to the progressive fade in / out of a high-power LED. As a result the sample-accurate synchronization between the power on / off sounds and the extension / retraction scrolling speed is rarely required or looks too slow. Like on our previous boards, the power on / off timing can be adjusted to an eye-pleasing speed
using the quick-on / quick-off parameters in the configuration file.

* Neopixel AccuBolt™  special Fx
Designed initially in 2011 (and not in 2013 as posted elsewhere by myself, it actually got implemented in CFLS v5, therefore before CFLSv6) it recreates the bolt impact on the blade, and stands for Accurate Bolt. Thanks to the neopixels, we've for sure propped it up

- The bolt is no long a segment flashing (obvious technology limitation of the 6 segment strip, back in the day) but now a fully defined, color-size-duration-location configurable impact simulator
- It replicates the blade energy alteration due the impact. It's not a random chopped-slice/segment of blade that changes of color, but it has smooth edges with a brighter central spot where the impact is.
- It progressively returns to the blade color in a realistic "temperature effect". Think hot metal hue changing when you watch a blacksmith hitting glowing metal on an anvil.
- Specific color or randomized/altered hue or totally random color (configuration based, font specific)
- And at last but not least, thanks to the fruitful discussion with Alex Gordon, we've added MultiBolt™ for extended realism. MultiBolt™ is a system that allows to trigger the bolt impact on the blade when it's *actually* happening, not when the sound starts playing. As a result, multiple blaster sounds can be initiated and further blade-blocked with associated visual impact

Title: Re: Please Welcome the PRIZM v5 sound board
Post by: Darkmatter73 on May 05, 2017, 08:18:36 AM
These upgraded boards are looking fantastic Erv, thank you so much for all your hard work!
-Darkmatter73
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: Darth Chasm on May 05, 2017, 09:32:44 AM
Even more goodies!

What's in store for tomorrow?
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: Meatsweats on May 05, 2017, 12:59:30 PM
Accubolt and Multibolt looks amazing on the demo. Seriously can't wait until the blades start getting produced!!!
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: EXAR KUN on May 08, 2017, 07:52:52 AM
We all died and went to Saber Heaven
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on May 08, 2017, 08:03:48 AM
I've uploaded the NBv4 manual with a simple tutorial regarding ledstrips. The prizm v5 manual should be there at the end of this week. It should be quick to write as there's less modification to talk about compared to the NB and most of the ledstrip work has been already written and documented for the NB manual
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: Elim Vos on May 24, 2017, 05:07:01 PM
Is there any info for the ETA at TCSS?

Title: Re: Please Welcome the PRIZM v5 sound board
Post by: CHEWBACCA on May 24, 2017, 08:19:44 PM
It has passed all beta testing now and will be shipping probably tomorrow so I would say first part of next week.
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on May 25, 2017, 02:00:50 AM
What chewie said :-) my pcbs are on the way too
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: Darthvix on May 31, 2017, 07:21:51 AM
Awesome, I cannot wait to try out the new v5.

If I had a chassis to fit the v4, the v5 should still fit since its just thinner
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: Wolf69 on July 05, 2017, 06:54:38 AM
Erv, i have seen some info on a possible V5.1 version but without any log.
Board seems smaller not just in heigh (yellow piece) but in width, is that true, would it still fit current chassis for V4?
Seems also that it has a new firmware?
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on July 05, 2017, 07:43:49 AM
about to announce this, indeed, that's the narrow prizm 5.1, 20.3mm wide and slightly shorter as well. Fits 7/8"  :angel:
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: PearlYeti on July 05, 2017, 11:29:20 AM
Any word on when TCSS will have more 5.0 or 5.1 to buy?
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: CHEWBACCA on July 05, 2017, 12:54:46 PM
Any word on when TCSS will have more 5.0 or 5.1 to buy?

Either Friday or Monday.  I am sending out boards today.
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on July 07, 2017, 01:22:58 AM
announced on FB pretty much everywhere, relaying here :-) EU stock should be there anytime soon, Elegant weapon got their goods, JQ has the parcel in transit, supposed to be delivered today
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: crain300 on July 11, 2017, 06:38:27 PM
does this support pulse effects?
thank you for all replies
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on July 12, 2017, 01:21:40 AM
does this support pulse effects?
thank you for all replies

yes, as posted in the spec page (#1)
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: Wolf69 on July 29, 2017, 09:31:49 AM
Could you please post or explain the wires for a ws2813 led strip and the fourth wire?

Thank you
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on July 29, 2017, 11:06:22 AM
You don't use it
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: Sethski on August 07, 2017, 06:31:57 AM
A bit of a newb question - for the data wire/pin for LED strips, the manual recommends a 330 to 470 ohm resistor. I wondered what Wattage of resistor you'd recommend? Thanks.
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on August 13, 2017, 11:14:12 PM
1/4 or 1/8 W will work
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: Sethski on August 15, 2017, 12:03:52 PM
1/4 or 1/8 W will work
Thanks - wired up to test out of hilt before install and all working fine. Especially loving the blaster bolt effects  :smiley:
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: MikeyX on August 27, 2017, 12:16:14 PM
Today I completed my first PRIZM v5.1 build and it’s an amazing card - really great work by Erv - and special thanks to JQ Sabers for supplying me with it.

Of note though I’m sure I’m just being stupid, but I had no idea the new MultiBolt feature worked on standard LED builds. For some reason I’d only seen it mentioned alongside the NeoPixel/LED strip features which I just skipped over as I was doing a standard RGB LED build.

Anyways I was slightly surprised when firing up the build on the bench that everything worked perfectly - except there was a long delay before the ‘FoC’ effect with the blaster blocks.

What could I have done wrong? I thought.

Nothing as it turned out - a quick read of the manual and a config file change later and I realised that the ability to timeline up to 10 blaster blocks for each of the 4 blaster sounds is not confined to the LED strips, but works for a standard build as well (and has been pre-configured for the 3 standard fonts - hence why it was happening out of the box).

It’s an amazing feature in it’s own right - I’ve already had fun creating multiple blaster/swing/blaster/swing sequences for some of my fonts and it’s great fun trying to mentally lock in to which blaster sequence has started (of the 4) and then keep up with what I programmed!

Anyways just thought I’d highlight this great new feature.  :grin:
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on August 27, 2017, 10:47:43 PM
you're not the first to be "locked" to expect to hear the sound when you release aux.  :cheesy:

thanks a lot for the kind words !
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: SaberSlucker on September 03, 2017, 09:56:21 AM
Hi there,
first of all - Thank you so much for your hard work!
I just bought after the Nano, which is working perfectly, the Prizm 5.1. And now I got a little problem with the LED-strips and I dont know where my mistake is. They just wont light up. I got sound, the clashes the 2nd switch is working and it makes also the sound if I want to change colors. But no light.

- solved -

The soldering on the dataport for the strip was the problem. Still don't know why, because the soldering looks perfect. I bridged it and connected it directly on the smd resistor.

So happy now, after 4 days of try and error. :)

Title: Re: Please Welcome the PRIZM v5 sound board
Post by: SaberSlucker on November 20, 2017, 07:18:34 AM
Hi there!
Is it possible to run a RGB switch over the high power led drive section? (LED input voltage 12V) I don't use the high power LEDs for the blade.
Two LED stripes are installed just as in the manual described. It would be cool if the color of the switch would change like the blade.

Grand merci!
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on November 20, 2017, 07:30:04 AM
yes but if your switch led is 12V rated you'll probably need to knock off the internal resistor to use it on a single cell !
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: SaberSlucker on November 21, 2017, 04:34:59 AM
Thanks!
Since I'm more the mechanical guy and not the electrical one, are the resistors these black pieces I have to bridge?
(https://ibb.co/kvm0F6)
Resistor ? imgbb.com (https://ibb.co/kvm0F6)
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on November 21, 2017, 05:09:56 AM
No, the resistors are inside the switch itself (if any)
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: SaberSlucker on November 22, 2017, 10:11:41 AM
Ok, mine is running with 6V but it works. Guess I will order new ones.
But here is one little problem, it works only if I set "ledstrip=0". I've seen your pics posted on FB, how did you combine both?

Thanks again for your support!  :smiley:
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on November 22, 2017, 10:35:47 AM
traditional PWM drive are repurposed to the neopixel strip drive so if you wish to mirror the blade on a RGB switch, mod it to put a pixel inside. That's what I've demonstrated a couple of month ago, I hacked an AV switch for this purpose.
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: Sloda Foade on December 29, 2017, 05:01:31 AM
Wow thanks Erv, I just finished installing a Prizm 4 in my son's new saber for Christmas, and I just opened the new 5.1 that I bought for my own lightsaber walking stick (undergoing it's 3rd regeneration) and I can't get over how much smaller it is. It is actually too small to fit in TCSS's battery and nano biscotte chassis. Brilliant work, this will allow me much more leeway to fit the board above the battery in the chassis I am designing.
Once again, well done Erv.
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on December 29, 2017, 05:34:46 AM
Wow thanks Erv, I just finished installing a Prizm 4 in my son's new saber for Christmas, and I just opened the new 5.1 that I bought for my own lightsaber walking stick (undergoing it's 3rd regeneration) and I can't get over how much smaller it is. It is actually too small to fit in TCSS's battery and nano biscotte chassis. Brilliant work, this will allow me much more leeway to fit the board above the battery in the chassis I am designing.
Once again, well done Erv.

Taken to the heart, I can't tell how much those comments are important to me, thanks a lot. Can't wait to see the latest version of your work ! Happy holidays !
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: Sloda Foade on December 29, 2017, 07:02:17 AM
Hi again Erv, here is a link to the latest saber I made for my son for Christmas as discussed.
Vision Sith-y Lightsaber for my 11 yo Son (https://www.fx-sabers.com/forum/index.php?topic=52635.0)

Hope you like it.
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on December 30, 2017, 01:53:28 AM
very cool build and present Sloda, thanks for sharing !
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: Wolf69 on January 16, 2018, 10:21:42 AM
Quick question Erv, when i push the aux button on some fonts, the blade turn off with the bolt and 1 second later come back to the original color, is that a parameter on the bolt functionnality?
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on January 16, 2018, 11:14:53 PM
Make sure you define your bolt size and location correctly in regards with the blade lenght (i'm assuming that's a pixel blade here)
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: Wolf69 on January 17, 2018, 07:26:36 AM
You mean the lbolt parameter in regards of the strip lengh? (Yes you figured right, neopixel)
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on January 17, 2018, 09:17:21 AM
lbolt and sbolt
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: Wolf69 on January 18, 2018, 11:23:12 AM
Erv,

I can't figure it out, with ither color than blue it's working, i have copied other config file on the bank and i'm still having the issue, a quick video to show you:
Untitled | Jc Wolf69 | Flickr (https://flic.kr/p/FsbCpd)
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on January 20, 2018, 08:43:20 AM
you probably just need to edit your flash on clash color
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: BEN KENOBI on January 29, 2018, 09:46:04 AM
Erv how do I disengage the multi bolt sound on this board ? Every time I turn it on it does the bolt clash and won't stop.
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on January 29, 2018, 10:32:03 AM
Edit the bolt.txt file. Either remove all timelines or use on bolt only for each timeline
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: BEN KENOBI on January 29, 2018, 04:03:01 PM
Thanks!!
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: BEN KENOBI on February 01, 2018, 02:28:01 PM
Edit the bolt.txt file. Either remove all timelines or use on bolt only for each timeline


I looked and I can't find that file.
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on February 02, 2018, 12:08:43 AM
it's definitively part of the default package.

also, are you sure that you're not having a aux switch wiring issue for your multiple sounds ? are those clash or blaster sounds ?
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: BEN KENOBI on February 02, 2018, 06:35:40 AM
it's definitively part of the default package.

also, are you sure that you're not having a aux switch wiring issue for your multiple sounds ? are those clash or blaster sounds ?

   Hey Erv I switch switches and it still does it. I'm thinking now my sd card is messed up . It will not read on my computor.
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: erv on February 02, 2018, 07:15:04 AM
it's definitively part of the default package.

also, are you sure that you're not having a aux switch wiring issue for your multiple sounds ? are those clash or blaster sounds ?

   Hey Erv I switch switches and it still does it. I'm thinking now my sd card is messed up . It will not read on my computor.

I'm wondering how you could previously look at the SD and not find bolt.txt if your SD card cannot be read in your computer ?
Indeed your card seems to have a problem or needs formatting
Title: Re: Please Welcome the PRIZM v5 sound board
Post by: BEN KENOBI on February 02, 2018, 02:08:57 PM
ERv I had to down load your files from your web site on a new SD card ( Not yours) because the other one for some reason was messed up. I've already bought a new one from the Custom Saber Shop.