I have a workflow that downloads a video using the YouTube processor. I noticed in the work folder that the processor writes the .info.json for the YouTube video.
I looked at the documentation and what variables there are to access the work folder, but with the filenames being seemingly random, I have no idea how to access the file name that looks like this: ~20211004-110402-646-63941528b643.info.json.
Is there some way to access this file so that I can use the $jsonget function to populate variables from the JSON data?
Parse JSON Info From YouTube Processor
Re: Parse JSON Info From YouTube Processor
Hey sunkast, good to read from you again!
Unfortunately the info.json filename cannot be foreseen, it is a Unique ID generated by the youtube processor.
Fortunately, the youtube proc is the only one that uses ".info.json" as file suffix. So unless you have multiple youtube downloads in your workflow you have an easy time to just search for *info.json files in the job work dir and just work with the first found file.
Attached an example workflow, be aware this one uses a little helper plugin processor "files find", you must download and "install" from here: https://www.ffastrans.com/wiki/doku.php ... processors
Also, be aware that when using the yt proc with manual submission, you need to submit the link file from harddisk (just as when using with monitor folder proc), you cannot submit just a raw youtube url.
Unfortunately the info.json filename cannot be foreseen, it is a Unique ID generated by the youtube processor.
Fortunately, the youtube proc is the only one that uses ".info.json" as file suffix. So unless you have multiple youtube downloads in your workflow you have an easy time to just search for *info.json files in the job work dir and just work with the first found file.
Attached an example workflow, be aware this one uses a little helper plugin processor "files find", you must download and "install" from here: https://www.ffastrans.com/wiki/doku.php ... processors
Also, be aware that when using the yt proc with manual submission, you need to submit the link file from harddisk (just as when using with monitor folder proc), you cannot submit just a raw youtube url.
emcodem, wrapping since 2009 you got the rhyme?