IPB

Welcome Guest ( Log In | Register )

6 Pages V  < 1 2 3 4 5 > »   
Reply to this topicStart new topic
> Version 5 - proof of concept
null_pointer
post Aug 31 2007, 08:03 PM
Post #41


Web Scheduler Developer


Group: Developers
Posts: 4,495
Joined: 9-July 03
From: Melb
Member No.: 9
Card: None


The idea is that activation codes for version 4 will be valid for version 5 also, if you purchased version 4 you get version 5 when it is released.
Go to the top of the page
 
+Quote Post
Calvi
post Aug 31 2007, 10:22 PM
Post #42


Forum Regular


Group: Members
Posts: 875
Joined: 8-November 04
Member No.: 1,988
Card: DVICO FusionHDTV


QUOTE (null_pointer @ Aug 31 2007, 05:43 PM) *
New test build (5.0.0.1) with fix for the XML details not being saved, available from dev area, link in first post.


Confirmed fixed. Nice work.
4 simultaneous captures all working nicely here.
Go to the top of the page
 
+Quote Post
murrayt
post Sep 1 2007, 05:11 PM
Post #43


Forum Regular


Group: New Members
Posts: 209
Joined: 17-July 06
Member No.: 5,107
Card: None


null_pointer

I've loaded 5.0.0.1 onto two installations and left it running today with about 20 recordings overlapped on 2 tuners plus overlapped within the same mux. Almost all complete and all seems to be working well.

Just a question on the tuner allocation logic. If a tuner has been allocated to record mux1a in the future, and then you request mux1b to be recorded with some temporal overlap with mux1a will tuner 1 be allocated to mux1a, and tuner 2 be allocated to mux1b (precluding the opportunity to record mux2 if desired) or do you check and ensure that tuner 1 is allocated to mux1a, and mux1b and therfore leaving tuner 2 free for futher allocation?
Go to the top of the page
 
+Quote Post
Calvi
post Sep 1 2007, 05:43 PM
Post #44


Forum Regular


Group: Members
Posts: 875
Joined: 8-November 04
Member No.: 1,988
Card: DVICO FusionHDTV


My understanding is that all recordings on the same mux will automatically be assigned to the same tuner.

This is how it has behaved in testing for me also.
Go to the top of the page
 
+Quote Post
null_pointer
post Sep 1 2007, 05:48 PM
Post #45


Web Scheduler Developer


Group: Developers
Posts: 4,495
Joined: 9-July 03
From: Melb
Member No.: 9
Card: None


QUOTE (murrayt)
Almost all complete and all seems to be working well.

What happened with the ones that did not?

QUOTE (murrayt)
Just a question on the tuner allocation logic.

I think I understand what you are asking but I will state it again just so you can make sure I have answered the question are are asking.

mux1a is a program on mux1 (lets say a mux on frequency 10)
mux1b is a another program on mux1 (on frequency 10)
mux2a is a program on mux2 (lets say frequency 20)

The first thing is that a schedule is not assigned to a device, just like the old version devices are allocated in the order they appear in the device list thus the priority you set is observed.

As each schedule starts it check to see if there is already device sharing a mux that the schedule is looking to capture, if there is it uses the existing shared mux and device, if not it tires to start a new shared mux with the next free device.

So back to your example.

-Schedule for mux1b starts, the schedule starts a producer on device 1 and shares mux1 and start mux1a capturing
-Some time later a schedule for mux1b starts, it check for a shared mux of mux1 and it exists so it uses it to start the capture of mux1b
-Later still a schedule for mux2a starts and looks for a shared mux of mux2 but can not find one so starts a new producer on device 2 for mux2 and starts capturing mux2a

So as each schedule starts it looks for an existing shared mux of the stream it needs, if it find one it will use it, if not it will try to create one using the next free device.

QUOTE (Calvi)
My understanding is that all recordings on the same mux will automatically be assigned to the same tuner.

yep, in a nutshell that is how it should work.
Go to the top of the page
 
+Quote Post
murrayt
post Sep 1 2007, 06:29 PM
Post #46


