Just go to the Download section of this site and download the Belle Nuit Subtitler application. The application is functional in offline license mode, that means export is limited to 10 titles. Try the program out and when you are ready, go to the Kagi site and buy the online license.
The keyfile was not saved. On OS X you need an account with administrative rights to save the keyfile.
We get some, but very few reports on this. It looks like you disabled too much on your system folder. Try on a clean system. Or use Belle Nuit Subtitler 1.1.
Report us these errors, so that we can narrow them.
On OS X yes. You can even have one line of Roman and one line of non-Roman characters for the fonts which support that (for example Lucida Grande). Note that character spacing is disabled for Non-Roman fonts and that simple and smart wrap work only on langauge with spaces (eg not in chinese and japanese).
On OS 9 it may work with some fonts, but we do not officially support it.
Yes, you can. It works flawlessly on DV or digital video projects
(720*576 or 720*480 pixels). Export your titles to TIFF-RLE. Drag
them to your bin. You may adjust the alpha-settings of the
clip-property to get proper transparency. Depending your hardware,
imported titles have to be rendered. Like internal titles, preview
does flicker on 25% and 50% views, but this is related how FCP shows
the image on the monitor and has no influence to the final
output.
If you have a timecoded titlelist, you can import it into Titlelistconverter and export and EDL and a Subtitler file. The EDL has comments, so that you can batch import the video files. You will not need to edit the titles manually.
Yes, you can. Export your titles to PICT-alpha and use the option "Invert existing alpha".
Yes, and Subtitler files are cross-platform.
You need a separate license for Subtitler for Windows.
You should know that there are 3 types of STL files:
Belle Nuit Subtitler supports import for basic textfiles. This includes texftiles with tabs (one tab field, one line) or with lines (one double paragraph as title separator).
The textfile must be a real textfile encoded in Unicode UTF-8 which is to become the native format of many text editors. If your textfile is MacRoman or ANSI, you need to open it in TextEdit and convert it to Unicode UTF-8.
Subtitler does not import RTF files. Open them first in TextEdit and save them as straight textfile (.txt) in the Unicode UTF-8 textencoding.
Subtitler does not import Word files. Unfortunately Word saves only in Unicode UTF-16, so this will result in an empty file in Subtitler. Copy-paste them directly into a new Subtitler document.
Some QT movies from nonlinear editing applications contain internal informations which make stepping difficult. If you use Final Cut Pro, you should not export a Final Cut Pro movie (File:Export:Quicktime Movie with a FCP icon) but export a Quicktime movie (File:Export:Using Quicktime Conversion with a native Quicktime icon).
If you put your subtitles inside the editing system, then there is no problem. Export as Quicktime 24p, set the framerate in subtitler to 24, spot, export and import the titles into the editing system.
The situation gets more complicated if you need to export an EBU (.stl) file. EBU does not support a framerate of 24, and the program in PAL will run 4% faster. You cannot simply set the framerate in subtitler to 25, because the movie in Subtitler always runs at 100%. This leaves you with three solutions:
This problem does not concern NTSC users. While the framerate 24 and 30 is different, the speed is still the same (if 24p is actually 23.976). If you encounter a problem, consider spotting the pulldown version of the film.
It depends on how the NTSC-PAL conversion was made. If it was a time-accurate video-conversion, then you can set:
If the conversion was made with a simple pulldown like MPEG conversions and the duration has changed, you need to make it in two steps. First correct the duration, then the framerate:
You have to export the TIFF files first and then export the XML file. If the Export folder is not defined, the path will not be included in the XML file. And if the TIFF file is not available during XML import in FCP, FCP decides that it is a clip and not a still. You can however still reconnect the media: Select all titles, do the menu command File:Reconnect Media, select Offline and Select Files manually (to avoid FCP from scanning the entire harddisk), then in the file dialog, set the Show popup-menu to Still Image Files and navigate to point to the first TIFF file. Select Reconnect all files with relative path to let find FCP the others. You will now also see in the timeline that the property of the clip changed from Clip to Still.
What you are seeing in Photoshop when you look at RGB only is the unmultiplied image.
As quite a few NLE support premultiplied alpha, the RGB values are unmultiplied by the alpha value.
You will see that in the Preview application the antialiasing looks fine.
In the compositing, when you set the alpha property right, the titles will look right.
For example in Final Cut Pro, if you select the clip in the sequence, check the menu Modify:Alpha Type.
the alpha type you have now is probably Black. it should be Straight.
Select all subtitles and set Modify:Alpha Type:Straight.
Final Cut Pro does not have an option to select the transparency of imported still files. It makes some guesswork and often guesses false and even inconsistely. It's possible that on the same import you may have mixed alpha interpretations. You can however change the alpha interpretation after import. Select the clips and then the menu Modify:Alpha Type:Straight.
Subtitler sometimes cannot successfully store paths to folders, when the path contains non-ascii characters or when the path is too long. Try to simplify the path (move the folder direct to the root of the harddisk.
Also, paths can be lost when you move the subtitler files between computers.
Note that black and white are not the same numbers in computer images and in video applications. Computer images have a rangefrom 0 to 255, video has a range from 16 to 235. Going outside this range results in illegal video levels.
This means for example if you need white titles with black borders for the Avid, you need to set the title color to 235,235,235 and the border color to 16,16,16 and to import the titles into the Avid at ITU (CCIR) levels.
This is a memory problem. If the program is running out of memory,
it will not antalias properly. Give Subtitler 25 MB of RAM and you
should be fine.
This problem should not happen any more with Subtitler 1.4.
This is a memory problem. If the program is running out of memory,
it will not work properly. Give Subtitler 25 MB of RAM and you should
be fine.
This problem should not happen any more with Subtitler 1.4.
No, it doesn't. Importing of a animated title would be longer than creating it inside Avid.
Ask me (matti@belle-nuit.com). Please understand however, that program support is limited to users with an online licence.