Using Vintage Modes on Single Tracks

peterpiper wrote:Haha. Now thats dope. Thank you for publish this info AnSolas.

Next step to do:
copy the files to your Cubase, Reaper, whatever VST folder
renaming them with the extention .dll
Run Cubase, Reaper, whatever
rescan VST folder
use the vintage modes in Cubase, Reaper whatever

just a thought


peace

Have you tried this? I can't get them to show up in Maschine.

grinchmob wrote:

peterpiper wrote:Haha. Now thats dope. Thank you for publish this info AnSolas.

Next step to do:
copy the files to your Cubase, Reaper, whatever VST folder
renaming them with the extention .dll
Run Cubase, Reaper, whatever
rescan VST folder
use the vintage modes in Cubase, Reaper whatever

just a thought


peace

Have you tried this? I can't get them to show up in Maschine.

Not all .dll files are 100% self contained operation wise. Some are and those do not require installers and can usually be "liberated" or scanned by another host app as the .dll is entirely self contained and does not reference a connected .exe or .dmg installed application.

In other cases, possibly this one, the .dll file relies on data in the Program or Data folders of the host app and without that present it's not going to run in another host app even if it passes scan.

Just guessing but if it is like I described it would explain why they are interchangeable to the MPC Studio host environment but seemingly not other host applications.

Still a dope and clever find though.

Metatron72 wrote:

grinchmob wrote:

peterpiper wrote:Haha. Now thats dope. Thank you for publish this info AnSolas.

Next step to do:
copy the files to your Cubase, Reaper, whatever VST folder
renaming them with the extention .dll
Run Cubase, Reaper, whatever
rescan VST folder
use the vintage modes in Cubase, Reaper whatever

just a thought


peace

Have you tried this? I can't get them to show up in Maschine.

Not all .dll files are 100% self contained operation wise. Some are and those do not require installers and can usually be "liberated" or scanned by another host app as the .dll is entirely self contained and does not reference a connected .exe or .dmg installed application.

In other cases, possibly this one, the .dll file relies on data in the Program or Data folders of the host app and without that present it's not going to run in another host app even if it passes scan.

Just guessing but if it is like I described it would explain why they are interchangeable to the MPC Studio host environment but seemingly not other host applications.

Still a dope and clever find though.

Gotcha!

But try it anyway.

I just tend to let my mind wander on DAW crap and found it really cool this was being done. But if it doesn't work what I posted would likely be why.

Yes I know that . But I thought it is worth trying cause it might work. I don't have the Ren so I can't test it.

peace

xparis001 wrote:our plan was eventually to allow vintage mode on individual tracks, but since this is untested, your mileage may vary. Also, as you see, there's no GUI as yet. we're looking at implementing this fully soon.

So where does this leave Studio owners? Do you patch it up so they can't use the exploit or do you also open it up for them?

xparis001 wrote:our plan was eventually to allow vintage mode on individual tracks, but since this is untested, your mileage may vary. Also, as you see, there's no GUI as yet. we're looking at implementing this fully soon.

that's good to hear,...

although bit funny that this feature was undisclosed and is working fine as opposed to official features that crash

So this is the legendary Ren hack

Watch Akai **** it up and block the paths and then implement a buggy version.

Hello! i did excactly what was written in the first post, but i cant see the emulation plugins.
When i rescan it reads them but then i cant find them.
I also tried to reopen the software!

Any ideas?

I wonder what results would come if you used serveral different vintage modes across a track on top of the master out being a different vintage mode???

For some reason when I do this on the studio, the only one that shows up is the sp12 45 emulator, the others I do have since I used to have the Ren, but they wont show up?

Anyone having problems should post up their system specs - Ren or Studio, Mac or PC, OS version etc.

I've made a little tutorial out of this BTW:

http://www.mpc-tutor.com/mpc-studio-mpc ... unleashed/

I initially found the only problems have been related to the ring mode emulation (not showing or being the only one showing), although I've had several reboots since then and all has been fine.

As I say in the article, I don't really see the point in running the Ring Mode vst as it's just the Decimator, so if you are having issues, see what happens when you remove the ring mode vst (rescan and restart app after removing).

DjRaz wrote:Hello! i did excactly what was written in the first post, but i cant see the emulation plugins.
When i rescan it reads them but then i cant find them.
I also tried to reopen the software!

Any ideas?

Check page 4 of this thread if you're using windows.

I'm excited to have my vintage mode plugs on separate tracks. Big up to Ansolas.

I have the mpc studio runnng on a macbook pro OSX 10.3 and did the hack and it does work on the studio plugins are located all the way at the bottom of the list. and all work great