IPB

Welcome Guest ( Log In | Register )

178 Pages V   1 2 3 > » 

null_pointer
Posted on: Aug 11 2010, 10:42 AM


Web Scheduler Developer


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


not sure why you would need to add either of them to the firewall as they don't make network connections.

Well perhaps the StreamConsumer of it needs to save the output to a network share but that is all.
  Forum: WebScheduler · Post Preview: #78640 · Replies: 3 · Views: 2,635

null_pointer
Posted on: Jun 8 2010, 11:46 AM


Web Scheduler Developer


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


There is also this TS File Source filter available.

http://www.dvbportal.de/projects/hdtvpump/

It was worked well in some of my tests.
  Forum: Software General Discussion · Post Preview: #78311 · Replies: 7 · Views: 4,037

null_pointer
Posted on: May 31 2010, 11:51 AM


Web Scheduler Developer


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


QUOTE
such as those based upon the flexcop chips


cool, what products are these used in?
  Forum: BDA Driver Development · Post Preview: #78240 · Replies: 3 · Views: 3,491

null_pointer
Posted on: May 28 2010, 12:20 PM


Web Scheduler Developer


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


QUOTE
Multi-tuner (up to 6)

wow cool, more tuners than we have stations :-) for those people that need to capture everything, all the time, at the same time :-)

QUOTE
networked (icl wireless) (accessible from anywhere any time)

that would be cool, if it works well you could have a single multi tuner device networked so all network connected devices could use to watch record etc. Well devices and machines that had the correct drivers etc. Would be nice to have an open well defined network protocol to tune/request/deliver data from a device like this.

QUOTE
small (imagine 4 tuner in the space of the Tinytwin)

small is good but not that important in my setup, but 4 tuners in a single USB 2 device might be cool, if the USB 2 buss could keep up that is, perhaps USB 3 would be a good option here, we will wait and see.

QUOTE
efficient (on antenna input for everything?) no antenna at all! (hehe)

have you been sacrificing chickens to the god of attenuation again :-) no antenna, the TV station is built into the device cool lol.

QUOTE
To start with I'd like your views on our first product if you can accommodate a low profile PCIe card in your PC to try

Would like to help you out in this area but still stuck in the last gen of MB hardware, no PCIe for me, my hardware is working well so have not upgraded for a long time, perhaps MB manufacturers should stop making reliable hardware so we upgrade more often :-)

This all looks good, look forward to seeing some of these types of devices on the market in the near future.
  Forum: DNTV · Post Preview: #78216 · Replies: 28 · Views: 17,918

null_pointer
Posted on: May 28 2010, 09:32 AM


Web Scheduler Developer


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


One thing you can try to help identify where the issues is is demux the transport stream recordings of ABC HD & ABC 2 using ProjectX and just play back the extracted video stream, also look at the ProjectX "fix" logs to see how many errors it found.

If the video that ProjectX extracts plays back ok, then look more closly at the plaback software, if the video ectracts has issues then look more closly at the recoding software and activity.
  Forum: DNTV · Post Preview: #78214 · Replies: 5 · Views: 2,156

null_pointer
Posted on: May 28 2010, 09:25 AM


Web Scheduler Developer


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


It might be better if you ask a specific question.

If you are asking if it is software that extracts/demuxes/splits out the data streams form a Transport Stream then the answer is yes. You can get hardware demuxes but at the consumer level all demuxing is done in sodtware.
  Forum: BDA Driver Development · Post Preview: #78213 · Replies: 3 · Views: 3,491

null_pointer
Posted on: May 28 2010, 09:21 AM


Web Scheduler Developer


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


Cool new epic lootz, any hints as to what the new hardware is :-)
  Forum: DNTV · Post Preview: #78212 · Replies: 28 · Views: 17,918

null_pointer
Posted on: May 12 2010, 07:36 PM


Web Scheduler Developer


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


yep, I have done all I can I think to stop the system form going into sleep or hibernate but win 7 give the user the final say.
  Forum: WebScheduler · Post Preview: #78105 · Replies: 5 · Views: 3,453

null_pointer
Posted on: May 11 2010, 07:13 PM


Web Scheduler Developer


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


windows 7 happened :-)
  Forum: WebScheduler · Post Preview: #78095 · Replies: 5 · Views: 3,453

null_pointer
Posted on: May 8 2010, 02:29 PM


Web Scheduler Developer


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


QUOTE
Yes the method was changed due to a mistake on my part that I never got back to fixing. This was brought about due to the removal of the con-current task method from the base build that was used for DNTV version. I have made the nessesary changes to correct the method of the options and added a new option to enable starting the task after the capture has started.

