Echopraxia

Did you get your opl3 board from Smash? If so you have to fix a trace on the board that was not processed properly at the factory. Just a thought. I had a lot of problems with my MBFM before I got it to work. I found that using a flux paste/gel on your smd pins, tweezers with micro tips and small diameter solder wire will get you nice clean solder joints. If you can't get good solder joints on the smds nothing is gonna work. I had somewhat similar weird noises and the smds were the problem for me. I would try to resolder your smds with flux and get the magnifier out. Don't give up.

Dude....... Dude....... :D

Any one have any silk screen graphic ideas? I'd love to see some. The only small suggestion I would make is to have the track buttons(not groups) labeled as track 1/2/3/4 track 5/6/7/8 track 9/10/11/12 track 13/14/15/16 I have mine labeled as just track 1, track 2, track 3 and track 4 and I sometimes forget how to count and select tracks accordingly :) As far as the back panel, is there a lot of interest? I'll probably just drill holes for what ever I need (Yes USB too :)) and dremel a line out for the sd card. If anything I don't think we would need TK's aout port correct? But I would think that some might want aout holes, maybe ethernet (not me). I guess if the price is right and we can decide on something without going to fancy. I still wish we could have the V4 cases shipped directly from factory to engraver company and have them do the panels that come with the cases themselves instead of paying for unused metal and shipping (i'm a cheap ass). Is there a reason we are not doing this? No biggie, just thought maybe a few of us are thinking this. Don't mean to come off as an ass :pirate:

Ditto:)

I can verify JulianF's work. He is very picky :) and makes good quality panels and lcd windows. However, for US buyers, cost for the panel was more because of the exchange rate from USD to Euro/GBP. I think for a one off it was $185 USD including shipping?? Correct me if I am wrong Julian. I think if we all had the same currency we would go with your service. Just my opinion. Still really appreciate those windows! Regards

I have not had a chance to update to beta 28 yet. I was using a midi keyboard controller going to the midi in of the seqv4 and had a question. Right now, to pick which midi out port and channel for the seq to respond to the keyboard, you use the midi router correct? Is there a way that we can have another option that would be on/off selectable that can change the midi router to what ever track 1-16 is selected? I was using one keyboard and was using the live record feature and thought it would be very productive to be able to just select the track you want and have the keyboard automatically get routed to that midi out port and channel so you can quickly record to several tracks one after another without having to go into the midi router each time to hear the corresponding track while in live record mode. Is this workable? Also can more than one keyboard controller get connected by way of another midi in on the seqv4? Its limited to 2 ins right now yes? I guess you could always get a midi merge box and merge several keyboards upto 16 for one midi in :santa: I would probably use 2 maybe 3 keyboards at most to do appregiators on one,keys on another and samples on another. 16 would be crazy though and I bet someone will try it. Can the seqv4 and midi router handle this ammount of input on top of a master midi clock at the other midi input? regards

Lets get a wiki order list going. Sorry not volunteering :) What if we got 50+? I think we have a bunch of case orders so if we can get everybody on board it would be even more worth it.

Last I checked, all of the functions at least for v3 were available using a midi keyboard's keys i.e the c2 key would be "select track 2". This was workable on v3 but not sure if it was ported over to v4.

Funny how a hardware issue ends up also digging up a software one. No more invalid sessions here:) I did have some other weird stuff happen when copying files back to the sd card after erasing it. I had for instance all of the track groups load with track group 1 instead of the appropriate group #. For instance track group #3 was set to group #1. Easy to fix of course. Also my drum maps got scrambled and was only left with the presets I had luckily saved. Hopes this helps. If you can benefit from any sd card files let me know. Thanks again,

Thanks for the tips guys. Some weird things happened when i copied files from sd card and later put them back. I deleted everything out of the session folder on sd card and put the card back into the seq and created a new session. I then put the new session in my PC and copied the old session I wanted from the hard disk to the sd card. The display will only show the "last one" at any time no mater which session I try to load. Say I have session# 1,2 and 3 in there and i'm playing #1 and decide to switch to #2 It will say session invalid (but will load) and the session name will not update. I know you said don't woory about invalid pop ups but it also does it with brand new sessions. I had something weird happen too where a lot of tracks reverted to group #1 and midi ch's 1-4. I am very tired right now so I will try to better explain myself later.

