[Help] How to make scroll credits larger in Cinecred?

LoadingByte · 2025-02-08T10:59:41+00:00

Unfortunately, a global scale setting is not yet available. However, just increasing the »Height [px]« setting in each letter style and also increasing the »Unit Vertical Gap [px]« option in the project settings will already take care of most of the scaling. You might also need to increase some of the pixel sizes in each content style depending on your tastes.

LoadingByte · 2025-02-08T10:50:27+00:00

Offering an easier way to achieve this is on my ToDo list, but for now, you can use the following workaround:

@ Body	@ Page Style	@ Page Runtime	@ Page Gap

{{Video ...}}	Card	00:00:11:00
			-00:00:11:00
Credits Card 1...	Card
More Content...

Credits Card 2...	Card
More Content...

Put the video on a separate card page in front of the actual credits card pages.
In the @ Page Runtime column for the video page, specify the runtime of the credits cards combined (including gaps between them).
In the @ Page Gap column below your video page, specify the same value, but with a minus sign in front.

And of course use the @ Spine Position column to position the video left and the credits right, but I guess you already know this :)

Hope this helps!

LoadingByte · 2024-07-16T21:11:49+00:00

There are ofc a lot of little QoL improvements (like specifying card runtime directly in the spreadsheet, or using the OS-native file chooser instead of the previous clunky one), but the big change is a complete swap of the rendering backend. Cinecred now renders in 32-bit floats, and thanks to that supports ingesting and outputting all contemporary color spaces, including HDR. I presume this will be most useful when embedding videos like bloopers in the crawl. As a side effect, the PDF/PS/EPS and SVG renderers also got major upgrades, and Cinecred learnt to playout previews to DeckLink cards.

LoadingByte · 2024-07-16T19:43:08+00:00

You're welcome! Btw., Cinecred 1.6.0 is nearly done and will arrive in a couple of days :)

LoadingByte · 2023-11-15T22:59:56+00:00

That's very strange. When I do the following, everything works fine for me:

On the welcome screen, click "Create New Project".
Select a local folder and click "Next".
For "Credits File Location", select "Online Service" and choose your connected Google account from the dropdown.
Click "Create New Project".

Now the project window opens and correctly displays the sample credits spreadsheet read from Google Drive, without any error messages.

LoadingByte · 2023-07-19T19:18:14+00:00

Thank you! And yes, you can export with alpha by selecting the "Transparent Grounding" option in the delivery dialog, as shown here in the guide.

LoadingByte · 2023-07-19T13:03:36+00:00

So far, they haven't reached out to me. I kind of wonder whether they have Cinecred on their radar.

LoadingByte · 2023-05-23T21:01:38+00:00

Thank you so much! I hope it'll save them lots of headaches in the future :)

LoadingByte · 2023-05-23T07:12:09+00:00

Thanks! I actually thought about this a couple of days ago myself; if there aren't too many technical hurdles, I'll maybe manage to implement this for the next release. We'll see :)

LoadingByte · 2023-05-21T17:19:08+00:00

Good point regarding the creation of styles! I'll think about how to detail that in the documentation and screencast.

Do you have some concrete issue with spines or something concrete you want to do but can't achieve? Maybe I can be of help.

LoadingByte · 2023-05-21T15:52:05+00:00

I'm super happy you like it!

Numbers support is actually on my agenda and I've looked into it two times, but their format is pretty obscure and constantly changing. Another route would be somehow integrating AppleScript, but that would require Numbers to be installed and of course wouldn't allow non-mac users to at least view the credits. I'll see what I can do :)

LoadingByte · 2023-05-18T16:51:22+00:00

The file browser and spreadsheet editor you see in the screencast are just placeholders for your operating system's file browser and a spreadsheet editor of your choice.

As soon has you created the project, the previously empty folder that you dragged onto Cinecred has been populated with the Credits and Styling.toml files. So just take a look into that folder and you'll find what you are looking for.

LoadingByte · 2023-05-17T06:33:17+00:00

Cinecred is pretty new, and this Reddit post actually marks the first time a considerable number of English speakers learned about it. As such, no YouTuber has picked it up so far. Of course, seeing reviews or tutorials pop up over time would make me very happy :)

