Data Colada Table of Contents

Mike's Notes

Data Colada is a remarkable effort by Uri Simonsohn, Leif Nelson and Joe Simmons on topics such as fake data, research design, meta-analysis, and the reproducibility of science, among others.

Here is the table of contents of Data Colada.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

26/09/2025

Data Colada Table of Contents

By: Uri Simonsohn, Leif Nelson and Joe Simmons.
Data Colada: 26/09/2025

Thinking about evidence and vice versa.

Table of Contents

About Research Design

About Research Tips

Comment on media coverage

Credibility Lab

Data Replicada

Discuss own paper

Discuss Paper by Others

Effect size

Fake data

file-drawer

Interactions

Just fun

Lawsuits

Meta Analysis

Music

On Bayesian Stats

Opinion

p-curve

p-hacking

Preregistration

Replication

Reproducibility

Researchbox

Statistical Power

Teaching

Unexpectedly Difficult Statistical Concepts

By , No comments:
Tags , , ,

Further UI customisation

Mike's Notes

Something I figured out last night. This will be very easy to implement.

Resources

  • Resource

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

25/09/2025

Further UI customisation

By: Mike Peters
On a Sandy Beach: 25/09/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Enterprise Account

The various Ajabbi Appl UI will come out of the box with industry-standard language strings used for terms in the ribbon, menus, controls, navigation, and other elements. However, the option of customising these strings will be available for all Enterprise accounts.

These changes can be saved as a template, shared and applied to any owned Deployment Workspace. The underlying terms still remain and can be easily restored.

Healthcare example

In healthcare, SNOMED provides a comprehensive list of terms, ensuring that any healthcare app utilises these terms. But an Enterprise account will be able to override any of these terms. This may be necessary if SNOMED is currently being implemented to replace an existing system. Another example would be healthcare not covered by SNOMED.

By , No comments:
Tags , , ,

Building like it's 1984: A comprehensive guide to creating intuitive context menus

Mike's Notes

This excellent article was originally published on the Height App Blog in 2022. Height is being discontinued. You may need to click on the videos to play them.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

24/09/2025

Building like it's 1984: A comprehensive guide to creating intuitive context menus

By: Michael Villar
Height: 01/02/2022

Michael Villar is the founder and CEO of Height. Height closed September 24, 2025.

Context menus have existed for decades, from macOS to Windows, from Xerox Parc to the web. They’re a widely understood user interface concept, but many new apps still fail to deliver them at the standard users have come to expect.

Since the context menu paradigm has existed for so long and is so widespread, users anticipate them to behave in similar ways across platforms and apps. But in reality, they don’t! In fact, each new web app creates their own custom menus, and users have to relearn what is possible and what is not in each app. Moreover, just like with the best animations, a great context menu should feel so intuitive that users don’t even stop to think about it.

In this post, we’ll go through some of the basics, as well as some more advanced interactions, for building seamless context menus.

The basics

Context menus are menus that appear upon user interaction, usually from a right-click or clicking a button. They have many names (pop-up menus, dropdowns, contextual menus), but they usually look pretty similar across different operating systems and apps. What does differ — however — is how they behave during user interactions.

Note: while context menus also exist on mobile devices, this post will focus desktop menus.

Historical examples of context menus, from Windows 95 through macOS 12 and Height.app 2021. 

They may look simple, but context menus can actually be quite intricate. We’ll go through the details one by one to break down the context menu user experience.

Position menus correctly

There are two main ways to open a context menu these days: from a right-click, or from a button-click.

Here’s an example of opening a context menu from our app:

Most context menus open from a right click.

If there is enough space, context menus align their top-left corner to the bottom-left of the cursor or button. They’re extremely predictable, as they should be — a user should instinctively know where to move their cursor to next.

It’s also a nice touch to highlight what the context menu is attached to, so the user clearly understands what their selection will be applied to (see the examples above, where the task and button are highlighted while their menu is open). Look around, and you'll see this is actually also true on macOS and Windows when right-clicking a folder or file.

Reposition menus as needed

Menus should auto-position themselves based on available space.

There are many instances where menus need to be repositioned as they approach an edge of the screen.

The consensus logic is to position the menu to the opposite side of the origin frame, which basically means inverting the horizontal/vertical axis to align menus.

