Search options (Page 2 of 4)

This is quite obvious practice, since patterns not stored in the sequence list will not be saved to disk, which is why the tracker assumes they were abandoned and safe to overwrite. However, described bug happens regardless of that.

Yes, these were my previews for 25Hz compo at CSDb that I shared with my friends and forgot to set the private flag. The music is already finished and now released.

Active/muted voice visual bug (2SID only).

When muting voices in 2SID mode, the visual representation of which channels are currently on/off is incorrect (e.g. muting VOC0 for SID1 makes the label VOC0 disappear for SID2 as well. It requires a few toggles to unclog. This is purely visual, the channel mute works fine.)

There are many quirks that could probably be brought up, but it's debatable whether they would fall under the tracker-specific behavior discussion or a "bug" report.

From the musician's point of view, the most imminent behavior that made my interaction with the tracker problematic was the AF column, and specifically - how the set finetune range works "separately" from the pitch bend (80-FF). To portray it better, I made this small graphic scheme:

However, there's very little reason to consider doing any adjustment/rework as of now, mostly because of the downward compatibility loss.

2SID executable PRG export (request).

It would be ultra-dope thing to be finally able to pack some of 2SID defMON pearls into the executable form.
https://www.youtube.com/watch?v=Gj0JVTV6IU4

Instrument "double jump" bug.

This is mini-report on newly discovered bug. Weirdly enough, it affects only packed files - PRG and RAW, but does not happen in the tracker.

Let's use this picture as an example:
- When we call A5 - it will play A5, jump to 9F, play 9F and and stop instead of jumping back to 9E (as continuous loop).

I'm not really up much for live sound programming, even though defMON seem to have great potential on the field.

Regarding that hard-restart thingy again, a sample tune here with a few instrument puzzles to think about.

Also, if you take a look at line 06, you'll notice 09 06 values ($09 for gate-bit and 06 for ADSR). You can change 06 from 01 to 0F to affect volume of the drum sound. Small "out of manual" trick if you struggled with optimizing volumes of your sounds/instruments.

I'd say that full hard-restart (including oscillator reset via test-bit) feels obligatory only with drums and snares as you really need that sharp "click" in the beginning of the sound/instrument. The rest (lead melody, bass, arpeggios etc.) should be fine with soft-restarting.

Now it's time to make things more complicated.

First of all, emulated environment works differently than real C64. Long story short, Vice 2.xx (reSID-fp engine) will usually not cut the sound when real C64 sometimes will, but (surprisingly!) Vice 3.xx will provide way more hiccups to your ears than real C64. Therefore, some hard-restart delays should be tested via trial-and-error, but usually 2 frames total are enough to do the job with short sounds.

Second, you need to set proper delay (DL) values to both gate closed (e.g. $00) and oscillator hard-restart ($09) frames/lines in order to make it work. Please note that using multi-speed tunes (x2/x4/x8) will require you to adjust those delay values accordingly (but not necessarily by multiplying them).

If you take a closer look at Amelinium's YT video, you'll notice that she restarts ADSR by setting 0000 value in WGWG ($00=no waveform and gate closed), and ADSR value set as 0F00. Then she'll open the gate by setting WG (gate) to $09 along with proper ADSR values that will later apply to the instrument ($41, $55... whatever). This is very similar to what I do and what I've also seen in Goto80's tracks (also a good reference).

Works like a charm and I'm very thankful we actually have manual hard-restart in defMON. The freedom of editing with this tool is simply mindfucking and gives tons of possibilities.