You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Difficulty finding executable, and not parsing folder name #1
I'm really sorry about this, I haven't taken the time out in my job to get my head round accessing githubs repositories or development structures, so this issue is probably mainly about my inadequecy!
From what I have found the executable found in PanoptoScheduleUploader.UI/bin/debug is the only one which is working for me so far, however it is not for some reason parsing the CourseTitle/Folder name to the scheduler. Instead it is always looking for a Folder on our Panopto server called #Test. Otherwise it's working great - I am in a fix with a ton of classes to schedule so I'm happy to create this folder on our server, then move the scheduled recordings to where they belong, and be immensely grateful for your work in the process!
Am I doing anything wrong, am I looking in the wrong place for the executable? thanks, Will
Other executables:
PanoptoScheduleUploader.UI/bin/release - only takes XML file selection, authenticating and finding folder ok, but returns with error description 'Pagination.MaxNumberResults must be equal or less than 1000'. Only gives this when found an existing folder
PanoptoScheduleUploader/Obj/x86/Release - does nothing on my machine
PanoptoScheduleUploader/Obj/x86/Debug - does nothing on my machine
Hi Panopto, no frustration just part of the process!
I downloaded the new version, updated the server information in the various config files and it is now working like a trooper! So very happy with this, and has allowed me to do what would normally take me a week in one afternoon.
It would be great if in the future it allowed optional setting of the 'Availability Dates', as this is quite a repetative thing here as we basically set it to two days after the event in all cases, so would save a lot of time if we can do this calc in Excel and be able to instate at time of the batch scheduling. Do you think this would be possible to implement in the future?
I wish I had the coding skills to contribute my self!
Many thanks ans best wishes, Will (Liverpool School of Tropical Medicine)
Hi Panopto,
I recently ran into the same issue with the #Test folder not being on the server. I replaced the #Test with the real folder name in the code and it worked but that is not sustainable for large amounts of scheduled recordings. I used both the executable in the debug and release folders with identical errors. I just downloaded the source files yesterday, so I can only assume I have the latest updates.
Hi Jenn,
Yes I did include the Folder Name in the csv file. I did delete the headers
out of Row #1 on the csv file. I thought I read that the headers would
conflict with the process.
Your best bet would be to include the folder in the input file for each
row. Is that an option in your case? That is what we would expect for cases
with many scheduled recordings.
Activity
wmoindrot commentedon Feb 2, 2015
Hi Panopto, no frustration just part of the process!
I downloaded the new version, updated the server information in the various config files and it is now working like a trooper! So very happy with this, and has allowed me to do what would normally take me a week in one afternoon.
It would be great if in the future it allowed optional setting of the 'Availability Dates', as this is quite a repetative thing here as we basically set it to two days after the event in all cases, so would save a lot of time if we can do this calc in Excel and be able to instate at time of the batch scheduling. Do you think this would be possible to implement in the future?
I wish I had the coding skills to contribute my self!
Many thanks ans best wishes, Will (Liverpool School of Tropical Medicine)
larryhess commentedon Mar 25, 2015
Hi Panopto,
I recently ran into the same issue with the #Test folder not being on the server. I replaced the #Test with the real folder name in the code and it worked but that is not sustainable for large amounts of scheduled recordings. I used both the executable in the debug and release folders with identical errors. I just downloaded the source files yesterday, so I can only assume I have the latest updates.
Thanks,
Larry
larryhess commentedon Mar 25, 2015
Hi Jenn,
Yes I did include the Folder Name in the csv file. I did delete the headers
out of Row #1 on the csv file. I thought I read that the headers would
conflict with the process.
Thanks,
Larry
On Wed, Mar 25, 2015 at 12:27 PM, Panopto, Inc. notifications@github.com
wrote:
Larry I Hess Jr.
Owner, Larry Hess Photography and Design LLC
304 532 2513
Larry Hess Design http://www.larryhessdesign.com