Help with rendering samplerates

[jmkz]

I have an issue with VST plugins and the samplerate. When I rendering to wave this (~800KiB) module in 44100Hz and then in 88200Hz Some VSTs sounds different. I'd like to know what I can do to get the results of the instrument 12 (at 88.2KHz) rendered at 44.1KHz.

Instrument 12 @88.2 has a shorter:?: fadeout sound as I like to be.

The final saved samples:

44.1KHz (~3MiB)
88.2KHz (~8MiB)

[LPChip]

I've experienced this in the past too.

The reason was that the internal mixing rate of that particular vst is not processing it right (aka, a bug in that particular plugin).

Basically, that vst is not following the VST SDK design specs. (if my memory serves me right, that is what was the case)

I solved it by updating the plugin to a newer version that did fixed it.

[jmkz]

Thanks for the reply, it was a little annoying but anyway there is nothing to do other than update unless if I found it.

[Saga Musix]

Have you tried closing the module, then changing the player's mixing rate and then opening the plugin again and export it at the same mixing rate? That should work in most cases.

[Nahkranoth]

djmakas, there are plugins (mostly old ones) that can work only with certain samplerates. I remember playing with ReFX Slayer and it sounded normal only on 44,1 hKz. I'm still waiting for VST resampler that will solve the problem, but it won't happen anytime soon.

[jmkz]

Have you tried closing the module, then changing the player's mixing rate and then opening the plugin again and export it at the same mixing rate? That should work in most cases.

Yes, I also tried this, but I'm asking if there's another way to get the "accelerated" sound for the instrument 12 at 88.2KHz. Maybe is possible without edit the final song to add the desired 'accelerated' fragment with Audacity or other program.

And as final, is there anything I can do that when you double click to open a module in the same instance? I think this would be a practical feature IMO. (I don't known if actually is possible)

[Saga Musix]

And as final, is there anything I can do that when you double click to open a module in the same instance? I think this would be a practical feature IMO. (I don't known if actually is possible)

what?

[jmkz]

This is related with the new installer of OpenMPT, the associations. By opening one file once a time, they open in a new instance of OpenMPT. This consumes a lot of memory, but my question is: There is possibility of OpenMPT capable to open each song in the same instance when I open by double click?

[LPChip]

Although its not the answer to your question, its another thing you can do.

You can at all times drag a song into OpenMPT and it will open it. If you don't have OpenMPT visible on your screen but its in your taskbar, drag and hold the file onto the taskbar. Wait till OpenMPT pops up, and continue the drag into OpenMPT and it'll open that song. (works with many programs actually)

[psishock]

djmakas, its Windows default feature, to behave on double clicked, associated file type, just like you have described.

There are several ways to "override" that, one is dragging the selected files on the taskbar and adding it up to opened ompt instance (like LP suggested), or you can also use directly the ompt file/open menu option. That way too, every new song that you would open, will use the same ompt instance.

[LPChip]

Not to forget that you can also use the treeview and drag a tune from there into right side to open it. (not just to open samples/instruments.)

[Saga Musix]

This was possible with the old MPT, but DDE commands somehow don't work with the OSS version, I dunno why, but it's not possible anymore to open all files in the same instance. However, MPT just consumes about 16mb per session, so memory really shouldn't be an issue.