DCP-o-matic users June 2013

users@lists.dcpomatic.com

10 participants
12 discussions

by Carsten Kurz

Did anyone have the same experience: I was checking the trim feature yesterday with specially made test footage - an MP4 file with frame accurate numbers counting from 1 to 300, white numbers on black background. On my sandybridge notebook, it converted at around 4fps, no special processing (1998*1080 in, 1998*1080 out). With real word footage (but also a large number of black frames at the beginning), I only get around 1fps conversion speed, sometimes even below that. Is the J2k compression speed depending on content complexity or target datarate? I could see in the log that the MXF frame write intervals reflected these different conversion speeds perfectly. Both files on local disc. Will need to do some more testing. I have a large project with a lot of partial/trimmed conversions ahead. Carl - when using encode servers, I guess the main dvd-o-matic server will send uncompressed still images to the remote J2k encode servers? That's why a Gigabit network is beneficial? - Carsten

11 years, 10 months

[DVD-o-matic] [0.89] crash with negative audio gain values

by Karim 'Kasi Mir' Senoucci

Hello again, I just encountered another problem with DVDom; I had a source file where the audio is a little too loud. Thus I entered a negative value in "Audio Gain" on the Audio Tab. Promply, DVDom (both the full gui and the batch encoder) crash as soon as the conversion is started. I could reproduce this behaviour with four different Quicktime sources with the value "-10", so I guess this happens every time I enter "-10", at least with quicktime source files. Did I do something wrong? Should I do something different to tone done the audio during conversion? As before, any help is appreciated. Greetings from Germany Kasi Mir

11 years, 11 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

DCP-o-matic users June 2013