Example: if a menu aligns their top-left corner to the bottom-left of a button, but doesn’t have space vertically, we can simply invert the vertical axis. So the menu would align their bottom-left corner to the top-left corner of the button.

One simple thing to do is monitor the window dimensions and re-layout the menus on the fly, so they can work in any situation.

Menus should be reoriented as the surrounding space changes.

Add keyboard navigation

Type-to-select

Typing the beginning or part of an option to select it makes keyboard navigation feel slick.

Though it's so useful and seems obvious, type-to-select is a feature that's often forgotten in newer apps. The most common implementation is to listen for keystrokes and automatically select the first menu item that matches the same prefix. At Height, we build a solution using match-sorter to be more forgiving as people might miss a keystroke when typing fast.

Keyboard navigation

Navigating a menu with your keyboard should be predictable and fast.

Your context menu should be navigable through keyboard shortcuts. This is another one that seems unpredictable on the web these days, yet it's so obvious in retrospect. And of course, a nice little touch is to cycle through the menu when reaching the end of the options.

Shortcut Action
Enter Select action
↓ Select next
↑ Select previous
← Close submenu
→ Open submenu
Esc Close menu

Give hints to the user

Feedback on click

Give the user subtle confirmation about which action was successful.

Something that makes context menus special is that they disappear right after being used. Adding some form of feedback after you’ve clicked an action is important to convey to the user that their action was successful. We stole the flashing indication from macOS, but there are many other ways to deliver a similar feeling of confirmation.

Menu anatomy

Copy-writing and information architecture might be the most important part of user interface. When it comes to designing the content of a menu, there are a few rules that are easy to follow to stay consistent and feel predictable to an user. Apple does a great job going through best practices around naming and organization menu. A few highlights:

  • Separate menu items with dividers, based on their similarity or relation with each other.
  • Dissecting a context menu's anatomy by type of action.
  • Disable menu items instead of removing them. A user can then discover actions, and be greeted by a menu that looks the same in any context. It’s also clearer to users that an action isn’t supported when it’s greyed out rather than just completely missing.
  • Display shortcuts next to menu items to increase their discoverability.
  • Suffix “…” to menu items that require user input to indicate the user needs to do something.

Simple and fast transitions

Animations are often used as transitions from one state to another. They’re important because they help the user understand the link between their actions and their effects.

Context menus are user interfaces designed for productivity. Speed and predictability are extremely important, and animations can quickly obstruct these goals.

At Height, we decided to briefly animate the primary context menu, but disable all submenu animations. To us, it gives the user the best of both worlds: a way to better understand how a menu relates to its environment, while keeping complex menus a blast to navigate.

Intuitive access to submenus

An interesting problem with submenus is: how do you access them with your cursor before they get disappear? Specifically, you would see this problem when moving your mouse diagonally towards the submenu.

A naive approach of implementing submenus. In this example, trying to quickly access the "Sort by" submenu is frustrating.

There are different solutions to this problem:

Delay

The simplest solution to this problem is to keep the submenu around for some time after leaving its parent menu item. If the submenu gets selected, it stays around and its parent menu item gets reselected.

Delay approach to the submenu problem.

Unfortunately, there are two issues with this solution:

  • It feels a bit janky to have a submenu open while another menu item is selected. Example: "Show visualizations options" is selected, while the "Sort by" submenu is visible.
  • When going through different menu items rapidly, there will be a delay for submenus to appear, causing the user interface to feel unresponsive.

Safe triangle

Amazon used to have a big dropdown menu and it became famous for the way it toggled submenus while moving your cursor. The basic idea is to show the submenu while the cursor is within a safe triangle.

macOS also uses the safe triangle principle and adds a timeout to disable the safe triangle logic. This makes it easier to select siblings while staying in the safe triangle.

Here's a showcase of this concept, with the safe triangle visible for comprehension.

Keeping submenus opened while the cursor is in a safe triangle gives us good results.

Content overflow

In some rare cases, context menus cannot be repositioned in a way that shows their entirety. There are two ways to avoid this problem.

macOS chose to let the user scroll through the menu using arrows, going through menu items one by one.

At Height, we didn’t like this solution as it is a bit cumbersome to navigate. Instead, we added a scrollbar into our menus that is shown when needed to let users know when a portion of the menu is hidden. We think this is a more modern way of solving this problem.

