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.
Last post by sveakul -
Thanks oops. Yep, "using a single instance of VU Meter in DUI on x64 in light mode" is me also . I'm at .91 currently with absolutely no issues; will be interested to see what this was about before taking the leap.
Last post by daveb30 -
Thanks for the Windows command Porcus. I have a Linux machine and a Windows. I am trying to get off of Windows so I jumped onto my Linux box, and SimBun's code works like a charm. But thanks for this... Next time I fire up my Windows box I will give this a try. Thanks
I have become lost with the latest succession of rapid-fire updates. It has become impossible to tell if some are purely in response to a test requested by a poster trying to get something to work in a "niche" fashion specific to them, and those that are general updates supplying fixes and changes relevant to all. I don't use CUI or on-the-fly color changes, exotic loading/splitting techniques or special forms of transparency. What is the latest version that does NOT include personalized experimentation??
For those regularly requesting the plugin to be altered to fit specific uses, why not offer a "development version" of the plugin that contains responses to their requests from a separate "nightly build" source?
As I said above, I'm very happy with the development of the component. The code base is stable at this point, many of the major problems have been hashed out and I don't think there will be any large changes going forward. In fact, most of the changes I outlined in the last release notes are less than 10 lines.
With that, I'm with you on a lot of it. I don't use CUI or fancy anything, personally. All of the requests are "niche" at this stage. But we are all evolving the component together. And part of the fun is seeing people's creative set ups and marveling at how far they push the component. But be aware, there is no version I've released that is not experimental in some way as I'm not a corporation with a professional dev team verifying and reviewing the updates (and as I've stated before, this project is a learning endeavor first-and-foremost).
I simply do not want to spend the bandwidth to offer anything beyond what is in my "master" branch or write yet another script to publish the CI builds.
One last thought. Basic functionality will likely not break because my post-build hook copies the current build DLL over the existing one in my copy of the music player. So, if you're using a single instance of VU Meter in DUI on x64 in light mode, you are using what I do and dogfood daily. But as we've learned, if that was all the component offered, non-stop complaints and wishlists flood this forum ;)
Last post by Porcus - grep does not work in Windows out of the box? (Mine is gnu'ed up a bit, so I do have grep here, but I don't think that's default command. From the directory backslashes I presume it is Windows.)
The | ("pipe") sends the output to the next command.
The next command, findstr (or grep if you have that) is a string finder. /B finds it only at beginning of line, /E finds it only at end of line, so that means you are searching for a line that is "SongRating=" and nothing before or after; /V means to invert it, so to return every line that does NOT match.
If you are familiar with regular expressions, then findstr supports that as well, if you give the /R switch. Then it would be findstr /R /V "^SongRating=$" which closely matches the grep command suggested. In regex speak, a sole "^" means beginning of line and a sole "$" means end of line. The problem about regular expressions is that you need to know that there are special characters, so if all you need is "this is the entire line" then /B /E is just as good.
Then piping what grep/findstr found (namely the whole shebang except lines that are exactly "SongRating=") on to the next command. Which is another metaflac, that removes all the tags and imports the tags from "-" which is the standard input it was sent by the command before the pipe.
And yes, whitespace after "-", and sure you can use whitespaces around | too.
Last post by isidro -
From SOX manual: All resamplers use filters that can create artefacts with transient signals like highly percussive sounds. Are more noticeable if they occur before (‘pre-echo’) than if they occur after it (‘post-echo’). A phase response setting control the distribution of any transient echo between ‘pre’ and ‘post’: with minimum phase, there is no pre-echo but longest post-echo; with linear phase, pre and post echo are in equal amounts; intermediate phase setting attempts to find the best compromise by selecting a small length (and level) of pre-echo and a medium lengthed post-echo.
Mastering engineer Daniel Ovie tests found out that it's perceptible and the least disturbing setting is Intermediate instead of the default Linear. As for dithering, 18bit implies s/n of 108dB, usually everything below that is noise, with dithering some of the two folowing bits is included. My usual setting (run from a BATCH file) for processing all WAVs in folder is:
I'll leave it with you, nothing more I can test about it. Keep me informed.
Thank you so much for testing this out! I found the problem. It was due to my misunderstanding of Win32 window styles. Fixed. Not painting the transparency in fullscreen, but it is not lost in window mode after fullscreen or resizing. Also, fullscreen will be reenabled fully in Columns UI regardless of the configuration or parent container. Pseudo-transparency in JSplitter not tested.
For those looking for a working implementation, here it is. Be aware that the order of the operations is absolutely critical:
I'll leave it with you, nothing more I can test about it. Keep me informed.
Thank you so much for testing this out! I found the problem. It was due to my misunderstanding of Win32 window styles. Fixed. Not painting the transparency in fullscreen, but it is not lost in window mode after fullscreen or resizing. Also, fullscreen will be reenabled fully in Columns UI regardless of the configuration or parent container. Pseudo-transparency in JSplitter not tested.
For those looking for a working implementation, here it is. Be aware that the order of the operations is absolutely critical: