ModPlug Central

OpenMPT Development (Archive) => Bug Reports => Bug Report Archive => Topic started by: rewbs on October 18, 2005, 22:41:10

Title: .41 Temporary test build bug report thread
Post by: rewbs on October 18, 2005, 22:41:10
Update:

Note: from v1.17.02.40, we store the plugin cache on the file system rather than in the registry. If you have lots of plugs listed in your mptrack.ini, your first startup will be a bit slow since we need to rebuild the cache.  You might get some errors if plugins have been removed / have expired etc... Subsequent startups should be just fine.

Latest builds are here: http://modplug.sourceforge.net/builds/#dev
Title: .41 Temporary test build bug report thread
Post by: Squirrel Havoc on October 19, 2005, 00:48:34
Uh, are you sure you pasted the right link? I get taken to a stats page when I click it. Will it be at that page in a few hours?
Title: .41 Temporary test build bug report thread
Post by: speed-goddamn-focus on October 19, 2005, 06:13:47
http://cvs.sourceforge.net/viewcvs.py/modplug/wild/mptrack/bin/Attic/mptrack_Generic.exe?hideattic=0&only_with_tag=OpenMPT_1_17RC
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on October 19, 2005, 07:22:07
:D fukk, i still got 7 hours to work until i can get my hands on it
Title: .41 Temporary test build bug report thread
Post by: rewbs on October 19, 2005, 08:17:13
Quote from: "Squirrel Havoc"Uh, are you sure you pasted the right link? I get taken to a stats page when I click it. Will it be at that page in a few hours?
D' oh! Still learning to use multiple clipboards.  :oops:
Thanks speed-goddamn-focus.
Still, the stats (http://sourceforge.net/project/stats/detail.php?group_id=100385&ugn=modplug&type=prdownload&mode=60day&package_id=110953&release_id=350443&file_id=0) are quite interesting no? notice how the 1.17RC2 downloads trippled when modplug.com was linking to this forum (which has clear up-to-date download links), but dropped again as soon as the modplug.com redirect broke.
Title: .41 Temporary test build bug report thread
Post by: Rakib on October 19, 2005, 13:28:36
well, of course. Modplug.com is the source everybody relyon when talking about mpt software
Title: .41 Temporary test build bug report thread
Post by: Rakib on October 19, 2005, 13:33:19
/ <rewbs> experimental: muting a channel with a VSTi playing should turn off the active note on that channel.
<----tnx this was something i was really waiting for
Title: Re: Temporary test build bug report thread
Post by: Relabsoluness on October 19, 2005, 19:14:28
Quote from: "rewbs"Note delay (SDx) is written automatically during "live tracking" if there are no effects already on the row.
With my poor playing skills, I get quite realistic sounding recordings with the autodelay, so at least it's working quite well. But it would be really nice to hear other comments on how good results can really be obtained with it.
There seemed to be a small bug in the feature; for s3m-file the delay command wasn't written correctly - it wrote command of style ?D2.
Title: .41 Temporary test build bug report thread
Post by: Rakib on October 20, 2005, 18:57:19
muting a channel with a VSTi playing should turn off the active note on that channel. <--- this thing only works when a vsti is not assigned to a vst effect. If it is, the muting of the vsti channel is not working.

edit: well. it does, but in a effect called bj lofi, a small piece of the sample is looping and not stopping. Maybe another vst effects have the same issue
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on October 21, 2005, 06:46:11
Quote from: "Rakib"muting a channel with a VSTi playing should turn off the active note on that channel. <--- this thing only works when a vsti is not assigned to a vst effect. If it is, the muting of the vsti channel is not working.

edit: well. it does, but in a effect called bj lofi, a small piece of the sample is looping and not stopping. Maybe another vst effects have the same issue

i'll also have a look on this when i get home...

version seems to work fine for my purposes  :D

but please hurry on the conversion of pattern effects to macros  8)
(most important: VOLUME)
Title: .41 Temporary test build bug report thread
Post by: Rakib on October 24, 2005, 00:25:24
no else has encountered this problem?? ::)
Title: .41 Temporary test build bug report thread
Post by: speed-goddamn-focus on October 24, 2005, 05:37:33
Quote from: "Rakib"no else has encountered this problem?? ::)

I haven't tried, but I believe you.
Title: .41 Temporary test build bug report thread
Post by: Squirrel Havoc on October 24, 2005, 17:05:35
Found a serious bug. If you create a new song, it will be titled "Module1". If you click the save button on the main toolbar, it will ask where to save it and what to call it. BUT, if you click on "Song Properties", then click "Ok", the title of the song gets changed to "Module1.it". Now when you click the save button, it will save it as "Module1.it", overwriting your original Module1.it! Luckily I have backup song enabled, but if I didn't, I would have lost a song (when I cant think of a name, I go with the default Module1.it until I name it).

All the more reason that you should backup your work from time to time...
Title: .41 Temporary test build bug report thread
Post by: Rakib on October 25, 2005, 08:17:17
same if you open a wavefile as a file and you accidentally press the save button, it will erase any file that is called module1.it. I lost one of my best songs that way :(
Title: .41 Temporary test build bug report thread
Post by: rncekel on October 28, 2005, 13:11:31
I think this is not new, but in the Edit menu, Cleanup, the Rearrange Samples doesn't work. Well, in fact it is worst, because it mess up the samples.
Title: .41 Temporary test build bug report thread
Post by: rewbs on October 28, 2005, 15:09:22
Quote from: "rncekel"I think this is not new, but in the Edit menu, Cleanup, the Rearrange Samples doesn't work. Well, in fact it is worst, because it mess up the samples.

With all tracks?
If not, can you provide the simplest possible track which gets messed up on cleanup samples?
Title: .41 Temporary test build bug report thread
Post by: rncekel on October 28, 2005, 16:38:38
Here you have a silly but very small example of what happens
http://www.oocities.com/rncekel/prueba1.it

Instrument 3 is really a triangle. But if you open the Edit menu->Cleanup-> Rearrange samples, instrument 2 will still point out to sample 3, that will now be empty.
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on October 29, 2005, 11:12:09
btw: this version threw some of my vsti out of the list
Title: .41 Temporary test build bug report thread
Post by: Squirrel Havoc on October 29, 2005, 21:21:55
Well, it's a new modplug, i got a new computer (same OS, Win2K Pro), and new everything. And just when I thought it was over, shutting down MPT caused a halt on my computer, and I had to reboot. I can't remember what kind of halt it was, but ive never seen it before.

Onlything really different this time is I upgraded to the newest WinAmp (which also crashes a lot more than it used to).

I know you can't reproduce this bug, so don't spend too much time thinking about it, just think about it whenever you mess with the shutdown code  8)
Title: .41 Temporary test build bug report thread
Post by: LPChip on October 29, 2005, 21:49:52
Quote from: "Squirrel Havoc"Well, it's a new modplug, i got a new computer (same OS, Win2K Pro), and new everything. And just when I thought it was over, shutting down MPT caused a halt on my computer, and I had to reboot. I can't remember what kind of halt it was, but ive never seen it before.

Onlything really different this time is I upgraded to the newest WinAmp (which also crashes a lot more than it used to).

I know you can't reproduce this bug, so don't spend too much time thinking about it, just think about it whenever you mess with the shutdown code  8)

This sounds more like an unstable windows install...

I've had after a fresh install that windows just didn't run well... For instance, it could crash if I tried to open IE. Only way to fix it was to reinstall windows.
Title: .41 Temporary test build bug report thread
Post by: rewbs on October 29, 2005, 23:18:57
Quote from: "Squirrel Havoc"I know you can't reproduce this bug, so don't spend too much time thinking about it, just think about it whenever you mess with the shutdown code  8)

I haven't touched shutdown code in ages, but that doesn't mean there isn't an intermittent issue.
Title: .41 Temporary test build bug report thread
Post by: Squirrel Havoc on October 30, 2005, 15:31:56
Quote from: "rewbs"
Quote from: "Squirrel Havoc"I know you can't reproduce this bug, so don't spend too much time thinking about it, just think about it whenever you mess with the shutdown code  8)

I haven't touched shutdown code in ages, but that doesn't mean there isn't an intermittent issue.

Sometimes I wonder if it's my computer, because other MIDI capable programs have done the same in the past (not as often though)
Title: v. 1.17.02.35 (1.17RC3_)
Post by: Matt Hartman on November 04, 2005, 14:34:15
Hypersonic VSTi crash when selecting edit under vst effects menu .

message me if you *need* Hypersonic for uh...testing purposes.
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 08, 2005, 19:08:39
QuoteHypersonic VSTi crash when selecting edit under vst effects menu
You got a crash when trying to open the plugin GUI?
How consistent is this? So far I can't reproduce any crashes with Hypersonic v1.12.808. Nice plug by the way.
Title: .41 Temporary test build bug report thread
Post by: Matt Hartman on November 08, 2005, 20:26:56
QuoteYou got a crash when trying to open the plugin GUI?
How consistent is this?

Precisely.
It's every time I try to load actually. MPT slaps up an unexpected error screen.

