A disk on the server ran out of space. Things should be working again.

I'm not really interested in making the site a place to upload POV demos. I have no problem with some POV demos being uploaded but if they get uploaded in large volumes I might have to implement some measures to keep the hosting sustainable.

These sound reasonable and I might add them some day.

fixed

- improved handling of some demos where the recording wasn't finished correctly, leading to a truncated demo

- Fixed an issue where the editing would crash when trying to unlock pov on an stv demo
- It now shows if there was an error during editing instead of showing nothing

Yes,

I'll look into adding a separate download button for cases where it doesn't start automatically

It should automatically start the download once the processing is completed

demos.tf now includes the a demo editor to perform some limited editing to demo files: https://demos.tf/edit

The editor currently comes with the following options:

• pov unlock:
  
  Allows unlocking the camera in pov demos, allowing free camera movement as if it were an stv demo
  
  
• demo cutting:
  
  Allows cutting/trimming the demo file down to a specific tick range.
  This can be used to remove the need to spend a long time seeking through the demo in game to record that one airshot 23 minutes into the game.
  

Although it usually works, editing, and especially cutting, is still experimental and the resulting demo files might be broken in any number of ways.
If you're experiencing issues with a cut demo, trying to set the start tick a few seconds earlier or later can sometimes helps to alleviate some issues.

You're pretty much completely right, I never bothered adding pause handling, to do it properly would probably involve cutting out the pauses when caching the tick data and save the pause start/end tick so you can later translate the ticks back.

I've never done this because I've personally never had to open a demo in the browser that had a tick in it :)

looks like this has been resolved

Did updating existing logs per round break? Since yesterday it's creating a new log per round instead of updating the existing one and I didn't change the anything on the server.

After a long period of downtime, caused by issues with the previous hosting provider, I've finally had enough time to properly move everything over to a new hosting platform.

Apologies for the long downtime.

Can you upload the demo somewhere else so I can have a look at it

The json output for a log always shows an empty map name even when the map is set for the log

You have to do it separate at the moment, might add a mirror option later