Celestia 1.7.0 Development Thread

[john71]

https://video.stackexchange.com/questions/20495/h ... t-up-and-use-ffmpeg-in-windows

[onetwothree]

That's was initial attempt, but then we faced some issues with it and due to lack of windows devs and unfriendliness of ffmpeg to newcomers I reverted ffmpeg on windows.

[john71]

I know it is a stupid question, but...why can't you use the 1.6.2.2 video recording code?

It is just PERFECT, it produces compressed and beautiful video.

If it works, why change it?

[cartrite]

One day we will figure this out. Right now I'm just comfortably numb. About a 0.15 bac. But I did get ffmpeg to build on windows but was getting link errors to unavailable symbols. Last night was the end of a brutal week at work. In the next few days I'll give another shot at getting ffmpeg to work on windows.

[john71]

OK, the new version seems to be working (except the video recording, which is still flipped).

Are there any new functions we can try?

[cartrite]

I was able to build ffmpeg into the celestia-qt version by editing qtappmain but there is still a few problems. It does get the images right side up but the windows player can't play them. Mplayer on linux can. Still scatching my head with winmain.cpp to get it to work with celestia-win.

[john71]

That would be very nice!

By the way, can the anti-aliasing be improved?

In it's current state it is a little bit blocky...

[cartrite]

I'm a long ways from that. I just finally got it going. The video plays on windows with vlc player but not windows media player or the movie tv player. I don't have a clue yet as to what code needs to go into winmain.cpp yet.

I'm also seeing some more problems. Although the lossless option works for all window sizes, the h.264 works with 640x480 and lower. Anything higher and the capture never happens. It can also freeze celestia if another capture is attempted. So this will take more time until I figure out what's going on.

[john71]

I hope that the full HD Lagarith and Huffyuv codecs will work, because they have the best quality/size ratio (they are lossless, but compressed formats).

[cartrite]

I can see why they abandoned ffmpeg on windows systems. I'm seeing a lot of problems. But I only see 2 codec options. x264 and what they call lossless (FFVH). It's been a long time but I think 1.5 and 1.6 used to have a lot more.

[john71]

Well, even the flipped video is better, than being restricted to those two.

But please answer this: how can the 1.6.2.2 video capture code work in Windows?

[cartrite]

A lot of code has changed since then. Code that works in 1.6 simply will not work in 1.7.

[john71]

Code that works in 1.6 simply will not work in 1.7.

Ok, so the OLD video recording code is not working with the NEW Celestia graphic code.

But why? What did change so dramatically?

[cartrite]

Here is where they gave up on ffmpeg on windows systems
https://github.com/CelestiaProject/Celestia/commits/master?after=cbdd9de63f1d0d779c003d89bf0fc6c2127d47ff+174&branch=master

Here is where it started.https://github.com/CelestiaProject/Celestia/commits/master?after=cbdd9de63f1d0d779c003d89bf0fc6c2127d47ff+209&branch=master

Here is the actual link to the actual commithttps://github.com/CelestiaProject/Celestia/commit/8dab250f2262b40bff9048969d7da7262207a814

Added after 26 seconds:
That started using ffmpeg

[john71]

By the way is the 1.7 code ready? Is it a pre-release code? Should we start testing it with all our add-ons?

[onetwothree]

What do you mean by readiness? Please define.

[john71]

Ready=it has all the new - mostly bug free - features which make it substantially different from a 1.6.x release.

[Markerz]

Should we start testing it with all our add-ons?

if you want to test add-ons, one good way to test your add-ons at the moment is via mobile versions. they use the master branch code, the same code a 1.7.0 release would be built with. and in my opinion is quite stable.

[john71]

I will try that thanx, but it is nearly impossible to transfer all my add-ons to a mobile phone.

[cartrite]

By the way is the 1.7 code ready? Is it a pre-release code? Should we start testing it with all our add-ons?

This is the whole purpose of development. You should test all your add ons and report any problems so the problems can be fixed . If possible.