ShotNotes adds a dedicated notes-and-tasks panel to Adobe Premiere. It targets the everyday problem that never makes it into a spec sheet: remembering what to fix, what to check, and what to deliver while the timeline keeps changing.

The core idea is sequence-based notes: You add an entry, and it belongs to the sequence you are working on. Notes can be colour-coded, and the panel can filter what you see by colour, so you can separate client feedback from internal reminders or mark items by priority.

A note can include an optional timecode pulled from the current playhead position. When an entry includes timecode, ShotNotes automatically places a marker on the timeline so the entry stays linked to that frame. The panel treats timecode as more than a label: it turns timecode into a navigation control.

Clickable timecode that behaves like a jump button

ShotNotes can insert clickable timecode into a note so you can jump straight to the referenced point in the timeline. The note becomes a shortcut, not just a comment.

The panel supports copying timecode from one sequence and pasting it into a note for another sequence. That makes it possible to reference a moment in a different sequence and still navigate there quickly from the note.

Notes can also reference other sequences directly. The result is a lightweight way to connect the dots across a project: a note in one sequence can point to a specific moment in another sequence and take you there with a click.

If your usual approach is to build a marker forest, ShotNotes can still feed that workflow by creating markers for each note so the timeline can carry the breadcrumbs the panel shows, without forcing you to rely on markers alone as the only place your thinking lives.

Links and reference material that stay one click away

Notes support hyperlinks. If you type a URL into a note, ShotNotes turns it into a clickable link and opens it in a web browser. That is handy for reference docs, client frames, internal shot tracking pages, relevant memes, or just the one weird spec sheet everyone forgets until export day. The point is not that links are rare, but that links usually end up in a separate app, which becomes another place to lose context.

Search and filters for the whole project brain

ShotNotes can search notes across the entire project. When you need to find that one line about audio cleanup, the one producer note that actually made sense, a missing lower third, or the exact frame that needs stabilization, the panel can locate it without you hunting sequence by sequence.

The interface also includes filtering, including options to filter based on whether entries have timecode. Combined with sequence-based organisation, this lets you narrow the panel down to the entry you need right now. Notes and tasks can expand and collapse in the panel, so you can keep long entries around without turning the panel into a wall of text.

Marker sync, because timelines move

ShotNotes links entries to timeline markers when you include timecode. When edits move markers later in the project, ShotNotes provides Sync and Sync All buttons to sync entries to the marker’s new position, because a note is only useful if it still points at the right moment after the cut changes. (*looks emberassed at the heap of PostIts building a ramp below the screen*)

There is an important limitation: depending on how you edit, Premiere Pro may not move the markers. If that happens, you may need to manually update the timecode in the affected notes when frame accuracy matters.

A built in time tracker for tasks and receipts

ShotNotes includes tasks with timers. You can start and stop a timer for a task, log multiple timer entries, and then review those entries in the task log. If you forget to stop a timer, the panel includes an edit option that lets you adjust the end time so the entry reflects when you actually finished. If a timer entry is junk, you can delete it so it does not appear in exports.

The time tracker also logs certain events to provide more detail about what happened while a timer ran, including switching sequences or selecting a clip in the timeline. That makes the report more descriptive than a single number on an invoice.

This is also where reality bites a little. Premiere Pro limits what events can be captured, so the activity log does not represent every editing action. Some actions can appear as delete and add events because Premiere Pro treats certain edits that way internally.

Export and backup that fits the handoff phase

ShotNotes can export notes and other data in a variety of formats for printing out or viewing.

For backup and transfer, ShotNotes includes exporting to JSON as its native format. That JSON export can be imported on another computer, copied to another sequence, or used as a backup. For time tracking, ShotNotes can generate a report that saves timer entries for a sequence to a CSV file that can be viewed in a spreadsheet.

Exportable notes and exportable time data matter for finishing and delivery, because that is where you often need to share information outside the NLE. Like, what to bill the client for his latest “Just one more change”. ShotNotes gives you a structured way to pull that information out without rewriting it.

Licensing, trial, and getting it into the workspace

ShotNotes includes a free seven-day trial, which is fully functional. Licensing can be done with a serial number or by logging in to a Digital Anarchy Cloud account. The cloud account method is described as the easiest way to license if you want to install on a different machine without juggling serials. If you cannot license online, support provides an offline activation file option.

Compatibility notes, including one awkward bug

