SageTV V6.0.13 Beta is Now Available

[Lucas]

Have any of you noticed that SageTranscoder.exe frequently crashes with 6.0.13?

I get a popup on the SageTV server saying that the transcoder needs to close due to an error. Ofcourse SageTV stays active. It seems to be hapenning when I go in to the Imported Videos section and seems that it stambles on some imported videos for which it cannot generate a thumbnail.

[kevpriest]

Actually, I had the problem with SageTranscoder.exe crashing on the previous betas, and it was supposed to be fixed with this version. I haven't tried it yet.

Did you not have this problem with previous versions of the beta?

[Narflex]

Please send in your whole log for this if you have it to betatest at sagetv.com. You don't happen to have the property:

minimum_tv_file_size

set to something higher than 500000 do you?

Originally Posted by jds23

You really made me want to look into this further. This is about the deepest I have eer really got into the logs...BUT I FOUND EVERY ONE that got deleted..... here is a sample from the log for just one of the removals..

 Sat 10/28 19:17:03.908 MediaFile failing verify testFile=\\mce2-blue\Recorded TV\2006WorldSeriesofPoker-1969483-0.mpg isFile=true len=2471548864 isTV=true isRecording=false
Sat 10/28 19:17:03.909 Removing MediaFile because it failed verification:MediaFile[id=2105718 A[1969483,1925380,"2006 World Series of Poker",12444@1022.21:00,60] host=HPMCE-BLUE encodedBy= format=MPEG2-PS 0:59:59 0 kbps [#0 Video[MPEG2-Video 29.97003 fps 720x480 4:3 interlaced]#1 Audio[MP2 48000 Hz 2 channels  MAIN idx=15 id=c0]] \\mce2-blue\Recorded TV\2006WorldSeriesofPoker-1969483-0.mpg, Seg0[Sun 10/22 21:00:01.897-Sun 10/22 22:00:01.292]]
Sat 10/28 19:17:20.562 SageTV received connection from:Socket[addr=/192.168.100.70,port=1601,localport=42024]
Sat 10/28 19:17:20.592 MsgSend thread spawned for /192.168.100.70:1600
Sat 10/28 19:17:20.593 MsgRecv thread has spawned for /192.168.100.70:1600
Sat 10/28 19:17:26.392 Deleted media segment file \\mce2-blue\Recorded TV\2006WorldSeriesofPoker-1969483-0.mpg dtime=22483 len=2471548864

I play these files somewhat often, and I am 99.999% sure they were not bad files, does that data above say that it deleted them because it thought they were bad? These files sat on that drive for many days (if not weeks) and then this happens, to over 20 files of the exact same show..just in that dir...Do you think this is a bug by chance?? I just really don't have a clue myself. Thanks for the help into this! -John

[agover]

Originally Posted by Patilan

I am not very clear what you mean by "one increment". But my guess would be that you are used to the search accuracy of the DVD compliant streams, where one keyframe comes every 15 frames (half a second). For mpeg4 encodes, the default rate for keyframes is set to like 250 or 300. You could set a lower value for your encoding, probably at the expense of some encoding efficiency.

I hope this helps.

I wasnt really too clear - and im still trying to nail down whats happening.

The best description I can give is to say that if I hit FF1 (the small forward jump key) sage now jumps back to the previous keyframe with the first press of the ff1 key. The second press now results in you actually jumping forward until you reach the correct location.

As an example:
So if you are at location 00:01:05 the closest keyframe is at say 00:01:00.

You hit FF1 the first time and sage now jumps to 00:01:00.

Now you hit ff1 again and it jumps to 00:01:10 (assuming ff1 is set to 10 secs)

This example is exaggerated but kind of shows whats happening on mpeg4 files in this version. Its not perfect but inleast navigation works in this version

[Lucas]

Originally Posted by kevpriest

Actually, I had the problem with SageTranscoder.exe crashing on the previous betas, and it was supposed to be fixed with this version. I haven't tried it yet.

Did you not have this problem with previous versions of the beta?

I did not have this problem with 6.0.11.

[tmiranda]

The photo slideshow is still freezing on my MVPs. I will file another bug report on this tonight.

[zz5]

Are the MPEG-4 conversions Blu-ray and/or HD-DVD compliant? There is a lot of potential for problems. For example, you have to make sure the encoding algorithm doesn't produce a video that has too high decoding complexity because it will stutter.

[stanger89]

Unlikely, the default profiles are not H.264 (unless that changed).

The other complication is that the HD DVD and Blu-ray profiles are not public information AFAIK.

[mayamaniac]

using SageTV Video Conversion, in the Sage.properties file, I see this line:

transcoder/formats/MPEG4\ Deinterlaced\ in\ AVI-High\ Quality=f\=avi;MCompressionDetails\=-vtag xvid -deinterlace;[bf\=vid;f\=mpeg4;br\=2000000;][bf\=aud;]

The video bitrate seems to be 2000kbps, but audio bitrate is not set, do I just change it to [bf\=aud; br\=128000;] to make it 128kbps?

Better yet, can someone explain what all the options mean so that I can make a custom encoding template? Is it documented somewhere?

[trini0]

I placed my order for the upgrade about 30 minutes ago.
But I haven't recieved the receipt or the serial via email.
I just checked the mail logs, and I see a couple attempts from sage sending the email and it bounced.
What options are available to me now?
Thanks

[mayamaniac]

this is a User-To-User support forum, for official support, contact SageTV Support: orders@sagetv.com or support@sagetv.com

[Opus4]

Originally Posted by trini0

I placed my order for the upgrade about 30 minutes ago.
But I haven't recieved the receipt or the serial via email.
I just checked the mail logs, and I see a couple attempts from sage sending the email and it bounced.
What options are available to me now?

Check this FAQ. If it isn't in your spam folder, or someplace similar, then you'll have to contact SageTV. Since you mentioned seeing email from SageTV bouncing, check your email rules to see if you can set an option to allow it through in the future.

- Andy

[trini0]

Thanks. Already sent an email to Sage.
I opened up the spam rules, and will tighten it down again after I hear from Sage (I hope the spammers do not murder me).

[chadman]

Tagging is still broken for wma files. I am not able to see album/artist at all and tagging is correct. Has anyone gotten this to work with the default stv? Chad

[sainswor99]

Originally Posted by chadman

Tagging is still broken for wma files. I am not able to see album/artist at all and tagging is correct. Has anyone gotten this to work with the default stv? Chad

I got their workaround to work; it's still not reading the Artist tag, but the AlbumArtist tag gets used instead. In order to make it work, I had to remove the media directory from the Sage Setup Menu, Refresh my Imported Media, and then reset up the Media directory to re-add all of my wma files.

HTH,
Stu

[chadman]

Originally Posted by sainswor99

I got their workaround to work; it's still not reading the Artist tag, but the AlbumArtist tag gets used instead. In order to make it work, I had to remove the media directory from the Sage Setup Menu, Refresh my Imported Media, and then reset up the Media directory to re-add all of my wma files.

HTH,
Stu

Great! I will give that a shot when I get home. That is the one bug that has me bummed out. I hate to ditch Jrivers because it works well, but I really want one solution that is easy to use! Thanks, Chad

[chadman]

Originally Posted by sainswor99

I got their workaround to work; it's still not reading the Artist tag, but the AlbumArtist tag gets used instead. In order to make it work, I had to remove the media directory from the Sage Setup Menu, Refresh my Imported Media, and then reset up the Media directory to re-add all of my wma files.

HTH,
Stu

Just tried it and the artitst and album tag are still missing(

Chad

[Humanzee]

I mapped a button on my remote to the new toggle aspect ratio command. This would make for a nice quick way to change between the aspect ratio's, however, something is goofy. I notice when switching to 16:9 aspect ratio (the one that clips the letterbox bars from top and bottom and zooms to fill my screen), it doesn't always actually scale to fit the screen. I.e. it looks the same as fill or source. But this only happens some times, if I keep toggling the aspect ratio button eventually it will work. I also noticed that if it is in 16:9 aspect mode and I toggle from and then back to full screen it will then work like it is supposed to. I actually noticed this back in 5.x too so I don't think its a new bug for 6.x. Quite frustrating.
I have a wide screen TV and am using overlay with the nvidia and AC3 decoders.