Bug #1148
Can't add new recording configurations
0%
Description
Sorry, here's another one...
I'm running a build from yesterday's master(commit:426ee1c03d70f5c8025fd474c51ef1adf33cbded), i.e. with the new recording passthrough stuff included. 2 problems have become apparent:
1. I've changed the default configuration (the only one that I have) to 'Pass-through', but programs have continued to be placed in mkv containers. This may be because those recordings were set up before the new pass-through stuff was introduced?
2. So I then tried to mess around with the configs and create a new one. I tried to open the drop down list in the DVR config section in the WebUI, but it wouldn't open (and there's no 'new config' button) so I renamed the default config to 'Test' which resulted in "dvr: Saving configuration 'Test'".
However, once the web page has been refreshed, it goes back to being named 'default' with no sign that it has actually stuck. This also persisted through a service restart. Hope I've not missed anything!
Files
History
Updated by Ben . over 12 years ago
Note: I just started a new recording on a currently playing program and it is coming out as .ts, so I guess point 1 is related to timers being set prior to me changing the config.
Updated by Adam Sutton over 12 years ago
There have been reports of problems with that drop down in some browsers. Though I forget what/if any the solution was. However it might have been related to some bad entries in the config as I think we determined it varied from user to user on the same browser version.
I've just checked and I can definitely create new configurations with Chromium 18.0.1025.151.
And you're correct, existing recordings will probably keep the old configuration.
Updated by Ben . over 12 years ago
Using Chrome 21 (Win 7) here, I just tested out the 'bad config' theory by wiping the dvr config folder, but no change. I would try using IE8, which is the other browser I have installed, but weirdly even if I log into an account with admin rights all I can see is the EPG/DVR tabs and I get a 401 error message coming up in the system log in Chrome.
Updated by Adam Sutton over 12 years ago
Are you building and installing a deb? If not what exactly are you doing?
Updated by Ben . over 12 years ago
I am building and installing a deb yeah, ./configure & make followed by the Autobuild script for precise/x64. I've attached the one I've currently got installed if you want to have a look at it.
This isn't really a serious issue since it's clear that problem #1 was just pre-existing timers, but I guess if I can run across it someone else will too.
Updated by Adam Sutton over 12 years ago
- Status changed from New to Resolved
- Priority changed from Normal to Low
Note: configure and make are redundant if you're building a deb, they have no impact on the deb build. Since it builds in a sandbox environment.
Can you try another browser just to confirm whether this is a browser specific issue in the UI or something more sinister.
Adam
Updated by Ben . over 12 years ago
Grabbed the portable version of Firefox 14.0.1, same behaviour, unable to open the drop down box. Checking the ~/tvheadend/dvr folder however, I can see that after attempting to create a config with the name '12345', there are now 2 config files:
config
config12345
Both contain what looks like valid info, so I guess it's a UI issue? The same problem with the drop down box occurs on the EPG window when trying to set the recording config, btw.
Updated by Adam Sutton over 12 years ago
This sounds like an exact duplicate of this then: #1045.
I'm guessing the posted fix won't work for you if you've started from scratch? But it might be worth a try.
Updated by Ben . over 12 years ago
Welp. It was All Configs (VR) not being ticked in the Access Control, as talked about on that ticket. I guess that's designed as a parental control or similar? Because I'm struggling to think of a situation where you'd want to limit access to DVR profiles, especially in such a way that you can still edit the default...
Sorry for wasting you time anyway.
Updated by Adam Sutton over 12 years ago
I'm going to leave this open for now. I think this has caused enough confusion that I need to investigate whether the issue is that config is not being properly migrated.
Updated by Ben . over 12 years ago
Not sure there was a problem with it being migrated, just me being an idiot and leaving it unticked just because. It's really, really not intuitive to have it unticked leaving what appears to be a broken dropdown box though. Really low priority stuff, but worth looking at altering I think.
Updated by Adam Sutton over 12 years ago
- Status changed from Need feedback to Invalid
Having looked at the code, I think it has to be the way it is. Though I agree that we should possibly make a note somewhere about the consequences of not ticking the box. But I don't think its a bug, like you say, its a misunderstanding.
I've created a general issue to update docs for 3.2 and have made a note about this. See #1150.