Celestia 1.7.0 Development Thread

[cartrite]

I found the video bug. I was reading about avi file formats and found what the problem was. biHeight needs to be set to negative. This only works for Full frames uncompressed. With yuv compression, biHeight needs to be positive. So there needs to be an if statement that controls this. Here is some Pseudo code

Code: Select all

 If compression = full frames Then bi.biHeight = (height - height * 2); Else bi.biHeight = height

I changed line 107 in avicapture.cpp to bi.biHeight = (height - height * 2); The movie captures correctly with Full Frame uncompressed. But the other compressors don't work. So there needs to be a way of having one or the other in the avi header depending on compression. But according to what I read, the compressed files should have worked because biHeight was already positive. So something else is probably wrong.

[cartrite]

I cant find any code referring to the compression window that appears in the movie capture process. No code for any of the compressor formats. Is raw uncompressed the only option or are all the options supplied by the windows os?

[john71]

Is raw uncompressed the only option or are all the options supplied by the windows os?

No, there should be Microsoft video 1, Intel IYUV, RLE codecs too. And you can optionally install x264, xvid and huffyuv codecs.

[cartrite]

Right. I understand that. That is what I see in the last window. But I can't find any mention in the code.

[Janus]

A note on doing video recordings, speaking from experience.
When I do recordings with Celestia, I use the following codec into avi.

Lagarith

https://lags.leetcode.net/codec.html

It is lossless, and uses multiple cores.
It is also open source and you can compile it yourself if you desire.
Works as x86 or x64 as well.

Being fair here, I use a non standard setup on my systems, so your results may vary.
I also cannot tell you how it will do under the last two versions of windows, neither of those are allowed on my network.
Works well on the twelve year old system I use making recordings.


Janus.

P.S. Did anyone ever put a patch in place to sync video recording framerate to real time?
Since lua and the rest use different clocks, I had to put a time check into the render loop to keep sync.
I had either posted or sent it, I don't recall off hand.
I am sure someone more versed than I am in C/C++ could make a better version from it.

[john71]

You can use this codec pack, it installs all the necessary components in one step, Lagarith too (Windows):

http://www.codecguide.com/download_k-lite_codec_pack_mega.htm

[Markerz]

I made two major changes to the win32 front end.

One to enable visual styles so that controls look more modern and not like they were from win95, the other to enable proper hidpi support so rendered result and controls will look sharp instead of blurry on a HiDPI monitor.

Might be a good time to rebuild an installer.

[cartrite]

How many people use the other video compressors. With the windows versions the default is uncompressed full frame. I got that working but the fix isn't in the master. The change I posted at the top of this page hasn't been added, reviewed, or anything. I'll build another installer after I hear some feedback from that. Or I can build an installer with a broken movie capture with unaltered code. Up to you all.

[john71]

How many people use the other video compressors.

You need a compressor to record a full HD video with usable frame rates.

[cartrite]

All the compressors will be broken. They don't work with the fix. They don't work without it either. They record everything upside down.

I don't know where the compressor code is. I couldn't find it. If I could find it, maybe I could figure out how to make it compatible with the fix.

[john71]

If I could find it, maybe I could figure out how to make it compatible with the fix.

Video recording wasn't properly working in the 2021.07.21 version.

It allowed to use only the mkv codec.

So it must be in the code.

[cartrite]

I'm gonna look at the code in 1.6.2 and see if I can figure out how it used to work. If I can't figure anything out I'll build a new installer tonight from the latest git pull. Untouched. 64 and 32. So movie capture will not work correctly.

[cartrite]

I uploaded the new 64and 32 bit installers. Movie Capture will still have problems. The texture/hires folder will still be empty. Enjoy.

viewtopic.php?p=156142#p156142

Added after 1 hour 5 minutes:
Warning: I just discovered an issue with the Installers. For some reason, even though the x64 installer is supposed to have C:\Program Files as the default and the x86 installer has C:\Program Files (x86) as the default, this only works for a new installation.

OK. Explanation. Example. I installed the x86 version. Then I tried to install the x64 version. The x86 version was installed in C:\Program Files (x86). The x64 version was also trying to install in the C:\Program Files (x86). If I install the x64 version first, then the x86 version gets installed in C:\Program Files. So they overwrite each other. I'm gonna try and figure this out but it will probably take some time. Be sure to backup your original installation before installing.

Added after 25 minutes 54 seconds:
Forget the above warning. I forgot to generate a new GUID for the 32 bit installer. I just uploaded the 32 bit installer with a new GUID. The 64 bit was unaffected. They should both get installed in their default folders unless you want them somewhere else.

[john71]

Same old problems in the 64 bit version. Codecs are working while recording video, but everything is upside down. There are rectangles in the data numbers.

[onetwothree]

I have found the root cause for rectangles and I'm thinking how to fix it properly.

[john71]

Very nice!

Added after 1 hour 39 minutes:
One more thing: in the case of ISS there are NO rectangles, when I'm CLOSER than 1000 km.

[onetwothree]

Yes and that's expected. Celestia internally uses UTF-8, while windows unless you use Win10 released in 2019 or later or Win11 uses 8bit encodings such as cp1251, cp1252 etc. For this particular issue this was not a problem until the recent time (I think MSVC was updated in github actions) because as a thousands separator ASCII symbol was used (comma or period depending on your locale) which had the same code both in UTF-8 and CP125X. Now in some locales the symbol with code > 127 is used which is invalid value for UTF-8.

Added after 41 minutes 28 seconds:
https://github.com/CelestiaProject/Celestia/actions/runs/1714675275 - this build should fix squares. please confirm.

[cartrite]

I can't confirm this works because I never could reproduce the problem. But, john71, be sure to back up the originals. You should be able to copy these files into an installation I uploaded. All the other files should be the same.

fix-square-numbers.zip

(2.06 MiB) Downloaded 663 times

Added after 35 minutes 12 seconds:
I'm sorry john71, I found out that the qt version needed an extra dll. So I tried to upload a new file that included the dll. But uploaded the wrong one. Give me a few minutes. I need to boot into windows to upload the file. I noticed that the file was downloaded once. This is the right file. It contains 2 dll's and 2 exe's.

Added after 15 minutes 26 seconds:
The right file has now been uploaded.

[john71]

It WORKS.

The "rectangles" bug has disappeared!



Even the old exe file is working perfectly.

Only the "mirror video recording" bug remains.

Added after 59 minutes 36 seconds:

Found a few tips:

It’s very easy to reverse a video using FFmpeg because FFmpeg has a built-in reverse filter that can do this job for both audio and video.

https://ottverse.com/reverse-a-video-using-ffmpeg/

[cartrite]

It WORKS.

The "rectangles" bug has disappeared!



Even the old exe file is working perfectly.

I'm not sure what you mean by that. But probably celestia.dll is what is getting the old exe to work. Glad this worked.