Windows 64 bit Installer news

[SHS]

I think the problem this Codec ID : 2000 when should say Codec ID : ac-3
Make a back copy of that file 101 Dalmatians (1996).avi
I used XMedia Recode write a new test
add file file to XMedia Recode
Format change to AVI
Video: change mode to copy
Audio: It should be on convert mode, changes codec to AC-3, changes stereo to 5.1 the first or last one in the drop down list.
Look at bottom be sure to setup a destination place
add to queue then encode

[SHS]

And god sake don't load stuff like to google or any where else that get in some real problem

[jerrym]

Originally Posted by SHS

I think the problem this Codec ID : 2000 when should say Codec ID : ac-3
Make a back copy of that file 101 Dalmatians (1996).avi
I used XMedia Recode write a new test
add file file to XMedia Recode
Format change to AVI
Video: change mode to copy
Audio: It should be on convert mode, changes codec to AC-3, changes stereo to 5.1 the first or last one in the drop down list.
Look at bottom be sure to setup a destination place
add to queue then encode

I did these steps. The 64 bit client continues to abort. The 32 bit client works fine. The codec does still show a 2000 after the export though. I tried recoding to MP3 and 64 bit client still aborts.

[jerrym]

Originally Posted by SHS

And god sake don't load stuff like to google or any where else that get in some real problem

I only uploaded the first minute of the file and it is a movie that I own the DVD for. I figured it was acceptable and would give something to troubleshoot with. I can pull it down though if you think it is a problem.

[SHS]

Originally Posted by jerrym

I only uploaded the first minute of the file and it is a movie that I own the DVD for. I figured it was acceptable and would give something to troubleshoot with. I can pull it down though if you think it is a problem.

I rename the file and zip it and your link is broken anyway

[jerrym]

Originally Posted by jerrym

I did these steps. The 64 bit client continues to abort. The 32 bit client works fine. The codec does still show a 2000 after the export though. I tried recoding to MP3 and 64 bit client still aborts.

I was wondering if maybe it had something to do with the AVI container so I used XMedia Recode to convert to an MP4 container. I set both Video and Audio to copy.

The MP4 version does play in the 64 bit client while the AVI version causes it to abort. Both versions play fine in the 32 bit client.

I have attached the Media Info exports for both versions.

Any thoughts on what might be wrong?

[jusjoken]

Originally Posted by jerrym

I was wondering if maybe it had something to do with the AVI container so I used XMedia Recode to convert to an MP4 container. I set both Video and Audio to copy.

The MP4 version does play in the 64 bit client while the AVI version causes it to abort. Both versions play fine in the 32 bit client.

I have attached the Media Info exports for both versions.

Any thoughts on what might be wrong?

When you state 32 bit version...which one do you mean? The beta version or the current prod release 9.1.x

k

[jerrym]

Originally Posted by jusjoken

When you state 32 bit version...which one do you mean? The beta version or the current prod release 9.1.x

k

The 9.2.0 beta version.

[wnjj]

Originally Posted by jerrym

The 9.2.0 beta version.

Can you create a file called "NATIVE_LOG.ENABLE" in the SageTV directory for both 32 and 64 bit versions and then play the file on each? I would like to see the sagetv_0.txt and native.log from both systems to compare.

I'm wondering if the XVID filters you have installed are causing issues since the significant difference between the 32 and 64 are the external DirectShow filters used. All of the internal SageTV stuff should be equivalent.

[wnjj]

Jerrym,

I went back to your original post and it sounds like your client crashes back to the desktop when this happens too? If so, can you check for any hs_err_pid* files? Those happen if a Java application hard crashes and can help identify native code issues.

[wnjj]

Ghildebr sent me an hs_err_pid file from a crashing AVI client playback. It shows this:

Stack: [0x000000a6b9200000,0x000000a6b9300000],  sp=0x000000a6b92fe2b0,  free space=1016k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [d3d9.dll+0xf1523]
C  [d3d9.dll+0xac164]
C  [d3dx9_43.dll+0x11af5b]
C  [d3dx9_43.dll+0xff7c3]
C  [SageTVDX93D.dll+0x4dd7]
C  0x0000029ad0109f2e

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  sage.DirectX9SageRenderer.createD3DTextureFromMemory0(IILjava/nio/ByteBuffer;)J+0
j  sage.DirectX9SageRenderer.createNativeImage(Lsage/MetaImage;I)Z+1130

