Skip to main content
Topic: foo_midi (Read 25529 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: foo_midi

Reply #175
You can try a quick dirty hacky component http://www.saunalahti.fi/~cse/temp/foo_dyndec.fb2k-component. It exposes the dynamically changing fields you need in %dartist% and %dtitle%. Probably best to use with some if function wrapping, something like $if2(%dtitle%,%title%).
Hi there!
@kode54, @Case,
if the foo_dyndec component is installed, then playing any midi file will crash of fb2k if the syxg50.dll VST-plugin is set.
Please see how this can be fixed?

Re: foo_midi

Reply #176
The crashing is probably my fault. I noticed in the documentation that the function rendering the string can be called from multiple threads and I had not taken that into account. New version with appropriate protections uploaded to http://www.foobar2000.org/components/view/foo_dyndec.

Edit: changed the link.

Re: foo_midi

Reply #177
Hi kode54, is it possible to add a never looping mode with adjustable decay time or lowest volume threshold after the last note ended? 1s decay time still chops off a lot of MIDI files.

Re: foo_midi

Reply #178
I can make it do an auto decay search pattern once the file has ended, but I'll have to do this a bit later, as I need to set up my dev environment again.

Re: foo_midi

Reply #179
Thanks!

Re: foo_midi

Reply #180
"MIDI Player 2.2.12" has a new error which upon opening the respective Options page for foo_midi it just stalls and crashes Foobar2000 entirely.
No error popup either, just the generic (Not Responding) text above most Windows titlebars.

EDIT: Upon removing my respective VSTi path it now works, It would be nice to still have that VSTi support though.
Furthermore with these tests, it seems any VSTi will crash the options page now, as I have singled out many of them from 3 to 1 different VSTi's within the respective folder of choice.


Re: foo_midi

Reply #182
I was advised to remove a message pump from my pipe processing loops, which were in place for both VST instruments and the Secret Sauce. This message pump was causing one of Case's input wrapper components to crash.

I need further input from Peter for what to do, since this message pump is 100% necessary when the pipe interaction happens in the main thread.

Edit: I've fixed at least a possible cause for indefinite hangs. It will still hang while scanning, and while displaying an instrument's configuration/editor dialog, but it won't hang indefinitely like it did for that brief release. Still waiting on a proper solution.

Re: foo_midi

Reply #183
Edit: I've fixed at least a possible cause for indefinite hangs. It will still hang while scanning, and while displaying an instrument's configuration/editor dialog, but it won't hang indefinitely like it did for that brief release. Still waiting on a proper solution.
Completely fixed thank you very much, amazing work as always!
It's doesn't even "still hang while scanning, and while displaying an instrument's configuration/editor dialog".

Another note: "Skip to first note" option actually changes the VSTi instruments of certain songs.
Although I like this change, I understand if you wish to fix this.

 

Re: foo_midi

Reply #184
thank you Kode54, how about supporting Steinberg HALion Sonic 3, foo_midi doesn't want to see that marvelous VSTi plugin. Belive me HALion Sonic is the best of the best. I tried many of them and I know that for sure.
I recently discovered it for myself and was simply amazed how my midi files sounded now. It allows you to customize any instrument as you wish and assign any effects you want for each of them separately.
You can also download tons of different professional instrument or create them by yourself and assign them status of general midi, and they will be loaded automatically when midi plays.
You can achieve sound comparable to professional soundtracks if you spend enough time and tune them all.

thank you! please don't ignore my message.

 
SimplePortal 1.0.0 RC1 © 2008-2020