Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
You are not logged in 
CSDb User Forums


Forums > CSDb Discussions > Project SIDFX (formerly known as SIDFIXER)
2015-12-20 14:29
Scarzix

Registered: Aug 2010
Posts: 134
Project SIDFX (formerly known as SIDFIXER)

Sorry for spamming you all, but regarding the DUAL SID hardware module SIDFX:

I mailed all PRE-ORDER contacts tuesday and I still miss a reply from 33% of you... please check your spam folder/email if there is any mail from sidfx-preorder@kick-ass.dk (16th december)

Thanks in advance.

There will be a registration site up shortly... so if you didnt pre-order/registrate already, you can also just mail me directly on the sidfx-preorder@kick-ass.dk mail address.

Cheers and merry X-mas to everyone!
 
... 175 posts hidden. Click here to view all posts....
 
2016-11-03 19:40
Scarzix

Registered: Aug 2010
Posts: 134
Not going to work. The power transfer from the SIDFX is controlled to match the SID model installed. I cannot recommend trying as this might break your unit. (havent tested myself, but this is outside the specs and normal usage)
2016-11-04 00:05
Scarzix

Registered: Aug 2010
Posts: 134
okay, we added some more pictures and explanations for a lot of the ASSY's.

If anyone has installed the SIDFX in those with missing images, feel free to post them to me on contact@sidfx.dk and I will put them on the manual page too.

http://www.sidfx.dk/manual
2016-11-06 11:14
lft

Registered: Jul 2007
Posts: 303
It was mentioned in another thread that SIDFX will always route read accesses to the chip in slot 1. In my opinion, that's a rather serious design limitation. It means that sid detection routines will always detect what's in slot 1, regardless of what chip is currently selected. So any tunes that adapt themselves to the current sid model (e.g. my tune in VN65) will sound wrong, and the only way to get it right is to open up the case and switch the chips around---which is precisely what SIDFX was supposed to eliminate. Is there any chance that this can be fixed in a firmware upgrade?
2016-11-06 13:49
Lotus

Registered: Nov 2004
Posts: 6
LFT: During the design phase (this was probably back in late 2013) we concluded that it may be unwise to swap read accesses based on the switch 1 position, due to the differences between 6581 and 8580. We wanted to make sure that SID players utilizing the OSC3/ENV3 registers would not end up playing incorrectly due to manual switching during playback. Therefore switch 1 only alters the audio path, not the register map.

However, if you wish SID2 to be detected by a demo, then (using the SIDFX config tool) you can make a configuration profile with mode “MONO - SID2 ONLY”. Then all read accesses go to SID2, and you can still switch the audio output between SID1/SID2 using switch 1. Using switch 2 you have 3 available configuration profiles that you can choose between prior to loading a program.
2016-11-06 16:24
lft

Registered: Jul 2007
Posts: 303
Ah, excellent! That solves the problem.
2016-11-06 16:51
Frantic

Registered: Mar 2003
Posts: 1310
Yes, excellent.

...and speaking of that, it would be very nice if the source code for that configuration tool was available, especially since there is no programming reference available for SIDFX (as far as I know?). I would like to implement explicit support for the SIDFX in a music editor that I am currently working on.
2016-11-06 17:03
AmiDog

Registered: Mar 2003
Posts: 92
Just installed my SIDFX. Other than the first SID I took from a broken C64 being broken, it all went smoothly. Took about 3 hours to mod the case and get everything installed.

I've run the config tool a few times, and once it failed to detect the SID types. It found two SIDs but listed them as unknown. Should I be worried about that?
2016-11-06 17:20
Lotus

Registered: Nov 2004
Posts: 6
Frantic: Don't worry, the SIDFX API will be made available soon'ish (Scarzix will coordinate that), including example source code for easy implementation. But right now we are focusing our efforts toward improving the general documentation :)
2016-11-06 17:35
Lotus

Registered: Nov 2004
Posts: 6
AmiDog: SIDs detected as unknown are operated in "safe mode" at 9V (and with 8580 filter caps) so the chips will not be damaged, but they may not operate properly for several reasons. I have only seen this with a handful of bad SID chips (mostly 6581), that were either totally dead or sounded very wrong in a plain C64. Have you tested them prior to using them with SIDFX?
2016-11-06 19:15
mhindsbo

Registered: Dec 2014
Posts: 31
I have the same issue. I have a C64R with SID socket #1 : 6581and SID socket #2 : 8580. Both SID's are tested and working stand alone.

Sometimes the diagnostic tool detect none (unknown), sometimes one and sometimes the other and sometimes both.

When it does detect both then everything works fine and I can play stereo tunes or switch back and forth from one to the other.
Previous - 1 | ... | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 - Next
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
bluecursor
TomoAlien
ZeSmasher/F4CG
Karmic/HVSC/ONS
Twoflower/ΤRIΛD
Guests online: 53
Top Demos
1 Uncensored  (9.7)
2 Edge of Disgrace  (9.7)
3 Coma Light 13  (9.6)
4 The Shores of Reflec..  (9.6)
5 Lunatico  (9.6)
6 Quad Core 100%  (9.5)
7 Comaland 100%  (9.5)
8 Incoherent Nightmare  (9.5)
9 Wonderland XII  (9.5)
10 Comaland  (9.5)
Top onefile Demos
1 Pandemoniac Part 2 o..  (9.6)
2 Synthesis  (9.6)
3 Dawnfall V1.1  (9.5)
4 Daah, Those Acid Pil..  (9.5)
5 Field Sort  (9.4)
6 Treu Love [reu]  (9.4)
7 Dawnfall  (9.3)
8 Globe 2016 [reu]  (9.3)
9 KAOS 64  (9.3)
10 Hardware Accelerated..  (9.2)
Top Groups
1 Booze Design  (9.4)
2 Censor Design  (9.4)
3 Oxyron  (9.4)
4 Crest  (9.3)
5 Finnish Gold  (9.3)
Top Webmasters
1 Slaygon  (9.6)
2 Perff  (9.6)
3 Morpheus  (9.5)
4 Sabbi  (9.4)
5 CreaMD  (9.3)

Home - Disclaimer
Copyright © No Name 2001-2017
Page generated in: 0.484 sec.