Print

[sverx]

I'm working mostly on this "lapinjrven_j"... I've found -for instance in pattern 04 channel 10- a lot of effects EB0...
Here, in the documentation, it says that it's "Fine volume slide down"... but -of course- it has no sense to lower by 0 the volume... so it means that EBx has 'memory effect'? Does it share this memory with Axx and/or with EAx ?

Thanks

[raina]

EBx effect memory is shared with EAx, but not with Axy. It wouldn't be the same parameter as EAx/EBx operates per row and Axy does so per tick.

[Saga Musix]

aren't confusing the both now? ticks are finer, so EBx should be per tick and A0x per row...

[raina]

Fine slides are fine because they are applied once per row. Normal slides are applied on every tick except the first one so that makes them faster and more coarse. Just compare the results after the row is played.

[sverx]

EBx effect memory is shared with EAx, but not with Axy.

mmm... so you mean both

1. EAx and EBx effects both do have 'memory' effect.
2. An EA0 after an EBx (or vice-versa) will restore the volume to the previous effect.

... right? And do this effect shares the effect memory with the corresponding effect in the volume column? And the memory is 'per channel', right?

And, about Axy effect, do this shares the effect memory with some other effect?

Thanks once more for the help

Ciao!

[Saga Musix]

Fine slides are fine because they are applied once per row. Normal slides are applied on every tick except the first one so that makes them faster and more coarse. Just compare the results after the row is played.

ah right, i confused "more sensitive" and "finer" once again

[raina]

mmm... so you mean both

1. EAx and EBx effects both do have 'memory' effect.
2. An EA0 after an EBx (or vice-versa) will restore the volume to the previous effect.

... right? And do this effect shares the effect memory with the corresponding effect in the volume column? And the memory is 'per channel', right?

And, about Axy effect, do this shares the effect memory with some other effect?

Thanks once more for the help

Ciao!

1. & 2. Yep.

Volume column: Yes and no. Those volume column effects that can't be entered without a value (volume and panning slides), aren't shared. But an M0 can repeat a 3xx value and thus produce a finer effect than M1 does. And V0 can continue a 4xy vibrato. Memory is per channel. If you only use one value for a command throughout the whole song, it's possible to only enter it once in the beginning of the song. But working in MilkyTracker it's practical to introduce the values per pattern because the memory is reset when playback is started. In Fasttracker II, the memory was very persistent; values were remembered even between songs which could result in "faulty" modules where effect values aren't introduced properly the first time, or at all. An easy mistake was using R0y instead of R8y and when modules were played in succession in FT2, Rxy x value was inherited from a previously loaded module possibly ruining playback for the current one. Only restarting the program would fully erase effect memory in FT2.

Axy effect memory is shared with 5xy and 6xy.

[sverx]

Volume column: Yes and no. Those volume column effects that can't be entered without a value (volume and panning slides), aren't shared.

Mmm... I never noticed I coulnd't place a '-0' or a '+0' (or a 'down 0' or 'up 0', or '<0' or '>0') in the volume column... by the way it's still possibile for this values to be zeroed in a module... I mean the XM documentation says:

Code: [Select]

$60-$6f   Volume slide down
$70-$7f   Volume slide up
$80-$8f   Fine volume slide down
$90-$9f   Fine volume slide up
[...]
$d0-$df   Panning slide left
$e0-$ef   Panning slide right
so -even if MilkyTracker wouldn't let me insert it- I guess it should support it... I think.
Ok, I'm going to test it later...

Axy effect memory is shared with 5xy and 6xy.

Nice to know that, even if I'm still not supporting 5xy and 6xy effect yet.

Thanks! Ciao

[sverx]

[...]... I mean the XM documentation says:

Code: [Select]

$60-$6f   Volume slide down
$70-$7f   Volume slide up
$80-$8f   Fine volume slide down
$90-$9f   Fine volume slide up
[...]
$d0-$df   Panning slide left
$e0-$ef   Panning slide right
so -even if MilkyTracker wouldn't let me insert it- I guess it should support it... I think.
Ok, I'm going to test it later...

I made that test with MilkyTracker: $60, $70, $80 etc... are completely ignored, they do not even appear in the pattern
So there's no memory effect and -of course- sliding of a value that is zero has no meaning.

Does somebody knows if other trackers have different effect with that?