Forum Regular


Group: New Members
Posts: 209
Joined: 17-July 06
Member No.: 5,107
Card: None


null_pointer

OK apolgies they were still to complete at the time of my post. They have now all completed successfully.

Thanks, the question I was asking is clearly dealt with in the logic. So no concerns there. I just hadn't taken the time to test that sequence of events
Go to the top of the page
 
+Quote Post
Guest_dns_*
post Sep 3 2007, 07:40 PM
Post #47





Guests






With version 5.0.0.0 I have gotten the following:
CODE
03/09/07 16:12:04 : Starting producer, device 0:Bluebird, BDA Tuner1
03/09/07 16:12:05 : Producer start failed with code: -103


I did record several programs with 5.0.0.0 without any problems and nothing has changed with my machine from what i can see so i am not sure about it. I have also tested 5.0.0.1 and it has recorded without any problems so it seems like a temporary problem that has sorted itself out.
Go to the top of the page
 
+Quote Post
null_pointer
post Sep 3 2007, 08:27 PM
Post #48


Web Scheduler Developer


Group: Developers
Posts: 4,495
Joined: 9-July 03
From: Melb
Member No.: 9
Card: None


The -103 error is a failed to build capture graph, this is interesting as it shoul dnto happen or happen all the time, one or the other.

Zip and post the logs, one I am interested in is the Producer log for the failed capture, it will be names something like the following in the log dir:

Capture-***-Producer.log

Where *** will be the date time the log file was created.
Go to the top of the page
 
+Quote Post
Guest_dns_*
post Sep 3 2007, 09:33 PM
Post #49





Guests






attatched
Attached File(s)
Attached File  log.zip ( 195.18K ) Number of downloads: 3
 
Go to the top of the page
 
+Quote Post
null_pointer
post Sep 3 2007, 10:33 PM
Post #50


Web Scheduler Developer


Group: Developers
Posts: 4,495
Joined: 9-July 03
From: Melb
Member No.: 9
Card: None


The error message form the log

QUOTE
Could not CoCreateInstance CLSID_TSMemSinkFilter (0x80040154)


This looks like the mem sink filter was not registered, so is this problem still occurring? If it happens it should happen all the time not just some times.
Go to the top of the page
 
+Quote Post
fuss
post Sep 4 2007, 05:07 PM
Post #51


Participant


Group: New Members
Posts: 35
Joined: 21-July 06
Member No.: 5,137
Card: DNTV Live! DVB-T Pro


Hi,

I've Loaded this on my prod machine with no problems.

Installed over the top of 4.3.0.8 I checked the settings but didn't need to alter anything.

details of my testing so far
  • All test recordings using DVRMS. Configured Webscheduler Service to use same account that the htpc logs on as.
  • With 3 tuners I started recording from the EPG on 3 different muxes (sydney Channels ABC, 7, 9). All started fine
  • Then added a recording from the EPG for ABC2 (Same Mux as ABC). Started Fine shared the producer)
  • Then I started going nuts and added a whole bunch of extra 5 minute test recordings on ABC & ABC2.. In Total I had 8 recordings going at once from the ABC Mux, while I was still recording from the 7 and 9 muxes. All Started fine.
  • I checked the XML's were outputing, and Calvi's webscheduler importers bringing them into Meedio. Good.
  • While the programs were still recording, I went and watched a few... (through meedio, and dvrview) All Good.

So from a testing point of view It's passed all my tests.

I'll leave it running in production and see how it goes.

Thanks.
Tony
Go to the top of the page
 
+Quote Post
fuss
post Sep 8 2007, 06:56 AM
Post #52


Participant


Group: New Members
Posts: 35
Joined: 21-July 06
Member No.: 5,137
Card: DNTV Live! DVB-T Pro


Hi,

I just had a crash in WS 5.0.1 last night in StreamProducer. Looks like the producer crashed when it was trying to finish, but fro mthe webscheduler log it looks like the actual consumer finished fine. The Recording looks ok as well. This is the first crash I've had, and I've probably done about 50 recordings since I installed it. At the time I was recording off all 3 cards .

