Mailing List Archive

1 2 3 4 5 6 7  View All
Re: (no subject) [ In reply to ]
On Jan 12, 2012 6:55 AM, "Thomas Boehm" <mythtv-users@lists.boehmi.net>
wrote:
>
> James Olsovsky wrote:
> > [SPAM deleted]
>
> Can somebody please unsubscribe this Spammer? If he's not subscribed,
> how is it possible that this comes through?

I did so last night.
Re: (no subject) [ In reply to ]
Thomas Boehm wrote:
> Can somebody please unsubscribe this Spammer?

Was he a spammer or was his Google account cracked?

Doug


--

Ben Franklin quote:

"Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety."

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: (no subject) [ In reply to ]
On Thu, Jan 12, 2012 at 11:22 AM, Doug Lytle <support@drdos.info> wrote:
>
> Thomas Boehm wrote:
>> Can somebody please unsubscribe this Spammer?
>
> Was he a spammer or was his Google account cracked?

How the heck would we know? Don't know, don't care. Two spam in two
days, he's no longer on the list.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
RE : (no subject) [ In reply to ]
Oups! scuse for the noise.


-------- Original message --------
Subject: [mythtv-users] (no subject)
From: YB <ydebx2@free.fr>
To: mythtv-users@mythtv.org
CC:




Envoyé depuis Samsung Galaxy Note
Re: (no subject) [ In reply to ]
http://velplan.vndv.com/foxnews.newnewstory01.php
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: (no subject) [ In reply to ]
On 29.03.2013 13:41, Richard Morton wrote:
> http://www.engadget.com/2013/03/28/bbc-details-iplayers-open-source-tv-application-layer/
>
> Does this help with integrating to BBC services (and eventually other
> companies if they adopt a similar approach)?

From my understanding its a framework to create similar applications,
but not to integrate with their backend services.
There appear to be some APIs under way for that, too. At least that's
my understanding from following some blogs, but this something else.

Regards,
Karl
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: (no subject) [ In reply to ]
>> I currently use Sony PS3 bluetooth remotes to control my various myth
boxes - whilst working ok >>they are very demanding on batteries.
>>
>> Im thinking in the future to use this technology : Bluetooth Low
Energy. There are already dongles out and some initial linux support.
>>
>> Does anyone have any experience of it? or any views on this subject?

>Do you apply the kitlaan bluez patches to allow them to sleep? My
>batteries last months. Only drawback is they take a few seconds to
>wake up but you soon get used to that
>Martin

Hi Martin , thanks for the reply.

Yes I've applied the kitlaan patches - using a ppa for mythbuntu. These
remotes are heavily used by the family and last a few weeks.

Also when they get low on batteries they tend to go a bit crazy ;key keeps
repeating, even though the batteries in the remote are removed.

I've also tried the bluetooth ng on google code. (
https://code.google.com/p/bdremote-ng/) This has similar problems.

I've got 3xfrontends and 3x PS3 remotes with 3 different bluetooth
adaptors.
Re: (no subject) [ In reply to ]
> Hi Martin , thanks for the reply.
>
> Yes I've applied the kitlaan patches - using a ppa for mythbuntu. These
> remotes are heavily used by the family and last a few weeks.
>
> Also when they get low on batteries they tend to go a bit crazy ;key keeps
> repeating, even though the batteries in the remote are removed.
>
> I've also tried the bluetooth ng on google code. (
> https://code.google.com/p/bdremote-ng/) This has similar problems.
>
> I've got 3xfrontends and 3x PS3 remotes with 3 different bluetooth
> adaptors.
>
>
>
I use mine without any problems and they last months...that long I can
never remember when the batteries were last put in. That said I do use
pretty high capacity NiMH batteries so prob have more life than alkaline
cells

My wiki page is here regarding how I have set mine up

http://www.harley-jones.co.uk/?p=41

This might be slightly outdated now as I did this some time ago but it wont
be far wrong. I think the main change is uinput now part of the kernel(?)

I use a 5 minute timeout on mine and just accept that you have to be a bit
patient allowing it to come out of sleep mode to the order of a few seconds
(and sometimes press the key again). We soon got used to that.

I think your craziness of repeated key presses are brought on by low
batteries but not the root problem. I use boith xbmc and mythtv on the same
box and switch between the two using irexec applied to the eject key. I
have had the craziness you describe but only in mythtv and never in xbmc
and this occurs when when the remote is coming out of hibernation if I
press the same key twice in fairly quick succession (if the remote is awake
then it is never a problem).

