New build 1.17.03.02 (revision 371) is now available for testing.
Download: OpenMPT-1.17.03.02.zip (http://lpchip.com/modplug/files/OpenMPT-1.17.03.02.zip) (LPChip's server)
OpenMPT-1.17.03.02.zip (http://sagamusix.de/openmpt/download/) (Saga Musix's server)
MD5 : 5ee30dc3b7a485f0428d3e13c0647ac7
SHA-1: 160e6c3e1cc9311cfb8cb27ad69c38f22872ec9f
----Changes----General:[New] New default directories: plugins and plugin presets.
[New] IT "Note Fade" command. Works only in instrument mode. Will be displayed as "~~" in the pattern.
[New] Cleanup -> Rearrange samples is back.
[New] Cleanup -> Compo cleanup. Useful for creating samplepacks for compos.
[New] Can import/export color settings. example colour schemes (http://sagamusix.de/openmpt/download/colors/)
[Mod] Default keybindings and tunings are now bundled in the executable file. So for example there are always default keybindings available even without default.mkb.
[Mod] Soundcard latency can now be reduced to 1ms.
[Fix] Keyboard manager: Octave offset for key descriptions is now C, not A
[Mod] MP3 Export uses ID3v2 Tags.
[Mod] When loading a tune with VSTs that are currently not installed, only one "plugin not found" dialog with a summary will be shown instead of many small dialogs.
[Mod] Autosave: If a file hasn't changed since the last autosave, it won't be saved again and again...
Instrument tab:[New] Envelope points can now be added by shift-clicking somewhere in the envelope editor. Middle mouse button click removes the nearest point.
[Fix] No relative values are shown for envelopes with no release node (status bar)
[Fix] Fix to crash that occurred when multiple windows had instrument tab of the same document open.
[Fix] Didn't update properly when rows per beat were 0.
Legacy support:[New] XM compatibility export.
[New] Can now import GDM (General Digital Music) files.
[New] Can now import IMF (Imago Orpheus) modules
[New] Can now import all "new" PSM modules (Epic Pinball, Extreme Pinball, Jazz Jackrabbit, Sinaria, One Must Fall)
[New] Can now load XM Version 1.02 and 1.03 modules
[Fix/Imp] Loads of (optional) compatibility fixes making playback routines behave more like in original trackers (Fast Tracker, Impulse tracker etc.)
[Imp] Various module conversion improvements between formats.
MIDI mapping:[New] Can now record parameter changes to pattern (MPTM).
[New] Holding shift-key while modifying a plug param from GUI will open MIDI mapping dialog with corresponding settings preset. Doesn't work with plugs that don't have their own GUI.
MPTM:[New] New plug param control "notes" (see "Parameter control (MPTm only)" and "Parameter control(smooth)(MPTm only)" from setup->keyboard->Pattern editor - Note col).
Differences to macros:
-No need to assign to channel before using.
-Extended parameter index range:
[0, 999]
-Extended parameter value range: [0, 999]
-Consumes all columns in channel instead of just the effect column.
[/list]
Command format: PCS 01 002 123. Instrument column defines the plug index, volume column the plug param and the effect column the effect value in range [0,999]. The example would smoothly set (similarly to /xx command) parameter 2 of plugin 1 to value 123/999.
Important: At the moment the plug indexes in the parameter control notes are not automatically adjusted when reordering plugs. Thus any action that causes the plug index to change will make all parameter control notes that use the index invalid.
[New] Can have multiple sequences in one file.
[New] Extended envelopes: can now have up to 240 points.
[Imp] Channel settings(vol&pan) for channels after 64 will now be saved in the file.
Pattern tab:[New] Channel reset(stops note, sets initial chn settings). Available from channel header context menu and new key binding.
[New] Overflow paste: Paste will now optionally continue on next pattern. Includes a new keyboard shortcut for toggling.
[New] When shift-clicking somewhere, a selection will be drawn from the previous cursor position to the new position.
[Imp] Various improvements to effect descriptions.
Orderlist:[New] Multiple orders can be selected in the pattern sequence. At the moment, it is possible to insert, delete, duplicate and dragondrop multiple orders.
[New] Can render a order selection to wav directly from orderlist context menu.
Macro Configuration:[New] Also detect preset macro types for Z80-ZFF
Sample tab:[New] Sample drawing.
[New] Add silence and resize sample.
[New] Can now play sample from given position with Ctrl + left mouse button.
[New] DC offset removal. Includes a new possible keyboard shortcut.
[New] Batch export samples (shift + click on "save sample" icon)
[Imp] Better loop point handling when deleting sample selections.
[Imp] Add the key "FinetuneStep" to section "[Sample Editor]" in mptrack.ini to change finetune steps for configuring C-5. For example, add "FinetuneStep=100" for 100 hertz steps.
VST:[Mod] Changed host IDs and a couple of related return values. If compatibility problems occur, old IDs can be set with ini-settings.
Comment tab:[New] Double-click sample/instr names to directly go to sample/instr tab
[Imp] Show instrument tab by default for XM files
Setup:[New] Position aware timer: When jumping around in your modules manually, the timer will be adjusted (must be enabled from setup screen)
[New] Reset channels on loop: When this is enabled (this was the default until now), all channels will be reset when the song loops (i.e. jumps back to position 0). When disabled, channels won't be stopped/reset and the global settings (volume, tempo, speed) will also not be reset.
And in addition numerous smaller fixes, changes and improvements such as GUI tweaks.
Additional file hashes:
mptrack.exe
MD5 : 2fb98a30d0b109478e90fd38094ce31b
SHA-1: 64fcddfbc95749f684f294290aa2822d3c757b1d
I have prepared a few colour schemes to try out:
http://sagamusix.de/openmpt/download/colors/
My own colour scheme (Jojo.mptcolor) is the default colour scheme, but with darker VU meters.
Feel free to share more themes!
EDIT: I would also beg you to go through the Bug Reports / Feature Requests forums and check if we have accidentally (lol) fixed a bug / included a feature that has not been marked as such.
НОГУ КЯАР!
Quote from: "Jojo"MPTM:
[New] New plug param controls.
Differences to macros:
-No need to assign to channel before using.
-Extended parameter index range: [0, 999]
-Extended parameter value range: [0, 999]
-Consumes all columns in channel instead of just the effect column.
[New] Can have multiple sequences in one file.
Wow, this is impressive..
Here's a more or less complete list of all playback improvements:
Impulse Tracker:
- Better sample vibrato compatibility. Vibrato Sweep isn't perfect yet, though.
- Special cases of Retrigger + Envelopes
- Offset beyond sample range
- Vibrato, Tremolo and Panbrello were behaving incorrectly (fixed waveforms)
- Don't reset Tremolo on new note, don't ignore tremolo if note volume is 0
- Ignore S[345]x with x > 3
- Multisample instruments change with no entry in the instrument column (tentative fix)
- Compatibility Export: Using an own Tracker ID in the "made with" header field
- Added "Note Fade" notes. You weren't able to enter them in Impulse Tracker's editor, but they work. Applications that currently support them are OpenMPT, SchismTracker and XMPlay.
- Row Highlight is now saved in the IT header, as Impulse Tracker in fact supported this.
- OpenMPT was loading the volume column command hx (vibrato depth) as ux (vibrato speed) and also saving it like this.
- Tremor is implemented correctly now
- Retrigger is implemented correctly now
- Can now load IT files with very small patterns (< 4 rows)
- Pattern loop count won't be reset on pattern transition
- Tempo slides won't exceed 255 BPM in compatible mode.
- Fixed handling of very short pitch / filter envelopes
- Panning fx (Xxx, S8x, pxx) override pan swing
- SD0 / SC0 is now interpreted as SD1 / SC1
- Portamento up / down resets the destination of tone portamento
- Load default tempo of 31 BPM as 32 BPM instead of 125 BPM (until a better solution is found)
- Handle out of range global volume commands
- Global volume slides are stored per channel
- 4-Bit panning didn't disable surround
- Remember Arpeggio parameter even if no note is playing
Fasttracker 2:
- XM Format 1.02 and 1.03 will load correctly now.
- Portamento + New Note with no previous note
- Offset beyond sample range
- More compatible Arpeggio
- More compatible "Note Off + Something"
- Note Off with instrument number causes fadeout for samples that have no envelope
- Volume command Ux only sets the vibrato speed
- Pxy effect was too deep
- Don't ignore last pattern when loading XM files that have no instruments
- Compatibility Export cuts off channels > 32.
- When channel count is odd, an empty channel will be attached when saving XM files (so Fasttracker 2 won't screw up)
- Using an own Tracker ID in the "made with" header field
- F20 won't turn into G20 when saving
- Tempo slides won't exceed 255 BPM in compatible mode.
- More compatible retrigger
- More compatible Kxx effect
- Pattern loops are now handled correctly
- Handle out of range global volume commands
- Global volume slides are stored per channel
Scream Tracker 3:
- Using an own Tracker ID in the "made with" header field
- Patterns are now saved correctly and should no more result in garbage the pattern end in ST3 (and BWSB)
- Notes with SD0 are now ignored, SC0 is completely ignored
- 4-Bit panning didn't disable surround
- Remember Arpeggio parameter even if no note is playing
ProTracker:
- 8xx Panning ranges from 800 to 8FF
- F20 won't turn into G20 when saving
- Pattern loops are now handeled correctly
- Compatiblity export: Modules created with OpenMPT won't crash Amigas anymore.
General:
- Correct handling of "break to row" command on last pattern: Don't reset all channels, break to correct row.
- Updated mod specifications (that define what can be input into the tracker and what not)
And while we're at it:
Small example tune (ftp://ftp.untergrund.net/users/sagamusix/openmpt/resources/modules/pcnotes.mptm) that shows how to use Param Control notes. The Electri-Q plugin is required.
Quote from: "Nahkranoth"НОГУ КЯАР!
Quote from: "Jojo"MPTM:
[New] New plug param controls.
Differences to macros:
-No need to assign to channel before using.
-Extended parameter index range: [0, 999]
-Extended parameter value range: [0, 999]
-Consumes all columns in channel instead of just the effect column.
Agreed! :D
Nice work, Relabs & Jojo!
Impressive :)
I don't know what i'm more excited about, USING the new build or writing it up in the OHM!
Excellent work devs! :boogie:
Even I'm impressed. :)
Good job guys! :)
Yeah nice work guys. Controlling VSTs from the pattern without macros has been a long time coming.
Changes Comments:
Quote[New] Cleanup -> Compo cleanup. Useful for creating samplepacks for compos.
Please describe. What happens when choosing? Which track formats does this work in?
Quote[New] Can have multiple sequences in one file.
Need more info. How do i access and use this feature?
Quote[New] Also detect preset macro types for Z80-ZFF
What changes does this entail? Is it only of use for plugins whose controller values exceed 7F?
Quote[Imp] Add the key "FinetuneStep" to section "[Sample Editor]" in mptrack.ini to change finetune steps for configuring C-5. For example, add "FinetuneStep=100" for 100 hertz steps.
Does this mean portamento gradations? When do we need to fiddle with this?
Quote[New] Position aware timer: When jumping around in your modules manually, the timer will be adjusted (must be enabled from setup screen)
Seemed to work fine, but i did not test against wildly changing tempos or speeds. Does this clock account for tempo and speed changes from patterns before it?
QuoteImpulse Tracker:
Special cases of Retrigger + Envelopes
Offset beyond sample range
Ignore S[345]x with x > 3
Multisample instruments change with no entry in the instrument column (tentative fix)
Row Highlight is now saved in the IT header, as Impulse Tracker in fact supported this.
Tremor is implemented correctly now
Retrigger is implemented correctly now
Pattern loop count won't be reset on pattern transition
Panning fx (Xxx, S8x, pxx) override pan swing
Portamento up / down resets the destination of tone portamento
Handle out of range global volume commands
I know you're going to hate me for asking, Jojo, but can i get details of what's going on with these particular changes, and perhaps what the problem was before? You may be addressing problems i've had before, but i'm not sure with these short descriptions.
I'm especially concerned about S3x, S4x, and S5x, where x > 3. Does this mean IT cannot retrigger oscillator waveforms (vibrato, tremolo, and panbrello), or are they always assumed to be continuous?
In IT, it seems you're saying that calling Exx and Fxx resets the tone portamento, but to what? How has using portamento changed?
Changes i'm VERY impressed with (in no particular order):
Quote[New] Envelope points can now be added by shift-clicking somewhere in the envelope editor. Middle mouse button click removes the nearest point.
Works beautifully and makes envelope editing 100% more efficient.
Quote[New] Holding shift-key while modifying a plug param from GUI will open MIDI mapping dialog with corresponding settings preset.
Have yet to really dive into MIDI mapping, but i have a feeling i will love this when i hook up my Alesis synth to MPT!
Quote[New] Can now record parameter changes to pattern (MPTM).
If this works as simply as i think it will, i will be glad i started tracking in MPTM format last year (when there was no great benefit). What's even better are the shortcuts for this!
Quote[New] Overflow paste: Paste will now optionally continue on next pattern. Includes a new keyboard shortcut for toggling.
The few times i need this will still be worth the inclusion into MPT. (I may need it more than i realize now that i think about it....)
Quote[New] Multiple orders can be selected in the pattern sequence. At the moment, it is possible to insert, delete, duplicate and dragondrop multiple orders.
The best thing to happen to the Order List since +++.
Quote[New] Can render a order selection to wav directly from orderlist context menu.
No, THIS is the best thing to happen to the Order List!! (http://download.modplug.com/uploads/files/1254415186dancing.gif)
Quote[New] Sample drawing.
In testing it for the first time, i found myself doodling to my heart's delight -- when i had far more important things to do (like writing up this post)!!! This function i found leads to impulsive creative exploration, as i found myself drawing and previewing, drawing and previewing, seeing what various waveforms sound like. To be honest i didn't think this would be any good of a feature. I'm glad i was wrong!!
Quote[New] Double-click sample/instr names to directly go to sample/instr tab
Finally! The Comments tab has some functionality! This is a good feature.
Quote[New] Position aware timer: When jumping around in your modules manually, the timer will be adjusted
The clock in the bottom right now has a reason to be looked at!(http://download.modplug.com/uploads/files/1254416822studying.gif)
Quote from: "Harbinger"Changes Comments:
Quote[New] Cleanup -> Compo cleanup. Useful for creating samplepacks for compos.
Please describe. What happens when choosing? Which track formats does this work in?
For the normal user, this is not of interest since it basically destroys the whole module. It's for us One Hour Compo hosters who need to quickly create a samplepack. This option removes all patterns, optionally removes all instruments and cleans up the samples (i.e. resets default volume, global volume, panning and vibrato settings) and converts the module to .IT.
QuoteQuote[New] Can have multiple sequences in one file.
Need more info. How do i access and use this feature?
At the moment, you can only access the sequences by right-clicking on the order list, but treeview support is currently being worked on.
QuoteQuote[New] Also detect preset macro types for Z80-ZFF
What changes does this entail? Is it only of use for plugins whose controller values exceed 7F?
No, this has nothing to do with plugin parameters. While the upper part of the Zxx configuration dialog (Z00 - Z7F, "parametered macro") always "remembers" which macros you use, MPT always displayed "Custom" for Z80 to ZFF (the lower part of the window), even if you didn't specify custom macros. So after setting f.e. Z80-ZFF to control filter resonance and closing the dialog, the dialog will now say "Z80-ZFF: Control Filter resonance" instead of "Custom" when opening the dialog again.
QuoteQuote[Imp] Add the key "FinetuneStep" to section "[Sample Editor]" in mptrack.ini to change finetune steps for configuring C-5. For example, add "FinetuneStep=100" for 100 hertz steps.
Does this mean portamento gradations? When do we need to fiddle with this?
You don't need to do anything with this (hint: when INI settings are involved, it
never affects mod playback, in a sense). See here for more details (http://forum.openmpt.org/index.php?topic=2830.0).
QuoteQuote[New] Position aware timer: When jumping around in your modules manually, the timer will be adjusted (must be enabled from setup screen)
Seemed to work fine, but i did not test against wildly changing tempos or speeds. Does this clock account for tempo and speed changes from patterns before it?
This uses the same mechanism as "show row play time" in the pattern editor context menu, so everything is taken into account.
QuoteQuoteImpulse Tracker:
Special cases of Retrigger + Envelopes
Offset beyond sample range
Ignore S[345]x with x > 3
Multisample instruments change with no entry in the instrument column (tentative fix)
Row Highlight is now saved in the IT header, as Impulse Tracker in fact supported this.
Tremor is implemented correctly now
Retrigger is implemented correctly now
Pattern loop count won't be reset on pattern transition
Panning fx (Xxx, S8x, pxx) override pan swing
Portamento up / down resets the destination of tone portamento
Handle out of range global volume commands
I know you're going to hate me for asking, Jojo, but can i get details of what's going on with these particular changes, and perhaps what the problem was before? You may be addressing problems i've had before, but i'm not sure with these short descriptions.
I'm especially concerned about S3x, S4x, and S5x, where x > 3. Does this mean IT cannot retrigger oscillator waveforms (vibrato, tremolo, and panbrello), or are they always assumed to be continuous?
In IT, it seems you're saying that calling Exx and Fxx resets the tone portamento, but to what? How has using portamento changed?
You can get details about some of the fixes here (http://eval.sovietrussia.org/wiki/Player_abuse_tests).
QuoteI'm especially concerned about S3x, S4x, and S5x, where x > 3. Does this mean IT cannot retrigger oscillator waveforms (vibrato, tremolo, and panbrello), or are they always assumed to be continuous?
I don't get you here. Sxy commands set the waveform once and forever. The fix here is only that e.g. S3F or S4A are ignored, because Impulse Tracker only does something for S30...S33 (same for S4x and S5x of course).
If you have more question about a specific fix that's missing on that wiki page, I may elaborate, but I certainly won't write up a detailed list of what the fixes change, simply because there are too many and because there's a basic description for every fix already.
I have testcase .IT files for almost all fixes, though, so if you're intersted, I can maybe upload those instead?
Also note that many of the bugs are rather unlikely to break a "normal" module (like "Pattern loop count won't be reset on pattern transition"), they were nevertheless bugs.
QuoteChanges i'm VERY impressed with (in no particular order):
Nice to hear that. :)
Jojo, the cleanup compo function could theoretically be used to create a new song using samples from an old song.
I can see why someone would quickly start a new song using sounds from an old song.
Isn't it an idea to rename the cleanup to: Cleanup: reset all but sounds
or something like that.. or Quick new from song, or something like that...
I see much potential in this feature for normal users and I also think it should be in the manual for that very same reason.
LPChip (et al):
Here's a sneak preview of what I was working on today:
(http://sagagames.de/ithumb/thumbs/cleanup8288rp13.jpg) (http://sagagames.de/ithumb/show/cleanup8288rp13.png)
(Note that this is just a draft)
Basically, the last checkbox is what "compo cleanup" was until today, so that should hopefully avoid confusion.
1. Compo cleanup: I am not sure what the first one means.
2. Multiple sequences: This is accessed in OpenMPT format by right-clicking the pattern row, hovering over the Sequences item, and clicking Create new sequence. Be aware though that this is a duplication, so if you change the patterns without changing their numbers, changes will also affect any sequences which contain those pattern numbers. For example, if you have 4 sequences, all having the same pattern numbers, and you change pattern 5 in sequence 3 for example, all of the patterns with the number 5 will change in addition to that one. Note: I am only guessing on this, as I have only done it with two sequences, though I would imagine that it would happen with any number of them > 1.
3. I am not sure on this one, as I do not use that effect.
4. That sounds interesting, but I am not 100% sure what it means nor when it would be used.
5. That is a great question, unfortunately, I do not know the answer to it.
6. Interesting changes, though I do not use the IT format too often (or many of the things in the list).
7. That sounds interesting, though I do not recall ever modifying the envelopes themselves, only the sample mapping.
8. I do not use a music keyboard to make music, only a keyboard designed to work with Windows.
9. I am not sure what that means.
10. The overflow paste is nice indeed. It is too bad though that it was not thought of before now!
11. As with the overflow paste, it is too bad that it was not thought of before now.
12. That is an interesting feature indeed.
13. I am not 100% sure that means.
14. Oh, from the Comments tab... I thought that it meant from the tree view, but that already existed.
15. Actually, I look at it quite a bit to see how long the song has been playing. :lol:
Note to Harbinger: In case you were curious, I do still [primarily] use version 1.17.02.52. I only use the newer version to start my songs (unless they are fewer than 4,000 patterns, then I will make them, but more often than not, the songs are more than 4,000 patterns long.) From a message that I received from Relabsoluness, apparently the 65,000 number was a mistake (which probably explains why the display was not updated to not chop the five-digit pattern numbers). Perhaps 4,000 patterns was intended the whole time, but somehow that got messed up and 65,000 was used instead. That (65,000) is a good number though (but perhaps not quite a good as 65,536, as it is a power of 2 and those are good numbers, but that is 4,096 × 16, so that is not that big of a deal).
Wow, what a helpful posts of "I don't know"s... ::)
RWP: It tell you something now, and I really mean this.
I would appreciate it if you stopped mentioning that you don't like what we fixed and if you stopped molesting (at least I consider this molesting) us via Forum PM. We know that the limit has been decreased, ok?! Stop telling us with all those mathematical equations that you need 64,000 empty patterns + 1,000 patterns being filled with one or two notes to look at. We (at least I) don't care. We care about a stable OpenMPT, and many parts of the program were unstable when this insanely high limit existed. Everytime I have to deal with the order list I see why it was a good idea to reduce the limit. Just to mention yet another example, it was (and still is) impossible to play certain order list items > 0x8000 using the treeview.
Seriously. Just stop bugging is with that.
I do not recall ever mentioning that I did not like what was done. Perhaps you are overreacting due to the mentioning of the pattern limit (and/or the parts that mentioned the multipattern selection and overflow paste being implemented sooner) and superimposing that on everything else. If that is the case, I cannot help you, as how you react to my posts is your decision, not mine.
QuoteJust to mention yet another example, it was (and still is) impossible to play certain order list items > 0x8000 using the treeview.
Perhaps I am misinterpreting that, but I used both the patterns folder and the sequence folder and double clicked four numbers (I think that the first one may have been random, the second one was [pattern] 255, the third was [pattern] 256, and the fourth was [pattern] 16,766 and none of them seemed to have any problems. I will tell you this though. The extended limit has indeed caused two main problems. There are no others that I notice because of it though.
Problem #1: In the pattern row, when scrolling past pattern 32,821 using the scroll bar, the display goes to the beginning again. The scroll bar's position is not reset, but the pattern row is. I tested this wih a shorter song to see if the problem is proportional (meaning that it would have occurred with the scroll bar at the same position) or positional (meaning position 32,820) and it appears to be positional.
Problem #2: The one I mentioned before about the five-digit number chopping on the display. This does not seem like it would be too hard of a fix though.
There is also a problem with the position jump, but I think that would have to do with the position jump itself and the fact that it is not updated to reflect either of the new limits, not the extended pattern limit.
Quote from: "Really Weird Person"
Perhaps I am misinterpreting that, but I used both the patterns folder and the sequence folder and double clicked four numbers (I think that the first one may have been random, the second one was [pattern] 255, the third was [pattern] 256, and the fourth was [pattern] 16,766 and none of them seemed to have any problems. I will tell you this though. The extended limit has indeed caused two main problems. There are no others that I notice because of it though.
I was talking about orders, not patterns. When executing an order item from the tree, it will always be ORed with 0x8000, meaning order items that should not have bit 0x8000 set would be interpreted wrong.
And I don't care about problem #1 and #2, because they have
luckily been fixed by reducing the order limit, and no, they won't be fixed by increasing the limits again. And I would kindly prompt you not not mention this damn order/pattern limit again. Thank you.
I have noticed in the past where I am making a song (of the full length) where the patterns appear to be misplaced. Perhaps that is what you are referring to. I think that I can only recall one time where that happened though. Perhaps it has happened more than that to you, I am not sure. As for the problems not being fixed, that is true. They will not fix themselves indeed. I think that it has long become obvious that you are against such an addition. I have no idea if you are against the backward compatibility that doing that would also provide, but that aspect I would imagine you are not necessarily against. Perhaps the problem is that you do not want to be personally responsible for any problems that such a feature may impose, which is completely understandable.
Now that the new version is out (actually long ago) I want to ask, is there a possibility to send aftertouch messages to them synths using this brand new parameter control command or something?
No, because that would be a MIDI CC. PC Notes can only control, well, parameters.
So we still can't send aftertouch? And is it possible to send MIDI CC using something as cool as PC notes?
Should I fill a request or it is already in the pipeline?
:wink:
At least I didn't plan such a thing; I dunno about Relabs' plans, though ;)
But IMO, it's more important to pump out a new "official" release before adding any new features.
I guess it would be not too much of a new feature, just a logical ...um, forgot the damn word... shit:-)
I am not sure what word Nahkranoth is referring to with that post. My guess is the word feature, but I am also guessing that it is certainly not the word profanity, because he used plenty of it.
...CONTINUATION! That's the right word. Still wondering how I could forget this one :D
2RWP: yeah, say "profanity" - and here I am :lol:
<insert random profanity here, just to annoy RWP>
Nahkranoth, I can guess that it's not much of a "big" feature, but it still is a feature which needs to be tested before a release can be made. And I want to have a release being made rather sooner than later.
If you wish, I can test those features concerning CC and aftertouch, yeah baby :wink:
When they will be available of course.
How, when they don't even exist yet? :nuts:
(I know what you mean :P)
Edited just before I saw your response :D
Quote<insert random profanity here, just to annoy RWP>
Unfortunately, I think that I could possibly see everybody doing that. After all, it seems to have become the world's second language of choice.
Quote from: "Really Weird Person"... I could possibly see everybody doing that....
<insert random profanity here, just to annoy RWP> :nuts: :lol:
Quote from: "Really Weird Person"After all, it seems to have become the world's second language of choice.
Become? Oooooooh come on, don't tell me the ancient romans and greeks didn't know profanity 2000 years ago!
Quote from: "Jojo"Quote from: "Really Weird Person"After all, it seems to have become the world's second language of choice.
Become? Oooooooh come on, don't tell me the ancient romans and greeks didn't know profanity 2000 years ago!
Then again, one would think we had evolved a little (socially and culturally) since then... I don't mind cuss words, but they lose their meaning if you use them all the time. Profanities without meaning have no purpose besides making the person saying them appear ignorant. So please, my friends, give it up; that fucking shit is pissing the ass off of me.
Sincerely,
g
I tried time stretching a sample in the new (this version) OMPT yesterday and ran into an error saying OMPT couldn't find a library. "failed to load soundtouch library"
I've just downloaded the binary for the library.
Can someone give me a clue as to what to do to make this functional?
Thanks,
Chris
Download the official 1.17.02.54 package first, then put the new exe file (this one) over the 1.17.02.54 one.
ok thank you, I'll try that.
thank you - I got it working just by dropping it into the same folder even being named for its version.
I keep each version - named with version number - not sure why... but there it is.
ok,
for what it is worth, 3.XX works fine in Vista 64 including VSTi's - and funky enough, a VSTi (real guitar) that won't load and work in Sonar (32 bit) will work in OMPT.
Nice to hear that. OpenMPT also works on Vista64 and Win7 64 here as well.