VS2017 64Bit Build

[jusjoken]

This is great news and progress. When you succeed i will need to figure out how to adjust the installer...unless you feel like taking that challenge on as well

Thanks for taking this on,

k

[sdsean]

So excited! Let us know if there's any further research or code we can help with!

[EnterNoEscape]

Very cool. It's exciting to see progress on the one thing I thought would never happen for SageTV.

[wnjj]

Originally Posted by sdsean

So excited! Let us know if there's any further research or code we can help with!

I'm pretty sure the 7 libraries needed to compile PushReader are:

faac
faad
xvidcore
x264
avformat
avcodec
avutil

I've gotten faac and faad to compile. Xvidcore has a VS project with it so it can probably be built directly in VS.

I haven't figured out x264 (third_party/codecs/x264) or the 3 "av" libraries (third_party/ffmpeg).


If you can manage to build any of those 4 into 64-bit .a or .lib files, that is the main block right now. Even building them for 32-bit is just as difficult. As it is now, pushreader.lib (which links all 7) is already built and sitting there in the Pushreader dir so it hasn't ever been built for V9.

[wnjj]

If this ffmpeg stuff becomes too difficult, shouldn't you still be able to run a headless server in 64-bit and then connect a 32-bit client to it? In other words is there enough reason to even get all of the video/audio playback filters working in 64-bit?

For that matter, isn't the Sage demux optional? I have to admit I don't fully understand how all of the filter graphs get built and what you don't really need.

[jusjoken]

Originally Posted by wnjj

If this ffmpeg stuff becomes too difficult, shouldn't you still be able to run a headless server in 64-bit and then connect a 32-bit client to it? In other words is there enough reason to even get all of the video/audio playback filters working in 64-bit?

For that matter, isn't the Sage demux optional? I have to admit I don't fully understand how all of the filter graphs get built and what you don't really need.

In my opinion having playback on the server is not required. The 32 bit client and placeshifter would fill that void. The gap we windows folk need is a 64 bit server so we can have numerous clients connected.

k

[SteveW]

Originally Posted by jusjoken

In my opinion having playback on the server is not required. The 32 bit client and placeshifter would fill that void. The gap we windows folk need is a 64 bit server so we can have numerous clients connected.

k

Very much agree. I often do playback on my server when I'm troubleshooting my HD-PVRs and the satellite receivers beside them.


If I can still fire up a Sage Windows client on the same windows server that has the Sage server running on it, that all works for me...

[KryptoNyte]

Originally Posted by wnjj

If this ffmpeg stuff becomes too difficult, shouldn't you still be able to run a headless server in 64-bit and then connect a 32-bit client to it? In other words is there enough reason to even get all of the video/audio playback filters working in 64-bit?

1) Does it affect Placeshifter if the server can't render the video?
2) When configuring the channel lineup on some tuners, the station preview can be helpful, although not necessarily required.

I like the idea that you could run the client on the server machine if a user needed to.

This is very exciting to see the 64 bit part happening!

[SHS]

Originally Posted by KryptoNyte

1) Does it affect Placeshifter if the server can't render the video?
2) When configuring the channel lineup on some tuners, the station preview can be helpful, although not necessarily required.

I like the idea that you could run the client on the server machine if a user needed to.

This is very exciting to see the 64 bit part happening!

That what I was think plus it may also be need for transcoding

[wnjj]

I agree that it would be nice to get video playback working. I'm just not sure if the Sage demux is required for that.

So to update on my progress, see the attached image.

There are still plenty of missing and untested pieces. For example I haven't gotten the Freetype font library complied without missing dependencies, there's an error in the log file about a "bundle for base name" (i18n) and I had to skip over the pixel shader code since it kept returning an error code. I'll keep at this but it's definitely showing some promise!

EDIT: The "bundle for base name" was a typo in my sage.properties that I had hand-edited the paths in. One down, several to go...
EDIT2: It looks like the pixel shader code is missing some compiler...probably because I hand-copied some 64-bit DX9 dll's to my test system. There must be a couple more needed.
EDIT3: Yep. Just needed to install the DX9 runtimes and that fixed the pixel shader issue. I assume the installer has to define dependencies and include 64-bit now?

[jusjoken]

[deanm]

[trk2]

[EnterNoEscape]

[NetworkGuy]

[wnjj]

I installed 64-bit LAV filters on my test machine and voila, it played an MPEG2 recording (originally from an HDHR source)!

This is without the problem child Sage StrmDeMux.ax filter complied/installed.

So who here can explain how all these decoders, renderers, demuxes, splitters, etc. work? I see all kinds of if/else code for selecting filters mostly based upon media type (naturally) plus registry options to disable at least the Sage stream demux. I've read plenty of generic DirectShow stuff talking about filters/graphs generically so I have some idea but I've never really had a good handle on what pieces (dll's/ax's) do what specifically for SageTV. Are all these custom Sage filters less relevant these days with other options like LAV?

If the StrmDeMux.ax filter isn't strictly needed, all that remains is further testing and getting the installer to deal with 64-bit stuff which I've never dealt with.

What I did to get this running by hand was:

1. Copy the newly-built 64-bit binaries into a new directory.
2. Copied the STVs & JARs folders and existing sage.jar, sage.properties & RemoteClients.properties.defaults from the 32-bit setup.
3. Hand-edited the paths inside sage.properties to point to the new install area.
4. Ran 'regsrv32.exe' from an elevated command prompt on all of the .ax files in the 'common' directory plus STVEVRPrstr.dll in the main directory.
5. Installed the DX9 redistributables to get the 64-bit versions.

So I then tried connecting an HD200 and nothing showed up but when I checked the server, another client window was sitting there open and had me go through the config menus. So it looks like it rendered it locally instead of at the HD200. It may be something I did wrong since it's been 9 years since I configured a server.


There will be other issues as I only tweaked stuff until some things worked. My test video was one OTA MPEG2 file since that's mostly what I deal with. I did play an mp4 from a camera OK but the progress bar never moved so something's up there. I put a ripped DVD into the video directory but it won't show up in Sage either. Not sure why that is. Maybe some missing Sage component is needed to locate those?

[MattHelm]

Originally Posted by wnjj

So who here can explain how all these decoders, renderers, demuxes, splitters, etc. work?

It's magic. Ask Harry!

[wnjj]

Answering some of my own questions just a bit by looking in the code. It seems that "MpegDeMux" is used for MPEG2-TS/PS formats, a standard MS filter is used for AVI and then all other DirectShow playback goes through "StrmDeMux".

If StrmDeMux is disabled through the registry setting "Directshow/EnableSageTVStreamDemux" = 0, no filter is used for non-MPEG2/AVI formats. In that case I assume DShow builds a playback graph automatically from whatever it finds installed on the system?

[jusjoken]

Have you pm'd Narflex to see if he can explain?

BTW: although time is tight i will take on the installer work as i think its important and i SO appreciate you getting us this far. PM me when you want help with that.

k

[wnjj]

Originally Posted by jusjoken

Have you pm'd Narflex to see if he can explain?

BTW: although time is tight i will take on the installer work as i think its important and i SO appreciate you getting us this far. PM me when you want help with that.

k

I PM'd him. I was kind of hoping he'd drop by but I'm sure he's a busy guy.

That would be great if you can help with the installer. I know nothing about that but have learned quite a bit about what's needed to run in 64-bit mode, the first of which is the 64-bit DX9 runtimes. I'm not even sure how external dependencies are handled. Does the installer include the 32-bit versions of those binaries today? Just a few DLL's or a whole DX9 install-able package? When I downloaded the DX9 runtimes, I ended up with a .zip file full of .cab files (remember those?). Then the DX9 installer program extracted the DLL's needed (and likely many more not needed ones).