A Teaser :P

[reven]

make sure you have a "App_Data" directory and there is a NextPVRWebConsole.db file in there that has data, might be permission issue.

you might be better off just waiting for the alpha.

[carpeVideo]

It was there (app data and db) - I think there was an issue with IIS vs visual studio - I stopped everything and dl'd the project from scratch and it appears to function. Looks quite nice, great work, though a tad slow at times. Let me know if there is anything I can do to help.

CV

[reven]

whereabouts is it slow? the only slow place im aware of is exiting the guide page after loading another day, which im currently trying to fix (I think its all the knockout data binding).

everything else for me is basically instant page changes.

[carpeVideo]

Here is what I see so far -
Recordings: Available spelled incorrectly, entries do not match those of NPVR, may be because of recording group, I only get one recording group which is the title of the last recording
Slowness: Frequently when I hit the guide page (20 secs to refresh), sometimes when I go to the recordings tab
Dashboard/Disk Usage: Key is overlapping one of the categories % values
User Settings/Channel Group: Here you can configure your own CHANEL (mis-spelled) groups
When I open NPVR with the web app on I have had intermittent NPVR crashes. I will see if I can capture a log.
Sometimes when the "working" dialogue is up and I switch tabs I see a red "An unexpected error has occurred"

That is what I see for now, a great bit of work in a short time. Let me know if you want me to log any on github,

CV

[reven]

nah dont log anything on github yet, only log against a actual release.

spelling mistakes im aware of a few, honestly havent paid a lot of attention to this yet, more worried about features/bugs and not to worried on cosmetic issues. more worried about making sure everything is in the translation files and can be translated. then the spelling stuff arent hardcoded and can be easily updated.

the dashboard disk space is temporary, basically just a placeholder for now, will be switching this after the first alpha. will be switching to a bar graph type display so can show multiple drives (my tv buffer drive is on a different drive than my recordings so pie doesnt make sense). just a place holder to show what will go there. open to suggestions as to what else you want to see on the dashboard.

guide slowness, if you open chrome dev tools see how long its taking to pull the XHR request data, ive gotten it down from 15 seconds on my machine to 400ms the first time then 200ms the second time (with around 70 channels in the epg). but rendering still takes a couple of seconds (working on improving this).

i suspect the slowness you are seeing on the recording tab is just after leaving the guide page, the guide page is taking a long time to exit for some odd reason. im working on fixing this.

im moving all the direct npvr calls to one place and trying to cache them as much as possible, hopefully that will stop the npvr crashes (i believe its due to the sqlite db file being locked, im not doing any direct sql commands against the db, so its an api call in npvr itself, dont believe anyone has used npvr the way im using it atm).

[UncleJohnsBand]

reven....can you post your system specs (CPU, Mem, HD, Video) that you are running on so we have a baseline of what should be working fast as you indicated above?

[reven]

this was on a core i5 3.6ghz with 16gb ram, which yeah is fast

but also same speeds i saw on a windows xp machine running in VirtualBox, changing pages should be near instant, loading epg data should be the only slowish thing (since has to load all the data for the day, check if any recordings are scheduled, check if that user has access to the scheduled recording), but im working on getting that done to a second or two atm.

not sure what the average channel count is however, i think 70 is on the high side (def on the high side in nz)

[UncleJohnsBand]

not sure what the average channel count is however, i think 70 is on the high side (def on the high side in nz)

sub may be able to answer that.....for US users that may be average.....international I would guess it is on the low side.

My current dev laptop (dual core) with 2GB ram W7 x64 it is slow.

[reven]

you're not running against the the released version, so i wouldnt pay much attention to speed, i cant guarantee the speed at some random point of the source code.

having said that, 2GB is really low, but my windows xp VM only had 1 GB assigned to it.

also what part is slow?

[carpeVideo]

I would not pay much attention to spelling either - definitely the boring part :0)
One quick suggestion, in the guide show detail you may want to add the subtitle.

CV