I'll try that, thanks...


while you are at it, could you update the API list and add the type of parameter each function needs?

Thanks again.

PS.:

is it possible that DDMODAPI_ADD_LOG is broken as well?


Also, is there a way to display something on the status bar and/or in the system tray balloon tip?

Thanks, optional would be just fine

WARNING: No TS packets in the queue in last 1000 ms

What does this log file message mean?

Well, I know what it means but I am wondering why I see thousands of these. Why isn't DD trying to re-tune, re-start the device, or do whatever is necessary to fix this?

Thanks.

since I was able to reproduce it, here a screenshot of the 'small window'

I know the window you are talking about, unfortunately, I see it frequently with my TBS tuners... However, in this case there is no such window, just a small one saying 'sending message' (or similar), and a few seconds later a message box with a failure message like this: ---------------------------...

Hi,

DD 2.7.1 is sometimes trying to send crash emails which fails. This is actually a good thing, since it shouldn't send anything without the user's consent anyway.

Where can I turn this feature off?

RP

Thanks for the quick response.

hopefully soon...

can anyone help?

this is still not working...

Did you get a chance to find a solution for this?

I have a similar problem because of a changing device list.

could you add some sort of sleep timer command line option?

It should allow me to start DD at a certain time and exit after the set number of minutes. For instance, to have the news pop up on the second monitor and disappear again automatically...

from the online help:
>You can't start DD with multi-record cmd line options. They should be used after tuning to a channel initially. <

Could you make it possible?

If there is no other process running, it should automatically tune to the required transponder.

one can end a running DVBDream process by starting another process with the command line option /quit.
However, if the main process doesn't exist anymore, the 'quit'-process stays around until closed manually (or if you run it a second time with that command line option).

any update on this?

any update on this?