Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Is there any reason to stick to multiples of 16/32 for target bitrate in opus encoder or does it not matter? I noticed qaac/Apple AAC forces 112-128-160-192 etc.
Unless it's a special use-case which also requires hard CBR, it does not matter.
Last post by Case -
I did some benchmarking and GCC's fprintf takes 100 times longer even here compared to MSVC's or clang's function. Attached is a patch that changes progress printing to use WriteConsole on Windows when stderr isn't redirected to file. That gives consistently fast progress display on all compilers. I also noticed that stopping encoding by keyboard press didn't work when not compiled on Visual Studio, fixed that too.
I also changed the progress printing to happen 4 times less often than originally. I think maikmerten's progress update happened too seldom, it looked buggy when it was so sluggish.
I hope @KevinB52379 can test this and report if things now work correctly.
I'm still working on it. But I need more time than expected because I decided to use OpenGl instead of GDI+ and therefore a large part of the code has to be rewritten. But OpenGl is much faster than GDI+. So it's worth the effort. So far I have been able to solve everything. Here is a current picture of the component. [attach width=500 align=center]30325[/attach]
Very well presented interface, I'll keep an eye on it!
This one adds strings on exit and enables the dynamic stream info updates in the Log tab too.
The problems others have brought up recently still remain with this version--how can the log entries be date/time stamped (%datetime% is NOT recognized, unlike the original np_simple), and how can the entries be logged latest first instead of last??
The immediate solution for those with jscript panel3 is its Play Log sample as mentioned above, but it would be nice to see this plugin at least retain the functionality of its predecessor.
Last post by jdimsa -
Is there any reason to stick to multiples of 16/32 for target bitrate in opus encoder or does it not matter? I noticed qaac/Apple AAC forces 112-128-160-192 etc.
I would like to give the Microsoft Store version a try, but it seems there's only the x64 version available. Many of my components are still x86-only, so I can't switch to the Store version. Additionally, the latest version in the Store is 1.6.17, but I'd prefer to use version 2.x...
There's no such thing as version 1.6.17 x64.
Version 1.6.17 is available separately from the latest 2.x for people who need full backwards compatibility. It is still being updated with critical bug fixes (1.6.18 will be out soon).
2.x series is available in all CPU architectures, MS Store decides which one to install for you, depending on your system.
I'm sorry TF3RDL, but my primary goal is to increase the performance of the component. After I release the OpenGL version of the component, I will take care of your ideas. Probably not all of them, but may be a few :-) Thanks for your patience.
Oh ok, thanks for switching away from legacy GDI+ to something GPU-accelerated graphics API (probably one of many reasons why the next version of this component take too long to release), but the difference between Direct2D and OpenGL shouldn't matter performance-wise right?
And I understand that my ideas (e.g. IIR filter bank mode as well as adjustable number of bands per-octave for frequency bands mode) might take a lot of time to actually being materialized into this component and it makes sense to have fewer (and not all) ideas made into it