Windows 64 bit Installer news

[wnjj]

Originally Posted by NetworkGuy

Since I no longer have a test system, can I have both the 32 bit and 64 bit installed on the same system?

Yes. Just not running at the same time.

[NetworkGuy]

Originally Posted by wnjj

Yes. Just not running at the same time.

The 64 bit will have it's own copy of wiz.bin, correct?

[wnjj]

Originally Posted by NetworkGuy

The 64 bit will have it's own copy of wiz.bin, correct?

Yeah. It's always in the directory with the .exe.

[thomaszoo]

I installed the 64 bit version about a week ago and had a couple issues at first. It turns out those had nothing to do with the 64 bit version (one had to do with SiliconDust having problems with the Premium channels and the second had to do with an updated Java for OpenDCT). Just bad timing on my part.

While I was testing things out I made .bat to stop the service I was running, copy wiz.bin over to the other .exe file location and start the other service (both services were set to "manual"). While I used these .bat files several times at first, I soon realized that the 64 bit version was very stable. I haven't used the 32 bit version at all once I determined what my actual problems were.

With the 32 bit version I would sometimes have some problems with it when it first came up after a system reboot. I haven't had any problems with the 64 bit version.

[wnjj]

Originally Posted by jerrym

As an FYI - I am also getting a similar abort when trying to play any music files (MP3's). I suspect this is a very rarely used function, it has been a couple of years since I have used it. I didn't grab the log, but can if it would be useful and others are experiencing similar issues.

Confirmed this on my system. Crashes in the native visualization code when I play an mp3. I'll track it down.

[wnjj]

Originally Posted by wnjj

Confirmed this on my system. Crashes in the native visualization code when I play an mp3. I'll track it down.

I've updated my previous post with a patched DShowPlayer.dll to include a fix for music. Find it here: https://forums.sagetv.com/forums/sho...&postcount=456

[wnjj]

Originally Posted by jerrym

Thanks for trying, yes - I am running Windows 10 Pro on a couple of machines and Windows 10 Home on another machine. The Windows 10 Home was a fresh instance (I brought up a VM) that I loaded Sage on.

Is there any diagnostics I can try, or maybe a patched version that does some more logging in that area? I would be happy to help.

I did get around most of the issue by converting my AVIs to MKV containers (coping the video and audio - not re-coding). They play fine as MKVs.

As an FYI - I am also getting a similar abort when trying to play any music files (MP3's). I suspect this is a very rarely used function, it has been a couple of years since I have used it. I didn't grab the log, but can if it would be useful and others are experiencing similar issues.

Hi Jerry,

See my post right above this one for the music fix.

Attached to this post, you’ll find an updated "SageTVFileSrc.ax". I found some 32/64 bit type mismatches in this code that will not play nice in a 64-bit app. This filter is used to read several file types including AVI so this could well be causing the AVI crash issue. The file goes in the SageTV\Common directory. As always, shut down and back up the existing file first. Good luck!

EDIT: Confirmed that this is a good patch to fix AVI playback.

[jerrym]

Originally Posted by wnjj

Hi Jerry,

See my post right above this one for the music fix.

Attached to this post, you’ll find an updated "SageTVFileSrc.ax". I found some 32/64 bit type mismatches in this code that will not play nice in a 64-bit app. This filter is used to read several file types including AVI so this could well be causing the AVI crash issue. The file goes in the SageTV\Common directory. As always, shut down and back up the existing file first. Good luck!

Other users: This is a trial file only for now. Only grab this if you want to help debug the AVI crashing upon playback issue. Thanks.

My hat is off to you! Two for Two!

Both my AVI and music playback aborting problems were solved by these two updates. Works in all of my environments.

Thanks again!

[wnjj]

Originally Posted by jerrym

My hat is off to you! Two for Two!

Both my AVI and music playback aborting problems were solved by these two updates. Works in all of my environments.

Thanks again!

Excellent news and thanks for the quick response. I’ll get both pulled into the main codebase for the next (actual release) build.

[Ghildebr]

Originally Posted by wnjj

Hi Jerry,

See my post right above this one for the music fix.

Attached to this post, you’ll find an updated "SageTVFileSrc.ax". I found some 32/64 bit type mismatches in this code that will not play nice in a 64-bit app. This filter is used to read several file types including AVI so this could well be causing the AVI crash issue. The file goes in the SageTV\Common directory. As always, shut down and back up the existing file first. Good luck!

Other users: This is a trial file only for now. Only grab this if you want to help debug the AVI crashing upon playback issue. Thanks.

I can also confirm that this has fixed my .avi playback issues as well.
Gary

[texasex1998]

I tried the 64bit version today, got it running and it does indeed seem very stable. My only issue is since I run Sage on a monitor-less server I use the web interface to set and manage all my recordings and I could not get that to work on 64bit. Has that portion been updated to work yet? TYIA

[wnjj]

Originally Posted by texasex1998

I tried the 64bit version today, got it running and it does indeed seem very stable. My only issue is since I run Sage on a monitor-less server I use the web interface to set and manage all my recordings and I could not get that to work on 64bit. Has that portion been updated to work yet? TYIA

Isn't that a plugin? There shouldn't be anything 64-bit specific to update but with a new install you'll have to set it up again.

[texasex1998]

Originally Posted by wnjj

Isn't that a plugin? There shouldn't be anything 64-bit specific to update but with a new install you'll have to set it up again.

yes it is, I got that working finally but have one last problem. I had the DirecTV multi tuner plugin working great on the 32 bit version, I haven't been able to get it working on the 64 bit though. It shows up with a strange name in the setup section for my HD PVR 2. and when I click on it to change it doesn't give me any option. Has anyone else used this setup? Thank you

[JustFred]

Originally Posted by texasex1998

I had the DirecTV multi tuner plugin working great on the 32 bit version, I haven't been able to get it working on the 64 bit though. It shows up with a strange name in the setup section for my HD PVR 2. and when I click on it to change it doesn't give me any option. Has anyone else used this setup? Thank you

I've used EXEMultiTunerPlugin without issues on Sage-x64. Although I haven't personally tested DirecTV plugin, I'm pretty sure Sage relies on the same registry entry in order to "connect" to either plugin. Have you manually created this entry?

[texasex1998]

Originally Posted by JustFred

I've used EXEMultiTunerPlugin without issues on Sage-x64. Although I haven't personally tested DirecTV plugin, I'm pretty sure Sage relies on the same registry entry in order to "connect" to either plugin. Have you manually created this entry?

I had created it under the 33 but version, and it still works for that one do I need to recreated it for the 64 bit? I never see the CMD window flash like I do with the 33 bit either so I don’t even think it is sending

[wnjj]

Originally Posted by texasex1998

I had created it under the 33 but version, and it still works for that one do I need to recreated it for the 64 bit? I never see the CMD window flash like I do with the 33 bit either so I don’t even think it is sending

The registry location for 64-bit programs is different. It's the same path but without the Wow6432Node in the path that 32-bit uses.

[texasex1998]

Originally Posted by wnjj

The registry location for 64-bit programs is different. It's the same path but without the Wow6432Node in the path that 32-bit uses.

Thanks I thought it would just use the 32 bit version patch but I will try that when I get home. Much appreciated

[wnjj]

Originally Posted by texasex1998

Thanks I thought it would just use the 32 bit version patch but I will try that when I get home. Much appreciated

It's a Windows thing. The registry path is identical within the code but when running as a 32-bit program on a 64-bit Windows OS, it automatically inserts the Wow6432Node in there to keep them separate in the registry, much like using "Program Files (x86)" instead of just "Program Files".

If you still need help, there's a nice post here (https://forums.sagetv.com/forums/sho...&postcount=183) how to get it going. You shouldn't need the DLL inside his .zip file since it is already installed but the other files and explanation is helpful.

[waylo]

Probably a silly question, but can a x86 server connect to a x64 client, or vice versa?

[wnjj]

Originally Posted by waylo

Probably a silly question, but can a x86 server connect to a x64 client, or vice versa?

Yep.