Can you please share ...

• ... your voukoder logfiles (with low-level debugging) Where do I find the log file?
• ... screenshots of the issue

Robert Niessner

This is a very interesting approach.

When using the Reaper model VoukoderPro could even still be OpenSource (GPL) and I could ship it with x264/x265 encoders.

Companies would still have to obtain commercial licenses otherwise they'd violate their own compliance rules.

Can you guys please test if Voukoder 13beta1 fixes the 24bit audio issue?

[11:06:25] Timebase:        529191533/-1841018880 (-3.48 fps)
[11:06:25]   FFmpeg: The encoder timebase is not set.

Selecting the proper frame rate in premieres export dialog should fix this. Auto detecting the framerate was not successful.

Please provide a voukoder lofile with low level debugging enabled.

Thema

Where do I find the log file?

Main log file

The main log file contains all log data for one single day:

• Voukoder initialization
• All exported files

These log files are located here and will remain for 7 days:

(Quelltext, 1 Zeile)

The files are named by the ISO date (yyyy-mm-dd).log:

Export specific log file

If you have "Create log next to the export file" enabled you can also find it - well ... - next to the exported file. This log file contains only the export relevant information.

Low level debugging

Sometimes its…

Vouk

20. April 2020 um 14:57

Release Notes

This is a BETA version and not intended for production use!

Make sure you are using the latest connector for your application(s). For using NVENC (SDK 12) encoders driver version 522.25 or later is required.

Fixes / Changes

• Using FFmpeg build from master branch 20230228
• Encoders
  • libx265: Presets updated (iAvoe)
  • Intel QSV
    • Switch from MFX to VPL
    • AV1: Added the AV1 encoder

Credits

Thanks to my all supporters by either Ko-fi, PayPal or Patreon. Also thanks alot to the translators.

Top Patrons

Todd Scarbrough, Gronkh, Schauerland, Kleinrotti, Chris Woods

Good to know that Elements is basically working.

When FFmpeg 6 is out i'll make a new voukoder release with it. That should improve working with intel qsv encoders. (and add AV1 support), just waiting for the FFmpeg 6 release. Voukoder is already prepared for it.

I haven't tested this for a couple of years with Elements. I don't even have a copy of elements anymore for testing.

Do you experience issues with DVR and Voukoder too? Please post details in this thread.

I'm investigating this issue ...

The filter engine already works and is quite powerful in this graph based config. As you can see above it'd be possible to create one mp4 with different video/audio tracks where different filters (i.e. resolutions, subtitles, etc...) are applied. And that all with just one export.

Please uninstall voukoder, download 12.2 again and install it again.

I never understood why lossy and high compressed formats became so popular as intermediate codecs. Yes, they save space and money but it's a pain to edit and work with them. Imagine to work with MagicYUV or ProRes ... scrubbing is so much with these codecs. Once cutting is finished export them as h264 or AV1 as the final file.

People have already asked me why Premiere can't import AV1. It'll be even worse to work with it ...

Zitat von Couleur

One thing you could do is release versions early for your Patreons

I have had this idea a couple of years ago too. But it didn't work out to get more patreons that way. Basically just because the pre-releases still had bugs and required testing. So people thought "Okay, I have to pay and then I get untested stuff which I can't use?" Plus, the more people testing these versions, the more feedback I get.

Zitat von Joe24

So it's not viable for VP to use the x264/x265 libraries ONLY if they are present in the FFmpeg build? (Which would only happen if the user has chosen to download and compile their own version of FFmpeg, manually enabling these encoders.)

That'd be a way yes. FFmpeg as LGPL will be located as DLLs in the VoukoderPro app directory. But who would be able to do so?

You have to choose the pixel format in the encoder settings, i.e.:

For x264 you can try this to set the all-intra mode:

With NVENC h264 it should be this:

It is not about FFmpeg. FFmpeg can be built as LGPL - no problems. It is about x264 and x265. This (L)GPL topic is quite complex. You might read more about this on the FFmpeg or x264 and x265 website.

Thank you all for participating and sharing your opinions and suggestions in this topic.

Zitat von Howard Vigorita

Why not solicit financial support from the commercial NLE companies who are benefiting financially from the added value your Pro plugin might add to their platforms?

Companies are currently behaving completely different in supporting me and Voukoder. My contact to the VEGAS Pro Team is actually quite good, and I even get free licenses for every new version of VEGAS Pro. Talking with Adobe is good, they did reply to my questions and were helpful in the past. And BlackMagic DaVinci Resolve ... they didn't even reply to my questions in their forums. So asking them for money is not an option in my opinion.

Zitat von Kleinrotti

Maybe a payment plan for companies which have more than a specific amount of employees?

Zitat von kalamazandy

I'm not a huge fan of the idea of costs based on total employees of a company, or even total revenue, because that creates huge limitations for people who work at a large place who's primary business isn't related to the software they are doing.

I feel the same. I'd rather like something simple and clear. And not all companies would like to share their revenues and other company details. And even if they do - How am I supposed to verify that information?

Zitat von rsmith02

I think paying to unlock full features is reasonable

Right, I think this would be the best solution.

So my current idea on this is:

• VoukoderPro "unregistered"
  • About the same features that you have with the current Voukoder
  • I still want private/home/small content creators to be able to simply encoder their videos for free
  • No water mark, time limit, frame limit or such crap
  • You can try the full version for like 14 or 30 days (not sure yet)
• VoukoderPro "registered"
  • Full Feature set and all the exciting new stuff (I have so many ideas)
• Voukoder
  • As it currently is
  • No further development as soon as VoukoderPro gets released

I'd like to give users flexible options like:

• Subscription model
  • Monthly low price (You'll always get the latest version with all features)
  • Software stops working if you cancel your subscription
• Fixed price (classic model)
  • Classic one time payment
  • Just for one major version number (Updates for this major version number are included)
  • Release cycle will be one year
  • This software version continues to work for youeven if there are new versions

Making VoukoderPro (partly) commercial would also have some significant implications:

• Licensing
  • I need a monetization provider
    • Accepting payments worldwide
  • I'd have to add license verification logic
    • Maybe there are LaaS provider platforms like Steam for Apps, Windows Store, etc?
• It can't be GPL / OpenSource anymore
  • FFmpeg needs to be compiled as separate LGPL libraries
  • GPL parts like x264, x265 can't be included
    • Or I have to buy a commercial license for both (Quite expensive - I've heard about min. 10k EUR for x264 alone)
    • Or somehow work with x264.exe in a separate process
• Old financing stuff
  • Website ads will be removed
  • Patreon will be removed
  • The registered app will not contain any asking for payments
  • I might keep one-time payment services like PayPal or ko-fi for people want to show their appreciation for the free version
• FFmpeg
  • If this works out I'd even like to donate a share to the FFmpeg guys (and other free projects I'm using). Without their amazing work Voukoder and VoukoderPro wouldn't be possible.

All the above are my current thoughts. Final decisions might be different.

What encoder exactly? Currently there are four h264 encoders in Voukoder.

Is there a visual difference if you compare the files exported with crf=1 and crf=51?

Normally you can get this by setting the "key frame interval" to 1. In FFmpeg this is the "g" parameter. The name might vary with different encoders.