danser-go VS GORM

I would recommend using danser to generate replay recordings, don't have to worry your performance while recording and can using higher sample rates for motion blur, as well as many other settings.

If setting up danser is easier than other options, you could render in whatever quality and see the pp number at the end.

Still, if you do want to compare multiple replays, maybe something like danser's knockout could work (although replays get removed when you miss, so I'm not sure how you'd combine replays with misses).

Try danser, there seems to be a Linux release. I have no idea what I'm talking about, I've never used Linux before.

you could also render a replay with a program like danser

I don't know how to solve your problem with osr2mp4, but I recommend using danser and using its motion blur.

danser

if you don't know anything about danser. go here!

GORM is a comprehensive ORM tool in Go, offering a code-first approach which allows defining database schemas using struct tags in Go. It's known for its developer-friendly nature, making it suitable for both beginners and experienced users. GORM supports a variety of SQL databases like MySQL, PostgreSQL, and SQLite. It's designed to be flexible, allowing developers to drop down to raw SQL when necessary. However, it's important to be cautious about its performance implications in large-scale applications.

Homepage: https://gorm.io/

Since most of these APIs will be simple CRUD (Create/Read/Update/Delete) endpoints, let's build this service using GORM, an ORM library that makes building CRUD endpoints really simple.

After successfully configuring the application, it's time to delve into integrating the data layer. For this purpose, I will utilize gorm, a powerful SQL ORM that facilitates rapid development of the data layer using model structs.

For basic INSERT ... VALUES ... or SELECT ... WHERE ... JOIN ..., use a library such as GORM. For INSERT .... SELECT ... statements where one combines two round trips (SELECT and INSERT) into one, ORMs have a hard time performing this query. Particularly when you start doing joins. Joins are the heart of Relational database theory (they denote relationships). So get to know what an INNER, LEFT, RIGHT and OUTER join is and why you would use them. Also learn INSERT ... SELECT ...

I have never hated gorm and it serves me well. However I tend to feed it raw SQL very often.

Array of values with embedded value all pointed to the last value, reflect code was broken: https://github.com/go-gorm/gorm/pull/5901 data corruption