Is there any possibility of modplug being used as a plugin in another software?
I don't think so. And why should it ? It's like asking Word being a plugin for Notepad.
Modplug is a stand-alone application, and a plugin is a totally different construction, and dependent of a Host.
Maybe some kind of connection could be possible between Modplug and another program, but I don't know that.
And maybe there exists some VSTi plugin with a tracker-like system, I dunno that either.
for something like that,have a look at http://www.nashnet.co.uk/english/revisit/
Nice tip. And the page has a nice explanation about things, and why tracking is something else than using a sequencer.
Thanks guys. I'm gonna check this out. All i really want is a way to time-sync modplug with a multitrack software. I'm sure it cant be that difficult
QuoteI'm sure it cant be that difficult
This is a standard argument by the people who ask for a solution, never of the people who have to solve the problem.
Using a tracker as VSTi can be very good option, especially if you record guitars and vocals on your songs. You can make adjustments to the song without rendering the whole song to .wav again, and still be able to hear all the tracks of the song (recorded & tracked).
There are trackers that can already do this (e.g. Skale, works ok in Cubase)
Another option is to use one of the sound data interfaces, like re-wire.
Quote: From Sam Zen
QuoteThis is a standard argument by the people who ask for a solution, never of the people who have to solve the problem.
You are correct in saying this, as if it was that easy it would probably have been done already. My apologies to the programmers.
I agree, modplug would be great as a vst instrument. I primarily started making music in modplug, but eventually made the jump to a cubase/fruity loops combination. Being able to open FL in cubase has been a godsend, I can run my sequences and record guitars or vocals at the same time, never rendering my sequences to .wav. In order to use any of my old modplug songs, I have to:
1. resequence everything from scratch in fruity loops; OR;
2. render all of the tracks, ONE AT A TIME (not fun when you have 60+ tracks running) to wav, and move them into cubase. (this also seems to eat up more memory in cubase, as I'm running WAY more lengthy wavs.)
Also, both FL and ModPlug have their cool points, and being able to run them simultaneously from cubase would be positive, taking advantage of both interfaces.
So, when will we see a VSTi feature for ModPlug?
Oh, and Fruity Loops IS a stand alone application that can be used as a plugin for cubase, Sam_Zen. It's actually really cool!
Chances of that ever happening are next to nothing i think lol
The fact that fruityloops is standalone and also useable as vsti isn't saying anything,you're talking about it as if it were real easy to make a vsti of modplug which most likely isn't easy at all.
2 Roman Only
I don't use cubase, I did test FL and I'm usually looking for cool results instead of cool tools.
In the meantime I noticed a plugin already with tracker-like properties.
Well, hopefully one day we might see this happen, especially because I've almost completely stopped using modplug since I've discovered FL VSTi. I think that's about the only feature that could bring me back around to tracking, until then, the FL step sequencer does almost everything MPT does, and lots of things it doesn't! Hopefully the tracking world can keep up with the technology!
Quote from: "Roman Only"2. render all of the tracks, ONE AT A TIME (not fun when you have 60+ tracks running) to wav, and move them into cubase. (this also seems to eat up more memory in cubase, as I'm running WAY more lengthy wavs.)
Why would you want to render them one at a time?
If you mean 60+ channels, then you can do export to wav, and check channel mode.
It will export all channels to a seperate wavefile.
Quote from: "LPChip"If you mean 60+ channels, then you can do export to wav, and check channel mode.
It will export all channels to a seperate wavefile.
Thanks for the tip LP! I still have a few old MP songs I need to render, and this will help greatly! It still takes a while for it to render all of them, but at least I don't have to stare at the screen for hours on end.
dBlues: I render them all seperately so that I can mix them in Cubase, as it has a much better eq situation. As for one at a time, I'll be using the tip LPChip just dropped me. :D
I still wish I could use ModPlug in Cubase, though. :oops:
Quote from: "Roman Only"
dBlues: I render them all seperately so that I can mix them in Cubase, as it has a much better eq situation. As for one at a time, I'll be using the tip LPChip just dropped me. :D
I still wish I could use ModPlug in Cubase, though. :oops:
Sure, thats what I have been doing since I first installed Modplug.
But back to the original topic. From what I understood before, I think MFC dependency, or rather, mixed UI and other code-architecture, could hinder the Modplug VSTi/DXi-plugin development. If Modplug could somehow be refactored to separate non-UI-specific code under a platform, it would be much easier. This is not the case atm, however, and again it is the same thing that limits Modplug development. But, this is something that probably needs to be accepted and lived with. At least until a mythical diamond-hard-coder comes and refactors everything just like that (smells like irony here...)
Quote from: "Roman Only"
But back to the original topic. From what I understood before, I think MFC dependency, or rather, mixed UI and other code-architecture, could hinder the Modplug VSTi/DXi-plugin development. If Modplug could somehow be refactored to separate non-UI-specific code under a platform, it would be much easier. This is not the case atm, however, and again it is the same thing that limits Modplug development. But, this is something that probably needs to be accepted and lived with. At least until a mythical diamond-hard-coder comes and refactors everything just like that (smells like irony here...)
I think of simpler approach to this matter: create some simple VSTi DLL file which would connect to running MPT with e.x. pipe object, and add sound output device in MPT which will write to that pipe - both tasks seems fairly simple, because there are examples in VST Plugins SDK and MPT sound output devices are based on a simple interface.
Based on that, I see "modplug being used as a VSTi" like this: you start MPT, load some song, start Cubase, load "Modplug_VSTi", they connect to each other somehow, and then you press in Cubase notes C-4 to B-4 to play patterns 1 to 12 in MPT, notes C-5 to B-5 to mute/unmute channels 1 to 12, C-6 to pause/continue the song, C#6/D-6 to increase/decrease BPM etc. etc.
Nice idea... Quite Linux-y, with all its pipes. =) The only problem would be minimising latency. Any additional layer will necessarily add a degree of latency, so the vst-i interface to mpt would have to be _very_ highly optimised.
I have zero technical knowledge in this area, but i gather now that it must be very difficult to link Modplug with Cubase as a vsti or re-wire. However, do any of you guys think that it would be easier to link Modplug to Cubase via midi time-code? Then once your happy with the arrangement and mix you could render the file to wav and load into Cubase as an audio file.
I've made some progress on this topic - Get the archive (http://www.4shared.com/file/23749924/8d30db73/OpenMPT_VSTi.html).
Put OpemMPT_VSTi.dll to your VST plugins dir, put OpenMPT_VSTi.exe to mptrack dir.
Run VSTi host (even OpenMPT itself will go :) ) and load .dll - it will show config dialog for the first time (you'll be amased how do I like to write config dialogs ;) ). After you finished with config (typically change path to .exe from archive), restart VST host. Then, when you load .dll, the mptrack window pops up (note "VSTi" in the title). Load some song in mptrack and then send MIDI keys to VSTi DLL:
C-4 to A-4 to start playing patterns 1-10 (in theory, right now it just starts playback from current pattern).
C-5 to A-5 to mute channel 1-10 (mptrack GUI won't show it, but it is muted, really ;) ).
B-5 to stop playback.
Hold A#4 when hitting some key to toggle On Transition mode - that's it, mute toggled and selected pattern played at the end of current pattern (that's the only way to go to some pattern for now).
Hold B-4 and type large number with several keypresses - the selected channel muted / pattern played when you release B-4 (doesn't work yet).
Yeah. Bugs are not just possible - they are expected 8) , so please report them :boogie: .
Oh. That's taken the whole week to code, and it's still prerelease.
Quote from: "pelya"I've made some progress on this topic - Get the archive (http://www.4shared.com/file/23749924/8d30db73/OpenMPT_VSTi.html).
Put OpemMPT_VSTi.dll to your VST plugins dir, put OpenMPT_VSTi.exe to mptrack dir.
Run VSTi host (even OpenMPT itself will go :) ) and load .dll - it will show config dialog for the first time (you'll be amased how do I like to write config dialogs ;) ). After you finished with config (typically change path to .exe from archive), restart VST host. Then, when you load .dll, the mptrack window pops up (note "VSTi" in the title). Load some song in mptrack and then send MIDI keys to VSTi DLL:
C-4 to A-4 to start playing patterns 1-10 (in theory, right now it just starts playback from current pattern).
C-5 to A-5 to mute channel 1-10 (mptrack GUI won't show it, but it is muted, really ;) ).
B-5 to stop playback.
Hold A#4 when hitting some key to toggle On Transition mode - that's it, mute toggled and selected pattern played at the end of current pattern (that's the only way to go to some pattern for now).
Hold B-4 and type large number with several keypresses - the selected channel muted / pattern played when you release B-4 (doesn't work yet).
Yeah. Bugs are not just possible - they are expected 8) , so please report them :boogie: .
Oh. That's taken the whole week to code, and it's still prerelease.
Awesome! Now, I need to find myself a sequencer :P
Version 0.2 of OpenMPT_VSTi (http://www.4shared.com/file/24449367/3ef1863b/OpenMPT_VSTi_02.html) is out. All bugs mentioned in previous post are fixed + another config option added to reduce latency ( delete your OpenMPT_VSTi.dll.cfg file and it will show new config dialog again :) ). To control playback with MIDI notes you should have Pattern tab open in VSTi.
This should be enough for e.x. syncing playback of MOD-file and recorded audio track or running two OpenMPTs in sync. When used as VSTi OpenMPT retains all editing features and massive GUI, so it is recommended to disable Follow Song and minimize OpenMPT window. Also Modified flag is cleared with every MIDI note, so it won't ask you to save MOD-file when exits.
Edit: SVN patch (http://www.4shared.com/file/24928069/506d947e/OpenMPT_r191_VSTidiff.html) for revision 191 - doesn't include any MinGW-specific code, just VSTi implementation.
ok , first of all this program may be the solution to my problem, BIG UP!! for that,
but i doesnt seem to work properly , can you give detailed instructions please. i downloaded open mpt vsti 0.2 and put exe file in mpt folder , and dll to my vst folder.. when i open omptvsti in acid pro 6.0 , it opens properly as a vsti .. the sound from mpt goes to acid and, midi messages should also go to mpt .. but theres no sync at all
it says something... "cannot connect pipe ....."
Shut down both acid and modplug, then start acid, load VST - modplug should be started automatically from acid, if you'll just launch that .exe it won't work (Cannot connect pipe message may be because of that, or because you moved modplug_vsti.exe to different place - edit your .cfg file then).
And send MIDI notes from acid to start/stop playback in modplug, if you'll hit Play/Stop inside modplug window it will be desynced. Note that start/stop playback in modplug is timely operation and may cause that desync, I suggest starting playback and then jumping to the pattern start with C-4 - A-4.
Oh, and also you may ask Relabs to include that little haxx of mine into SVN :P so it will include latest bugfixes made by him.
By going through all the requests, I see that this one is still open. Should we keep it open since there is a VSTi version of modplug now?
Keep it open, since it it's not beeing updated with newest versions.
yea.. keep it open , this vst thing is best direction to develop MPT ... DAW world is full of superslow-mousebased-pianoroll type of sequencers , theres nothing faster than MPT for sequencing ... i would like to see some day perfect sync with ableton , and drag&drop waw. rendering ( like in maschine.vst)
this is the way that development should go... at least for me since i like to play instruments on top of my tracker tracks.. but i think this could be really nice thing for tracker purists also , imagine multiple trackers on ableton perfectyly in sync , live remixin/mixing of songs.. mad stacks of VST effect with abletons great implementation this could be really big thing for those who want to play live their MPT producted songs...
This workaround is not stable enough to be usable, so yeah keep it open. A proper implementation of MPC as a VST is the best of both worlds (tracker+DAW). I've made the jump to Reaper just for recording guitar, but when you want to lay down say a drum track the midi editor is a nightmare! I can do it in no time in MPC and I'm sure that many people dreamed of a DAW with a tracker sequencer
:wink:
Quote from: "immortalx"I can do it in no time in MPC and I'm sure that many people dreamed of a DAW with a tracker sequencer
:wink:
Well, you dream already became true (http://forum.openmpt.org/index.php?topic=3685.0), just not with OpenMPT.
Quote from: "Jojo"Quote from: "immortalx"I can do it in no time in MPC and I'm sure that many people dreamed of a DAW with a tracker sequencer
:wink:
Well, you dream already became true (http://forum.openmpt.org/index.php?topic=3685.0), just not with OpenMPT.
TBH i don't really like Revisit's interface and always thought that modplug was a revolution with it's standard windows forms and buttons. So OpenMPT as a vst is still a dream :)
Quote from: "immortalx"Quote from: "Jojo"Quote from: "immortalx"I can do it in no time in MPC and I'm sure that many people dreamed of a DAW with a tracker sequencer
:wink:
Well, you dream already became true (http://forum.openmpt.org/index.php?topic=3685.0), just not with OpenMPT.
TBH i don't really like Revisit's interface and always thought that modplug was a revolution with it's standard windows forms and buttons. So OpenMPT as a vst is still a dream :)
You can run OpenMPT as VSTi, just not the newest version. Should be a download link somewhere in this topic and in the download forum as well.
Hello captain obvious! :)
Quote from: "immortalx"This workaround is not stable enough to be usable, so yeah keep it open