DVBViewer Recorder: Network encoder

[jeroen020]

Originally Posted by StephaneM

Hello,
When you use the DVBViewer Recorder Configuration utility and when you are done with it click on the "Restart Recorders and Exit". This will restart the recorder and as a consequence will load its new settings.

Thanks for your quick reply! I thought I already tried the "restart recorders and exit" option, but to be sure I tried again and unfortunately it did not solve my issue, still the same errors and no apparent connection between the SageTV and DVBViewer.

However I did realize that the naming of my recorder instance could be the problem. The log points to 'NewRecorder' (which is a name for a quick test I entered in DVBViewer Recorder) while I'm actually using the 'DVBViewerRecorder' instance now. It seems that the sage.properties is a bit of a mess, I tried cleaning it but it still doesn't work. I think I'll just reinstall SageTV all together and see if a fresh start gets me going.

Another question before I do so - what's the recommended set-up with regards to the IP address? Would you recommend the local IP address (192.168.0.149 in my case) or localhost (127.0.0.1)? Any thoughts if the standard firewall in Windows Home Server (I haven't installed any specific software, just use the standard config) could be messing with me?

Thanks!

[StephaneM]

Originally Posted by jeroen020

However I did realize that the naming of my recorder instance could be the problem. The log points to 'NewRecorder' (which is a name for a quick test I entered in DVBViewer Recorder) while I'm actually using the 'DVBViewerRecorder' instance now. It seems that the sage.properties is a bit of a mess, I tried cleaning it but it still doesn't work. I think I'll just reinstall SageTV all together and see if a fresh start gets me going.

It shouldn't be an issue. What matters is the IP and port used for connecting to the recorder. The name is purely cosmetic.

The sage.properties file does have the name of the recorder only for displaying it withing SageTV. The importer information in the sage.properties file is the IP / Port and recording format (TS / MPEG)

Another question before I do so - what's the recommended set-up with regards to the IP address? Would you recommend the local IP address (192.168.0.149 in my case) or localhost (127.0.0.1)? Any thoughts if the standard firewall in Windows Home Server (I haven't installed any specific software, just use the standard config) could be messing with me?

Well it's a matter of IP configuration. If your local IP address can change (because of DHCP for instance) and you don't need to use the recorder through the network use 127.0.0.1.

The Windows Firewall will block the recorder. You have to add it to the exceptions (the Recorder Service and the Standalone Recorder)

Though from your previous experiments : SageTV was connecting to the recorder without issue. The only issue you have was that your lineup was empty.

To start from scratch :

* uninstall the recorder, wiping out your settings
* delete the sage.properties file and the wiz.bin (no need to reinstall SageTV, this will be enough to do a clean start)
* Launch SageTV do usual configurations steps except video sources
* Install the recorder : choose the name (tip: give it a name that does describe your source feed, for instance "Satellite"), the IP / Port, and select "Record Transport Stream". Give a channel number to the channels you want to include in your lineup. Click on "Add to SageTV".
* click on "Restart Recorders and Exit" : verify that the Recorder Service was restarted (you can manually restart the service to be on the safe side)
* Restart SageTV and configure the video source.

It's also easier to troubleshoot issues by using the standalone recorder, and when all is working with the standalone, to switch to recorder service.

Regards,
Stéphane.

[jeroen020]

Thanks again for your swift reply! OK, I'm getting closer. I added the rules for the DVBViewerRecorder and service, as well as port TCP/IP 9090 as exceptions to the firewall.

I also deleted all entries in sage.properties that I thought could be related to DVBViewerRecorder, and followed your instructions.

Next, In SageTV, I can scan for all channels and all the ones I gave numbers to were found in the scan. However I still can't tune to any of the channels. It's tuning to the selected channel for about 15 seconds, but then the screen stays black; strangely, in the recording folder, short .ts files with recordings do show up, but they tend to be short files! There seems to be an issue with the folder it writes the recordings to? I've attached the log, but here's some text:

