ppavc is now called "endemm".

I have renamed the ppavc project to "endemm" for obvious problems when the name is pronounced in english. "endemm" should work better. It is an abbreviation for "encoder and decoder for multimedia".

The repository has already been renamed which means that you need to update the origin in git when you had previously checked out ppavc.

The project page is now located here: https://codeberg.org/ncc1988/endemm

#ppavc #endemm #floss #software #development

ppavc is now called "endemm".

I have renamed the ppavc project to "endemm" for obvious problems when the name is pronounced in english. "endemm" should work better. It is an abbreviation for "encoder and decoder for multimedia".

The repository has already been renamed which means that you need to update the origin in git when you had previously checked out ppavc.

The project page is now located here: https://codeberg.org/ncc1988/endemm

#ppavc #endemm #floss #software #development

I have created a draft for command line argument handling in ppavc. Contrary to ffmpeg, the command line arguments in ppavc would not have to be placed at a certain position. Here is the current draft with a complex and a simple example for the command line arguments:

https://codeberg.org/ncc1988/ppavc/issues/5

Questions? Comments? Feel free to write them here. 🙂

#ppavc #commandline #FLOSS #software #development

I have created a draft for command line argument handling in ppavc. Contrary to ffmpeg, the command line arguments in ppavc would not have to be placed at a certain position. Here is the current draft with a complex and a simple example for the command line arguments:

https://codeberg.org/ncc1988/ppavc/issues/5

Questions? Comments? Feel free to write them here. 🙂

#ppavc #commandline #FLOSS #software #development

ppavc development fun:

When writing wave data into a RIFF container in packets, the RIFF container instance must track the number of written bytes to be able to update the chunk size of the "data" and "RIFF" chunk after the last data packet has been written. The code for that is in the „processing-chain“ branch:

https://codeberg.org/ncc1988/ppavc/src/branch/processing-chain

ppavc - planned program for audio and video conversion.

#ppavc #FLOSS #Software #development #RIFF

ppavc development fun:

When writing wave data into a RIFF container in packets, the RIFF container instance must track the number of written bytes to be able to update the chunk size of the "data" and "RIFF" chunk after the last data packet has been written. The code for that is in the „processing-chain“ branch:

https://codeberg.org/ncc1988/ppavc/src/branch/processing-chain

ppavc - planned program for audio and video conversion.

#ppavc #FLOSS #Software #development #RIFF

ppavc development fun: Defining methods for audio chain objects and writing code where each object can pass data to the following objects in the chain. But there was no method for the last objects in the chain to send data somewhere else, so the data gets discarded and no output is produced. This has been fixed now:

https://codeberg.org/ncc1988/ppavc/commit/a0034d94c1356e6ee1bccf9f286ddc5476319c80

(ppavc = planned program for audio and video conversion)

#ppavc #FLOSS #software #development

ppavc development fun: Defining methods for audio chain objects and writing code where each object can pass data to the following objects in the chain. But there was no method for the last objects in the chain to send data somewhere else, so the data gets discarded and no output is produced. This has been fixed now:

https://codeberg.org/ncc1988/ppavc/commit/a0034d94c1356e6ee1bccf9f286ddc5476319c80

(ppavc = planned program for audio and video conversion)

#ppavc #FLOSS #software #development

I'm doing another refactorisation in ppavc (planned program for audio and video conversion): inverting the relationship between media containers and codecs, giving codecs more control.

The background is that codecs are the first and last elements in conversion chains. Each input codec now reads data and passes them to the next chain object until they reach an output codec which will then write the data into an output container.

https://codeberg.org/ncc1988/ppavc/issues/4

#ppavc #software #FLOSS #development

I'm doing another refactorisation in ppavc (planned program for audio and video conversion): inverting the relationship between media containers and codecs, giving codecs more control.

The background is that codecs are the first and last elements in conversion chains. Each input codec now reads data and passes them to the next chain object until they reach an output codec which will then write the data into an output container.

https://codeberg.org/ncc1988/ppavc/issues/4

#ppavc #software #FLOSS #development

Which notation for identifying media streams you find more readable?

- ffmpeg: "0:0", "0:1", "1:0", "1:2"

- ppavc: "0:A0", "0:V0", "1:V0", "1:A1"

#ffmpeg #ppavc

Which notation for identifying media streams you find more readable?

- ffmpeg: "0:0", "0:1", "1:0", "1:2"

- ppavc: "0:A0", "0:V0", "1:V0", "1:A1"

#ffmpeg #ppavc

Spending more than half an hour to figure out how to use ffmpeg's filters so that three inputs are combined into one output with one audio and video stream is one example why I'm attempting to make such tasks easier by working on ppavc and its scripting support.

https://codeberg.org/ncc1988/ppavc/issues/1

#ffmpeg #scripting #ppavc #FLOSS #software

Spending more than half an hour to figure out how to use ffmpeg's filters so that three inputs are combined into one output with one audio and video stream is one example why I'm attempting to make such tasks easier by working on ppavc and its scripting support.

https://codeberg.org/ncc1988/ppavc/issues/1

#ffmpeg #scripting #ppavc #FLOSS #software

I now have a plan to complete the refactorisation of ppavc. In short: Documentation, renaming and documentation. After it is completed, ppavc should be able to connect to ffmpeg:

https://codeberg.org/ncc1988/ppavc/issues/2

#ppavc #Software #FLOSS

I now have a plan to complete the refactorisation of ppavc. In short: Documentation, renaming and documentation. After it is completed, ppavc should be able to connect to ffmpeg:

https://codeberg.org/ncc1988/ppavc/issues/2

#ppavc #Software #FLOSS

Status update:

I have converted the source code of ppavc to modern C++ and fixed errors in the RIFF container handler (that is still in "cha bu duo" quality).

Now I need to check for undefined behavior and memory leaks before I can define interfaces and use ffmpeg objects in ppavc.

Scripting support is still far away, but getting a step closer. 😉

https://codeberg.org/ncc1988/ppavc

#ppavc #Video #Software #FLOSS

Status update:

I have converted the source code of ppavc to modern C++ and fixed errors in the RIFF container handler (that is still in "cha bu duo" quality).

Now I need to check for undefined behavior and memory leaks before I can define interfaces and use ffmpeg objects in ppavc.

Scripting support is still far away, but getting a step closer. 😉

https://codeberg.org/ncc1988/ppavc

#ppavc #Video #Software #FLOSS

I'm thinking about reviving a project of mine called "ppavc", with the goal of providing easy access to ffmpeg and its filters using YAML files. These would let you describe the timeline of the desired output: When to play which file and which filters to use on what channel and how to switch to the next input file in the timeline. I created an issue for this in the project at Codeberg which has a sample YAML file:

https://codeberg.org/ncc1988/ppavc/issues/1

#ppavc #Video #ffmpeg #Scripting #Software #FLOSS

I'm thinking about reviving a project of mine called "ppavc", with the goal of providing easy access to ffmpeg and its filters using YAML files. These would let you describe the timeline of the desired output: When to play which file and which filters to use on what channel and how to switch to the next input file in the timeline. I created an issue for this in the project at Codeberg which has a sample YAML file:

https://codeberg.org/ncc1988/ppavc/issues/1

#ppavc #Video #ffmpeg #Scripting #Software #FLOSS