from Tuesdays in Autumn

“Before the invention of the gummed envelope in the 1830s, how did people secure their private letters?” begins the blurb on the front dust-jacket flap of a book that attempts to answer that question — Letterlocking: The Hidden History of the Letter, by Jana Dambrogio and Daniel Starza Smith. A copy arrived on Friday; I finished reading it on Sunday. Returning to the same blurb, letterlocking is defined as “the ingenious process of securing a letter using a combination of folds, tucks, slits or adhesives such as sealing wax, so that it becomes its own envelope”. The book gives an overview of a variety of the relevant techniques, illustrating them with detailed instructional diagrams and wonderful photographs of historical correspondence.

I say I finished the book — rather I finished an initial brisk skim through its text and an admiring perusal of the accompanying images. I intend to go back to it to carefully work through some of the examples and try a little letterlocking of my own. It's a lovely volume to look at, though I suspect its true merits or faults will come to light while grappling at length with its finer details.

The other book I read this week (on Thursday) was another slim volume of poetry: Pink Tongue Out, Blind Cat by María Paz Guerrero, translated from the Colombian Spanish by Robin Myers. It’s another volume I think I’ll have to return to. I confess I ordered it almost purely on the strength of its title and cover design. It didn’t prove the most successful such impulse-buy. The poems, presented with the originals and translations in parallel, have a contemporary & improvisational feel, albeit in a style that didn’t immediately draw me in. Much, if not most of their meaning eluded me. One puzzling feature of the book were italicised lines in the originals. Many of these were given in both English and Spanish in the translated text, while others were left untranslated and others still given only in English. At least some of them appear to be song lyrics: perhaps they are all interpolations of others’ words? Anyhow, some explanatory notes about them would have been a welcome addition. Just enough of it all got through to me that I will want to give it another chance or two before giving up on it.

I loved The Hitchhiker’s Guide to the Galaxy in my youth. I first encountered it in the form of the BBC TV series, which aired when I was twelve. It felt like the perfect entertainment for me at that time. I didn’t get around to reading the books until I was sixteen, when I tore through the first three volumes of the ‘trilogy’ in quick succession. While I enjoyed them very much, it seemed to me that some of the humour was already slightly stale: a little too redolent of the departed ‘70s. In my wisdom, I imagined their appeal surely couldn’t last much longer! Despite that, I still read So Long and Thanks for All the Fish a year or so later (and thought it a let-down). Around the same time, I was amused and frustrated in equal measure by the computer game adaptation of the story. I never did read Mostly Harmless. Much later, enticed by nostalgia, I eventually made the mistake of watching the Hitchhiker's Guide movie when that came out on DVD.

Having missed out on the original radio broadcasts, I’d remained slightly curious about them. On Friday I happened to find a double album version of The Hitchhiker’s Guide in a bin of bargain vinyl at a market stall, and spent £10 buying it along with two other LPs. Vexation ensued when I learned this did not contain the radio shows, but rather a somewhat abridged audio re-recording done in 1979. The irritation soon faded again when I spotted an inscription in the record’s gatefold that read “To Gordon, Best Wishes, Douglas Adams” (Fig. 31). While I’ve no provenance or authoritative opinion to back it up, I like to think it’s a genuine signature (appropriately enough done in blue biro). To my inexpert eye it does resemble other of Adams’ signatures to be found on-line. The recording itself I found only intermittently amusing, with over-familiarity having taken its toll.

At the Marches Deli in Monmouth on Friday they had yet another artisanal Welsh blue cheese (there are more than I had ever imagined!) in the shape of Trefaldwyn Blue, which is my cheese of the week. It says here that “This rich blue cheese has a lovely egg-yolk orange colouring with ample blue veining. It has a dense, buttery texture and a gentle, slightly sweet flavour, with subtle lactic notes.” I can’t argue with that.

 
Read more... Discuss...

from PlantLab.ai | Blog

What You'll Build

A Node-RED flow that captures a photo on a schedule, sends it to PlantLab for diagnosis, and takes action based on the result. Push notifications, dashboard updates, MQTT messages to your controller, log lines into InfluxDB, or whatever combination you want. No Python. No YAML. Nodes and wires.

Setup runs about 25 minutes on a Node-RED instance that's already up. The cost is whatever camera you own plus PlantLab's free tier at 3 diagnoses a day. The output is a structured JSON result: 31 possible conditions, a growth stage, nutrient antagonism hypotheses, and confidence scores, all ready to feed into whatever comes next.

Node-RED suits growers who already have their tent wired up with visual flows. If you've got temp sensors piping into an InfluxDB dashboard, MQTT switches on a power strip, or a Telegram bot that announces fan speed changes, you already know the pattern. Plant health diagnosis is just another node in the chain.

Coming from Home Assistant? There's a tutorial for that too. Node-RED gives you more granular flow control and broader protocol support. HA gives you a cleaner device-and-entity model. Both work. Pick whichever one matches the rest of your setup.

Prerequisites

Before we start:

  • Node-RED running (Docker, Pi, bare metal, or the Home Assistant add-on – any of them works)
  • A camera that can deliver a JPEG – IP camera with snapshot URL, Frigate, ESP32-CAM, Wyze with RTSP bridge, Reolink, anything that responds to an HTTP GET with a JPEG or that you can shell out to ffmpeg for
  • A PlantLab account – sign up free at plantlab.ai, copy your API key from the dashboard
  • Optional but recommended: node-red-dashboard for a visual panel, node-red-contrib-image-tools if you want to resize photos before sending, an MQTT broker if your grow controllers talk MQTT

Camera tip: shoot the canopy from above or at a slight angle, with neutral light. Blurple grow lights throw the model off because everything comes out tinted purple. Either schedule the check during a lights-off window or use the camera's built-in flash. PlantLab wants to see actual leaf color, not a magenta smear.

Step 1: The Basic Flow

Here's the smallest flow that actually does something useful. Four nodes. Inject on a schedule, pull an image from the camera, POST to PlantLab, debug-log the result.

[inject: cron 08:00] -> [http request: GET camera.jpg] -> [http request: POST plantlab] -> [debug]

Open Node-RED, drag these four nodes in, and wire them together.

The inject node

  • Repeat: at a specific time, 08:00:00
  • Payload: empty (we only need the trigger)

The camera snapshot node (HTTP request)

  • Method: GET
  • URL: your camera's snapshot endpoint, e.g. http://192.168.1.50/snapshot.jpg or your Frigate http://frigate:5000/api/grow_tent/latest.jpg
  • Return: a binary buffer

If your camera needs auth, add a basic auth header. If it's RTSP-only, use an exec node running ffmpeg -i rtsp://... -frames:v 1 -f image2pipe - and pipe the stdout through.

