PC still playing Amiga catchup

[bloodline]

I see your EMU10K and raise you a MOS Technology 8634!!

Emu10K... pah, I have one of those on a card I'm not even using (in my old PC)

Actually I found my old SBLive 1024 a bit of a pain for line in audio capture. There's a noise floor of about -80dB that you can't seem to get rid of.

I still have one too!!! With the "live drive", it was a good card and I did a lot of work on it from about 2001 to 2004... Then I moved on to Mac and Firewire equipment. You are right though, the Live isn't great for recording

[bloodline]

Dodgy M$ timer:

This is an experiment for those of you with good internal clocks. Play your favourite House/Dance track on Windows Media Player and watch the progression bar. To me, it doesn't appear to keep the beat.
Let me know.

A few years ago (2003), I wanted to get some of my old OctaMED files into Logic 5...

The solution I came up with was to play the OctaMED file via MIDI into the PC, which was set to record... (The Amiga had no way of getting files out other than via floppy, and OctaMED's save SMF function refused to save properly).

I had both machine set to the same BPM... but the Amiga drifted out quite dramatically over the course of 3min... I had no choice but to work out the Average BPM and use that... quantizing the musical data on the PC later... That was my first experience with the lameness of the Amiga's timing.

[bloodline]

OctaMED (or CAMD or the interface driver?) doesn't support an external clock? Can it act as a clock source? EDIT: OK, so I guess CAMD just passes along system messages, and it's up to the devices and sequencer to decide how to use and interpret clock messages. There's an old thread here on Amiga.org talking about MED supporting legacy MIDI clock messages but not MIDI timecode. Sounds like Bars 'N Pipes is good to go, though. Wish I still had my AMAS. Just have the DSS8+ now and no MIDI interface. Don't feel like wiring my own (which I'd probably foul up anyway).

Yeah, OctaMED's MIDI support wasn't the most amazing thing ever... I didn't bother messing around, this was 6 years ago... got the job done... haven't worried about it since.

I have a Creative/E-mu 1212m in my PC. It's a decent card, but I'm not very fond of the software interface.

Oh E-mu... how the mighty have fallen... I must get myself an old EMAX-II, some time...

I just bought Logic Express for my MacBook Pro, and I've got my Motif ES8 connected via USB. I've been trying to track down an mLAN interface, but they're no longer in production, and I don't trust eBay for this. :-/ I also need a low latency audio interface for the Mac. Any suggestions? Something that's supported on both Windows and Mac OS would be ideal, but not required. Cost is a factor, but only because I don't plan on using the interface very often; otherwise, I'd probably just buy something nice from MOTU.

If you only need a single audio in, then I recently used a "Blue Icicle" (http://www.equixotic.com/2008/11/07/blue-icicle-xlr-to-usb-mic-converter/) USB interface. The Audio quality is great, low latency (uses core audio) and it provides Phantom power. For a £50 interface, wonderful!

I have had a number of different interface over the years, but whenever I start a new project... I always go back to my Edirol FA-101... I bought it back in September 2004... and it's been my workhorse ever since... Other interfaces have come and gone, but not this one... for both studio and live work, it's built like a tank.

If I were to buy an interface today, it would be a MOTU UltraLite Mk3.

[bloodline]

I did in post #275 (way back).  I stated some since then, but even those in post #275 haven't been addressed.  Part of the gaming interface is not just joystick speed but even the gaming elements are standard on amiga like sprites, collision detection, priority settings, blitter, etc.  Sure you can find some cards that may have a few of these but mostly it's done in software.  So amiga would win there as well when it you time how long it takes to find collision detection of various elements, move sprites around, etc.

If you had ever written anything more complicated than a simple shoot'em up or platformer, then even on the amiga, you would avoid using the sprite hardware and use the blitter... And the hardware colision detection was also only useful for the simplest of tasks... Software routines were simply better.

>Um... The work I do, music production, simply can't be done on older machines, they are just too slow and have no support for the high definition audio interfaces that I use.

For many things, Amiga audio is sufficient for things.  I know they have a method of doing 14-bit sound by merging amiga's audio channels which is more than enough for me.

I have written several subranging routines on the amiga I know how to fake 14bit the audio, the results are noisy and certainly not suitable for professional audio... Or even modern consumer Hi-Fi equipment!

>What, a few years ago, used to require several rooms of equipment and a large mixing console, can now be done on a £2000 MacBook Pro, a 24bit firewire multichannel audio interface and Logic Studio (plus and other software of your choice)...

You may have that-- but is that a standard.  If not, you can buy an audio board for Amiga as well.

The laptop is standard, albeit top of the range CPU. The laptop comes as standard with a 24bit 48Khz audio interface! Something that you can't get for the Amiga at all (which even with expensive hardware never got beyond 16bit @44100Hz.

The is no FireWire for amiga, thus no good audio interfaces