Service - 22:09:38.031 - Verbose - Satellite - START Satellite Digitale TV Tuner|20|2498833156062|E:\SageTVRecordings\21_20_0804_2209-0.ts|Fantastisch
Service - 22:10:10.453 - Warning - Satellite - Recording 'E:\SageTVRecordings\21_20_0804_2209-0.ts' could not start, check that DVBViewer is creating the recording in the right directory, or has enough permissions to do so.
Service - 22:10:10.453 - Verbose - Satellite - current recording = 'E:\SageTVRecordings\21_20_0804_2209-0.ts'
Service - 22:10:10.453 - Verbose - Satellite - 'E:\DVBViewer\21_20_0804_2209-0' is the current recording, stopping...
Service - 22:10:10.875 - Info - Satellite - Recording stopped: E:\SageTVRecordings\21_20_0804_2209-0.ts
Service - 22:10:10.921 - Verbose - Satellite - START = ERROR
Service - 22:10:10.937 - Verbose - Satellite - GET_FILE_SIZE E:\SageTVRecordings\21_20_0804_2209-0.ts
Service - 22:10:10.937 - Verbose - Satellite - GET_FILE_SIZE = 0

After enabling audio/video in DVBViewer, trying out the Standalone Recorder showed that when I change to a channel in SageTV, DVBViewer in fact changes to this channel and plays it in DVBViewer itself.

So somehow the connection between DVBViewerRecorder, DVBViewer and SageTV is there, but it's still missing the crucial part of seeing it....

Another weird thing: there's a strong blue or sometimes magenta tint to both the image in DVBViewer as well as the resulting recorded .ts files. Strangely, the tiny preview window you get when selecting preview from the view menu in DVBViewer shows the colors correct. I tried different decoders and all but I keep getting this weird color. Not my main concern now, but it will probably be my next.

[StephaneM]

Originally Posted by jeroen020

Service - 22:10:10.453 - Warning - Satellite - Recording 'E:\SageTVRecordings\21_20_0804_2209-0.ts' could not start, check that DVBViewer is creating the recording in the right directory, or has enough permissions to do so.

From the recorder perspective, it means that the recorder asked DVBViewer to create a recording (in the E:\SageTVRecordings\ folder), waited a little time (30 sec. at max if I remember correctly), and constated that the expected recorded file was not there.

So the recorder warn you that DVBViewer may not be able to put the recorded file in the specified directory. You should verify that this directory is present in the DVBViewer options (the recorder service should add it automatically) and that permissions are ok for this folder: DVBViewer will run either with your account when using Standalone recorder, or with Local System account when using recorder service.

[jeroen020]

OK your tip for looking into the filesystem was very useful, although I don't think it had to do with the rights - there were some traces from a previous directory I used so it wanted to write E:\SageTVRecordings data into E:\DVBViewer

I've now pointed everything I could find towards E:\DVBViewer and voila, I get a picture in SageTV!!! At least, for a few channels... So far, pay TV and HD channels don't seem to work (yet), or worse still, only BBC SD channels on Astra have been working. But at least that's a start, and I also haven't properly added the EPG data so I'll do that to check if that makes a difference.

I'll keep prodding and let you know more as I (hopefully) progress.

[jeroen020]

Small update: I didn't do anything specific, but now all channels that work in DVBViewer work in SageTV as well, so the Disecq switching and decryption of pay TV channels is OK, which is great. It also works just as well on HD200 extenders as it does on the SageTV server itself.

One slight disappointment is the speed (or lack thereof) when changing channels - it takes 5 to 10 seconds for a new channel to show after pressing channel up or down. Is there a setting in the Recorder, DVBViewer and/or SageTV that would speed this up?

Also I couldn't get the XMLTV working but this is something I can probably fix myself when I look a bit more into the channel numbers/ID's, there's probably a mismatch there.

I'm now thinking of getting a second smart card & DVB-S tuner so I can record and watch simultaneously.

[slimyosra]

Hi,
I have set up the dvbviewer recorder. and it works fine on the server side.
But if I try to zap from a mediaMvp or sageclient I got blank screen.
In the log I noticed a crash but I could not fix it. Any help are welcome.

ven. 9/18 3:19:58.580 [VideoFrame-SAGETV_PROCESS_LOCAL_UI@53a9d5] VIDEO FRAME EXCEPTION THROWN:java.lang.NullPointerException
ven. 9/18 3:19:58.580 [VideoFrame-SAGETV_PROCESS_LOCAL_UI@53a9d5] java.lang.NullPointerException
ven. 9/18 3:19:58.580 [VideoFrame-SAGETV_PROCESS_LOCAL_UI@53a9d5] 	at sage.VideoFrame.run(Unknown Source)
ven. 9/18 3:19:58.581 [VideoFrame-SAGETV_PROCESS_LOCAL_UI@53a9d5] 	at sage.cs$a.run(Unknown source)

