Version 0.5 preview

General discussion about tracking, help and support.
User avatar
recme
Posts: 96
Joined: Thu May 07, 2015 12:47 am
Location: Somewhere, FL
Contact:

Re: Version 0.5 preview

Postby recme » Thu Jul 16, 2015 9:04 pm

i was trying to make c64 drums on 5b, which works perfectly. however, whenever i start the song up, the noise and a few notes of the pulse are muted for some reason. i've attached an ftm below to show you what i mean
Attachments
missingnoise.ftm
(1.89 KiB) Downloaded 27 times

8BitZtunerYT
Posts: 379
Joined: Thu Apr 23, 2015 7:20 pm
Location: Somewhere stuck in Winamp

Re: Version 0.5 preview

Postby 8BitZtunerYT » Thu Jul 16, 2015 9:35 pm

Are you using the latest beta?
slowly ceasing to exist.
"8BitZ caresses his keyboard as he orgasms to the sounds of Winamp."
-retrodpc, 2015

User avatar
recme
Posts: 96
Joined: Thu May 07, 2015 12:47 am
Location: Somewhere, FL
Contact:

Re: Version 0.5 preview

Postby recme » Thu Jul 16, 2015 10:20 pm

yes. i am using beta 5.

8BitZtunerYT
Posts: 379
Joined: Thu Apr 23, 2015 7:20 pm
Location: Somewhere stuck in Winamp

Re: Version 0.5 preview

Postby 8BitZtunerYT » Fri Jul 17, 2015 11:45 am

NSFplug seems to have issues when playing a N163 PCM Stream at 67hz

Attached FTM (works in both 0CC-FT and the Latest Beta) and NSF
Attachments
Yeah! WOO 0CC-FT N163 PCM Original declicked.nsf
(22.25 KiB) Downloaded 28 times
Yeah! WOO 0CC-FT N163 PCM Original declicked.ftm
(32.41 KiB) Downloaded 38 times
slowly ceasing to exist.
"8BitZ caresses his keyboard as he orgasms to the sounds of Winamp."
-retrodpc, 2015

User avatar
HertzDevil
Posts: 475
Joined: Thu Apr 23, 2015 7:39 pm
Location: Hong Kong SAR
Contact:

Re: Version 0.5 preview

Postby HertzDevil » Fri Jul 17, 2015 12:22 pm

I am able to reproduce the same issue in 0CC-FamiTracker because the tempo value is set to 255, which is much higher than what the engine speed allows (167.5 BPM); the internal tempo counter underflows after the subtraction in ft_skip_row_update, causing some rows to become much longer. Because the remainder of the tempo division has been taken care of since 0.4.6, that routine should make sure var_Tempo_Accum never underflows:

Code: Select all

ft_skip_row_update:
    ; Speed division
    ; ...
    lda var_Tempo_Accum + 1
    sbc var_Tempo_Count + 1
    bcs :+
    lda #$00
    sta var_Tempo_Accum
:   sta var_Tempo_Accum + 1
If this check is absent, for the official build the only way to get around this in exported NSFs would be to set the engine speed to default (60 Hz) first, and the tempo to 150, then export the NSF, and finally edit the refresh rate at $006E as necessary to minimize the phase shift through the N163 waves. Although the 0.5.0 beta allows directly setting that refresh rate, most values do not admit a straightforward way to specify the number of ticks per row, rendering them unstable for use with N163 PCM.
refactoring 0cc-famitracker

User avatar
ollaxe
Posts: 736
Joined: Mon Apr 20, 2015 7:07 pm
Location: Sweden
Contact:

Re: Version 0.5 preview

Postby ollaxe » Fri Jul 17, 2015 10:26 pm

Volume in Digging in the past on the 5B is totally broken. It wasn't like that in the last beta I tested it in, which is beta 2.

I also noticed that 5B note table or whatever it's called has been modified slightly (which I'm really happy about, no need for P7F on high-pitched notes anymore, yay!), so I'm going to have to edit this song accordingly later when the volume glitch has been fixed.

Edit: This glitch has for some reason stopped happening. I have no idea how or why, but whatever.

Edit 2: I'm dumb. I'm just completely idiotic and stupid. I think with my feet. I had sunsoft 5B at +6 dB in the mixer.
Last edited by ollaxe on Sun Jul 19, 2015 3:55 pm, edited 2 times in total.
Hi! I'm not really active here anymore but I still make music. Nowadays I mostly make dubstep with emphasis on good melodies and chord progressions.
SoundCloud: soundcloud.com/ollaxe
Twitter: twitter.com/ollaxe
Discord server: dis.gd/tK7uRnc
I'm also on Spotify. Search "OllAxe" and you'll find me.

User avatar
HertzDevil
Posts: 475
Joined: Thu Apr 23, 2015 7:39 pm
Location: Hong Kong SAR
Contact:

Re: Version 0.5 preview

Postby HertzDevil » Sat Jul 18, 2015 8:17 am

The note displays next to the registers are incorrect when PAL is enabled; for example, C-3 gives "281.77 Hz C#4 +28".
refactoring 0cc-famitracker

8BitZtunerYT
Posts: 379
Joined: Thu Apr 23, 2015 7:20 pm
Location: Somewhere stuck in Winamp

Re: Version 0.5 preview

Postby 8BitZtunerYT » Sat Jul 18, 2015 12:43 pm

I am not entirely sure if that's a bug too but, the 5B Squares are "pitched down" a few cents.

The Attached module and it's source NSF sound somewhat different, the FTM was pure boredom but since the latest Beta it sounds pitched down than normal.
I don't know if that was changed to fix the 2A03 + 5B issue (something with the n163 interferring somewhere).
Attachments
entry009.nsf
(32 KiB) Downloaded 23 times
wat 0.5 Beta.ftm
(1.51 KiB) Downloaded 20 times
slowly ceasing to exist.
"8BitZ caresses his keyboard as he orgasms to the sounds of Winamp."
-retrodpc, 2015

User avatar
Xyz
Posts: 297
Joined: Tue Apr 21, 2015 4:36 pm

Re: Version 0.5 preview

Postby Xyz » Sun Jul 19, 2015 4:27 pm

That nsf (which is mine) was not made in Famitracker but made in ppMCK, which uses a different tuning table from Famitracker.
Attachments
Tuning Difference.txt
(1.39 KiB) Downloaded 17 times
>:( Fuck you hentai boy i hate you squid anus

User avatar
HertzDevil
Posts: 475
Joined: Thu Apr 23, 2015 7:39 pm
Location: Hong Kong SAR
Contact:

Re: Version 0.5 preview

Postby HertzDevil » Sun Jul 19, 2015 9:11 pm

8BitZtunerYT wrote:I am not entirely sure if that's a bug too but, the 5B Squares are "pitched down" a few cents.

This is mentioned at the change log in the OP:
  • Fixed YM2149 period table being off by one.

This in turn is due to the fact that 2A03 and 5B share a similar frequency generator:

Code: Select all

2A03: Frequency = Clock / (16 * (Period + 1))
5B:   Frequency = Clock / (2 * 16 * Period)
The previous versions had the inaccurate behaviour where the 5B and the 2A03 use the same period table, so the same value results in a higher frequency for 5B than one would expect. For the fixed behaviour the 5B will be exactly an octave lower than the 2A03 when the same note is inputted.
refactoring 0cc-famitracker


Return to “General Talk”

Who is online

Users browsing this forum: No registered users and 1 guest