-
Notifications
You must be signed in to change notification settings - Fork 41
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
Wallop getting 404 - Stuck on "Preparing Stream" #27
Comments
It looks like your ffmpeg build doesn't include the appropriate AAC encoder. Try building from source or what's in the repo to get a good build.
|
Thanks! I forgot the parameter "--with-fdk-aac" when installing FFMPEG through BREW |
Great! Working now?
|
Yes and loving it! Question, is there a way for Wallop to see more than one HDHOMERUN Prime? |
Not right now. Thanks for reporting back.
|
Not sure what I'm missing, getting the same results on two different MAC installs:
Here is the log entry from the FFMPEG log:
[mpeg2video @ 0x7f951b83fa00] 0x0 is invalid
Last message repeated 4 times
[mpegts @ 0x7f951b806600] max_analyze_duration 2000000 reached at 2002000 microseconds
[mpegts @ 0x7f951b806600] Estimating duration from bitrate, this may be inaccurate
Unknown encoder 'libfdk_aac'
Terminal display:
127.0.0.1 - - [19/Jan/2014 11:35:41] "POST /channels/3.1/tune HTTP/1.1" 200 29 0.0012
127.0.0.1 - - [19/Jan/2014 11:35:41] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0008
127.0.0.1 - - [19/Jan/2014 11:35:41] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0007
127.0.0.1 - - [19/Jan/2014 11:35:41] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0007
127.0.0.1 - - [19/Jan/2014 11:35:42] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0007
127.0.0.1 - - [19/Jan/2014 11:35:42] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0007
127.0.0.1 - - [19/Jan/2014 11:35:42] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0007
127.0.0.1 - - [19/Jan/2014 11:35:42] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0008
127.0.0.1 - - [19/Jan/2014 11:35:42] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0007
127.0.0.1 - - [19/Jan/2014 11:35:42] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0007
127.0.0.1 - - [19/Jan/2014 11:35:42] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0007
127.0.0.1 - - [19/Jan/2014 11:35:43] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0011
127.0.0.1 - - [19/Jan/2014 11:35:43] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0007
127.0.0.1 - - [19/Jan/2014 11:35:43] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0008
127.0.0.1 - - [19/Jan/2014 11:35:43] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0007
127.0.0.1 - - [19/Jan/2014 11:35:43] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0007
127.0.0.1 - - [19/Jan/2014 11:35:43] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0007
127.0.0.1 - - [19/Jan/2014 11:35:43] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0007
127.0.0.1 - - [19/Jan/2014 11:35:44] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0007
127.0.0.1 - - [19/Jan/2014 11:35:44] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0007
127.0.0.1 - - [19/Jan/2014 11:35:44] "GET /channels/3.1/status HTTP/1.1" 200 88 0.0007
127.0.0.1 - - [19/Jan/2014 11:35:44] "GET /channels/3.1/status HTTP/1.1" 404 - 0.0006
127.0.0.1 - - [19/Jan/2014 11:35:44] "GET /channels/3.1/status HTTP/1.1" 404 - 0.0016
The text was updated successfully, but these errors were encountered: