'synthesized' encoding field value bug (?)

2018-10-05 11:14:23

This definitely was not present in older versions, but I'm not sure since which version it stopped working.
For synthesized files the %__encoding% field (which is 'synthesized') can be checked and returned fine, until you play the file. Then the file stops returning encoding field and displays a question mark.
I'm using OpenMPT 0.3.12 if that has anything to do with it.

Re: 'synthesized' encoding field value bug (?)

Reply #1 – 2018-10-05 12:58:19

I narrowed it down to Columns UI and OpenMPT combination, so I guess it's either a columnsui or an openMPT bug.
Neither openmpt with dui nor foo_dumb with cui produce this error.

Re: 'synthesized' encoding field value bug (?)

Reply #2 – 2018-10-06 05:00:10

Nope, it's not an issue with Columns UI. The OpenMPT component(s) never implemented $info(encoding) -> "synthesized", because I forgot to do that, and they picked up most of their recent changes from me. I have since added this to my fork, which is now 0.3.12+1.

I denote my fork's version numbers based on the version number of the libopenmpt that they're built against, with +N added if I make any commits to the frontend plugin after updating to a particular version of libopenmpt. This version is 0.3.12, plus one release: The $info(encoding) -> "synthesized" attribute.

You can probably help get this added to the official libopenmpt plugin as well, I don't control that repository, so I can't exactly make the change unilaterally.

E: By picked up changes from me, I mean that I have contributed to the frontend plugin development for foobar2000. Otherwise, I have only contributed minor changes to what is otherwise the gargantuan effort behind libopenmpt and OpenMPT. I am ever thankful that their team makes their work available for people like me to use, and share it with the foobar2000 space. And they also provide their own official binaries, which are updated with the library, and usually faster on the uptake than I am with my manual updates.

Re: 'synthesized' encoding field value bug (?)

Reply #3 – 2018-10-06 11:27:05

Cool, didn't know about your fork. It does work, thank you.

Re: 'synthesized' encoding field value bug (?)

Reply #4 – 2018-10-07 03:33:11

The official will likely have that minor addition in the next public release, or this current one, if they decide to replace it just for that minor change. I just need to tell them about it.