mltframework / mltframework/mlt
XML consumer not serializing full multitrack graph
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.9k
- Forks
- 387
- Avg merge
- 17h 28m
- Merged PRs (30d)
- 8
Description
I am writing the results of my video graph out to XML via the XML consumer which I will then run through melt. This has worked fine when my producer was simply a playlist. I increased the complexity of my program to use a multitrack, but now the output of my XML is devoid of much of the information that should be in there.
<?xml version="1.0" encoding="utf-8"?>
<mlt LC_NUMERIC="en_US" version="6.17.0" root="C:\Clients\MyClient\Projects\VideoGenerator\Dev\ConsoleRunner\build\Debug-Windows\netcoreapp2.2" title="Anonymous Submission" parent="producer0" in="" out="">
<profile description="DV/DVD PAL" width="1920" height="1080" progressive="0" sample_aspect_num="1" sample_aspect_den="1" display_aspect_num="889" display_aspect_den="500" frame_rate_num="30" frame_rate_den="1" colorspace="601"/>
<producer id="producer0" in="" out="">
<property name="length">1246</property>
<property name="eof">pause</property>
<property name="resource"><tractor></property>
<property name="mlt_service">tractor</property>
</producer>
</mlt>
Just to make sure I didn't do something wrong, I changed the consumer to sdl2 and sure enough, my video plays as expected.
I'm not receiving any warnings, errors, or odd behavior otherwise.
Is there something I'm missing?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the XML consumer entry point and compare its output for a playlist with the multitrack graph described in the issue. Check how the generated XML is passed to melt, using the working sdl2 playback as a behavioral comparison. Done means the XML contains the full multitrack graph and can be processed by melt.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, xml
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100