It came up with a windows popup asking if I wanted to report it to microsoft.

The Event log was

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 7/09/2007
Time: 9:40:11 PM
User: N/A
Computer: MEDIACENTRE
Description:
Faulting application StreamProducer.exe, version 0.0.0.0, faulting module TSMemoryShare.ax, version 1.0.0.0, fault address 0x00002093.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 53 74 72 ure Str
0018: 65 61 6d 50 72 6f 64 75 eamProdu
0020: 63 65 72 2e 65 78 65 20 cer.exe
0028: 30 2e 30 2e 30 2e 30 20 0.0.0.0
0030: 69 6e 20 54 53 4d 65 6d in TSMem
0038: 6f 72 79 53 68 61 72 65 oryShare
0040: 2e 61 78 20 31 2e 30 2e .ax 1.0.
0048: 30 2e 30 20 61 74 20 6f 0.0 at o
0050: 66 66 73 65 74 20 30 30 ffset 00
0058: 30 30 32 30 39 33 002093

The Webscheduler Log is

07/09/07 19:30:00 : Using Calculated Usage (50 MB Minute)
07/09/07 19:30:00 : Doing path AutoSelect of type : 1
07/09/07 19:30:00 : Using Path(0) D:\DVR 249475
07/09/07 19:30:00 : Channel data loaded from Item : 7 Digital
07/09/07 19:30:00 : File Name : Better Homes And Gardens (2007-09-07 19-30).dvr-ms
07/09/07 19:30:00 : File Path : D:\DVR
07/09/07 19:30:00 : Frequency : 177500
07/09/07 19:30:00 : Bandwidth : 7
07/09/07 19:30:00 : Prog Pid : 1312
07/09/07 19:30:00 : Video Pid : 513
07/09/07 19:30:00 : Audio Pid : 514
07/09/07 19:30:00 : Cap Type : 1
07/09/07 19:30:00 : Starting producer, device 2:DNTV Live! Pro BDA DVB-T Tuner/Demod
07/09/07 19:30:04 : Producer Started.
07/09/07 19:30:04 : Producer Start Log:

07/09/07 19:30:04 : Starting consumer process
07/09/07 19:30:06 : Capture started.
07/09/07 19:30:06 : Start Log:

07/09/07 19:30:06 : Capture Started
07/09/07 21:40:04 : Action Finished
07/09/07 21:40:06 : Consumer Stopped(0) with exit code:0
07/09/07 21:40:31 : Producer Stopped(0) with exit code:-1073741819
07/09/07 21:40:31 : Signal Strength (67, 68, 73)
07/09/07 21:40:31 : Signal Quality (93, 93, 94)
07/09/07 21:40:31 : Capture : Better Homes And Gardens (2007-09-07 19-30).dvr-ms (6,074 MB)
07/09/07 21:40:31 : Free Space : (241,413 MB)
07/09/07 21:40:31 : Capture Finished

Cheers
Tony
Go to the top of the page
 
+Quote Post
null_pointer
post Sep 8 2007, 09:54 AM
Post #53


Web Scheduler Developer


Group: Developers
Posts: 4,495
Joined: 9-July 03
From: Melb
Member No.: 9
Card: None


QUOTE
Faulting application StreamProducer.exe, version 0.0.0.0, faulting module TSMemoryShare.ax, version 1.0.0.0, fault address 0x00002093.

Looks like it was a crash in the Shared Memory filter when it tried to stop the filter.

In the log dir there should be a TSMemSink-***.log file for the failed producer stop, if you can find it or just zip ALL the logs and post them here that would be a big help.
Go to the top of the page
 
+Quote Post
fuss
post Sep 8 2007, 01:18 PM
Post #54


Participant


Group: New Members
Posts: 35
Joined: 21-July 06
Member No.: 5,137
Card: DNTV Live! DVB-T Pro


Alright here are 4 log files that look like they are from that recording. (the date/Time stamp lines up with it anyway)
Attached File(s)
Attached File  ws_logs.zip ( 57.4K ) Number of downloads: 1
 
