MiCom Bug Thread

ProffieOS
41

The second fix was meant to fix this problem. Did you apply it?

42

Yes, manually in the folder, thanks Fredrik, I think my cache wasnā€™t clear when I downloaded from the repo.

Getting weird behavior out of it now, trying to diagnose. It compiled and uploaded. I created a new font, and I canā€™t get the other buttons to activate while I am playing the background track. The background track is a t8hld.wav in 44.1 mono 16 bit pcm. I canā€™t stop that wav once it starts, and I also canā€™t play other triggers. But in other fonts, I can still play triggers while the track is playing. Iā€™m trying to figure out why. The only thing different in this font is that I have no t7clkX.wav or t8clkX.wav.

43

Does it say anything interesting (or different) in the serial monitor?

44

i didnt know serial monitor worked with teensy! Ill check that.

45

Hi all, Iā€™m trying to muddle my way through to create something similar to MiCom now that they are no longer producing sound rigs.
Does anyone have an example config setup that was used for the units at all?

46
47

I might be making some again this winterā€¦

2 Likes
48

Is that an official micom run or your own version?

1 Like
49

So, not ā€œmicomā€ run. .y own version, trooper com or whatever I call it.

I invented it, while Mike was the face of it I was the nerd behind the scenes that designed the initial units. Look at the year this video was made.https://youtu.be/JmrZ4-T-vYI?si=HZga9V3A0HgY18k5

and this one: https://youtu.be/oTW04YLEaIM?si=Kwf7DDcIwfAsand6

I am the ā€œco founderā€ of micom. The reason ā€œmicomā€ doesnt exist, is partially because I stopped building them. It lasted for 2 runs when I left. So, it wont be MiCom, it will be my own iteration. I am DS-74759/TK-74759 in the 501st Legion. I have the proper motivation to roll this back out, in a different brand with my own spin that makes it better, like an improved trigger boad:

20231018_151107
20231018_1511071848Ɨ4000 712 KB

So MiCom is dead, this will be something different, TrooperCom or something. Still need to research naming, and I have already talked with saber font makers about vouce packs for it they will sell. Im currently designing the 3d printed case that may incorporate a hard wired battery to reduce wire clutter of the unit.

Tom

2 Likes
50

Need some name ideas?

  • TalKie 421
  • MegPhone
  • HandJabber
4 Likes
51

Hey Tom, nice to meet the ā€˜nerdā€™ behind the magic. haha
Nice work btw.

I started creating sound units a few months back. Using the adafruit board.
Am on FB - EngageSoundRig
Currently itā€™s a 5 button device using some enclosed buttons that arenā€™t prone to the ā€˜sweatā€™ elements. :wink:

Working on a custom PCB as a trigger board as I didnā€™t like the look of the micom one. Seems you are on a similar wavelength. :slight_smile:

The version 2 has always intrigued me. Not necessarily from a ā€˜sellingā€™ point of view but just how it all works. Iā€™m new to this whole thing but love learning about the building and programming.

I do hope Iā€™m not stepping on your toes by learning how the unit and its setup works.

52

*Just chiming in to verify/validate Tomā€™s statement above. He indeed did invent the ā€œMiComā€ and personally I cannot wait to see what the new iteration is since I know a ton of cosplayers that are in other things where this device will get used.

**Buddy, thatā€™s awesome youā€™re gonna bring out a newer/better version!! Love It! Gonna definitely be watching this topic more.

2 Likes
53

Steve,

Here is one of my latest config files from my last run. I have not built on OS6, and I never added a common folder. Might be safer to program on an older OS, like 5.7? I have a version of 6, before the common folder was a thing. It might be ok. I have been having button conflicts since OS7, but I havenā€™t reported here yet, because I was trying to lay low. But now that it most certainly appears that ā€œmicomā€ is deceased, I will begin posting my issues again.

Here is a config file with 3 folders for different characters. Each preset, represents a different character, or you could have additional lines for the same character by switching presets due to your more limited button units. I think the big problem for your units, is that I think we used 2 buttons pressed simultaneously to change presets, thinking it was 1 and 8? Iā€™d have to go read the prop file againā€¦

