Rio
-
Posts
712 -
Joined
-
Last visited
-
Days Won
9
Content Type
Profiles
Forums
Blogs
Gallery
Posts posted by Rio
-
-
... but SID isn‘t analog, only the DAC Part inside, right?
-
On 4/22/2021 at 2:38 AM, Noise-Generator said:
Right, it's just my personal opinion, everybody can do what he wants to and DSP SIDs do have their advantages but it turns the MBox SID just into an VA and if you would redesign the Box to a DSP Synth with much more Power you could just emulate the SIDs inside.
I think the term VA is not quite right, but yes it is no longer a real SID and an emulation is running. Nobody hears the difference in productions anymore. I think this is more about the aspect of using these 'retro' chips (including me) than just the pure sound.
.. and of course, adequate respect should be paid to all developers who deal with the chips and their emulations.
-
I have the armsids for two main reasons: I see them as quite passable replacements in case all my SIDs break down, and with regard to the 6581, the armsid might be a better choice as I can never find suitable filter pairs with the originals can. The 8580s, on the other hand, are quite stable.
-
This is a far better option than wearing down the c64 socket or the SID that is in my beloved C64.
-
But they may replenish it (but yes possibly).
-
Quote
Awesome; the board has only space for 2; so I guess I can either use the 2 as stereo pair, or as 2 different mono devices (which should give me a total of 6 oscillators and 6 notes, if I understand this correctly; since each SID has 3 oscillators that can be played together or individually).
I'm not sure now whether your plan matches what has already been implemented with the MBSID. There are 4 sound engines, take a look here:
- Lead Engine
- Bassline Engine
- Drum Engine
- Multi Engine
-
1
-
Yes very good! I just wanted to make sure that the wrong thing is not accidentally uploaded, although the "MIOS Studio" already warns or maybe blocks this. Your bootloader is fine on your PIC just MIOS and the app needs to be uploaded in order. You can't screw up a lot there either. Otherwise just upload the two things again. Have fun and don't hesitate to ask :D
-
Oh my fault ... I meant MIOS. You only upload the newer MIOS version with the bootloader (which is already burned on the microchip). You don’t upload the bootloader itself!! (that's for a burner and not for midi transmission).
Sorry, my confusion in the binary term - I just recognized it now. I hope you read it before trying, but however, MIOS Studio should warn you about this (range detection).
from the readme.txt of mios1.9h take case A):
A) you've already installed MIOS8 V1.9g, and want to update to MIOS8 V1.9h Thats the common case, you have to upload one of these files via MIDI as described on the http://www.ucapps.de/mios_bootstrap.html page depending on the PIC derivative you are using. ... PIC18F4685: -> pic18f4685\midi\mios8_v1_9h_pic18f4685.hexupload the mios1.9h hex and then you can upload the MBSIDv2 app again.
-
1
-
-
First of all, ask modular addict whether there are any new ones
-
hi,
3) use PC messages, not CCs.
4) right - you have 1 stereo pair. (you can stuff up to 8 sids by 4 cores), but i am not sure how many cores can be loaded in sammichSID because I am not familar with sammich board.
5) pls use the "mios studio" software. and yes first upload the newer
bootloaderMIOS and then the application. Everything can be uploaded via midi, but take care about the core IDs and the correctbootloaderMIOS file.MBSID V2.044 changelog: Please update to MIOS V1.9h before uploading the application, otherwise the improvements won't be effective.
have fun with the synth!
-
1
-
-
I remember, 500mA was minimum for 1 core 1 Sid.
-
just check all contacts. maybe the PIC is not firmly in place, midi port connections may become loose over time. it could also be cold solder joints. take a close look at the hardware.
-
short and thick... and if that doesn't help, we'll try to update the firmware of the probe.
ps: don‘t forget to remove the jumper of JP3
-
but if you read further below, you can see that the problem was with the cable again!
-
ok, i have now tested a different usb cable (the cable is short and thicker - it looks more stable). Everything works now (also with win7 and win10). The jumper must be removed, otherwise the linker will not work. no mbed driver needed or anything else...it worked for me without installing anything or without updating the firmware now. but i'm not sure if i ever installed the mbed stuff before i was switching to win10 - that was 2 years ago, but I don’t think so, because I restore a untouched/clean OS once a year.
so either you actually don't have a really good short cable at hand, or you have an old firmware on the probe.
check out:
1. better cable
2. update linker/probe firmware
have a look here:
so, therefore you can hold 'reset' button on board or solder a bridge on JP4. I just did the solder solution. that's working. so you get into the ISP mode and you can copy the newer not mbed-based firmware for the linker board (LPC11U35 debug probe) again. I didn't do that now, because my board already works, but it should work as described here.
QuoteThat year we introduced a new version of the firmware that was not based on mbed...
-
ok i tried the same steps that you mentioned. And I come to the same conclusion that it does not work under win10 as you described (with me, however, no drivers are shown in the device manager). I don't quite get it - I'm (actually) sure I got it installed in the past - but that was a win7. But when I try to install it in Win7 it doesn't work either. When installing the mbed driver, the same error message appears. it is really crap right now ... maybe gerald.wert has an idea, he also successfully connected it, just didn't write how.
-
there are 3 more links at the bottom by ZhangJennie, about that post about 1769 rev.D problems, referred to:
- MBED serial driver
- probe firmware
- Can't find debug Probe ticket..
I know the picture you posted/shown is related to a lpc8xx but I think it uses the same probe (CMSIS-DAP).
BTW: You have to think of it this way: there are two boards - on the one hand it is the debug / linker probe and on the other hand the LPC1769 board - both are connected. If the jumper is set, the probe has priority.
-
The board isn't different...LPC11U35 is the CMSIS-DAP Debug Probe board name, or not? and it is referred to by the LPC1769 board rev.D on that side.
-
i found this too:
did you follow these instructions?:
I know tired but it should work at some point.
-
and did you install LPC11U35 installer before and restart PC?
-
Ok, i have found my rev.D1 board again and plugged it in. It's using CMSIS DAP linker too.
Yes, it is also not found (with closed jumper). So something is still fishy. Have you ever tried to load the host drivers from nxp:
at the bottom:
Host Device Drivers ( 1 )
- Firmware and drivers for LPC11U35 debug probes
I think that's for it ..
-
did you try this:
If his guidance on the rev D doesn't help, you could PM him. at least he managed it.
Edit: Oh, I just checked again at myself: I had actually successfully flashed a Rev D1 via the IDE 8.2.2 in the past. I can't remember any unusual things now.
-
rev D should work:
I'm not sure what else to do ... but maybe try another PC. After that you can find out what's going on with the current one.
-
In some posts, people get in trouble with CMSIS-DAP. but take a look here:
On the other hand, I read that it probably also worked with 8.2.2 ... I can't test it myself (i have only rev.A B C). Do you have the chance to grab an older revision? Don't you want to go to the newer CPU sooner if that is so much trouble? But you could still do some research ... it's up to something.
SID "Clones" List/Sources/Experiences
in MIDIbox SID
Posted · Edited by Rio
Yes, without a doubt, I understand what you are referring to ..
.. and otherwise we would hardly have dreamed of making a box with sound chips from old home computers.