citp-protocol.org

May be this is clear, but i still don't understand some things. I was read docs about "physicaloutput" parameter, but ... Tell me if i wrong. VSRC - this is a only message for naming channels (outputs) and layers. Information about binding layer to output can be found in LSTA message, ok?...

My question is about mediaserver with multiple physical outputs. How can i divide it into multiple independed units ? Should i run multiple PLoc threads with different ports or no? Please suggest fr me right decision. No, you do not need to send multiple PLoc messages. I'm a bit confused by the que...

As discussed in the forum, I have added the 3D Mesh element type, corrected a typo and clarified the uint16 fields of the MSEX 1.2 ELUp message.

The CITP_MSEX_1.2_ELIn message allows for more than 256 libraries and/or elements. The CITP_MSEX_1.2_ELUp message is limited to 256 in the number of libraries and/or elements it can report. There is a disparity between the two messages. Yes and no. Sure, uint16 allows for big numbers, but is necess...

tomgr wrote:The example text associated with 10.4.1 MSEX/GELI shows library id's such as {1,0-256,0,0} and {2,0,0-256,0}. The range 0-256 is incorrect, a total of 257 elements and larger than 8 bits. The range should be 0-255.

You're right - fixed this now.

tomgr wrote:Not sure of the intent of the AffectedLibraries bit field. Is this intended to provide a hint to the client to dig deeper into the library structure for further changes?

Well, the element library as such has properties too such as its name, which is perhaps the most likely to change.

The product is the High End Systems DL/Axon media server. The server is a 3D server. Media is textured onto variously shaped 3d meshes. Meshes range in shape from highly abstract, to product logos, to 2D rectangles. I'm in favour of adding a new type then, "3D Mesh" on the next available ...

I have just updated the spec with a couple of minor changes:
- Corrected []-typo for the image buffer of thumbnail messages
- Style fix of logo and removed the "protocol stack" illustration that didn't come out right anyway

Hi Tom, Unless you reveal more detail about your product and the properties of these mesh objects, I think it will be difficult to help you choose one of the existing. We could of course add a new, but then the question becomes how existing products will behave - will they ignore it alltogether or a...

Hi Tom, This is very much to your implementation I would say. I would say that the specific path on disc where your media resides is not very interesting to the consumer, unless each media is possibly in a different location and the path is important (say if you had c:\green\logo.mpg, c:\red\logo.mp...