That crash is in the native code, specifically inside something in the DirectX9 DLL. I'm not sure what is causing it since that createD3DTextureFromMemory0 function is called many times successfully prior to the crash. I'm scouring the code for a possible 64-bit issue with data types.

[jerrym]

Originally Posted by wnjj

Can you create a file called "NATIVE_LOG.ENABLE" in the SageTV directory for both 32 and 64 bit versions and then play the file on each? I would like to see the sagetv_0.txt and native.log from both systems to compare.

I'm wondering if the XVID filters you have installed are causing issues since the significant difference between the 32 and 64 are the external DirectShow filters used. All of the internal SageTV stuff should be equivalent.

I created the "NATIVE_LOG.ENABLE" in the SageTV directory for each version, but I did not get any native.log file on either version.

I did play the file on both versions. The 64 bit crashed to the desktop and the 32 bit played it fine. The log files are attached.

These log files were from a simple SageTV install on a new windows image. I thought these were cleaner then the ones that come off my main implementation which has Gemstone installed on it.

[jerrym]

Originally Posted by wnjj

Jerrym,

I went back to your original post and it sounds like your client crashes back to the desktop when this happens too? If so, can you check for any hs_err_pid* files? Those happen if a Java application hard crashes and can help identify native code issues.

I am not getting any hs_err_pid files in the x64 version.

[wnjj]

Originally Posted by jerrym

I am not getting any hs_err_pid files in the x64 version.

Are you looking in the directory where SageTV.exe is? Ghildebr had both native.log and hs_err_pid files.

Your client log and his look like they die in exactly the same place.

[jerrym]

Originally Posted by wnjj

Are you looking in the directory where SageTV.exe is? Ghildebr had both native.log and hs_err_pid files.

Your client log and his look like they die in exactly the same place.

I put the "NATIVE_LOG.ENABLE" file in the same directory as SageTV.exe. I just created a 0 byte text file and renamed it. Is that ok, or is there something special in the file?

Unfortunately I did not get either native.log or hs_err_pid files in that directory.

[wnjj]

Originally Posted by jerrym

I put the "NATIVE_LOG.ENABLE" file in the same directory as SageTV.exe. I just created a 0 byte text file and renamed it. Is that ok, or is there something special in the file?

Unfortunately I did not get either native.log or hs_err_pid files in that directory.

That is correct but the results are unexpected, however I’ll just work with what I have for now. Thanks.

[JustFred]

Originally Posted by jerrym

I put the "NATIVE_LOG.ENABLE" file in the same directory as SageTV.exe. I just created a 0 byte text file and renamed it. Is that ok, or is there something special in the file?

Unfortunately I did not get either native.log or hs_err_pid files in that directory.

NATIVE_LOG.ENABLE needs to be present when Sage **starts up**.

[jptheripper]

Just wanted to say a HUGE thank you for this. I have been on the 64bit for a few weeks. My system is more stable (not longer requires service restarts or reboots) and is so much more responsive.

Thank you all

For reference
windows 10 64bit 16gb ramphenom x6 processor
Sage 64bit 9.2.0
happauge dcr cablecard tuner
happauge colossus component tuner with option
usb-uirt tuning
happauge OTA tuner (2250)

~2500 videos
~2000 tv shows

3 windows 64 clients
2 hd100s
1 hd300

[Eternal]

The past couple of days using the 64 bit version with hdhomerun have been buggy.
The hdhomerun software doesn't detect the 64 bit version and doesn't have the bda compatibility option.
Sagetv shows no signal on all channels even tho it tunes them properly.

The only way I was able to get it to display properly again was install the 32bit version to get the bda compatibility option back and then it would work again.

[jusjoken]

Originally Posted by Eternal

The past couple of days using the 64 bit version with hdhomerun have been buggy.
The hdhomerun software doesn't detect the 64 bit version and doesn't have the bda compatibility option.
Sagetv shows no signal on all channels even tho it tunes them properly.

The only way I was able to get it to display properly again was install the 32bit version to get the bda compatibility option back and then it would work again.

This has been discussed but we have not decided on a solution as HDHR software is looking in the wrong registry location so installing the 32 bit solve it

PS: i will try to remember to add this to the notes on the first post.

k