This page is officially canonical to the FP137 Universe. Click here for more information.

Difference between revisions of "Microsoft Sam's Wacky Signs and Errors"

From The TTSCpedia
Jump to navigationJump to search
m
FairPlay137
FairPlay137 (talk | contribs) (→‎Trivia: mention Atom Smasher's defunctness)
Line 26: Line 26:
 
==Trivia==
 
==Trivia==
  
*The first run of episodes will be produced with Windows Movie Maker 2.0 on Windows XP Service Pack 3, simply due to how fast FairPlay137-TTS can get episodes done that way. However, some technical limitations may be worked around via Macromedia Flash 8 and/or Audacity.
+
*The first run of episodes was produced with Windows Movie Maker 2.0 on Windows XP Service Pack 3, simply due to how fast FairPlay137-TTS can get episodes done that way. However, some technical limitations may be worked around via Macromedia Flash 8 and/or Audacity.
 
**Additionally, custom transitions, effects, and titles are used in this first run.
 
**Additionally, custom transitions, effects, and titles are used in this first run.
 +
*The second run of episodes will be produced with Windows Movie Maker 6.0 on Windows 11. No noticeable changes will be visible between the first and second run.
 
*This may be the first time FairPlay137-TTS's own [http://www.fairplay137.net/error/ error generator] has been put to use in a TTS series, despite the generator still being in the alpha stages of development.
 
*This may be the first time FairPlay137-TTS's own [http://www.fairplay137.net/error/ error generator] has been put to use in a TTS series, despite the generator still being in the alpha stages of development.
 
*During the production of the first run, funnysigns.net did indeed go defunct, forcing FairPlay137-TTS to get signs from other sources for episodes past Episode 4.
 
*During the production of the first run, funnysigns.net did indeed go defunct, forcing FairPlay137-TTS to get signs from other sources for episodes past Episode 4.
 +
*During Episode 4's production, the Atom Smasher error generator went defunct, forcing FairPlay137-TTS to start using a fusion of both nkrs200's Error Designer and FairPlay137-TTS's own error generator once the remaining stash of Atom Smasher errors were gone through, which should happen by the time Episode 5 production begins.
  
 
{{FairPlay137-TTS Canon}}
 
{{FairPlay137-TTS Canon}}
 
[[Category:Series]]
 
[[Category:Series]]
 
[[Category:Pages needing attention]]
 
[[Category:Pages needing attention]]

Revision as of 00:28, 16 July 2022

Microsoft Sam's Wacky Signs and Errors
Created byFairPlay137-TTS
Episodes3
Main CharacterMicrosoft Sam
Airs onNo solid schedule, but usually on Saturdays (on VidLii/Vlare; YouTube version releases later) whenever possible.
StatusAiring

Microsoft Sam's Wacky Signs and Errors is a series by FairPlay137-TTS where Microsoft Sam reads signs as well as Windows errors in a similar fashion to some other series.

Starring

Episode List

Trivia

  • The first run of episodes was produced with Windows Movie Maker 2.0 on Windows XP Service Pack 3, simply due to how fast FairPlay137-TTS can get episodes done that way. However, some technical limitations may be worked around via Macromedia Flash 8 and/or Audacity.
    • Additionally, custom transitions, effects, and titles are used in this first run.
  • The second run of episodes will be produced with Windows Movie Maker 6.0 on Windows 11. No noticeable changes will be visible between the first and second run.
  • This may be the first time FairPlay137-TTS's own error generator has been put to use in a TTS series, despite the generator still being in the alpha stages of development.
  • During the production of the first run, funnysigns.net did indeed go defunct, forcing FairPlay137-TTS to get signs from other sources for episodes past Episode 4.
  • During Episode 4's production, the Atom Smasher error generator went defunct, forcing FairPlay137-TTS to start using a fusion of both nkrs200's Error Designer and FairPlay137-TTS's own error generator once the remaining stash of Atom Smasher errors were gone through, which should happen by the time Episode 5 production begins.