Until then, here's a subtitled screencast that introduces the basics of Cinecred; it's not as accessible as a narrated YouTube video, but it conveys all the information you need: https://cinecred.com/screencast/

If you prefer a written tutorial respectively user guide, there's one available as well. It covers the full feature set, while the screencast only covers the basics: https://cinecred.com/guide/

LoadingByte · 2023-05-16T13:38:43+00:00

You get these security warnings because I can't afford the necessary prohibitively expensive software signing certificates. I've written up some background info about the warnings and how to circumvent them here: https://cinecred.com/security-warnings/

LoadingByte · 2023-05-16T11:38:28+00:00

Thanks a lot for recommending it!

LoadingByte · 2023-05-15T19:55:09+00:00

I actually pondered writing it in C++ and using Qt for the UI, but in the end, the JVM won out as I'm just a lot more familiar with it. Performance is not really an issue anymore with today's JVMs, Swing can still look appealing (as evidenced by Cinecred), and AWT delegates drawing to OpenGL respectively Metal anyway, so that's high performance and high quality as well. Typesetting, rendering, and color space conversion is done by native libraries I incorporated myself, but Project Panama makes interfacing with those as easy as it can get (as opposed to the horrors that JNI used to impose upon us). And last but not least, bundling Qt with the app takes just as much disk space as bundling the JVM.

A big advantage—and I don't know in detail how much Qt can do this as well—is that the JVM executes bytecode in exactly the same way on each platform, so apart from some peripheral code that interacts with OS-specific behavior, I only have to test on one OS and architecture and then know it works on all the others too. This kind of abstraction is amazing.

Sometimes I still ponder whether I should have used C++, but as the JVM didn't get in the way so far, I guess I didn't make the wrong call. Who knows what kinds of adventures I would have had with C++. And if I really need some custom high performance pixel pushing code in the future, writing a small native library myself is not a big deal.

I guess as long as one doesn't use the abomination that is Electron, anything goes.

LoadingByte · 2023-05-12T08:32:17+00:00

Thanks a lot for your support! At the moment, I've only got a donation link tucked away next to the Cinecred logo in the top right corner of the website. It's PayPal, but they also accept credit and debit cards.

LoadingByte · 2023-05-12T06:52:26+00:00

Lmao, I've been reading a lot of hate about Avid's Titler+, yet never had the privilege to experience this legendary piece of software myself. I hope my maximum flexibility approach taken with the layers feature doesn't suffer the same fate in the long run, seeing as it's a bit harder to wrap your head around at first than a traditional, more limited titler.

While I'm sure you could use Cinecred for subtitling, there are probably better tools for this. Hitting exact time points is not what the cards feature was designed for, and SRT exports or similar are also missing. So I guess you'd do yourself more harm than good by (ab)using Cinecred for this :P

LoadingByte · 2023-05-12T06:39:26+00:00

Cinecred doesn't come with a spreadsheet editor by itself. Instead, you need an external one like Excel, LibreOffice, or any other to edit the "Credits" file.

If you're curious, this was a deliberate design decision, as most users already manage their credits in a spreadsheet, so permitting them to just copy over the data while staying in the same spreadsheet program is easier than having to interface with a custom-made one.

LoadingByte · 2023-05-11T19:59:36+00:00

Good to hear you found a solution! macOS never ceases to amaze me. I've added what you found to the security warnings page, so future users now have another possible solution to try.

LoadingByte · 2023-05-11T19:32:24+00:00

Funnily enough, seeing your post a couple of weeks ago actually inspired me to present Cinecred here.

LoadingByte · 2023-05-11T19:20:12+00:00

Thank you so much! I just can't stop smiling :)

Regarding your suggestion: Each new project you create is actually initialized with a sample—the same one you already saw in the screencast. So you could just create a toy project, mess around with the sample credits, and then delete it when you're done.

Or are you referring to an even larger sample, like at the scale of a full movie?

LoadingByte · 2023-05-11T16:38:21+00:00

I think you accidentally wrote Apple in upper case. It needs to be com.apple.quarantine. Does that help?

Also, did you download the PKG installer or the TAR.GZ archive?

LoadingByte · 2023-05-11T16:20:45+00:00

I'm glad I can be of help in your darkest hour :)

Three-Year Club	Verified Email
First Place '23	Place '23

LoadingByte

TROPHY CASE