[DOCKER] Mythtv


Recommended Posts

I finally found the correlation between the folder structure I see while logged into mythtv through rdp & SSH into tower as root. 

 

When I ssh into TOWER using the root user I find the mythtv files here...

./var/lib/docker/btrfs/subvolumes/e3eb4128aafcf58dc7aecdbdebab205928ef824f3f600d180dc158ae9d96640f/

 

in the RDP window I created a new folder named testing, that folder appeared in the above directory in the SSH window.

 

So where is the problem, is it the docker/installs fault for locating the mythtv files here instead of the mapping I attempted while installing the plugin or are the files supposed to be represented here but then linked/pointer to the cache drive and the pointer isn't working right?

 

This install I changed the volume mappings to

  /home/mythtv -> /mnt/cache/mythtv

  /db -> /mnt/cache/mythtv/data

  /var/lib/mythtv -> /mnt/cache/mythtv

 

 

Link to comment
  • Replies 236
  • Created
  • Last Reply

Top Posters In This Topic

I just sent an email to a friend who told me about unRAID to see if he had any ideas, here is the meat of the email, in case I said something new in this email...

 

So from within mythtv any time I config it to save something to /home/mythtv it should instead save it to /mnt/cache/mythtv.  I assume based on others examples that subfolders work this same way so /home/mythtv/recordings should map to /mnt/cache/mythtv/recordings.  /mnt/cache/ is how unRAID has mounted the 1.5TB cache drive. So if I SSH into unRAID as root, I see that drive's files/folders at that path.

  I can RDP into the mythtv docker container, it looks like a desktop (what I assume a linux desktop looks like). There is an icon which looks and acts like Windows Explorer, from this I can see the folders and files that mythtv is creating (including .mpg recordings)

  I can also connect Kodi to the mythtv backend and see live tv and recordings listed, playing as expected. 

  I can also connect to the backend via the mythtv web interface (which I think is the front end, but I'm not sure since I can't get it to play video, only look at the tv guide, schedule recordings, see status, that kind of thing. pretty much everything I would expect from a gui except the window to watch tv/recordings.  The mythweb has a status page which shows Total Space: 5,689 MB.  I would expect it to show much closer to 1.5TB (the size of the drive it should be saving to).

  The problem is that its not saving them to the drive I expect to find them and I'm afraid its actually saving to RAM but I really don't know enough about Linux to figure out he physical media associated with the file structure I see when I log into SSH using root/pw

  Earlier I used RDP logged into mythtv user to create a folder named 'testing', then from SSH w/root I used 'find -name testing' to find that folder here... "./var/lib/docker/btrfs/subvolumes/e3eb4128aafcf58dc7aecdbdebab205928ef824f3f600d180dc158ae9d96640f/"

  A bit later that folder "e3eb..." disappeared.  (I may have reinstalled the container, not sure).  Now 'find' doesn't find the mythtv location anymore. I recorded a show and see via RDP it crated a file  "1042_20150914164300.mpg.png" So I tried doing the find again but it did not find it.  If I run the find from /var or any subfolder it returns nothing. If I run find from root I get this message.

root@Tower:/#  find -name 1042_20150914164300.mpg.png

find: WARNING: Hard link count is wrong for `./proc/fs' (saw only st_nlink=10 but we already saw 8 subdirectories): this may be a bug in your file system driver.  Automatically turning on find's -noleaf option.  Earlier results may have failed to include directories that should have been searched.

find: `./proc/20197': No such file or directory

 

So does any of this ring any bells for you?

 

unRAID is currently running a health check on one of the disks that will take several more hours. When that finishes I'll restart the system, maybe that will help :)

Link to comment

I wonder if it's a Docker issue instead.  The other container I installed is crashplan.  After initial installation it worked, but later (maybe after a restart) when I RDP into the crashplan port and try to connect the front end to the back end I get a message that it cannot connect to the backup engine.  So my current theory is that Docker isn't working right, instead of mapping to actual hard drives, it tried to install the containers into RAM, so when the computer restarts the container is hosed.

 

thoughts?  Anyone... Anyone... Bueller?  Bueller?

Link to comment

Fresh reinstall did the trick.  (I think).  I removed all containers, removed docker, deleted everything (data/files/folders/users/shares) anything that could have been associated with the docker or any containers.  After reinstalling everything, mythtv seems to be working.  crashplan front end (via RDP) connected to the backend just after install. I shutdown & restarted the computer (unraid and all). now crashplan front end doesn't connect to the backend.  So making progress, but not complete yet.

Link to comment
  • 2 weeks later...

Started the docker and all my settings got wiped. No idea how. My recordings and LiveTV were still there, but nothing else. Had to reinitialize all my tuners and such.

 

Might just go back to this in a VM. There is no longer any development, and it is buggy at best...

 

EDIT: see a few posts down. Sparkyballs was correct and my folders aren't mapping properly :-(

Link to comment

Started the docker and all my settings got wiped. No idea how. My recordings and LiveTV were still there, but nothing else. Had to reinitialize all my tuners and such.

 

Might just go back to this in a VM. There is no longer any development, and it is buggy at best...

 

 

what development is needed exactly ? it works as well as can be expected from docker doing something it really isn't designed to do.

 

i've been using it now for in excess of 4 months and have never once lost my settings... i'm guessing you haven't mapped all the volumes correctly.

 

 

 

Link to comment

RDP into this docker stopped working this week after updating the unRAID Server OS to 6.1.3  The port mapping option disappeared from the docker setup.  I did have it mapped 3389 -> 3389 when I finally did get the docker working.  Sparklyballs, is there an update needed to the docker to work with the new Server version?  Everything seems to still work, livetV, recordings, etc but I don't know how to access the backend without the RDP. Is there a SSH CLI that I can access the backend?

 

thanks

Everend

Link to comment

Started the docker and all my settings got wiped. No idea how. My recordings and LiveTV were still there, but nothing else. Had to reinitialize all my tuners and such.

 

Might just go back to this in a VM. There is no longer any development, and it is buggy at best...

 

 

what development is needed exactly ? it works as well as can be expected from docker doing something it really isn't designed to do.

 

i've been using it now for in excess of 4 months and have never once lost my settings... i'm guessing you haven't mapped all the volumes correctly.

 

You are correct. After pulling my hair out, I found the problem, the folders aren't being mounted correctly.

 

I use unassigned devices plugin for my MythTV folders. For some reason, folders on my unassigned device HD do not pass through to docker :-(

 

https://lime-technology.com/forum/index.php?topic=38635.msg412432#msg412432

 

More troubleshooting time!

 

Link to comment

I initially tried to use an unassigned device for mythtv but ended up making that drive a cache drive and then it mapped effortlessly.  If you don't have a cache drive yet, then I suggest making your unassigned drive the cache drive, then set up each user share NOT to use the cache drive (if you are avoiding a cache drive).  Then it is an unused cache drive that you can use for mythtv (always mounted and replicates what others are successfully doing.  If you already have a cache drive and want to use this other drive for mythtv, maybe assign it as a second cache drive, one as an actual cache drive and the other as the mythtv cache drive.  I haven't looked into using two cache drives, I just know that you can do such a thing. -- redacted since trurl said this wouldn't work.

Link to comment

Seems to be a race condition when you restart docker while unraid running...

 

https://lime-technology.com/forum/index.php?topic=38635.msg410787#msg410787

 

Although I rebooted my box several times and had the same problem as well. I have also rebooted in the past and haven't had any problems.

 

Need to do more investigating but it works now, so off for some rest and relaxation.

 

Sparkyballs --> I didn't mean any harm or disrespect with my comment before, this docker is AMAZING and makes TV life much easier. Thank you for all of your hard work!

 

 

Link to comment

here is the docker log info

 

*** Running /etc/my_init.d/001-fix-the-time.sh...

Current default time zone: 'America/Chicago'
Local time is now:      Tue Sep 15 23:01:37 CDT 2015.
Universal Time is now:  Wed Sep 16 04:01:37 UTC 2015.

*** Running /etc/my_init.d/002-fix-the-config-etc.sh...
*** Running /etc/my_init.d/003-bring-up-the-database.sh...
Creating database(s).
Database(s) created.
Starting MariaDB...
Checking whether database(s) are ready
waiting.....
waiting.....
Starting MariaDB...
*** Running /etc/my_init.d/004-bring-up-rdp.sh...
*** Running /etc/my_init.d/005-bring-up-the-backend.sh...
Checking whether database(s) are ready
*** Running /etc/my_init.d/006-bring-up-mythweb.sh...
*** An error occurred. Aborting.
*** Shutting down /etc/my_init.d/006-bring-up-mythweb.sh (PID 1510)...
*** Init system aborted.
*** Killing all processes...
*** Running /etc/my_init.d/001-fix-the-time.sh...
*** Running /etc/my_init.d/002-fix-the-config-etc.sh...
icon for kill switch is set
default config file(s) appear to be in place
.Xauthority file appears to in place
kill switch is set
setup desktop icon is set
mythtv folders appear to be set
*** Running /etc/my_init.d/003-bring-up-the-database.sh...
Database(s) exists.
Starting MariaDB...
*** Running /etc/my_init.d/004-bring-up-rdp.sh...
*** Running /etc/my_init.d/005-bring-up-the-backend.sh...
Checking whether database(s) are ready
waiting.....
waiting.....
*** Running /etc/my_init.d/006-bring-up-mythweb.sh...
*** An error occurred. Aborting.
*** Shutting down /etc/my_init.d/006-bring-up-mythweb.sh (PID 865)...
*** Init system aborted.
*** Killing all processes...
*** Running /etc/my_init.d/001-fix-the-time.sh...
*** Running /etc/my_init.d/002-fix-the-config-etc.sh...
icon for kill switch is set
default config file(s) appear to be in place
.Xauthority file appears to in place
kill switch is set
setup desktop icon is set
mythtv folders appear to be set
*** Running /etc/my_init.d/003-bring-up-the-database.sh...
Database(s) exists.
Starting MariaDB...
*** Running /etc/my_init.d/004-bring-up-rdp.sh...
*** Running /etc/my_init.d/005-bring-up-the-backend.sh...
Checking whether database(s) are ready
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
*** Running /etc/my_init.d/006-bring-up-mythweb.sh...
*** Running /etc/my_init.d/001-fix-the-time.sh...
*** Running /etc/my_init.d/002-fix-the-config-etc.sh...
icon for kill switch is set
default config file(s) appear to be in place
.Xauthority file appears to in place
kill switch is set
setup desktop icon is set
mythtv folders appear to be set
*** Running /etc/my_init.d/003-bring-up-the-database.sh...
Database(s) exists.
Starting MariaDB...
*** Running /etc/my_init.d/004-bring-up-rdp.sh...
*** Running /etc/my_init.d/005-bring-up-the-backend.sh...
Checking whether database(s) are ready
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
*** Running /etc/my_init.d/006-bring-up-mythweb.sh...
*** An error occurred. Aborting.
*** Shutting down /etc/my_init.d/006-bring-up-mythweb.sh (PID 809)...
*** Init system aborted.
*** Killing all processes...
*** Running /etc/my_init.d/001-fix-the-time.sh...
*** Running /etc/my_init.d/002-fix-the-config-etc.sh...
icon for kill switch is set
default config file(s) appear to be in place
.Xauthority file appears to in place
kill switch is set
setup desktop icon is set
mythtv folders appear to be set
*** Running /etc/my_init.d/003-bring-up-the-database.sh...
Database(s) exists.
Starting MariaDB...
*** Running /etc/my_init.d/004-bring-up-rdp.sh...
*** Running /etc/my_init.d/005-bring-up-the-backend.sh...
Checking whether database(s) are ready
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
*** Running /etc/my_init.d/006-bring-up-mythweb.sh...
*** An error occurred. Aborting.
*** Shutting down /etc/my_init.d/006-bring-up-mythweb.sh (PID 786)...
*** Init system aborted.
*** Killing all processes...
*** Running /etc/my_init.d/001-fix-the-time.sh...
*** Running /etc/my_init.d/002-fix-the-config-etc.sh...
icon for kill switch is set
default config file(s) appear to be in place
.Xauthority file appears to in place
kill switch is set
setup desktop icon is set
mythtv folders appear to be set
*** Running /etc/my_init.d/003-bring-up-the-database.sh...
Database(s) exists.
Starting MariaDB...
*** Running /etc/my_init.d/004-bring-up-rdp.sh...
*** Running /etc/my_init.d/005-bring-up-the-backend.sh...
Checking whether database(s) are ready
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
*** Running /etc/my_init.d/006-bring-up-mythweb.sh...
*** An error occurred. Aborting.
*** Shutting down /etc/my_init.d/006-bring-up-mythweb.sh (PID 794)...
*** Init system aborted.
*** Killing all processes...
*** Running /etc/my_init.d/001-fix-the-time.sh...
*** Running /etc/my_init.d/002-fix-the-config-etc.sh...
icon for kill switch is set
default config file(s) appear to be in place
.Xauthority file appears to in place
kill switch is set
setup desktop icon is set
mythtv folders appear to be set
*** Running /etc/my_init.d/003-bring-up-the-database.sh...
Database(s) exists.
Starting MariaDB...
*** Running /etc/my_init.d/004-bring-up-rdp.sh...
*** Running /etc/my_init.d/005-bring-up-the-backend.sh...
Checking whether database(s) are ready
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
*** Running /etc/my_init.d/006-bring-up-mythweb.sh...
*** An error occurred. Aborting.
*** Shutting down /etc/my_init.d/006-bring-up-mythweb.sh (PID 805)...
*** Init system aborted.
*** Killing all processes...
*** Not all processes have exited in time. Forcing them to exit.
*** Running /etc/my_init.d/001-fix-the-time.sh...
*** Running /etc/my_init.d/002-fix-the-config-etc.sh...
icon for kill switch is set
default config file(s) appear to be in place
.Xauthority file appears to in place
kill switch is set
setup desktop icon is set
mythtv folders appear to be set
*** Running /etc/my_init.d/003-bring-up-the-database.sh...
Database(s) exists.
Starting MariaDB...
*** Running /etc/my_init.d/004-bring-up-rdp.sh...
*** Running /etc/my_init.d/005-bring-up-the-backend.sh...
Checking whether database(s) are ready
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
*** Running /etc/my_init.d/006-bring-up-mythweb.sh...
*** An error occurred. Aborting.
*** Shutting down /etc/my_init.d/006-bring-up-mythweb.sh (PID 890)...
*** Init system aborted.
*** Killing all processes...
*** Not all processes have exited in time. Forcing them to exit.
*** Running /etc/my_init.d/001-fix-the-time.sh...
*** Running /etc/my_init.d/002-fix-the-config-etc.sh...
icon for kill switch is set
default config file(s) appear to be in place
.Xauthority file appears to in place
kill switch is set
setup desktop icon is set
mythtv folders appear to be set
*** Running /etc/my_init.d/003-bring-up-the-database.sh...
Database(s) exists.
Starting MariaDB...
*** Running /etc/my_init.d/004-bring-up-rdp.sh...
*** Running /etc/my_init.d/005-bring-up-the-backend.sh...
Checking whether database(s) are ready
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
*** Running /etc/my_init.d/006-bring-up-mythweb.sh...
*** An error occurred. Aborting.
*** Shutting down /etc/my_init.d/006-bring-up-mythweb.sh (PID 802)...
*** Init system aborted.
*** Killing all processes...
*** Running /etc/my_init.d/001-fix-the-time.sh...
*** Running /etc/my_init.d/002-fix-the-config-etc.sh...
icon for kill switch is set
default config file(s) appear to be in place
.Xauthority file appears to in place
kill switch is set
setup desktop icon is set
mythtv folders appear to be set
*** Running /etc/my_init.d/003-bring-up-the-database.sh...
Database(s) exists.
Starting MariaDB...
*** Running /etc/my_init.d/004-bring-up-rdp.sh...
*** Running /etc/my_init.d/005-bring-up-the-backend.sh...
Checking whether database(s) are ready
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
*** Running /etc/my_init.d/006-bring-up-mythweb.sh...
*** An error occurred. Aborting.
*** Shutting down /etc/my_init.d/006-bring-up-mythweb.sh (PID 811)...
*** Init system aborted.
*** Killing all processes...
*** Running /etc/my_init.d/001-fix-the-time.sh...
*** Running /etc/my_init.d/002-fix-the-config-etc.sh...
icon for kill switch is set
default config file(s) appear to be in place
.Xauthority file appears to in place
kill switch is set
setup desktop icon is set
mythtv folders appear to be set
*** Running /etc/my_init.d/003-bring-up-the-database.sh...
Database(s) exists.
Starting MariaDB...
*** Running /etc/my_init.d/004-bring-up-rdp.sh...
*** Running /etc/my_init.d/005-bring-up-the-backend.sh...
Checking whether database(s) are ready
waiting.....
waiting.....
waiting.....
waiting.....
*** Running /etc/my_init.d/006-bring-up-mythweb.sh...
*** An error occurred. Aborting.
*** Shutting down /etc/my_init.d/006-bring-up-mythweb.sh (PID 861)...
*** Init system aborted.
*** Killing all processes...
*** Not all processes have exited in time. Forcing them to exit.
*** Running /etc/my_init.d/001-fix-the-time.sh...
*** Running /etc/my_init.d/002-fix-the-config-etc.sh...
icon for kill switch is set
default config file(s) appear to be in place
.Xauthority file appears to in place
kill switch is set
setup desktop icon is set
mythtv folders appear to be set
*** Running /etc/my_init.d/003-bring-up-the-database.sh...
Database(s) exists.
Starting MariaDB...
*** Running /etc/my_init.d/004-bring-up-rdp.sh...
*** Running /etc/my_init.d/005-bring-up-the-backend.sh...
Checking whether database(s) are ready
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
waiting.....
*** Running /etc/my_init.d/006-bring-up-mythweb.sh...

Link to comment

...  If you already have a cache drive and want to use this other drive for mythtv, maybe assign it as a second cache drive, one as an actual cache drive and the other as the mythtv cache drive.  I haven't looked into using two cache drives, I just know that you can do such a thing.

Multiple cache drives are only supported as btrfs raid, so they cannot be used separately for different purposes.
Link to comment

thanks elfner11  That command did get me a cli inside the docker, but I haven't figured out how to do anything in there yet :) 

 

Unfortunately, It looks like mythlink.pl is not included in my docker container.

 

find . -name mythlink.pl

returned nothing

 

I found the mythlink.pl script online, now I just need to figure out how to get it into the container so I can run it.

 

g'night

Link to comment

(This thing works fantastic BTW, thank you +100 for putting this together, MythTV installation has NEVER been this easy!)

 

I've considered testing out passing through an extra NIC I have specifically to this Docker.

Since all of my tv tuners are HDHR's (I have 2, going up to 3) there is a decent amount of activity on my shared bridged NIC in UnRAID.

 

Every once in a while while skipping forward during playback of recorded TV I get a 2 second or so pause on every skip.

It gets annoying, as when it is working properly it is basically instant.

 

Anyhow, minus all of the specifics to my specific hardware address, would this be able to be accomplished by adding the proper string into the extra parameters section for the Docker?

I assume this would require the Docker to support/have a driver for an Intel NIC, which I have no idea if that is the case.

 

Any input appreciated.

 

Link to comment
  • 1 month later...

Edit:  Ended up solving this...not with cron, but by using mythtv setup. The 11th screen of General settings has a place you can add extra parameters for mythfilldatabase. I tried using this a few days ago but it wasn't working. I think, in my attempts to get cron working, that I changed the permission on my guide.xml file generated by webgrabplusplus. And now my guide data is downloaded and put in mythtv's database.  Sweet!

 

 

Original post:

 

Just switched over to MythTV from tvheadend as I was having trouble with pausing and skipping of livetv. I have to say I'm very happy with it's performance.

 

The only thing I can figure out is how to run a cron job and am looking for some guidance. I've tried something as simple as:

crontab -e, and adding this:

* * * * * /usr/bin/touch ./testfile

and I can't even get that to run. Needless to say I can't get mythfilldatabase to run in cron either and that's my goal.

 

I've also tried:

sudo nano /etc/crontab and adding:

* * * * * root /usr/bin/touch ./testfile

and

* * * * * mythtv /usr/bin/touch ./testfile

 

/var/log/syslog is empty.

 

touch and mythfilldatabase work from the CLI so I'm thinking it's a user or permissions thing, but can't figure it out.

 

Thanks for any help.

Link to comment
  • 4 weeks later...

trying to transition from a win2012 server to something that doesnt require as much maintenance to keep everything moving smoothly. freenas was too security driven, omv is a touch too buggy and not enough support atm so im trying out the unraid trial atm.

 

I have attic antennae feeding 2 hdhr3-us's, running to whatever nas i settle on, and 4 openelec front ends, fairly standard i believe. i need to run sickbeard, couchpotato, sabnzbd, plex and mythtv. all the other nas offerings worked fine on all but the mythtv. so i installed fresh unraid trial, and started there first. i followed sparklyballs directions (i think) and was able to rdp into mythtv but after database fill i get a box that comes and goes too fast to read. when i try to run webui i get the attached error messages, which im assuming is whats in that dissapearing box. can anyone make sense of that to tell me what im doing wrong?

mythtv_error.txt

Link to comment
  • 4 weeks later...

 

I finally found out what my problem was re not being able to record from the on-screen guide - and it was on my end. For whatever reason I never created a "Directory" in the "Default" group within "Storage Directories". Once I did this, I had instant success. I'm really sorry for wasting your time on this. Hopefully, however, somebody else will benefit from my idiocy. Thanks again for all of your help.

 

Sparkly, at the risk of increasing the size of your already exploded skull, you are back to being brilliant. Sorry that I every doubted you!

 

I followed your journey here and I ended up with with a non-assigned disk working with myth.

 

so I certainly benefited  ;D

 

thanks

 

Link to comment

Just a reminder to any one getting tuner going, you'll need to use the mediabuild version of unraid and remember to add extra parameters into the docker (mapping to card).

 

Settings that work for my dual tuner Hauppauge are below:

 

--device=/dev/dvb/adapter0/demux0:/dev/dvb/adapter0/demux0 --device=/dev/dvb/adapter0/dvr0:/dev/dvb/adapter0/dvr0 --device=/dev/dvb/adapter0/frontend0:/dev/dvb/adapter0/frontend0 --device=/dev/dvb/adapter1/demux0:/dev/dvb/adapter1/demux0 --device=/dev/dvb/adapter1/dvr0:/dev/dvb/adapter1/dvr0 --device=/dev/dvb/adapter1/frontend0:/dev/dvb/adapter1/frontend0

 

Hello, I could use some help, I have a Hauppauge WinTV 2250 I'd like to use with mythtv.  I am using a mediabuild version of unRAID, and the MediaTreeCheck plugin says Detected.  But the card doesn't show up in the dropdown menu in the mythtv backend (probably cause mythtv doesn't see it yet, right?).  MythTV is working nicely with my HDHomeRun, but I'd like to use the card as well.

 

I've attached a screenshot of my container setup.  I'm just not sure where to enter those settings quoted above.  Thanks for any help, I would appreciate it!

myth_container.png.269456fdf9e2bedaf5c3fb18f1bb7385.png

Link to comment

Just a reminder to any one getting tuner going, you'll need to use the mediabuild version of unraid and remember to add extra parameters into the docker (mapping to card).

 

Settings that work for my dual tuner Hauppauge are below:

 

--device=/dev/dvb/adapter0/demux0:/dev/dvb/adapter0/demux0 --device=/dev/dvb/adapter0/dvr0:/dev/dvb/adapter0/dvr0 --device=/dev/dvb/adapter0/frontend0:/dev/dvb/adapter0/frontend0 --device=/dev/dvb/adapter1/demux0:/dev/dvb/adapter1/demux0 --device=/dev/dvb/adapter1/dvr0:/dev/dvb/adapter1/dvr0 --device=/dev/dvb/adapter1/frontend0:/dev/dvb/adapter1/frontend0

 

Hello, I could use some help, I have a Hauppauge WinTV 2250 I'd like to use with mythtv.  I am using a mediabuild version of unRAID, and the MediaTreeCheck plugin says Detected.  But the card doesn't show up in the dropdown menu in the mythtv backend (probably cause mythtv doesn't see it yet, right?).  MythTV is working nicely with my HDHomeRun, but I'd like to use the card as well.

 

I've attached a screenshot of my container setup.  I'm just not sure where to enter those settings quoted above.  Thanks for any help, I would appreciate it!

 

Does it detect both the mediabuild and the DVB adapter?

Link to comment

Click on "Advanced View" (in the upper right). Fill in the "Extra Parameters" field with that text (--device=/dev/dvb/adapter0...etc) you quoted in your original post, and restart the docker.

 

The colour of the "Advanced View" button and label is terrible. It's hard to see and/or it looks greyed out like it can't be selected. It got me the first time too. It should be changed.

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.