google / spatial-media

Specifications and tools for 360º video and spatial audio.
Other
1.86k stars 429 forks source link

Documentation for running CLI metadata injector is confusing #86

Open bquandt opened 8 years ago

bquandt commented 8 years ago

The build docs are not in sync with the code. Trying to figure out how to make the cli version of this tool to report tags inserted into a previously processed file, can't seem to figure out how to make the tool do that.

dcower commented 8 years ago

Hi @bquandt, what issue are you running into specifically?

bquandt commented 8 years ago

Build instructions on github, executable/script file name are not in sync with the actual code.

In short the github build instuctions really are more misleading then much more.

On Thu, Jun 2, 2016 at 5:19 PM, Dillon Cower notifications@github.com wrote:

Hi @bquandt https://github.com/bquandt, what issue are you running into specifically?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/google/spatial-media/issues/86#issuecomment-223459908, or mute the thread https://github.com/notifications/unsubscribe/ADgIn5YPv0SZ3PxKy17Uh48kvsVlBehKks5qH3MsgaJpZM4IlErG .

dcower commented 8 years ago

I think the issue you might be running into is that you're running the script from the directory containing __main__.py, rather than the directory above it; i.e., python spatialmedia should be run from the directory containing the directory spatialmedia. We have a small blurb about it, but I agree that it's confusing as is.

Thanks for bringing up the issue. I'll take a look at what we can do to simplify the documentation.

dcoffey3296 commented 8 years ago

Agree on confusing but this thread is very helpful thanks!