QuoteSo far I can't reproduce any crashes with Hypersonic v1.12.808.

This is frustrating so.  :x

QuoteNice plug by the way.

I wouldn't exactly know...  :(
Title: .41 Temporary test build bug report thread
Post by: anboi on November 08, 2005, 21:02:13
i still have weird performance issues i mentioned in another thread but have not had time to track down which version number they start at, here are some other things i noticed lately:


Possible bugs:

using reorder/remove in the channel manager makes the wrong channels be muted/unmuted according to the markings but plays back correctly. fixed by going out f pattern view then back in.

something weird with the screen redraw in some instances when changing to pattern view from something. (possibly involves 2 tunes open and closing one while behind is the pattern view showing in the other tune). it basically leaves big blocks of grey where there should be buttons.

think there is a bug where trying to play a note lower than G#-0 results in... nothing! d'oh! tried with a few samples but nothing seemed to work, i might have done something stupid here again...

bug with setting of highlighting - seems to check the highlight values are valid or not against an old model that doesn't take into account new tempo modes so when set to bpm is highlighted then it objects. it complains about  primary highlight needing to be higher value than secondary or something along those lines. i think i was using modern bpm settings.

strange behaviour:

when typing in instrument allocations (which sample is mapped to which note in the instrument view) changing the pitch moves the cursor down (annoyingly) after entering it, but changing sample number does not. also logic of order is silly. pitch - pitch - sample no. should be pitch - sample -pitch so it can be read sensibly as 'when playing note X do so with sample Y at note Z'
again in this section clicking miles up on note part only moves it up one, instead of jumping to where clicked, seems strange.

can't type user wave names into imposcar cos modplug steals the keypresses. probably the case with other vstis with their own interfaces for stuff?

sorry for not having all the necessary info in some cases but i think most are relatively clear, i'll try and help as much as possible with any specifics you might need.
Title: .41 Temporary test build bug report thread
Post by: Squirrel Havoc on November 08, 2005, 21:22:56
Here's one I bet no one could answer.

Has anyone got MPT working under Linux, with 2 soundcards? One integrated (which is the one MPT tries to use, but I dont use it), and one PCI that I want to use, but it doesnt register.

Now THAT's a tech support question!  :lol:
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 09, 2005, 19:21:07
Matt - Can I check exactly which version of MPT and Hypersonic you're using?

anboi - thanks for the notes, will take a look.

Squirrel - no idea, do other apps in Wine detect the card?
Title: .41 Temporary test build bug report thread
Post by: Squirrel Havoc on November 10, 2005, 00:40:47
Quote from: "rewbs"Squirrel - no idea, do other apps in Wine detect the card?

Yeah it's weird, MPP works just fine. I was thinking it could be that Wine doesn't understand the instructions for a P4, so I switched to generic version. Same thing, hangs when i hit "play".

Anyone know the right place to ask this kind of question? I really dont want Rewbs thinking too hard about this :)
Title: .41 Temporary test build bug report thread
Post by: VSh on November 11, 2005, 15:46:27
Can I report a bug here?

OpenMPT 1.17.02.28, Windows XP.

If Midi Library was imported from some SF2 file with stereo samples and some midi file was opened after that, samples aren't recognized as stereo (only mono) and midi sounds very bad.
Title: .41 Temporary test build bug report thread
Post by: grantek on November 12, 2005, 05:17:34
Quote from: "Squirrel Havoc"Here's one I bet no one could answer.

Has anyone got MPT working under Linux, with 2 soundcards? One integrated (which is the one MPT tries to use, but I dont use it), and one PCI that I want to use, but it doesnt register.

Now THAT's a tech support question!  :lol:
If you don't use any 2-card functionality, just disable the internal one in the BIOS.
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 12, 2005, 15:11:05
anboi,

Quote from: "anboi"i still have weird performance issues i mentioned in another thread but have not had time to track down which version number they start at
Let me know when you do, I'm eager to figure that one out. :)

Quoteusing reorder/remove in the channel manager makes the wrong channels be muted/unmuted according to the markings
Thanks, fix will be in next revision.

Quotesomething weird with the screen redraw in some instances when changing to pattern view from something
Hmm I think I need more info to reproduce that one.

Quotetrying to play a note lower than G#-0 results in... nothing! d'oh!
For IT files, there's a hard coded upper limit for the period length (which goes up when the freq goes down). Has been there since pre-open source days.  I couldn't figure out the rational for that limit, so it will experimentally be removed in the next revision. Look out for bugs that kick in at very low notes.

Quotebug with setting of highlighting - [...] it complains about  primary highlight needing to be higher value than secondary or something along those lines
Are you sure this is a bug? When highlighting is set to match time signatures, the rows/beat will be used for secondary highlights, and the rows/measure will be used for primary highlights. It is normal that the latter must be greater, since you should have at least one beat per measure. Does that clarify things or does it still feel wrong?


Quotewhen typing in instrument allocations (which sample is mapped to which note in the instrument view) changing the pitch moves the cursor down [...] clicking miles up on note part only moves it up one, instead of jumping to where clicked, seems strange.
Agreed that this is irritating, will be changed in next revision.

Quotealso logic of order is silly. pitch - pitch - sample no. should be pitch - sample -pitch
I kind of agree, but don't think it's worth changing since many people will be used to the current layout and will yell at a swap. Certainly not worth the effort of making it an option...

Quotecan't type user wave names into imposcar cos modplug steals the keypresses.
I have added a "Pass keypresses to plug" switch available from the pluginwindow's "options" dropdown menu; will be in next revision.


Quotesorry for not having all the necessary info in some cases but i think most are relatively clear, i'll try and help as much as possible with any specifics you might need.
Thanks.
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 12, 2005, 15:12:53
Hi VSh, thanks for the bug report.

Quote from: "VSh"If Midi Library was imported from some SF2 file with stereo samples and some midi file was opened after that, samples aren't recognized as stereo (only mono) and midi sounds very bad.

Hmm yeah SF2 support is a bit flaky, not sure how much time I will be able to invest in improving it. Can you point me to the specific SF2 file you're using?
If there's a quick fix I'll check it out.
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 12, 2005, 17:18:22
I'm just uploading v1.17.02.36. See beginning of thread for details.
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on November 12, 2005, 17:26:54
Quote(+ <rewbs> volume commands without notes now send volume MIDI CC to plugs, but as far as I've seen, no plugs seem to respond to it.)

:cry: damn


wow, my name as betatester is in the product-info  :D

thx man
Title: .41 Temporary test build bug report thread
Post by: Anonymous on November 12, 2005, 19:55:59
Quote from: "rewbs"Hi VSh, thanks for the bug report.
Thank you for this good tracker.
Quote from: "rewbs"Hmm yeah SF2 support is a bit flaky, not sure how much time I will be able to invest in improving it. Can you point me to the specific SF2 file you're using?
It is the best to try with Reality_GMGS.SF2 from sf2midi.com. Some samples sound good (as "52: Choir Aahs" or "10: Music Box"), but "0: Piano 1" sounds very bad in midi.
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 12, 2005, 20:30:26
Quote from: "rncekel"Here you have a silly but very small example of what happens
http://www.oocities.com/rncekel/prueba1.it

Instrument 3 is really a triangle. But if you open the Edit menu->Cleanup-> Rearrange samples, instrument 2 will still point out to sample 3, that will now be empty.

Sorry rncekel, i forgot to put the fix for this in the latest build. The problem is a small typo that prevents the last intrument from being adapted to the new sample positions. Fix will be in next revision. Meanwhile you can add a dummy instrument in the last position before doing re-arrange samples, and all should be fine.
Title: .41 Temporary test build bug report thread
Post by: rncekel on November 13, 2005, 09:38:34
I don't know what happens, I supposed I am doing something wrong, but I can't find the new version 1.17.02.36, but the old one 1.17.02.35.
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 13, 2005, 12:03:04
Quote from: "rncekel"I don't know what happens, I supposed I am doing something wrong, but I can't find the new version 1.17.02.36, but the old one 1.17.02.35.

No you're probably looking in the right place, but Sourceforge's CVS web frontend is taking ages to update.
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on November 13, 2005, 17:14:03
still not there  :cry:
Title: .41 Temporary test build bug report thread
Post by: Relabsoluness on November 13, 2005, 20:46:08
Quote from: "rewbs"
Quote from: "rncekel"I don't know what happens, I supposed I am doing something wrong, but I can't find the new version 1.17.02.36, but the old one 1.17.02.35.

No you're probably looking in the right place, but Sourceforge's CVS web frontend is taking ages to update.
No new files are available even when using cvs-update - shouldn't it be updated much faster than the web frontend?
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 13, 2005, 22:40:12
Quote from: "Relabsoluness"
Quote from: "rewbs"
Quote from: "rncekel"I don't know what happens, I supposed I am doing something wrong, but I can't find the new version 1.17.02.36, but the old one 1.17.02.35.

No you're probably looking in the right place, but Sourceforge's CVS web frontend is taking ages to update.
No new files are available even when using cvs-update - shouldn't it be updated much faster than the web frontend?

Yes hmmm... maybe I didn't commit properly. I've recommitted.
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 14, 2005, 11:41:16
Relabsoluness, can you try CVS update again?
I think I'm in sync with the repository, but the web frontend is still not updating.
Title: .41 Temporary test build bug report thread
Post by: LPChip on November 14, 2005, 13:31:00
Quote from: "rewbs"Relabsoluness, can you try CVS update again?
I think I'm in sync with the repository, but the web frontend is still not updating.

On my end, the download points to rev. 35, and checkout is empty.

http://cvs.sourceforge.net/viewcvs.py/modplug/ModplugCheckout/?
Title: .41 Temporary test build bug report thread
Post by: Squirrel Havoc on November 14, 2005, 13:31:23
I'll check out the new update with my Linux box. Just so you know, CVS is still reporting the old version
Title: .41 Temporary test build bug report thread
Post by: Squirrel Havoc on November 14, 2005, 13:32:32
Quote from: "grantek"
Quote from: "Squirrel Havoc"Here's one I bet no one could answer.

Has anyone got MPT working under Linux, with 2 soundcards? One integrated (which is the one MPT tries to use, but I dont use it), and one PCI that I want to use, but it doesnt register.

Now THAT's a tech support question!  :lol:
If you don't use any 2-card functionality, just disable the internal one in the BIOS.

I did disable it acutally. MPP works fine, and even with my internal sound card selected. I think it has something to do with the options I've set in MPT, so I'll goof off, and report what settings I used if I can get it to work. I know other people use is with Wine, so I should be able to as well
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 14, 2005, 14:31:34
Quote from: "LPChip"
Quote from: "rewbs"Relabsoluness, can you try CVS update again?
I think I'm in sync with the repository, but the web frontend is still not updating.

On my end, the download points to rev. 35
Yes, like I said the web frontend doesn't seem to be updating, which is why I asked Relabsoluness to try accessing the CVS repository directly. I tried myself just now and was able to pull down rev 1.17.02.36... So if the web front end isn't up to date by tomorrow I'll raise a problem with Sourceforge.

Quote from: "LPChip", and checkout is empty.
http://cvs.sourceforge.net/viewcvs.py/modplug/ModplugCheckout/?
And what do you think that means? AFAIK ModplugCheckout is just a garbage directory I created when I was learning the CVS thing. Have you ever seen it not empty?
Title: .41 Temporary test build bug report thread
Post by: LPChip on November 14, 2005, 15:17:39
Quote from: "rewbs"
Quote from: "LPChip"
Quote from: "rewbs"Relabsoluness, can you try CVS update again?
I think I'm in sync with the repository, but the web frontend is still not updating.

On my end, the download points to rev. 35
Yes, like I said the web frontend doesn't seem to be updating, which is why I asked Relabsoluness to try accessing the CVS repository directly. I tried myself just now and was able to pull down rev 1.17.02.36... So if the web front end isn't up to date by tomorrow I'll raise a problem with Sourceforge.

Quote from: "LPChip", and checkout is empty.
http://cvs.sourceforge.net/viewcvs.py/modplug/ModplugCheckout/?
And what do you think that means? AFAIK ModplugCheckout is just a garbage directory I created when I was learning the CVS thing. Have you ever seen it not empty?

LOL, You could also ask: Have you seen it before? :P

I remember from the history that url's used to contain *checkout*, so I though that this directory might be where new files came or so :P

Rewbs, can you perhaps upload the exe manually and link it for us? Or perhaps link to the CVS... I dunno how this works...
Title: .41 Temporary test build bug report thread
Post by: Relabsoluness on November 14, 2005, 20:06:53
Quote from: "rewbs"Relabsoluness, can you try CVS update again?
I think I'm in sync with the repository, but the web frontend is still not updating.
Still no new files seem to be there.
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 15, 2005, 01:59:17
CVS definitely contains version 1.17.02.36. I'm writing up a simple script to make the bleeding edge dev builds available more quickly and more presentably than via sourceforge's cvs web frontend, should be ready by the end of the week. Meanwhile they are available crudely here: http://modplug.sourceforge.net/builds/storage/bin/
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on November 15, 2005, 14:07:57
values in the volume column don't seem to work right...
only with certain VSTi and on some only from 32 oder even 16 to 00
and as you said only in combination with a note

:cry:
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 15, 2005, 14:17:46
Quote from: "BooT-SectoR-ViruZ"values in the volume column don't seem to work right...
only with certain VSTi and on some only from 32 oder even 16 to 00
and as you said only in combination with a note

What do you mean "don't seem to work right"? Are you saying there's a new problem with volume in this build? Also I can't do anything unless you give the names of the VSTis explicitly (you should know  that by now. ;) ).

Notes with a volume value in the pattern use the volume value to set the VSTi's note velocity This has been the case since pre open source days. Check your VSTi is configured to respond to velocity. If it can't respond to velocity, you're screwed.

The new "feature" is that volume values in the pattern without a corresponding note send volume MIDI CCs. Unfortunately, I have not yet found a VSTi that responds to this CC.

Next I will try to make volume commands affect the dry/wet ratio so you don't have to go through macros... but obviously the downside here is that it will be impossible to control volume for individual notes when playing a chord.
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on November 15, 2005, 14:41:46
Quote from: "rewbs"
Quote from: "BooT-SectoR-ViruZ"values in the volume column don't seem to work right...
only with certain VSTi and on some only from 32 oder even 16 to 00
and as you said only in combination with a note

What do you mean "don't seem to work right"? Are you saying there's a new problem with volume in this build? Also I can't do anything unless you give the names of the VSTis explicitly (you should know  that by now. ;) ).

jupp, but i'm too lazy right now ;)
Title: .41 Temporary test build bug report thread
Post by: LPChip on November 15, 2005, 15:05:27
Quote from: "rewbs"
Next I will try to make volume commands affect the dry/wet ratio so you don't have to go through macros... but obviously the downside here is that it will be impossible to control volume for individual notes when playing a chord.

Can't you create a new effect for that? eg: v64 controls volume, so w64 controls the dry/wet ratio. Perhaps you can do this with slide to volume aswell? (dxx)
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 15, 2005, 15:16:55
Quote from: "LPChip"
Quote from: "rewbs"
Next I will try to make volume commands affect the dry/wet ratio so you don't have to go through macros... but obviously the downside here is that it will be impossible to control volume for individual notes when playing a chord.

Can't you create a new effect for that? eg: v64 controls volume, so w64 controls the dry/wet ratio. Perhaps you can do this with slide to volume aswell? (dxx)

We can't easily add more effects to the vol column since we only have a byte to represent that slot... this can of course be improved, but for now my plan is to try to find a satisfactory way of controlling VSTi volume "like samples" (I was hoping to not have to fall back on wet/dry because of the issues with polyphony, but it seems like the best method for now).
I can confirm that when a method has been settled upon, volume slide effects will be adapted to use it, and we can think about introducing new effect letters to clarify the subtle differences between "types of volume control".
Title: .41 Temporary test build bug report thread
Post by: LPChip on November 16, 2005, 14:27:27
Hmm, Can you try sending a midi note with different volume with a tone portamento? This is how most older midi programs do a volume change.

they send a note-on with volume, but in such way that the note itself isn't being triggered.

We could make mpt trigger it by not providing a note, but do provide the instrument number and volume:

C-4 01 v64
--- 01 v40
etc...
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 16, 2005, 14:49:42
Quote from: "LPChip"Hmm, Can you try sending a midi note with different volume with a tone portamento? This is how most older midi programs do a volume change.

they send a note-on with volume, but in such way that the note itself isn't being triggered.

Don't forget to distinguish volume and velocity when describing behaviour of MIDI apps, else I'm going to get confused. :) I think all occurences of volume in what you just said could be replaced with velocity, except "this is how most older midi programs do a volume change", right?

Are you suggesting you set the portamento time CC to min, set portamento on, issue a new note with a new velocity, and expect that to change the volume of the prior note? What if the device doesn't support portamento? I'd be very suprised if this works as you imagine, but I'd love to be wrong... Can you give me an example of a MIDI program which work like that? I'd like to try.

(The idea of changing the volume of an individual note during that note is a very tracker-esque thing; I just don't think it is possible in MIDI which models more realistic instrument behaviour.)
Title: .41 Temporary test build bug report thread
Post by: LPChip on November 16, 2005, 17:50:54
Quote from: "rewbs"
Quote from: "LPChip"Hmm, Can you try sending a midi note with different volume with a tone portamento? This is how most older midi programs do a volume change.

they send a note-on with volume, but in such way that the note itself isn't being triggered.

Don't forget to distinguish volume and velocity when describing behaviour of MIDI apps, else I'm going to get confused. :) I think all occurences of volume in what you just said could be replaced with velocity, except "this is how most older midi programs do a volume change", right?

Are you suggesting you set the portamento time CC to min, set portamento on, issue a new note with a new velocity, and expect that to change the volume of the prior note? What if the device doesn't support portamento? I'd be very suprised if this works as you imagine, but I'd love to be wrong... Can you give me an example of a MIDI program which work like that? I'd like to try.

