|
From: Ivan M. <iv...@ma...> - 2019-12-12 03:38:59
|
Hi Christian On 11/12/2019 12:30, Christian Schoenebeck wrote: > > Hmm... I wonder what GSt actually expects on gig file level if no loop was > enabled. I mean it's probably not a big deal if GSt spits out a warning on > such gig files, but would be nice to have if fixed on libgig side if > reasonable. > > Can you identify what GSt instrument editor changes/fixes after you created a > simple .gig file from scratch with Gigedit with no loop on? Yes, I managed to get GSEdit3 to output debug logs showing the structure (as it sees it) of input gig files (like gigdump in LS). This showed me several differences between gig files created with gigedit and the ones corrected by GSEdit3. The problem causing the 'irregular structure' message was the wrong number of '3gnm' strings - there should always be 128. There was also a duplicate DimensionRegion chunk being created when designing an instrument from scratch with gigedit. Finally, I discovered two new chunks from the official spec. They always seem to have the same content and I have no idea what they do :-) I just wanted to rule them out as a cause of the problem. I've attached a patch with these changes. > > CU > Christian > All the best, Ivan |