[slimyosra]

anybody?

[StephaneM]

Originally Posted by slimyosra

I have set up the dvbdream recorder. and it works fine on the server side.

If you are using the DVBDream encoder you may have more success if you ask in the dedicated thread if any.

Regards,
Stéphane.

[slimyosra]

Sorry I am using dvbviewer

[StephaneM]

Originally Posted by slimyosra

Sorry I am using dvbviewer

Then it depends on how you set your recording format with the DVBViewer Recorder : you can choose to record in TS (transport stream) or not (program stream).

I guess that for the MVP you need to use program stream, I don't think the MVP can support all transport streams.

For the client, if the server can play it, the client (not placeshifter) should play it (Though I don't have any problems personally with placeshifter and TS).

You may also try to use the current beta demuxer (recording natives) on your client / server this may helps.

One other thing to check : schedule a test recording (a few minutes), and try to play it on your client or MVP instead of trying to view Live TV.

Note: when you change the recording format in DVBViewer Recorder, you must readd the source in SageTV (the recording format is stored in the sage.properties file)

Regards,
Stéphane.

[slimyosra]

Originally Posted by StephaneM

Then it depends on how you set your recording format with the DVBViewer Recorder : you can choose to record in TS (transport stream) or not (program stream).

I tried both TS and PS on Hauppauge MVP and sageclient 6.6

For the client, if the server can play it, the client (not placeshifter) should play it (Though I don't have any problems personally with placeshifter and TS).

the server plays PS and ts, strange enough it works perfectly on placeshifter

You may also try to use the current beta demuxer (recording natives) on your client / server this may helps.

Sorry what is beta demuxer.

One other thing to check : schedule a test recording (a few minutes), and try to play it on your client or MVP instead of trying to view Live TV.

black screen on sageclient, sage placeshifter works fine instead.

Thanks
Slim

[StephaneM]

Originally Posted by slimyosra

Sorry what is beta demuxer.

This is the new native directshow playback demuxer you'll find here.

Otherwise, I guess you can't do anything more. DVBViewer record (more or less) the streams as they are broadcasted. Broadcasters do have some oddities in their streams...

Also if you choose TS as the format for your recording, in DVBViewer Settings for the Output format, choose also TS and select all the streams you need (Teletext, DVB Subtitles, All Audio tracks) and make sure you select "Adjust PAT/PMT"

You can also contact SageTV support to see if they are able to play your recordings. However if the recordings play fine on the SageTV server, there is something wrong with your client.

Regards,
Stéphane.

[B00ne]

Hi Staphane,

I want to share my thoughts on the experience with DVB viewer recorder.

Its a great piece of software, so first the good:
- it works marvellously most of the time
- produces much less hard drive activity then using sage alone (believe this is due to that fact that sage can only record program streams, so it has to convert the transport stream from the TV card to PS)
- uses much less CPU recources that sage alone (2-7% using DVBviewer recorder with sage vs. 30-50% using sage as tuner (live TV or recording)
- i can tune channels broadcasting in DVB-S2 (main reason for trying it), which for some unknown reason is not possible in sage

now the bad:
- it doesnt work on all channels (sage problem) - some channels i get sound, but the video freezes after a second or two
- wont grab EPG data by itself (although I set it to grab every day of the week)
- even manully (changing the grab time to something close to now) it is a matter of luck if it will grab or not
- epg data is not complete vs. EPG in DVB viewer

unfortunately those minor bad point are the reason why i wont be using it. and besides needing to use DVBviewer recorder seems like this:

I bought a shiny new car with all the bells a whistles and great luxury (sage) but the engine will only work in broad daylight. Now there is this other car with crappy interiror and no luxury but it has a magnificent engine (DVB viewer). I have to buy this car too, to use its angine in my great one. But because this wont work easily, I need a new device to make the interface (DVB viewer recorder). Now my luxury car can drive anytime anywhere, but you have to feed the gas manully to make it work (XML epg). Now in the end I do have the gratest car but you need to be a mechanic to drive it - so it lost its merits :-).

Can you make dvbviewer recorder to just covert the EPG data to xml, that DVB viewer writes to a file anyway (EPG.dat or so)?

If I would be using the DVBviewer recorder just for some channels and sage for the remainder, is there a solution to recording conflicts?
Right now sage doesnt realize there is a recording conflict because for sage there are two sources but in reality there is just one tv card in the system...

Regards,

[StephaneM]

Hello,

Originally Posted by B00ne

Can you make dvbviewer recorder to just covert the EPG data to xml, that DVB viewer writes to a file anyway (EPG.dat or so)?

Well, this is really what the recorder is doing:

* at scheduled time it tunes to a channel in DVBViewer. Letting time for DVBViewer to grab EPG data on this channel.
* when schedule is over, it writes the EPG data DVBViewer collected into a XMLTV file.

So the EPG grab feature is only useful for EPG data provided by a bouquet, where the data cover more than now and next. Usually the EPG you get in DVBViewer is only now & next : there is no efficient way to transfer this in SageTV with XMLTV (I think that another DVB plugin, DVBDream or ProgDVB, is doing this the other way around => it installs a java plugin in SageTV that is waiting for EPG data from the DVB plugin).

Honestly the best way to get data is to use XMLTV...

If I would be using the DVBviewer recorder just for some channels and sage for the remainder, is there a solution to recording conflicts?

No, SageTV will see two tuners, so it will use them both if needed.

Regards,

[guddis]

Hi,
Hope someone can help me on this.
I have a setup with a WHS as a Sage server with two FireDtv-S2 tuners connected to it and 3 HD-200 extenders. I'm using latest version of Sage sw both on server and extenders.
I installed the latest version of the DvBViewer and the DvBviewer Recorder according to the install docs, but still I'm not able to get anything on the extenders. Screen is black. It doesn't show the no signal logo, it's just black. However I must be doing someting right because the recorder does record the programs I tune in to from the extenders. When I playback these recordings they show up just fine. It's watching live streams that seems to be the problem. So I'm thinking maybe there are some settings on the DvBViewer I've overlooked or some codecs that need to be installed. Maybe I got it wrong, but i though the transport stream is decoded by the extenders ? Are there different kinds of transport streams ?

[StephaneM]

Originally Posted by guddis

the recorder does record the programs I tune in to from the extenders. When I playback these recordings they show up just fine. It's watching live streams that seems to be the problem.

You should check that in DVBViewer Settings / Options / Recorder, you selected the "Adjust PAT/PMT" option.

If things are not better, try to wait a very very long time. Sometimes SageTV doesn't like very well the DVBViewer inprogress recordings, it can takes up to 1 to 2 mins before it starts playing (this however doesn't happen on completed recordings)

Regards,
Stéphane.

[gianpieroizzo]

For anyone interested,

I installed SageTV 6.6.2, DVBViewer 4.2.1 on a fresh WIndows7 machine.
I installed latest Native recording patch (7)
I took care NOT to install any additional codec/splitter.

DVBViewer uses just only Microsoft DTV/DVD codec for audio and video, default render.
Sage uses Microsoft DTV/DVD codec for H.264 and Sage internal ones for audio and MPEG2 video, EVR render

With this configuration I can have a minimal CPU usage: both sage and dvbviewer at 20%, with total CPU always lower than 50% on an Athlon64 x2 5000 + AMD780G (ATI HD3200) chipset.

The image is smooth, but unfortunately not perfectly clean: I observe some spurious frames sometimes, and sometimes it just hangs :-(
However good improvement, hope that it'll go better, I sent Qian some logs to check the pach behaviour.

ciao
Gian Piero

[guddis]

still not working properly. I got a picture from live TV (or maybe a recording?) on a few occations, but mostly I get nothing. Here is the output on the monitor. Seems that it cant get to the folder I specified. However I don't see why the recorder shouldn't have permission to that folder ..

Service - 19:37:50.171 - Verbose - DvbViewer01 - START DvbViewer01 Digital TV Tuner|101|2508318940194|D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts|Great
Service - 19:38:22.484 - Warning - DvbViewer01 - Recording 'D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts' could not start, check that DVBViewer is creating the recording in the right directory, or has enough permissions to do so.
Service - 19:38:22.515 - Verbose - DvbViewer01 - current recording = 'D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts'
Service - 19:38:22.515 - Verbose - DvbViewer01 - 'D:\shares\Videos\SageTV\Eggheads-160695-0' is not the current recording, ignoring...
Service - 19:38:22.531 - Verbose - DvbViewer01 - '' is the current recording, stopping...
Service - 19:38:23.531 - Info - DvbViewer01 - Recording stopped: D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:23.546 - Verbose - DvbViewer01 - START = ERROR
Service - 19:38:23.562 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:23.578 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:23.625 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:23.640 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:23.671 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:23.687 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:23.703 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:23.703 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:23.718 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:23.750 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:23.765 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:23.781 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:23.812 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:23.828 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:23.843 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:23.859 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:23.875 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:23.890 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:23.937 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:23.953 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:23.984 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:24.015 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:24.031 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:24.046 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:24.062 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:24.078 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:24.093 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:24.109 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:24.125 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:24.140 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:24.156 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:24.171 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:24.187 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:24.203 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:24.218 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:24.234 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:24.250 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:24.265 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:24.296 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:24.312 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:24.328 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:24.343 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:24.359 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:24.375 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:38.562 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:38.593 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:38:53.562 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:38:53.593 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:39:08.578 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:39:08.609 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:39:08.640 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:39:08.671 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:39:08.703 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:39:08.734 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:39:08.750 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts
Service - 19:39:08.765 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:39:08.781 - Verbose - DvbViewer01 - STOP
Service - 19:39:08.796 - Warning - DvbViewer01 - Not currently recording, nothing to stop
Service - 19:39:08.812 - Verbose - DvbViewer01 - STOP = ERROR
Service - 19:39:08.828 - Verbose - DvbViewer01 - START DvbViewer01 Digital TV Tuner|101|2508319097142|D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-1.ts|Great
Service - 19:39:40.843 - Warning - DvbViewer01 - Recording 'D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-1.ts' could not start, check that DVBViewer is creating the recording in the right directory, or has enough permissions to do so.
Service - 19:39:40.890 - Verbose - DvbViewer01 - current recording = 'D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-1.ts'
Service - 19:39:40.921 - Verbose - DvbViewer01 - 'D:\shares\Videos\SageTV\Eggheads-160695-0' is not the current recording, ignoring...
Service - 19:39:40.953 - Verbose - DvbViewer01 - '' is the current recording, stopping...
Service - 19:39:41.859 - Info - DvbViewer01 - Recording stopped: D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-1.ts
Service - 19:39:41.906 - Verbose - DvbViewer01 - START = ERROR
Service - 19:39:41.937 - Verbose - DvbViewer01 - GET_FILE_SIZE D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-1.ts
Service - 19:39:41.984 - Verbose - DvbViewer01 - GET_FILE_SIZE = 0
Service - 19:39:42.015 - Verbose - DvbViewer01 - STOP
Service - 19:39:42.031 - Warning - DvbViewer01 - Not currently recording, nothing to stop
Service - 19:39:42.078 - Verbose - DvbViewer01 - STOP = ERROR

[StephaneM]

Originally Posted by guddis

Service - 19:37:50.171 - Verbose - DvbViewer01 - START DvbViewer01 Digital TV Tuner|101|2508318940194|D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts|Great
Service - 19:38:22.484 - Warning - DvbViewer01 - Recording 'D:\SHARES\VIDEOS\SAGETV\RegionalNewsandWeather-161082-0.ts' could not start, check that DVBViewer is creating the recording in the right directory, or has enough permissions to do so.

This "could not start" error, means that the recorder has wait 30s but DVBViewer has not produced the recording file (not even a 0 Kb file, nothing, nada..)

So that means, it has produced the file elsewhere or has failed completely to start the recording.

For troubleshooting this you need to use the standalone recorder (instead of the recorder service), it will allow DVBViewer to run on the desktop and for you to see what is happening in DVBViewer.

What is worrying me is the "D:\shares\Videos\SageTV\Eggheads-160695-0" DVBViewer timer (recording) that is still going on... Was it a previous recording attempt? If this is the case, then maybe the recorder was unable to stop it. To see if this is the case : use the standalone recorder. restart everything to make sure that no timers exists in DVBViewer and start a recording from SageTV, let it go for a few minutes, then stop it. Does the Recorder live trace shows it has stopped the recording correctly?

Regards,
Stéphane.