I can open both at once... not sure why you wouldn't be able to. (Oh you mean if single instance is checked? I don't know how that is handled. Probably it has changed in 0.3.7.)
If you want to post an example of the hardware slides, go ahead, but a good way to check for yourself is export back to NSF and listen to that in whatever foo_gep is to compare.
I don't know if this is a glitch, but it happens to me both with v0.3 and v0.4: I used to be able to open both FT and NSFImporter at the same time, even when "Single Instance" was checked in FT's option (which is a good thing), and now I can't do that anymore.
Otherwise, all is well in Importer world Thanks!
EDIT: Actually, I don't know if it's an issue with the importer or Famitracker itself, but the hardware slides from imported NSFs sound slightly lower in pitch than they do in foo_gep.
What happens when you try to open multiple instances? Does it crash? I seem to be having a problem in Linux with Wine 1.3 where any version of famitracker will crash if something else is using DirectSound while it initializes, but somehow plugging in a USB sound card fixes it and I can have an indefinite number of tracker windows open.
_______________________
Everything moves real slow when it's 40 below.
a good way to check for yourself is export back to NSF and listen to that in whatever foo_gep is to compare.
Just did that, and the exported NSF does have the same problem.
com63 wrote:
What happens when you try to open multiple instances? Does it crash?
Nah, it just won't open the other if one of the two is already open. Just like it does when I try to open a second instance of FT. It didn't use to do that with v0.2, though...
Yeah, but don't you think it's inconvenient to have 2 famitrackers on HDD, one with NSF import feature, but without possibility to save?
Since it's modded FT after all, can't you just unlock it? It would be easier for creators of NES OST remixes.
Or you could take the extra two seconds to just save it to your hard drive. Think of it as opening a read-only file, you can view it, but in order to edit it you'll have to make your own copy.
don't you think it's inconvenient to have 2 famitrackers on HDD
As a matter of fact, no. No, I don't think it's an inconvenience. But if you beg to differ, Famitracker is opensource, and so is the importer. So feel free to edit rainwarrior's code to make editing possible in the importer.
There has been talk of including NSF importing in Famitracker in the distant future, but it probably isn't a priority for now.
I do it so that people will still use the main build of FamiTracker. I don't want to maintain and distribute a real fork. This way its purpose is clear, and you will know which you're using always.
Honestly, rainwarrior has great thinking. It's only an add-on & it would be up to JSR if he wants to implement it in the next official FamiTracker build. And why maintain a separate fork if the original project's still active & if you're a contributor to the original project? This is beside not having enough time on your hands to do other things.
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
Thanks!
