Jump to content

Rio

Members
  • Posts

    724
  • Joined

  • Last visited

  • Days Won

    9

Rio last won the day on April 20 2021

Rio had the most liked content!

About Rio

  • Birthday 04/26/1978

Profile Information

  • Gender
    Not Telling
  • Location
    Germany
  • Interests
    Music, 8Bit, Synths

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Rio's Achievements

MIDIbox Guru

MIDIbox Guru (4/4)

9

Reputation

  1. Is it possible that j14 can be configured programmatically as an output pin and if so, how can the pin be set to high or low?
  2. Short feedback: Regardless of the clock rate (must be below 400khz), my solution now works with clock stretching.
  3. Thx tk, for finding out. So only the last note is missing in the changelog ;)
  4. Where can I find the MIOS 8 sources as version 1.9h? I can only find version 1.9g on Git: https://github.com/midibox/mios8/tree/master/mios Thanks, rio
  5. as i know, it is only based on ASM (core8), but it has long long been prepared on a rudimentary C basis. but not implemented. This is unlikely to change officially.
  6. And if you go back to 4.096? Does it work then? Plug the SD card out and then in. Maybe the contacts for your setup on SD are just a bit morbid over the time, but the app would normally have informed you about this. And If 4.096 works, check out the changelog for the last version.
  7. I also use an LPC17. Maybe I can help you. My SEQv4 has been running fine for years (decades) with 12 midi outputs. I need more details on what you have configured in your app? Are all the other messages to your midi ports working (NOTE ON/OFF etc. and is it CC related only)? Which midi ports have you connected and how?
  8. Simple question for the core v3 /PIC18F board using MIOS8: How fast is the SC line for both modes (MIOS_IIC_CtrlSet [0 default / 1 clock stretching]) ? and is it <400KHz? Because one of my external boards as an IIC slave only accepts a clock up to 400KHz and it does not react as it should ATM. It seems that I get an ACK back to the PIC18F master in clock stretching mode, but the external device itself remains without any functionality. If I try it without clock stretching, the watchdog restarts the PIC18F master app because it does not receive an ACK in the loop and the loop probably runs too long for that. BTW: the external board can be well controlled by an Arduino using the standard frequency of 100Khz defined in the wire/twi classes of the Arduino core library:https://github.com/arduino/ArduinoCore-avr/blob/master/libraries/Wire/src/utility/twi.h#L30 But of course I don't want to control it with an Arduino, but with my PIC18F with MIOS8!
  9. yes it is. it is described here: http://www.ucapps.de/mbhp_iic_midi.html
  10. Hi, I want to use clock stretching, so I had read about: http://www.ucapps.de/cmios8_fun.html#MIOS_IIC_CtrlSet MIOS_IIC_CtrlSet notes to add a 1k pull-up resistor to the SCL line (Pin #22 of the PIC). Required for use? If I take a look at: http://www.ucapps.de/mbhp/mbhp_core_v3.pdf there is already a 1k resistor to +5V on J4 (SC line) Pin 6. Is it the same resistor that was named here? Greetings, rio
  11. I am quoting myself, but just to confirm that it is possible to compile & run on a Mac M2. Thank you for the concise instructions two answers ago. However, there are a few visual glitches and a few crashes (but unrelated for working playback), probably due to using outdated classes. Crashes occur with sidplay by midi device list detection due to previously connected midi device, by window resizing and sometimes midipatch bay crashes when exiting.
  12. @dwestbury Vice/vsid runs stable and well on Windows (also as a x64 build). Do you currently have a Sidplay build for the mac version with ASID support at hand, which will also run on the latest macOS versions (maybe Arm64 Silikon support)? I can try to compile it according to your description...
  13. Ok. 3387 ist the one, which is used in 1st Waldorf 4-pole Revision.
  14. Are you looking for CEM 3387 or CEM 3378? Both differ in certain functionality. Yes, it is rare, but not impossible to get. Wait and watch on ebay or second hand sellers, etc. the price should be double (or even higher) what it was 20 years ago. e.g. the cem3378 were rare even then. I got mine (3378) around ~2006 for 20 euros each. But those were already the last in stock. Greetings, rio
  15. Do you have experience in programming? The reason I ask is because it requires that. And your approach of changing the args of a core function is definitely not the right way. Btw: I think this is pretty custom for your needs, since the mute works in a different way in the midi implementation (regarding tracks). Otherwise, if you absolutely need it and above all if you are confident that you can do it, then you can hack the seqv4 source and define and include your own external control as a CC and specify & transmit the channel there as a value, which is used in your own loop through the tracks and mutes or unmutes the corresponding tracks if (value == track's channel). e.g. seq_midi_in.h --> #define SEQ_MIDI_IN_EXT_CTRL_MUTE_BY_CHANNEL 16 #define SEQ_MIDI_IN_EXT_CTRL_NUM_IX_CC 17 <-- (make sure to increase the NUM_IX_CC) seq_midi_in.c --> seq_midi_in_ext_ctrl_asg[SEQ_MIDI_IN_EXT_CTRL_MUTE_BY_CHANNEL] = 122; // your cc for that control const char* ext_ctrl_str[SEQ_MIDI_IN_EXT_CTRL_NUM] = { .. "Mute by channel", // your name for that control } <-- (index 16 must be noted here) append your external control handling inside: static s32 SEQ_MIDI_IN_Receive_ExtCtrlCC(u8 cc, u8 value) if (cc == seq_midi_in_ext_ctrl_asg[SEQ_MIDI_IN_EXT_CTRL_MUTE_BY_CHANNEL]) { ... } but i think if you want to change something in the code, you have to get familiar with the structure of the entire source anyway. Greetings,rio
×
×
  • Create New...