<![CDATA[ChipMusic.org - Horrible bug on Nanoloop 2.6]]> https://chipmusic.org/forums/topic/12676/horrible-bug-on-nanoloop-26/ Tue, 19 Nov 2013 15:15:43 +0000 PunBB <![CDATA[Re: Horrible bug on Nanoloop 2.6]]> https://chipmusic.org/forums/post/191455/#p191455 dasid says:

whoa. this deserves its own thread but man this a hefty update. excuse me while I go get lost in these new features for the day. love it. love Oliver.

]]> Tue, 19 Nov 2013 15:15:43 +0000 https://chipmusic.org/forums/post/191455/#p191455 <![CDATA[Re: Horrible bug on Nanoloop 2.6]]> https://chipmusic.org/forums/post/191454/#p191454 oliver says:
seatrash wrote:

is there a set release date for 2.7?

now.

details: http://www.nanoloop.com/two/specs.html

]]> Tue, 19 Nov 2013 14:51:32 +0000 https://chipmusic.org/forums/post/191454/#p191454 <![CDATA[Re: Horrible bug on Nanoloop 2.6]]> https://chipmusic.org/forums/post/191398/#p191398 seatrash says:

is there a set release date for 2.7?

]]> Tue, 19 Nov 2013 00:06:58 +0000 https://chipmusic.org/forums/post/191398/#p191398 <![CDATA[Re: Horrible bug on Nanoloop 2.6]]> https://chipmusic.org/forums/post/191360/#p191360 _-_- says:

Intriguing.

]]> Mon, 18 Nov 2013 19:29:41 +0000 https://chipmusic.org/forums/post/191360/#p191360 <![CDATA[Re: Horrible bug on Nanoloop 2.6]]> https://chipmusic.org/forums/post/191348/#p191348 dasid says:

boom there you go tongue

]]> Mon, 18 Nov 2013 18:48:48 +0000 https://chipmusic.org/forums/post/191348/#p191348 <![CDATA[Re: Horrible bug on Nanoloop 2.6]]> https://chipmusic.org/forums/post/191330/#p191330 oliver says:

Actually, there are no more notes in 2.7.

]]> Mon, 18 Nov 2013 17:24:57 +0000 https://chipmusic.org/forums/post/191330/#p191330 <![CDATA[Re: Horrible bug on Nanoloop 2.6]]> https://chipmusic.org/forums/post/191324/#p191324 dasid says:

I do love the squares. should def be a toggled feature.

]]> Mon, 18 Nov 2013 16:54:13 +0000 https://chipmusic.org/forums/post/191324/#p191324 <![CDATA[Re: Horrible bug on Nanoloop 2.6]]> https://chipmusic.org/forums/post/191323/#p191323 _-_- says:

Yeah, that would be great in a live performance. Just don't change it to note names entirely! wink

]]> Mon, 18 Nov 2013 16:40:23 +0000 https://chipmusic.org/forums/post/191323/#p191323 <![CDATA[Re: Horrible bug on Nanoloop 2.6]]> https://chipmusic.org/forums/post/191321/#p191321 dasid says:

even though I know the workaround, I sometimes forget so I look forward to this update!
my biggest wish now is to have the note names when making chords (the way it is in nl 1.6) - it would make tuning on the fly way easier

]]> Mon, 18 Nov 2013 16:21:50 +0000 https://chipmusic.org/forums/post/191321/#p191321 <![CDATA[Re: Horrible bug on Nanoloop 2.6]]> https://chipmusic.org/forums/post/191229/#p191229 oliver says:

I'm sorry for that. Will fix this with 2.7, which is around the corner.

In the meantime, please use this workaround: Only change a bank's name after you have seen that bank's song.

After a bank's name was changed, the whole bank is re-saved with the new name and song data from RAM as soon as you select a different bank or leave the file menu (select). However, song data are only loaded in RAM when entering the song editor. So, when the bank is re-saved after a name change, different or empty song data may be present in RAM.

In 2.5 / 2.6, this has been fixed partially: When selecting a different bank after a bank's name was changed, the changed bank is saved with the correct song data (by loading them from flash first). But it still uses the song data in RAM when leaving the file menu. So in 2.5 / 2.5, you may just switch to a different bank and back after the name was changed.

]]> Sun, 17 Nov 2013 20:31:15 +0000 https://chipmusic.org/forums/post/191229/#p191229 <![CDATA[Re: Horrible bug on Nanoloop 2.6]]> https://chipmusic.org/forums/post/190786/#p190786 e.s.c. says:

this bug is also in 2.3, never upgraded to 2.5, so i cant say for sure if its an issue there, too

]]> Wed, 13 Nov 2013 16:48:57 +0000 https://chipmusic.org/forums/post/190786/#p190786 <![CDATA[Re: Horrible bug on Nanoloop 2.6]]> https://chipmusic.org/forums/post/190785/#p190785 e.s.c. says:

its a documented bug, but a weird one (and id thought he'd fixed it by now)... if you rename a bank without having gone into its song screen first, it overwrites your song pattern with whatever song pattern was loaded at the time (or blanks it if none is loaded)

]]> Wed, 13 Nov 2013 16:45:53 +0000 https://chipmusic.org/forums/post/190785/#p190785 <![CDATA[Re: Horrible bug on Nanoloop 2.6]]> https://chipmusic.org/forums/post/190782/#p190782 defPREMIUM says:

that's horrible!

]]> Wed, 13 Nov 2013 16:21:35 +0000 https://chipmusic.org/forums/post/190782/#p190782 <![CDATA[Horrible bug on Nanoloop 2.6]]> https://chipmusic.org/forums/post/190781/#p190781 Robin says:

It's happened a couple of times: For some reason, a song pattern gets overwritten with the song pattern from another bank. Thankfully the bank itself remains intact. I'm pretty sure both times this happened, I had just given a bank a name, and it was the song of that bank which got changed.

Anyone else had this problem? Any suggestions on how to avoid it?

I'm guessing naming a bank before making a song, and then not changing it may avoid this. And, of course, backup, which I'm working on...

R.

]]> Wed, 13 Nov 2013 16:18:56 +0000 https://chipmusic.org/forums/post/190781/#p190781