smaudio
-
Posts
36 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Gallery
Posts posted by smaudio
-
-
Hi blingy, have you managed to resolve your Din sync lagging issue? I seem to be having the same problem. I have level shifted the J10 clock output from my STM32 and I'm getting 4.99V on the start/stop signal (which works fine), but only around V0.20 on the clock signal. My MC202 does respond to changes in the tempo but it always lags behind a bit. I wonder if there is any way I could compensate for this lagging through the software.
-
Wow, Seems like we got a result!!
Here are the results:
app_skeleton_unmodified.hex: No drivers come up after upload and reboot.app_skeleton_without_usb_host.hex: Works! Query works too :)
app_skeleton_enforced_usb_device.hex: Works! Query works too
app_skeleton_r2023.hex: Works! Query works too
midibox_seq_v4_087_pre4: Works like a Charm!
Thanks so much for all the work and for an awesome OS for the MBSeq, I played around v 4.084 yesterday for the first time and it's an awesome system. Have a beer on me, it's the least I can do!
-
Hi TK,
You're right, it seems that I'm using an A-type USB cable (it's got the letter A on it).. hm that'd be very interesting if that's the culprit. I've used another 2 cables but I don't know if they're type B as they haven't got a letter on them. Thanks for building the apps, if it's not easy to fake it in software, I can get a B cable later in the week and test it with that.
Many Thanks :)
-
Thank you, here are the results:
app_skeleton_r2023.hex: works, query works and core info come up in the window (like in bootloader mode)
app_skeleton_unmodified.hex: loads without a warning, but after loading no USB driver comes up, and thus no communication can be achieved
app_skeleton_without_usb_host.hex: driver comes up and query works!So do we deduce that there is something in the new USB host that messes up the communication in this core?
I have attached the result after loading app_skeleton_r2023.hex and 4 screenshots of the messages exchanged while loading app_skeleton_unmodified.hex, in case they are useful.
Best Regards
-
Here are some images from my core and MIOS studio to go with the points above too ;)
-
3) Yes, the query has always worked without issues under bootloader mode, I get the core information and everything in the device info window as expected.
4) It's just a MBHP_CORE_STM32F4 PCB from SmashTV's shop that I've put together with the components from Reichelt
With the core working standalone like in your pic above, the same thing happens ('no response from MIOS8 or MIOS32 core..' in the device info box) however, I get information in the MIOS studio communication box underneath: Init DHCP, SD card not found, and when I type help in the command line, I get the welcome message and commands list, so it seems like the core communicates in normal mode, it just doesn't send the device info somehow...
-
Hi Thorsten,
1) the 'normal' driver didn't seem to appear in the list of USB sources here, only the bootloader driver when boot holding, so seems like the latest driver doesn't get transmitted at all from the core when in normal mode but....
2) some success!! the midibox_seq_v4_083 driver does display the USB driver ('MIDIbox SEQ 4') on both Win and Mac, and also the other 3 MIDI drivers ('MIDIIN2 (MIDIbox SEQ 4)','MIDIIN3 (MIDIbox SEQ 4)', 'MIDIIN4 (MIDIbox SEQ 4)' )! However, I'm still getting 'No response from MIOS8 or MIOS32 core' and it won't get the core details listed underneath. The core does send a f0 00 007e 32 00 0f 4d 4f 53 33 32 f7 message though every time I query.
So it seems like we need to configure the options in the new driver?
Many Thanks
-
Thanks for that.. I successfully flashed the core with the midibox_ng_v1_032_pre4 STM324F/project.hex file through ST-Link 3.4.0 Win7, but I'm getting the same behaviour again: the Midibox NG app works fine on my MBSeq4 (READY.) but the drivers don't come up on either Win7 or Mavericks. Only the MIOS Bootloader driver comes up when I boot hold.
I tried to find the saved USB MIDI driver in my PC device manager, but I didn't seem to be able to find something that fits - I looked in the same place where the boot hold 'MIOS bootloader' driver comes up and anywhere else I could think of. On the mac I deleted the MIOS Bootloader (the only thing that comes up) to no avail.
I have used 2 different micro USB cables interchangingly, but I'm not sure they'd be just power cables as the boot hold MIOS bootloader seems to come up ok. I have tried everything both powering from ST-LINK or USB-MIDI (by stuffing the jumper on the module).
The only thing difference I've noticed from your instructions image is that the ST-LINK utility Memory display size used to be 0x020CE8 and now it is 0x4DAD8 (not 0x12700). Would this give any clues to what is wrong?
Many Thanks again
-
Hi Thorsten,
Many thanks for looking into this (and for all the awesome projects)!
I do appear to have a STM32F407 core on the STM32F4 Discovery board (STM32F407VGT6 MCU 168 MHz/210 DMIPS), so no luck there..
I should also say that when I flashed the core for the very first time on my PC, I did get the 'good' USB host showing up as 'MIOS' and everything seemed to work as planned (and I've been able to achieve this once again after flashing), but the host just stopped working somehow after I power-cycled again :(
Other than that I don't know what else it could be.. it's very strange. Perhaps it's my STM32F4 then and I need a new one?
-
Hi everyone,
I have a strange problem with my STM32F4 Discovery not being able to communicate with MIOS studio.
I flash the STM32F4 with the mios32 bootloader no issues via ST link, but then if I reboot the core and connect through the left Micro-USB, the USB MIDI driver doesn't come up on either windows or macOS (so I can't connect it to MIOS studio). If I boot the core in boot hold mode, the USB-MIDI driver comes up on both Mavericks or Win7 (MIOS bootloader) the core gets recognised and can upload an application (ID=0), but when I then upload midibox_seq_v4_086 and reboot, even though it works on the displays of my MbSeq4, no USB Midi drivers again in either Win7 or Mavericks.
To test further, through boot hold mode I uploaded midio128_v3_019, reboot, and the drivers do come up and I can use the terminal, but I get 'No response from MIOS8 or MIOS32 core' (I've checked with all Device ID values, none works). If I now try to upload midibox_seq_v4_086 I get the 'Warning: no reponse from the core' message half way through and the core doesn't seem to send an upload request after booting.
I have done this when the STM32f4 Discovery board is not connected with the MBHP_CORE_STM32F4 module and it exhibits the same behaviour.
Is this midibox_seq_v4_086 messing up the USB midi drivers somehow?
Or perhaps some residual code somewhere if it connects under boot hold?
Any help is much appreciated!
-
I guess I can get them as spare parts. I'll ask for the price in a few days and let you know.
If you can't get the profiles only, put me down for an aluminium case (it'd be wasteful but by far the most effective way of getting those profiles!) Many Thanks
-
I guess I can get them as spare parts. I'll ask for the price in a few days and let you know.
Many Thanks! Let me know
-
I mean without side, bottom, front or back panels, just the aluminium profiles (guides). Or if that's not possible, with whatever panels would be the minimum I could go for (eg. just side&bottom)?
-
Hi Kristal, would there be any chance that I just ordered a set of the profiles through you (no panels)? I have customised my Midibox seq and as a result I have to print the panels elsewhere.
Let me knowThanks
-
if you're referring to http://www.sequencer.de/synthesizer article the pictures do tell that he used STM32 core, not LPC, as can also be seen from answering the questions throughout the article.
Some time ago I tried to make the measurements to accommodate LPC core in the box but never finished that (I still have the A3 paper with http://www.heidenrei...n_variant_b.pdf printed in my laptop bag). Making the front slightly taller will probably cause the frontpanel height to change since it's angled, maybe by a fraction but maybe enough already for the panel not to fit (and Heidenreich doesn't use the panel size a manufacturing parameter, alas). So you would need to lift both H as well as H1.
The problem (for me, at least) was that http://www.ucapps.de...se_measures.pdf shows all the dimensions (e.g. 35,78mm from bottom to the front-side top screw but this doesn't seem to be the H1 dimension (that seems to be till the front hinge top if I can say from the enclosure sketch). If I got it right you can't re-create the order based on the sheet - you're still missing the H1, the other (H, B, T) seem to be there assuming the 'B' doesn't include the side panel thickness. But maybe TK can reveal the number and we could simply add 5mm to both H1 and H and have the job done...
My two cents, if anyone can prove me wrong I'd be happy to hear that my concerns are not really concerns and would be first one to get the case (two, actually) :rolleyes:
P.S. Am I the only one missing 'preview before posting' in the upgraded forum engine and the only one missing lack of GUI when quoting? :sad:
Hope this helps,
freddy
I've calculated based on the http://www.ucapps.de...se_measures.pdf diagram, that H1 would be 44.10 mm. So would that mean that all we need is: H1= 49.1mm, H=86.82mm, T=125.20mm and B=434.50mm (17.5'' as in TK's design) or 482.6mm (19'')?
Is there no need to increase the T at all?
-
I'm in for a 19'' LPC enclosure too.
I've counted 6 people interested in the 19'' and 7 in the 17''.
Aesthetics aside, wouldn't the 19'' suit both 17'' and 19'' users (isn't the only difference just 5.1 of cm on the sides ('B') )?In which case I would be willing to put an order through for the 19'' LPC Heindereich case if people are interested and someone helps me with the design. Would the difference between a Core and an LPC be just an increase of the width ('T') of the case?
-
I'd be up for one of these cases too, big or small depending on what we decide to do. Even though I think making it slightly bigger to accommodate for the new core would make sense for future buyers too.
-
Hey guys,
no, I'm in London lol
I've had a look at pollin's website but I can't find anything in English (!) do these guys speak english? How did you contact them about posting to australia, I presume that means that they should post to UK too?
-
I don't expect you'd still have any of these left, tilted (or anyone else) by any chance?
sm
-
You'll need to send them an email asking them for a quote on the shuttle knobs: #866003 DK38-144 A.6 and how many you'd like to order. Once you're ready to order you'll have to ring them up to pay by credit or debit card (you can't do it on line) but they speak english no problem and they're really friendly and helpful so there shouldn't be any probs at all. :)
Unless you can make it a business transaction, you'll probably need to pay german VAT (19%) and the shipping costs, which aren't that big but you should just take these things into account in your calculations ;)
-
Hi guys,
I don't think I'll make another order for these shuttles as I've now got enough of them (!) but I would encourage someone else to do it as the overall process went really smoothly for me..
However, I'm thinking of asking for a quote for the albs knobs DK16-185.
I'll open up another post for those ones if the quote sounds ok :)
sm
-
Hi again,
just got the parcel! ;D
I'll weight the packages and send everyone an invoice or pm with their respective pricing.
Shouldn't take long!
-
Hi everyone,
just a quick update on the order - I'm still to receive the parcel so I've just sent a follow-up email to albs.
I hope that it arrives asap as I'm growing a bit impatient...
I'll let you know and start the invoicing process as soon as I receive them.
necro- yeah, I've closed this order quite quickly as I'd like to get things going asap, plus we got quite a lot of interest quick enough so why wait ;)
-
Hi everyone,
Order placed and confirmed :)
Order costs after shipping and 19% tax (which unfortunately had previously escaped me) came up to 2.5 EUR per button.
After Paypal fees, it works up to 2.875 EUR (£2.34) per knob per order and depending on the country of delivery, you can add the additional shipping charges that apply to you (see my previous post)
I’ll PM everyone with their individual payment details and after payment I will send out invoices and send out the packages.
Midibox SEQ V4L Din Sync
in MIDIbox SEQ
Posted
Ok, I think I've figured this out - After checking with another Din sync/MIDI converter it looks like it's not the clock being sent from the Midibox seq v4 that's wrong (and thus it's not a matter of voltage), but that the MC202 adds some extra time in the last step of every sequence. This makes it drift. I've worked out that the 202 sequences need to be trimmed a bit at the end to get the two to synch properly.
I hope this helps anyone that comes accross the same issue