Many of you are starting to try out the workflow for creating a Direct Publisher channel. The core requirement is that you have a well formed MRSS or JSON feed that lists all your content.
I need one for 24/7 radio stream so I can convert my channel. And, how / where to save JSON file and get URL.. How to add it it to amazon server?.. Need help on it and 9 more channels…ugh
Have mercy…
“RokuChrisT” wrote:
Many of you are starting to try out the workflow for creating a Direct Publisher channel. The core requirement is that you have a well formed MRSS or JSON feed that lists all your content.
Hope this helps!
Hi RokuChrisT:
I have to apologize in advance because I’m angry and frustrated at how much information is missing regarding using direct publisher. It says in several places that it takes only minutes to create a new channel without having to write ANY CODE. REALLY?? A direct publisher feed JSON file isn’t code? If this was possible without having to write any code, there would be a web-based fill-out form where you simply enter in title, credits, link to media, etc., and the web-based function would return to you a complete JSON file. But NO WHERE is there any mention of having to set up folders on remote servers, such as Amazon S3, and having links to those folders, and permissions, et. al, before you can actually create a channel. The channel creation flow you reference here is virtually useless because it doesn’t provide ANY INFORMATION on how to create a JSON file. It doesn’t EVEN say that you have to cut and paste each of those sections together, or any information on the best way to do that or that you have to create that file and then host in on a server somewhere, and… the list of omissions goes on. I’ve been using the instanttvchannel.com service for a couple of years now, and wanted to move away from them and the monthly expense for just hosting my script, but they at least provide a fill-in-the form function that not only creates the proper file, but also packages it and all I have to do is upload it to ROKU.
Again, I’m sorry for being so angry, but to me, the emperor has no clothes, especially when it comes to the claim that no code-writing is involved. Am I just missing it, or is there really a major component missing here on how to create a JSON file… AND, having to go into a text file and enter URL paths and file names, and uploading those files to a remote server isn’t considered coding? The documentation, in my opinion, is severely lacking in all respects, and is misleading in the “you can create a channel in 15 minutes” verbiage. Sure, you can create a channel by copying and pasting the provided JSON file, and uploading the provided art placeholders, but that’s not creating a channel. The channel creation came when the JSON file was written in the first place as that is really the “channel”.
Again, apologies for the rant, but I have many channels to create, and it appears that I’m going to have to pay an outside service to create files, unless there’s a hidden instruction file on the developer site somewhere that has a step by step of how to create a JSON file in the first place, with the instructions required for how to link to an Amazon S3 server, for example. The beginning and end are there for channel creation, but the missing link for me is the most crucial: creating feed files.
Any help you can provide is of course much appreciated. I’d like to hear from other developers who may be sharing my frustration.
Thanks,
Ken
I too was thouroughly confused when I first started. I know a bit about web design and code, but JSON was unfamiliar to me. I seemed way in over my head. However, I disagree with part of your sentiments, as just “replacing links” was really all I was looking for. I don’t find that actual “coding”, but all I was asking for was a sample template.
What’s not mentioned in the tutorial is that all you need to do is copy the mumbo jumbo text/code from their sample feed: https://api.myjson.com/bins/4tu28 and paste it into a JSON validator like here: http://jsonlint.com/ and it nicely formats your code for you. All you then need to do is replace the names, descriptions, IDs, and mostly the video link URL. Just getting a URL should be pretty easy, I can’t see how Roku could find it video any other method.
After all, let’s not make it too simple. Gotta hope Roku can seperate the wheat from the chaff, otherwise it’ll turn into YT.
So I can add all of the info for the channel into one json file and put it on my server and then use the url to that one file, correct? I don’t need to make a json for each category, genre etc? What about saving the JSON…“encoding” should it be the utf-8?
And Ken, I too have been feeling frustrated. I wanted to learn what to do but couldn’t find the missing pieces.
Yes, all the categories and video urls, etc., are in one file. Here is my channel with three categories using the TV Specials object. See the categories/playlist at the bottom of the file. http://hproku.s3.amazonaws.com/JSON/content-feed.json
I do mine in dreamweaver, so I dont have to choose one of those but I am sure that will work. Also, remember when you upload your file to AWS, switch back to the old console and change your metadata to content-type and then type in “applicatiom.json”
I’ve been using Cloudberry to access the aws. It has made the process for the other channels I made a lot easier. Not sure how to do the metadata change you mentioned..Do you mean on the server or in the json file itself? I’ll have to look into that part.
EDIT: Just looked up info for changing content-type using cloudberry and they have a tutorial in case it helps anyone else. I have not attemped it yet but looks like a good tutorial.
I would try just pasting it into Notepad if you don’t have any coding software. Eclipse or Notepad++, free software should work as well. Anyway one novice coding thing to look out for, if you copy & paste video sections to make more, please note that the last video in the list cannot have a comma after the last }] bracket. All others will end }], meaning more to follow, so they need the comma. However I ran into “Invalid JSON” on my first due to still having a comma in the last one, with nothing more to follow. Beginners mistake:)