OK here is what i got from the terminal using sdcard. [21019.078] sdcard [21019.069] SD Card Informations [21019.069] ==================== [21019.069] -------------------- [21019.069] CID: [21019.069] - ManufacturerID: [21019.069] - OEM AppliID: [21019.069] - ProdName: SD [21019.069] - ProdRev: 16 [21019.069] - ProdSN: 0xc5600722 [21019.069] - Reserved1: 116 [21019.070] - ManufactDate: 150 [21019.070] - msd_CRC: 0x7b [21019.070] - Reserved2: 1 [21019.070] -------------------- [21019.070] -------------------- [21019.070] - CSDStruct: 0 [21019.070] - SysSpecVersion: 0 [21019.071] - Reserved1: 0 [21019.071] - TAAC: 47 [21019.071] - NSAC: 0 [21019.071] - MaxBusClkFrec: 50 [21019.071] - CardComdClasses: 1525 [21019.071] - RdBlockLen: 10 [21019.071] - PartBlockRead: 1 [21019.071] - WrBlockMisalign: 0 [21019.072] - RdBlockMisalign: 0 [21019.072] - DSRImpl: 0 [21019.072] - Reserved2: 0 [21019.072] - DeviceSize: 3869 [21019.072] - MaxRdCurrentVDDMin: 5 [21019.072] - MaxRdCurrentVDDMax: 5 [21019.072] - MaxWrCurrentVDDMin: 5 [21019.073] - MaxWrCurrentVDDMax: 5 [21019.073] - DeviceSizeMul: 7 [21019.073] - EraseGrSize: 31 [21019.073] - EraseGrMul: 29 [21019.073] - WrProtectGrSize: 31 [21019.073] - WrProtectGrEnable: 1 [21019.073] - ManDeflECC: 0 [21019.074] - WrSpeedFact: 5 [21019.074] - MaxWrBlockLen: 10 [21019.074] - WriteBlockPaPartial: 0 [21019.074] - Reserved3: 0 [21019.074] - ContentProtectAppli: 0 [21019.074] - FileFormatGrouop: 0 [21019.074] - CopyFlag: 0 [21019.075] - PermWrProtect: 0 [21019.075] - TempWrProtect: 0 [21019.075] - FileFormat: 0 [21019.075] - ECC: 0 [21019.075] - msd_CRC: 0x22 [21019.075] - Reserved4: 1 [21019.075] -------------------- [21019.075] [21019.078] Reading Root Directory [21019.078] ====================== [21019.078] Retrieving SD Card informations - please wait! [21019.078] SD Card: '': 2003 of 2024 MB free [21019.078] [......a] 09/24/10 00:53:46 AM 384546 MBSEQ_B3.V4 [21019.078] [......a] 09/24/10 00:53:46 AM 384546 MBSEQ_B4.V4 [21019.078] [......a] 09/24/10 00:53:46 AM 384546 MBSEQ_B5.V4 [21019.078] [......a] 09/24/10 00:53:46 AM 384546 MBSEQ_B6.V4 [21019.078] [......a] 09/24/10 00:53:46 AM 384546 MBSEQ_B7.V4 [21019.078] [......a] 09/24/10 00:53:46 AM 384546 MBSEQ_B8.V4 [21019.078] [......a] 09/24/10 00:53:46 AM 995 MBSEQ_C.V4 [21019.078] [......a] 09/24/10 00:53:46 AM 4742 MBSEQ_G.V4 [21019.078] [......a] 05/26/10 10:05:20 AM 12052 MBSEQ_HW.V4 [21019.078] [......a] 09/24/10 00:53:46 AM 35618 MBSEQ_M.V4 [21019.078] [......a] 09/24/10 00:53:46 AM 66850 MBSEQ_S.V4 [21019.082] [.....d.] 09/24/10 00:59:48 AM <DIR> 0 PRESETS [21019.082] [.....d.] 09/24/10 00:59:48 AM <DIR> 0 SESSIONS [21019.082] [......a] 09/24/10 00:53:46 AM 384546 MBSEQ_B1.V4 [21019.084] [......a] 09/24/10 00:53:46 AM 384546 MBSEQ_B2.V4 [21019.084] [21019.084] Checking SD Card at application layer [21019.084] ===================================== [21019.084] File MBSEQ_B1.V4: doesn't exist [21019.084] File MBSEQ_B2.V4: doesn't exist [21019.084] File MBSEQ_B3.V4: doesn't exist [21019.084] File MBSEQ_B4.V4: doesn't exist [21019.084] File MBSEQ_M.V4: doesn't exist [21019.084] File MBSEQ_S.V4: doesn't exist [21019.084] File MBSEQ_G.V4: doesn't exist [21019.084] File MBSEQ_C.V4: valid [21019.084] File MBSEQ_HW.V4: valid [21019.084] done. [21110.531] [SDCARD_ERROR:-150] see seq_file.h for description [21110.531] [SDCARD_ERROR:-134] see seq_file.h for description [21110.531] [SDCARD_ERROR:-134] see seq_file.h for description [21110.531] [SDCARD_ERROR:-134] see seq_file.h for description [21110.531] [SDCARD_ERROR:-134] see seq_file.h for description [21110.531] [SDCARD_ERROR:-165] see seq_file.h for description [21166.796] [SEQ_UI_Button_Handler] Button SR:21, Pin:2 not mapped, it has been pressed. [21167.062] [SEQ_UI_Button_Handler] Button SR:21, Pin:2 not mapped, it has been depressed. [21167.218] [SEQ_UI_Button_Handler] Button SR:21, Pin:2 not mapped, it has been pressed. [21167.265] [SEQ_UI_Button_Handler] Button SR:21, Pin:2 not mapped, it has been depressed. [21167.295] [SEQ_UI_Button_Handler] Button SR:21, Pin:2 not mapped, it has been pressed. [21167.578] [SEQ_UI_Button_Handler] Button SR:21, Pin:2 not mapped, it has been depressed. [21172.687] [SDCARD_ERROR:-162] see seq_file.h for description [21176.577] [SDCARD_ERROR:-162] see seq_file.h for description I was messing with the panel while I was trying to press buttons and the SR21 pin2 errors came up. After taking the pcb off of the panel I found a little piece wire on a shift register. So I booted back up and the weird constant sr messages were gone! Now when I try to load sessions it gives me a response. However the response is "session invalid". Before all of this I backed up the entire sd card and formatted it then loaded all the files back onto the sd card. Did I miss some hidden files maybe? such as from code above "MBSEQ_B1.V4: doesn't exist" I dragged the sd card icon in "my computer" to a folder on my PC to copy the contents.formatted. Then I went into the pc sd card folder and did "select all" and dragged them to the sd card itself. I will look into the "[sDCARD_ERROR:-162] see seq_file.h for description" when I get a chance tomorrow.