Go to the top of the page
 
+Quote Post
null_pointer
post Sep 8 2007, 01:52 PM
Post #55


Web Scheduler Developer


Group: Developers
Posts: 4,495
Joined: 9-July 03
From: Melb
Member No.: 9
Card: None


I have built a new test build, it is available form the dev center download page:

http://www.bluebit.com.au/cms.php?id=4

Version 5.0.0.2

* [added] flag matching for match list items allowing matches to specify (Repeat, Wide Screen, High Definition etc)
* [added] fall behind detection and reporting for shared memory system
* [bugfix] use more status change lock to stop the shared memory from being deleted when writing to it.
* [added] crash dump handler for consumer and producer to log crash dump details to a file
Go to the top of the page
 
+Quote Post
frednerk33
post Sep 8 2007, 09:16 PM
Post #56


Forum Regular


Group: New Members
Posts: 308
Joined: 29-April 06
From: australia
Member No.: 4,667
Card: DNTV TinyTwin USB


Just wondering what spec machine is needed, it seems like a few processes are being created ... eg I have an AMD3000 + IDE 200Gb +1Gb XP box with a TinyUSB2 and an AMD3500 + Sata 250Gb +1Gb XP box with a DVICO HDTV-lite ... just not sure of anticipated performance limitations.

Will these be "fast enough" do you think, to capture simultaneous programs in a channel's TS (or whatever it's called) ?

Cheers
Go to the top of the page
 
+Quote Post
null_pointer
post Sep 8 2007, 09:22 PM
Post #57


Web Scheduler Developer


Group: Developers
Posts: 4,495
Joined: 9-July 03
From: Melb
Member No.: 9
Card: None


Yes there are a few process being created, at least 2 for each capture in this new version, one for producing the memory share and one for consuming and saving the data.

The actual capture takes very little CPU, it sits at about 3% to 5% for a simple capture on my 2.4 GHz Intel machine, I have tested 4 consecutive captures using 2 devices and CPU was 10% to 20%.

It might be good if other people could comment on system specs and what captures use on their machines to give you a better idea.
Go to the top of the page
 
+Quote Post
Guest_dns_*
post Sep 8 2007, 11:21 PM
Post #58





Guests






Some of my problems do seem to be cpu usage related.
Is it possible to increase the thread priority a little?, the captures seem to struggle when i have something else using the computer such as playing games.
The recordings do still continue to work but it appears when i play it back the video seems to have dropped frames. This could also be driver related so i am not sure.
Go to the top of the page
 
+Quote Post
frednerk33
post Sep 8 2007, 11:38 PM
Post #59


Forum Regular


Group: New Members
Posts: 308
Joined: 29-April 06
From: australia
Member No.: 4,667
Card: DNTV TinyTwin USB


Just a thought ... one box has a 333Mhz FSB bus and the other a 400Mhz FSB bus ... I recall in the past analogue captures using a Winfast struggled with data throughput on a motherboard of 333 Mhz FSB or less and even sometimes on the 400 and at that with a PCI connected card ... is bus data throughput/choking a possible issue regardless of CPU usage (also given the TinyUSB2 is USB based) ... ? I'm not sure what data xmission spikes these things generate especially with multiple concurrent disk write "streams" on top of the incoming video stream to be processed too ... does that make sense ?
Go to the top of the page
 
+Quote Post
fuss
post Sep 9 2007, 07:12 AM
Post #60


Participant


Group: New Members
Posts: 35
Joined: 21-July 06
Member No.: 5,137
Card: DNTV Live! DVB-T Pro


testing 5.0.0.2 no crashes so far. Tested flag matching on repeats works for me.. Thanks.

My box is Intel 2.8mhz HT with 3 captures cards, 700gb Hard Disk, 512 RAM and I use it to view recorded shows at the same time using Meedio, DVRview & Zoomplayer.

It seems to handle the load fine.

Tony
Go to the top of the page
 
+Quote Post

6 Pages V  < 1 2 3 4 5 > » 
Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 21st October 2018 - 02:09 AM