I think you are seeing this when the batteries get low because it has
hibernated/lost connection. This ONLY ever happens in mythtv and never in
xbmc but I dont really know why this should be any different between the
two. I find when it happens my only course of action is to get the keyboard
and press esc

Martin
Re: (no subject) [ In reply to ]
Am 08.04.2013 14:01, schrieb Adam Skinner:
>
> >> I currently use Sony PS3 bluetooth remotes to control my various
> myth boxes - whilst working ok >>they are very demanding on batteries.
> >>
> >> Im thinking in the future to use this technology : Bluetooth Low
> Energy. There are already dongles out and some initial linux support.
> >>
> >> Does anyone have any experience of it? or any views on this subject?
>
> >Do you apply the kitlaan bluez patches to allow them to sleep? My
> >batteries last months. Only drawback is they take a few seconds to
> >wake up but you soon get used to that
> >Martin
>
> Hi Martin , thanks for the reply.
>
> Yes I've applied the kitlaan patches - using a ppa for mythbuntu.
> These remotes are heavily used by the family and last a few weeks.
>
> Also when they get low on batteries they tend to go a bit crazy ;key
> keeps repeating, even though the batteries in the remote are removed.
>
> I've also tried the bluetooth ng on google code.
> (https://code.google.com/p/bdremote-ng/) This has similar problems.
>
> I've got 3xfrontends and 3x PS3 remotes with 3 different bluetooth
> adaptors.
>
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users

Hey thanks for the hint to PS3 BT remotes - just ordered one on eBay
because I do not always have good reception with my IR remote... I will
use it with Eneloop LSD rechargeable batteries and don't really mind to
change batteries every once in a while.

I recommend Eneloop to you too, they give good performance (last long
without discharging too much when being left alone) in low energy
devices like a remote and you will save a lot of money if you use them
instead of replacing all the hardware.
Re: (no subject) [ In reply to ]
Dave Matthews wrote:
> Alternatively - where can I get the 0.25 sources so that I figure out
> what is being called? Google found 0.26 and 0.27pre but not the 0.25.

git clone -b fixes/0.25 git://github.com/MythTV/mythtv.git

Doug


--
Ben Franklin quote:

"Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety."

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: (no subject) [ In reply to ]
Doug,

Thanks. It has been a long time since I wrote c++ but there is nothing
obvious. It looks like the device name is being found (seems to be passing
the test) and the fail is on. The device name appears to be the audio
device line out of the GUI with the left 5 characters removed.

if (AlsaBad(snd_pcm_open(&pcm_handle, alsa_device.constData(),
SND_PCM_STREAM_CAPTURE, 0), // blocking mode
"pcm open failed"))

Looks like I am going to have to look into the ALSA code to figure out what
snd_pcm_open is looking for.

Dave
Re: (no subject) [ In reply to ]
On 27/05/2013 1:17 PM, Dave Matthews wrote:
> I am running MythTV 0.25 on Ubuntu. The machine had a failed upgrade
> to 12.04 from 11.something and would not boot. A fresh install of
> 12.04 was done to a new drive and the database and recording
> directories brought over from the old drive. OTA recoding works fine.
> I also use a V4L analog input for a feed out of my satellite receiver.
> I get video recorded but not audio. Troubleshooting I find this in the
> mythtvbackend.log file.
>
> May 27 10:31:42 htpc mythbackend[3160]: I TVRecEvent tv_rec.cpp:3989
> (TuningNewRecorder) TVRec(1): rec->GetPathname():
> '/var/lib/mythtv/recordings/1110_20130527103200.nuv'
> May 27 10:31:44 htpc mythbackend[3160]: E TVRecEvent
> audioinputalsa.cpp:336 (AlsaBad) *AudioInALSA(default:CARD=CA0106):
> pcm open failed:* Invalid argument
> May 27 10:31:44 htpc mythbackend[3160]: E TVRecEvent
> NuppelVideoRecorder.cpp:772 (AudioInit) NVR(/dev/video0): Failed to
> open audio device ALSA:default:CARD=CA0106
> May 27 10:31:44 htpc mythbackend[3160]: E TVRecEvent
> NuppelVideoRecorder.cpp:700 (Initialize) NVR(/dev/video0): Failed to
> init audio input device
> May 27 10:31:44 htpc mythbackend[3160]: N Scheduler autoexpire.cpp:263
> (CalcParams) AutoExpire: CalcParams(): Max required Free Space: 2.0 GB
> w/freq: 15 min
> May 27 10:31:44 htpc mythbackend[3160]: I Scheduler scheduler.cpp:2033
> (HandleReschedule) Reschedule requested for id 0.
> May 27 10:31:44 htpc mythbackend[3160]: E NVRAudio
> audioinputalsa.cpp:336 (AlsaBad) AudioInALSA(default:CARD=CA0106): pcm
> open failed: Invalid argument
> May 27 10:31:44 htpc mythbackend[3160]: E NVRAudio
> NuppelVideoRecorder.cpp:2380 (doAudioThread) NVR(/dev/video0): Failed
> to open audio device ALSA:default:CARD=CA0106
> May 27 10:31:44 htpc mythbackend[3160]: I Scheduler scheduler.cpp:2093
> (HandleReschedule) Scheduled 2 items in 0.2 = 0.00 match + 0.21 place
>
> This is the parameter that was in place for years on the old
> installation. The CA0106 is a soundblaster PCI card. Something has
> changed in 12.04. How should I adjust the parameter so Mythtv gets
> the right sound input device?
> Alternatively - where can I get the 0.25 sources so that I figure out
> what is being called? Google found 0.26 and 0.27pre but not the 0.25.
>
> Dave

Just a shot in the dark here, is it possible the device name got changed
in the upgrade? What does 'aplay -L' show for available audio devices
and are the permissions on the audio devices are correct?

HTH,

Andrew.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: (no subject) [ In reply to ]
On Tue, May 28, 2013 at 10:36 AM, Andrew Stadt <acstadt@stadt.ca> wrote:

> On 27/05/2013 1:17 PM, Dave Matthews wrote:
>
>> I am running MythTV 0.25 on Ubuntu. The machine had a failed upgrade to
>> 12.04 from 11.something and would not boot. A fresh install of 12.04 was
>> done to a new drive and the database and recording directories brought over
>> from the old drive. OTA recoding works fine. I also use a V4L analog input
>> for a feed out of my satellite receiver. I get video recorded but not
>> audio. Troubleshooting I find this in the mythtvbackend.log file.
>>
>> May 27 10:31:42 htpc mythbackend[3160]: I TVRecEvent tv_rec.cpp:3989
>> (TuningNewRecorder) TVRec(1): rec->GetPathname():
>> '/var/lib/mythtv/recordings/**1110_20130527103200.nuv'
>> May 27 10:31:44 htpc mythbackend[3160]: E TVRecEvent
>> audioinputalsa.cpp:336 (AlsaBad) *AudioInALSA(default:CARD=**CA0106):
>> pcm open failed:* Invalid argument
>> May 27 10:31:44 htpc mythbackend[3160]: E TVRecEvent
>> NuppelVideoRecorder.cpp:772 (AudioInit) NVR(/dev/video0): Failed to open
>> audio device ALSA:default:CARD=CA0106
>> May 27 10:31:44 htpc mythbackend[3160]: E TVRecEvent
>> NuppelVideoRecorder.cpp:700 (Initialize) NVR(/dev/video0): Failed to init
>> audio input device
>> May 27 10:31:44 htpc mythbackend[3160]: N Scheduler autoexpire.cpp:263
>> (CalcParams) AutoExpire: CalcParams(): Max required Free Space: 2.0 GB
>> w/freq: 15 min
>> May 27 10:31:44 htpc mythbackend[3160]: I Scheduler scheduler.cpp:2033
>> (HandleReschedule) Reschedule requested for id 0.
>> May 27 10:31:44 htpc mythbackend[3160]: E NVRAudio audioinputalsa.cpp:336
>> (AlsaBad) AudioInALSA(default:CARD=**CA0106): pcm open failed: Invalid
>> argument
>> May 27 10:31:44 htpc mythbackend[3160]: E NVRAudio
>> NuppelVideoRecorder.cpp:2380 (doAudioThread) NVR(/dev/video0): Failed to
>> open audio device ALSA:default:CARD=CA0106
>> May 27 10:31:44 htpc mythbackend[3160]: I Scheduler scheduler.cpp:2093
>> (HandleReschedule) Scheduled 2 items in 0.2 = 0.00 match + 0.21 place
>>
>> This is the parameter that was in place for years on the old
>> installation. The CA0106 is a soundblaster PCI card. Something has changed
>> in 12.04. How should I adjust the parameter so Mythtv gets the right sound
>> input device?
>>
>> Alternatively - where can I get the 0.25 sources so that I figure out
>> what is being called? Google found 0.26 and 0.27pre but not the 0.25.
>>
>> Dave
>>
>
> Just a shot in the dark here, is it possible the device name got changed
> in the upgrade? What does 'aplay -L' show for available audio devices and
> are the permissions on the audio devices are correct?
>
> HTH,
>
> Andrew.
>
>
>
I think I have it figured out. Ubuntu switched to Pulseaudio being the
default and that is what is causing the grief. They have a device picker
that was conflicting with gnome-alsamixer. I didn't realize that I was
turning things on and off in alsa with their GUI tool that I was using to
look at the sound system. Would it have been so difficult to get the state
of the sound system at app startup and indicate which devices were set as
default? I found this by ripping the soundblaster out of the machine and
trying to set up with the internal card (simplify the system to
troubleshoot). The plan for tonight is to put the soundblaster back in and
use the Ubuntu Sound Settings tool to pick the correct input and output
devices. Then I will set up MythTV to use either the default alsa devices
or to use pulse. If that doesn't work I will download Debian and dump
Ubuntu. It used to work so well until they decided to go off into never
never land and try to emulate Apple.

Dave
Re: (no subject) [ In reply to ]
Oops, didn't mean to leave the subject blank. I'll only re-post if I don't
get responses.

On Tue, Oct 6, 2015 at 9:39 PM, Jonno <jonnojohnson@gmail.com> wrote:

> I have a combined BE/FE mythbuntu machine. All of a sudden today the
> recordings aren't showing up in the recordings page. It does show that I
> have 90% of my storage used so it's not like it can't find the storage
> directory.
> I can access and play the recordings over mythweb.
>
> Any thoughts? I've done the optimize tables etc for the database.
>
Re: (no subject) [ In reply to ]
> On 30 Nov 2015, at 8:00 pm, mythtv-users-request@mythtv.org wrote:
>
>> [for the ignorant like me 11n is 300M bits/sec]
>
> No it isn't.
> Like any wireless system, it's speed is "up to ..." and of course the marketing types will quote the maximum theoretical figures even if the only people in the world who can achieve that are engineers in a screened lab with perfect conditions and no interference from the neighbours.
>
> I recall reading of some research a few years ago that showed that in some places (eg blocks of flats and so on with dense coverage of WiFi routers), the actual throughput of WiFi on the 2.4G band was "naff all" as 95% of the theoretical bandwidth available was taken up by signalling - with the remaining 5% being shared between all the users.
>
> As already said, if you can, try the 5.8G band - not only is it less busy (still lots of 2.4G only kit around), there are more channels, and the signals travel shorter distances through buildings so less interference from neighbours.
>
>
> Better WiFi kit is now starting to employ "band steering" that will force client devices onto the 5.8G band where both ends support it and the signal is adequate for just these reasons.
>
>
> I'd suggest downloading iStumbler and exploring how much WiFi you have around you. If there's a lot then you can expect poor WiFi throughput.
>
>
> I *always* recommend cabled connections where practical. Short of faulty components/equipment, I've yet to see a situation where a cabled connection isn't superior in performance and reliability to wireless - but obviously it lacks the mobility element.
> At work we have a client who has just built an extension for a new office - we weren't consulted in any way or we'd have advised them accordingly. They put cabling in for phones and power - but said "we'll use WiFi". Last I heard their IT guy was pulling some cables in and clipping them along the new walls :-/

Simon thanks. Spoiled Aussies my nearest and only neighbour router is 50m away.
I too stick to wires, BUT macbook has *only* a USBC socket and you can but I’ve not put a suitable hub on it. I tried a 5th Gen i3 NUC (using the onboad wireless) and it was perfect.

I put an old eeepc and the macbook side by side and downloaded (scp) 200M. Rate on eee 4.5 MByte / sec while on the macbook 450 kByte / sec. (4.5 MByte is close to 53 MBit hmmm) So I guess a trip to apple shop is warranted.

Thanks all. With 20/20 hindsight that was so easy to do that I ought to have done it and spared the list the noise. Well a line in the sand: with a good wifi connection and 802.11g you can get flawless mythtv.

James
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: (no subject) [ In reply to ]
On 7 February 2018 at 23:25, Justin Smith <justin@smithpolglase.com> wrote:
>
> My frontend log doesn't show anything than a failure to connect to the
> backend. The log is here:
>
> https://pastebin.com/ZsQ8b4rg
>
> Cheers,
> Justin.
>

Hi Justin,

There have been multiple threads on here recently about Ubuntu being unable
to connect to the database after an upgrade, due to the database listening
on the wrong port due to a configuration change issue in mysql/mariadb.

I would suggest you go through those, as it looks like the same issue all
over again.

1 2 3 4 5 6 7  View All