Beiträge von deco

    I've still never gotten Adobe Media Encoder to work correctly with Pro, but I decided to whack my head against it again :) But that's for a different thread.

    I've been poking at youtubeuploader, which is a CLI tool to upload videos to youtube, and it seems to work correctly when invoked by Postproc nodes in the Designer. However, I don't see an obvious way to use individual file names in the process.

    My test setup is basically this: I've got a normal setup in a copied scene, so that I know the output file is fine; I can then add a Postproc node after the Output (file) node that runs youtubeuploader. The syntax for uploading is youtubeuploader -filename <filename>.mp4, which means I'd need to use the same generic name for every rendered video, since it's hard-coded into the Exec line in the Postproc node. While workable, I'd really like to avoid that, especially when I have a couple renders queued up!

    Before I whip up a script to guess & rename the video before upload, I just wanted to check to see if there was a built-in way to pass the variables from the Output node to the Postproc node(s), to save some trouble!

    What do you mean with full/full-shared and essentials builds?

    For reasons that aren't clear to me, they have an "Essentials" build and a "Full" build, that differ in what libraries they contain. Both of them are available as a either a monolithic static build (with all libraries) or a shared build, which uses, well, shared libraries, which are shared :) Sorry, I feel like I'm talking down to you...

    The full/full-shared builds contain everything possible; I didn't really look at the essentials builds, because I want everything :) I'm sure you have lots of concerns about licensing (and patents), so something like this moves that to a 3rd party. But, I'm not a programmer :)

    I really like scoop because a lot of Linux syntax has been imported. Some people have written a cross-platform implementation of most of core GNU utls and the various findutils, which makes my life wildly easier. Now I can finally use PowerShell :) I have no interest in learning to use actual PS, so this is great.

    I also really like the system of "zero"-installs, where everything is contained in one directory, Windows is not involved, and it just makes shims as necessary. Delete that directory if you don't like it, and it's gone!

    Rather than needing to maintain dedicated builds, it's actually really easy to keep up with the current ffmpeg versions using scoop (think, if Windows had a repository). It's stupid easy to install (two lines of PowerShell, as user), and you can track either nightlies or releases. For example, I like using the actual "releases", because I like nice round numbers, so all I have to run is:

    > scoop install main/ffmpeg-shared

    Ta-da! I think the automatically default directory is C:\<user>\scoop, but I don't remember if I had to add it to the PATH myself. Luckily, it's really easy these days. Then you can just run > scoop update whenever it crosses your mind,

    The only problem at the moment is that 8.0 was just released a few days ago, and Voukoder is expecting ffmpeg 7.1.1. I'm guessing that's a pretty easy fix, and aiming new users at scoop may be easier than compiling your own builds. Or, maybe not! :)

    (edit: this is actually the way that the gyan devs recommend installing pre-built shared binaries on Windows. Well, alternatively you could use win-get, if you want to really screw up your computer.)

    Agh, it's so close! I can see you took the time to work on the YouTube UI, and I appreciate it :) The UI works fine (amusing, sometimes the built-in ones don't, but switching to a Voukoder preset fixes it), however, sending it to "Media Encoder" or just directly "Exporting" it causes...nothing. The preview UI goes blank, and it just kind of sits there. Toggling to another preset and back fixes to UI again, but it's the same behavior. I've tested this with exporting just as a Media file, and that works perfectly, either direct or queued.

    Well, here's another fun one. When the "YouTube" destination of the Export tab is set to use a Voukoder Pro preset, the UI in the Export panel gets all screwy, as seen in the attachment. I just toggled between two presets, and you can see what happens. Very odd. Trying to use the "Send to Media Encoder" or "Export" buttons doesn't do anything. Everything renders out perfectly fine in the "Media File" destination, but one of the reasons I pay for Premiere is for huge Media Encoder queues.

    I'm not sure what kind of diagnostics you'd like? I'm not getting any errors, because it's not even making it to the moving parts, as far as I can tell. I've attached the scene (with an extra .txt extension), which is pretty simple, and the encoder profile in Premiere is basically the same.

    [ed: one of these days I'm going to create a thread that's not about bugs & problems...]

    Aha! It lives! Whatever you changed made it suddenly produce correct files! I did note that Premiere was previously adamant that my input FPS was 29.97 (instead of 60); once I'd finished screwing around, it identifies the actual timecode! (easiest to see in the preset settings, in the "Summary" window.) Thanks again for your help and work!

    [For future web searches] If anyone's curious, these are the settings I use. Bear in mind, this is for recorded gameplay -> YouTube. For the items in the Designer, the text in curly braces {} is what you should see in the bottom window:

    Premiere's presets are always a land of mystery and terror. In this case, best to pick a preset that already does x264, copy, and modify. That said, it's basically "Match Source" and the correct Scene.

    I've been beating my head against this wall for a couple hours now, so I'm just tossing this out for you :) First pictures, then error logs.

    So, I uninstalled the deprecated program & connector for Adobe Media Encoder, and installed v2.0.2 of the Pro version. The designer is really neat, by the way :) So. Here's my pain. This is Adobe Premiere/Media Encoder v25.1 (the most recent as of this post), computer is Windows 10 and gets along with Adobe suspiciously well.

    Virtually everything I do is YouTube uploads, hence some of the options (or I was too tired to click my mouse again). As you can see in the "Designer" file, I'm running video through libx264, audio through AAC, muxing them to MP4, then tossing it in the output folder.
    You can see the options listed in the "Video" file, encoding via LIBX264, basically stock. Generally I'd mess with it more, but I wanted to just do the bare minimum of changes. "Audio" is just straight-up AAC, CBR 320, low complexity. The MP4 output has the faststart flag set.

    And now the horror that is Adobe presets. I tried to capture most of it in the "Fill size preset" image (Premiere is being a bitch and adding "_1" to the end of all my presets). This is just showing that I'm not doing anything weird except that I forgot to set the framerate to 60 for the screenshot. The "Smaller preset" image is the Voukoder Pro tab, I just left the color options alone.

    And now, on to logs. Or rather, not much, because Adobe gives me fuck-all for feedback. The first time I was playing with it, I was getting:

    (I think the selector was the same number). The most helpful info suggested that "Exit Code 20 comes when he required files are missing in the installer", but I don't believe that. Reinstalled anyway, just in case, and now all I get is:

    This is just as helpful as you might expect.

    I need to go fix my back and get some work done, hopefully this is something fairly easy!