(The idea of changing the volume of an individual note during that note is a very tracker-esque thing; I just don't think it is possible in MIDI which models more realistic instrument behaviour.)

Back then, the program I used was Magix music studio deluxe. I used it to do this tracker-ish thing. :)
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on November 16, 2005, 20:44:25
new bug:

"initial panning" of 256 on a channel (general tab) will cause mute on VSTi playing on that channel

(so far only tested with slayer2... sort of accident while tracking ;))

no effect on pentagon I & junoX2... hmm... maybe it's a bug in slayer2...
Title: .41 Temporary test build bug report thread
Post by: rncekel on November 17, 2005, 09:11:23
To rewbs: changing the volume of a note while playing it is very often used in real instrument playing. Not, of course, in percuted ones (except in rolls, that do use it), but very often in wind instruments and in bowed strings.
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 17, 2005, 09:30:15
Quote from: "rncekel"To rewbs: changing the volume of a note while playing it is very often used in real instrument playing. Not, of course, in percuted ones (except in rolls, that do use it), but very often in wind instruments and in bowed strings.

Good point. Maybe MIDI devices that model such instruments would respond  to specific MIDI CCs (such as breath, expression, brightness? don't know...) that have the effect of attenuating/enhancing specific notes or MIDI channels during a note. But I can't find a generic way that has also been picked up by VSTis.
Title: .41 Temporary test build bug report thread
Post by: LPChip on November 17, 2005, 12:31:05
SourceForge has updated their page finally, but now there are 2 .36 revisions :P
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 17, 2005, 12:34:06
Quote from: "LPChip"SourceForge has updated their page finally, but now there are 2 .36 revisions :P
Hehe nevermind. :)
I'm writing some scripts to automatically publish dev builds to a separate page so we won't be dependant on that system for much longer.
Title: .41 Temporary test build bug report thread
Post by: LPChip on November 17, 2005, 13:45:40
Quote from: "rewbs"
Quote from: "LPChip"SourceForge has updated their page finally, but now there are 2 .36 revisions :P
Hehe nevermind. :)
I'm writing some scripts to automatically publish dev builds to a separate page so we won't be dependant on that system for much longer.

Nice. Then we can alter the download page too I guess?
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 22, 2005, 00:27:51
Here it is: http://modplug.sourceforge.net/builds/index.php
It's all driven off RSS - the direct links to the xml feeds are provided.
It should get updated instantly when I commit new binaries, so no more hanging around for sourceforge's web interface.
LP, I'll update the downloads page when I've committed a few builds to confirm it works OK. :D
Title: .41 Temporary test build bug report thread
Post by: Squirrel Havoc on November 22, 2005, 00:37:14
Quote from: "rewbs"Here it is: http://modplug.sourceforge.net/builds/index.php
It's all driven off RSS - the direct links to the xml feeds are provided.
It should get updated instantly when I commit new binaries, so no more hanging around for sourceforge's web interface.
LP, I'll update the downloads page when I've committed a few builds to confirm it works OK. :D

Hey, thats a slick looking interface. Good job!  :wink:  8)  ;D
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 22, 2005, 00:39:22
Quote from: "Squirrel Havoc"Hey, thats a slick looking interface. Good job!  :wink:  8)  ;D

Thanks! Actually I just noticed it's screwed up in IE. :P
I'll sort that out tomorrow.
Title: .41 Temporary test build bug report thread
Post by: LPChip on November 22, 2005, 10:56:36
Nice, and noted :)
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on November 22, 2005, 18:42:26
somehow values in the volume column seem to have some effect on the sound of "Pentagon I"

this is strange, because it didn't happen immediately, but after some minutes :shock:

(i made a simple fade-in from 0-64)

rewbs, can you check that?

i'm now rebooting my system to check if it's still there afterwards
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on November 22, 2005, 18:53:11
hmmm... still there  :cry:
Title: .41 Temporary test build bug report thread
Post by: rewbs on November 22, 2005, 18:55:57
Quote from: "BooT-SectoR-ViruZ"somehow values in the volume column seem to have some effect on the sound of "Pentagon I"
Is this with or without a note on the same row?
It it occurs on the same row as a note, the value in the volume column represents the velocity of that note. Pentagon I has parameters you must set to define how much variations in velocity affect the volume and the filter. This is the case with many VSTis.

Perhaps initially these parameters were at 0, so velocity had no effect. Then you changed the params so velocity had an impact.
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on November 22, 2005, 18:59:15
think it's as you suppose...

great, so it seems like this is unavoidable  :(
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on December 03, 2005, 15:07:29
Macro-Problem:

i'm sending "JunoX2" to "Classic EQ"
now i want to control "Classic EQ" via macro (e.g. param 57)
but my macro does not affect "Classic EQ" at all.
it only changes param 57 of "JunoX2"

==> not so cool

had this problem with several VSTi in the last time...

macros shouldn't controll FX-params globally and i think they didn't in the old build
Title: .41 Temporary test build bug report thread
Post by: rewbs on December 03, 2005, 15:09:39
Quote from: "BooT-SectoR-ViruZ"I'm sending "JunoX2" to "Classic EQ"
now i want to control "Classic EQ" via macro (e.g. param 57)
but my macro does not affect "Classic EQ" at all. it only changes param 57 of "JunoX2"

You simply need to assign Classic EQ directly to a separate channel and put your macro commands there.
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on December 03, 2005, 15:10:44
hmmm... k
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on December 06, 2005, 12:51:36
news:

"Plugsound Free" can not be controlled via macros  :cry:

no params to choose from

download here: http://www.usbsounds.com/jsp/demos.jsp

@rewbs: any idea how to manage that one?

btw: it also doesn't respond to values in the volume column correctly
Title: 2 rewb! problem: mute channel = STOP CHANNEL
Post by: Spanky on December 07, 2005, 18:03:15
2 rewb!
Old problem of all releases of ModPlug Tracker and OpenMPT:
mute channel = STOP CHANNEL

in Impulse Tracker, FT2 and maybe others

mute channel = MUTE CHANNEL  (!!! Channel Volume=0 !!! )

Because of this feature OpenMPT couldn't be used in live sessions.
WANTED TO BE FIXED!  
SOS ! SOS ! SOS !
Title: .41 Temporary test build bug report thread
Post by: rewbs on December 07, 2005, 19:10:23
BSV - looks like it can only be controlled with MIDI CCs. I will improve the macro config GUI to make it more simple to setup macros for MIDI CCs asap.

Spanky - I feel your pain. Some people already use MPT live so I suppose they are used to the way it currently works. I'll see what is involved in adding an option which lets sample and envelope positions increase when the chan is muted.
Title: 2rewbs synchronization
Post by: Spanky on December 07, 2005, 21:47:12
2rewbs

I mean that when you use sample and mute and then unmute the channel
you lose synchronization...
when you mute and then unmute channel sample starts playing from the begining that sucks...
Title: Re: 2rewbs synchronization
Post by: rewbs on December 07, 2005, 21:55:39
Quote from: "Spanky"when you mute and then unmute channel sample starts playing from the begining that sucks...

That you can fix by toggling "ignore muted channels" in the general settings.
But the changes I described above are still required to get what you want.
Title: 2rewbs
Post by: Spanky on December 08, 2005, 20:59:10
2rewbs
you dont get it... may be its my bad english...
check out this file http://nestor.avtlg.ru/test.it
one same sample on two channels... press mute then unmute (quickly) one of the channels and you hear that synchronization is lost... the channel that you mute\unmute starts play faster\slower...
That is the problem...
Title: Re: 2rewbs
Post by: rewbs on December 09, 2005, 09:37:38
Quote from: "rewbs"I'll see what is involved in adding an option which lets sample and envelope positions increase when the chan is muted.

Quote from: "Spanky"2rewbs
you dont get it... may be its my bad english...
check out this file http://nestor.avtlg.ru/test.it
one same sample on two channels... press mute then unmute (quickly) one of the channels and you hear that synchronization is lost... the channel that you mute\unmute starts play faster\slower...
That is the problem...

I think I do get it, actually. The problem is that when a chan is muted, the sample position and envelope position freeze. As mentionned, when I get the chance I'll see what is involved in adding an option which lets sample and envelope positions increase when the chan is muted.
Title: .41 Temporary test build bug report thread
Post by: rewbs on December 10, 2005, 04:00:53
Quote from: "BooT-SectoR-ViruZ"news:
"Plugsound Free" can not be controlled via macros  :cry:
no params to choose from
OK I have a test build which makes assigning CCs to macros easy, will release soon. Check the plugsound manual to see which CCs correspond to which params.

Quote from: "BooT-SectoR-ViruZ"btw: it also doesn't respond to values in the volume column correctly
Yes, it does. :P
It seems to respond fine to volume commands sent with notes over here.
Make sure the veloity curve is set correctly (bottom right of the plug GUI) and that the Key param is only non-zero if you want velocity to affect the filter envelope (read the plug manual).
Title: .41 Temporary test build bug report thread
Post by: rewbs on December 10, 2005, 11:32:54
Just checked in new dev build 1.17.02.37: http://modplug.sourceforge.net/builds/#dev
BSV & Spanky, please check out this version.
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on December 10, 2005, 11:46:24
:D
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on December 10, 2005, 12:51:46
worx fine!

thx a lot  :!:
Title: .41 Temporary test build bug report thread
Post by: rewbs on December 10, 2005, 13:25:59
Muting channels that play VSTis has no effect with the new mute mode. Will fix soon.
Title: .41 Temporary test build bug report thread
Post by: Spanky on December 10, 2005, 16:10:22
well i guess everything works fine...
thx a lot dude...))
now iam happy...
OpenMPT is the best tracker...
Title: .41 Temporary test build bug report thread
Post by: Diamond on December 10, 2005, 16:48:01
Thanks for the new keys.  I did notice that the new "Song Properties" item you added to the view menu is grayed out and doesn't seem to work.  It also doesn't show the assigned hotkey on the menu like other commands do, but the assigned key still works just fine.
Title: .41 Temporary test build bug report thread
Post by: HarD-TeX on December 10, 2005, 18:14:35
Quote from: "rewbs"Just checked in new dev build 1.17.02.37: http://modplug.sourceforge.net/builds/#dev
BSV & Spanky, please check out this version.

i must i install this version ?
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on December 10, 2005, 18:41:26
just unzip the program-file
Title: .41 Temporary test build bug report thread
Post by: HarD-TeX on December 10, 2005, 19:00:42
but i have also the older OpenMPTRC2.exe
Title: .41 Temporary test build bug report thread
Post by: rewbs on December 10, 2005, 19:41:10
Quote from: "HarD-TeX"but i have also the older OpenMPTRC2.exe
You can just put the new .exe in the same directory as your original .exe.
Title: .41 Temporary test build bug report thread
Post by: HarD-TeX on December 10, 2005, 19:49:03
ok thanks  :D
Title: .41 Temporary test build bug report thread
Post by: Relabsoluness on December 10, 2005, 20:27:39
How can it be that at times 'modified'-star appears right after loading the module while nothing else have been done? I'm not quite sure what causes it, but it seems to be reproducable by

1. Creating new it module
2. Loading vst 'String theory 1.5'
3. Loading some presets in .fxp-file.
4. Saving and opening the file. The modified star appears right after loading.

Tested with rc2 and .37.

Quote from: "BooT-SectoR-ViruZ"somehow values in the volume column seem to have some effect on the sound of "Pentagon I"
I'm not sure whether it is related to this, but recently several times the vst-settings of some vst's(e.g. string theory) without any apparent reason have 'gone wild', i.e. the settings have changed dramatically. This is not very nice since the right settings doesn't seem to return even when closing without saving and reopening after that occurs. I haven't been able to figure out how it can be reproduced - the occurance seems quite random.
Title: .41 Temporary test build bug report thread
Post by: rewbs on December 10, 2005, 20:34:48
Quote from: "Relabsoluness"How can it be that at times 'modified'-star appears right after loading the module while nothing else have been done?
This is listed as a known issue in the RC2 release notes. It is to do with detecting whether a plugin parameter has changed. Some plugs set some of their own params on load or on playback and trigger the same mechanisms as when a user changes a param. So the song gets marked as modified.