it looks lik I will have to resolve this sr problem first as the mios terminal keeps spitting out sr problems and the sd card line zips past way too fast to see what it means. I'll report back when I find out whats going on.

The terminal shows that something is wrong with the sequencer. I attached a picture of what its doing. It is pressing and depressing button SR:6 pin:1 very rapidly as soon as MIOS is loaded. Is this encoder #5 or F1 button? Maybe this explains why sessions quickly switch back to the "last one"? I guess I should move this conversation to trouble shooting now. I did format the sd card and put the files back on it but still received the same errors. I also ran error checking (vista) and it found some error and said it fixed it but that didn't help my situation. FAT32 is the way to go yes?

Yes I tried saving/loading using beta 27. When I get a chance I will open it up and connect it back to usb and drill a hole out of my case to access it :) I will also try to back up my seq SD card files to pc then format the card again and load the sessions back onto the seq. If that does not work I may just have to get another sd card. It could very well be a physical issue as I had a short somewhere which only occurred when I pressed down of the panel firmly and my screen flipped out. Most likely the problem But for sure I will do a proper usb mios test for you. regards, echo

I am not getting any MIOS terminal feedback when trying to load or save from the SD card. I have the seq connected midi style (not USB). Could this be why? I have not made a hole "yet" in my case for the usb port. I have also more bad news about my situation. I can do "save as" and make a new session but I cannot save into the one I am working on. it says "SD CARD ERROR !!!" and underneath that it says "E 11 (FATfs: D 0)". I am having problems loading also. When booting the sequencer it sometimes would not load the last session used and I would have to press "exit" then load and pick the session. NOW its acting like its stuck on the boot up sessino. NOW when I turn the sequencer on I am given the last session used but I cannot load any other session. In the lcd window, at the load save menu, I see it switch to the newly selected session but then quickly revert back to the start up session. So loading is not available for me as well as saving! I at least can "save as" but that won't do me any good if I can't load. Please advise, echo PS Thank you!