macOS uses arrows to scroll through menu items one by one.
Height uses a scrollbar to navigate within a long context menu.

As you can see, building context menus isn’t as straightforward as it seems — and doing it right can make navigation smoother for your users. At Height, we aim to be really intentional about building, from seemingly small details like context menus and scrollbars to core features and workflows. We’re excited to continue sharing our story of building a PLG product so you can develop your own product strategy. If you’d like to try the first-of-their-kind autonomous workflows we’re building at Height, sign up today…and make sure to follow along with our blog for more posts like this in the future.

By , No comments:
Tags

Translation website

Mike's Notes

Notes on the new translation website. Feedback is very welcome.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

19/10/2025

Translation website

By: Mike Peters
On a Sandy Beach: 23/09/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

The new translation website went live yesterday. It will become a catalogue of all strings used by Pipi when rendering web pages.

In Pipi 9, the UI strings are not with the code. Strings are added at render time by the Render Engine (rnd) from a database. Each copy of Pipi is configured to work with one i18n language.

Subdomain

Languages

The translation website has a separate section for each language. The section URL can include, if required.

<3-letter language code>-<4-letter script code>-<2-letter country code>/

Examples

Each section will be written in that language and script. The language home page provides information about;
  • About
  • Terms
  • Downloads
  • Locales
  • Sources

Terms

Each language has a list of terms in that language.

Each Term links to a web page for that term.

The term home page will provide information about;

  • Term
  • Meaning
  • Part of speech (Verb/Noun/Pronoun/etc)
  • Grammatical number (Singular/etc)
  • Where it is used by Pipi
  • Source of information
  • List the same term in other languages and scripts. These will be linked back to the native language term page

Downloads

The lists of terms in different languages will be freely downloadable in multiple formats.

Work in progress

The website layout requires significant improvement and is subject to change based on the discovery of what works and is useful.

Translation Workspace

A separate workspace for logged-in users to edit translations will be made available in the future. This will use automated workflows to propose changes to the translation database.

By , No comments:
Tags , ,

List of UI Phrases

Mike's Notes

This is a draft list of English phrases required for the user interface (UI). It will be updated over time. Suggestions and corrections are most welcome.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

27/09/2025

List of UI Phrases

By: Mike Peters
On a Sandy Beach: 22/09/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

These common phrases are required for the English language User Interface (UI). They will be automatically used in the ribbon menu, controls, basic forms, and navigation by the Pipi CMS Engine (cms). Their equivalents in other languages and scripts will also be used by the CMS where internationalisation and localisation are required.

Source

  • 100%
  • About
  • Align left
  • Align middle
  • Alight right
  • Automatic
  • Bold
  • Bullet list
  • Calendar
  • Cancel
  • Change password
  • Clear
  • Clear formating
  • Close
  • Close all
  • Contact
  • Contact Us
  • Convert
  • Copy
  • Copy to
  • Create
  • Cut
  • Database
  • Date
  • Date modified
  • Decrease indent
  • Delete
  • Description
  • Deselect
  • Deselect all
  • Design
  • Down
  • Drafts
  • Edit
  • Email
  • English
  • Exit
  • Export
  • External links
  • FAQ
  • File
  • Filename
  • Find
  • Find and replace
  • First
  • Font
  • Font colour
  • Font size
  • Font type
  • Forgot password
  • Format
  • Help
  • Hide
  • Home
  • Import
  • Inbox
  • Increase indent
  • Insert
  • Insert image
  • Insert video
  • Italics
  • Justify
  • Keyword
  • Keywords
  • Label
  • Labels
  • Last
  • Layout
  • Maori
  • Message
  • Maximise
  • Minimize
  • Modify
  • Month
  • Move
  • Move to
  • Name
  • New
  • New Task
  • Next
  • Numbered list
  • OK
  • Open
  • Open all
  • Open as
  • Options
  • Page setup
  • Password
  • Paste
  • Permission
  • Preferences
  • Preview
  • Previous
  • Print
  • Profile
  • Published on
  • Quoted text
  • Redo
  • Reference
  • References
  • Refresh
  • Rename
  • Reset password
  • Revert to draft
  • Role
  • Save
  • Save As
  • Search
  • Search description
  • See Also
  • Select
  • Select all
  • Send
  • Sent
  • Setting
  • Settings
  • Sitemap
  • Size
  • Sort
  • Spam
  • Strikethrough
  • Subscribe
  • Task
  • Text background
  • Text colour
  • Today
  • Type
  • Underline
  • Undo
  • Unsubscribe
  • Up
  • Update
  • Updated
  • User name
  • View
  • Website
  • Week
  • Workspace
  • Zoom In
  • Zoom Out
By , No comments:
Tags ,

UI Phrases

Mike's Notes

I'm looking for a list in English of standard phrases or terms commonly used in the User Interface (UI).

eg;

  • Align Left
  • Align Middle
  • Alight Right
  • Cancel
  • Clear
  • Close
  • Copy
  • Create
  • Cut
  • Delete

This would serve as the basis for creating an online translation database that supports multiple languages and writing systems, again using the words commonly used. It seems pointless to recreate the wheel.

Maybe 500 common phrases would be enough to make the basic website UI and user workspaces available in different languages. Even if it is to sign up, create a profile, and help with community translation.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

23/09/2025

UI Phrases

By: Mike Peters
On a Sandy Beach: 21/09/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

I have been experimenting with importing the Microsoft Term Collection. It is a freely downloadable zip file containing a collection of TBX files, one per language. TBX is an XML format with file extension ".tbx". There seem to be about 110+ languages. Each file record contains a source term in US English, and a translated term in the target language, eg French, German, Ukrainian.

Success

I was able to extract the terms that Microsoft uses. There are about 37,000     unique English terms. Some of them are useful, most are not, while others that are needed are missing. But it is a start.

Language Tools

To extract the language translations, the main challenge is converting the XML files into a tab-delimited format in the correct Unicode.

I'm trying a range of tools to see what works.

There is a list of TBX tools here

https://www.tbxinfo.net/tbx-support/

I used the free tool Glossary Converter to batch import 110+ language TBX files and convert to 110+ Excel 2007 format .xlsx files ready for batch import into the translation database.

The only 4 languages where there was a conversion problem were;

  • Central Kurdish
  • Punjabi (Arabic)
  • Tartar (Cyrillic)
  • Wayuu

This probably happened because I'm still learning how to use Glossary Converter and had the wrong setting for handling terms.

Importing

Importing has worked so far for these language files.

  • Afrikaans
  • French
  • Hebrew
  • German
  • Maori
  • Russian
  • Spanish
  • Ukranian

TermBase eXchange (TBX)

"TermBase eXchange (TBX) is an open XML-based standard that allows you to represent structured, concept-oriented terminological data in a database, which is known as termbase." - Wordbee

.tbx File Format

"TermBase eXchange (TBX) is an international standard (ISO 30042:2019) for the representation of structured concept-oriented terminological data, copublished by ISO and the Localization Industry Standards Association (LISA). Originally released in 2002 by LISA's OSCAR special interest group, TBX was adopted by ISO TC 37 in 2008. In 2019 ISO 30042:2008 was withdrawn and revised by ISO 30042:2019. It is currently available as an ISO standard and as an open, industry standard, available at no charge.

TBX defines an XML format for the exchange of terminology data, and is "an industry standard for terminology exchange"." - Wikipedia

Translation Website

To accommodate the translation needs of Ajabbi, a static translation website using a subdomain is now being created. It will be batch-rendered from a database containing a list of terms in each language and writing system (script), with a page for each term and its usage.

Database

As the database is updated, the website will grow. It will begin with English-UK spelling and Māori, both of which use the Latin script, and gradually expand to cover all languages and dialects requested by users.

The database data model should be compatible with importing and exporting TBX.

Translation Website URLs

Many languages have a local dialect (localisation) and sometimes use more than one script. There needs to be a robust pattern language for the automated naming of URLs. Using a naming pattern of 3-digit language code, plus a 4-digit script code, plus a 2-digit country code. If there is no variation, then use the 3-digit language code only, etc. 

Some examples to think about;

Translation Workspace

A dedicated workspace for users to help translate phrases in the UI should be built. Later, this could be extended to include translating help documentation, content, and other materials. Something similar to how Wikipedia or OpenOffice enable community translation efforts. Of course, each workspace needs to be available in any of the 110+ languages imported so far.

Open-source

The phrase library on the translation website should be made freely available for download in multiple formats, including TBX, CSV, and Database Formats.