Quotebut recently several times the vst-settings of some vst's(e.g. string theory) without any apparent reason have 'gone wild', i.e. the settings have changed dramatically.
Please keep me posted with any further details (this is not related to BSV's point about pentagon).
Title: .41 Temporary test build bug report thread
Post by: Relabsoluness on December 10, 2005, 20:54:03
Quote from: "rewbs"This is listed as a known issue in the RC2 release notes.
Didn't even cross my mind to check that :oops: - hopefully I can remember to check it in the future in similar occasions.

Quote from: "rewbs"
Quotebut recently several times the vst-settings of some vst's(e.g. string theory) without any apparent reason have 'gone wild', i.e. the settings have changed dramatically.
Please keep me posted with any further details (this is not related to BSV's point about pentagon).
I hope I can find some logic behind that, for it surely has been an annoyance; several times I have had to copy the settings from backup files.
Title: .41 Temporary test build bug report thread
Post by: rewbs on December 17, 2005, 21:32:56
v1.17.02.38 is up with a few bug fixes. Available immediately here: http://modplug.sourceforge.net/builds/#dev
Title: .41 Temporary test build bug report thread
Post by: minktos on December 23, 2005, 00:59:16
so i finally got around to upgrade from 1.17RC1 to the latest release and...crap! you moved a menu option!

(http://img477.imageshack.us/img477/7677/modplugmenus6nb.gif)

that little "solo" option there on the old version was a feature i really heavily relied on. now you have to go to the "channel #" bit at the top and click...and then it's the second option :(

any chance the features in the dropdown could be customizable or there could be an option to revert back to the old menus?

i hate to gripe but this really hurts my workflow :(

thanks for doing a great job, though!
Title: .41 Temporary test build bug report thread
Post by: rewbs on December 23, 2005, 11:21:17
Hi,

Lots of people who work at lower resolutions complained about the context menu getting too big.
I added an option in the general settings to keep the old style context menu before 1.17RC2, I think. But it doesn't have the solo option. I'll perhaps put it back and see how many people complain. :)
Yes it's of course possible to make the context menu customisable, but really not something I personally want to spend time on - particularly since pretty much all actions can be carried out with 100% customisable keys.

On a side note:
1. 1.17RC1 is pretty old now.
2. How about using shortcut keys? You could speed up your workflow further.
Title: .41 Temporary test build bug report thread
Post by: minktos on December 24, 2005, 12:25:33
Quote from: "rewbs"But it doesn't have the solo option. I'll perhaps put it back and see how many people complain. :)

thanks dude, it would be awesome if you could!

Quote1. 1.17RC1 is pretty old now.

i guess i'm a little slow on the updating heheheh.

Quote2. How about using shortcut keys? You could speed up your workflow further.

i dunno, i guess in certain ways i'm just kinda set in my ways. like, i'm still using XM because i know all the effects by heart all the way from the MOD days...

Cxx is volume, 4xx is vibrato, 3xx is portamento, etc

kinda sucks because i can't use any of IT features like NNA's but i've made my bed, now i'll sleep in it. ha!

thanks again for everything you're doing, rewbs (and everybody else) it's absolutely awesome.

merry christmas!
Title: .41 Temporary test build bug report thread
Post by: LPChip on December 26, 2005, 16:03:17
Quote from: "rncekel"I think this is not new, but in the Edit menu, Cleanup, the Rearrange Samples doesn't work. Well, in fact it is worst, because it mess up the samples.

This has been fixed in .38 Can you verify that your problem exists in .38?
Title: .41 Temporary test build bug report thread
Post by: LPChip on December 26, 2005, 16:05:43
BUG: Midi input places 2 notes instead of one

I've hooked up my midi keyboard to my MPT. When I select for example the Piano instrument, and I have follow, off, but am in the pattern editor, it places 2 notes after pressing down the key. If i quickly release it and press another, it puts 2 notes down again. If i release and don't press another == is being placed afterwards which is good, so the problem doesn't lay there.
Title: .41 Temporary test build bug report thread
Post by: Squirrel Havoc on December 26, 2005, 16:47:50
Quote from: "LPChip"BUG: Midi input places 2 notes instead of one

I've hooked up my midi keyboard to my MPT. When I select for example the Piano instrument, and I have follow, off, but am in the pattern editor, it places 2 notes after pressing down the key. If i quickly release it and press another, it puts 2 notes down again. If i release and don't press another == is being placed afterwards which is good, so the problem doesn't lay there.

Are you sure it has nothing to do with split keyboard or transpose settings? I can't reproduce this bug with my keyboard
Title: .41 Temporary test build bug report thread
Post by: LPChip on December 26, 2005, 17:50:20
Quote from: "Squirrel Havoc"
Quote from: "LPChip"BUG: Midi input places 2 notes instead of one

I've hooked up my midi keyboard to my MPT. When I select for example the Piano instrument, and I have follow, off, but am in the pattern editor, it places 2 notes after pressing down the key. If i quickly release it and press another, it puts 2 notes down again. If i release and don't press another == is being placed afterwards which is good, so the problem doesn't lay there.

Are you sure it has nothing to do with split keyboard or transpose settings? I can't reproduce this bug with my keyboard

I dunno what caused this, but I might have a clue.

I closed down MPT, reopened it, and it was gone. I think it has something to do with auto-save. Am going to verify this first ofcource. If Auto-save saves my 17 mb song, MPT is halted for approx 1 sec. I have auto save set for 1 minute to make 1 backup of the song (for bug testing purpose) But If I'm playing at my keyboard, and auto-save kicks in, the sound is halted too and then after the save rapidly playes all notes. Am seeing if this has something to do with suddenly having 2 notes written during play.

EDIT: Dunno. Can't seem to get it either anymore. neither with autosave. If it happens I'll report it back. case closed for now.
Title: .41 Temporary test build bug report thread
Post by: Anonymous on December 30, 2005, 17:00:14
found a bug with 1.17RC2.....

VST issue

Xlutop chainer VST/VSTi do not work any more.  I get a message saying 'at least one of the plugins was not valid' or whatever.  It worked fine on RC1.

Actually, I just rebuilt my machine with a new mainboard, SATA HD and Athlon 64+ 3500.  On this new machine I just installed the 'newest' version of MPT and now Xlutop fails.  Strange.

Maybe I should be using the build optimised for P4/Athlon64???

I'll try the athlon 64 build -- i'll keep you guys posted if I get the same problem.
Title: .41 Temporary test build bug report thread
Post by: rewbs on December 30, 2005, 19:24:33
Hi,

I use Xlutop Chainer very regularly - it works fine on RC2 over here.
Chainer comes with 3 dlls and only 2 of them are valid VST plugins (Chainer.dll isn't, Chainer VST.dll and Chainer VSTi.dll are). Make sure you're trying to load the right ones. Let us know what happens.
Title: .41 Temporary test build bug report thread
Post by: LPChip on December 30, 2005, 20:10:07
Quote from: "rewbs"Hi,

I use Xlutop Chainer very regularly - it works fine on RC2 over here.
Chainer comes with 3 dlls and only 2 of them are valid VST plugins (Chainer.dll isn't, Chainer VST.dll and Chainer VSTi.dll are). Make sure you're trying to load the right ones. Let us know what happens.

Rewbs, he is saying that it doesn't work anymore, which indicates that it worked before. So I think something else is happening here. I have experience with this software so I can't assist on this matter. Is there anything else you can think of why this wouldn't be working, and things to try to make it work again?

For instance, can you delete the dll's from your harddrive, and download and extract again, also remove from MPT and re-add them?
Title: .41 Temporary test build bug report thread
Post by: Squirrel Havoc on December 30, 2005, 22:45:52
Well he rebuilt his machine, so if it's a new hard drive and installation, then maybe he just selected the wrong DLL
Title: .41 Temporary test build bug report thread
Post by: Leitmotif on December 31, 2005, 13:36:23
I just realised I wasn't logged in before -- hence "guest".

Quote from: "rewbs"I use Xlutop Chainer very regularly

... as do I......... for EVERYTHING.  Which is why it more than a tad irritating that OMPT is not recognising it anymore....

Quoteit works fine on RC2 over here.

Really?  Hm....  maybe I do need the athlon 64 build, eh?  I'll get that on there in the next half-hour or so and see if the issue is still there.

QuoteChainer comes with 3 dlls and only 2 of them are valid....

*nods* I am aware.

Quote from: "Squirrel Havoc"Well he rebuilt his machine, so if it's a new hard drive and installation, then maybe he just selected the wrong DLL

No, I was definitely sober at the time -- picked the right DLL.  Oh, and while it is a new HD and rebuild, I tx'd most general data (inc VSTs, samples/ITIs, mods, documents, etc, etc, totalling over 40GB), but I've done this before and don't remember Xlutop actually NEEDING to be reinstalled.  Not like Amplitube, which bases registration on variables of the system.  Kinda daft considering it's still as easy to crack as anything else.  (remember the thread topic -- I don't want to start a lengthy discussion on cracking etc here).



Well, thanks... at least I know it's not actually a bug with OMPT-RC2, as Rewbs said.  So it's something with my machine (worst-case-scenario) or the fact I'm using the generic build of OMPT.  Time for the proper Athlon64 build of OMPT, then.....



EDITTED TO ADD -------------

I just installed the Athlon64/P4 build.  Not only does OMPT 'start' faster (the main window appears, like 8ms after the splash logo!! -- may disable the splash, infact), but Xlutop works fine now!  Yes, XLUTOP WORKS FINE NOW!  :)  So, there ya go -- be sure to use the right build for your machine.  Why OH WHY does that even MAKE A DIFFERENCE TO VSTs!!!!?!?!?   :x

Cool.  Thanks.
Title: .41 Temporary test build bug report thread
Post by: rewbs on January 04, 2006, 23:15:29
Leitmotif, you're right it shouldn't make any difference, and I can load Xlutop Chainer with the generic build with no problems. Not sure what's going on.


Anyway, build 1.17.02.39 is available with some enhancements from Relabsoluness: http://modplug.sourceforge.net/builds/#dev
Title: .41 Temporary test build bug report thread
Post by: Relabsoluness on January 05, 2006, 13:01:45
Just noticed that when looping pattern that has pattern break command, and then unchecking the 'loop pattern' checkbox, playing may jump instantly to some other pattern - surely something it should not do  :? . Also when using the loop pattern checkbox, the playing may continue from beginning after last pattern even if loop song was off.
Title: .41 Temporary test build bug report thread
Post by: Anonymous on January 10, 2006, 20:17:27
Quote from: "rewbs"Leitmotif, you're right it shouldn't make any difference, and I can load Xlutop Chainer with the generic build with no problems. Not sure what's going on.

*pulls out his Kazoo and buzzes the theme from 'The Twilight Zone'*
Title: .41 Temporary test build bug report thread
Post by: anboi on January 17, 2006, 01:22:32
i got a weird bug today for the second time where the pitch of all vsts (but not samples) went down by itself... i have been totally unable to recreate it. saving, closing then reloading corrects it. it happened in a track with lots of VSTs in and it retuned all but the one i was tweaking but i'm not entirely sure. the pitch then sneaked down slowly for a bit. i also had the one i was tweaking soloed and noticed the retuning when i returned to listening to all. i am also absolutely 100% sure it changed the tunings of all the others before anyone says anything! it was at least 12 cents.
i also discovered the other day that the weird performance issues turned out to be my motherboard being broken and fucking up when accessing the IDE bus. at least i think that was it - my computer is now much faster so its hard to tell but if no-one else had trouble then i imagine its fine.
Title: .41 Temporary test build bug report thread
Post by: Laci on January 21, 2006, 11:16:46
I also found a bug... sometimes mpt misses notes/events (lines, only one), they are not passed to VSTIs. This is not the "note drop" issue when rendering. Seems to occur randomly, usually misses a line in the playing channel, so for example: when it misses a note off command then the note keeps playing, i have to stop and restart playback. The bug is also present when rendering to disk. Occurs only for VSTIs.

Second, the Slow rendering option is very nice, works ok, but it's too much, i mean realtime "slowness" should be enough... the current is painfully slow. While On low-end systems it can be still handy, so i'm suggestin a dropdown menu for selecting rendering method -> normal (fast as possible), realtime (for Vst compatibilty), slow (for very low-end systems). I would be glad if the devs could implement this. Thanks.

PS. My English is still bad   :oops:
Title: .41 Temporary test build bug report thread
Post by: LPChip on January 21, 2006, 11:25:12
Quote from: "Laci"I also found a bug... sometimes mpt misses notes/events (lines, only one), they are not passed to VSTIs. This is not the "note drop" issue when rendering. Seems to occur randomly, usually misses a line in the playing channel, so for example: when it misses a note off command then the note keeps playing, i have to stop and restart playback. The bug is also present when rendering to disk. Occurs only for VSTIs.

Second, the Slow rendering option is very nice, works ok, but it's too much, i mean realtime "slowness" should be enough... the current is painfully slow. While On low-end systems it can be still handy, so i'm suggestin a dropdown menu for selecting rendering method -> normal (fast as possible), realtime (for Vst compatibilty), slow (for very low-end systems). I would be glad if the devs could implement this. Thanks.

PS. My English is still bad   :oops:

Can you tell me what version of the tracker you use? Cus I've also found stuck notes, but they're fixed in the latest beta build.
Title: .41 Temporary test build bug report thread
Post by: Laci on January 21, 2006, 11:54:13
I'm using the newest build (1.17.02.39)
Title: .41 Temporary test build bug report thread
Post by: LPChip on January 21, 2006, 12:07:02
Quote from: "Laci"I'm using the newest build (1.17.02.39)

Can you tell me what plugin(s) is causing this, and preferabelly create a small song that shows this bug? (you don't need include the plugin, and if its a commercial plugin, you even may not :P)
Title: .41 Temporary test build bug report thread
Post by: Laci on January 21, 2006, 12:29:40
I tested it a bit, seems its plug specific, occurs with Absynth 3 (v3.0.2.011), and i google-ed up some info, (NI support forums), its a bug in the plug, its not related to MPT, sorry for this.  :)
Title: .41 Temporary test build bug report thread
Post by: LPChip on January 21, 2006, 12:30:42
Quote from: "Laci"I tested it a bit, seems its plug specific, occurs with Absynth 3 (v3.0.2.011), and i google-ed up some info, (NI support forums), its a bug in the plug, its not related to MPT, sorry for this.  :)

Thats okay. :) Thanks for letting us know though. :)
Title: .41 Temporary test build bug report thread
Post by: rewbs on January 22, 2006, 09:32:23
Quote from: "Laci"I tested it a bit, seems its plug specific, occurs with Absynth 3 (v3.0.2.011), and i google-ed up some info, (NI support forums), its a bug in the plug, its not related to MPT, sorry for this.  :)

