

They are stored in PRo7 documents using a standard textual string representation that 36 characters long. UUIDs are used throughout ProPresenter documents as identifiers for many objects.

This is the unique identifier for the presentation. This describes which application and which operating system that the presentation file was created with.
#Propresenter tutorials update#
proto files, you have the power to easily create, read and update Pro7 data files!Ī great feature built into Visual Studio Code is that it lets you collapse logical sections of text and this makes it much easier to look at and learn the structure of the data: The collapsed view makes it easier explore and learn the presentation structure. An example is given at the end of the Protocol Buffer Basics: C# Tutorial… public void PrintMessage ( IMessage message ) \\uc1\\paperw12240\\margl0\\margr0\\margt0\\margb0\\pard\\li0\\fi0\\ri0\\ql\\sb0\\sa0\\sl240\\slmult1\\slleading0\\f0\\b0\\i0\\ul0\\strike0\\fs100\\expnd0\\expndtw0\\cf0\\strokewidth0\\strokec1Īs you can see above, there is a quite a bit of data even in a simple presentation – but it seems the proto files needed for presentation files are working well and if you have these. proto files that were originally used to generate it.

NET to get the required information to rebuild the. It turns out that the Google protocol buffer compiler generates C#.NET code that allows the use of Reflection in. Over the weeks that followed, I found a much better way.
#Propresenter tutorials manual#
In my first post I started doing this by manual methods. proto files were reverse engineered – just in case there any nerds out there that are interested. This is not important, and you might like to skip ahead to the next section.

Do NOT contact Renewed Vision (the makers of ProPresenter) for support if you blow up your documents, configuration or the entire computer! proto files I have created are unsupported reverse-engineered files. proto files, the tutorials by Google are great – read them to quickly get up to speed on how easy it is to automatically generate code from. pro6 documents, this might be of interest to you. If you are a programmer who has built applications or scripts to work with. I now have a somewhat-complete and useable set of proto files that enable programmers to create code for their applications and scripts that can work directly with pro7 document and configuration files.
#Propresenter tutorials series#
In part 1 of my series on exploring the new Pro7 file format, I had discovered that Pro7 uses Google protocol buffers and started to reverse engineer the structure of the (.pro) document file format. TLDR: I now have a useable set of proto files that enable programmers to automatically generate code for their applications and scripts that can work directly with pro7 document and configuration files. This information is probably only of interest to developers – nothing here will be of any real use to “regular users” of ProPresenter. Part 2 of a technical exploration of the ProPresenter 7 file format (.pro)