By , No comments:
Tags , , ,

Ajabbi Research Monthly Newsletter

Mike's Notes

Below is an initial mockup of Ajabbi Research's proposed free monthly email newsletter. The newsletter will focus on a different subject in-depth each month. Examples could include User Interfaces, Ontologies, and API.

Existing content from On a Sandy Beach and Ajabbi.com will be referred to.

This draft mockup is an experiment. A presentation will be given to the Open R&D Group on Sunday. All suggestions are welcome. Please forgive the formatting. It will get better.

Subscriptions

Anyone is welcome to subscribe; it's 100% free, and it can be discussed, shared, and reused.

Schedule

Publishing on SubStack will begin in January 2026 and will be issued on the first Friday of each month. Each issue will also be published on the Ajabbi Research website a month later.

Planned Issues

  • January 2026: Workspace
  • February 2026: i18n
  • March 2026: Open Handbook
  • April 2026: Complex Adaptive Systems
  • May 2026: Origins of Pipi
  • June 2026: 

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

06/10/2025

Ajabbi Research Monthly Newsletter

By: Mike Peters
On a Sandy Beach: 22/09/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Ajabbi Research

October 2026

Design System Issue

"A design system is a set of standards to manage design at scale by reducing redundancy while creating a shared language and visual consistency across different pages and channels." - Therese Fessenden, NNGroup

Summary

One paragraph goes here. etc

The Problem

Some words to explain what the problem is, and what a design system does. The lack of a naming standard for components. Why the need for Design Tokens? etc

Design Systems

Give detailed examples of other successful design systems. etc

Design Tokens

Nathan Curtis. etc

Pipi Design System Engine

Explain how the Design System engine was built over time. Its unique features. Its integration with the CMS. UI component primitives. The engine can automatically lay out the components. No code interface. etc

User Customisation

Ability of users to customise the UI component primitives. etc

Conclusion

Two paragraphs of words go here. etc

References

  • Reference 1
  • Reference 2

Further Reading

  • Book 1
  • Book 2

See Also

  • Design System
  • Etc

External Links

By , No comments:
Tags , , , ,

Why Does Biological Evolution Work? A Minimal Model for Biological Evolution and Other Adaptive Processes

Mike's Notes

Stephen Wolfram on why biological evolution works. There is a 147-minute video and two articles. The video is below. A good introduction to evolutionary algorithms, which Pipi 9 uses. A lot of detail in the second article on examples of storing "genetic information" in adaptive evolution of machine learning.

See also the similarities and differences between evolutionary algorithms and the backpropagation algorithm.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library > Authors > Stephen Wolfram
  • Home > Handbook > 

Last Updated

19/09/2025

Why Does Biological Evolution Work? A Minimal Model for Biological Evolution and Other Adaptive Processes

By: Stephen Wolfram
Stephen Wolfram Writings: 03/05/2024

Stephen Wolfram is the creator of Mathematica, Wolfram|Alpha and the Wolfram Language; the author of A New Kind of Science; the originator of the Wolfram Physics Project; and the founder and CEO of Wolfram Research. Over the course of more than four decades, he has been a pioneer in the development and application of computational thinking—and has been responsible for many discoveries, inventions and innovations in science, technology and business.

Stephen Wolfram Readings: Why Does Biological Evolution Work?

YouTube: 2:27:28

By , No comments:
Tags , ,

Pipi 9 RBAC

Mike's Notes

This is a summary of the RBAC (Role-based access control) now used globally within Pipi 9.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

17/12/2025

Pipi 9 RBAC

By: Mike Peters
On a Sandy Beach: 18/09/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Summary

Pipi 9 uses automated RBAC (Role-based access control) to control user access to everything that has a namespace.

Pipi 10 will have additional authorisation frameworks available to be chosen by enterprise accounts.

User Account Properties

  • ID
  • Code Name
  • Namespace
  • Name
  • Default Language
  • Global authorisation framework (RBAC)
  • Account type
  • ...

Deployment Properties

  • ID
  • Code Name
  • Namespace
  • Name
  • Description
  • Language (eg English)
  • Inherited User Account
  • Deployment Class (type of tenancy)
  • ...

Workspace Properties

  • ID
  • Code Name
  • Namespace
  • Name
  • Description
  • Inherited language (eg English)
  • Inherited User Account
  • Inherited Deployment
  • Domain Model
  • Domain Model Template
  • ...