Excellent, I had noticed dropped notes with Absynth 3 too, and was a bit concerned. Thanks for the research! Any indication that this will be fixed in an upcoming version of Absynth?
Title: .41 Temporary test build bug report thread
Post by: Laci on January 22, 2006, 10:43:18
This is a mysterious bug, it seems that only some people experienced it (both on PC and MAC, using FL studio, Cubase SX, etc.), and until the devs at NI can reproduce it, there will be no fix. Also There is no workaround. This problem might be system related, but no one traced it yet.
Title: .41 Temporary test build bug report thread
Post by: shableep on January 22, 2006, 12:37:22
"The plugin Kontakt2 threw an exception in processReplacing. It has automatically been set to "Bypass"."

this is the error i get when try to use the VSTi in anyway. it loads up, and i can apply it to an instrument. but, the second i try to play a note it throws up this message and the plugin continues to do nothing.

any ideas?
Title: .41 Temporary test build bug report thread
Post by: Laci on January 22, 2006, 15:21:33
Add and use the "Kontakt2_16out.dll" or "Kontakt2_8out.dll" instead.
Title: .41 Temporary test build bug report thread
Post by: Laci on January 22, 2006, 15:54:28
I have a VST plugin: Image-Line Sytrus DXi VSTi v2.0
It's settings are not saved by MPT. After saving and reopening all settings are reset to default.
The demo version can be downloaded at www.sytrus.com (aprox. 2megs)
Title: .41 Temporary test build bug report thread
Post by: LPChip on January 22, 2006, 18:09:25
Quote from: "Laci"I have a VST plugin: Image-Line Sytrus DXi VSTi v2.0
It's settings are not saved by MPT. After saving and reopening all settings are reset to default.
The demo version can be downloaded at www.sytrus.com (aprox. 2megs)

Maybe a dumb question, but can it be that the plugin resets itself? as somekind of demo-feature? Cus preset saving is something the plugin must support. Sometimes in a demo version of a plugin, you can't save the preset.
Title: .41 Temporary test build bug report thread
Post by: Laci on January 22, 2006, 18:38:14
Nope, i have the right "tools" for demo versions  :wink:
and i tested it in cubase sx3 and it worked well there.
Title: .41 Temporary test build bug report thread
Post by: shableep on January 22, 2006, 21:15:53
thanks Laci. i'll give it a shot.
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on February 03, 2006, 18:40:10
recognized problems with "coldcutter1_beta2"

works fine when playing a pattern first that starts with this effect,
but doesn't work when you play some patterns without it before

:cry:

VU-meter shows something, but it's not audible
Title: .41 Temporary test build bug report thread
Post by: rewbs on February 03, 2006, 19:05:37
Quote from: "BooT-SectoR-ViruZ"recognized problems with "coldcutter1_beta2"
works fine when playing a pattern first that starts with this effect,
but doesn't work when you play some patterns without it before

Correct me if I'm wrong, but I think this plugin samples the stream for a fixed duration, then plays back random chunks of what it has just sampled. If you feed it silence, it will chop up and play back silence. This is not a bug.
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on February 04, 2006, 09:53:01
aaaah, so i got to assign it to the instrument, not to the channel... sure.... i'm so stupid  :D

edit: still doesn't work  :cry:

btw: effect can not be stopped by cut or setting volume 00
Title: .41 Temporary test build bug report thread
Post by: rewbs on February 04, 2006, 10:59:02
Quote from: "BooT-SectoR-ViruZ"aaaah, so i got to assign it to the instrument, not to the channel... sure.... i'm so stupid  :D

edit: still doesn't work  :cry:
No of course not...  it's an effect plugin. Again, the plugin records the FIRST piece of sound you feed it and uses that as a loop. There's probably a way to get it to reset the loop. I suggest you read any docs associated with the plug.

Quote from: "BooT-SectoR-ViruZ"btw: effect can not be stopped by cut or setting volume 00
Those commands affect samples & VSTi, not effect plugins that don't receive midi commands. If you want the plugin to shut up, use the dry/wet ratio.
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on February 04, 2006, 11:04:14
but if it's associated to a certain instrument only, it doesn't get any input till i play the instrument, or am i missing the spot?
Title: .41 Temporary test build bug report thread
Post by: rewbs on February 04, 2006, 12:37:01
Quote from: "BooT-SectoR-ViruZ"but if it's associated to a certain instrument only, it doesn't get any input till i play the instrument, or am i missing the spot?
Ah ok I see what you mean.. no unfortunately MPT isn't clever enough to invoke effects "on demand", they are always processing their input buffer, even if it's empty. This is very useful is many cases. The VST api does provide a tail function to detect whether the plug needs to process or not, but it's a bitch to implement into MPT.. have been meaning to do it for a while.

But I don't think that would help with this plug anyway. I glanced over the plug's homepage and it sais it was designed for use with Live, which I believe provides a button to suspend the plugin, thus resetting its loop. I don't think it will work as you intend with MPT. Have you tried dfx scrubber? Similar plug, might work better with MPT.

Edit: Sorry I meant dfx buffer override (http://destroyfx.smartelectronix.com/).
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on February 04, 2006, 15:34:32
buffer override doesn't cut samples in tiny pieces and plays them at random order ;)
Title: .41 Temporary test build bug report thread
Post by: rewbs on February 04, 2006, 15:50:05
It can. But if you're hooked on that other plug I suggest you contact the plugin author and ask him how to reset the loop. If this is a host dependant functionality ask him to add it as a plugin param.

Edit: OK I played with cold cutter a bit and it resets the loop when you change the loops length. You need to nudge the loop length param just as your sample starts. Imagine cold cutter is applied to this channel:

|........SF0      Here cold cutter
|...........      is sampling
|...........      silence
|...........
|...........
|...........
|...........
|...........
|...........
|...........
|...........
|...........
|...........
|...........
|...........
|........Z01
|C-501...Z00      Here you
|...........      nudge the
|...........       loop length param
|...........      and cold cutter starts
|...........      recording again
|...........      (SF0 is mapped to param 87 - loop length)
|...........
|...........
|...........
|...........
|...........
|...........
|...........
|...........
|...........
|........C00


I should mention this is also explained in the plugin's instructions: http://www.brightonart.co.uk/coldcutter.shtml
RTFM and all that shite :P
Title: .41 Temporary test build bug report thread
Post by: BooT-SectoR-ViruZ on February 04, 2006, 18:32:47
asking rewbs is better than rtfm in most cases ;D

thx, sweetheart
Title: .41 Temporary test build bug report thread
Post by: Diamond on February 04, 2006, 23:35:04
Quote from: "BooT-SectoR-ViruZ"buffer override doesn't cut samples in tiny pieces and plays them at random order ;)

Other VSTs to try which might do something similar.
------------------------------------------------------------
Traks
http://www.kvraudio.com/get/1905.html
Sample Stutterer
http://www.kvraudio.com/get/1877.html
Pseudograins
http://www.kvraudio.com/get/1610.html
Title: .41 Temporary test build bug report thread
Post by: Sam_Zen on February 13, 2006, 04:31:26
I'm aware of the fact, that this is a minor problem, compared to plugin-compatibilities, but anyway. (running 2K)
Normally, GUI-settings of MPT are saved with closing. Because I, so far, never used the 'tree view', because I prefer to have maximum screen while working, I had to disable that after starting.
But this default came back most of the time, so everytime I first had to disable this view again.
I tested this somewhat further (this problem is valid with both RC2 and the beta) :
- As long as I opened, disabled the view, closed, opened again, the view was correct without the tree at the left.
- As soon as, after opening, disabling the view and closing, I opened another app, close the app again, and open MPT again, the treeview comes back as default.
Title: .41 Temporary test build bug report thread
Post by: LPChip on February 14, 2006, 13:05:00
Quote from: "Sam_Zen"I'm aware of the fact, that this is a minor problem, compared to plugin-compatibilities, but anyway. (running 2K)
Normally, GUI-settings of MPT are saved with closing. Because I, so far, never used the 'tree view', because I prefer to have maximum screen while working, I had to disable that after starting.
But this default came back most of the time, so everytime I first had to disable this view again.
I tested this somewhat further (this problem is valid with both RC2 and the beta) :
- As long as I opened, disabled the view, closed, opened again, the view was correct without the tree at the left.
- As soon as, after opening, disabling the view and closing, I opened another app, close the app again, and open MPT again, the treeview comes back as default.

This bug has been discussed in the following topic:

http://forum.openmpt.org/index.php?msg=3339.0#msg3339

This link provides the cause and the solution to this problem.
Title: .41 Temporary test build bug report thread
Post by: Squirrel Havoc on February 20, 2006, 02:55:56
Ok, this is either a bug in Winamp, or in MPT, and I upgraded winamp and changed some settings, then this happened, but it's also the first time I used them both at the same time, so I am reporting it anyway.

I was working in the latest MPT beta, double clicking on XI instruments in the tree view, and I unpaused winamp and then I clicked another. Then winamp changed the sound output for itself, all you hear is the stereo imaging (stuff that only comes out of one speaker, or both but with a delay between them). All the mono stuff was gone. It was quite cool actually, but now I can't get it to stop. I haven't tried rebooting yet, I think I will just deal with it. But I am using the waveOut output in winamp, and the ASIO in MPT. Does MPT use the set output for sample previews, or does it always use waveOut?

Anyway, it's no big deal, just though I would report it. Since I can't get winamp to sound right, it would be impossible to recreate the problem
Title: .41 Temporary test build bug report thread
Post by: LPChip on February 20, 2006, 11:59:25
Quote from: "Squirrel Havoc"Ok, this is either a bug in Winamp, or in MPT, and I upgraded winamp and changed some settings, then this happened, but it's also the first time I used them both at the same time, so I am reporting it anyway.

I was working in the latest MPT beta, double clicking on XI instruments in the tree view, and I unpaused winamp and then I clicked another. Then winamp changed the sound output for itself, all you hear is the stereo imaging (stuff that only comes out of one speaker, or both but with a delay between them). All the mono stuff was gone. It was quite cool actually, but now I can't get it to stop. I haven't tried rebooting yet, I think I will just deal with it. But I am using the waveOut output in winamp, and the ASIO in MPT. Does MPT use the set output for sample previews, or does it always use waveOut?

Anyway, it's no big deal, just though I would report it. Since I can't get winamp to sound right, it would be impossible to recreate the problem

This sounds like a Winamp bug. Its weird though that this happens because these are 2 different devices. Perhaps it has something to do with switching between audio modes (like 44.1khz with 48khz, or switching from a mono to stereo, etc...)
Title: .41 Temporary test build bug report thread
Post by: Squirrel Havoc on February 20, 2006, 18:52:14
GOD im a freakin MORON!!!!!!!!!! My problem was the computer speaker cable came a little loose  :oops:  ::)  :?  :cry:  :lol:


