Home » The PARIS Forums » PARIS: Main » We can all be proud now.
| We can all be proud now. [message #57042] |
Thu, 18 August 2005 12:59  |
whatever
Messages: 1
Registered: August 2005
|
Junior Member |
|
|
gt;
> ;oP
>
>;O)
"EK Sound" <spamnot.info@eksoundNO.com> wrote in message
news:430510b2$1@linux...
> You would need TWO to be able to record the theme to Deliverance
> wouldn't you??? ;-)
>
> David.
>
> DJ wrote:
> > http://www.sonicstate.com/news/shownews.cfm?newsid=2275#
> >
> >
> > I'm sure this will be useful in my bluegrass recording sessions
> >
> > ;oP
> >
> >LOL...
"EK Sound" <spamnot.info@eksoundNO.com> wrote in message
news:4304f6b4@linux...
> One word.... ICK!
>
> David.Man.....I KNOW we don't need any Behringer reviews around here.....
Jimmy
"EK Sound" <spamnot.info@eksoundNO.com> wrote in message
news:4304f6b4@linux...
> One word.... ICK!
>
> David.EK Sound <spamnot.info@eksoundNO.com> wrote:
>One word.... ICK!
>
>David.
Two words: Fire Extinguisher
LOLHi all,
Well, I just had to shut down a session because, frankly, I'm stumped. Everything was going
quite smoothly, and then POW! PARIS locked up and wouldn't respond. This happened just after hitting
STOP after a vocal take. What was funny about this was that the MEC's obviously lost sync, and just
sat there blinking as if I'd just turned the computer on, in their idling state. This happened
immediately upon PARIS locking up.
After restarting, I tried to start PARIS, and saw the MEC's being to go through their
initialization (on-screen the PARIS startup window said "Beginning Hardware Initialization" or a
reasonable facsimile thereof). They appeared to get sync (yellow lights turning solid), then dropped
out and went back to their idling behavior ( yellow clock lights blinking).
I then tried restarting, only to have the same thing happen again.
1. Unplugged and reinserted all SCSI cables going from the EDS cards to the MEC's; no dice.
2. Switched out SCSI cables from EDS to EDS with all three cables still attached but re-ordered; no
dice.
3. Tried going into PARIS.cfg and removing UseHouseSync=1, only using one EDS and one MEC; no dice.
4. Tried editing PARIS.cfg so that "MasterOutputCard=1" instead of "0"; no dice.
5. Tried switching out SCSI cables from EDS to EDS with only one cable attached to one MEC at a
time; no dice.
6. Tried switching EDS cards from slot to slot and subsequently switching cables to that card; no
dice.
7. All the above starting with #3 occurred with the Aardvark master clock turned off.
8. Also tried booting up from a different hard drive and starting PARIS from there, with a
completely different .cfg file, different PARIS on a different hard drive, different Default Project
file, everything. This worked fine last time I used it, but no dice.
So, what the hell? I got nothing here. I feel like I've tried everything.
My setup was as follows:
PowerMac 933, upgraded to 1.467 GHz (have been using this with no problem for a year). UAD-1 card
installed, with:
3 EDS, 3 MEC
MEC 1: 2 input cards, 2 output cards
MEC 2: 2 ADAT cards, 2 output cards
MEC 3: no cards
Aardvark TimeSync II word clock generator.
Lucid word clock distribution box.
ZAOLLA word clock cables, all the same length, all coming from the Lucid.
Like I said, I got nothin'. Any ideas? I need to get this project mixed and sent out for a
film; it's only a few tracks and wouldn't take long if only I could actually get PARIS to start up
and open the project.
Crapulence.
bc
bcYeah... before you ask, "Did you disconnect the EDS ribbon cable interconnects during your
card-swapping?"
Yup, I made sure to try that.
Thanks in advance for any help or advice...
bcTry removing and reinstalling the Paris software. Make sure
to purge all Paris items and extensions, and cold boot after
removal and installation.
David.
Brian Carter wrote:
> Hi all,
>
> Well, I just had to shut down a session because, frankly, I'm stumped. Everything was going
> quite smoothly, and then POW! PARIS locked up and wouldn't respond. This happened just after hitting
> STOP after a vocal take. What was funny about this was that the MEC's obviously lost sync, and just
> sat there blinking as if I'd just turned the computer on, in their idling state. This happened
> immediately upon PARIS locking up.
>
> After restarting, I tried to start PARIS, and saw the MEC's being to go through their
> initialization (on-screen the PARIS startup window said "Beginning Hardware Initialization" or a
> reasonable facsimile thereof). They appeared to get sync (yellow lights turning solid), then dropped
> out and went back to their idling behavior ( yellow clock lights blinking).
> I then tried restarting, only to have the same thing happen again.
>
> 1. Unplugged and reinserted all SCSI cables going from the EDS cards to the MEC's; no dice.
> 2. Switched out SCSI cables from EDS to EDS with all three cables still attached but re-ordered; no
> dice.
> 3. Tried going into PARIS.cfg and removing UseHouseSync=1, only using one EDS and one MEC; no dice.
> 4. Tried editing PARIS.cfg so that "MasterOutputCard=1" instead of "0"; no dice.
> 5. Tried switching out SCSI cables from EDS to EDS with only one cable attached to one MEC at a
> time; no dice.
> 6. Tried switching EDS cards from slot to slot and subsequently switching cables to that card; no
> dice.
> 7. All the above starting with #3 occurred with the Aardvark master clock turned off.
> 8. Also tried booting up from a different hard drive and starting PARIS from there, with a
> completely different .cfg file, different PARIS on a different hard drive, different Default Project
> file, everything. This worked fine last time I used it, but no dice.
>
>
> So, what the hell? I got nothing here. I feel like I've tried everything.
>
>
> My setup was as follows:
>
> PowerMac 933, upgraded to 1.467 GHz (have been using this with no problem for a year). UAD-1 card
> installed, with:
>
> 3 EDS, 3 MEC
>
> MEC 1: 2 input cards, 2 output cards
> MEC 2: 2 ADAT cards, 2 output cards
> MEC 3: no cards
>
> Aardvark TimeSync II word clock generator.
> Lucid word clock distribution box.
> ZAOLLA word clock cables, all the same length, all coming from the Lucid.
>
>
>
> Like I said, I got nothin'. Any ideas? I need to get this project mixed and sent out for a
> film; it's only a few tracks and wouldn't take long if only I could actually get PARIS to start up
> and open the project.
>
> Crapulence.
>
>
>
> bc
> bcIn article <43053184$1@linux>, "Dave(EK Sound)" <audioguy_nospam_@shaw.ca> wrote:
> Try removing and reinstalling the Paris software. Make sure
> to purge all Paris items and extensions, and cold boot after
> removal and installation.
>
> David.
>
OK, sure-- why not? Thing is, I just did this a few weeks ago, with a clean hard drive,
zeroed out and ready to rock, and even a new, super-stripped-down (and I mean
ultra-mega-super-stripped-down) OS 9.2.2 installation.
So, this is a fresh installation, more or less. Though, of course, you never know. We had
storms the other day and my computer shut down during a power outage rather suddenly. And this is
obviously worth a try.
Thanks for the quick reply. I really hadn't thought of that-- you get a little frustrated,
and it's just that much harder to think clearly.
Oh, well-- we got the tracking done we needed; just a matter of editing and mixing if I can
get PARIS up and runnning...
I should really get a backup power supply...
bcIn article <43053184$
|
|
|
|
| Re: We can all be proud now. [message #57065 is a reply to message #57042] |
Fri, 19 August 2005 04:10  |
John [1]
Messages: 2229
Registered: September 2005
|
Senior Member |
|
|
r />
> injured between April and October. This gives an annual death rate of 7,700,
> a third of the IBC estimate.
>
>Paris is an OS ? hehe
DJ wrote:
> Do the software reinstall that Dave recommends. Almost the exact same thing
> happened to me a couple of weeks ago. For some reason, when I added a device
> to a second computer that was sharing the same clock with Paris, Paris would
> lose sync and fil to boot. A Paris OS uninstall/reinstall solved the
> problem.
>
> Deej
>
> "Brian Carter" <bricrter@skedaddlemindspring.com> wrote in message
> news:bricrter-A2C593.20154318082005@adsl-23-222.swiftdsl.com.au...
>
>>In article <43053184$1@linux>, "Dave(EK Sound)" <audioguy_nospam_@shaw.ca>
>
> wrote:
>
>>>Try removing and reinstalling the Paris software. Make sure
>>>to purge all Paris items and extensions, and cold boot after
>>>removal and installation.
>>>
>>>David.
>>>
>>
>> OK, sure-- why not? Thing is, I just did this a few weeks ago, with
>
> a clean hard drive,
>
>>zeroed out and ready to rock, and even a new, super-stripped-down (and I
>
> mean
>
>>ultra-mega-super-stripped-down) OS 9.2.2 installation.
>>
>> So, this is a fresh installation, more or less. Though, of course,
>
> you never know. We had
>
>>storms the other day and my computer shut down during a power outage
>
> rather suddenly. And this is
>
>>obviously worth a try.
>>
>> Thanks for the quick reply. I really hadn't thought of that-- you
>
> get a little frustrated,
>
>>and it's just that much harder to think clearly.
>>
>> Oh, well-- we got the tracking done we needed; just a matter of
>
> editing and mixing if I can
>
>>get PARIS up and runnning...
>>
>>
>> I should really get a backup power supply...
>>
>>bc
>
>
>These cards get SO hot make sure you have plenty of fan going on.
Brian Carter wrote:
> Bad card.
>
> ~{8^<)Hi all,
As promised I've put together a PPJ of collected Paris FX presets - unfortuantely
I can't attach it as it's too large (c.1.7Meg) - I'll happily e-mail it though
if you drop me an e-mail. I'll also send a copy to Mike Audet as he's got
some webspace for this purpose.
Most of these have been compiled from other users or the newsgroup or the
FX preset updates. There are settings for the Comp, NoLimit, Plate and Room
Reverbs, Chorus, and Tap Delay.
If anyone has any to add, let us all know. You might also want to contact
Mike Audet (mike@mikeFSPAM!audet.com) and myself, as Mike has some webspace
(www.mikeaudet.com/paris) set up for Paris FX Presets.
Enjoy.
Dan B / dbp.s.
Note that: The TubeWarmer comp preset is just the active gain element. The
PCM 60 reverb preset requires the BarbQ or FreakQ plug-in as well (search
the newsgroup). The UAD 1172LN vocal preset requires about 14db of gain reduction.
Cheers,
db
"db" <daniel_burneNOSPAM@yahoo.com> wrote:
>
>Hi all,
>
>As promised I've put together a PPJ of collected Paris FX presets - unfortuantely
>I can't attach it as it's too large (c.1.7Meg) - I'll happily e-mail it
though
>if you drop me an e-mail. I'll also send a copy to Mike Audet as he's got
>some webspace for this purpose.
>
>Most of these have been compiled from other users or the newsgroup or the
>FX preset updates. There are settings for the Comp, NoLimit, Plate and Room
>Reverbs, Chorus, and Tap Delay.
>
>If anyone has any to add, let us all know. You might also want to contact
>Mike Audet (mike@mikeFSPAM!audet.com) and myself, as Mike has some webspace
>(www.mikeaudet.com/paris) set up for Paris FX Presets.
>
>Enjoy.
>
>Dan B / dbP.S.S. (!)
- Just to reiterate, I don't think there's anything/much new here, but it
should be a useful compilation.
- The actual file size is nearer 2.4 meg.
- John- I'm not having any joy replying to your e-mail address.
- Mike Audet is posting it up on his webspace fairly soon.
Best wishes,
db
"db" <daniel_burneNOSPAM@yahoo.com> wrote:
>
>
>p.s.
>Note that: The TubeWarmer comp preset is just the active gain element. The
>PCM 60 reverb preset requires the BarbQ or FreakQ plug-in as well (search
>the newsgroup). The UAD 1172LN vocal preset requires about 14db of gain
reduction.
>
>
>Cheers,
>
>db
>
>"db" <daniel_burneNOSPAM@yahoo.com> wrote:
>>
>>Hi all,
>>
>>As promised I've put together a PPJ of collected Paris FX presets - unfortuantely
>>I can't attach it as it's too large (c.1.7Meg) - I'll happily e-mail it
>though
>>if you drop me an e-mail. I'll also send a copy to Mike Audet as he's got
>>some webspace for this purpose.
>>
>>Most of these have been compiled from other users or the newsgroup or the
>>FX preset updates. There are settings for the Comp, NoLimit, Plate and
Room
>>Reverbs, Chorus, and Tap Delay.
>>
>>If anyone has any to add, let us all know. You might also want to contact
>>Mike Audet (mike@mikeFSPAM!audet.com) and myself, as Mike has some webspace
>>(www.mikeaudet.com/paris) set up for Paris FX Presets.
>>
>>Enjoy.
>>
>>Dan B / db
>Hi guys,
Thanks for the suggestions. Just to let you know ...
I've ditched the Oasys (it was disabled anyway in the device manager... but
still), and moved both cards to different slots. I've also removed some redundant
HDs from the system. This seems to have helped – but not totally resolved
- the stability with a one card system (and reduced XP boot up times of around
8 minutes to less than 1 minute), so clearly something dodgy was going on
(IRQs?).
The FXs subsystem is (was) installed (as per XP install instructions).
Fingers crossed, the presets are now saving. At least, they do when between
restarts of Paris now – haven’t rebooted and restarted Paris yet, but – as
I say – fingers crossed.
It seems the second EDS card is basically busted. So I’m back in the market
for another EDS…
db
"DJ" <animix_spam-this-ahole_@animas.net> wrote:
>OK,
>
>It's been a long time since I've used Paris on win ME, but my thoughts are
>that if it was unstable with one card that issue needs to be resolved first
>off so losing the Korg Oaysis card (at least for now) is the first step.
>
>When I was running Paris on Win XP I was using a pre-SP1 OS that was very
>stable. Maybe the SP1 or SP2 is glitching things so if you've got an older
>XP system disk, don't load the SP's. Paris doesn't need them and you don't
>want to use this computer for anything other than audio
>anyway.........right?
>
>Assuming that there is a stable Win XP install, it sounds like one of the
>following situations may be in play.
>
>1. Maybe the newest Paris XP subsystem is not installed properly.
>
>2. It may be an IRQ conflict with the graphics card (or other device besides
>the Korg Oaysis which is no longer a factor in this)
>
>3. It may be an actual problem with the EDS card itself.
>
>4. It may be a bad SCSI cable between the card and the Paris IF
>
>5. Faulty RAM can be a big party stopper and faulty ribbon cables that are
>connecting the HD's to the controllers can cause instability as well.
>
>6. The Radeon graphics card may not be happy on a VIA chipset. I had this
>problem trying to use an NForce card on my ASUS A7V8X mobo. It likes
>
>Assuming that one EDS card can be configured to be stable, then after
>checking to make sure there are no IRQ conflicts between the cards and any
>other devices/controllers, I would start looking at the sync cables between
>the two cards if the 2nd card starts causing additional instability
>problems.
>
>Also, TheSoniq knows the error codes and what causes them. He's a nice guy
>and will help if you call him up.
>
>Hope this helps.
>
>Deej
>
>
>
>
>"justcron" <justcron@hydrorecords.compound> wrote in message
>news:Report message to a moderator
|
|
|
|
Goto Forum:
Current Time: Fri Sep 20 06:37:41 PDT 2024
Total time taken to generate the page: 0.01459 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
