Started it under linux/wine and windows with vbox. Works, but it is sloooooooooooow, eskimonika plays at about 1/2 its real speed in both ways. Is there a native linux version of this player?
Edit: eskimonika is supposed to play at 100 Hz, maybe this causes problem.
Is there some trick to running SIDcog Serial Player under Windows 7?
The FTDI chip's LEDs don't flash at all when a song is supposed to be playing. There also isn't any sound.
I'm using a Propeller Demo board.
I attached a couple of screen shots showing the com port used.
Edit: Some additional information. The play list is saved from one session to the next but not the com port information. I do see "COM20" inside the file "settings.dat" when I open it with notepad.
@Duane Degn
If I remember correctly, there's something extra funky with com ports with higher number than 9 in Windows; They are internally named differently for some reason.
How come you are getting such a high numbered port anyway?
The com port is actually retrieved after restarting the application. It's just that the "line edit field" doesn't get updated correctly. (tabbing around will make the field get updated)
@pik33 The reason why "eskimonika,sid" plays too slow is because it doesn't use VBL interrupts (50 Hz) and SIDcog serial player just assumes 100 Hz is right for timer interrupt driven tunes. (Eskimonika is really 200 Hz)
I can easily compile a Linux version of the player, because it's written for the QT framework.
The emulated C64 in "SIDcog serial player" just constists of the 6502 processor, 64kB of memory and a SID.... that's ALL!
Obiously tunes making use of ANY other hardware component in the C64 will play incorrectly. (if at all)
The coolest feature found in the player is the ability to "run 6502 code backwards", just try the slider.
(Of course there's a trick to it)
So, if there are songs with strange frequencies, like this Eskimonika (it is beautiful piece of SID music) I have a feature request: custom frequency set in next version of player
Roadster
Posts: 209
Comments
I've sent a message out to Ahle2, perhaps he'll re-post.
OBC
/Ahle2
You are welcome!
Are you just playing around with the code or do you have an interesting project to share?
/Ahle2
Edit: eskimonika is supposed to play at 100 Hz, maybe this causes problem.
The FTDI chip's LEDs don't flash at all when a song is supposed to be playing. There also isn't any sound.
I'm using a Propeller Demo board.
I attached a couple of screen shots showing the com port used.
Edit: Some additional information. The play list is saved from one session to the next but not the com port information. I do see "COM20" inside the file "settings.dat" when I open it with notepad.
If I remember correctly, there's something extra funky with com ports with higher number than 9 in Windows; They are internally named differently for some reason.
How come you are getting such a high numbered port anyway?
The com port is actually retrieved after restarting the application. It's just that the "line edit field" doesn't get updated correctly. (tabbing around will make the field get updated)
@pik33
The reason why "eskimonika,sid" plays too slow is because it doesn't use VBL interrupts (50 Hz) and SIDcog serial player just assumes 100 Hz is right for timer interrupt driven tunes. (Eskimonika is really 200 Hz)
I can easily compile a Linux version of the player, because it's written for the QT framework.
/Johannes
Obiously tunes making use of ANY other hardware component in the C64 will play incorrectly. (if at all)
The coolest feature found in the player is the ability to "run 6502 code backwards", just try the slider.
(Of course there's a trick to it)
Each new FTDI device creates a new com number. I had a bunch of QuickStart boards attached to this computer before using the Demo Board on it.
I'll try SIDcog on my wife's notebook. I'm pretty sure the Demo Board uses a lower com number on her computer.