| |
Tommy
Registered: Sep 2024
Posts: 11 |
Questions about the packer/relocator in GoatTracker
Hi there!
I've been playing around a bit in GoatTracker and might release my first two songs on the C64 soon.
So here's the newbie question - when exporting to PSID from GoatTracker, what settings do you use? I don't use anything fancy in my songs and they all run at 1x. I've just tried these settings with seemingly good results in Sidplay3:
Buffered SID-writes: "Yes"
Sound effect support: "No"
Volume change support: "No"
Store author-info: "Yes" (*)
Use zeropage ghostregs: "No"
Disable optimization: "No"
Full SID buffering: "Yes" (**)
SELECT START ADDRESS: "$1000" (***)
SELECT ZEROPAGE ADDRESS: "$FD-$FE (Unused)"
SELECT FORMAT TO SAVE IN: "SID - SIDPlay music file format"
* How does the timing mark work? I've tried putting DXY (where X isn't 0) at different positions of the song but it doesn't seem like PSID picks it up and displays the song length. What am I missing here?
** Is "No" fine if the song runs at 1x?
*** I guess this only matters for a demo/game, but not for a PSID?
Are there any settings I might want to change for whatever reason? It would be a shame if I would have to release fixed versions of songs just because I don't fully grasp the consequences of all the settings.
Since I don't have any real hardware currently available to test the songs on (apart from a really old HardSID with a 6581 and a 8580 which can't be used in a modern computer) I guess I'll just have to cross my fingers and hope for the best.
Any help would be greatly appreciated. |
|
| |
Hein
Registered: Apr 2004
Posts: 954 |
Quoting Tommy
Buffered SID-writes: "Yes"
Sound effect support: "No"
Volume change support: "No"
Store author-info: "Yes" (*)
Use zeropage ghostregs: "No"
Disable optimization: "No"
Full SID buffering: "Yes" (**)
SELECT START ADDRESS: "$1000" (***)
SELECT ZEROPAGE ADDRESS: "$FD-$FE (Unused)"
SELECT FORMAT TO SAVE IN: "SID - SIDPlay music file format"
* How does the timing mark work? I've tried putting DXY (where X isn't 0) at different positions of the song but it doesn't seem like PSID picks it up and displays the song length. What am I missing here?
** Is "No" fine if the song runs at 1x?
*** I guess this only matters for a demo/game, but not for a PSID?
* Timing marks are only needed if a programmer wants to do something based on your timing marks. For example, switching effects in a demo whenever the timing mark value == XY.
** AFAIK, full sid buffering would only be usefull if there are some instability bugs in high speed tunes (higher than 1x at least)
'Buffered SID writes' on the other hand does improve quality of playback (it's a bit snappier), but it also costs a bit more rastertime. So you can keep that 'yes' for your standalone songs.
*** Yes, if a programmer needs your tune in some other memory location, you can change it accordingly. But $1000 is a good default to keep, especially for crack intros. |
| |
Tommy
Registered: Sep 2024
Posts: 11 |
Quoting HeinQuoting Tommy
* How does the timing mark work? I've tried putting DXY (where X isn't 0) at different positions of the song but it doesn't seem like PSID picks it up and displays the song length. What am I missing here?
* Timing marks are only needed if a programmer wants to do something based on your timing marks. For example, switching effects in a demo whenever the timing mark value == XY.
Ah, ok. So I completely misunderstood the feature. =) Thanks for clearing it up for me. Now it makes more sense.
So can I assume that Sidplay3 tries to figure out the length of the song by itself? The two (unfinished) songs I've exported have both been looping, is that the reason that Sidplay3 doesn't show the length of the song? |
| |
Hein
Registered: Apr 2004
Posts: 954 |
Quoting Tommy
So can I assume that Sidplay3 tries to figure out the length of the song by itself? The two (unfinished) songs I've exported have both been looping, is that the reason that Sidplay3 doesn't show the length of the song?
I think the songlengths database is updated each time there's a new HVSC release. So when your tunes are added to HVSC, the songlengths are stored in a seperate file. |
| |
Tommy
Registered: Sep 2024
Posts: 11 |
Quoting Hein
I think the songlengths database is updated each time there's a new HVSC release. So when your tunes are added to HVSC, the songlengths are stored in a seperate file.
Ah, that explains it. Thanks for clearing up another misunderstanding. |
| |
LMan
Registered: Jun 2010
Posts: 83 |
Edit -sorry wrong thread please delete |
