Skip to content
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

not properly working in windows #2

Closed
the-eater opened this issue Jan 30, 2014 · 12 comments
Closed

not properly working in windows #2

the-eater opened this issue Jan 30, 2014 · 12 comments
Labels

Comments

@the-eater
Copy link
Contributor

bugs found:

  • When scanning it loops infinitely through all the files
  • images and MP3's paths are resolved to "C:\C:"

I may have missed some things

@benkaiser
Copy link
Owner

What do you have the directory set to in your config.js file?

Do you know what could be causing this code-wise, it would be located in the library_functions.js file.
If you manage to figure it out feel free to clone my repo, fix the bug and submit a pull request.

@benkaiser
Copy link
Owner

It might just need a few path.join calls instead of using / characters. See the documentation here. It is not my highest priority supporting windows as it is not my main platform on any of my devices, I just use it for occasional gaming.

@the-eater
Copy link
Contributor Author

my dir is C:\Users\corné\SkyDrive\Musica by remove the { root: '/' } thingies I solved around 70% of them. I will try again to fix it >.> (cloned your repo already like 2 times xD)

@benkaiser
Copy link
Owner

What did you change the { root: '/' } thingies to? submit a pull request and it will all make sense then :)

@the-eater
Copy link
Contributor Author

I actually just removed them because if your path already starts with '/' linux will just call from the main '/' :)

@the-eater
Copy link
Contributor Author

the multiple looping error thing not found yet

@benkaiser
Copy link
Owner

Yeh I found that I needed to include it if the file I was serving was anything higher than the current directory. It was a think express.js did to protect users of your app entering urls of higher directories and hacking you apps, but in this case we have control of the urls so I used {root: '/'} to say we can go all the way up to root.

@benkaiser
Copy link
Owner

@Eaterofcode is there any other major problems that needed fixing on windows? or does it all work now?

@the-eater
Copy link
Contributor Author

I dont know, been busy with my own project, Im sorry

@benkaiser
Copy link
Owner

@Eaterofcode that is fine, if someone finds this thread and is interested they can create the patches needed for window support

@benkaiser benkaiser added the bug label Jul 14, 2014
@benkaiser
Copy link
Owner

Some logs when hard rescanning then reloading the page (perhaps the wrong location stored in file):

C:\Users\benkaiser\GIT\node-music-player>node app.js
connect.multipart() will be removed in connect 3.0
visit https://github.com/senchalabs/connect/wiki/Connect-3.0 for alternatives
connect.limit() will be removed in connect 3.0
Express server listening on port 2000
0 tracks deleted
C:\Users\benkaiser\GIT\node-music-player\node_modules\musicmetadata\lib\index.js
:66
    }, done, opts.hasOwnProperty('duration'), fsize);
                 ^
TypeError: Cannot read property 'hasOwnProperty' of undefined
    at Stream.<anonymous> (C:\Users\benkaiser\GIT\node-music-player\node_modules
\musicmetadata\lib\index.js:66:18)
    at Stream.g (events.js:199:16)
    at Stream.emit (events.js:107:17)
    at drain (C:\Users\benkaiser\GIT\node-music-player\node_modules\musicmetadat
a\node_modules\through\index.js:36:16)
    at Stream.stream.queue.stream.push (C:\Users\benkaiser\GIT\node-music-player
\node_modules\musicmetadata\node_modules\through\index.js:45:5)
    at Stream.write (C:\Users\benkaiser\GIT\node-music-player\node_modules\music
metadata\node_modules\through\index.js:14:43)
    at Stream.stream.write (C:\Users\benkaiser\GIT\node-music-player\node_module
s\musicmetadata\node_modules\through\index.js:26:11)
    at ReadStream.ondata (_stream_readable.js:540:20)
    at ReadStream.emit (events.js:107:17)
    at readableAddChunk (_stream_readable.js:163:16)

C:\Users\benkaiser\GIT\node-music-player>l^Nn^N

C:\Users\benkaiser\GIT\node-music-player>node app.js
connect.multipart() will be removed in connect 3.0
visit https://github.com/senchalabs/connect/wiki/Connect-3.0 for alternatives
connect.limit() will be removed in connect 3.0
Express server listening on port 2000
Error: ENOENT, stat 'C:\Users\benkaiser\GIT\node-music-player\Users\benkaiser\Mu
sic\soundcloud\smash_mouth___all_star_teddy_cream___mimmo_bootleg_.mp3'
    at Error (native)
Error: ENOENT, stat 'C:\Users\benkaiser\GIT\node-music-player\Users\benkaiser\Mu
sic\soundcloud\smash_mouth___all_star_teddy_cream___mimmo_bootleg_.mp3'
    at Error (native)

@benkaiser
Copy link
Owner

I fixed the above issues and now upon installing soundcloud downloading, scanning the library and most other features (except youtube unless ffmpeg is installed) should work.

If any other issues arise for windows please add them in their own issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants