Search results

ok, the same example above, after running back in forth into my main project, rebooting my emulator, etc. no. longer. works. I bet it's something really easy I'm missing but I'm properly stumped. this should output 0,1,2,3 in the first 4 trackno debugging values on the right since I'm at...

so maybe the solution is to use a handle so I can avoid my structs pointers to get trampled over? seems to work here:

I've been working on programatically open up a .mid file, parse it to find the minimal MIDI command bytes out of it and set up a data structure that makes it easy to play it back on a System 7 Mac SE/30. All the more esoteric parts of the project have been more or less solved already, but this...

YES, it finally works. Thanks for the refresher tips on bytes and on how to address pointer offsets more efficiently. Thanks for your patience and offering great guidance and some good ol' vintage docs. As soon as I saw the scope behave well with this under 31,250, I disconnected my breadboard...

Can anyone verify if I'm doing what I think I'm doing? int *addr = (int *) 0x0001DA; *addr = 11; asm { MOVE.B (SP),(SP) } *addr = 0x28; this freezes my program but I still can move my mouse cursor around. When I click, even that freezes as well.

Good idea. It gets my bytes correctly at 38,400 set in both the mac SCC through SerReset and on the scope, using these 2 lines: const int kConfigParam = 1+data8+noParity+stop10; gOSErr = SerReset(gOutputRefNum, kConfigParam); I have no easy way to probe these lines. My small MIDI...

Getting MIDI across to my sound modules I have achieved, no problem, for years. However, only through commercially developped software that I open and execute as an end-user (Cubase, Space Quest III, Master Tracks Pro 4, etc). The goal is to recreate what they did through my own C routines. If...

SE/30 modem port -> pocket Mac, midi out -> my breadboard midi in connector, current limited loop Other side of H11: 5V and GND are provided and a 1k resistor acts as load that I'm probing. I don't understand what you're suggesting I do differently since my use case under normal conditions...

I also tried keeping the default clock, setting the SerReset parameter like above but adding '2' instead of '1' to get 28,800 instead of 38,400 and my scope is detecting: 0xC6 0x22 instead of 0x90 0x3C 0x64

I assembled a small breaboard midi-in circuit, powered by a bench supply providing 5V, according to this well known circuit: which looks like this (I had optoisolator H11 chips from previous projects) and just to prove it works, I plugged my pocketmac midi out cable to this breadboard while...

I don't want the solution to depend on this. I have other modules that should be used for this purpose, like a Roland MT-32, just as it was used without a special system folder extension for MIDI at all in Space Quest III, just a pure code wise solution dealing with this.

Interesting parts in IM: Serial Device: so I could just drop the asm stuff that seems to lead me astray, go back to the IM: serial device code, and just massage the right data for a PBControl call inserted at the right place to get external clock going?

I can *try* to convert it to C but you assume I'm solid in 68k assembly to begin with - I am not. There are so many questions that pop into my head as I'm typing this up and trying to compile it as I go, so that I don't let typos creep in. branching seems to work if I use labels in THINK C using...

yeah, I started poring over the entire code and I guess that's only a small section of a bigger initializing routine. I'll see if I can replace everything I had for serial comm with this, hopefully my asm block adaptation chops are not too rusty

I naively brought this code from this post https://68kmla.org/bb/index.php?threads/external-localtalk-serial-port-clocks.35645/post-453444 formatted for THINK C: void SCCASMInit(void) { asm { MOVE.B #4,(A0) ; pointer for SCC reg 4 MOVE.L (SP),(SP) ; Delay...

Just a wrapped asm { } block Good to know , I'll give it a try, thanks!

I saw your thread but did not understand how to leverage it. What doesn't connect in my mind is the fact that without bringing in my own breadboard circuit with a 1 MHz oscillator and frequency dividers, I'm able to use Cubase just fine and play arbitrary .MID files all day long, + play a...

// Insert your include list here #include <stdio.h> #include "Serial.h" // Insert your #define list here // --- MIDI spec hard coded values --- // good reference is here: https://www.music.mcgill.ca/~ich/classes/mumt306/StandardMIDIfileformat.html#BM1_1 // from the midi.org itself...

Let's get what I'm using as gear out of the way: Dev Machine: modern PC with Basilisk II set with System 7.5.5, Symantec C++ 6.0 Target Machine: SE/30 with System 7.5.3, no Apple MIDI Manager (prefer not to use it since I want to target 6.0.8 and a Mac Plus as well) PocketMac MIDI interface...

I took mine from Macintosh Garden here: https://macintoshgarden.org/games/mac-a-mug-pro I was able to successfuly take that file, unstuff it under System 7 (using Basilisk II) since I found dealing with unstuffing under System 6 is just asking for pain usually, then gone back to mini-vMac and...