| |
Bamu®
Account closed
Registered: May 2005
Posts: 1332 |
The worst music editors?
Which are the absolutely worst music editors for the c64?
(crappy or no interface, huge rastertime usage, stupid handling, ugly bugs, worse hardrestart ...and so on.) |
|
| |
tlr
Registered: Sep 2003
Posts: 1790 |
Electrosound. _Huge_ rastertime usage!
Some really cool songs done using it though. :) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
"worse hardrestart"
thats a pretty "modern" feature which none of the early players/editors has.
as for huge rastertime usage...soundmonitor is the prime example i guess :) |
| |
T.M.R
Account closed
Registered: Dec 2001
Posts: 749 |
Nah, Electrosound is worse; sometimes a compiled Leccysound tune can take over a frame of rastertime! |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
more than a frame? wtf :) |
| |
Richard
Registered: Dec 2001
Posts: 621 |
Music System sucks :D |
| |
Raf
Registered: Nov 2003
Posts: 343 |
future composer seems to be user unfriendly ;-) |
| |
Puterman
Account closed
Registered: Jan 2002
Posts: 188 |
The Odin Tracker player is absolutely horrible when it comes to rastertime and memory usage. |
| |
Bamu®
Account closed
Registered: May 2005
Posts: 1332 |
Quote: The Odin Tracker player is absolutely horrible when it comes to rastertime and memory usage.
Isn't it possible to make a better player for Odin? |
| |
T.M.R
Account closed
Registered: Dec 2001
Posts: 749 |
It's possible to make a better driver for any editor, i have an (unreleased) version of Future Composer with a driver that Odie/Cosine wrote into it f'example. |
| |
cadaver
Registered: Feb 2002
Posts: 1160 |
From the player source, it seems to use multiplies for vibrato calculation, which isn't a good idea for speed. If exact same operation is desired, then either the player has to be slow or there have to be huge lookuptables. |
... 54 posts hidden. Click here to view all posts....
|
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 - Next |
