Attempts made
Mac Plus:
SoundEdit 1.0 crashes if I open it from my bluescsi system 6.0.8, but runs if I let it boot from these diskettes (finder 4.2), then you're left with 60kb free on disk unless I whip out a FloppyEMU or external disk drive
SoundEdit 2.0.5 runs under System 6.0.8 no...
I'm happy to sell:
1x bare main PCB
1x front case plate PCB
1x back case plate PCB
1x pre-programmed pic12F1501 chip, which you'd then be able to remove from the Bom list you'd buy yourself.
Keep in mind I'm in Canada and sending even a small box to the US is now salty.
Let's do a napkin economic analysis about this particular project.
First of all, despite it being well known in the late 80's, it concerns mostly 68000 macs since other solutions started appearing around the time of the powerbooks, making it relatively niche.
While the PCBs are cheap (around $6...
thanks all, it seems to work taking 0 chances with:
-using a MaxApplZone() at the start
-using MoreMasters() for good measure (who knows how some .midi files go up in size and data content)
-NewPtr and DisposePtr for those arrays in case a 2nd, 3rd, etc file is loaded up (so I'm currently...
MaxApplZone();
MoreMasters();
is a promising avenue being tested atm.
edit - and using NewPtr for those dynamically allocated arrays instead of malloc
and using HLock HUnlock on theBigList....
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...
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?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.