|
Ian @ un4seen
Administrator
Posts: 15276
|
 |
« Reply #680 on: 23 Jun '09 - 14:11 » |
 Quote
|
You would need to restart XMPlay to do that. That is because each track record needs to have a unique filename and they are not removed from memory (until XMPlay is closed), even if they are currently not in either the playlist or library.
Let me know if you still can't change the track's filename after restarting.
|
|
|
|
|
Logged
|
|
|
|
|
saga
Posts: 1365
|
|
« Reply #681 on: 23 Jun '09 - 16:51 » |
Quote
|
Well yes, it works after restarting, but that's a bit inconvenient for on-the-fly playlist editing...
|
|
|
|
|
Logged
|
|
|
|
|
saga
Posts: 1365
|
|
« Reply #682 on: 24 Jun '09 - 19:16 » |
Quote
|
this s3m file seems to be played kinda wrong. At position 7 (pattern 5), channels 3 and 4 are supposed to be played the same way, but this is not the case. MPT and ST3 play this tune correctly. The problem is that the volume column has the value "66" which is obviously two too much. This should be reduced to 64, not 0.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
saga
Posts: 1365
|
|
« Reply #684 on: 25 Jun '09 - 15:23 » |
Quote
|
That looks like the volume issue has been fixed but... Is it just me or is xmplay randomly breaking to the next pattern all the time?!
EDIT: Seems like the whole S3M loader is broken, it happesn with all S3Ms...
|
|
|
|
« Last Edit: 25 Jun '09 - 17:34 by saga »
|
Logged
|
|
|
|
|
deus-ex
Posts: 186
|
|
« Reply #685 on: 25 Jun '09 - 17:57 » |
Quote
|
That looks like the volume issue has been fixed but... Is it just me or is xmplay randomly breaking to the next pattern all the time?!
EDIT: Seems like the whole S3M loader is broken, it happesn with all S3Ms...
Current stuff build 110 has that fixed. |
|
|
|
|
Logged
|
|
|
|
|
saga
Posts: 1365
|
|
« Reply #686 on: 25 Jun '09 - 21:35 » |
Quote
|
yep, that sounds better again.  |
|
|
|
|
Logged
|
|
|
|
|
Ian @ un4seen
Administrator
Posts: 15276
|
|
« Reply #687 on: 26 Jun '09 - 13:28 » |
Quote
|
Yeah, the earlier "fix" (.109) actually broke the S3M loader, so it was corrected in the day's later update |
|
|
|
|
Logged
|
|
|
|
|
jperez
Posts: 7
|
|
« Reply #688 on: 1 Jul '09 - 11:39 » |
Quote
|
Hi everyone, I'm new to these forums, but not new to XMPlay. Been using it for years and even bought 2MIDI a couple years back. Now, a strange thing has occurred with one of my rearrangements. Usually all of my music is played perfectly when playing in XMPlay, but I made one that was a bit different and seems to be dropping out notes which it doesn't do for other files I've worked with. Here's the scenario: I'm playing the music and the notes are dropping out when the pattern looks like this (IT): |A-401......
|===........
|E-401...SD2
|...........
|===........
|A-401...SD1
|===........
|...........
|G-401......
|...........
|===........ It basically isn't playing nice with Note Delay in this file. Speed is 4 and Tempo is 190 and I even changed the speed and tempo to see if that would solve the problem, but no go. I've tried everything, but it just doesn't want to work and I'm not willing to recreate the rearrangement and double it's length as it was a pain to make in the first place.  I can provide the IT file in question if needed. I just want to be able to hear it clearly like I can using the MODPlug & DUMB engines. I love XMPlay and has "replaced" ImpulseTracker (MS-DOS) for playback. I really would like to keep it that way. Any ideas? :/ Jesse~ |
|
|
|
|
Logged
|
|
|
|
|
|
|
jperez
Posts: 7
|
|
« Reply #690 on: 1 Jul '09 - 20:11 » |
Quote
|
Okay, it's been uploaded as Overworld.it. It hope it's something that can be easily fixed. I don't want it to be too troublesome. Jesse~ |
|
|
|
|
Logged
|
|
|
|
|
Ian @ un4seen
Administrator
Posts: 15276
|
|
« Reply #691 on: 2 Jul '09 - 14:55 » |
Quote
|
I think the note delay is actually a bit of a red herring Your file is also using "carry" envelopes together with the "note cut" NNA, and it appears that the "carry" element should be ignored in that case. So here's an update to try, which should do just that... www.un4seen.com/stuff/xmplay.exe |
|
|
|
|
Logged
|
|
|
|
|
jperez
Posts: 7
|
|
« Reply #692 on: 2 Jul '09 - 19:58 » |
Quote
|
Boy do I feel stupid  Still, I'd never known about carry envelopes. This will be useful information in the future. Thanks for the update! It really helps. I wonder what other of my musics now with this update and new information... Jesse~ |
|
|
|
|
Logged
|
|
|
|
|
winner
Posts: 193
|
|
« Reply #693 on: 6 Jul '09 - 00:55 » |
Quote
|
Ian, I've got a problem!  After installing XMPlay version 3.4.2.111 and rebooting my computer, whenever I try to run XMPlay I get the following error: ERROR! This file has been tampered with and MAY BE INFECTED BY A VIRUS! XMPlay refuses to run. I get the same error when I try to run previous versions. I even reinstalled the standard package from the website to another folder, but get the same error. I've identified this message as coming from code in another program you've written, called Petite Packer, which to my knowledge I have never installed on my computer. I suspect XMPlay is a packed executable and something is going wrong when it self-decompresses. This message has been extremely disconcerting for me; I've run numerous virus/malware scans and installed three additional malware scanners to find what might be wrong. I'm relieved to learn it's code that you probably wrote and know something about. Please advise on how I can stop this from appearing and run XMPlay again. I also suggest that if this code is part of XMPlay or the Bass engine, that a more useful message is constructed, so that people encountering this will better know where to look for help. Thanks Ian! |
|
|
|
Logged
|
|
|
|
|
ChrisW
Posts: 1
|
|
« Reply #694 on: 6 Jul '09 - 10:13 » |
Quote
|
whenever I try to run XMPlay I get the following error:
ERROR! This file has been tampered with and MAY BE INFECTED BY A VIRUS!
I started getting this message after Comodo Internet Security updated to version 3.10. After downgrading to v3.9 XMPlay now works again. |
|
|
|
|
Logged
|
|
|
|
|
winner
Posts: 193
|
|
« Reply #695 on: 6 Jul '09 - 13:18 » |
Quote
|
whenever I try to run XMPlay I get the following error:
ERROR! This file has been tampered with and MAY BE INFECTED BY A VIRUS!
I started getting this message after Comodo Internet Security updated to version 3.10. After downgrading to v3.9 XMPlay now works again. Thanks! This problem starting appearing for me also after an upgrade of Comodo. I'll try to revert as well and see what happens. I've notified Comodo about the problem. |
|
|
|
|
Logged
|
|
|
|
|
Ian @ un4seen
Administrator
Posts: 15276
|
|
« Reply #696 on: 6 Jul '09 - 13:55 » |
Quote
|
That message should only appear if the XMPLAY.EXE file (or perhaps a plugin) has been tampered with, possibly by a virus. Please first try downloading the latest "stuff" (.112) and reproduce the problem with that alone in a directory. If the problem happens then, upload the XMPLAY.EXE file, and I'll confirm whether it has been modified... ftp.un4seen.com/incoming/ |
|
|
|
|
Logged
|
|
|
|
|
winner
Posts: 193
|
|
« Reply #697 on: 6 Jul '09 - 14:08 » |
Quote
|
That message should only appear if the XMPLAY.EXE file (or perhaps a plugin) has been tampered with, possibly by a virus. Please first try downloading the latest "stuff" (.112) and reproduce the problem with that alone in a directory. If the problem happens then, upload the XMPLAY.EXE file, and I'll confirm whether it has been modified... ftp.un4seen.com/incoming/Thanks Ian!!! Sorry, didn't see your reply quick enough. I reverted Comodo Internet Firewall to previous version 3.9 and XMPlay 3.4.2.111 works! All previous versions of the executable work as well, while they didn't work under Comodo Internet Firewall 3.10. Grrrrrr! Troubleshooting this issue consumed my 4th of July day and more. |
|
|
|
|
Logged
|
|
|
|
|
Ian @ un4seen
Administrator
Posts: 15276
|
|
« Reply #698 on: 6 Jul '09 - 14:23 » |
Quote
|
The same XMPLAY.EXE file that was giving the error message is now fine? In that case, I guess the Comodo update must have been just modifying things in memory and not the file itself.
|
|
|
|
|
Logged
|
|
|
|
|
winner
Posts: 193
|
|
« Reply #699 on: 6 Jul '09 - 14:30 » |
Quote
|
The same XMPLAY.EXE file that was giving the error message is now fine? In that case, I guess the Comodo update must have been just modifying things in memory and not the file itself.
The problem persisted after reboots. Yes it seems that Comodo modified it when unpacking and somehow the checksums of the executables then changed? Hmmmm. |
|
|
|
|
Logged
|
|
|
|
|
