Hi,
what is the best way to make a cList derived object thread safe?
I have an object derived from cList and access it in the main thread and
also in a background thread.
The main thread access can modify the object (insert, edit, delete or
even reload the complete list) while the background t
On 20 Aug 2006 Christian Wieninger <[EMAIL PROTECTED]> wrote:
> what is the best way to make a cList derived object thread safe?
You have to protect all functions of your object which are
dealing with the list (reading and/or writing) with a cMutex.
Alternatively you could use a cRwLock, but thi
You have to protect all functions of your object which are
dealing with the list (reading and/or writing) with a cMutex.
Thanks! So the following should work (please correct me if I'm wrong):
I add a cMutex object in the cList derived class and 2 functions:
class cThreadSafecList: public c
Christian Wieninger wrote:
Thanks! So the following should work (please correct me if I'm wrong):
I add a cMutex object in the cList derived class and 2 functions:
class cThreadSafecList: public cList<...> {
...
private:
cMutex mutex;
public:
void Lock(void) { mutex.Lock(); }
void Unloc
Anssi Hannula wrote:
Martin Dauskardt wrote:
I upgraded to 1.4.1-4, which seems to include the patch from Anssi
(http://linuxtv.org/pipermail/vdr/2006-August/010360.html )
I am not happy with this patch: My machine has a FF-card and
Budget-Card+CAM. There was no timer for any encrypted channel
VDR maintenance patch 1.4.1-5 is now available at
ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-5.diff
This is a 'diff' against version 1.4.1-4 (which is the official
version 1.4.1, patched with
ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-1.diff,
ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-
Gavin Hamill schrieb:
On Wed, 16 Aug 2006 19:38:20 +0300
"Petri Helin" <[EMAIL PROTECTED]> wrote:
You might as well try your luck at the ProjectX forum. Although most
of the messages there are german, at least I have always gotten an
answer in english if the question was in english. dvb.mat
On Sun, 20 Aug 2006 15:59:21 +0200
Steffen Barszus <[EMAIL PROTECTED]> wrote:
> For the time being, you should also be able to deselect the audio
> track. If you have selected the recording, change to the list of
> recordings to be burned and hit ok, while you are at the recording
> there. You wi
Klaus Schmidinger wrote:
@Martin: any news on this? With recent drivers and firmware it should be
possible to record and watch even the high-bandwidth channels like ZDF
on a FF card.
Question is, how recent. I'm just running a recording on ARD.
vdr-1.4.1-5, DVB driver of kernel 2.6.16.19, late
Udo Richter wrote:
Klaus Schmidinger wrote:
@Martin: any news on this? With recent drivers and firmware it should be
possible to record and watch even the high-bandwidth channels like ZDF
on a FF card.
Question is, how recent. I'm just running a recording on ARD.
vdr-1.4.1-5, DVB driver of ke
Klaus Schmidinger wrote:> @Martin: any news
on this? With recent drivers and firmware it should be> possible to
record and watch even the high-bandwidth channels like ZDF> on a FF
card.
The problem appeared with "Tagesschau" on ARD. Not
every recording on ARD or ZDF has buffer problems, but
Martin Dauskardt wrote:
Klaus Schmidinger wrote:
> @Martin: any news on this? With recent drivers and firmware it should be
> possible to record and watch even the high-bandwidth channels like ZDF
> on a FF card.
The problem appeared with "Tagesschau" on ARD. Not every recording on
ARD or ZDF
Hello,
what does a line like this mean?
Aug 20 20:01:23 martini vdr: [29347] timer 7 (6 2250-0020 VPS '00new~Law &
Order - Die heimliche Geliebte') set to event Die 22.08.2006 23:10-00:00 'Law &
Order'
FYI: Timer 7 is a VPS timer. But its start time (22:50) is
NOT exactly the start time of the
On Fri, Aug 18, 2006 at 12:15:49PM +0300, Ville Skytt? wrote:
> On Tue, 2006-08-15 at 14:52 +0200, Jens Auer wrote:
>
> _syscallX are not available for userspace in recent kernel headers
> (since April), this causes VDR compilation failures also with the
> current Fedora Core 6 test versions. Mor
Dirk wrote:
Hello,
what does a line like this mean?
Aug 20 20:01:23 martini vdr: [29347] timer 7 (6 2250-0020 VPS '00new~Law & Order -
Die heimliche Geliebte') set to event Die 22.08.2006 23:10-00:00 'Law & Order'
FYI: Timer 7 is a VPS timer. But its start time (22:50) is
NOT exactly the star
Klaus Schmidinger wrote:
Dirk wrote:
Hello,
what does a line like this mean?
Aug 20 20:01:23 martini vdr: [29347] timer 7 (6 2250-0020 VPS
'00new~Law & Order - Die heimliche Geliebte') set to event Die
22.08.2006 23:10-00:00 'Law & Order'
FYI: Timer 7 is a VPS timer. But its start time (22
Klaus Schmidinger wrote:
Udo Richter wrote:
Lots of transfer buffer overflows and sluggish OSD, because
VDR used the primary FF card for recording, while the secondary budget
card is idle. System is back to normal if I switch to another channel.
Just tested it by recording ARD from the primar
Udo Richter wrote:
> Klaus Schmidinger wrote:
>
>> Udo Richter wrote:
>>
>>> Lots of transfer buffer overflows and sluggish OSD, because VDR used
>>> the primary FF card for recording, while the secondary budget card is
>>> idle. System is back to normal if I switch to another channel.
>>
>>
>> Ju
Anssi Hannula wrote:
Consider this scenario:
- user watches channel 1, transponder 1, via FF
- recording starts for channel 1, transponder 1, via FF
add here:
- live view is interrupted as FF switches to transfer mode
- recording starts for channel 2, transponder 2, via budget
The primary d
Udo Richter wrote:
> The primary device should be available for live viewing as long as
> possible. Even if I do a recording, the primary device should be
> available for channel switching, and not requiring transfer mode.
> Recording is the job of the budget card.
Hmm, it's not that easy beca
Chris Elsworth wrote:
On Fri, Aug 18, 2006 at 12:15:49PM +0300, Ville Skytt? wrote:
On Tue, 2006-08-15 at 14:52 +0200, Jens Auer wrote:
_syscallX are not available for userspace in recent kernel headers
(since April), this causes VDR compilation failures also with the
current Fedora Core 6 test
Jörn Reder wrote:
Hmm, it's not that easy because it ignores the original intention of
this thread.
Not really. The side effect that osdteletext will force recordings on
the FF card on the same transponder was caused by the change in 1.4.1-2,
that was some time before your post. Its going bac
Udo Richter wrote:
Jörn Reder wrote:
Hmm, it's not that easy because it ignores the original intention of
this thread.
Not really. The side effect that osdteletext will force recordings on
the FF card on the same transponder was caused by the change in 1.4.1-2,
that was some time before your
23 matches
Mail list logo
