I disabled the two modules.

I don't agree with what you said. It's all a question of how robust the software is.
Error/Exception handling should be a part of any software product.

Prog wrote:Why too many packets losted?

I don't know. Maybe it's the weather?
But I don't think it matters. The applications shouldn't crash.

Prog wrote:ps: I am not can repeat bug with double audio.

Do you see it in the log? Do you want me to try things and let you know what happens?

More crash logs. This time I muted the audio and left it running in the background while doing something else.

Prog wrote:Not bad idea but not now. Added to my planlist.

You're right. The stability issues are more important, I think.
Is it just me?

...or maybe just a checkbox in the channel properties: Don't include in Time-Shift Buffer. Default is unchecked.

Same transponder/mux? This is possible but need good idea for UI...
Yes, same transponder.
Regarding UI:
Maybe add another time-shift option "Current Channel + Selected Time-Shift Channels".
And add a checkbox in channel properties: Include in Selected Time-Shift Channels.

Just a suggestion, you ...

OK, your English is not very good, and it is difficult to communicate like this.

Let's say I use current channel mode in Time-Shift.
I watch Euro Sport. Then, when there are commercials I switch to BBC for some time because I don't like watching commercials. After 10 minutes I switch back to Euro ...

If you open 2 channels in "current channel mode" then both in buffer. Or?
If I use current channel mode and I watch channel 2. Then, when there are commercials I switch to channel 10 for some time and then switch back to channel 2 - The time shift buffer for channel 2 is empty.

Currently you ...

I set the buffer size to 800MB. That's enough for ~8 minutes. Most commercial breaks are longer than that. It's so short because all the channels are stored in the buffer. In my case: 6 TV channels + 13 Radio channels.
Currently, it's either current channel and every channel. Why not current ...

aac not very easy for detection. I hope no any problem in playback..
I can hear audio. Not sure if it is stereo or not.
It's not difficult to detect. I've done it myself. ISO/IEC 14496-3 Describes it and the LATM transport layer, SBR tool, etc.
Would you like me to record some of in TS format and ...

Prog wrote:thanks. I will test this.

ps: you have bad signal. Many packets losted. This is not important for double audio bug but very important for stability.

It depends on the time of day. At night it is very bad. During the day quality is at 99%-100%.

TV channel's audio is stereo AAC/LATM, and it uses the SBR tool, but ProgDVB says it is mono in OSD whenever I switch to the channel.
When I switch to radio stations it does show they're stereo.

It's easy to create that double audio bug with any two channels. I just did that with a TV channel and a Radio(!) channel.

And quickly clicking on channels in the channels panel and ProgDVB becomes unstable: Frame rate drops to 1 frame per second. Unwatchable. And it's not the DVB-T reception ...

...and another log. Same as before, ProgDVB minimized, I was listening to the news on TV. Then audio started stuttering and a few seconds later it stopped.
The application stopped responding, I couldn't restore the window.
So I killed it.

I tried to upload the log but it won't let me.

Here's a the log following a crash. I just left ProgDVB minimized (or was just just in the background?), listening to the news while playing chess online.

I've been using the free version (6.96.1) without a problem . I started the trial for the Pro version today and it's terribly unstable.

Here's what I did:
1. Started ProgDVB and watched channel 2.
2. Started PIP and selected channel 10. So now I see channel 2 in the small frame inside the big channel 10 picture.
3. Pressed on channel 2 in the Channel list.

Result: Video: switched to channel 2, no longer in PIP mode. Audio: I can ...