progdvb.com

nope

try disable "save last channel" in settings->Options->Other

did the job yesterday partially

1st recording ok, second no way

lets see whats happening today...

;-((((

Two "crashed" tasks of ProgDVB today - no recording.

"crashed" means the popup, that a crash prior has happened.... normal start,....

I like this function, so I dont marked "disable this feature" ...

...same problem here. I'm waiting badly for the "without-ui-scheduler-version"-which can wakeup the computer.

Thanks,
Olnima

seemed to be solved here....
Two days aotomatic recording successfull.

Switching back to last channel = OFF seemed to be the right tip.
May also be possible, that something in the newest version corrects the bug...

Anyway: Thanks!

arghhh....

to early I declared the "solved"!

Two days ok, third day again two pending tasks ("the program has crashed...") and no recording.

Boring.... ;-(((

Just some thoughts...
As this seem to happen only on a real timer recording, but not on a short simulation, you should think about possible energy saving issues on your machine, perhaps also related with ProgDVB internal timings.
Do you allow the hard disk to fall asleep? Or the tuner? Do you use a screen saver? ...

Some hardware may need to long to wake up from some savings mode.
Or perhaps it won't wake up properly, like known from several early DVB tuners.

To find out more, maybe it could be helpful to test with a manually edited timer event, allowing a minute or two between starting ProgDVB and starting the recording.

"you should think about possible energy saving issues on your machine, perhaps also related with ProgDVB internal timings."

24/7up-server
ok, Windows-index only 5.9 - because of the HDs

"Do you allow the hard disk to fall asleep? Or the tuner? Do you use a screen saver? ..."

No, no, and again no

Yesterday I got one recording (the first scheduled) completely ok.
Second recording again pops up with "ProgDVB has crashed before... what shall I do" ... and: waiting...
In this case ProgDVB doesnt came in conflict to start a recording, because program didnt come up complete!

I dont really believe that this is a timer or energy saving issue.
Sometimes ProgDVD did his job, sometimes it reports a "prior crash" and waits for answer at the terminal. Waiting = no recording

How to disable the "crash-protection" ?!
It protects (prohibits) in tghis case too much
Even I like this feature, again!

Shall I switch of those function? How to reactivate if done to get it back??

again.... first recording ok, second the boring "crash - reset - wellknow - normal"-choice.
I switched that off now, lets see tomorow

Three days later...:
Next two days.... no recording at all. I have switched off the crash-prompt as promised, as a result I´ll get two white (!) screens of ProgDVB.
How to get back the witched off "crash-screen" when once disabled?

BTW: the newest version installs, but prompts back as "03" instead the awaited 4 ?

boring....

Installed meanwhile version 04 (which prompts to be a 03). The newest one (Italian support) I havent installed.
Cleared MS-Scheduler again totally.
Arranged the recordings in ProgDVB again. Yep, after that I did a complete restart of the pc to give a chance to read modified regsitry!

Yesterday: first recording: none, second: didnt end!
When I came to the pc this morning I found a black ProgDVB-screen with blinking recording... since yesterday 1500 !
I stopped the programm, and there was the right done question if I want really stop ProgDVB and the current recording.
Saying "YES" ... found the second recording (even with picture and sound) at my hardrive.
Thanks god the programm stopped writing to harddrive at endposition (1600)
But see: programm still this morning is still running with a black screen blinking "recording".

Anyway: in the right taskbar the ProgDVB-symbold after quitting resides till i touch it with the mouse.

Nothing what gives me the impression to be "stable"

And I dont really like banana-products: becoming good at the user.
Nothing against to help if there are problems...
But they should be solved in moderately time.

And again the question: how to switch on again the "crashed before"-question if once disabled?
Where to find some infos about PIP?

just meanwhile installed .06-version
ok, ONE recoring (the first) -but:

Didnt stop!

So yesterday I got a file named with the awaited name, but still this morning ProgDVB was active recording....
90 GB since yesterday, best quality and ALL IN ONE ;-(

Timeshift ? )))

The second timer hasnt any effect meanwhile, because I only found one ProgDVB-symbol in the tasklist and there was no entry for the second recording on harddrive.

Something must have been changed, that recording starts not for the first timer. Unfortunately this Task will never end - except you stop it manually next morning.

Yes, the task has activated "Perform action after recording is completed = LEAVE"

Would be nice if he would

the recording from 6th this month was the last one.

Now I've to kill to ProgDVB-windows each morning, both completely white.
First one is ok, secon one didnt like to be closed.
Only kill in taskmanager can stop.

Frustrated!

...to give a successfull message: Capturing with 6.48.1 is working perfect now!!!
The only thing is, when waking up my netbook from STANDBY, Netbook can not go down again (standby, hibernate, shut down, whatever, doesn't matter). Waking up from hibernation and going back runs without any problems.
Seems to have something to do with the graphic - when waking-up from standby because of a progdvb-capture-task, the screen stays allways totally black. tried out different renderers - without succes. Waking up and capturing (with vmr7) works, but no shutting down to any state.

Anyway, thanks a lot, hibernate is ok for me
Olnima

agree, since 6.48.02 I also succeeded.

Second hint:
I did the crons by using EPG - record.
What I never realized was the timewindow for end of recording....
In case of 1405-1500 and 1505-1600 it fails becuase of overlapping.

But my respect:
after realizing this at my site and the 6.48.02 : full satisfied!