Here is the config file:

#ifdef CONFIG_TOP
#include "teensy_audio_board_rev_d.h"
#define NUM_BLADES 0
#define NUM_BUTTONS 8
#define VOLUME 2500
const unsigned int maxLedsPerStrip = 144;
#define CLASH_THRESHOLD_G 2.0
#define ENABLE_AUDIO
#define ENABLE_SD
#define ENABLE_DEVELOPER_COMMANDS
#endif

#ifdef CONFIG_PROP
#include "../props/micom.h"
#endif

#ifdef CONFIG_PRESETS
Preset presets[] = {
  { "bank1", "tracks/jp.wav", ""},
  { "bank2", "tracks/mando.wav", ""},
  { "bank3", "tracks/breathe.wav", ""},
};
BladeConfig blades[] = { { 0, CONFIGARRAY(presets) }, };
#endif

#ifdef CONFIG_BUTTONS
Button Bt1(BUTTON_TRIGGER_ONE, trigger1Pin, "b1");
Button Bt2(BUTTON_TRIGGER_TWO, trigger2Pin, "b2");
Button Bt3(BUTTON_TRIGGER_THREE, trigger3Pin, "b3");
Button Bt4(BUTTON_TRIGGER_FOUR, trigger4Pin, "b4");
Button Bt5(BUTTON_TRIGGER_FIVE, trigger5Pin, "b5");
Button Bt6(BUTTON_TRIGGER_SIX, trigger6Pin, "b6");
Button Bt7(BUTTON_TRIGGER_SEVEN, trigger7Pin, "b7");
Button Bt8(BUTTON_TRIGGER_EIGHT, trigger8Pin, "b8");
#endif
1 Like
54

Thanks Tom, much appreciated.
Yeah I wont be looking to use the this setup with my 5 button rig.
Iā€™ll definitely move to an 8 button. Just need to wait for the latest revision of my PCB mounting board.

I guess with both of us testing on newer revision we can iron out any bugs sooner. :slight_smile:

55

I just want to clear something up in my head with this.
So the above shows that the SD Card will have 3 folders bank1,2&3 and their respective tracks.

If a rig just had bank 1 (For arguments sake configured as a Storm Trooper).
Then that customer wanted to have a second character installed would the config file need to be updated to have bank 2 listed in the presets?
Or can it just be a case of adding bank2 to the SD Card?

Many thanks

56

Youā€™ll get an error message if you switch to a preset where the font is missing, so in most cases you would want to reprogram the board if you add a font. That could be changed I suppose, but thatā€™s how it works today.

57

Ah ok, I was just thinking of the scenario of someone having a unit and wanting to add another character.
Sounds like the only option would be to send the unit back to get a new config loaded with a new character preset.
(Or obviously doing it themselves, but would want to avoid that).

I guess you could say configure the presets like this:

#ifdef CONFIG_PRESETS
Preset presets[] = {
  { "bank1", "tracks/bank1.wav", ""},
  { "bank2", "tracks/bank2.wav", ""},
  { "bank3", "tracks/bank3.wav", ""},
  { "bank4", "tracks/bank4.wav", ""},
};

So the SD card could have the above. Banks 2-4 would just have the wav files that might say something like ā€œNo profile loadedā€ but Bank1 has the sound files and bank1.wav says ā€œStormtrooperā€.

Then the owner could be sent a folder called bank2 that has files for another character and they just copy over whats on the SD card?

Would that work?

58

Pre-programming it with empty banks would work, although itā€™s not perhaps the best user experience.

We could also do some programming that automatically scans whatever folders are available on the sd card and uses those automatically. Not that hard really.

59

Hmm yeah I guess your right.
Just thinking on a long term ā€˜supportā€™ basis being able to supply a user with a folder to add to their SD card with another character without the need for reprogramming.
I think it would be a really good option.

60

I programmed all boards for 3 font folders, and then we had generic ā€œempty bankā€ wav files we put in other folders.

the adafruit rig was better for single character, tge advantage of the micom prop file is the ability to play a breathing loop or soundtrack, while simultaneously playing character sounds.

1 Like