Jump to content

ris8_allo_zen0

Programmer
  • Posts

    173
  • Joined

  • Last visited

Everything posted by ris8_allo_zen0

  1. Hi all, I was wondering if there was a reason to set the left-right oscillators with a different wave type (left is Pulse, right is Sawtooth) in the default bassline patch. I discovered this thing when I checked my gear after expansion (now it has 2 stereo 8580's and one mono 6581) and noticed that in the default bassline patch the left channel's VU meter in my mixer was clearly higher than the right one. I started checking thoroughly all the audio wires and SID modules with no results. It was when I connected an oscilloscope to both outputs when I noticed the (quite obvious) difference in the wave shape. I can confirm this in the source code (sid_preset_bassline.inc, ca. line 45): ;; Voice #1 ;; Flgs Wave AD SR PW_L PW_H Acc Delay Trns Fine PRng Port. ArpM A.S/D A.G/R Res2 db 0x01, 0x04, 0x00, 0xc0, 0x00, 0x09, 0x10, 0x00, 0x28, 0x80, 0x02, 0x28, 0x00, 0x1f, 0x05, 0x00 [...] ;; Voice #2 ;; Flgs Wave AD SR PW_L PW_H Acc Delay Trns Fine PRng Port. ArpM A.S/D A.G/R Res2 db 0x01, 0x02, 0x00, 0xc0, 0x00, 0x09, 0x10, 0x00, 0x28, 0x80, 0x02, 0x28, 0x00, 0x1f, 0x05, 0x00 ^^^^ HERE IT IS Bug or feature? ;) Many thanks, RAZ
  2. That would be perfect for me! OMG :o Please don't let me know what request I unintentionially thrown into the deep...
  3. About "new" chaining modes (which I'd love as a feature in my SEQ): I thought about a possible solution which can lead to many other effects: a new event mode whose events are step numbers (S1..S32), and at least one constant is a track number or a group number: when a non-empty event of this track is triggered, the track or the entire group jumps immediately to that step, the same way as using the "Manual step trigger" function. This function becomes useful only when its clock is a fraction of the target track/group. (otherwise it can be used to make custom progression models) So, a chain like 1->2->1->3 (each 8 steps long) could be made this way: set track 1 to "step index", set its clock to 2 and length to 4, then program the events like S1 S9 S1 S17 (or S1 --- S1 S17, since an empty event will just let the things going). For 1->2->1->3->1->2->1->4: S1 --- S1 S9 S1 --- S1 S17. With other sequences and clock/length ratios (even uncorrelated ones), possibilities get endless... Too nerdy? ::)
  4. If it's not too late, what about crossing the two wires the OPL3 uses to send data to the YACs? It could be just a matter of cutting two PCB tracks and soldering a pair of jumpers. Here's what the schematic says: IC1 pin 21 (DOAB) --> IC2 pin 4 (DIN) IC1 pin 22 (DOCD) --> IC4 pin 4 (DIN)
  5. Penso a tre possibilità : 1) il 16f876 ha due uscite PWM, che equivalgono a due uscite analogiche se colleghi a ciascuna un filtro passa basso (vedi lo schema dell'altro post), quindi potresti creare un sintetizzatore stereo nello stesso chip (chissà se ti basterà la potenza dell'876 per gestire scheda SD e due uscite audio...) 2) sfrutti quello che hai fatto già (output di due canali MIDI) per: 2a) controllare altri due CORE aventi il firmware che ti ho indicato nell'altro post; 2b) controllare un CORE che fa parte di un MIDIbox SID in combinazione stereo. Ci vorrà sicuramente più tempo (e non so se ne hai da spendere da qui al tuo esame) ma quello che ottieni è un sintetizzatore coi controattributi!! sentiti gli esempi nel manuale e capisci che intendo. P.S. un lettore di file Midi da SD potrebbe essere parecchio utile nell'ambito di questa community! Che ne pensi di pubblicare schemi e firmware qui?
  6. Hello, my 2cents: can a PIC emulate an I2C eeprom? If so, it could be visible to the Core as a common (huge) BankStick and no modification to MIOS would be required. On the other hand, the emulator can implement all the SD/FAT stuff, or even gather data from anything else than an SD.
  7. Ciao e benvenuto anche da parte mia :) Immagino che per "file midi" voglia dire che hai un file midi nel tuo PC e lo voglia passare al tuo microcontrollore tramite un collegamento MIDI. Se è così la piattaforma MIDIbox può effettivamente andar bene. Se per segnale analogico intendi un segnale audio, prova a dare un'occhiata a questo post che parla di un sintetizzatore audio creato su PIC. E' scritto in C ma può essere un buon inizio, specie nelle prime versioni che credo siano più semplici da capire.
  8. If you decide to place the LEDs horizontally, I'd suggest you to put them above the encoders, not below, otherwise your hands will cover them when you operate.
  9. My SIDs are finally here in Italy! :) I just have to wait the kits from SmashTV and my Doomsday Device will be complete ;D
  10. Thank you guys for all the comments!! I must admit this video has many layers of interpretation, but I didn't expect anything about the meaning of life and the goals of human race... Me and my colleagues filled 17 pages about innovation, intelligence and relation with new media. I think the main problem is that we were so accustomed by the broadcast media (and their monodirectional way to communicate) that almost all of us think there's nothing we can actively do in our world, nothing to solve, nothing to change simply because somebody else did that already, and better. Now the new media are all around. People can share their ideas with no physical limits (exactly like we're doing here), either because of Internet and multimedia software available, and challenge the biggest media corporations. The problem is that nobody still knows exactly how to deal with this, i.e. which kind of society is growing from now on. Somebody has great ideas, somebody else not. Sometimes good things grow up spontaneously, by "emergence". Some other times people just stop thinking and become slaves of their own solutions, like our caveman. I once read that while educators are seeing more and more difficult to impose the hierarchical, monodirectional way to learn things, e.g. writing, some of the younger generations are exploiting new media to share their love for Harry Potter stories, invent new "fan" stories and, by doing so, exercise themselves in writing. I mean, communities of children 12-13 years old. That's awesome, and much better than writing those boooring texts in classroom. And I wish some time later I'll read about another community which helps people to learn electronics (another booooooring thing) by sharing the fashion of MIDI and audio synthesis ;)
  11. Hi all, some days ago me and my classmates were asked to produce a video about "innovation" in some aspect. So we made this fake advertisement for our university, a humor critic about misuse of technology: (sorry, the volume is a little low...) I was the actor, the co-writer of the screenplay and, what I'm most proud of, the chooser of song and the fonts :D Comments please :)
  12. ris8_allo_zen0

    Pulsanti

    Ciao, anch'io mi sono trovato nella stessa situazione ma non è che mi sia sforzato un granché... per il MBSID ho usato cinque pulsanti di quelli del sito di Mikes più quelli forniti dagli encoder (pessimi), mentre per il MBSEQ ho sfruttato la tastiera di un Commodore 64. Ti converrebbe chiedere nella sezione internazionale, sempre che non ci sia già una discussione in merito... Ciao! Enrico
  13. That's fine! It's a good point to start. Sorry for not immediately understanding that (I also misread crown as crowd)! The IR receiver should be placed as near to the hub as possible, along with other components so that the momentum doesn't rise too much. Anyway an IR receiver has usually a very high viewing angle (110° or so), so as long as the transmitter is positioned in front of the wheel, there shouldn't be any problems.
  14. That's not a big problem for me. What I want is to make this thing compatible with good old IR remote controls, so I can use it for other purposes while not using the SEQ. Choosing a radio interface instead of an IR one is not a major issue. It can be an alternative, though. Do you mean "interleaved" data stream? That would need N infrared receivers, each with its own circuit to drive a Led. Since there's already a microcontroller, I think it's better to attach just one infrared receiver to it, then write some protocol in software. Please be aware that these are just fuzzy ideas, not final decisions. I write them here hoping they'll get useful to somebody (edit: forgot to complete the sentence :D)
  15. Simply because I imagine a loop as something circular, and maybe you do too :) Good to know! But I think this POV display should be quite bigger than a handheld display. Think about a room fan, or the device Sasha reported here. Another idea (please forgive me!....): instead of each button, a pair of IR led and receiver that can sense the approach of a finger near them. They could be put together to the leds in the POV bar. That makes a touchscreen POV display! Why should a radio means required for this application? Wireless means "without wires", not strictly radio communication :)
  16. My aim was not to make a CS out of a POV display, but simply to design an output-only interface used in addition to the standard CS. It will provide a global view of the patterns, or simply something nice to see while playing or dancing. But for you that think about an input too, I have a veeery conceptual idea: a "ray bar" in front of the POV wheel, attached to the center by a rotary encoder and having a row of 16 buttons and leds that overlap their POV counterparts. The bar can be freely moved around the circumference to select steps, and with buttons you change the steps in each orbit/track. Another idea: a fixed ray bar and a knob in the center. The knob rotates the POV disc: spin it until you see your steps under the bar (and re-represented by the Leds in the bar), then edit accordingly.
  17. Hello, since a few days I was hit by an idea: build a rotating LED bar for a persistence-of-vision display like SpokePOV, and use it as a pattern display for a SEQ. Each orbit represents a track and its steps are equally distributed into its length, according to the track length. All this can help to have a global view of the tracks, but also to get a nice light effect for the public during live playing! :D SpokePOV, among other similar projects (see also "propeller clock"), is made of a LED bar driven by some shift registers which are in turn driven by a microcontroller that has the image bitmap and knowledge about the rotational speed and phase. The bitmap is usually static or dynamically generated (e.g. by current date&time), the rotational data are read by a sensor that triggers when a revolution is made. All of this stuff must reside into the rotor / wheel / fan / anything able to spin. The difficult part is how to interface this circuitry with the rest of the world, since physical connection is not so easy and IMHO a wireless solution is more efficient and elegant. I thought about an IR interface between the SEQ core and the rotating microcontroller. The former sends the updates of the tracks (step activation, track length, cursor position) by some ad-hoc protocol, and the latter reads these data and paints the air accordingly :) An IR interface also allows me to use the POV display for other purposes by simply using an IR remote control. According to this page, realizing a simple IR transmitter only requires two pins of a PIC, whose one is a PWM output calibrated to ca. 38kHz. What I'm asking you, is what do you think about this idea and if it's possible to implement such a IR transmitter into the SEQ hardware and software. Many thanks!!
  18. Lenwe, that's the same schematic I've used for my MIDI adapter too. (it's also the most famous, available on the 'net since one decade I think). But by my side the problem was lying in the master keyboard, unable to communicate to the Core. Link between Core and the adapter was always been OK. Eventually I had to modify the Core so it could also read from the keyboard. Now I got rid of my DIY interface because of other issues. I'm very happy (even with Linux!) using a Midisport 2x2.
  19. Thank you, and thank you again to let me remember to link to the original thread where for the first time I talked about this: http://www.midibox.org/forum/index.php/topic,8500.0.html
  20. Now I know what inspired those packaging guys at Ferrero's :D
  21. Hello, just my 2cents: maybe you're having an issue similar as this one? http://www.midibox.org/forum/index.php/topic,9425.0.html
  22. What about "controlled morphing"? A pattern would play normally if no steps are currently focused; a focused step plays the event/triggers from another pattern. Besides that, I thought about some "focusing templates": even steps odd steps Or, to generalize, set up a "interval" and "offset" parameter, such that can be selected a step every "interval" starting by "offset" (so, for even steps: int=2, off=0; for odd steps: int=2, off=1; '90s dance claps: int=8, off=4 :)) Edit: templates could be applied within a limited range and using different methods: Replace, Add, Sub, XOR (toggle). Hey, what about applying templates to the trigger layers too? One can create cool patterns in seconds!! Sorry for being such a generator of so many features :P
  23. Thanks TK for giving account of this idea!! Some ideas while reading the manual (please note that I speak more as a nerd than as a musician :D) limiting the actions in the Utility page (copy, paste, clear, move, scroll, random) for just the focused ones; step recording that only (over)writes the focused steps; This filtering can be applied by simply calling the respective function while displaying the focus layer (as far as I know, no one of them take account of which event/trigger layer you're displaying) Some nice tools for the focus layer: invert; select a step range (doable by pressing the first and last GP of the range); scroll (combined with the existing Utility function?);
  24. (in this post, I assume that a "selected" step is intended as "activated" in the user manual, i.e. with the GP led turned on) I sometimes need to modify not all the steps, neither just the selected ones, but rather an arbitrary subset (let's say "focused" steps). I rapidly thought (and not considering consequences or implementation issues!) about adding a fourth layer where you can "focus" or "unfocus" the steps. This layer doesn't trigger anything by itself, nor it will be stored into any pattern. This layer can be edited with GP buttons as usual, but with something like a FOCUS button, you just turn the datawheel and the events of the focused steps get modified. The behaviour of this button could be the same as ALL. By pressing both FOCUS and, while pressed, one of the trigger layers' buttons, a trigger layer gets copied and pasted into the focus layer. So the behaviour bosone thinks about can be accomplished by pressing FOCUS + Trigger Layer A, then spinning the datawheel while keeping FOCUS pressed. The trigger layer and the focus layer are normally independent. If one wants to always focus the steps selected in a layer ("autofocus" :) ), i.e. making the focus layer a slave of a trigger layer, he can press both Trigger Layer A/B/C and, while pressed, the FOCUS button (similar as before but the order is swapped). What do you think about? It can be a feature I'd really like to have!
  25. Sono un felice possessore di un SIDv2 con due Core mono (presto lo espanderò) e di un SEQ quasi finito. Tutto quello che so di elettronica è tramite giochini ed esperimenti vari, insomma le cose che trovi su Internet... potrei dire delle cavolate assurde però puoi tempestare volentieri!! meglio cmq in un altro thread (così almeno facciamo capire che c'è attività :) ) Piacere, Enrico da Agrigento (a Torino x studio)!!
×
×
  • Create New...