Recent Posts

Pages: 1 [2] 3 4 ... 10
Help and Questions / Passing midi messages from one vst to another
« Last post by Exhale on February 20, 2017, 15:41:21 »
I have been searching and searching for the conditions under which this works:
you send a midi message to 1 vst or vsti and it adds messages to the midi, then you send those new messages to a new vsti so that it can render them... I have done this in the past, but I have forgotten under what conditions it works and have been searching for hours now... the instructions seem to say the vsti should be under the initial vst or vsti which is editing the midi messages on the plugin list, but it doesnt seem to work...
The example I am playing with starts with randomid vsti and I just tried to send it to polyslop as a test but nothing is going through.
What am I missing?
I am sure I will kick myself, but yeah I need to get the hang of this.
I think plugins like this are generally called arpegiators, but I admit I barely ever use them & now want to start using them more.
Development Corner / GIT mirror and SVN repository cleanup
« Last post by manx on February 18, 2017, 20:11:43 »
Rewriting History

I am currently in the process of providing a read-only git mirror of the OpenMPT Subversion source code repository.

In order to facilitate easier mirroring in git, it turned out to be useful to first canonicalize the Subversion repository as much as possible.
The Subversion repository had originally been a CVS repository and got converted to Subversion on 2006-03-14. In that conversion process, branch relationships got confused and misrepresented. Additionally, commits without author were introduced during the conversion. This fact and various other problems have been addressed and the folowing modifications have been made to the Subversion repository:
  • date back the earliest revisions to the actual release date of the source code of ModplugTracker 1.16
  • set Olivier as committer for ModplugTracker 1.16
  • fill-in various missing committers
  • provide a useful commit message for Olivier's source drop
  • in Subversion, old branches got deleted to make them invisible, this is not representable in git and thus, in order to make them reappear without weird commit dates, date back the deletion of old branches
  • as there exists meaningful history in open source releases before ModplugTracker 1.16, namely modplugxmms 1.0 to 2.0, add this code to the OpenMPT repository
  • add a variant of the very early OpenMPT modifications only found in a zip archive (MPT-1.16-noMMX)
  • up to about OpenMPT 1.17, OpenMPT was developed in a wild subdirectory which can make viewing history confusing, thus move all tags and branches to refer to this subdirectory directly
  • add a ton of old branches and tags for as many versions and variants as Saga Musix and I were able to identify unambiguously
  • add a new top-level folder devbranches where future development and experimental branches are supposed to be stored which makes it easier for the git conversion tool to skip those in the future
  • make the naming of all branches and tags consistent
  • in particular, the current 1.26-maintenance branch is renamed to OpenMPT-1.26
About half of these modifications modify ancient revisions and thus actually modifiy the history. Subversion does store this history information in revision properties on the old revisions and does not record the old state when doing modifications. As I did not want to actually lose information, I recorded all modifications to revision properties in freeform text inside the commit message of the respective revision.
I also made a backup of the Subversion repository before doing the modifications.

Actions required on SVN repository clients

If you are running a svnsync mirror of the repository, you are advised to resync ALL revision properties (use svnsync copy-revprops) in order to have the same state as the official repository.
If you have a working copy of the 1.26-maintenance branch, use svn switch


The actual git mirror will still take some days or weeks to setup. Please be patient and stay tuned.

As OpenMPT 1.27 and libopenmpt 0.3.0 will still take some time until the release is ready, I am contemplating to drop even more compiler support than originally planned.
Visual Studio 2017 will be released before OpenMPT 1.27, thus we can drop VS2013 support in 1.27 and still have 2 supported Visual Studio versions.
Debian 9 will also very probably be released before libopenmpt 0.3.0, and thus we can drop GCC 4.6 and GCC 4.7 and still have the latest 2 Debian releases supported. The latest 2 Ubuntu LTS releases are also covered when requiring GCC 4.8.

Thus, the required compiler versions might very well end up being:
  • MSVC >= 2015
  • GCC >= 4.8
  • Clang >= 3.2
Yup, I have been able to access the forum from exactly one IP address since then - neither of my vServers, my home IPs nor my university IPs work.
Let's hope the issue gets sorted out soon. I guess we set up the information site just in time, otherwise VSE would still be the only place with information about the memory card project.
There is also a thread on Gearslutz about the project, but with 0 replies so far:
Just thought I'd sign up here and let you know that the VSE forum has become inaccessible to a vast majority of its members. We all get a screen that tells us that our IP address has been permanently banned. There's a thread about it on GS here:
Help and Questions / Re: Orderlist
« Last post by Saga Musix on February 12, 2017, 20:21:02 »
I can work around it by setting all the orderpositions to pattern 0 for example.
Or just jump to the last order item before the "---" pattern. The pasted patterns will be inserted after the selected item, so this is equivalent to what you want to do.

But i can't figure out why the shortcut for copy order doesn't work. It's listed in the keyboard tab in the setup menu but nothing happens.  I don't know if its relevant but i have Windows 7 64bit Openmpt 32bit.
Indeed it's listed, but it doesn't do anything. ;) This is fixed now.
Help and Questions / Re: Orderlist
« Last post by FWL on February 12, 2017, 19:27:59 »
Ok, thanks again! I understand how it works now. I can work around it by setting all the orderpositions to pattern 0 for example. Then it will always paste in an existing pattern.

But i can't figure out why the shortcut for copy order doesn't work. It's listed in the keyboard tab in the setup menu but nothing happens.  I don't know if its relevant but i have Windows 7 64bit Openmpt 32bit.
Help and Questions / Re: Orderlist
« Last post by Saga Musix on February 12, 2017, 18:37:51 »
As the paste location depends on the last edited pattern, and the currently edited sequence position is not a valid pattern, it won't paste there. I know that's not very sensible, it's just an explanation how it works internally. It's difficult to revise this behaviour but I will try.
Help and Questions / Re: Quick question about Mixing/Normalizing
« Last post by Saga Musix on February 12, 2017, 18:36:08 »
I'm surprised that this is happening, since I made sure to click Normalize Output on every export.
Normalizing is not the same as dynamics processing. If one of your songs has one very large peak somewhere but apart from that is rather quiet, then this peak will remain the loudest part even after normalization, so the rest of the song will stay quiet too. You can counteract this by manual or automatic dynamics processing. Manual processing requires to adjust the global volume of your songs to make the loudest parts more quiet. This is a good idea in general, but it's also a bit of work. The alternative is to use a dynamics processor, e.g. a master limiter or compressor effect. There are thousands of such effects available as VST plugins, but you shouldn't overdo it (or you will be part of the loudness war).
Pages: 1 [2] 3 4 ... 10