-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
losing loop points (.it .mod .xm .s3m) #33
Comments
Hi, Yes, xmodits should do this automatically if it finds valid loop points in a sample (for versions But if the trackers do have valid loops, then this sounds very strange. Can you provide a screenshot of the settings you used? If you can provide an example module, that would also help. Thanks! |
the screenshots you provided are very similar to what i'm using. i had thousands of chipsounds (20 bytes etc) without loop points. is the issue that i'm saving them as wav instead of raw? will raw have the "module loop-points"? @B0ney |
No, saving the samples as When you were configuring the program, did you happen to uncheck "Self Contained"? Disabling this would mean that all of the ripped samples are placed in the destination folder. But since most of the samples have similar names (01.wav, 02.wav, etc), there's an extremely high chance that those names would collide, resulting in data being overwritten. This can be mitigated by checking "prefix samples", which will prefix the ripped samples with the tracker's filename: example for
This was a UX issue I've recently fixed. Was that the case for you? |
i haven't had any issues with the file naming itself. just the loops going missing. from my pov, the file naming tickboxes are already great, and there was no overwriting. :) |
@esaruoho Okay, I think I found the source of the problem. Scream Tracker 3 and Impulse Tracker will only read sample data from a WAV file. So additional metadata such as loop points are ignored. To load samples with looping, you would need to load an They were originally planned for version They're not that hard to implement, so |
wow, hey, thanks for looking at it! so in theory, in a future release, i'll be able to load .its files? how near or far is that from 8th july 2023? :) |
Yes, here's what I currently have planned for version
The next release is relatively small, so it shouldn't take long. Supporting more platforms for the GUI version is quite finicky, so I may end up removing some targets. Not making any promises, but you should expect a release some time between |
@esaruoho Hi, I've published the first release candidate for version You can download the builds here. Do let me know if the samples load properly under Impulse Tracker 2 and Scream Tracker 3. Thanks! |
ok i finally have a method for transferring files easily from mac to windows 98 se / dospc. so i can finally try the build and see if the files will have loop points. btw any chance of providing ARM architecture macOS builds too?
you have fixed it! i can now get loops in! this is awesome!!! thank you so much!! |
Awesome!
Yes. The next release will have a single universal Currently, only the command line version has builds for Apple Silicon, so you can use that for the time being: And regarding the logs you provided:
I am most interested in I am not too concerned with the last 2 errors though. The |
Also, do you have any more Thanks for testing it out :) |
of course. here it is. i don't know what it is.
no loop-point issues at all anymore. i was glad to see that you enabling .its allowed me to get going and that .its files can actually be keyjazzed in the impulsetracker f3 sample loader, which is super-important. i was worried i needed to do it from the F4 instrument loader, which would be completely different and probably unjazzable. so, yes, the original issue can now be considered fixed and ticket can be closed. much appreciated. sorry it took me a month to try the build! |
Cheers! Btw, I checked out the file you've uploaded. After a bit of analysis, it's actually a zip file with its extension changed to Just change its extension back to |
so i just dumped 4600 modules to wav-samples, and realized all the loop-points are gone.
is there a way of using xmodits so that the loop-points are not lost? i'm trying to load the samples into ST3/IT2.
The text was updated successfully, but these errors were encountered: