I'm curious, how you reversed engineer this, and I'm taking a look at a project file b

Problems trying to understand the format about flparser HOT 2 CLOSED

monadgroup commented on May 24, 2024

Problems trying to understand the format

from flparser.

Comments (2)

cpdt commented on May 24, 2024

Hey, I think you might've made a mistake, that line should be reading the 08/09 bytes:

FLParser/ProjectParser.cs

Lines 41 to 42 in 7c5e266

    
           if (Encoding.ASCII.GetString(reader.ReadBytes(4)) != "FLhd") 
        
               throw new FlParseException("Invalid magic number", reader.BaseStream.Position);

This will read the first 4 bytes, 00-03.

FLParser/ProjectParser.cs

Lines 44 to 47 in 7c5e266

    
           // header + type 
        
           var headerLength = reader.ReadInt32(); 
        
           if (headerLength != 6) 
        
               throw new FlParseException($"Expected header length 6, not {headerLength}", reader.BaseStream.Position);

This will read the next 4 bytes, 04-07 (Int32 is four bytes).

FLParser/ProjectParser.cs

Lines 49 to 50 in 7c5e266

    
           var type = reader.ReadInt16(); 
        
           if (type != 0) throw new FlParseException($"Type {type} is not supported", reader.BaseStream.Position);

So this will then read bytes 08-09 (Int16 is only two bytes).

As for how it was reverse engineered, the basic parsing structure and some of the "event types" were from andrewrk's Node FL parser library (which is very out of date now) and the rest was just from changing different values in FL and seeing what changed. As far as I'm aware his library was based on an old implementation in LMMS (which doesn't exist anymore afaik) which was based on an old thread somewhere (which I haven't been able to find again) where an Image-Line employee talked about the basic structure.

I'll close this thread for now, but if you have any other questions please feel free to ask them!

from flparser.

JakubKoralewski commented on May 24, 2024

I see it now, I somehow mistook a byte for 4 bits 😄.
Thanks for the patience and the detailed answer.

github.com/LMMS/lmms/pull/2904
Seems like it was a licensing problem.

from flparser.

Recommend Projects

Problems trying to understand the format about flparser HOT 2 CLOSED

Comments (2)

Related Issues (12)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

	if (Encoding.ASCII.GetString(reader.ReadBytes(4)) != "FLhd")
	throw new FlParseException("Invalid magic number", reader.BaseStream.Position);

	// header + type
	var headerLength = reader.ReadInt32();
	if (headerLength != 6)
	throw new FlParseException($"Expected header length 6, not {headerLength}", reader.BaseStream.Position);

	var type = reader.ReadInt16();
	if (type != 0) throw new FlParseException($"Type {type} is not supported", reader.BaseStream.Position);