Skip to content

add support for Net-Timecode by LaserAnimation - #11

Closed
i-n-g-o wants to merge 1 commit into
fiverecords:mainfrom
i-n-g-o:la_net_timecode_support
Closed

add support for Net-Timecode by LaserAnimation#11
i-n-g-o wants to merge 1 commit into
fiverecords:mainfrom
i-n-g-o:la_net_timecode_support

Conversation

@i-n-g-o

@i-n-g-o i-n-g-o commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@i-n-g-o

i-n-g-o commented Jul 1, 2026

Copy link
Copy Markdown
Contributor Author

Hello.

I was wondering if this PR could be merged.

It was created in coordination with LaserAnimation and was also tested by them. LaserAnimation and I would love to see Net-Timecode support in this great tool.

If you have any questions or comments about the code please let me know.
When do you plan to do the next release?

@fiverecords

Copy link
Copy Markdown
Owner

Thanks for this, and sorry it sat for a while. It's a thorough piece of work — the input and the output both follow the existing conventions closely, and the integration into the settings, the interface selectors and the UI was complete, which made merging it much easier than it could have been.

Merged into main with your authorship preserved. Two small adjustments on my side, neither of them a problem with your code:

I qualified the ByteOrder references as juce::ByteOrder. This project builds with addUsingNamespaceToJuceHeader disabled, so JUCE types need the full namespace here.
I added LA-Net to the input and output lists in the README, alongside the file table entries you'd already added.

I don't have LaserAnimation hardware, so I can't verify the protocol on the wire. If you spot anything that needs adjusting once it's out in a build, let me know.

@fiverecords fiverecords closed this Sep 6, 2026
@i-n-g-o

i-n-g-o commented Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants