| |
Turtle
Account closed
Registered: Jan 2002
Posts: 70 |
GoatTracker v2.0 beta
That's a great one!!!!
Cadaver, didn't I hear you denying any activities in that direction a few weeks ago in an other thread.
I guess this major version release will make a lot composers more than happy. All points on my wishlist are marked as accomplished....
Now it's time to start a new topic of tips&tricks with this release.
Thanx,
Turtle |
|
... 1022 posts hidden. Click here to view all posts....
|
| |
cadaver
Registered: Feb 2002
Posts: 1153 |
At least not consciously.. probably my memory fails. What was it, how do you repro? |
| |
pvcf
Registered: Feb 2005
Posts: 18 |
the player recognize the multi-frames, but not the positions of called interrupts, it seems it plays together, at the same position , for a 2frames sid, like
jsr$1003
jsr$1003
rts
without giving the time between the 2 frames like in goattracker, the result is to play only every first frame
of the wavetable,
eg
41 00
41 0C
ff 00
only 41 00 will be played. (i think this is the problem...i'm not a coder)
so multispeed songs, saved to sid, sounds like played as singlespeeder, but with correct songspeed. |
| |
cadaver
Registered: Feb 2002
Posts: 1153 |
The calling interval of playroutine should be correct (because GT2 adds an init code to adjust CIA timer speed) but there may be small timing differences that result to the note starts being different. Fiddle with the buffered writes -option and see if it helps.
Typically, when using normal "hard" hardrestart in a 2x speed song (if you adjust the gatetimer value to 2x compared to the singlespeed value, so 4 default) the first wavetable row *should* be inaudible. |
| |
pvcf
Registered: Feb 2005
Posts: 18 |
ho cadaver,
i did'nt understand you right; the problem which i found:
in goattracker itself it sounds fine and mulitspeed worked perfektly as it shoult,
BUT if i export the song to sid-format, just for listening in acid64 or sidplay, the problem occours ;(
so its the exporter which doesnt handle the cia-timer correctly, shell i make a example for you, so that you can hear the problem?
ps.: thanx for taking care 8) |
| |
cadaver
Registered: Feb 2002
Posts: 1153 |
Yeah you can make an example, but I'm 99% sure it's due to small timing differences: when GT2 editor writes to reSID to achieve sound output, it doesn't take the actual C64 playroutine code, and how many machine cycles that takes, into account. It just assumes a fixed amount of cycles between each SID write.
So, if you depend on things that are timing-sensitive, it's only after exporting you get to know how exactly the song sounds like, and in that case the editor is "wrong".
If the exported song didn't set up the correct CIA timer value, you wouldn't even hear the song played at correct tempo.
|
| |
pvcf
Registered: Feb 2005
Posts: 18 |
hey cadaver, i tried to make a demo, but i found out that the bug is gone... (1) tested it with 2.67 and 2.68.
but there is a other problem, please listen to 2xsnare.mp3 and 2xsnare.sid,
mp3 is recorded direct out of goattracker (recordet on hardsid-pci with an old sid).
the high-claves sounds very bad in the exported sid.
second thing (its not a major one): pls listen to aah_test.mp3 vs the aah_test.sid,
the mp3 is exact at the same freq-shift like the goattracker, where is it from recorded.
(hardsid pci) and if i play it from acid64 or sidplay2 the frequnce table seems to be shifted up
a halftone.
(maybe thats the same probleme like in the 2xsnare where i used ringmodulation...?)
http://www.reflex-studio-storage.com/temp/freq_bug.zip (526kb)
(1) since i have plugged a 6581 instead of my good 8580 ... wtf... i'll check it later again with new sid model.
edit...
after on more test:
if i export the 2xsnare after loading the song WITHOUT press play, the exported sid and the claves sounds exactly like in goattracker.
if i start the song in goattracker, press stop, go on export, the sid sounds bad like the one in the package...
can you second this behavior ? (v2.68) |
| |
cadaver
Registered: Feb 2002
Posts: 1153 |
Hardsids operate on a different frequency than a C64, therefore the tuning will be different.
As for playing/stopping affecting the exported output, couldn't reproduce. |
| |
pvcf
Registered: Feb 2005
Posts: 18 |
Quote:Hardsids operate on a different frequency than a C64, therefore the tuning will be different.
thanx for testing 8)
and why hardsid sound different in goattracker+hardsid and acid64+hardsid and sidplay+resid (acid64+hardsid and sidplay+resid have the same tuning) ? |
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
pvcf: you are forgetting what i told you...
a .sid needs installed code to do the CIA timer stuff, so it will be multispeed.
|
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
Quote: Quote:Hardsids operate on a different frequency than a C64, therefore the tuning will be different.
thanx for testing 8)
and why hardsid sound different in goattracker+hardsid and acid64+hardsid and sidplay+resid (acid64+hardsid and sidplay+resid have the same tuning) ?
uh what ? :D
HardSID runs at 1.0 Mhz, not 0.987.... like C64
so hardsid tunes are in fact all playing too fast! |
| Previous - 1 | ... | 94 | 95 | 96 | 97 | 98 | 99 | 100 | 101 | 102 | 103 | 104 - Next |
