-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not find recorder #183
Comments
I can think of a couple of things that might cause this. One is that the time intervals specified for your archive's device connections may not include the time interval of the recording you are trying to import. If so, you can fix the problem by editing the relevant device connection with the Django admin interface, at 127.0.0.1:8000/admin, and, say, extending the connection's time interval. Another is if the string "MSGR" is an abbreviation for a longer station name that's in your archive database, but your station name aliases preset does not map "MPGR" to the longer name. If that's the case, you can edit the preset in a text editor to map the longer station name to the abbreviation. In either case, be sure to restart the Vesper server after making your edits. I plan to simplify the way Vesper handles devices and recording imports for Vesper 0.5.0, due later this year. One of the main goals of the changes will be to reduce the number of configuration issues that users encounter, both when creating an archive and (as in your case) when using one across multiple years. |
I think you're right about the time intervals! Changing it in the admin interface fixed the problem. Thank you, Harold. Might be good to add that to the warning? |
I'm inclined to close this issue since you found the source of the problem. Is that okay with you? |
Works for me. Thanks, Harold. |
This is probably more of a user support issue than a bug, but Vesper couldn't find the recorder for me recently. I don't think I changed anything in this archive, so I am rather confused by this. I'm still on 0.4.8.
Log:
The text was updated successfully, but these errors were encountered: