| |
Stainless Steel
Registered: Mar 2003
Posts: 966 |
Sid Duzz It
Hi'yall,
I was wondering who else is using Shape's SDI editor around here. I would like to talk about the editor with other users about their experiences with it and maybe some technical blah blah aswell.
Cheers! |
|
... 169 posts hidden. Click here to view all posts....
|
| |
robozz
Registered: Oct 2003
Posts: 43 |
Two bugs related to the new version 2.1:
When using the new function loop play current sequence (shift+return) and
red mode(follow play) is activated there appears flickering in one or more channels
for a frame or so when the song loops.
but wait... there seems to be yet another condition for this bug to show, you have to
be using tempo values < 3
also it looks like sequence #00 is where the flickering data comes from.
The other one is perhaps not a bug, but the 2.1 keyboard manual says:
"Return Start playing music from top of current sequence"
well, it doesn't do what it says on the label! :)
it behaves more like:
"Z Play song from current line"
two keyboard commands that do the same thing can't be ideal :)
This next bug appears in older versions aswell, and also takes some explaining.
When restarting the music with F1 over and over again (while still playing)
and gate is still on, the sound is cut off.
Also note that it sometimes may take up to ten "repeats" (hitting F1) to produce this
behavior, but it could just as well fail after only two.
I've narrowed it down to certain adsr values, namely sustain and decay.
It only occurs with sustain F and any decay other that 0.
So for instance ADSR : 01F0 will under the conditions above turn off the channel,
while 00F0 or 01E0 will not. (attack and release doesn't seem to matter)
I can't understand what this is, maybe some hard restart thing? |
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
the sound fallouts that can happen are cause of the sid hardware. sometimes a RELEASE phase is still running, when there comes a new ATTACK, and depending how, it will give a no sound.
i never use play from sequence or so while composing.
i work in parts, and listen whole part from start using a mark with f2 and f1 to play. its a better workflow when composing.
also the tracker is going out of sync all the time when editing the playlist, coz a bug in the new loop system.
if this happens, you just have to go to top, and scroll all ways down again, then its ok. (grg alredy know this)
|
| |
robozz
Registered: Oct 2003
Posts: 43 |
When inserting and deleting lines in arpeggio table the pointer is given wrong value if it passes $40 one way or the other.
$40 + insert:
new value = $00 (not $41 as it should be)
$40 + delete:
new value = $fe (not $3f as it should be)
not a new bug, happens in all versions of SDI. |
| |
6R6
Registered: Feb 2002
Posts: 246 |
Bugs noted down.
I will fix them and release a update. |
| |
Fredrik
Registered: Apr 2009
Posts: 205 |
Sometimes the bmtass freezes when importaing the dumped musicfile with "arrow e"
why?
It does this with the new 2.1 version
|
| |
6R6
Registered: Feb 2002
Posts: 246 |
Quote: Two bugs related to the new version 2.1:
When using the new function loop play current sequence (shift+return) and
red mode(follow play) is activated there appears flickering in one or more channels
for a frame or so when the song loops.
but wait... there seems to be yet another condition for this bug to show, you have to
be using tempo values < 3
also it looks like sequence #00 is where the flickering data comes from.
The other one is perhaps not a bug, but the 2.1 keyboard manual says:
"Return Start playing music from top of current sequence"
well, it doesn't do what it says on the label! :)
it behaves more like:
"Z Play song from current line"
two keyboard commands that do the same thing can't be ideal :)
This next bug appears in older versions aswell, and also takes some explaining.
When restarting the music with F1 over and over again (while still playing)
and gate is still on, the sound is cut off.
Also note that it sometimes may take up to ten "repeats" (hitting F1) to produce this
behavior, but it could just as well fail after only two.
I've narrowed it down to certain adsr values, namely sustain and decay.
It only occurs with sustain F and any decay other that 0.
So for instance ADSR : 01F0 will under the conditions above turn off the channel,
while 00F0 or 01E0 will not. (attack and release doesn't seem to matter)
I can't understand what this is, maybe some hard restart thing?
Quote:
When using the new function loop play current sequence (shift+return) and
red mode(follow play) is activated there appears flickering in one or more channels
for a frame or so when the song loops....
Can't say I have noticed anything strange about this
Maybe if you give me a screenshot. ?
It will use the length of the sequence number your cursor are positioned in as base length and base sequence for the loop play.
So if you got varying lengths for the surrounding sequences then they might jump or flicker when the base sequence positions itself to top of screen.
Quote:
... the 2.1 keyboard manual says:
"Return Start playing music from top of current sequence"
well, it doesn't do what it says on the label! :)
Infact, you can do:
CBM+return : Start playing song from start of sequence
SHIFT+return : Play loop sequence (from start of sequence).
Return & Z: Play song from cursor position.
(Z was the old way) |
| |
6R6
Registered: Feb 2002
Posts: 246 |
Quote: When inserting and deleting lines in arpeggio table the pointer is given wrong value if it passes $40 one way or the other.
$40 + insert:
new value = $00 (not $41 as it should be)
$40 + delete:
new value = $fe (not $3f as it should be)
not a new bug, happens in all versions of SDI.
Fixed for the next update:
Fixed: Inserting/Deleting arpeggio data. Pointer bugs when crossing $40. (x register was wrong)
Fixed: Bug with dumper not working after some time of editing. (F4 to blue mode -> hit key -> Irq writes data into dumper code.)
Fixed: Full Screen view bugged when loading "castle in the sky" and some other v2.0 songs. (subroutine forgot to return zero)
Fixed: Sometimes pulse counter displayed #### insead of numbers. |
| |
6R6
Registered: Feb 2002
Posts: 246 |
It's on the sdi forum now.
Here's a download link:
https://sites.google.com/site/real2sid/sdi-2-1 |
| |
robozz
Registered: Oct 2003
Posts: 43 |
Quote:Can't say I have noticed anything strange about this
Maybe if you give me a screenshot. ?
It will use the length of the sequence number your cursor are positioned in as base length and base sequence for the loop play.
So if you got varying lengths for the surrounding sequences then they might jump or flicker when the base sequence positions itself to top of screen.
Make sure there's some data in sequence #0, and also that channel 4 is set to "unused", set tempo to 2 or 1 and turn on loop play with follow play and you'll see the bug.
There's another small bug when selecting arpeggios with keys > and < If you're not located in the arpeggio table the numbers aren't updated correctly. |
| |
6R6
Registered: Feb 2002
Posts: 246 |
Ok, fixed cycling arpeggios with < and >.
Ok, I understand where the play loop display bug get it's sequence 00 data from.
When it loops the displayer reads from the line above the loop line. And when you are on line 000 and it loops it tries to read from 7fe+07ff. Which contains Transpose 00 sequence 00. |
| Previous - 1 | ... | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 - Next |
