-
Notifications
You must be signed in to change notification settings - Fork 10
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
Error: expected frame header but was not found #193
Comments
Cool! I'll have to hunt down where this is throwing. |
Seeing the same problem after pulling down latest master. Tried clearing out old configs too. Will try to figure out how to get it working again this evening. |
I'm pretty sure these are just logged as warnings. If you are doing a large scan, wait it out a few mins as 15k tracks can take a few mins. We need to improve the feedback that something is actually happening, and provide a partially updated interface ideally. For now though, this shouldn't be a total show stopper. |
Ok I will give it another try and leave it running. |
Ok I just let it run for over an hour. I got the main process error right away again. No sign of anything happening in the UI, though nothing seems to be frozen. No errors in the renderer console. |
It shouldn't take over an hour, only a few mins in my runs. I'll poke at it! |
I let it run all night for good measure. No noticeable changes. |
Sounds like its getting hung up somewhere. I'll improve the feedback of the scanning process and maybe it will help track down the source of the hangup. |
Definitely not just logged errors. The error halts the scanning process. Coming from a returned callback in musicmetadata |
I have a feeling metadata parsing (end eventually editing) is going to be a gigantic only-partially solved problem in JS land. |
cc @0x00A :) |
Quick fix: Just handle the errors slightly differently. The metadata scanner seems to fail in a number of unknown ways still that we need to sort out at some point. Fix lives in the HEAD of master right now: 5ded061 If you have time, give it another shot. If you are running from the cli, you will see scanning progress logs during the scan. We probably want a log viewer in the main window that shows errors and progress detail updates. |
Also, I just noticed we are using the less robust metadata parsing library in the main music scan ( This will require a bit more research. |
Okay I just pulled latest master, But then.. It hangs. The last file is:
A song which I'm embarrassed to say I don't know by name. Checked it out and it's only 4K and won't play in macOS Finder thingy. Here's the mp3 itself: https://cloudup.com/cfhoTNipZDU Deleted the file and starting again. So far so good... |
🎉 |
Hrmm... weird.. Perhaps a set-timeout is needed. EDIT I see its right there. |
Does cloudup have copyright / contentID? |
@ungoldman will you try again too? |
@bcomnes just tried, works for me now. 🎉 There's no visual indication that it's scanning outside of logs though, we might want to throw a loader in for now and maybe have some more interesting feedback on scanning in progress later. edit: looks like you already noted that here: #192 (comment) 💯 |
Also clearing out previous config seems to help from time to time. Related PR: #198 |
Thanks for the data points everyone :D I landed #198 and I think we should also have a front-end button to reset the config, essentially as a low-rent migration script users can run from the front-end. Will open that soon. As for scanning feedback I opened: #192 I was thinking that one step forward on that would be to merge the + and the gear icon, and when scanning, have the gear spin, and stop when its done. |
Closing in favor of #185 |
I see this in the main console when I try to import my music directory:
The text was updated successfully, but these errors were encountered: