Andreas Kiel
Forum Replies Created
-
Some maybe stupid question. Why do you export/import XML on the same machine?
Andreas
Spherico
https://www.spherico.com/filmtools -
30″ with 2560×1600 are big enough for sure.
But as said, what counts is not the displayed size, but the real size. This from your screen shots is totally correct.
You may try to hit cmd-1 in the QT7 Player and refresh the Inspector. You also may use cmd-J in QT 7 Player to figure out the discrepancy about real and display size.
There are some apps which really do use the display size, but as long you do not save the files displayed in QT Player there won’t be any issue.Spherico
https://www.spherico.com/filmtools -
Some edit to my earlier post is are a bit of math.
If your display doesn’t match, means has enough space for title bars in the vertical, then this scenario can happen:
The title bar uses 16 px, subtract this from the actual image height. You’ll get 1064 px displayed image height. This divided by 9 results in 118.222222222222222 which is not possible to display with an 16:9 picture
since picture width would be 1891.555555555555556.
So it’s rounded down to 118. Resulting display will be 118×9 = 1062 and 118×16 = 1888As said it’s only the display size
Spherico
https://www.spherico.com/filmtools -
Edit NTSC in a NTSC project/sequence.
Once you’re done convert. Use either Nattress or Compressor (or hardware).Spherico
https://www.spherico.com/filmtools -
A bigger display connected to your computer will fix this 🙂
1888×1062 is the displayed size!It has nothing to do with the real size, as you see in your screen shots.
Spherico
https://www.spherico.com/filmtools -
Beside Bouke’s excellent Subbits you try my TitleExchange.
I can read DVDSP track files and convert them to FCP XML files with a generator of your choice (as long as the generator has no special text encoding/decoding needs like with Boris)
You can get the demo here:
https://www.spherico.com/filmtools/TitleExchange/Andreas
P.S. it’s never a good idea to create subtitles within DVDSP
Spherico
https://www.spherico.com/filmtools -
You have to de-interlace/re-interlace if you do a down conversion from interlaced HD to interlaced SD broadcast – regardless of the codec.
Spherico
https://www.spherico.com/filmtools -
As Shane said, keep the proportions in square pix. For a 16/9 1920×1080 video it’s 1920×1080. If you want to zoom you might have to multiply the x/y values by the zoom factor.
The bad thing is that different apps/companies do have a different opinions how to handle square pix from a still within a non-square video timeline. Even worse is that this might change by versions of the app.
With FCP they are constant and you can rely on that, with Premiere/AE it has changed over the versions and currently it is different from FCP’s calculation. It’s the ever lasting fight about vertical blanking in the digital world. So you might experience a 3% horizontal for example with SD. Other formats and other NLEs might or might not slightly squeeze horizontal.Spherico
https://www.spherico.com/filmtools -
I don’t know Michael’s online generator. But you can check the XML generated by it. If it contains ‘-Hi-Hi’ then there is something wrong within the XML.
If you are using 7.0.2 this might be an issue as well. That version did some weird handling for linebreaks.
You may download my TitleExchange, it’s shareware and the demo/free version is limited to 50 titles. But there is a helper app called ‘gText’ after you installed – this app is free. gText allows you to see all subtitle text of an XML in FCP format in a kind of spread sheet.
You can step thru the subtitles easily and change them. The changes can be saved back to the XML without destroying the settings of the original generator.
Maybe you test the TitleExchange app with SRT as it can convert SRT files to FCP XMLs with your DH_Subtitle generator, but as said TEP is not free.Andreas
Spherico
https://www.spherico.com/filmtools -
Export to XML. But you will loose several things.
Andreas
Spherico
https://www.spherico.com/filmtools