| |
6R6
Registered: Feb 2002
Posts: 245 |
SDI 2.0 Beta
Hi.
A working preview here:
http://home.eunet.no/~ggallefo/sdi/
Report your bugs and thoughts here:
GRG |
|
... 195 posts hidden. Click here to view all posts....
|
| |
Bamu®
Account closed
Registered: May 2005
Posts: 1332 |
Quote: Quoting nataFor my taste SDI 2.0 is a bit too complex.
Not really, its about as complex as any other music editor (i dare to say gt is no less complex)
Its just a matter of time you invest to get around its usage. I'd say 1-2 weeks, given you know the basics of composing on the c64.
You are right. GT2 & SDI has about the same complexity. |
| |
Bamu®
Account closed
Registered: May 2005
Posts: 1332 |
Quote: Well, I can live without it, but MMC64 support would be nice. So we'll wait for a bios with load/save routines, I guess...
Maybe some custom loader/saver included in SDI would help. As far I can remember SDI has enough free memory for such a feature. |
| |
Henne
Registered: Feb 2005
Posts: 26 |
Hi!
I made a tune in SDI 2.0 beta 7 that plays correctly in the editor. But in the stand-alone player it plays the first few patterns (or sequences) correctly and then one voice doesn't jump to the next pattern in time. From there on this voice is delayed with regard to the other two voices.
I already spent several hours looking for some error in the tune. But I didn't find anything. In the editor it seems to be ok.
GRG, I can send the tune to you if you want to have a look.
Henne
|
| |
Stainless Steel
Registered: Mar 2003
Posts: 966 |
I've had a similar problem with one of my sdi tunes lately. The first pattern of channel 3 would play 1 pattern delayed. i couldn't figure out why. I copied the pattern date from the pattern i thought caused the delay into another pattern and exchanged them. It worked after that. Not sure if that helps you.
|
| |
6R6
Registered: Feb 2002
Posts: 245 |
@Henne and Stainless Steel:
I looked at this today. And it is a player bug.
Load the player source into bmtass and
find the ;--- SEQUENCER--- part of the player.
Scroll down till you find the line saying:
"beq dur_20"
Remove this line and it should be ok.
|
| |
Stainless Steel
Registered: Mar 2003
Posts: 966 |
Oh btw glenn, ive been having the odd situation that the dumped tune has large sections of $00 bytes in it.
I removed them manually in tass and the tune worked fine afterwards. i think i read something somewhere about that problem but i dont recall where or what it was ?
PS : i still use the old 1.8 editor sometimes and just append the z8,z9 and fs sections to the dumped source from 1.8 when compiling with the 2.07 player. dunno if that has anything to do with it.
|
| |
Stainless Steel
Registered: Mar 2003
Posts: 966 |
Feature request : copy / paste across all 3 channels.
|
| |
6R6
Registered: Feb 2002
Posts: 245 |
At LCP 2009 we tested a swedish C64 with the SDI editor.
It turns out that it doesnt work very well. It has to do with the keyboard layout.
Swedish C64 is not compatible with the editor ( all versions ).
|
| |
GT
Account closed
Registered: Sep 2008
Posts: 308 |
Quote: @Henne and Stainless Steel:
I looked at this today. And it is a player bug.
Load the player source into bmtass and
find the ;--- SEQUENCER--- part of the player.
Scroll down till you find the line saying:
"beq dur_20"
Remove this line and it should be ok.
Don't remove BEQ dur_20, it has a purpose of setting higher duration in the packed data than $20. Simply having twenty free "-- ---" lines between commands make this bug. I forgot 15 years ago to add duration $20 also for that command. If you follow positive numbers in the tracker, you won't have this bug. It will be fixed though. ;) |
| |
GT
Account closed
Registered: Sep 2008
Posts: 308 |
Quote: At LCP 2009 we tested a swedish C64 with the SDI editor.
It turns out that it doesnt work very well. It has to do with the keyboard layout.
Swedish C64 is not compatible with the editor ( all versions ).
Yes, that was my Swedish C-64, Glenn. Kernal-rom is swedish, so some keys are on the wrong positions. Well, it is swedish though, that says a little. It's not SDI's fault. :) |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | ... | 21 - Next |
