Network encoder delay between tuning and playing

[michaeldjcox]

There seems to be delay between SageTV telling a network encoder to tune and it actually responding to the growing mpeg file it has specified to record to.

This seems to correspond in the GUI to the tuning popup windows "circle of death" stopping circling for 5 seconds.

Is there some kind of configurable delay in action here that can be tweaked?

[phelme]

Originally Posted by michaeldjcox

There seems to be delay between SageTV telling a network encoder to tune and it actually responding to the growing mpeg file it has specified to record to.

This seems to correspond in the GUI to the tuning popup windows "circle of death" stopping circling for 5 seconds.

Is there some kind of configurable delay in action here that can be tweaked?

Do you mean it takes a while for the playback of that recording to start or just instigating the recording itself? If you ever watched the logs on both machines as the net encoder process starts, you'll see that there isn't a lot of time wasted.

[michaeldjcox]

As its a network encoder of my writing I have a log file that details when the start rec command from SageTV arrives and also prints out the file size of the recording mpg file SageTV will play.

The start request comes in from SageTV.

But then the file grows to 60-100Mb and around 5-10 seconds delay occurs before SageTV actually seems to play the file.

But it seems to be more of a delay than file size dependent.

I'd really like to be able to reduce this delay period

[michaeldjcox]

Does anybody have any idea on this?

Just creating a recording file for sage to play is not enough.

It seems to want to wait before playing.

Some built in delay seems to be occuring that I feel is probably adjustable by a property in Sage.properties.

Thanks

[AndersNolberger]

Do you respond to the "GET_FILE_SIZE" command in the network encoder? If you do, how do you get the file size? If you ask the file system then you will get 0 as an answer for several seconds even though the file is bigger. When Sage gets 0 as size it waits a little longer to get an actual size. If you instead answer with the actual bytes written by your program it will be faster. That is the reason that i wrote my own file writer filter for my network encoders.

Other than that I don't recall me doing enything else to speed up the tuning.

[AndersNolberger]

I am looking at my code now and I actually never responds with 0 to GET_FILE_SIZE but instead answers 200 if it should be 0. If I remember correctly that was to speed things up a little.

[michaeldjcox]

Originally Posted by AndersNolberger

Do you respond to the "GET_FILE_SIZE" command in the network encoder? If you do, how do you get the file size? If you ask the file system then you will get 0 as an answer for several seconds even though the file is bigger. When Sage gets 0 as size it waits a little longer to get an actual size. If you instead answer with the actual bytes written by your program it will be faster. That is the reason that i wrote my own file writer filter for my network encoders.

Other than that I don't recall me doing enything else to speed up the tuning.

Thanks for your reply.

I use java's File.length() method to return the length in bytes unless that returns 0 in which case I return 200.

I did try lying about the size and returning a very large number but that didn't seem to make any difference.

Regards

[AndersNolberger]

Try to ly a little more convincing! Answer with a small size and then increase at every question. I don't meen this as a solution but as a test to see if it helps.

[michaeldjcox]

Heh.

Yeah - always been a bad liar.

Will try that out.

Thanks,

Michael