VL.Audio.LTC 0.1.0

dotnet add package VL.Audio.LTC --version 0.1.0
NuGet\Install-Package VL.Audio.LTC -Version 0.1.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="VL.Audio.LTC" Version="0.1.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add VL.Audio.LTC --version 0.1.0
#r "nuget: VL.Audio.LTC, 0.1.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install VL.Audio.LTC as a Cake Addin
#addin nuget:?package=VL.Audio.LTC&version=0.1.0

// Install VL.Audio.LTC as a Cake Tool
#tool nuget:?package=VL.Audio.LTC&version=0.1.0

VL.Audio.LTC

A set of nodes to encode and decode Linear (or Longitudinal) Timecode (LTC) in VL.Audio.

Code borrowed from VVVV.Audio by Tebjan Halm. Depends on libtc by Robin Gareus and LTCSharp (enclosed) by Elliot Woods.

Using the library

In order to use this library with VL you have to install the nuget that is available via nuget.org. For information on how to use nugets with VL, see Managing Nugets in the VL documentation. As described there you go to the commandline and then type:

nuget install VL.Audio.LTC

Try it with vvvv, the visual live-programming environment for .NET
Download: http://visualprogramming.net

Some Remarks

LTC only supports framerates of 24, 25 and 30 FPS that are tradionally encoutered in the context of film/video. As long as software runs at those framerates all should be fine and dandy, seconds will be split into [0 ... 23], [0 ... 24], [0 ... 29] frames.

60 (or 50) fps like you'd more likely use in real time media are not supported though. You need to pick a LTC standard that is a divisor of your desired framerate. The count of frames returned will then be multiplied by the ratio of that division. So for a desired Mainloop framerate of 60 FPS you'd pick an LTC standard that uses 30 FPS, the decoder will then ideally return the following frames [0,0,1,1,2,2,3,3 ... 29,29] and you need to account for that (see Interpolate on the ToSeconds node).

But things can get finicky. During testing I encountered for example the following [0,0,1,1,1,2,3,3 ... 29,29] and wirmachenbunt even reported that some frames totally got lost like [0,0,1,1,1,1,3,3 ... 29,29]. From what I can tell this is more likely to happen when using WASAPI or ASIO with a audio buffer size >256. Might be hardware and/or driver dependend. So make sure to check the continuity of the incoming frames (by queuing them for example).

TBH if you are working in a professional context and can spare the money using a dedicated timecode reader card might be the better option.

Issues with C++/CLI

C++/CLI libraries in .NET Core need a shim called Ijwhost.dll for finding and loading the runtime. Currently there seems to be no "official" method on how to deal with this shim when having a C++/CLI library in a NuGet package. Some say to include it in the package other say that this can easily lead to dll hell (what happens when to packages come with different versions of the shim?). Here are some related github issues with further info:

Tried the "workaround" of including a manifest file for Ijwhost.dll. But:

  • vvvv only finds the shim when located alongside LTCSharp.dll, e.g. both files are in VL.Audio.LTC\lib\net6.0-windows
  • when the shim is located in VL.Audio.LTC\runtimes\win-x64\native as suggested by some vvvv doesn't pick it up
  • in neither case the shim gets copied to the output when exporting a document referencing VL.Audio.LTC when using normal vvvv library workflow

Thanks to Elias for a PR and helping me to figure out that the copying of the shim works when VL.Audio.LTC is referenced as "real" package.

Unfortunately this makes debugging of exporting executables during development a bit of a pita.

So for now one has to:

  • Make changes
  • right-click the VL.Audio.LTC project inside VS and select the Pack command
  • this will create a nuget package inside the pkg folder, for example: X:\path\to\_vl-libs\VL.Audio.LTC\pkg

To test the package you can run the following nuget command to install the package: nuget install VL.Audio.LTC -source X:\path\to\_vl-libs\VL.Audio.LTC\pkg;nuget.org For testing the export you'll have to add to add your local path (X:\path..) to your nuget.config file which should be in C:\Users\yourusername\AppData\Roaming\NuGet.

Alternatively move the created package from the pkg folder into the root folder of *VL.Audio.LTC* and start vvvv with the follwing arguments: start X:\vvvv\vvvv_gamma_6.2\vvvv.exe --package-repositories X:\path\to_vl-libs\ --export-package-sources D:\path\to_vl-libs`


License

LGPL-3.0

VL.Audio, VVVV.Audio and libtc are released under LGPL-3.0 license. LTCSharp is released under MIT license.

Credits

Initial development and release sponsored by wirmachenbunt.

Product Compatible and additional computed target framework versions.
.NET net6.0-windows7.0 is compatible.  net7.0-windows was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
0.1.0 102 4/22/2024