ShotNotes only supports Premiere Pro 2023 and newer versions. A known issue exists in Premiere Pro 2025 and 2026 that can occasionally cause the recorded timecode of newly created entries to be slightly inaccurate. The amount of offset can depend on how zoomed out the timeline is when the entry is created; zooming in typically reduces the offset. If needed, you can manually adjust the timecode for the entry.

Price, promo window, and the practical take

ShotNotes is available immediately at $129 USD, with a $99 price offered until May 15. As with any new workflow tool, test it before you rely on it for a deadline-sensitive job.

https://digitalanarchy.com/shot-notes/

The post Digital Anarchy releases ShotNotes panel for Premiere. first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Houdini can read in external data in various ways. The most comprehensive is certainly a self-written Python parser, but that is not necessary here, because Houdini comes with the Table Import Node as standard. This makes it possible to import tables in CSV format. If you look under the bonnet of the table import node, you will of course find a Python script there anyway. This is one of the reasons why I like Houdini so much: almost everything is open and can be studied or adapted to your own needs.

Import

The CSV format contains values that are separated by commas (CSV = comma separated values). These can be words or numbers. Most spreadsheet programmes can save or export tables as CSV. I use Google Sheets here, and it works great: the table import node initially only creates points, which then contain these values in attributes. I use the attributes:

@word, @pscale, @font.

@word gets the values from column A, which is the first column. In Houdini, counting usually starts with zero, hence Column Number 0. The attribute type is a string.

@pscale is a special attribute specified by Houdini. @pscale stands for Point Scale, i.e. the size of a point. This is Column Number 1, and the type in this case is a float, i.e. a floating point number. I could therefore also have entered 1.5 or 2.3 as values in the table.

i have defined @font as type integer, i.e. as an integer. As I want to use three different fonts, I have entered 0, 1 or 2 as values in the table.

The Table Import can also translate (e.g. Lat/Long to Sphere), but the Translator is not needed here.

The second node is Enumerate. This creates an @index attribute with which the points are counted in order to be able to assign them later. The group type must be changed from “Primitives” to “Points”. The next two nodes are not absolutely necessary, but as I wanted to create other sizes and these should be somewhat random, I first used Attribute Expression to convert the @pscale values 1,2,3 into 1.5, 2 and 2.5. To do this, “Custom” must be entered in the node attribute and “pscale” as the name and “Float” for the type. I use the VEXpression for this: “1 self * .5”.
And of course, I could have entered these values in the table straight away, but I didn’t. The zero named here as “OUT_points_with_attributes” is not necessary for the function, but is part of good style.

Loop it!

Now the first loop comes into play. This is a For Each Point loop. It contains 3 font nodes, one for each font. Firstly, I created a font node for this and added the spare input required later. To do this, click on the cogwheel and select “Add Spare Input”.

This font node was then referenced twice using drag-and-drop with the Shift, Ctrl and Alt keys held down. For the copies, I then held down the Shift and Ctrl keys and clicked on Font to remove the reference link. Alternatively, this can also be done with the right mouse button menu and “Delete Channels”.

Fonts

The most important node when it comes to text is of course the font node. It can generate both polygons and Bezier curves or both at the same time. I use polygons here. I have set the level of detail to 4 so that the tessellation is nice and fine.

Working with Bezier curves is also great, but unfortunately not useful here, as the UV layout node used later cannot process them. Now it gets a little more magical or technical. In the “Spare Input0” parameter, the “../foreach_begin1” node is referenced by drag-and-drop or, if you want and like typing, you can do that too. The text to be created is normally simply entered in the text field, but we want to read it in from the CSV table, which has already been converted into points. Backticks can be used here to execute code.

The command required here is “points”, whereby it is not about several points, but about string values from points. The “s” at the end stands for “string”. The first spare input is addressed with “-1”. The zero after it is the first point, here it is always just one point anyway, as we are looping over the points. Then “word”, because we want to read the @word attribute. Brackets around it and a backtick and that’s it.

As an aside and for the sake of completeness, “Add Text Attributes” should also be mentioned here. It is not needed here, but is very cool for other text gimmicks. If the box is ticked, the attributes @textindex, which indicates the number of letters in the word, and @textsymbol, which indicates which letter it is, are created for each letter or primitive. However, this is an ASCII value, i.e. a number. “f”, for example, is then 102.

