| Yes, the files saved as Format 0, using other programs (I've tried Digital
Orchestrator Plus, Midisoft's Recording Session, Cakewalk Home Studio,
Opcode's Vision for Windows) all work between themselves. Additionally, they
all play in other players, like the Window's Media Player. (I will test Cubase
soon, but haven't had the chance yet.)
I haven't recently tested MIDI files from a Mac in these programs, but I don't
think that there was a problem. I'll check and get back to you.
I think that there is a byte turnaround between Mac and Windows files, though
I've been able to save MIDI files created on a Mac on a PC disk and open them
on a PC without doing anything other than making sure there was a .mid
extension on the filename. The same was true for playing PC MIDI files on a
Mac. So, if there is a byte turnaround between the platforms, it doesn't seem
to make a difference as far as MIDI files are concerned.
I have been told (by someone who has looked at the files in a hex editor) that
one possible reason Cakewalk files aren't working is that Cakewalk may be
adding some meta information to the files. While this info is a part of the
MIDI standard, CSound may not be handling well. That's out of my realm of
knowledge, but I'll put it out there in case that makes sense to anyone.
Todd Hodges
Keenan Lawler wrote:
> Does anyone know why Csound doesn't accept Format 0 files from Cakewalk
> (and various other applications, as Todd reports)? Todd, do the "Format
> 0" files created on Windows with different applications work between
> those applications, and do the files created on the MAC work for those
> applications? What is the difference between a MAC-created and a
> Windows-created file with the same MIDI data? It would be peculiar if
> the Windows programs had it all wrong the right way (of all right the
> wrong way, I'm getting confused here).
>
> Job van Zuijlen
____________________________________________________________________
Get free e-mail and a permanent address at http://www.netaddress.com/?N= |