simple pro tools set-up for radio production???

hi, i've pointed out before on this newsgroup how protools is a
music-based app and was
adopted by default as the defacto 'standard' for the most part - for
broadcast commercial
production.

Now that i've got that bias out of my system...

I appreciate the simplicity i've known from experience of a pure
analogue experience - the
job-scrub splice/editing process, above all... in Bias Peak 2.63.

I need to abandon my long orphaned fostex foundation standalone daw..
the closest thing
to a simple straightforward broadcast production user interface.

having need for 8 channels for multitrack stuff, and being dedicated to
the Mac OS (preferably
pre osx since, again os 8 and 9 are all i ever really needed).. i am
revisiting the need to
move to some computer based daw app.

Nobody by any means makes it easy to emulate what i want, that's for
sure. Simplicity comes
at the greatest "cost." That said, any suggestions about a Digi or
alternative app, that is just
basically 8 tracks with a mac software platform, minimal BS,
(effects/features unnecessary
for commercial production) and something that's as close to an analogue
mixer/tape layout with
digiital I/O, as possible? The ideal scenario for me would be Peak 2.6
or 3, (the code in 2.6 is
smoother for scrub/edit than subsequent versions) - with 8 vs. 2
channels.

ProTools is filled with features i have no need for. Deck puts an
extra layer of bounce-in and bounce-out of "peak" in the way of direct
record in/out and editing.

I've toyed with shareware even; like Audacity- that had the illusion of
coming close - but has
its limitations.

I would be glad to try PT again, but need some help from somebody on
creating the most pared-down template layout as possible to allow for:
voice track only, or, alternately, mono voice,
and 6 to 8 other tracks for production music/efx lay-in mix with voice
- for spot work.

Ideas welcome and appreciated!

Cheers

Mike

.

Relevant Pages

  • Re: simple pro tools set-up for radio production???
    ... adopted by default as the defacto 'standard' for the most part - for ... to a simple straightforward broadcast production user interface. ... move to some computer based daw app. ... voice track only, or, alternately, mono voice, ...
    (rec.audio.pro)
  • Re: The curse of constant fields
    ... production branch, EAR construction etc) for a reasonably important J2EE app I am pretty fanatic about sanitizing everything prior to an official build. ... our environment it would be unrealistic. ... Because a lot of time can be wasted if a tester reports that an error is still there, and then it's a question of is the error still there because the build is flawed, or because the developer who "fixed" it only fixed it for a different use case or in his own development environment. ...
    (comp.lang.java.programmer)
  • Re: Homegrown synchronization
    ... my launcher just copies the production backends as is. ... What you need is to have the synch app zip up the production ...
    (microsoft.public.access.replication)
  • Re: What is the story with Server Busy
    ... If an activeX control calls your app then it will wait for ever without showing a message, but if something cross process calls your app and doesn't get a response then the message will appear. ... I put up a form for an error, and if I click on a button to debug then I return from the call to the error handler with a result code to execute the following: ... This highlights probably the BIGGEST problem in linking complex applications together via ActiveX controls, that you reach a level of complexity where you just can't tell what is causing problems. ... The original ANSI standard for C was delayed for one year - by me and two other people who were pushing hard to tighten up several things like its screwed up order of operations and arguments types in calls. ...
    (microsoft.public.vb.enterprise)
  • Re: The curse of constant fields
    ... EAR construction etc) for a reasonably important J2EE ... No automated testing of the complete app through its web ... Also, presumably, before you deploy to production, you deploy to a staging ... or pre-production environment which replicates the production environment, ...
    (comp.lang.java.programmer)