I plugged it back in, everything works peachy. Sorry about that...
Title: .41 Temporary test build bug report thread
Post by: rewbs on March 12, 2006, 14:40:20
New update with some fixes, no more registry accesses (except to read the settings the first time), and lots of good work from Relabsoluness. :)
See top of thread.
Title: .41 Temporary test build bug report thread
Post by: Diamond on March 13, 2006, 02:11:40
Version 1.17.02.40

I don't know if this is a bug or not, but the toolbar and "Recent File List" settings are being saved in a second INI file located in the windows directory.  Is there a reason why this information isn't just stored in the INI file that's in MPT's base folder with all the other settings?
Title: .41 Temporary test build bug report thread
Post by: rewbs on March 13, 2006, 15:28:49
Diamond, thank you for spotting that. I'll see if I can figure out how to tell window to use a specific ini file for those too.
Title: .41 Temporary test build bug report thread
Post by: Squirrel Havoc on March 14, 2006, 17:57:07
First of all, sorry for reporting bugs ins seperate threads, I missed the message in the first post

I think I might have discovered a bug, but you would think it would be reported by  now if it was a bug. The channel VU meters don't get re-enabled when I shutdown OMPT and restart it, no matter how many times I push the button. This is a recent bug, I believe it showed up in either the latest of the 2nd to the latest beta.
Title: .41 Temporary test build bug report thread
Post by: rewbs on March 14, 2006, 18:17:25
One of the new feature in this build is that settings were move from registry to ini, and I could have missed some, so it's a likely new bug.
Title: .41 Temporary test build bug report thread
Post by: Squirrel Havoc on March 14, 2006, 20:40:03
Another similar bug, it doesn't save the mod window position (like restored or maximized), so thats another one.
Title: .41 Temporary test build bug report thread
Post by: Relabsoluness on March 14, 2006, 21:21:50
I have the same with the vu-meters and the window size, and another one I've noticed is that when loading a file, it gets added to recent items, but if closing and reopening the program, the item has been disappeared. But when doing this for the second time, it seems to remain there :)
All of these appeared in .40
Title: .41 Temporary test build bug report thread
Post by: rewbs on March 14, 2006, 22:11:04
Yes row spacing doesn't save properly either - there are a few problems. :)
Title: .41 Temporary test build bug report thread
Post by: Diamond on March 14, 2006, 23:12:00
Quote from: "Relabsoluness"I have the same with the vu-meters and the window size, and another one I've noticed is that when loading a file, it gets added to recent items, but if closing and reopening the program, the item has been disappeared. But when doing this for the second time, it seems to remain there :)
All of these appeared in .40

I think this is also related to the bug which I reported.  I noticed the same problem myself.  This is what I noticed.  When you first run the program, it creates an INI file in the windows folder which has the same name as the executable.  This file stores the toolbar, screen resolution and recent file settings.  So this is the INI file which it reads the recent file list from unless you rename the executable.  If you rename it, a new INI file is then created based on the new file name and it then reads the recent file list from the newly created INI, making it appear as if items have disappeared.  For example, when I first downloaded the package, the file was name mptrack_Generic-1.17.02.40.exe.  I renamed it to just mptrack.exe.  I found two INI files in the windows folder, mptrack.ini and mptrack_Generic-1.17.02.40.ini.  However, I believe that even taking this into account there still seems to be a probably related secondary bug because I'm still getting inconsistent results on the recent file list.  I.E. Items disappearing and reappearing from the menu on subsequent runs of the program like Relabsoluness described.

Personally, I think that when you work out all the bugs, having MPT create the INI file based on the name of the executable is probably a good idea, but it should still be created in the same folder as MPT, not the windows folder.  This way you could have multiple copies/different versions running in the same directory with their own individual settings.
Title: .41 Temporary test build bug report thread
Post by: Relabsoluness on March 15, 2006, 21:49:23
The problem with the recent items list seemed to remain in .41 - the list seems to change on every opening time, being the same on every second time(if I understood it correctly, the same as what Diamond descripted).

EDIT: On the whole this seems bit chaotic behavior  :?
Title: .41 Temporary test build bug report thread
Post by: rewbs on March 15, 2006, 21:56:38
Quote from: "Relabsoluness"I still have the 'load twice to get the item to remain in recent items'-thing with .41
I can't reproduce this. Can you check the .ini to see how it evolves? In my case if I open a file and close .41, the filename is in the .ini. When I open .41 again, the file is in the MRU.
Title: .41 Temporary test build bug report thread
Post by: Diamond on March 16, 2006, 02:50:45
Quote from: "rewbs"
Quote from: "Relabsoluness"I still have the 'load twice to get the item to remain in recent items'-thing with .41
I can't reproduce this. Can you check the .ini to see how it evolves? In my case if I open a file and close .41, the filename is in the .ini. When I open .41 again, the file is in the MRU.

I can't reproduce this either.  Seems to be fixed for me as well.
Title: .41 Temporary test build bug report thread
Post by: LPChip on March 16, 2006, 13:29:41
Uh, what happened?

Somehow I failed to notice we're having a .41 version released? #1 post still says .40  :o
Title: .41 Temporary test build bug report thread
Post by: rewbs on March 16, 2006, 14:25:17
Yes, I didn't announce .41. It just contains minor fixes.. but those who are in sync with the repository or RSS will know it's there. :)
BTW, I'm considering no longer manually announcing every new dev build here, since it is already done automatically on RSS, and the RSS feed can be imported into any website (e.g.: http://openmpt.xwiki.com/xwiki/bin/view/Sandbox/rssTest )

Edit: also we need to get a proper bug tracker going again. I'm playing with the sourceforge one, it has all the features we need but, I find it really unpleasant to use. Maybe I'll try to integrate something into the wiki... or LP, how feasible is it to get the old system back into these forums - do you still have the code?
Title: .41 Temporary test build bug report thread
Post by: Relabsoluness on March 16, 2006, 21:30:58
Quote from: "Diamond"
Quote from: "rewbs"
Quote from: "Relabsoluness"I still have the 'load twice to get the item to remain in recent items'-thing with .41
I can't reproduce this. Can you check the .ini to see how it evolves? In my case if I open a file and close .41, the filename is in the .ini. When I open .41 again, the file is in the MRU.

I can't reproduce this either.  Seems to be fixed for me as well.
Well I actually could reproduce the 'bug' also with rc2 so it likely has nothing to do with .41 anyway - it seemed to have something to do with opening the program right after closing it. Sorry for the wasted time  :oops:
Title: .41 Temporary test build bug report thread
Post by: LPChip on March 17, 2006, 10:04:15
Quote from: "rewbs"
Edit: also we need to get a proper bug tracker going again. I'm playing with the sourceforge one, it has all the features we need but, I find it really unpleasant to use. Maybe I'll try to integrate something into the wiki... or LP, how feasible is it to get the old system back into these forums - do you still have the code?

The code was too easy to keep :P Doing this will take approx. 10 minutes, so considder it done (somewhere tonight) :P

The process consists out of 2 phases.

1. Making a forum, and make sure that all topics are made with (S=O) etc...

2. Doing a check on the title, and change its color depending on what (S=x) is set. (the last one I'll have to do tonight, but the first I'll do now.)
Title: .41 Temporary test build bug report thread
Post by: rewbs on March 17, 2006, 14:17:27
Thanks LP - Locking this thread. Please report each bug in an individual thread.