I scared myself this morning. I thought I blew up my FM. It turned out the voltage regulator pins on the underside were too close to the case and caused the regulator to get real hot and power down the synth when I gave it a thud on the table because the audio dropped out again. I found out it was hot by caveman exploration. :o I'm no expert but I trimmed the leads, let it cool down and now no glitching and no audio drops. Yay!

Always hard at work aren't ya? We certainly wouldn't want that trade off! :) Thanks again!

Yes button woks fine. I don't get the visual feedback of "all 4 patterns stored" but I can save sessions still luckily. However I may need to send you a system dump to see whats going on as one entire track group became corrupted on one particular session (Sorry how do you do this again?). It is on 1 track group on a couple different sessions that I get errors on. I cannot access any patterns on track group #1 with a couple sessions and I get SD card error. I lost tracks 2,3 and 4 but retained track #1 pattern for some reason and I cannot select any different patterns on track group #1 without getting sd card error. I think the problem duplicated because I may have copied a session after the problem came up. yes I and very much appreciate the feature! It actually still works but I don't get the visual feedback "cleared" anymore.

After playing with my new glitch feature I think I may not fix it :thumbsup: For the record it is probably a pin barely touching the case because the unit does stop producing audio sometimes and I have to reboot.

Having some issues with the save function. Maybe I should update to the lateest beta. i think I am still at 22. When I press the exit button, to go to the session load and save menu, I press the save button and I see that the leds that flash to select a session stop flashing and stay lit for a second and then nothing else happens. I get no response and I thought it used to tell me that it saved. And it was not saving when doing this. I can save by overwriting the session but I have to rename it correctly. I will update and let you know if that fixes the issue. Also does the clear button do nothing now?

I booted it up everything was working , audio was good yada yada.. BUT when I scroll to the far right (I.E USER) of menus I get weird glitch noises. When I press any of the 8 general purpose buttons and use the menu encoder to scroll to the very right this happens and as long as I stay on the far right icon the noise is constant. :turned: Not sure if this is a grounding thing. please advise.

I put the plastic jack on there and no sparks! Running well. next question. I drilled a hole in the bottom case and strapped a screw and nut to it with another nut on the underside of the bottom case and tightened a wire down between the top side nut and case. I then ran the wire to J2 Vs of the core and checked for voltages. I did get the 4.9v when I checked random Vd spots using the lug nut as the ground point. Did I do this correctly? I should point out that when the top panel is put on it is screwed down tight to the base panel. It was an older roland mixer that I gutted. So would I really need to still run a ground wire to the front panel?

next question. I drilled a hole in the bottom case and strapped a screw and nut to it with another nut on the underside of the bottom case and tightened a wire down between the top side nut and case. I then ran the wire to J2 Vs of the core and checked for voltages. I did get the 4.9v when I checked random Vd spots with the lug nut as ground. Did I do this correctly? Do I now just need to run another wire from the same nut to the front panel and tighten that wire down with another nut on the front panel correct?

"Throw it away and use a plastic one." I don't seem to have a local store for these. What would you reccomened? I am using Radio shack panel mount type N for my plugs and it fits perfect. Or should I just cut the connector off of the power supply and wire it to some headers? I'd rather not have a blocky power supply always attached to the unit ya know.

Thank you for the detailed respone nILS, Before I begin doing eveything wrong :) Could you clarify these steps for me? 5) Isolate the power connector: Do I just put something around it so the metal jack doesn't touch the metal case? Any recommendations for a fix? Plastic washer maybe or alternative connector? I am using a two prong 9V AC 400ma supply. 6) Is anything else connected to the case? +5V, +9V, anything on the CS, any data line? If so, find out where and eliminate the short.: I have just DIN and DOUT cables ran to the CS. I have a +12v and -12v power supply ran to the opl3 board. The MBFM works great when the two panels and not connected. Do you think I still may have a short somewhere? 7) properly connect MIDIbox ground to the case: Do I just run any of the Vs connections and screw it to a nut on the case? Do I do the same for the CS? This is a very important subject for me as I have curious young children around the house. I just read about grounding metal cases, and if by not doing so, say my little header pins came loose which are running Vd and touch the case I could get a harmful shock correct?. I'm now even more worried about doing this properly. I also should repeat this for my MBSEQ which I just put in a metal case. Thanks again,