The three font nodes are then connected with a switch that reads the @font attribute. I have also created a spare input for this. This time it is the “point” command and not “points”, as only a number is read out here and not a string. So “point(-1,0, “font”,0)”. In this case, “-1” is again the spare input, “0” is the first point, “font” is the attribute and the last “0” is a necessary argument, which doesn’t really make sense here. However, if we wanted to read out a vector, “0” would be X, “1” would be Y and “2” would be Z. This is also only mentioned here for the sake of completeness.

Copy to points

Okay, Houdini! Now we come to the copy to points node. First of all, some information in passing: This node will change a lot in H18 and make actions like this easier. No matter. Pack and Instance is not needed here. Transform Using Point Orientation is also not required here, but can also be on. Copy Points Attributes is used because we still need @index. So enter “index” under Set/To Primitive. Delete everything else.

Now you should be able to see a bunch of fonts on top of each other. Before, there was nothing to see in the viewport except a dot in the centre, at most. Tip: In the “foreach_end1” node you can set to “Single Pass” for debugging, then only one iteration of the loop is executed. And always keep an eye on the geometry spreadsheet, where you can see the values of attributes.
Now we come to the UV layout node, which is used here to distribute the words in a shape. In the picture, I have coloured the shape green. I have left space for the two logos of DP and DIGITAL PRODUCTION. Connecting this shape to the second input of the UV layout node should not be too complex. Of course, the words with the @index attribute go into the first one.

UVs

The UV layout node normally uses the @island attribute to delimit the UV parts from each other and the @uv attribute for the positions of the vertices on the UV map. Since there are no UV coordinates here at all, we replace “uv” twice with “P”.

in Houdini, @P is the position of the vertices. For Axis Alignment we select “none” and for Island Rotation Step we set “No Rotations”. If you want to create a Word Cloud with rotated words, they should either be rotated beforehand or you should select 90°, for example, so that no words are upside down.

Padding is the distance between the shapes to be distributed, in this case words, and Scale should be set to “Largest Packable”. The “Advan…” settings are also interesting. This must stand for Advanced. There are iterations here. Here the node randomly tries different layouts and then uses the layout with the best space utilisation. However, each iteration takes time, and 4 is sufficient for this purpose. Different layout versions can be generated with “Random Seed”.
That’s it as far as the layout is concerned, but now we want it in 3D. To switch to a so-called Packed Workflow, we need an @name attribute with a string, i.e. text content. At the moment, we only have an @index attribute, and these are numbers. We do this with an attribute wrangle node.

Select “Primitives” under Run Over and enter the following VEXpression: “s@name = sprintf(“%d”, i@index);”. This creates an @name attribute, which then contains the number as a string. For more details on this VEX function, please refer to the Houdini documentation, which would go beyond the scope of this article.

Now the whole thing is packed, i.e. each word is now represented by a point. This is practical because it is now easier to select the words, for example, in order to make manual corrections to the positions. Simply use an Edit Node to do this.

Before or after the edit node, I used an attribute copy node to write the attributes from the beginning @font, @pscale, @word back to the points, which now contain the packed geometry. Again, @index is used to assign the source and target points (Attribute to Match). Only @pscale is actually needed, but never mind. If you want, you could customise this even more variably and select words more easily or, for example, extrude them differently depending on the font.
Now rotate another loop and extrude the words. To do this, create a For-Each Primtive Loop and place an Unpack followed by a Pack Node. A polyextrude is placed in between.

Then either drag and drop the “foreach_begin3” into the spare input created or enter “../foreach_begin3”. I have set the parameter “distance_multiplier” to 0.025.
The magic is in the Distance parameter; enter “point(-1,0, “pscale”,0)*ch(“distance_multiplier”)” enter. Now @pscale is used to control the thickness of the letters. Do not forget to tick the “Output Back” box, otherwise the letter will be open at the back.

Finally, a file node to save the geometry. It can then be integrated into the rendering scene. The outline plate behind the words was also created procedurally, unfortunately no longer part of this article. But this much can be revealed: I converted a geo into a volume, more precisely into an SDF/VDB. Then enlarged it as an SDF or made it thicker. Then “vdbsmooth” and converted it into a mesh. An Intersection Aanalysis followed by Polypath, then Resample, then Fit and Resample again, and the outline is ready.

Outlook

I would also have liked to have written something about splines, i.e. curve modelling and editing. This works very well in Houdini, even if it takes some getting used to. I would also have liked to discuss rounded edges. But I ran out of pages – we’ll just do that in one of the next issues.

The post Blergh! Word Art! In Houdini? first appeared on DIGITAL PRODUCTION and was written by Olaf Finkbeiner.