One button to rule them all

Scrivener Scrivener for Windows
,
1

I write with Scrivener and Aeon Timeline 3, which share my screen as I write. The idea is to turn on my PC, press a single button, and dive straight into writing without manually launching and then positioning Aeon Timeline 3 and Scrivener.

To accomplish this, I have set up automation via Elgato Stream Deck to:

  1. Open and position Aeon Timeline 3 on my screen;
  2. Open and position Scrivener on my screen; and
  3. Navigate Scrivener to where I left off in my writing project.

I succeeded, but something unexpected is going on, which is why I’m posting about it. When I boot up my PC, the first time I launch Scrivener it takes 20 seconds to launch (with or without launching from Stream Deck). I have to set a 20-second delay in Stream Deck to account for this:

2
2707×947 31.8 KB

This makes it hard to set the Multi Action Delay timing, because sometimes I want to relaunch Scrivener later in the day without turning off my PC. But if I have just one button, it has to be set to the longest it would take to launch Scrivener after booting up (20 seconds), defeating the purpose of quickly getting down to writing in the afternoon. (Why wait longer than needed for Scrivener to launch the second and subsequent times?)

My workaround is to create two buttons: one for the first launch of Scrivener after booting my PC and the other for subsequent relaunches. So, here is the timing for the second button:

3
3695×957 33.2 KB

I can live with this, though it defeats my goal of having one button to rule them all. :rofl:

But it makes me curious about Scrivener:

  1. Why does Scrivener for Windows take longer to launch the first time following a PC boot than it does if closed and reopened?

  2. Is there anything I can do to reduce the time for Scrivener to launch the first time following a boot of the PC?

FYI, in case it matters, here are my machine specs: AMD Ryzen 9 5950X 16-core/32-thread processor at 4.9 GHz | 128GB RAM | NVIDIA GeForce RTX 4090 GPU | 2TB internal SSDs | Samsung 49-Inch CRG90 Curved Monitor | Elgato Stream Deck.

2

I checked with Copilot about this. Here’s what it came up with (which seems valid):

Why Scrivener Takes Longer to Launch After a PC Boot

The first launch of Scrivener after a system boot takes longer due to several factors:

  1. Cold Start vs. Warm Start – When you first boot your PC, Scrivener isn’t cached in memory, meaning Windows has to load all necessary files from your SSD. Subsequent launches benefit from caching, making them faster.
  2. Background Processes – On first launch, Scrivener may be initializing dependencies, checking for updates, or verifying license information.
  3. Antivirus Interference – Some antivirus programs scan applications more thoroughly on their first launch after a reboot, slowing things down.
  4. Windows Indexing & File Access – If Scrivener stores project files in a cloud-synced folder (like OneDrive), Windows may be indexing or syncing them, causing delays.
  5. Scrivener’s Auto-Load Behavior – If Scrivener is set to reopen the last project, it may take extra time to load large files or complex projects.
3

I believe this is more or less down to Copilot’s reason #1. Scrivener loads a bunch of stuff (technical term) at first launch; subsequent launches then pull from a cache.

If nobody with actual technical specifics happens along, you can possibly figure out the difference yourself between first and subsequent launches by enabling and studying the output from File > Options > General > Startup > Warnings > Show internal log console.

I doubt it!

However – If nobody comes along with something more elegant, something to try is

  • Create a very lightweight Scriv project (empty except for 1 blank doc)
  • Create a script that launches the LW project, waits the 20 seconds or whatever, then closes it
  • Launch the script automatically at Windows startup
  • Then, once your PC is up & running, you can press the magic button (you should be able to remove the 20 second wait)

Probably not exactly what you were looking for, but maybe it’ll give you ideas for something better?

Best,
Jim

3 Likes
4

Hey, Jim. I think your idea of launching a lightweight project at startup is interesting, though I’m not sure it really gets me anywhere. If I’m sitting here waiting for it to launch (and close) at startup, I might as well just launch the actual project, right?

So, I shall have two buttons to rule them all. :joy:

5

It’s all down to the result of your cost / benefit analysis: some extra seconds on the front end vs freeing up a button. (Plus the one-time cost of writing the startup script.) Only you know what an extra button is worth to you. :nerd_face:

One extra factoid to add to that equation -

I have a lightweight Scriv project that I use to test changes to themes.

My LW project takes 12 seconds on first launch, 5 seconds on second launch.

My old Lenovo laptop is far underpowered relative to your PC, which makes me wonder how much faster a LW project would start on your machine, first launch. And how fast it would close, if that project was set to turn off auto-backups.

I bet a lot faster than 20 seconds. This would be easy enough for you to test.

1 Like