Autonomous Agent Properties

  • ID
  • Code Name
  • Namespace
  • Name
  • Description
  • Agent Type (Pipi System, Engine, Domain, Algorithm, CAS, Digital Twin, etc.
  • ...
  • Many Roles
  • Many Policies
  • ...
By , No comments:
Tags , , , ,

Media Unit Options

Mike's Notes

My developing thoughts on how Ajabbi could record and broadcast quality video. This could be used for recording seminar presentations, live streaming, office hours, interviews, and more.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

19/09/2025

Media Unit Options

By: Mike Peters
On a Sandy Beach: 17/09/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Summary

The time is coming when Ajabbi will need much better video communication for recording seminar presentations, live streaming, office hours, interviews, and other purposes.

At the moment, I'm using a laptop camera, while using Zoom, etc, or a small USB attached camera on a tripod. It works, but it could be significantly improved.

Simple and reliable

Recently, I have watched video bloggers who interview guests. Their setup is highly reliable and produces good quality images and sound. Looking at glimpses of the gear in the video, it seems that the Blackmagic Studio Camera and Rhode studio boom arm look good and are popular.

I have some older gear that will suffice for the moment, including high-quality cables, tripods, and microphones.

The gear today is much cheaper and of better quality than it was 10 years ago.

Blackmagic Studio Camera

The main issue is a decent broadcast camera that is small, can be preset and doesn't always require an operator.

"Designed for powerful SDI switchers, Blackmagic Studio Camera 4K Pro G2 adds professional 12G-SDI and 10G Ethernet connections. That's perfect when the camera is located a long distance from a switcher. There's a 12G‑SDI output and a 12G‑SDI program return input that includes camera control, talkback and tally. You also get the same powerful HDMI output with control features. Plus the 10G Ethernet connection allows all connections on a single cable for a SMPTE style workflow that's much lower cost." - BlackMagic

ATEM Mini Pro

"ATEM Mini Pro is fast to set up and easy to use. It includes 4 standards converted HDMI inputs, USB webcam out, HDMI out, Fairlight audio mixer with EQ and dynamics, DVE for picture in picture, transition effects, green screen chroma key, 20 stills media pool for titles and free ATEM Software Control. ATEM Mini Pro also includes direct recording to USB flash disks in H.264 and direct streaming via Ethernet to YouTube Live and more. There's also a multiview with 4 cameras, media, preview and program plus status of recording, streaming and audio." - BlackMagic

Blackmagic Web Presenter HD

"Blackmagic Web Presenter is a complete streaming solution that includes a professional hardware streaming engine for direct streaming via Ethernet to YouTube, Facebook, Twitter and more! Plus you can stream to the internet using Ethernet or connect a 5G or 4G phone to use mobile data! The built in USB connections also work like a webcam, so you can connect a computer and use any video software. You even get a monitoring output with video, audio meters, trend graphs and more!" -  BlackMagic

Rhode Studio Boom Arm PSA+1

"The PSA1+ is the ultimate studio boom arm for podcasters, streamers and broadcasters. Its innovative parallelogram spring design ensures ultra-smooth movement and precise microphone placement in any position, while its fully damped internal springs and neoprene arm cover eliminate mechanical noise for completely silent operation. Integrated cable management ensures your setup is tidy and its extended reach and full 360-degree rotation make it easy to position your microphone exactly where it needs to be. Take your content to the next level." - Rhode

Lighting

A simple lighting kit, preferably battery-powered LED. It needs to make anyone look decent. I need to ask around for recommendations.

Camera Lenses

The BlackMagic Studio Camera has a Micro Four Thirds aperture.

Mobility

The whole kit needs to be able to fit into a couple of rugged cases and be taken anywhere.

Gear Budget

A draft list to test my assumptions. Do they work together? Are there better options? Is anything unnecessary or missing?

Looking like $10K. Now I just need to find the money.

Role Model $NZ
Camera BlackMagic Studio Camera Pro $5,099
Switcher ATEM Mini Pro $605
Streaming Blackmagic Web Presenter HD $920
Lens Panasonic?
Mic Boom Rhode Studio Boom Arm PSA+1 $288
Lighting




Total $
By , No comments:
Tags ,
Subscribe to: Posts (Atom)