{"id":2849,"date":"2023-04-23T19:21:06","date_gmt":"2023-04-23T19:21:06","guid":{"rendered":"http:\/\/julius-ihle.de\/?p=2849"},"modified":"2023-04-24T07:54:56","modified_gmt":"2023-04-24T07:54:56","slug":"playing-with-osl-7-text-node","status":"publish","type":"post","link":"https:\/\/julius-ihle.de\/?p=2849","title":{"rendered":"Playing with OSL #7: Text Node"},"content":{"rendered":"

\"osl_text\"<\/a><\/p>\n

Having text live in your shaders can be a great way to add decals, burn-ins, etc. to your renders. I’ve gone on a bit of an adventure to implement an OSL shader which can be used to display arbitrary text right in your shader.<\/p>\n

<\/p>\n

Unfortunately implementing a .ttf reader is way above my head, so I had to resort to a more primitive solution. I’m using a library of images of all the common characters found on an english keyboard layout. These are read back into the shader based on the text input. Having special characters (such as ~#!$?&) in file-names however is a big nono, so I resorted to unicode character naming conversion, where a single integer represents a given character. ASCII characters<\/a> are the most important ones, which I have included in the package in a few common fonts. If you would like to use a font other than the ones provided in the package, I’m also supplying an example Nuke script in which you can just change the font and output in the required manner for the shader to read it properly:<\/p>\n

https:\/\/julius-ihle.de\/wp-content\/uploads\/2023\/04\/osl_text_nuke-2023-04-23_19.56.39.mp4<\/a><\/video><\/div>\n

 <\/p>\n

The idea is to supply the shader with the rendered image sequence of the unicode characters in the font_source<\/code> parameter replacing the unicode numbers with a hash, like so:
\n\/home\/julius\/shaders\/util\/unicode_characters\/Arial\/#.tx<\/code>
\nNote that some DCC’s convert the #<\/code> to the current frame number, which can be avoided by escaping it, eg by prepending a backslash: \\#<\/code>
\nIf the input font path is not valid, you will get a warning in the terminal and the shader will output the color specified in the false_color<\/code> parameter.<\/p>\n

The text to render can be anything you like, provided you have a corresponding unicode character rendered. New lines can be added via \\n<\/code> (some DCC’s might need \\\\n<\/code>).
\n\"osl_text_img1\"<\/a><\/p>\n

 <\/p>\n

Apart from that you have a couple of options for placing it on the UV’s and general text editing stuff (alignment, leading, kerning, etc).<\/p>\n

One thing I find this particularly useful for is pipeline automation… automated burnins on slates, etc. The assets from example turntable setup in the demo below is from the awesome team at CAVE Academy<\/a>. Make sure you check them out!<\/p>\n

You can download it HERE<\/a><\/p>\n

Demo can be seen here:
\n