Mod Archive Forums

Music Production => NitroTracker => Tracking => NitroTracker Bug Reports => Topic started by: People on July 14, 2008, 11:53:33

Title: [nobug] NT 0.4 "sng" and "smp" blank
Post by: People on July 14, 2008, 11:53:33
I came across a bug when you use NT 0.4 and go the the sample and song file area. When you navigate to folders on your card, NT will remember and save the location of the last folders you accessed in the file area for the next time you run NT. But if you rename and/or move the folders on your card that were last accessed from NT 0.4, the next time you run NT and go to the file area, the "sng" and "smp" area is blank. There is no file box and no scroll bar. The one way of fixing this, is to go to the "DATA" folder at the root of the card and open the "NitroTracker" folder and delete the "NitroTracker.conf" file. I am using "NT 0.4" on the NAND memory on AK RPG.
Title: Re: NT 0.4 "sng" and "smp" blank
Post by: infradead on July 16, 2008, 05:26:41
you've corrupted the config file and that's why you need to delete it for it to work
Title: Re: NT 0.4 "sng" and "smp" blank
Post by: [Alpha]-0mega- on July 25, 2008, 16:01:17
I wouldn't say it's corrupt, all I had to do was make a folder with the same name as the original one. in the original location.

After that I could just navigate to the new location and delete the old folder.
Title: Re: NT 0.4 "sng" and "smp" blank
Post by: The Onyxmizer on December 26, 2008, 18:08:02
thanks for the tip off. I've been needing to rearrange my card, but was too afraid to.

:)
Title: Re: NT 0.4 "sng" and "smp" blank
Post by: usrfriendly on December 30, 2008, 10:57:21
I always reinstalled NitroTracker to fix it.
Title: Re: NT 0.4 "sng" and "smp" blank
Post by: cavemaneca on March 15, 2009, 07:48:07
simplest was is to just delete the config file. fast and easy, and if you have dsorganize you can do it without a computer.
Title: Re: [nobug] NT 0.4 "sng" and "smp" blank
Post by: devin on March 24, 2010, 08:21:44
Thank you so much for the solution!  I started freaking out from this same problem.  I think it started when my windows PC asked me if I wanted to fix the file structure on the card I'm using.  I said 'yes' and this is what happened...