DCP-o-matic

Clicking on any of the FAQ topics here only brings up an empty page...

http://dcpomatic.com/faq

So it was basically an issue with the CPU overheating then?

That's good to know. I was thinking of building a computer with a Ryzen 7 CPU, but I haven't decided yet. The new Intel Coffee Lake i7 looks interesting as well...

If you have a license key for Windows 7 Professional, you can download the Media Creation Tool from Microsoft and use it to create the installation disc for Windows 10 Professional. https://www.microsoft.com/software-download/windows10 It's usually no problem to install and activate Windows 10 with ...

http://dcpomatic.com/forum/viewtopic.php?f=2&t=825 Burn-In - yes, when you burn in subtitles, a complete re-encoding must be done for obvious reasons. In theory, DOM could restrict the reencoding to parts with subtitles only and pass through other footage, but that would be a bad idea. - Carste...

Yes, works fine now!

Well, dumping out the relevant part of the .mxf-file gives the following result, except that I have replaced all the spaces with "@"-characters to make them stand out. My guess is that any spaces present between <dcst:Text> and </dcst:Text> are significant and will be rendered by the playe...

I've made a very small test project that I can share, and which will illustrate the problem: First, I made a very simple subtitle file consisting of only one item: 1 00:00:01,000 --> 00:00:09,000 Testing is <i>really</i> fun! This is the <i>second</i> line! Then, I read that .srt-file into Subtitle ...

Sorry to disturb again, but the case where regular and italic fonts are mixed on the same line seems to be almost impossible to get right. Same subtitle source as before, but this time soft = NOT burnt in. DOM version is 2.9.38 and playback is by Easy DCP player version 3.4.5. http://hem.bredband.ne...

Yes, a quick test indicates that the problem has indeed been solved in version 2.9.38 !

I don't know what kind of mistake would cause that kind of behaviour... ?! Anyway, I tried reverting to version 2.9.30 and the problem immediately went away. I then re-installed 2.9.37 and the problem came back. So toggling back and forth between the versions makes it completely clear to me that it ...