![]() ![]() |
| Guest_zyrorl_* |
Jul 17 2005, 12:10 PM
Post
#21
|
|
Guests |
can someone who has this mirror it? i cant get to the address
|
|
|
|
Jul 18 2005, 09:48 AM
Post
#22
|
|
|
DigitalWatch Developer Group: Developers Posts: 2,263 Joined: 30-September 03 From: Melbourne Member No.: 169 Card: DNTV Quad |
Sorry everyone. Aparently my ADSL link at home is down. I've been away for the weekend and didn't get time to see what was wrong before i came to work this morning.
I'll fix it up tonight, but until then you can grab 2.0.0.9 from Edit: Link removed. -------------------- |
|
|
|
Jul 19 2005, 10:29 PM
Post
#23
|
|
|
DigitalWatch Developer Group: Developers Posts: 2,263 Joined: 30-September 03 From: Melbourne Member No.: 169 Card: DNTV Quad |
New Version - DW 2.0.0.11
Changes
-------------------- |
|
|
|
| Guest_DigiWatchSaver_* |
Jul 20 2005, 11:32 AM
Post
#24
|
|
Guests |
QUOTE (nate @ Jul 19 2005, 11:29 PM)
CONGRATULATION!!! Channel scanning works great now. I've attached the resulting file and also the log for you to check about the timeout thing with D44 Now you have the hardest remaining with that memory leak.... Good luck for that |
|
|
|
Jul 20 2005, 11:53 AM
Post
#25
|
|
|
DigitalWatch Developer Group: Developers Posts: 2,263 Joined: 30-September 03 From: Melbourne Member No.: 169 Card: DNTV Quad |
QUOTE (DigiWatchSaver @ Jul 20 2005, 11:32 AM) He he he!!!! There weren't any timeouts in the logs you sent me so it looks like your reception might have improved a bit. CONGRATULATION!!! Channel scanning works great now. I've attached the resulting file and also the log for you to check about the timeout thing with D44 QUOTE Now you have the hardest remaining with that memory leak.... Thanks. I did fix some leakage in the channel scanning code so if you could test this version so see if the memory leak has been lessened much that would be great.Good luck for that It would also be interesting to see how much memory gets cleaned up when you change channels. -------------------- |
|
|
|
| Guest_DigiWatchSaver_* |
Jul 20 2005, 04:35 PM
Post
#26
|
|
Guests |
QUOTE (nate @ Jul 20 2005, 12:53 PM) There weren't any timeouts in the logs you sent me so it looks like your reception might have improved a bit. Hmm nice QUOTE Thanks. I did fix some leakage in the channel scanning code so if you could test this version so see if the memory leak has been lessened much that would be great. Ok I did some tests for you on the memory leak. The best I could do to show you the results of my tests was to record what I did and make three small video files. I've archived them in a rar file (VideoFootage.rar - 1.41MB). I've uploaded it on my web site as it's too big to attach to this post. Please let me know when you've downloaded it so I can remove it.It would also be interesting to see how much memory gets cleaned up when you change channels. First.wmf is channel playing and channel switching with a video decoder that doesn't work Second.wmf is channel playing and channel switching with a video decoder that works Thrid.wmf is channels scanning then channel playing with a video decoder that works Please note that when I switch to certain channels/networks like Nine the menu doesn't disapear automatically eventhough the channel is displayed. You can see that on the videos I hope it will help... If you'd rather have my results otherwise please let me know Cheers |
|
|
|
Jul 20 2005, 05:20 PM
Post
#27
|
|
|
DigitalWatch Developer Group: Developers Posts: 2,263 Joined: 30-September 03 From: Melbourne Member No.: 169 Card: DNTV Quad |
QUOTE (DigiWatchSaver @ Jul 20 2005, 04:35 PM) Ok I did some tests for you on the memory leak. Thanks. It's looks like there's a fair sized leak when scanning. I'll check it out.QUOTE Please note that when I switch to certain channels/networks like Nine the menu doesn't disapear automatically eventhough the channel is displayed. You can see that on the videos I don't know why that's happening. Check the DigitalWatch.log file and see if ExitMenu is getting called.
-------------------- |
|
|
|
| Guest_DigiWatchSaver_* |
Jul 21 2005, 07:43 AM
Post
#28
|
|
Guests |
QUOTE (nate @ Jul 20 2005, 06:20 PM) Thanks. It's looks like there's a fair sized leak when scanning. I'll check it out. NPQUOTE I don't know why that's happening. Check the DigitalWatch.log file and see if ExitMenu is getting called. I did some testing for you this morning and I have 2 files for you. DigitalWatch.test1.log and DigitalWatch.test2.log. Those should be easier for you to read than for me...The first is a quick test with only 2 channels scanned while the other is an extensive test with all sydney channels scanned. What's odd is that sometimes it does work with a channel and some times it doesn't Let me know if you need me to do more tests Cheers |
|
|
|
Jul 21 2005, 10:26 AM
Post
#29
|
|
|
DigitalWatch Developer Group: Developers Posts: 2,263 Joined: 30-September 03 From: Melbourne Member No.: 169 Card: DNTV Quad |
QUOTE (DigiWatchSaver @ Jul 21 2005, 07:43 AM) What's odd is that sometimes it does work with a channel and some times it doesn't Yes. Something weird is going onCODE TVControl::ExecuteGlobalCommand - work Seems a pointer is getting a bit lost somewhere. Not sure why i havn't seen this myself though. I'll check it out anyway.
TVControl::ExecuteGlobalCommand - List(57) TVControl::ExecuteGlobalCommand - etwork -------------------- |
|
|
|
Jul 26 2005, 10:51 AM
Post
#30
|
|
|
DigitalWatch Developer Group: Developers Posts: 2,263 Joined: 30-September 03 From: Melbourne Member No.: 169 Card: DNTV Quad |
New Version - DW 2.0.1.3
-------------------- |
|
|
|
![]() ![]() |
|
Lo-Fi Version | Time is now: 25th May 2013 - 12:02 AM |