The PlantLab request node (HTTP request)

  • Method: POST
  • URL: https://api.plantlab.ai/diagnose
  • Return: a parsed JSON object
  • Headers: set in the function node below (not in the HTTP request node's UI)

Before this node, drop in a small function node to wrap the binary image as multipart form data and attach the API key header:

const boundary = '----NodeRedBoundary' + Date.now();
const bodyStart = Buffer.from(
    `--${boundary}\r\n` +
    `Content-Disposition: form-data; name="image"; filename="plant.jpg"\r\n` +
    `Content-Type: image/jpeg\r\n\r\n`, 'utf8');
const bodyEnd = Buffer.from(`\r\n--${boundary}--\r\n`, 'utf8');

msg.headers = {
    'X-API-Key': 'YOUR_API_KEY',
    'Content-Type': `multipart/form-data; boundary=${boundary}`
};
msg.payload = Buffer.concat([bodyStart, msg.payload, bodyEnd]);
return msg;

Put your API key in a Node-RED env variable or credentials node instead of hardcoding it. I wrote it inline for clarity.

The debug node

Hook this up to see the full response. You'll get something like this:

{
  "request_id": "req_abc123",
  "schema_version": "1.1.0",
  "success": true,
  "is_cannabis": true,
  "cannabis_confidence": 0.95,
  "is_healthy": false,
  "health_confidence": 0.87,
  "growth_stage": "flowering",
  "growth_stage_confidence": 0.9,
  "conditions": [
    {
      "class_id": "calcium_deficiency",
      "display_name": "Calcium Deficiency",
      "confidence": 0.92
    }
  ],
  "pests": [],
  "mulders_hypotheses": [
    {
      "excess": "potassium_excess",
      "explains": ["calcium_deficiency"],
      "evidence": 0.92,
      "evidence_count": 1
    }
  ]
}

The response can also include diagnostic_confidence, safety_classification, uncertainty_factors, environmental_patterns, and progression_risks. You can ignore the ones you do not need.

One thing worth knowing: the response is trimmed by omission. On a clearly healthy plant, you will NOT see a conditions: [] array – the field is left out entirely. Same with pests and mulders_hypotheses. Always guard with payload.conditions && payload.conditions.length before indexing.

Deploy. Click the inject node's button once to run it manually. If the debug panel shows a response with success: true, the plumbing is done.

Step 2: Branch on the Result

Now it gets interesting. You want different things to happen depending on what the diagnosis came back with. Drop in a switch node right after the PlantLab response, three outputs:

  • Property: msg.payload.is_healthy
  • Output 1: equals false (problem detected)
  • Output 2: equals true (all good)
  • Output 3: otherwise (covers the case where the image is not cannabis – is_healthy is omitted)

Always wire the third branch. If you accidentally point the camera at the lens cap, the wall, or your cat, the API returns is_cannabis: false with is_healthy left undefined. A two-output switch drops those silently. The third output catches them so you can log or send a “check your camera” notification instead.

Most of the work lives on the false branch.

A second switch for confidence

Inside the problem branch, add another switch:

  • Property: msg.payload.conditions[0].confidence
  • Output 1: >= 0.75 (high confidence – alert)
  • Output 2: < 0.75 (marginal – log only)

Early-stage symptoms produce lower confidences. You don't want every 0.4 nitrogen-deficiency blip triggering a Telegram ping at 3 AM.

Step 3: Notifications

Telegram

If you have a Telegram bot set up, drop a telegram sender node on the high-confidence branch. Use a template node before it to format the message:

[ALERT] Plant issue detected

Condition: {{payload.conditions.0.class_id}}
Confidence: {{payload.conditions.0.confidence}}
Growth stage: {{payload.growth_stage}}

Mulder's hypothesis: {{payload.mulders_hypotheses.0.excess}}

Discord

Swap the Telegram node for node-red-contrib-discord-advanced and point it at a webhook. Same template works.

Home Assistant (via webhook)

If you run both HA and Node-RED, Node-RED can fire an HA webhook that triggers a mobile notification with the snapshot attached:

[http request POST: http://homeassistant:8123/api/webhook/plantlab_alert]

The webhook handler in HA does the actual notification. Useful if you already have notification channels, templates, and quiet hours configured over there.

Step 4: Close the Loop

This is where Node-RED pays for itself over a static dashboard. You can fire automations directly from the diagnosis.

Auto-dose Cal-Mag on calcium deficiency

Add a switch on the condition class:

  • Property: msg.payload.conditions[0].class_id
  • Output 1: equals calcium_deficiency

Then wire a change node to set the MQTT payload and publish to your dosing pump:

[mqtt out]
  topic: grow/pumps/calmag/set
  payload: ON

Then a delay node (5 seconds), then another MQTT message flipping it back OFF. Always notify yourself when a dosing automation fires. A false positive that dumps nutrients is a bad morning to wake up to.

[set pump ON] -> [delay 5s] -> [set pump OFF] -> [notify]

Ramp up fan speed on fungal detection

If the diagnosis returns powdery_mildew or similar with high confidence, push the fan speed up and drop target humidity in your environmental controller. Same pattern – switch on class_id, change node for the new setpoint, MQTT publish.

Log everything to InfluxDB

Regardless of what happened, log every diagnosis to a time-series database so you can build dashboards later. Drop an influxdb out node on the main line, before the switches. A function node preps the fields:

msg.payload = [{
    is_healthy: msg.payload.is_healthy ? 1 : 0,
    health_confidence: msg.payload.health_confidence,
    top_condition: msg.payload.conditions[0]?.class_id || 'none',
    top_confidence: msg.payload.conditions[0]?.confidence || 0,
    growth_stage: msg.payload.growth_stage
}];
return msg;

Now you have a Grafana dashboard of plant health over time. Symptoms drift slowly over days. Watching a confidence line trending up on one specific condition is more useful than catching the single moment it crosses 0.75.

Step 5: Dashboard

With node-red-dashboard installed, you get a web UI for free. A simple panel:

  • ui_template showing the latest snapshot
  • ui_text nodes for condition, confidence, growth stage
  • ui_gauge for overall health confidence
  • A manual ui_button wired back to the inject node so you can trigger a check on demand

Drop them all in a group called “Plant Health” and they render in a grid at /ui. Pretty enough for the tablet stuck to the kitchen wall.

Putting It Together

Complete Node-RED flow: three triggers fan into GET camera, wrap multipart, POST plantlab, then is_healthy switch routes to confidence, healthy, and not-cannabis branches; confidence routes further into Telegram, HA webhook, class_id switch for cal-mag pump and fan up, plus log-only

The whole flow described in prose:

Three triggers feed the same pipeline. Two scheduled injects (morning, evening) and one manual dashboard button. Each trigger pulls a camera snapshot, wraps it as multipart, POSTs to PlantLab, and parses the JSON response. From there the signal fans out. One branch writes every result to InfluxDB so you can graph drift over time. The other branch hits switch: is_healthy. The true side logs and stops. The false side continues into a confidence switch. Low-confidence detections only log. High-confidence detections fan out into Telegram, an HA webhook, and a switch: class_id that routes specific conditions into downstream automations (cal-mag pump on calcium deficiency, fan bump on mildew, whatever you wire up).

One diagnosis call in. One structured log entry. Two scheduled checks, one manual button. Zero or more notifications, zero or more automations fired. All from five node types: inject, http request, function, switch, change.

Troubleshooting

Problem Likely cause Fix
is_cannabis: false Camera angle, blurple lights, lens cap Adjust position, use white light or flash
401 Unauthorized Missing or wrong API key Check the X-API-Key header in the wrap-multipart function node
503 Service Unavailable on upload Image over 10 MB hits the upstream limit before reaching the API Resize with node-red-contrib-image-tools before the POST. Target under 8 MB to be safe.
429 Rate Limit More than 3 requests/day or 90/month on free tier Space out injects or upgrade to Pro (500/month)
Request hangs Camera or API unreachable Add a catch node on the flow; set HTTP request timeout to 15s
conditions field absent Plant is healthy, or the image isn't cannabis, so no condition was detected Expected. Guard with payload.conditions && payload.conditions.length – the field is omitted entirely on healthy plants, not returned as an empty array.

Add a catch node wired to your alerting. When the flow itself breaks, you hear about it. Two weeks of silent green checkmarks on a flow that quietly stopped running is worse than a flow that never ran at all.

Why Node-RED Instead of Writing This in Python

A few reasons.

Protocols come free. MQTT, HTTP, WebSockets, Modbus, CoAP, serial, SNMP – all one node away. Your dosing pump speaks MQTT, your camera speaks RTSP, your logger speaks InfluxDB line protocol, alerts go to Telegram or Discord. Doing that same glue in Python means pulling in four libraries and maintaining them yourself.

Visual flows match the mental model. “When the camera sees X, send Y to the pump and notify me on Z” is already a diagram in your head. Node-RED lets you lay it out on a canvas instead of translating between code and back.

You can change a running flow. Deploy swaps it in place, no restart. Handy for grow-room automation where you tune thresholds based on what the plants actually end up doing, not what you assumed they would.

If you prefer code, the same flow is about 40 lines of Python with requests, paho-mqtt, and a cron entry. Use whichever fits.

What the API Actually Gives You

The response has every field you need for automation. The ones that matter most:

Field Type Notes
is_healthy bool The simplest switch
is_cannabis bool Guard against pointing the camera at the wrong thing
conditions array Sorted by confidence, top result first
conditions[].class_id string One of 31 possible values
conditions[].confidence float 0.0 to 1.0, maps empirically to real correctness
growth_stage string seedling / vegetative / flowering
mulders_hypotheses array Nutrient antagonism explanations

mulders_hypotheses is the block most growers end up leaning on. If the diagnosis is calcium deficiency but the hypothesis says the real cause is potassium excess, adding more cal-mag makes things worse. That's the kind of tip that saves you a week of chasing the wrong fix. More on nutrient antagonism here.

FAQ

Do I need a dedicated PlantLab Node-RED node?

Not yet. The standard http request node handles it fine. A node-red-contrib-plantlab package is on the roadmap and will collapse the multipart wrapping into one node. Until then, the function snippet above does the job.

How does this compare to the Home Assistant integration?

HA gives you entities and a config flow. Node-RED gives you wires and broader protocol reach. If your setup is already Node-RED-centric, don't force HA into the middle just for this. If you have both, let Node-RED handle the flow logic and use HA webhooks for the notifications that already work well there.

Rate limits?

Free tier: 3 per day, 90 per month. Pro: 500 per month. A home grow with morning and evening checks fits the free tier with a spare daily slot. If you're monitoring multiple tents or running high-frequency checks during flower, Pro is probably what you want.

Does 0.80 confidence really mean 80% certain?

Close to it. Over our evaluation data, a score of 0.80 lines up empirically with about 80% correctness. Worth knowing when you set automation thresholds – a 0.60 threshold fires more often than a 0.80 one, at a predictable cost in false positives. More on how we diagnose here.

Does it handle images from plant apps?

The endpoint accepts any JPEG or PNG. Grow-log app, phone gallery, file drop on a NAS – same POST, same result.

PlantLab detects 31 cannabis conditions – nutrient deficiencies, pests, diseases, environmental stress – at 99%+ accuracy in 18ms. Structured JSON out, works with anything that speaks HTTP. Free tier at plantlab.ai. HA integration is open source at github.com/plantlab-ai/home-assistant-plantlab.

 
Read more...

from PlantLab.ai | Blog

Powdery mildew on cannabis leaf - white powdery patches spreading across upper leaf surface

It looks like your plant is getting frosty. White powder spreading across the leaves, that pale shimmer catching the grow light. Then you touch it, and your finger comes away white.

That's not trichome development. That's powdery mildew – and if you're seeing it now, the infection has been active inside your plant for up to two weeks already.

Powdery mildew is one of the most misidentified conditions in cannabis cultivation – not because the advanced stage is hard to recognize, but because early-stage colonies genuinely look like trichome buildup to the untrained eye. Growers see white on their leaves and feel reassured rather than alarmed. By the time the mistake is obvious, the fungus has spread.

This guide covers visual identification at every stage, how to distinguish PM from trichomes and other lookalikes, and what to do when you find it.

Quick Identification

Powdery mildew on cannabis appears as white, flour-like patches on leaf surfaces that transfer to your finger when touched. Unlike trichomes – which are crystalline, sticky, and firmly attached – powdery mildew is fuzzy, powdery, and wipes off. It typically starts on older, lower leaves and can spread from a single infected plant to your entire grow within 5-10 days under favorable conditions.

Quick checklist: – White powdery patches on leaf surfaces (usually upper side) – Fuzzy texture, not crystalline or glittery – Transfers to your finger when touched – Wipes off with cloth (trichomes stay attached) – Started on older, lower leaves – Circular colony patterns, expanding outward

Why Powdery Mildew Is So Destructive

The Timing Problem

Powdery mildew is caused by obligate biotrophic fungi – primarily Golovinomyces species (formerly classified as Erysiphe) – that require a living plant host to survive. As an obligate biotroph, the fungus spends its first 7-10 days growing inside plant tissue, establishing a mycelial network before producing the visible white sporulation on the surface.

The practical implication: by the time you see powdery mildew, you're already two weeks behind.

This timing overlaps with the worst possible moment in the grow cycle. PM typically produces visible symptoms approximately two weeks into flowering – when plants are at their most developed and most valuable. A disease that becomes visible at week two of a nine-week flower has seven weeks to damage a mature crop.

The Spread Problem

Once sporulating, powdery mildew spreads through airborne spores called conidia. Unlike many fungal diseases that require water droplets to spread, PM spores travel through air and remain viable in typical grow room conditions. A single infected plant can contaminate an entire facility within 5-10 days.

This is not a slow disease. It spends two weeks being invisible, then spreads rapidly.

Visual Symptoms by Stage

Days 1-7: No Visible Symptoms

The fungal network is developing inside plant tissue. Nothing is visible externally. The only detection method during this phase is molecular PCR testing – available commercially but not practical for most growers as a daily routine.

What to do: Prevention only. No reactive treatment exists for pre-symptomatic infection.

Days 7-14: Early Visible Stage

Early powdery mildew on cannabis - small white chalk-dust spots on older leaf

What you see: – Fine white coating on upper leaf surface, often concentrated near veins – Circular “chalk-dust rings” as colonies grow radially from infection points – Small, discrete white spots (1-5mm diameter) resembling flour or powdered sugar – Patches separated by healthy-looking green tissue initially

This is when intervention is most effective. Catching PM at this stage – and responding within 48 hours – gives you the best chance of containing the infection before airborne spread reaches other plants.

Days 14+: Advanced Stage

Advanced powdery mildew - merged colonies covering cannabis leaf with yellowing

What you see: – Spots grow larger and merge into confluent white coverage – Thick, prominent coating across entire leaf surfaces – Fuzzy, hair-like texture that can resemble spider webs or white cotton candy in severe cases – Affected leaves turn yellow (chlorosis) as photosynthetic capacity is reduced – Leaf death and necrosis in severely affected tissue – Contamination of flower bracts and bud sites

At this stage, individual plant treatment may still limit damage, but facility-wide spread is likely already underway.

Where to Look: Detection Hotspots

Not all areas are equally at risk. Focus visual inspections here:

Check first: – Upper surfaces of older, lower leaves – Corners with poor airflow – Areas where leaves touch each other – Near the base of the plant

Check second: – Lower leaf surfaces – Leaf petioles and stems – Flower bracts and bud sites – Plants adjacent to any previously infected individual

High-risk conditions: – Humidity above 60% (optimal for PM at 95%+) – Temperature 68-86°F (20-30°C) – Poor air circulation or stagnant air pockets – Overcrowded plants with leaf-on-leaf contact – Recently introduced plant material (a common entry point)

One counterintuitive note: many growers assume low humidity prevents powdery mildew. It slows initial infection, but once PM is established, the fungus can continue growing even below 50% relative humidity. Humidity reduction is a preventive tool, not a cure.

Powdery Mildew vs. Trichomes: The Critical Distinction

This comparison matters because the error goes in both directions – growers see PM and think “good frost,” and they sometimes see heavy trichome coverage and worry it's disease.

Feature Powdery Mildew Trichomes
Texture Fuzzy, powdery, matte Crystalline, glittery
Color White to gray (can look dirty) Translucent to milky white
Touch test Transfers to finger, feels dusty Sticky, doesn't transfer
Wipe test Wipes off as powder Firmly attached
Shape Irregular patches with fuzzy edges Distinct mushroom stalks (under magnification)
Location Any leaf surface, starts on older lower leaves Concentrated on flowers and sugar leaves
Distribution Random colonies expanding outward Uniform coating across surface
Smell Musty in advanced infection Resinous, aromatic

Side by side comparison: powdery mildew vs. trichomes on cannabis

Three Tests to Confirm

Touch test. Lightly rub the white area with your finger. PM transfers as a dusty powder. Trichomes are sticky and stay on the plant.

Wipe test. Try to wipe the coating with a cloth. PM wipes off cleanly. Trichomes remain attached.

Magnification (10x loupe). Under magnification, trichomes show distinct mushroom-shaped heads on uniform stalks. PM looks like fuzzy, irregular filaments with no consistent structure.

If you're unsure after all three tests, assume it's PM and treat accordingly. The cost of a false positive – treating a healthy plant – is much lower than the cost of a false negative.

Distinguishing From Other Conditions

Powdery Mildew vs. Bud Rot (Botrytis)

Both can appear during flowering, but they start in different places and look different up close.

  • PM: Starts on leaf surfaces as white powder, spreads outward
  • Bud rot: Starts inside dense bud tissue as gray-brown mold, spreads inward
  • PM: Dry, wipes off as powder
  • Bud rot: Slimy, penetrates tissue, leaves mushy gray-brown areas when probed

Powdery Mildew vs. Spider Mite Webbing

Heavy spider mite webbing can be confused with PM in advanced stages.

  • PM: Powdery coating directly on leaf surfaces, no web structure
  • Webbing: Actual filamentous strands connecting leaves and stems, visible as a network with tiny mites present
  • PM: Surface phenomenon on the leaf
  • Webbing: Spans between plant structures

Powdery Mildew vs. Fertilizer Residue

Spray residue and fertilizer salt deposits are a common false positive.

  • PM: Fuzzy texture, grows and expands over days
  • Residue: Crystalline, stays fixed, doesn't spread
  • PM: Circular colonies from infection points
  • Residue: Irregular splatter pattern matching where spray landed

Treatment and Prevention

If You've Found It: Immediate Steps

  1. Isolate the infected plant. Remove it from the grow space carefully – don't shake the leaves, which disperses spores.
  2. Remove heavily infected leaves. Seal them in a bag before removal. Dispose of, don't compost.
  3. Increase airflow immediately. Run oscillating fans, check that exhaust is adequate.

  4. Apply treatment to the infected plant and all immediate neighbors:

    • Potassium bicarbonate spray (effective at any stage, flower-safe)
    • Copper-based fungicides (veg stage only)
    • Neem oil (veg stage only – off-gasses problematically in flower)
    • Commercial PM treatments labeled as flower-safe for late-stage infections

  5. Inspect every other plant in the grow. Assume airborne spread has already occurred. Look for early colonies on older lower leaves of adjacent plants.

Prevention

Environmental control (most effective): – Maintain humidity below 60%, below 45% in late flower – Install oscillating fans for continuous air movement – Prevent leaf-on-leaf contact through spacing and selective defoliation – Maintain stable temperature – fluctuations create favorable infection windows – Consider HEPA filtration between grow cycles to reduce ambient spore load

Cultural practices: – Inspect plants daily, particularly lower leaves and poor-airflow corners – Quarantine any new plant material for at least two weeks before introducing to your grow – Sterilize tools between plants – Remove dead leaves promptly – they create moisture pockets

Preventive treatments (before symptoms appear): – UV-C light treatment between grow cycles kills residual spores – Preventive potassium bicarbonate or copper sprays provide significantly better protection than reactive treatment after symptoms appear – IPM programs that address PM as a standing preventive protocol, not a reactive one

How AI Detection Works

Powdery mildew is fundamentally a texture classification problem – distinguishing the powdery, irregular surface of PM colonies from the crystalline structure of trichomes and the smooth surface of healthy leaf tissue.

PlantLab's model analyzes:

  • Color contrast: White patches against green leaf tissue create a high-contrast signal the model identifies reliably
  • Texture signature: PM colonies have a granular, matte surface texture measurably distinct from trichomes (crystalline) and healthy leaf (smooth with natural sheen)
  • Colony geometry: PM grows in circular patterns from infection points with fuzzy, irregular edges – different from the uniform distribution of trichome coverage
  • Location context: Where on the plant the pattern appears matters; PM preferentially affects older, lower leaves in early infection

Early-stage detection – colonies as small as 5mm – catches infection when treatment options are broadest. Automated daily scanning catches what manual inspection misses when you're managing more than a few plants.

Try it free at plantlab.ai – 3 diagnoses per day, no credit card required.

FAQ

Can I smoke buds with powdery mildew? No. PM spores and fungal material can cause respiratory issues, particularly for anyone with lung conditions or compromised immunity. Infected flower should be disposed of, not consumed.

Does powdery mildew spread to other plants? Yes, rapidly. Airborne spores can reach every plant in a contained grow space within 5-10 days under favorable conditions. Isolate infected plants immediately and inspect everything nearby.

Can plants recover from powdery mildew? Mildly infected plants can survive and produce with aggressive treatment, but affected tissue doesn't recover. The goal is to stop the spread. Heavily infected plants in late flowering are usually a loss.

Does lowering humidity kill powdery mildew? It inhibits new infection but doesn't eliminate established colonies. PM can remain active even below 50% relative humidity once established. Humidity reduction is a prevention tool, not a cure for active infection.

When is powdery mildew most likely to appear? Typically around two weeks into flowering, when dense bud sites create microclimates with trapped humidity and reduced airflow. It can appear at any life stage given favorable conditions, but flowering onset is the highest-risk window.

PlantLab's AI detects 31 cannabis conditions – including powdery mildew, bud rot, and 7 specific nutrient deficiencies. Start diagnosing free at plantlab.ai.

 
Read more...

from PlantLab.ai | Blog

Bud rot and root rot in cannabis - two diseases that spread faster than growers react

You won't smell it at first. By the time you do – that damp, musty sweetness coming off a cola that looked fine yesterday – you've already lost that bud and probably the ones touching it. You cut it open, and the inside is grey mush. A week from harvest.

Bud rot. It colonizes from the inside out, hiding in the densest parts of your canopy where airflow is worst and humidity is highest. By the time the exterior shows damage, the interior has been decomposing for days.

Root rot is the same story, underground. A plant that was drinking normally starts drooping despite a wet medium. You check the roots and they're brown, slimy, and smell like a swamp. The pathogen has been destroying the root system for a week before the canopy showed a single symptom.

What they share: the window between “detectable” and “devastating” is days, not weeks. Nutrient deficiencies give you time. Pest infestations give you time. Rot doesn't. It doubles and doubles, and by the time most growers catch it, the only option left is damage control.

Quick Identification

Bud rot is caused by Botrytis cinerea, a fungus that colonizes dense flower clusters from the inside out. The first thing you'll notice: a sugar leaf or two within a cola turning yellow or brown while everything around it stays healthy. That isolated patch of dead tissue – not matching any nutrient pattern – is your warning. Pull the bud apart and you'll find grey or brown tissue, soft and wet, with grey-white fuzz (mycelium) growing through it.

Root rot comes from several pathogens – water molds like Pythium (especially common in hydro) and true fungi like Fusarium (which hits both soil and hydro). The first sign is a plant that droops for no obvious reason even though you just watered. Growth slows. Roots shift from white to tan or brown. By the time the roots are dark brown, slimy, and smell rotten, the plant may not recover.

What separates rot from everything else: it's local. One cola dying while the rest of the plant looks fine. One section of roots going brown while others stay white. Nutrient deficiencies hit the whole plant uniformly. Rot has an epicenter.

Bud Rot: What to Look For

The Inside-Out Problem

Bud rot starts where you can't see it. Botrytis spores land on flower tissue, germinate in the humidity, and go straight for the densest part of the bud – the interior, where moisture sits longest. Outside? Green and healthy. Inside? Grey mush.

Doesn't matter how many cycles you've run. You can eyeball your canopy every day and miss it completely, because the infection is in the one place a surface inspection doesn't reach.

Early Symptoms (Day 1-3)

The first visible sign is almost always a single sugar leaf – or a small cluster of them – within a cola that yellows and wilts while the rest of the bud stays green. This is easy to dismiss as a light-deprived leaf dying naturally. It isn't.

What to look for: – A single yellowing/browning leaf within an otherwise healthy cola – The leaf pulls out easily with a slight tug (the stem base is already rotting) – The area around the discolored leaf feels softer or more moist than adjacent tissue – A faint musty smell when you press your nose close to the bud

Moderate Symptoms (Day 3-7)

  • Brown or grey tissue visible when you gently spread the cola apart
  • Multiple leaves in the same bud turning yellow or brown
  • White or grey fuzzy mycelium visible inside the bud under magnification
  • The affected area feels distinctly wet or spongy

Advanced Symptoms (Day 7+)

  • Grey mold visible on the bud exterior
  • Bud tissue is soft, wet, and pulls apart easily
  • Dark brown or black discoloration spreading to adjacent colas
  • Spore dust (grey powder) released when the bud is disturbed
  • Unmistakable musty or ammonia smell

At this point, that bud is gone. Everything you do now is about keeping it from spreading.

Where Bud Rot Hits First

Bud rot isn't random. It goes where the moisture is:

Your main cola. Any thick, tightly-packed bud where moisture can't escape. Spots deep in the canopy where leaves overlap and trap humidity. Anywhere a fan leaf rests against a bud, creating a little moisture pocket. And anywhere the bud surface is already damaged – caterpillar bore holes, supercrop scars, anything that gave the fungus a way in.

If you're only going to inspect one thing daily in late flower, make it the main cola and any bud that's touching a fan leaf. That's where bud rot lives.

Root Rot: What to Look For

The Drooping Paradox

Root rot looks like underwatering. Plant's drooping, so you water it. The drooping gets worse, so you water more. And now you're feeding the exact conditions that are killing the roots.

The tell: is the medium already wet? Overwatering droop and root rot droop look identical from the canopy. The answer is always below the surface.

Early Symptoms (Day 1-5)

  • Drooping or wilting even though the medium is wet
  • Slowed growth rate compared to other plants in the same environment
  • Roots shifting from bright white to off-white or light tan
  • Slight sour or stale smell from the root zone (especially in hydro)

Moderate Symptoms (Day 5-14)

  • Roots turning brown and developing a slimy texture
  • Leaves yellowing from the bottom up (mimics nitrogen deficiency)
  • Plant drinking less water than expected for its size
  • Stems near the base feeling soft or mushy
  • Distinct foul odor from the root zone

Advanced Symptoms (Day 14+)

  • Dark brown, mushy root mass that falls apart when touched
  • Severe wilting that doesn't recover with watering
  • Lower leaves dropping rapidly
  • Base of stem may show brown discoloration
  • The entire root zone smells of decay

Hydro vs Soil vs Coco

Root rot behaves differently across growing media:

Factor Hydroponic (DWC/NFT) Coco Coir Soil
Primary pathogen Pythium (also Fusarium) Pythium / Fusarium Fusarium / Phytophthora
Speed of onset Fast (2-5 days) Moderate (5-10 days) Slow (7-14 days)
First sign Slimy roots, off smell Drooping, slow drying Persistent droop
Temperature trigger Reservoir > 22C / 72F Overwatering + warm Overwatering + poor drainage
Visibility Easy (roots exposed) Moderate (can pull back medium) Hard (roots buried)

Hydroponic growers have one advantage here: you can actually see the roots. Check them daily. One brown root tip caught early is a ten-second trim. Caught late, it's a dead plant.

Why Speed Matters More Than Treatment

Most treatment guides bury the uncomfortable truth: by the time you've confirmed rot, your best options are already behind you. Both conditions double fast once established, and the pathogens produce spores (bud rot) or zoospores (root rot) that reinfect tissue you've already treated.

For bud rot: – Day 1-3: Remove affected cola plus 2-3cm of healthy tissue around it. Sterilize cutting tool between cuts. Drop humidity below 50%. Increase airflow. The remaining harvest is likely safe. – Day 4-7: You're removing multiple colas. Some adjacent buds may be internally compromised but not yet showing symptoms. Harvest early if possible. – Day 7+: Salvage what you can. Anything near the infected area should be assumed compromised.

For root rot: – Early stage: Hydrogen peroxide root drench (3ml of 3% H2O2 per liter for mild cases, up to 5ml/L for aggressive treatment), drop reservoir temperature below 20C / 68F, increase dissolved oxygen. Beneficial microbes (Bacillus, Trichoderma) as a preventive – not a cure, but they compete with pathogens. Note: H2O2 kills beneficials too, so don't use both simultaneously. – Moderate stage: Root pruning (remove all brown tissue), full reservoir change, lower temperature, and hope the remaining root mass can support the plant. – Advanced: The plant is dying. What's left of the root system can't support it. Sometimes the honest move is to pull it and focus on the plants you can still save.

Every day you don't catch it, your options get worse. Two days is the difference between losing one cola and losing a quarter of the canopy.

How to Distinguish Rot from Other Problems

Early rot symptoms can look like nutrient deficiencies, overwatering, or heat stress. The giveaway is where the damage is concentrated.

Rot vs other problems comparison chart

Symptom Bud Rot Root Rot Nitrogen Deficiency Overwatering
Affected area Single cola or bud site Whole plant from bottom up Whole plant, lower leaves first Whole plant
Symmetry Asymmetric – one point of origin May be symmetric Symmetric Symmetric
Progression Spreads from one spot outward Bottom-up canopy decline Bottom-up, gradual Uniform droop
Smell Musty, damp Sour, foul root zone None None
Physical touch test Soft, wet bud interior Brown, slimy roots Leaves feel normal Leaves feel heavy
Recovers with adjustment No – removal is the only fix Rarely once advanced Yes, within days Yes, within hours

If damage is spreading from one spot and doesn't respond to feed or environment changes – treat it as rot. Verify later. You don't have time to be wrong slowly.

Environmental Triggers

Rot is an environmental disease. The pathogen is probably already in your grow room – Botrytis spores are everywhere. But it needs specific conditions to take hold.

Bud Rot Triggers

  • Humidity above 60% during flower – this is the one that matters most
  • Poor airflow through the canopy, especially within dense colas
  • Temperature swings that cause condensation on flower tissue (lights-off drops are the usual culprit)
  • Dense genetics – strains bred for bag appeal often produce bud structures that trap moisture
  • Late flower, week 6-8, when buds are at their densest and you're tired of babysitting the dehumidifier

Root Rot Triggers

  • Reservoir temperature above 22C / 72F in hydro – this is the big one
  • Overwatering in any medium, especially with poor drainage
  • Low dissolved oxygen in the root zone
  • Contaminated medium or tools (reusing coco without sterilizing, dirty res)
  • Dead organic matter sitting in the reservoir

The 60/22 Rule

Two numbers. That's all you need to remember: flower room humidity below 60%, reservoir temperature below 22C / 72F. Not arbitrary – those are the inflection points where Botrytis and Pythium growth rates drop off hard. Stay below them and you're making it difficult for the pathogen. Go above and you're rolling out a welcome mat.

Catching It Before You Can

With rot, speed is the whole game. Early symptoms look like half a dozen other things, and most growers burn their response time treating the wrong problem.

PlantLab's vision model detects both bud rot and root rot as distinct conditions. You get a specific diagnosis with a confidence score, not “something might be wrong with your plant.” The model was trained exclusively on cannabis images – over 2,000 verified bud rot samples alone – across every severity stage from the first discolored leaf to full colonization.

If you're growing one plant, daily inspection is enough. But for a larger canopy – or if you're running cameras on a timer – a system that flags bud rot at 6 AM on a Tuesday before you walk into the room is worth having.

Try it free at plantlab.ai.

FAQ

How fast does bud rot spread?

Fast. An entire cola can go from first visible symptom to grey mush in 48-72 hours under favorable conditions (humidity above 60%, poor airflow). During that window, spores are landing on neighboring buds and starting new infections that won't show for days. Inspect your densest colas daily in late flower. There's no substitute.

Can you save a bud with rot?

No. Once Botrytis is inside the flower structure, that bud is done. Cut the affected cola plus a margin of healthy tissue around it, sterilize your tool between cuts, and get humidity down. Everything after detection is about containment, not cure.

Does hydrogen peroxide cure root rot?

It kills Pythium on contact, but it also nukes every beneficial microbe in the root zone. Think of it as a reset button, not a treatment plan. Use it alongside temperature correction (below 22C / 72F) and better oxygenation. Once most of the roots are brown and slimy, H2O2 won't save the plant – there's not enough healthy root mass left to recover from.

Why does my plant droop even though the soil is wet?

Rotting roots can't absorb water even when they're sitting in it. The plant wilts, you water more, the root zone stays waterlogged, and the pathogen thrives. If a plant droops and the medium is already wet, stop watering and check the roots.

Can bud rot spread to other plants?

Absolutely. Botrytis cinerea produces airborne spores, and disturbing an infected bud – touching it, cutting it, even a fan blowing across it – sends them into the air. They land on neighboring plants and start the cycle over. When you remove infected colas, work carefully and bag the tissue immediately. Some growers hit neighboring plants with a preventive fungicide application after removal, which isn't a bad idea.

 
Read more...

from PlantLab.ai | Blog

Spider mites on cannabis - by the time you see webbing, you're already losing

You adjusted your cal-mag for two weeks. The yellowing got worse. Then you saw the webbing.

That's how most growers discover spider mites – not when the problem starts, but when it's already out of control. The early damage looks so much like a nutrient deficiency that your first instinct is to adjust the feed. Meanwhile, a single female mite is producing thousands of descendants in a month.

Spider mites are the most destructive pest in indoor cannabis cultivation. Not because they're hard to kill – they aren't, when caught early – but because their early symptoms mimic nutrient problems so convincingly that growers lose their detection window treating the wrong thing entirely.

This guide covers visual identification at every stage, how to tell mite damage from a deficiency, and what actually works for treatment.

Quick Identification

Spider mites on cannabis produce tiny yellow or white speckles (stippling) on upper leaf surfaces where mites feed from below. Unlike nutrient deficiencies – which cause broad, uniform color changes across leaves – stippling appears as distinct pinprick dots scattered irregularly across the leaf. The damage is caused by Tetranychus urticae (two-spotted spider mite), an arachnid that punctures individual plant cells and drains their contents. By the time webbing is visible, the colony has been feeding for weeks.

Quick checklist: – Tiny yellow/white pinprick dots on upper leaf surface – Dots are irregular and scattered, not following veins – Leaf undersides show tiny moving specks (mites are 0.3-0.5mm) – Fine webbing between leaf tips or at branch junctions (advanced) – Damage starts on lower/inner canopy where airflow is poorest – Leaves eventually bronze, curl, and drop

Why Spider Mites Are So Hard to Catch

They look like a nutrient deficiency

The single most common spider mite mistake has nothing to do with treatment. It happens at identification.

Early stippling – those tiny yellow dots where mites have punctured cells – looks like the beginning of a calcium deficiency or light stress. The dots are small, scattered, and appear on older growth first. A grower sees yellowing dots on lower leaves and reaches for the cal-mag bottle. Two weeks of feed adjustments later, the dots have spread, the plant looks worse, and then the webbing appears.

This is not a knowledge failure. It's a pattern recognition problem. The visual difference between early mite stippling and early nutrient deficiency is subtle enough that experienced growers miss it regularly.

Spider mites vs nutrient deficiency comparison chart

Feature Spider Mite Stippling Calcium Deficiency Magnesium Deficiency
Pattern Irregular pinprick dots Irregular brown spots Interveinal yellowing
Distribution Scattered randomly across leaf Concentrated on newer growth Starts on older leaves
Symmetry Asymmetric, random Roughly symmetric Symmetric between veins
Leaf underside Tiny mites or eggs visible Clean Clean
Texture Leaf feels slightly rough/gritty Spots may feel crispy Leaf stays smooth
Progression Dots multiply, never merge into bands Spots expand and merge Yellowing expands between veins
Touch test Gritty feel from mite debris Normal Normal

The diagnostic key: flip the leaf over. Nutrient deficiencies don't leave anything on the underside. Spider mites leave everything there – adults, eggs, shed skins, webbing. A 10x loupe makes this definitive, but even a phone camera zoomed in on the leaf underside will show the difference.

They breed fast enough to outrun your diagnosis

Spider mites reproduce faster than almost any pest a cannabis grower will encounter.

  • Generation time: 7 days at 30°C (86°F). Egg to egg-laying adult in one week.
  • Reproductive rate: A single female lays up to 100 eggs. Her daughters start laying within a week.
  • Population math: One mite becomes thousands in a month at optimal temperatures. Two months of unchecked growth reaches millions.

This is exponential growth in the literal sense. The population you can't see on Monday is visible by Friday and webbing by the following Monday. The detection window – the gap between “early enough to treat easily” and “too late for simple solutions” – is approximately 5-7 days.

Every day of misdiagnosis as a nutrient issue is a day lost in that window.

Visual Symptoms by Stage

Spider mite infestation timeline - 4 stages from invisible to severe

Days 1-7: Invisible Phase

Mites have arrived but the colony is small. Fewer than 10 adults on the plant. No visible damage to the naked eye.

What to look for: Nothing you can see without magnification. Preventive inspection with a 10x loupe on leaf undersides is the only detection method during this phase – or an AI that can catch the earliest stippling pattern in a leaf photo before your eye does.

Days 7-14: Early Stippling

What you see: – Scattered yellow-white dots on upper leaf surfaces – Dots are pinprick-sized, irregular spacing – Lower and inner canopy leaves affected first – Leaves may appear slightly dull or dusty

This is the critical detection window. The damage is visible but the population is still manageable. Treat now and you win. Wait, and you're chasing exponential growth.

What growers confuse it with: Calcium deficiency, magnesium deficiency, early light stress, pH fluctuation damage. The distinguishing test: check the leaf underside with a loupe or zoomed phone camera.

Days 14-21: Moderate Infestation

What you see: – Stippling thickens into visible patches of yellow/bronze discoloration – Fine webbing appears at leaf tips and where leaves meet stems – Leaf edges may curl upward – Multiple plants now show symptoms (airborne spread via “ballooning” on silk threads)

Webbing marks the transition from “problem” to “crisis.” The silk isn't just housing – it protects colonies from predators and spray treatments. Once webs are established, contact sprays have to penetrate the silk to reach the mites.

Days 21+: Severe Infestation

What you see: – Dense webbing covering bud sites, connecting leaves – Leaves are bronzed, curled, and dropping – Mites visible as tiny moving dots on webbing – Plant growth has visibly slowed or stopped – Webbing on flowers makes bud unusable

At this stage, the plant is losing more photosynthetic capacity than it can replace. During flower, this level of infestation is often a total crop loss for affected plants. The mites are feeding on sugar leaves and bract tissue, leaving webbing embedded in the flower structure. Even if you kill every mite, the webbing and fecal matter remain.

Where to Look: Detection Hotspots

Spider mites prefer warm, dry, still air – the conditions that exist in the center and lower canopy of most indoor grows.

Check first: – Undersides of lower and inner canopy leaves – Where two leaves overlap (creates still-air microclimate) – Near intake vents (common entry point) – Any plant closest to heat sources

Check second: – Leaf undersides on middle canopy – Branch junctions where stems create sheltered pockets – Nearby houseplants, clones, or recently introduced plant material

High-risk conditions: – Temperature above 27°C (80°F) and rising – Humidity below 40% RH – Stagnant air in lower canopy – New clones or plants introduced without quarantine – Adjacent rooms or gardens with ornamental plants

One fact most growers don't realize: spider mites travel on clothing, pets, and skin. If you've been in a garden with mites and walk into your grow room, you may be the vector. This is why quarantine protocols matter even for indoor-only grows.

They're arachnids, not insects

This matters more than you'd think. Spider mites aren't insects. They're arachnids – closer to ticks and spiders than to aphids or thrips. A lot of insecticides just don't work on them, and growers figure this out the expensive way: they buy whatever pest spray the grow shop recommends, apply it twice a week for a month, and the mites keep spreading.

If a product label says “insecticide” but doesn't specifically list mites or arachnids, it probably won't work. You need a miticide (specifically targets mites) or a broad-spectrum acaricide (targets arachnids generally). Some biologicals and organic options work by physical mechanisms – suffocation, desiccation – that don't depend on the pest's taxonomy. These are often the safest first-line choice.

Treatment Strategies

They evolve faster than you can spray

Spider mites develop pesticide resistance at a rate that makes most agricultural pests look slow. With a 7-day generation cycle, resistance emerges in weeks, not seasons. Some strains of T. urticae are resistant to dozens of active ingredients simultaneously.

Worse: some pesticides cause “mite flaring” – the surviving mites respond to the chemical stress by increasing their reproductive rate by up to 30%. The intuitive response of “spray harder, spray more” can accelerate the infestation rather than control it.

Single-product treatment strategies fail. Always rotate between different modes of action.

During Vegetative Growth

Immediate response (first 48 hours): 1. Isolate affected plants if possible 2. Remove and dispose of heavily infested leaves (bag them, don't compost) 3. Spray leaf undersides thoroughly with a contact miticide or biological

Biological controls: – Phytoseiulus persimilis – predatory mite that feeds exclusively on spider mites. Effective in vegetative growth and early flower. Needs humidity above 60% to thrive. – Neoseiulus californicus – predatory mite that tolerates lower humidity and also eats thrips. Better for dry grow rooms. – Amblyseius andersoni – generalist predatory mite, survives without prey by eating pollen. Good for preventive releases.

Organic sprays (moderate infestations): – Neem oil (azadirachtin) – disrupts feeding and reproduction. Apply to leaf undersides only. Do not use in flower – affects taste and may not fully degrade. – Insecticidal soap (potassium salts of fatty acids) – kills on contact by desiccation. Must directly contact the mite. Repeat every 3-5 days for 3 applications to catch new hatchlings. – Spinosad – organic-approved, effective on thrips but weak against mites on its own. Can supplement a rotation but shouldn't be a primary miticide.

Spray rotation protocol: – Week 1: Product A (e.g., insecticidal soap) – Week 2: Product B (e.g., neem oil) – Week 3: Product A again (or a different miticide) – Never use the same active ingredient twice in a row

During flower

This is where most growers panic, and for good reason. During flower, almost everything that kills mites also ruins buds.

Safe in flower: – Predatory mites (biological control – no residue, no taste impact) – Water rinse with slightly elevated pressure (dislodges mites physically, must reach undersides) – Cold snap trick: drop temperature to 15°C (60°F) for 3 days if possible. Mite reproduction nearly stops below 18°C (65°F). This buys time for predatory mites to work.

Avoid in flower: – Neem oil (taste contamination, doesn't fully degrade on flower tissue) – Pyrethrin sprays (residue on buds) – Sulfur (burns trichomes, affects terpenes) – Any systemic product (absorbed into plant tissue including flower)

If webbing is on buds: The honest answer is that those buds are compromised. Webbing contains fecal matter and shed mite skins that don't wash off. You can salvage the plant by removing affected flowers and protecting remaining buds with predatory mites, but heavily webbed buds should be discarded.

Prevention

A few euros spent preventing mites saves hundreds in lost crop. Prevention beats treatment every time, especially with a pest that breeds this fast.

Environmental controls: – Keep humidity above 50% RH during veg (mites thrive in dry conditions) – Ensure airflow reaches the lower canopy (oscillating fans, open plant structure) – Run temperatures below 27°C (80°F) when possible – HEPA filter on intake if growing in an area with outdoor mite pressure

Good habits: – Quarantine new plants for 7-14 days before introducing to your grow – Change clothes before entering grow room if you've been in other gardens – Inspect leaf undersides weekly with a 10x loupe – make it routine, not reactive – Remove dead leaves and debris from the grow space (harboring sites) – Avoid overly dense canopy – defoliate lower growth that gets no light and creates still-air pockets

Preemptive predators: – Release Amblyseius andersoni or N. californicus at transplant. These predatory mites establish a background population that intercepts spider mites before colonies form. Cost: roughly €20-30 per release for a small grow, every 4-6 weeks.

How AI detection changes the timeline

The spider mite problem is a timing issue. The window between “just arrived” and “exponential growth” is about 5-7 days. Most growers catch mites after stippling is already obvious – right at the edge of that window, or past it.

The main reason growers miss that window isn't inattention. Early stippling – those first scattered yellow dots where mites have punctured cells – looks almost identical to the start of a calcium or magnesium deficiency. Same distribution, same size, same location on older growth. A grower sees the dots, checks pH, adjusts the feed, and waits a week for results. By the time the nutrient hypothesis is ruled out and a loupe comes out, mites have had 7-10 days of uncontested growth. At one generation per week, that adds up.

PlantLab's model covers 31 cannabis conditions including spider mite damage. It catches the stippling pattern at the 10-dot stage, from a routine photo. Not a replacement for the loupe – nothing is – but it flags the pattern before you've mentally filed it as “probably cal-mag” and moved on.

Catching mites at day 7 instead of day 14 is the difference between wiping down some leaves and losing a crop.

Free at plantlab.ai – 3 checks a day.

FAQ

How do I tell spider mite damage from a nutrient deficiency? Flip the leaf. Spider mite damage shows as scattered pinprick dots on top with mites, eggs, or webbing underneath. Nutrient deficiencies cause broader color changes with clean leaf undersides. A 10x loupe on the underside is the definitive test.

Can I see spider mites without a magnifying glass? Adults are barely visible to the naked eye (0.3-0.5mm) as tiny moving specks on leaf undersides. Eggs and juveniles are too small to see without magnification. By the time mites are easily visible, the colony is large. Use a loupe or phone camera zoom for early detection.

How fast do spider mites spread between plants? In optimal conditions (above 27°C / 80°F, below 40% RH), mites can move from one plant to adjacent plants within 24-48 hours. They also “balloon” on silk threads carried by air currents, reaching plants across a room. A single infested plant can become a room-wide problem in 5-10 days.

Will neem oil get rid of spider mites? Neem works as part of a rotation, not as a standalone. It disrupts feeding and reproduction but doesn't kill on contact, and mites build resistance to it quickly. Rotate with insecticidal soap and other modes of action. And never use it during flower – it doesn't come off.

What kills spider mites instantly? Insecticidal soap and pyrethrin kill on contact, but only what they touch. You'll miss eggs. Plan for 3 rounds over 2 weeks to catch hatching cycles.

 
Read more...

from PlantLab.ai | Blog

Fungus gnats on cannabis - small dark flies over damp topsoil with translucent larvae in the medium, botanical illustration

Every time you water, a little cloud of dark flies lifts off the soil, drifts around, and settles back down. They do not bite, they do not swarm the plant, and every forum thread calls them harmless. So you ignore them.

Meanwhile the plant is drooping. Lower leaves are yellowing, growth has slowed, and nothing about your feed or pH explains it. You start treating for overwatering, maybe root rot – and the real cause is still hovering over the pot.

Fungus gnats are the most under-estimated pest in indoor growing. The adults genuinely are close to harmless. The problem is their larvae: tiny translucent worms living in the top layer of wet medium, feeding on root hairs and opening wounds that let real root pathogens in. Because the above-ground symptoms look exactly like a watering or root problem, growers spend weeks fixing the wrong thing while the population builds.

Clearing them is not hard once you know what you are looking at. Getting there is the hard part – past the assumption that the flies are harmless and the droop is just a watering mistake. Here is how to confirm it is gnats, rule out the problems they mimic, and break the cycle instead of swatting adults forever.

Quick identification

Fungus gnats are small dark flies, 2-4mm, that stay near the surface of damp soil and fly weakly in short hops when disturbed. The damage is done by the larvae – translucent, thread-thin worms with a distinct black head – which live in the top 1-2cm of the medium and feed on fine roots.

Quick checklist:

  • Small dark flies hopping or drifting just above the topsoil
  • Flies lift off when you water or disturb the pot, then resettle
  • Adults stuck to yellow sticky cards placed near the medium
  • Translucent larvae in the top layer of soil when you scratch it back
  • Droop and lower-leaf yellowing that watering changes do not fix
  • Topsoil that stays wet for days between waterings

The decisive check is simple: are there flies at the soil surface, and is the medium consistently wet? Two yeses is fungus gnats until proven otherwise. Scratch back the top centimetre and look for the larvae to confirm.

Why fungus gnats get misdiagnosed

Fungus gnats damage roots, and root damage above ground looks like every other root problem: droop, slowed growth, yellowing that creeps up from the bottom. So the symptoms get filed as overwatering or root rot, and the flies get dismissed as a coincidence.

The three conditions live in the same wet-soil neighbourhood, which is exactly why they get confused – and often why they show up together. Chronically wet medium is what invites gnats, drowns roots, and breeds rot all at once.

Feature Fungus gnats Overwatering Root rot
Flies at soil surface Yes No No
Wet, slow-draining medium Yes Yes Usually
Wilt pattern Yellowing, gradual droop Puffy droop after watering Persistent wilt, does not recover
Roots Nibbled fine roots, entry wounds Pale, waterlogged Brown, slimy, foul-smelling
Fix direction Dry back + kill larvae Water less, improve drainage Sterilize, improve oxygen, often too late

The tell that separates them from the rest is the flies. Overwatering and root rot do not put insects in the air over your pots. If you see the flies and the wet medium together, gnats are in the mix – and there may be more than one problem to solve.

What the larvae actually do

Fungus gnat larvae in the top layer of wet soil among fine cannabis roots, with an adult fly above, botanical illustration

The adults are a nuisance and a warning sign, not the damage. The larvae are the damage.

Living in the wet top layer, fungus gnat larvae graze on root hairs and the fine feeder roots that do most of a plant's water and nutrient uptake. In a seedling or a young clone with a small root system, that alone can stall or kill the plant. In a larger plant the direct feeding matters less – but every feeding wound is an open door. Fungus gnats are a known vector for soil pathogens like Pythium and Fusarium, moving spores through the medium and giving them a wound to colonize. A gnat problem left alone often becomes a root-rot problem, which is a far worse thing to fix.

This is why “just live with a few flies” is bad advice. The flies are the visible edge of a root-zone problem that gets more expensive the longer it runs.

Symptoms by stage

Early

  • A few small dark flies drifting over the topsoil
  • Adults showing up on yellow sticky cards near the pots
  • Plant still looks normal above ground

Moderate

  • Several flies per plant, lifting off whenever the soil is disturbed
  • Loss of vigor or slight droop the watering schedule does not explain
  • Lower leaves yellowing
  • Translucent larvae visible in the top 1-2cm when you scratch the surface

Severe

  • Heavy adult populations drifting through the whole room
  • Stunted growth and yellowing climbing up the canopy
  • Persistent wilt and weak structure that reads exactly like root rot
  • Actual root pathogens taking hold in the damaged root zone

Where fungus gnats come from

Fungus gnats are a symptom of one thing above all: a topsoil that never dries out. Their eggs and larvae need constant surface moisture, so the root cause is almost always the watering routine or the medium.

  • Topsoil staying wet between waterings
  • Overwatering, or a heavy, poorly draining medium that holds water at the surface
  • Peat or compost-heavy mixes, which arrive with organic matter gnats feed on and sometimes with eggs already in them
  • New medium contaminated with eggs or larvae
  • Open windows and doors letting adults migrate in from houseplants or outside

Fix the moisture and you remove the habitat. Everything below is about killing the current generation while you do that.

Treatment

The winning approach hits two targets at once: dry out the surface the larvae need, and kill the larvae and adults directly. Do one without the other and the population just rebuilds.

Break the moisture cycle

  • Let the top 2-3cm dry out fully between waterings. This alone kills eggs and young larvae and stops new eggs from surviving.
  • Water from the bottom where practical, keeping the surface dry while the roots still drink.
  • Improve drainage – amend heavy medium, and never let pots sit in standing runoff.
  • Add a dry barrier on top – a 1-2cm layer of coarse sand, or horticultural grit – so adults cannot reach the medium to lay eggs.

Kill the current generation

  • Bti (Bacillus thuringiensis israelensis) – the standard larvae killer, sold as mosquito bits or dunks. Soak it into your water and drench the medium. It targets gnat and mosquito larvae specifically and is harmless to the plant.
  • Beneficial nematodes (Steinernema feltiae) – a living soil-drench control that hunts larvae in the medium. Strong choice for a persistent or recurring problem.
  • Yellow sticky cards flat or near the surface – these catch adults, cut the next generation, and double as your monitoring tool.
  • Hydrogen peroxide drench (diluted) – kills larvae on contact and adds oxygen to the root zone. A useful knock-down, though Bti and nematodes are better for lasting control.

Predatory options like Hypoaspis (soil-dwelling mites) also work well for growers who prefer a fully biological program.

Prevention

  • Water on a dry-back, not a schedule – let the surface dry before the next water. This is the single most effective prevention there is.
  • Bottom-water to keep the top layer dry
  • Run yellow sticky cards continuously as an early-warning system, not just once a problem starts
  • Quarantine and inspect new medium and new plants before they enter the room
  • Keep the space clean – no standing water, no decaying plant matter, no algae on wet surfaces (gnats feed on it)

Telling gnats from the root problems they mimic

Bti and a dry-back clear fungus gnats reliably. What trips growers up is getting to that point, because gnats, overwatering, and root rot all arrive together in wet soil and all droop and yellow the same way. Weeks go into treating a watering problem while the larvae keep working on the roots.

PlantLab covers 31 cannabis conditions, fungus gnats among them, and returns a calibrated-confidence read from a single photo in about 18 milliseconds. Where flies are visible near the medium, it is built to call fungus gnats rather than let the droop get filed as generic overwatering – the misread that lets larvae keep working on the roots for another two weeks. It is not a substitute for scratching back the topsoil and looking – that is always the confirmation – but it points you at the soil surface early, before a gnat problem turns into a root-rot problem.

Free at plantlab.ai – 3 checks a day.

FAQ

Are fungus gnats harmful to cannabis? The adult flies are mostly a nuisance, but the larvae feed on fine roots in the top layer of wet soil and open wounds that let root pathogens in. On seedlings and clones they can stall or kill the plant outright; on larger plants they set up the conditions for root rot. They are worth clearing early.

How do I tell fungus gnats from root rot? Fungus gnats put small dark flies in the air over your pots; root rot does not. Root rot shows brown, slimy, foul-smelling roots and a persistent wilt that watering never fixes. The two often occur together in chronically wet medium, so treat the gnats and check the roots.

What kills fungus gnats fast? Bti (mosquito bits or dunks) soaked into your water kills the larvae, and yellow sticky cards knock down the adults. Pair that with letting the top 2-3cm of soil dry out between waterings. For a stubborn or recurring case, add beneficial nematodes.

Why do I keep getting fungus gnats? Because the topsoil is staying wet. Their eggs and larvae need constant surface moisture, so the fix is a dry-back watering routine, better drainage, or bottom-watering. A dry surface removes the habitat and prevents the next generation.

Do fungus gnats go away on their own? Rarely, as long as the medium stays wet – they keep breeding in the moist surface layer. Drying out the top of the soil and running Bti or sticky cards is what actually ends the cycle.

 
Read more...

from blog//x2600.cc

good title, eh?

“You could have it all, My empire of dirt, I will let you down, I will make you hurt”

A note to self, to not let others become too attached. I will near always let them down, in the end

Other news: heading back to apartment in Crystal City (long story). Will shower, shave, eat, relax.

Blogging as well. And IRC. And lurking. And emails. And texting. And browsing. And AC. Etc etc

 
Read more...

from Waybuu

People of the world – especially those that represent the ‘power’ in this world – have created a place of deceit and willful deception. And it sprinkles throughout the land like ultimate truth. One thing is a given: connected within social media; controlled and scripted.

A red flat on a calm and humid day

On second thought and having just went for lunch and sliding down the most delicious smoothie, I said to myself, “You know what? What the hell are you writing that load of crap for today?” So I stopped and here we are, in such a pleasing mood.

Let’s get one thing straight: don’t distract your day because people have trouble decoding a rabbit hole, owned by the oligarchs-wanna-be. Might as well go for a smoothie. Enjoy this pic from my well-aged 5mp rangefinder ☀️

W

Like my style? https://ko-fi.com/waybuu

 
Read more...

from Roscoe's Quick Notes

Rangers vs White Sox

Texas Rangers vs Chicago White Sox.

Today's MLB game of choice has my Texas Rangers playing the Chicago White Sox in the second game of a three-game set. The White Sox won the first game last night by the score of 10 to 3. Tonight”s game is scheduled to start at 7:05 PM CDT. As I usually do, I'll follow the game's score and stats in real time via MLB's Gameday Service where we can also find links to the radio-call of the game provided by announcers of either team we choose.

And the adventure continues.

 
Read more...

from Progress／Catastrophe

Forest grows from the neglected seed The lands collapse, the skys cry Debts settle between you and me It's not supposed to be my fault Why you have to make me die?

 
Read more...

from The Marshall Review

A press release landed in my inbox this week about the Marine Institute's research vessel Tom Crean. It was full of the expected details. Days at sea. Scientific surveys. Fisheries research. Seabed mapping. Climate studies. The vessel travelled more than 31,000 nautical miles last year and is now one of Ireland's most important scientific assets.

But it was not the statistics that caught my attention. It was the name.

Years ago, when I wrote about Tom Crean, there was often a need to explain who he was. He was known in parts of Kerry and among Antarctic enthusiasts, but he had not yet become a household figure. Mention his name and many people would look puzzled. Back then, from time to time I would stop by Tom Crean's pub in Annascaul. Visitors liked to joke that they had made it to the South Pole, albeit by a somewhat easier route than Crean himself. Today the pub is a destination on the tourist map. Then, it felt more like a quiet local reminder of a largely forgotten man.

Now, things are different. A state-of-the-art research ship carries his name. Schoolchildren learn about him. His story has entered the fabric of Irish public life. The remarkable thing is not that Tom Crean has changed. The remarkable thing is that we have.

Names are curious things. We tend not to notice them until we stop and ask why they are there. Every nation reveals something about itself through the names it gives to ships, bridges, buildings and institutions.

The choice of Tom Crean is an interesting one. He was not a politician. He was not a military leader. He left no manifesto behind him and founded no movement. By most conventional measures, he was an unlikely candidate for national recognition.

What he possessed was something quieter. Endurance. Reliability. Courage. A willingness to keep going when circumstances became difficult. In the great Antarctic expeditions of the early twentieth century, he was rarely the man making the speeches or standing in the spotlight. More often he was the man pulling the sledge.

Perhaps that is precisely why he speaks to modern Ireland. There was a time when Irish history concentrated heavily on conflict and politics. Increasingly, however, we seem drawn to different kinds of figures. People who built things. People who explored. People who persisted. People whose achievements emerged not from ideology but from character.

The research vessel Tom Crean seems an almost perfect symbol of that shift. The original Tom Crean ventured towards the unknown edges of the map. The modern Tom Crean explores a different frontier. It studies the oceans around us, gathers evidence, maps the seabed and helps us understand our place in a changing world. Both are engaged in exploration. One travelled into physical darkness. The other seeks to illuminate what lies beneath familiar waters.

I found myself smiling at the thought. Somewhere between the quiet pub in Annascaul and the research vessel sailing out of Galway Harbour lies a story about Ireland itself. Not about how Tom Crean became famous. About how we finally learned to recognise him.

David Marshall Costa Coffee Omni Park Shopping Centre Swords, Co. Dublin

 
Read more...

from Unattributed

You've probably run into some Obsidian evangelist espousing some convoluted system of organizing all their notes, and building some knowledge base. Heck, I was just involved in a conversation about Personal Knowledge Management. This isn't that article.

My personal use of Obsidian tends to be simple. I build into it the tools that I need to get things done, to make things easier. There is a saying (which I can't locate, so I'll paraphrase) that a system should only be as complicated as needed, and nothing more. The idea is there is no reason to build a Rube Goldberg machine when all you really need is a wrench. That's the approach I take: use a wrench to bolt on a few tools, and tighten things up where necessary.

So, this article will walk through how I work with things now. This system has evolved a bit over the last few weeks, and is likely to evolve further. But the primary idea is, and will remain: keep it simple, but make it useful.

Planning

When I switched from WordPress to write.as, the biggest thing I “lost” was having a way to plan the articles that I wanted to work on. Obsidian recently added a feature called Bases that made it simple to set up a table containing all the articles for all three of my sites:

View of the main planning table. View of the main planning table. Unpublished articles blurred—no spoilers! ;)

The simplicity here is that the table quickly lets me see which articles I have published, which are in the planning / drafting stage, and the scheduled date for the articles. But, looking at a table this big could be tricky to navigate. Fortunately, I have a couple of alternate views available:

The Plan / Draft view lets me see just the articles I am working on.

The Plan / Draft view lets me see just the articles I am working on.

And the Published view lets me see what I've already posted.

And the Published view lets me see what I've already posted.

There are two “genius” parts to this system. First, all this information is part of the article, it's not some extra information that I need to keep track of. Second, I can update the “Published”, “Scheduled” and “Status” fields from this list without having to open the specific post. How is this done?

New Post Drafts

Every time I have a new idea, I create a new document in the website's folder, and insert a template:

Image of the template pick list Blog Template is for website posts, CMP Template is for my archived podcast posts.

Once the Blog Template is inserted, the document shows up in the Planning table. After the template is inserted the document looks like this:

Template inserted in document, with Properties for the *Planning* table circled. Template inserted in document, with Properties for the Planning table circled.

You might notice there is both an Untitled field, and a Title field. Untitled is Obsidian's filename for the document, whereas Title is the actual article title. Why both? Obsidian places some restrictions on the names of documents. For example, the character : isn't allowed in an Obsidian filename, but there are times when I need it in an article title.

From here, writing is dead simple…

Writing In Obsidian

Image: the full writing environment. The full writing environment, with a few highlighted items.

Now it's just time to write. The majority of the screen is dedicated to the editing window where I can work on an article. If I have images (like this article) they can be drag-n-dropped into place. To the left is the Navigation panel, with my folders on the top half, and the files in the selected folder on the bottom. To the left of the editing window is the version control panel for the current article (I'll explain my choice in the next section).

When I am done with the article I export it to an output directory. The export process converts any Obsidian specific markup (such as using wiki style links) to standard Markdown formatting, and places all the attachments (images) in a folder with the article. This makes it dead simple to upload to write.as.

Obsidian Plugins

I have a selection of Obsidian community plugins that I use for working in Obsidian as can be seen in this image:

Image: screenshot of installed community plugins Image: screenshot of installed community plugins.

The most important of these are Harper and LanguageTool, both of applications these plugins call are installed locally on my system as I have a slow internet connection, and prefer to have my tools running locally. markdown export is the export tool I use for blog posts. Notebook Navigator enhances Obsidian's built-in navigation panel a ton, I've barely scratched the surface of what it can do. Outliner provides better list handling, allowing drag-n-drop of items, folding, and more. Typewriter Mode is really only used for one feature: highlighting the current line I am editing. (I have been doing this for 40+ years as it helps with my unique form of dyslexia.)

Remotely Save is the tool I use for syncing my vaults between systems. Version Control is a simple built-in version control system. The advantage to using it over git or another external version control system is that the versions of my documents are synced with Remotely Save. This removes the need to synchronize a git repository separately from the vault.

Zotero Integration allows me to search and insert bibliographic references when I need them. Alas, write.as doesn't support reference links, so I have to do it inline, instead of in end-note style.

Safi Site Audit is a tool that is unique to this vault for me. It's used to check the health of my sites, and catch any major issues, like broken links, missing alt text, and so on. I don't run it often, but it's good to be able to check and generate a report once in a while.

Conclusion

Obsidian, between it's recently added Base feature and a handful of plugins makes for a great writing environment for me. The ability to track the status of the posts I am working on, have version control over the documents, and have some additional tools that allow me to customize the environment to my liking.

I know there are a lot of evangelists of Obsidian out there, and their enthusiasm and overly complicated setups can make Obsidian seem unapproachable. Personally, I've found that it is excellent if you tailor it to your specific needs. And that is what is most important, and makes me most productive with a tool: doing what I require in the way that I need.

This wasn't too detailed in terms how I actually tweak things (like key bindings for certain tools). Hopefully it gives you some insight into my workflow. And maybe it will give you some ideas about how you can refine your workflow.

Categories: #HowTo Tags: #obsidian, #tool, #writing, #blogging, #configuration, #workflow License: Copyright Unattributed. Licensed under Creative Commons BY-NC-SA 4.0.

 
Read more...

from Ira Cogan

Caution: continued from yesterday’s post about switching from one markdown editor to another. If that sounds boring to you, read no further.

To recap a little: Yesterday I wrote about how much I like a side by side view option in a markdown editor. The left pane shows what you’re writing. The right pane shows what it looks like with markdown applied. IA Writer does this very well for me, but I have issues with it being a kind of one-way sync between my different platform devices. So, I decided to try out StandardNotes.

If you’re a privacy or security nerd, you probably already know about Proton and the products that company offers, and I suspect that’s who this product is for most of all.

The value in StandardNotes, for me, is the side by side view option which IA Writer also has, but with terrific cross-platform sync between (probably) anything without having to jump through hoops or do much toggling when setting it up. The other features are a distant second in my case. The question was do I care about that enough to pay $90-$120 a year for it? Well, no. I suspect it’s priced this way because of the super duper encryption, but, that’s not a feature I was looking for in a markdown editor. With the seemingly world wide movement towards fascism and a surveillance state, I totally see the value in that. Like, it’s a good product and I’m glad I checked it out. I just don’t see myself using it enough right now.

tldr addendum: I thought about it some more and for me, I’d be paying to save myself Select/Copy/Paste a few times a day. Not that it doesn’t have other features that are worth the money for lots of people, but for me, that would be its only utility.

-Ira

 
Read more...

from bios

an interview with Eldon van Aswegen, director of FOSTA

FOSTA follows both the story of DJ Fosta and Bridges For Music, from Fosta's time in prison to his discovery of Bridges, playing at Glastonbury, and building the Bridges For Music School in Langa. Along the way it takes in Fosta's musical legacy, embedded in the jazz traditions of Langa.

Following our review, van Aswegen talks to us, via email, about the film's journey to screen.

bios: Did you set out to make this film? That is, when you first started shooting, was the intention to capture the story of DJ Fosta?

No, the initial intention was not to capture DJ Fosta's story. My intention in the beginning was two-fold: to prove myself as a filmer, visually, and to do good with the medium — telling stories of meaning. What presented itself was way beyond my expectations.

The second catalyst was experiencing a low at the same time as Fosta. From there it snowballed. Do you give up? “No” was the answer. Throw in Valentino's die-hard passion and vision, and the youthful energy of Siphe, and the opportunity to tell the rich South African story, and the power of music, and you have the film.

So in a nutshell, no. It really just told itself, and Fosta was kind enough to open up and facilitate the much-needed story.

bios: What is your background as a filmmaker?

This was my film school. Prior to this I had done a few productions for TV and worked a lot on various Red Bull productions. We cut our teeth in the Canon 5D days, and I learnt a lot about storytelling through that journey, with an emphasis on always diving deeper while keeping things real and authentic. This project took things to a new level — understanding narrative and the strength of the story as the backbone. I was always a visual person first, so self-taught is the answer there.

bios: Electronic music performance is notoriously unvisual, often compensated for with visual hijinks on stage, which can detract from the actual music-making. Was this a concern during shooting?

No — I think electronic music as a scene and a form of entertainment has done well to bring a very rich visual aesthetic to the scene. There is so much energy in these performances, it is quite easy to capture.

bios: There were two visual elements used as placeholders for footage — the animations, and the visuals projected onto faces near the end. Was this planned during production, or did it come about in the edit?

The animation came from the simple idea that the stories these segments carried could not be justified with simple archival footage, and deserved something more. Much like the filming, I was always looking for excuses to do creative things, and this aligned in that regard. Not having any budget, and not being an animator, the simpler the better made sense — it lets the story carry itself.

The projections came from a very similar place. How do you capture the entirety of the stories shared in one visual? Portraits are powerful, but portraits portraying the entirety of a journey, even more so.

bios: There's no direct bridge between Brenda and Siphe, but from the Brenda histography the implication is that he is related. What exactly is the relationship there?

Siphe is Brenda's nephew. More than that, music flows in that Fassie name for sure!

bios: With thirteen years of footage to work with, what did the edit process actually look like? How did you decide what stayed and what got cut?

It was a laborious and at times painful process. I wanted everything to come through as I experienced and heard it, so essentially no stone was left unturned. We started with a two-hour proof-of-concept cut. I had told a hundred stories and wasn't always sure which way it was going, so it became a process of elimination. At that stage we had a multitude of short stories stitched together, and I learnt a great lesson here: that the passage of time is not a story. Through the Rough Cut Lab process with Khalid Shamis, we identified the way to go was to lean into Fosta's story — it was undeniable, already captured, and by far the strongest vehicle to tell the myriad of tales and lessons we wanted to pass on.

From there, we did a ninety-minute cut and concluded it deserved this time to be told, while being well aware that you don't want to waste your audience's time.

We then did additional filming and interviews to bring the story to the current day, and wove that in as the backbone of the film, jumping between then and now.

Massive thanks to Matthew James, the editor who went through this process with me.

bios: The footage with Hawtin and Skrillex visiting for the first time, and the sheep's heads — how well did you know Fosta at this stage of the journey?

Not at all. It was only after that whole tour that I went and met him, Siphe and Vincent, with the idea to see if there was something more. And there was.

bios: What cameras did you shoot on?

Using the experience and opportunity to do everything I wanted was always at the fore. Owning your own gear is key in this regard — you can go and shoot whenever you feel the need, but at some stage budget and gear become limited.

At the time I owned a Canon C300 Mk I and a 5D. Over thirteen years, for obvious reasons, this world has exploded. With no funding it was hard to keep up, but I kept going and upgraded to the C300 Mk II.

In the final leg, with some funding through the PESP initiative, I wanted to end strong — we shot on the RED, owned by my assistant, along with some cine primes.

bios: How big was your crew, and did that change over the period?

A lot of the film was shot by me alone. For segments I'd have one assistant or second operator. In the latter stage it was a team of three to finish things off for “current day.”

Yes and no — I started with an assistant, as it was a paid gig, maybe five days, and ended with three, maybe ten days. The rest was man alone, mostly.

bios: How closely did you work with Fosta on the planning and editing phases? How much input did he have into the final cut?

None. His trust in me has been unbelievable.

bios: The story of Bridges For Music continues. Are you planning to continue to cover that story?

Their story is ingrained in the film. Valentino — his vision and his initial idea — was the catalyst for this.

Bridges Academy's story will continue to evolve, uplift and inspire in multitudes. I look forward to seeing that.

For the moment I'm not documenting, but I believe there's an opportunity to tell their story in more detail — in terms of modules, impact, and the depth of untapped talent.

· → “I am Mapanta”

 
Read more...

Join the writers on Write.as.

Start writing or create a blog