NscriptHelper - still working?

[psycik]

Been playing with nscripthelper to do some renames (move db entries from one location to another). But I seem to be having issues with the filenames.

In the DB under scheduled_recordings.filename I'm only getting a partial name: U:\Recordings\The Simpsons\The Simpsons_20170710_1

Am I missing something, and is it actually storing the entire name?

Then if I do a rename on either the partial or full name, it complains it can't find it.

[sub]

As far as I know it's still working.

Were the scheduled_recordings.filename entries correct initially (ie after recording), but became broken when you tried renaming them with nscripthelper? Any specific steps to reproduce?

Then if I do a rename on either the partial or full name, it complains it can't find it.

Did you remember to quote the parameters?

nscripthelper.exe -rename "U:\Recordings\The Simpsons\The Simpsons_20170710_1" "U:\Recordings\The Simpsons\The Simpsons_20170710_1.ts"

[psycik]

I'll try again, I'm sure they were quoted.

I tried with just the description parm and the log just says the recording can't be found with that name

[psycik]

So here's what it ran.

Running nScript helper on "C:\Program Files (x86)\NPVR\NScriptHelper" -Rename "U:\Recordings\The Simpsons\The Simpsons_20170710_15001530.ts" "\\aragorn\Recordings\The Simpsons\The Simpsons_20170710_15001530.ts"

And now I notice that recording doesn't show up in the recording_schedule table any more (that's the correct one isn't yet? Its been a while since i dug into this DB")

I've just removed the delete that happpen before nscripthelper runs - is my order a bit screwy, should I nscript rename, then delete the source video that's been copied to the new location?

[BrettB]

In the DB under scheduled_recordings.filename I'm only getting a partial name: U:\Recordings\The Simpsons\The Simpsons_20170710_1

Am I missing something, and is it actually storing the entire name?

What utility are you using to look at the scheduled_recordings table? In your example, the part that is listed is 50 characters. I'm wondering if your tool is only displaying the first 50 characters of the text field.

[psycik]

SqlLite Admin. Yeah does seem to be restricting it. Just got a new version. So if I run the utility by hand it seems to work, but not from postprocessing.bat.
set source=%1
set channel=%2
set recordingid=%3
set recorder=%4
set title=%5
set destPath=\\aragorn%~p1
set dest=%source:u:=\\aragorn%
"C:\Program Files (x86)\NPVR\NScriptHelper" -rename %source% %dest%

[mvallevand]

Your dest variable looks screwed up to me, not sure what you are trying to do. This might work better

dest=\\aragon\%%~pnx1

The 50 character problem is NextPVR doesn't follow its schema for the defined varchar field lengths and sqlite doesn't enforce it at all some tools do.

Martin

[psycik]

Your dest variable looks screwed up to me, not sure what you are trying to do. This might work better

dest=\\aragon\%%~pnx1

The 50 character problem is NextPVR doesn't follow its schema for the defined varchar field lengths and sqlite doesn't enforce it at all some tools do.

Martin

I can try that, but as far as I can tell, what I've got is giving me:
Source "U:\Recordings\The Simpsons\The Simpsons_20170710_15001530.ts"
dest "\\aragorn\Recordings\The Simpsons\The Simpsons_20170710_15001530.ts"

[sub]

The guys above are right - that 50 character problem can be ignored. The SQLite database engine doesn't enforce any string field lengths (even though they're defined in the schema). npvr.db3 has a lot of varchar(50) database fields that store a lot longer strings than 50 characters.

[psycik]

The guys above are right - that 50 character problem can be ignored. The SQLite database engine doesn't enforce any string field lengths (even though they're defined in the schema). npvr.db3 has a lot of varchar(50) database fields that store a lot longer strings than 50 characters.

YEah I didn't think that was the issue at all. Though Overnight I think I got it working.

I was deleting the source video before running the DB rename......I moved the delete to after the rename, and now it seems to be working. Perhaps it was checking both source and dest locations for the file?