ok so the 'When not capturing' was changed to be a start task once the capture starts to allow "as captured" conversion, if that correct?
  Forum: DNTV · Post Preview: #78062 · Replies: 17 · Views: 5,087

null_pointer
Posted on: May 8 2010, 11:47 AM


Web Scheduler Developer


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


A post capture task should be exactly that, post capture, I am not sure what the close version DNTV might have changed but the original intent was that post capture was run after the capture taking into account any options that were set like the not while capturing and wait for etc.

The options you have selected should do what you want, I can not see anything there would would be forcing the post capture task to be run pre capture. Unless of course you has this particular task set up in the task setup page to run as a pre capture task fro all captures. Apart from that this post task should run when the capture finishes.

As I have said though I do not know what might be different in the closed DNTV version I am only going on my experience with the open source version TV Scheduler Pro.
  Forum: DNTV · Post Preview: #78059 · Replies: 17 · Views: 5,087

null_pointer
Posted on: Apr 21 2010, 10:31 PM


Web Scheduler Developer


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


cool thx for the info, I might do a bit of digging also in this area.
  Forum: WebScheduler · Post Preview: #77941 · Replies: 5 · Views: 3,118

null_pointer
Posted on: Apr 12 2010, 10:34 AM


Web Scheduler Developer


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


Both the consumer and producer should run at high priority, they use the same code to elevate so I am not sure why one would work and the other would not.

The consumer started at normal and once it is running switches to high, this might take a few seconds.

I have just looked at my dvr system and both are elevated on windows xp sp3

Can you confirm this is only a problem on Win 7 64 Bit?
Attached thumbnail(s)
Attached Image
 
  Forum: WebScheduler · Post Preview: #77907 · Replies: 5 · Views: 3,118

null_pointer
Posted on: Mar 24 2010, 09:04 PM


Web Scheduler Developer


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


cool, thanks for testing, I will release this build tomorrow
  Forum: WebScheduler · Post Preview: #77825 · Replies: 12 · Views: 4,680

null_pointer
Posted on: Mar 23 2010, 08:00 PM


Web Scheduler Developer


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


wow, did you get hit hard.

np, I think it is good to go, I tested it a bit and it looks solid, if you can give it a run through that would be cool.
  Forum: WebScheduler · Post Preview: #77818 · Replies: 12 · Views: 4,680

null_pointer
Posted on: Mar 23 2010, 09:20 AM


Web Scheduler Developer


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


Has anyone had the time to test this one?
  Forum: WebScheduler · Post Preview: #77814 · Replies: 12 · Views: 4,680

null_pointer
Posted on: Mar 19 2010, 01:29 PM


Web Scheduler Developer


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


Ok this build fixes a bug with the test build that was retrying the failed captures even when it should have been waiting for the time out.

I also changed the error time out ammounts to

1 minute
2 minutes
3 minutes
4 minutes

with 1 minute being to default.

If you could test this one that would be good.
Attached File(s)
Attached File  TVSchedulerPro_Rev_179_.zip ( 1.46MB ) Number of downloads: 2
 
  Forum: WebScheduler · Post Preview: #77797 · Replies: 12 · Views: 4,680

null_pointer
Posted on: Mar 17 2010, 02:18 PM


Web Scheduler Developer


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


QUOTE
If the system retry interval is too short, say 15 seconds, and there are several receivers in the PC that take a long time to fail the tune / capture operation the interval can be exceeded (ie failed task is delayed 15 seconds and the multiple tuners take longer than 15 seconds to fail out) with the result that the same problem happens - ie, other tasks don't start.


hmm, good point, not sure how to "fix" this issue though, I set the default to 60 seconds so that should be enough time to fail and try the other schedules first, you would have to have a lot of tunes in your system to hit the 60 second mark but it is a possibility.

EDIT:
the dealy gets added after the schedule failed so the next cycle through in 5 seconds or so it should still be in the delay state. From what I can see what you have suggested should not be possible, well unless you have 2 unstable schedules and then they would just cycle back and forth between them with each one failing, taking to long to return and the error delay would be up on the other one so that one would then have a go at starting. This would stop a 3rd schedule from starting if it needed to. Perhaps a good idea would be to default to 120 seconds for a failed start and make the selectable times:

60
120
180
240

default it to 120 sec.

You know the next complaint I am going to get is that when a new tuner comes available it is taking to long for the next schedule to start, might need to look into resetting all the delays on schedules when a card is freed up.
  Forum: WebScheduler · Post Preview: #77772 · Replies: 12 · Views: 4,680

null_pointer
Posted on: Mar 17 2010, 11:29 AM


Web Scheduler Developer


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


Here is the test build with the above mentioned changes.

EDIT:
Attachment removed
  Forum: WebScheduler · Post Preview: #77768 · Replies: 12 · Views: 4,680

