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
Update to gui fixed the scrolling issue for me. Seems to connect and upload ok to our server. One thing worth mentioning is that the readme says about changing address attribute in PanoptoScheduleUploader.UI\bin\Debug, but to get work the user needs to do the same in the Release directory. This might be obvious for people who know what they're doing, not like me! As always it would be really really useful if we could set media availability dates through this tool at time of scheduling. Any chance in the near future?
The text was updated successfully, but these errors were encountered:
Cheers, for this additional info. Struggling to get this to work still. We have a ticket open with Panopto and are waiting on a response, but if you can give me any info that would help:
We use a moodle integration for authentication, does this work with this tool with that, or is a Panopto account necessary?
Should I be running the application from Debug, as per ReadMe, or in Release?
Is it likely we would need to get our central IT to configure anything, eg, to allow use of the services (*.svc URLS) this tool is hitting?
Are there any other omissions from the ReadMe I should be aware of (e.g. do all the references to the 192.169.#.# addresses in various *.config files need changed?)
Update to gui fixed the scrolling issue for me. Seems to connect and upload ok to our server. One thing worth mentioning is that the readme says about changing address attribute in PanoptoScheduleUploader.UI\bin\Debug, but to get work the user needs to do the same in the Release directory. This might be obvious for people who know what they're doing, not like me! As always it would be really really useful if we could set media availability dates through this tool at time of scheduling. Any chance in the near future?
The text was updated successfully, but these errors were encountered: