Skip to main content

Recent Posts

1
3rd Party Plugins - (fb2k) / Re: JScript Panel
Last post by marc2003 -
You generally don't see ActiveX errors with this component and any version of Windows unless something is really broken or perhaps something is interfering like an over-zealous security application??? Can you think anything just installed/changed recently?

What is the output of this script alone in a panel??

Code: [Select]
var arr = ['htmlfile', 'Shell.Application', 'WScript.Shell', 'Scripting.FileSystemObject', 'ScriptControl'];

for (var i = 0; i < arr.length; i++) {
try {
var obj = new ActiveXObject(arr[i]);
if (arr[i] == 'ScriptControl')
obj.Language = 'VBScript';
fb.Trace(arr[i] + ' tested OK!');
} catch (e) {
fb.Trace(arr[i] + ' not OK!')
}
}

Check the Console. I get...

Code: [Select]
htmlfile tested OK!
Shell.Application tested OK!
WScript.Shell tested OK!
Scripting.FileSystemObject tested OK!
ScriptControl tested OK!
2
If you want bulk encode with faac don't do it yet, better wait for upcoming releases.
Encoding improvements are underway.
3
3rd Party Plugins - (fb2k) / Re: JScript Panel
Last post by cFlavien -
Hi, from today I have this error :
Quote
JScript Panel (Menu Button by marc2003)
Erreur d’exécution JavaScript:
Un composant ActiveX ne peut pas créer un objet
File: E:\Ma LiberKey 5\MyApps\foobar2000\js_marc2003\js\helpers.js
Line: 45, Col: 1
<source text only available at compile time>
I have update with last version but same error
Quote
JScript Panel (Menu Button by marc2003)
Erreur d’exécution JavaScript:
Un composant ActiveX ne peut pas créer un objet
File: E:\Ma LiberKey 5\MyApps\foobar2000\user-components\foo_jscript_panel\samples\complete\js\helpers.js
Line: 560, Col: 1
<source text only available at compile time>
4
in the Opus encoder, in the advanced settings (Edit) - Display - Settings:, it always shows VBR for every setting
I can also see 'CBR' or 'constrained VBR' in encoder settings.
My English man ! ...what I mean is you only see VBR/CBR/constrained VBR and not the actual setting number or bitrate like all the other codecs are setup.
5
It doesn't apply immediately, the first step when scrolling, it using previous value.
Is it known issue/limitation? After that it works with the value on the advanced setting
Thank you for making it possible. Great :)
6
Just a bit wording concern. Change "Commandline" to "Command-line", Command-Line, or "Command Line" maybe?
7
WavPack / Re: bits/sample, kbits/second?
Last post by [JAZ] -
@j7n:   Oh... I see. You are probably right:  176000 /44100 = 3.99 (so, sample understood as individual sample, not as a sample frame)

8
It's a DSD512 DFF file (22 579 200 Hz / 1 bit). According to Rollin it was converted with WavPack 5, which is now able to losslessly compress DSD. And even if foobar2000 can't read DSD, the WavPack library automatically transforms DSD files to PCM at ultra-high resolution for compatibility reason.
It WAS DSD512 DFF file. Then it was encoded with wavpack, then it was decoded to PCM with foobar2000's native wavpack decoder. So, finally, it is simple PCM wav with 16 bit 2822400 Hz.

Anyway i am satisfied with response from Peter.
9
in the Opus encoder, in the advanced settings (Edit) - Display - Settings:, it always shows VBR for every setting
I can also see 'CBR' or 'constrained VBR' in encoder settings.
10
Regarding VS2017-
The foobar2000 SDK, version 2015-08-03 is compatible with the latest version of Visual Studio 2017 at this time - I just tested it myself.

There was a period in which Visual Studio auto updater would give you broken platform SDK which made lots of my code fail to compile due to Windows.h vs WinSock #include order issues. This appears to have been fixed on their end.

You can load foo_sample workspace into VS2017, retarget to the new toolchain (original projects are VS2010), optionally enable -XP version of the toolchain in project settings, enable /d2notypeopt as per this thread and you're good to go.

foo_sample demonstrates most commonly used parts of foobar2000 SDK, it's a good starting point to learn how the SDK works. Also don't forget to check the readme doc first, it has lots of essential info on SDK architecture.

Thanks for the help! There's lots of configurations in the foo_sample project that I found need to be copied over to any other plugin you're writing: the compiler option needed to be switched from /MD to /MT in my case - fixed issues when compiling. I also found out there's lots of plugins on GitHub whose code you can look through and get a grasp of what's going on, the foosion subdomain of foobar2000's website is also quite helpful even if it was originally written for the 0.9.x SDK.