null_pointer
Posted on: Mar 17 2010, 08:01 AM


Web Scheduler Developer


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


The main problem here is that the schedules are started in the same order with each loop of the timer thread and only one schedule per loop is started. This means if there are 2 schedules that need starting and the first one can not start for some reason it will it will get stuck and continually try to start the first schedule over and over. This effectively locks the scheduling system up until the unstartable schedule passes it stop time or is removed form the system.

One of the things that was done to help in this situation was add a delay to the timer loop to stop the unstartable schedule from retrying over and over with each loop of the timer thread. This had the draw back that if a failed capture occurred the scheduling system would stop for the error time out.

Proposed solution:
After thinking a bit on this I think I have a reasonable good solution, instead of delaying the whole scheduling timer for the error time out just delay the schedule that failed to start for the time out. Sounds simple right? well it is reasonably simple to implement but changes a fundamental way the schedule timer thread works works, this is the heart of the system and a change like this would require testing, not just "it works for me" sort of testing but some failed starts "unplug antenna etc" sort of testing and by multiple people.

So I have made the changes, the new error system will only delay the failed to start schedule, other schedules that are to start should now get a chance to start, the problem is it needs testing, I can build a test build and make it available for people to test.

Testing:
The change involves failed schedules, if a schedule failed to start in the details log of the schedule you should see a line like:

QUOTE
Schedule failed to start, it will be delayed for 60 seconds and then retried.


Also any schedules set to start at the same time should now be able to start. The main problem is that it is impossible to tell what order the schedules are going to be loaded in, they are sorted in order of a random number that is created when they are instantiated, this random number is used to sort them for processing, it is not possible to tell which order the schedules will be in when they are processed by the timer thread. So it may take some testing before a test shows the correct operation of the new failed start delay system.

One way to test it: (need multi tuner system)
Created a bogus channel with a bogus freq etc
Create two schedules starting in 10 min, one with the bogus channel and one with a working channel
Set the system clock to 15 min into the future

The next pass through the timer thread should see One capture start and one fail.
Check the order that started (time stamps in the schedule details page or schedule log files will tell you)
If the failed one was attempted first and failed and then the other one started ok then it is working.

For people that can and want to test I will upload a test build to a location and post the link here in a few hours.
  Forum: WebScheduler · Post Preview: #77767 · Replies: 12 · Views: 4,680

null_pointer
Posted on: Mar 12 2010, 12:49 PM


Web Scheduler Developer


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


The EPG server url is set in the EPG Data settings

System -> EPG Data Source Settings -> Search URL

Also readt the info on the bottom of the page info on how to specify the url and search parameters
  Forum: WebScheduler · Post Preview: #77706 · Replies: 8 · Views: 6,278

null_pointer
Posted on: Mar 12 2010, 12:46 PM


Web Scheduler Developer


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


small problem with the URL, fixed in rev 175

The new version is available form download now.
  Forum: WebScheduler · Post Preview: #77705 · Replies: 6 · Views: 3,164

null_pointer
Posted on: Mar 11 2010, 03:21 PM


Web Scheduler Developer


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


Is probably the same issues as this one:

http://sourceforge.net/apps/phpbb/tvschedu...p?f=4&t=107

Try what is suggested and see if it works for you.
  Forum: WebScheduler · Post Preview: #77695 · Replies: 6 · Views: 3,164

null_pointer
Posted on: Mar 11 2010, 09:30 AM


Web Scheduler Developer


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


From the log:
QUOTE
2010/03/10 11:55:07.313 - Producer Graph Running
2010/03/10 13:00:39.014 - Data not flowing
2010/03/10 13:00:39.015 - System exiting.


This means for some reason 5 min after the capture started the producer detected that no data was flowing and terminated, why there was no data flow is not indicated, the data flowing mechanism checks the raw data that flows through the memory sink filter, this is the raw data that the capture filter produces. For this data to have stopped means the capture driver or device itself has stopped producing data for some reason. This is usually a signal related problem but can also be driver or device related.
  Forum: WebScheduler · Post Preview: #77692 · Replies: 8 · Views: 3,835

null_pointer
Posted on: Mar 11 2010, 07:06 AM


Web Scheduler Developer


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


on the schedules page click the magnifying class then click the "Export" link at the top
  Forum: WebScheduler · Post Preview: #77690 · Replies: 8 · Views: 3,835

178 Pages V   1 2 3 > » 

New Posts  New Replies
No New Posts  No New Replies
Hot topic  Hot Topic (New)
No new  Hot Topic (No New)
Poll  Poll (New)
No new votes  Poll (No New)
Closed  Locked Topic
Moved  Moved Topic
 

RSS Lo-Fi Version Time is now: 21st September 2017 - 10:08 PM