Utility: Web Radio and TV Encoder

[michaeldjcox]

Originally Posted by Lester Jacobs

Hi Michael,

I've attached the encoder log for your perusal. I did a bit more investigating and discovered that if I supply vlc with \\\<server>\<share> instead of \\<server>\<share> then it works successfully (note the extra starting backslash on the sucessful UNC path). Thus it might be as simple as having a configurable option for the encoder to add an extra backslash to the beginning of any UNC recording path.

Thanks for taking the time to investigate this (especially when it's not an issue in your code)

Cheers
Lester

Hi,

Think I have a fix for this now. VLC seems to like it if the \'s are turned into /'s.

The extra '\' did seem to work in the manner in which WFE uses VLC

I'll release a patch later today.

Michael

[michaeldjcox]

Patch for the UNC path issue:

Web Feed Encoder 0.9.6a

Download, unzip, java -jar the jar file as Adminstrator, SageTV, web feed encoder, config tool and anything accessing the webfeedencoder home directory is stopped e.g. command shells, explorer windows etc.

Choose "Repair".

Michael

[michaeldjcox]

Originally Posted by scanner95

Hello Michael,

I wonder: do you still plan to implement multi-tuner WFE so we could watch/record several streams at the same time? And another question: any hopes for faster tuning (which for me is currently around 10s)?

Thanks!
Yuly

Hi,

Yes 0.9.7 will contain multi-tuner. As many as you like.

It will also be a SageTV V7 plugin and provide test tools for online services.

Tuning speedup not sure what I can do here - the delay is mostly SageTV I believe - but I will reinvestigate.

I will release a beta this week or early next week.

Michael

[SteveW]

Originally Posted by michaeldjcox

Patch for the UNC path issue:

Web Feed Encoder 0.9.6a

Download, unzip, java -jar the jar file as Adminstrator, SageTV, web feed encoder, config tool and anything accessing the webfeedencoder home directory is stopped e.g. command shells, explorer windows etc.

Choose "Repair".

Michael

Works a treat now with my IP camera. Many thanks!

[scanner95]

Originally Posted by michaeldjcox

Hi,

Yes 0.9.7 will contain multi-tuner. As many as you like.

It will also be a SageTV V7 plugin and provide test tools for online services.

Tuning speedup not sure what I can do here - the delay is mostly SageTV I believe - but I will reinvestigate.

I will release a beta this week or early next week.

Michael

Great news! Cant wait to test it Will it be SageTV7 only, or v6 is still supported?

Cheers,
Yuly

[michaeldjcox]

Originally Posted by scanner95

Great news! Cant wait to test it Will it be SageTV7 only, or v6 is still supported?

Cheers,
Yuly

V6 will still be supported.

Michael

[michaeldjcox]

Available here for the brave:

Web Feed Encoder 0.9.7

Includes:

• Multi-tuner support
• "Use Sample" File menu option for using demo channels
• Test tools for online services
• SageTV V7 support - including plugin manager support

This is not an pre-release so there may be a few wrinkles.

Michael

[scanner95]

Hello Michael,

Just tried the new version. I've reloaded back the channels after upgrade; inside SageTV I can see the lineup, 3 tuners and EPG looks fine.
However, if from inside configtool I test a channel reception, I get no picture. Here is what is in the log:

28.07.2010 17:13:39: WebFeedEncoder-0 Request recording 1balt C:\Program Files\webfeedencoder\tmp\1balt_test.mpg
28.07.2010 17:13:39: WebFeedEncoder-0 ********** Starting recording 1balt C:\Program Files\webfeedencoder\tmp\1balt_test.mpg
28.07.2010 17:13:39: WebFeedEncoder-0 Command: Vlc "VLC" "%url%" --demux=dump --demuxdump-file="%recording%" -I rc --rc-host=localhost:%streamAsVideoCommandPort% --rc-quiet %vlclogging%
28.07.2010 17:13:39: WebFeedEncoder-0 UNC fix keeping recording file as C:\Program Files\webfeedencoder\tmp\1balt_test.mpg
28.07.2010 17:13:39: WebFeedEncoder-0 Failed to process command Vlc "VLC" "%url%" --demux=dump --demuxdump-file="%recording%" -I rc --rc-host=localhost:%streamAsVideoCommandPort% --rc-quiet %vlclogging%
java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at uk.co.mdjcox.configdb.ConfigDb.getStreamAsVideoPort(ConfigDb.java:629)
at uk.co.mdjcox.webfeedencoder.RecordingThread.replaceTokens(RecordingThread.java:356)
at uk.co.mdjcox.webfeedencoder.RecordingThread.processCommand(RecordingThread.java:519)
at uk.co.mdjcox.webfeedencoder.RecordingThread.startRecording(RecordingThread.java:174)
at uk.co.mdjcox.webfeedencoder.RecordingThread.run(RecordingThread.java:77)
28.07.2010 17:13:39: WebFeedEncoder-0 Recording started
28.07.2010 17:14:35: WebFeedEncoder-0 Request stop recording 1balt C:\Program Files\webfeedencoder\tmp\1balt_test.mpg
28.07.2010 17:14:35: WebFeedEncoder-0 Stop recording 1balt C:\Program Files\webfeedencoder\tmp\1balt_test.mpg
28.07.2010 17:14:35: WebFeedEncoder-0 Command: VlcCommand %streamAsVideoCommandPort% stop clear quit
28.07.2010 17:14:35: WebFeedEncoder-0 UNC fix keeping recording file as C:\Program Files\webfeedencoder\tmp\1balt_test.mpg
28.07.2010 17:14:35: WebFeedEncoder-0 Failed to process command VlcCommand %streamAsVideoCommandPort% stop clear quit
java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at uk.co.mdjcox.configdb.ConfigDb.getStreamAsVideoPort(ConfigDb.java:629)
at uk.co.mdjcox.webfeedencoder.RecordingThread.replaceTokens(RecordingThread.java:356)
at uk.co.mdjcox.webfeedencoder.RecordingThread.processCommand(RecordingThread.java:519)
at uk.co.mdjcox.webfeedencoder.RecordingThread.stopRecording(RecordingThread.java:462)
at uk.co.mdjcox.webfeedencoder.RecordingThread.run(RecordingThread.java:93)
28.07.2010 17:14:35: WebFeedEncoder-0 Done processing stop commands
28.07.2010 17:14:35: WebFeedEncoder-0 ********** Stopped recording 1balt C:\Program Files\webfeedencoder\tmp\1balt_test.mpg

Any ideas?

Thanks,
Yuly

[michaeldjcox]

I've made a mistake

So if you said start of port range was 5000 and you have 3 tuners (in the main config screen)

There should be properties in webfeedencoder/config/encoder.props that say...

port=5000,5001,5002
streamAsVideoCommandPort=5003,5004,5005
saveToMp3CommandPort=5006,5007,5008

Please add those and use the config tool to stop and restart the encoder.

Will fix this properly so these are not needed

Michael

[scanner95]

Thanks!
That seems to have fixed it. Cool!

Best regards,
Yuly

[RetroBox]

I am having a little bit of a problem getting to the Config tool after installing 0.97 for SageTV 7.0.14. I go into Configure Plugin and click on the link but nothing happens. EDIT - I am referring to the link to open the configuration tool. I did dig around the installation directories but can't seem to locate anything that points to the config tool. I don't have much experience working with web encoder, but I'm excited to try it... can anyone lend a n00b a hand?

[chrishallowell]

Originally Posted by RetroBox

I am having a little bit of a problem getting to the Config tool after installing 0.97 for SageTV 7.0.14. I go into Configure Plugin and click on the link but nothing happens. EDIT - I am referring to the link to open the configuration tool. I did dig around the installation directories but can't seem to locate anything that points to the config tool. I don't have much experience working with web encoder, but I'm excited to try it... can anyone lend a n00b a hand?

I'm having the exact same problem. I looked in the log files and it looks like SageTV can't start the encoder because the Connection dies. Attached are the log files...
Thanks!

[robmich]

Hi all, I seem to have WFE working except for one thing:

error 1 starting service

The service will not start. All files look like they are there and where they belong. There are "two tuners" listed and the EPG and channel lineups are there. Any help would be greatly appreiciated.

Rob

[michaeldjcox]

Originally Posted by RetroBox

I am having a little bit of a problem getting to the Config tool after installing 0.97 for SageTV 7.0.14. I go into Configure Plugin and click on the link but nothing happens. EDIT - I am referring to the link to open the configuration tool. I did dig around the installation directories but can't seem to locate anything that points to the config tool. I don't have much experience working with web encoder, but I'm excited to try it... can anyone lend a n00b a hand?

Hi,

Are you clicking on this link on an extender or on a desktop?

Are you doing this on the PC where your SageTV server is installed?

It will only work on a PC the sageTV server is installed on OR you can download the WFE remote config plugin on another PC running sageTV client.

On the server there should be a directory <sageTV directory>/webfeedencoder/logs.

Theres a file in there called encoderplugin.log and one called configtool.log. Those would probably tell me all I need to know.

Michael

[michaeldjcox]

Originally Posted by chrishallowell

I'm having the exact same problem. I looked in the log files and it looks like SageTV can't start the encoder because the Connection dies. Attached are the log files...
Thanks!

Sorry for the troubles. Beta testing is a tricky business.

So it looks like you probably have a headless box on which you installed the WFE SageTV V7 plugin and then you have a remote PC on which you are trying to run the remote config tool.

I think there is a firewall issue here, ports 1099 and 1100 needs to be opened up for incoming access to the server box. There may be some other ports to open in the same sort of range. See post:

http://forums.sagetv.com/forums/showthread.php?p=407912&postcount=476

I good first quick test would be to disable the firewall for a short time.

Hope this helps.

Michael

[michaeldjcox]

Originally Posted by robmich

Hi all, I seem to have WFE working except for one thing:

error 1 starting service

The service will not start. All files look like they are there and where they belong. There are "two tuners" listed and the EPG and channel lineups are there. Any help would be greatly appreiciated.

Rob

Hi,

In the directory:

webfeedencoder/logs

there will be a file wrapper.log

Could you paste me that pls?

Michael

[michaeldjcox]

I've had a little play with tuning speed.

I've tried setting..

videoframe/network_encoding_to_playback_delay=0

in the SageTV client properties and Sage.properties

and also telling lies to SageTV about the current size of the recording file.

Nothing seems to make much difference.

Pretty much it goes like this:

0 seconds for WFE to launch a VLC process from being asking to tune
6 seconds before VLC dumps some content to the recording file
10+ seconds after that SageTV plays content on the media extender

A bit out of ideas really - not sure how I can influence SageTV to playback sooner and less so how I can reduce VLCs time to find a resource on the internet and start transcoding.

Open to any ideas here...

Michael

[RetroBox]

Hi Michael,

Here are my log files. I deleted several "repeating" lines from the ConfigTool.log for it was 26.9 MB! The two lines that kept repeating in the file with a different date/time stamp include:

Aug 6, 2010 3:34:34 PM Timer-0 uk.co.mdjcox.config.model.ConfigModel openConfigDb INFO: The Web Feed Encoder is not running - config cannot be edited
Aug 6, 2010 3:34:39 PM Timer-0 uk.co.mdjcox.config.model.ConfigModel openConfigDb INFO: Failed to connect to web feed encoder at Mediabox:1099

I am trying to launch the config tool from within my SageTV server, not a remote client or other type of headless configuration.

I'm not sure if this information is helpful, but I see 3 "tuners" under sources - Webencoder at localhost:5000; Webencoder_0 at localhost:5000 and Webencoder at localhost:5001. I also made sure that ports 1099; 5000 - 5008 were open in my router just in case (is this even necessary?).

[michaeldjcox]

Originally Posted by RetroBox

Hi Michael,

Here are my log files. I deleted several "repeating" lines from the ConfigTool.log for it was 26.9 MB! The two lines that kept repeating in the file with a different date/time stamp include:



I am trying to launch the config tool from within my SageTV server, not a remote client or other type of headless configuration.

I'm not sure if this information is helpful, but I see 3 "tuners" under sources - Webencoder at localhost:5000; Webencoder_0 at localhost:5000 and Webencoder at localhost:5001. I also made sure that ports 1099; 5000 - 5008 were open in my router just in case (is this even necessary?).

So it looks like the plugin is starting the web feed encoder process - but the web feed encoder is not starting properly. Hence the sagetv plugin component and the config tool cannot make contact.

Can you send the content of another log file in the same directory:

encoder.log

Thanks,

Michael

[RetroBox]

Absolutely.... here it is. Thanks so much for looking into this.

EDIT - I did play around with it a little more and noticed something new this time. It seems that the config tool is getting blocked somehow by Windows 7. I noticed a window called "Interactive Services Detection" telling me that an application has a message for me. I opened the message and it took me to a separate screen outside the desktop and saw the config tool, but it wasn't usable. I tried to turn on the encoder, but it would turn off a couple seconds later. I don't think my permissions are an issue blocking the tool (?)... I did some reading online and there is an option to turn Interactive Services Detection off, but this would mean all messages would be disabled and I may end up not seeing the config tool anyway. Maybe this tidbit along with the encoder.log file will help solve this problem. Thanks!

EDIT 2 - I looked into the "Interactive Services Detection" message and its a Windows compatibility thing. Apparently, we would need the encoder to be "Session 0 Isolation" compatible. There is a good article about this here: http://blogs.msdn.com/b/patricka/arc...ing-at-me.aspx

Is anyone else running this plugin with no issue in Windows 7?