Home » The PARIS Forums » PARIS: Main » Well, FWIW....in case any of you guys get adventurous
| Well, FWIW....in case any of you guys get adventurous [message #91687] |
Sat, 20 October 2007 16:46  |
DJ
Messages: 1124
Registered: July 2005
|
Senior Member |
|
|
gt ;crackles =
in=3D20<BR>>>>> =20
it?<BR><BR>Not nearly as bad...No=20
=3D<BR> >>>>=3D3D<BR>& gt;study=3D3D20<BR>>=20
=3D20<BR>>>>> diet of rice crispies, but there were =
a=20
couple<BR>of crackles=3D20<BR>>>>> =20
(random,<BR>=3D3D<BR>>I=3 D3D20<BR>> bounced =
twice and=20
listend =3D<BR>>>>>to both=3D20<BR>>>>> =
mixes out of=20
phase,<BR>set markers =3D3D<BR>>at=20
=3D<BR> >>>>the=3D3D20<BR> > =
=3D20<BR>>>>> =20
crackles, and verified by listening one at a time)=20
This<BR>also=3D20<BR>>>>> =20
leads<BR>=3D3D<BR>>me to=3D3D20<BR>> believe =
it's some=20
sort of =3D<BR>>>>>ppj=3D20<BR>>>>> =
corruption=20
brought on by the<BR>UAD=20
=3D3D<BR>>stuff,=3D20<BR>>>>> =
only=3D3D20<BR>>=20
it happens over time, but I haven't been able=20
=3D<BR>>>>>to=3D20<BR>>>>> =
verify=3D3D20<BR>>=20
=
=3D<BR> >>>>this<BR>yet.&a mp;lt;BR>><BR>>7.) =
Have=3D20<BR>>>>> you tried physically swapping=20
=3D3D<BR>>your left=3D3D20<BR>>=20
=3D<BR>>>>>speaker=3D20<BR>>>>> =20
with<BR>>your right speaker?<BR>swapping speakers=20
make=3D20<BR>>>>> no=3D3D20<BR>> =
difference, swapping=20
the cables leading to=3D20<BR>>>>> =
the<BR>speakers makes=20
it =3D3D<BR>>happen in=3D3D20<BR>> =
=3D<BR>>>>>the=20
right=3D20<BR>>>>> =
speaker.<BR>><BR>> Just=20
trying to think of things to=3D20<BR>>>>> =
=3D3D<BR>>try=20
&=3D3D20<BR>> narrow it down=20
=3D<BR> >>>>by<BR>> process =
of=3D20<BR>>>>> =20
elimination.<BR><BR>I appreciate=20
=3D<BR> >>>>=3D3D<BR>& gt;your=3D3D20<BR>>=20
=3D20<BR>>>>> thought process. If this makes a light =
go off=20
for you,<BR>please =
=3D<BR>>>>>let=3D20<BR>>>>> =20
=3D3D<BR>>me=3D3D20<BR>&a mp;gt; =
know.<BR>><BR>>Can =20
=3D<BR>>>>>you e-mail=3D20<BR>>>>> me an =
mp3 file of=20
any song or =3D3D<BR>>songs that=3D3D20<BR>>=20
=3D<BR>>>>><BR>>>>> =
it's<BR>>doing this=20
on? If so, send it to: neil=3D20<BR>>>>> =20
|
|
|
|
| Re: Well, FWIW....in case any of you guys get adventurous [message #91690 is a reply to message #91687] |
Sat, 20 October 2007 18:27  |
|
|
her me forever. It probably will.
>
>01:00pm -- The Fun Begins -- It took an hour to copy the .dmg file to my
>empty Leopard computer. I mounted the disk image and then shift-double-clicked
>it. The image dramatically increased in size then faded away. In its place
>was an open directory that looked exactly like my old Macintosh HD directory.
>Perfect. A quick reboot and I'll be done.
>
>
> ------------------------------------------------------------ --------------------
>Check out the Shelly Palmer Report archive.
> ------------------------------------------------------------ --------------------
>
>01:04pm -- WTF? You know you would not be reading this article if this trick
>worked. It didn't. You also know that the definition of insanity is doing
>the same thing over and over again and expecting a different result. I tried
>the shift-double-click trick about four more times while I dialed Apple
tech
>support to try to get into the queue.
>
>02:14pm -- Apple Tech Support, an Oxymoron -- If my first tech support person
>had a thick foreign accent, I don't even know how to describe the language
>this gentleman spoke. After I described my problem to him he said, "I am
>not qualified to help you, you must talk to Level 2 tech support. Can I
put
>you in their queue? The wait time will be about 15 minutes." The line magically
>disconnected after 30 minutes forcing me to call back and go through the
>process again.
>
>The songs they play on hold at Apple Tech support are not for everybody.
>I'm being overly polite.
>
>04:32pm -- Level 2 Tech Support -- I have a new best friend at Apple, her
>name is Dawn. English is absolutely her first language and she could not
>have been nicer on the phone. There was only one problem. She had no idea
>why Leopard would not permanently mount this disk image. In fact, she told
>me a story about her Friday evening Leopard experience. Truthfully, I'm
surprised
>she was able to function at work on Saturday. Just a few tidbits of Apple
>knowledge from our call ...
>
>Yes, I found a bug. Engineering would take five to seven days to get back
>to me with a workaround or solution. She copied every file from her old
hard
>drive to her Leopard hard drive by hand (one at a time). She didn't know
>if my suggested work around would work because Leopard was "too new." The
>five different things we tried together (that she thought would work) all
>failed. No, there is no published list of files you can manually copy from
>Tiger to Leopard with any reasonable expectation of success. If my proposed
>solution didn't work I could wait for Apple Engineering to fix the bug or
>try to reinstall my old operating system. Ugh!
>
>She gave me her name, email and a direct dial phone number at Apple and
told
>me to contact her anytime. I appreciated the concern, but I still didn't
>have a working computer.
>
>06:12pm -- My Work-around -- This is not my first rodeo and I am not a computer
>novice. The workaround was obvious to me, but what a huge pain in the butt.
>Here it is in shorthand for the techno-geeks who care.
>
>1) copy the disk image to an external drive (1 hour).
>
>2) mount the drive and launch the Apple migration assistant. (4 hours)
>
>3) rename your admin account and short name appropriately (or you'll be
forced
>to edit every program that stores data in your user account).
>
>4) set the startup for your new account so that you don't have to ever see
>the phantom account you were forced to setup.
>
>5) get ready to reinstall a bunch of programs and re-enter 60% of your serial
>numbers.
>
>11:30pm -- Almost done -- Leopard is running on my computer. Almost every
>program came back to life. I probably spent two-three more hours over the
>next few days tweaking and re-installing stuff to get the computer working
>more or less like it did before the upgrade. And, sadly, I am seriously
considering
>wiping the drive again, reinstalling Leopard and reinstalling my programs
>from scratch. There's something not quite right about this install.
>
>Epilog -- Was it worth it? No. Should you attempt an upgrade to Leopard?
>If you don't have to erase your drive, you won't have this experience. The
>300 new features that Apple lists on their site are all incremental improvements
>over Tiger. Safari is still slow, spotlight is better, cover flow, as a
way
>to view a folder, is wonderful and it's far more useful than I ever imagined
>it would be. And, on this computer, Time Machine (Apple's "set it and forget
>it" backup software) does not work.
>
>Post Script -- For those of you who a
|
|
|
|
| Re: Well, FWIW....in case any of you guys get adventurous [message #91700 is a reply to message #91687] |
Sun, 21 October 2007 01:21 |
Sarah
Messages: 608
Registered: February 2007
|
Senior Member |
|
|
nced=20
>>>>> =3D<BR>>file.<BR>><BR>>3.)=3D20<BR>> can =
>>>>>you=20
>>>>> determine where the crackle rears it's ugly head?<BR>>IOW,=20
>>>>> =3D<BR>>is it=3D20<BR>> constant, more or less, or is it =
>>>>>intermittent?=20
>>>>> If<BR>>it's =3D<BR>>intermittent,=3D20<BR>> does =
>>>>>it seem to=20
>>>>> coincide with any particular<BR>>instrument or =
>>>>>=3D<BR>>track?=20
>>>>> For=3D20<BR>> example, could it be a =
>>>>>particular<BR>>plugin on=20
>>>>> the - let's say - =3D<BR>>cowbell=3D20<BR>> track, which =
>>>>>occurs=20
>>>>> though<BR>>most of the song, but not on =
>>>>>the=3D20<BR>> =20
>>>>> (confounded) bridge?<BR><BR>totally random...not in anyway =
>>>>>
>>>>> associated<BR>=3D<BR>>with a=3D20<BR>> particular =
>>>>>instrument.=20
>>>>> Fairly<BR>study though, like a bowl of rice=3D20<BR>> =20
>>>>> crispies.<BR>><BR>>4.) mute/disconnect the right =
>>>>>channel=20
>>>>> when =3D<BR>>listening=3D20<BR>> back to<BR>>the=20
>>>>> crackle-infested bounce to see if there's any =3D<BR>>pattern=20
>>>>> that=3D20<BR>> <BR>>might apply to (3)=20
>>>>> above?<BR><BR>none<BR>><BR>>5.) Is=20
>>>>> =3D<BR>>the=3D20<BR>> crackle happening on ALL systems? =
>>>>>IOW, have=20
>>>>> you<BR>>burned a CD of =3D<BR>>the=3D20<BR>> =
>>>>>bounced tracks=20
>>>>> & played it back on a home<BR>>stereo, in your =
>>>>>=3D<BR>>car,=20
>>>>> on=3D20<BR>> headphones, etc? Is it possible =
>>>>>that<BR>>for some=20
>>>>> odd reason the =3D<BR>>crackle is=3D20<BR>> due to =
>>>>>something in=20
>>>>> your<BR>>monitoring setup that isn't showing up=20
>>>>> =3D<BR>>on=3D20<BR>> regular playback, =
>>>>>but<BR>>might be=20
>>>>> showing up on a rendered =
>>>>>=3D<BR>>file?<BR>This=3D20<BR>> first=20
>>>>> came to my attention after I burned a CD of test mixes for=20
>>>>> =3D<BR>>the<BR>client=3D20<BR>> and he called me =
>>>>>after he got=20
>>>>> home and listened on his system =3D<BR>>(this<BR>was=20
>>>>> an=3D20<BR>> audio CD)so I would say it happens on all =
>>>>>systems...but I=20
>>>>> havn't=3D20<BR>> burnt<BR>another CD yet.<BR>It =
>>>>>does happen=20
>>>>> on my NS 10's as well as my<BR>=3D<BR>><BR>> Mackie 824's. =
>>>>>The 824's=20
>>>>> are hooked<BR>up thru the spdif out of =3D<BR>>the =
>>>>>mec=3D20<BR>> =20
>>>>> to a DAC-1 to a PVC passive volume control.<BR>The NS 10's are=20
>>>>> hooked<BR>=3D<BR>>up thru=3D20<BR>> 2 analogue outs from =
>>>>>the Mec into=20
>>>>> a GFA power<BR>amp. Crackles exisist<BR>=3D<BR>>on =
>>>>>the=3D20<BR>> =20
>>>>> left channel on both sets of speakers.<BR>><BR>>6.) =
>>>>>What=20
>>>>> happens =3D<BR>>when=3D20<BR>> you open up an older =
>>>>>project that=20
>>>>> you<BR>>DIDN'T have this problem =
>>>>>=3D<BR>>on...?=3D20<BR>> If=20
>>>>> you do a bounce with that,<BR>>does it sound as it did =
>>>>>before,=20
>>>>> =3D<BR>>or does=3D20<BR>> it now have =
>>>>>the<BR>>crackles in=20
>>>>> it?<BR><BR>Not nearly as bad...No =
>>>>>=3D<BR>>study=3D20<BR>> =20
>>>>> diet of rice c
|
|
|
|
|
|
| Re: Well, FWIW....in case any of you guys get adventurous [message #91708 is a reply to message #91687] |
Sun, 21 October 2007 08:13 |
Gene Lennon[4]
Messages: 26
Registered: November 2006
|
Junior Member |
|
|
>>>it<BR>is=3D20
> >>>> tonight, there are no crackles. That's wierd.=3D20
> >>>> Also<BR>=3D3D<BR>>the=3D3D20<BR>> crackles never<BR>show =3D
> >>>>till=3D20
> >>>> listening to the bounced=3D20
> >>>> =3D3D<BR>>file.<BR>><BR>>3.)=3D3D20<BR>> can =3D
> >>>>you=3D20
> >>>> determine where the crackle rears it's ugly head?<BR>>IOW,=3D20
> >>>> =3D3D<BR>>is it=3D3D20<BR>> constant, more or less, or is it =3D
> >>>>intermittent?=3D20
> >>>> If<BR>>it's =3D3D<BR>>intermittent,=3D3D20<BR>> does =3D
> >>>>it seem to=3D20
> >>>> coincide with any particular<BR>>instrument or =3D
> >>>>=3D3D<BR>>track?=3D20
> >>>> For=3D3D20<BR>> example, could it be a =3D
> >>>>particular<BR>>plugin on=3D20
> >>>> the - let's say - =3D3D<BR>>cowbell=3D3D20<BR>> track, which =3D
> >>>>occurs=3D20
> >>>> though<BR>>most of the song, but not on =3D
> >>>>the=3D3D20<BR>> =3D20
> >>>> (confounded) bridge?<BR><BR>totally random...not in anyway =3D
> >>>>
> >>>> associated<BR>=3D3D<BR>>with a=3D3D20<BR>> particular =3D
> >>>>instrument.=3D20
> >>>> Fairly<BR>study though, like a bowl of rice=3D3D20<BR>> =3D20
> >>>> crispies.<BR>><BR>>4.) mute/disconnect the right =3D
> >>>>channel=3D20
> >>>> when =3D3D<BR>>listening=3D3D20<BR>> back to<BR>>the=3D20
> >>>> crackle-infested bounce to see if there's any =
>=3D3D<BR>>pattern=3D20
> >>>> that=3D3D20<BR>> <BR>>might apply to (3)=3D20
> >>>> above?<BR><BR>none<BR>><BR>>5.) Is=3D20
> >>>> =3D3D<BR>>the=3D3D20<BR>> crackle happening on ALL systems? =3D
> >>>>IOW, have=3D20
> >>>> you<BR>>burned a CD of =3D3D<BR>>the=3D3D20<BR>> =3D
> >>>>bounced tracks=3D20
> >>>> & played it back on a home<BR>>stereo, in your =3D
> >>>>=3D3D<BR>>car,=3D20
> >>>> on=3D3D20<BR>> headphones, etc? Is it possible =3D
> >>>>that<BR>>for some=3D20
> >>>> odd reason the =3D3D<BR>>crackle is=3D3D20<BR>> due to =3D
> >>>>something in=3D20
> >>>> your<BR>>monitoring setup that isn't showing up=3D20
> >>>> =3D3D<BR>>on=3D3D20<BR>> regular playback, =3D
> >>>>but<BR>>might be=3D20
> >>>> showing up on a rendered =3D
> >>>>=3D3D<BR>>file?<BR>This=3D3D20<BR>> first=3D20
> >>>> came to my attention after I burned a CD of test mixes for=3D20
> >>>> =3D3D<BR>>the<BR>client=3D3D20<BR>> and he called me =3D
> >>>>after he got=3D20
> >>>> home and listened on his system =3D3D<BR>>(this<BR>was=3D20
> >>>> an=3D3D20<BR>> audio CD)so I would say it happens on all =3D
> >>>>systems...but I=3D20
> >>>> havn't=3D3D20<BR>> burnt<BR>another CD yet.<BR>It =3D
> >>>>does happen=3D20
> >>>> on my NS 10's as well as my<BR>=3D3D<BR>><BR>> Mackie 824's. =3D
> >>>>The 824's=3D20
> >>>> are hooked<BR>up thru the spdif out of =3D3D<BR>>the =3D
> >>>>mec=3D3D20<BR>> =3D20
> >>>> to a DAC-1 to a PVC passive volume control.<BR>The NS 10's =
>are=3D20
> >>>> hooked<BR>=3D3D<BR>>up thru=3D3D20<BR>> 2 analogue outs from =3D
> >>>>the Mec into=3D20
> >>>> a GFA power<BR>amp. Crackles exisist<BR>=3D3D<BR>>on =3D
> >>>>the=3D3D20<BR>> =3D20
> >>>> left channel on both sets of speakers.<BR>><BR>>6.) =3D
> >>>>What=3D20
> >>>> happens =3D3D<BR>>when=3D3D20<BR>> you open up an older =3D
> >>>>project that=3D20
> >>>> you<BR>>DIDN'T have this problem =3D
> >>>>=3D3D<BR>>on...?=3D3D20<BR>> If=3D20
> >>>> you do a bounce with that,<BR>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: this may make things easier for you guys with hardware gear [message #91731 is a reply to message #91713] |
Sun, 21 October 2007 20:26 |
Nappy
Messages: 198
Registered: September 2006
|
Senior Member |
|
|
audio if tolerances are sloppy in chipsets,
etc, and that has been the case for a while now
(with TI being about the only one of any significant reliability, though
I've had a VIA work fairly well).
The only thing different between the MacBook Pros and a PC laptop is that
you have several PC laptop manufacturers
and models to choose from and find the ones with TI chipsets rather than
something else. MacBooks are
a single model line. Users are stuck with the apparently inferior chipset
until the next line, and only a hope that Apple will
somehow pay attention to the audio community when make the next chipset
decision. If general consumer firewire devices
work fine, there is no reference point to convince them it was a bad
decision. Streaming 16 channels of 96k audio at 1.5ms
latency just isn't on the radar for computer companies (only daw builders
hold that standard for us).
Hey James - regarding the cost of parts issue, it's never been about getting
cheaper parts (for me at least) - it's about getting quality parts for the
same price as inferior parts, or at least getting quality components without
paying an extra premium. However, as you've noted before accurately, there
is a difference between buying parts from Newegg at what amounts to a passed
on bulk price and building your own, vs. buying from Apple, Dell, HP or a
daw builder.
We're paying labor in prebuilt systems, though companies like Dell and Apple
get even better deals on parts than we do from Newegg, so there is a balance
in there. Of course the manufacturers have to make up labor costs in parts
savings in order
to keep costs from killing too much profit, or pushing prices beyond what
the market will bear. Apple's decision to go with that chipset probably had
more to do with price, power rating with their board, and availability for
large quantities, than whether it worked with firewire audio interfaces.
The point is I personally don't like the idea of paying more to get less
quality, but that is the case with many off the shelf computers,
sometimes they are Dells, sometimes Apples, etc - no one is immune. It's
hit or miss when someone else chooses the parts for you and you only have
one option, though, and that's where it really starts to hurt consumers
(esp. audio people like us that don't amount to a blip on the radar for
large companies).
This pretty much kills any consideration for replacing my Vista laptop with
a MacBook, unfortunately. It would have been too expensive to justify at
least for the time being (too many other things to put money into than a
laptop), but it has been a backup plan to get more use out of the laptop
than Vista or Linux would afford (e.g. as a slave comp for VSTi's, etc, not
just an email checker :-).
Regards,
Dedric
> That does not make sense to me. But, a
|
|
|
|
| Re: this may make things easier for you guys with hardware gear [message #91732 is a reply to message #91731] |
Sun, 21 October 2007 21:14 |
DJ
Messages: 1124
Registered: July 2005
|
Senior Member |
|
|
handful of Pro Audio manufactuers
> gear have problems? Maybe the Pro Audio vendors needs to have a bigger
> voice
> in the design process in order to assure a smooth transition..
>
> Chris Ludwig <chrisl@adkproaudio.com> wrote:
>>Hi James,
>>
>>
>>James McCloskey wrote:
>>> This kills me. Some of you guys for years have insisted that Apple
>>> stuff
>>> is no better than cheap PC MOBOs. That they use cheap inferior stuff.
> Some
>>> of you guys have complained about Apple costing more. Some of you guys
> have
>>> said that you want cheaper Apple products. Now Apple is starting to use
>>> cheaper components which will mean lower prices in the future. This is
> what
>>> you guys wanted, cheaper, remember? You can't have it both ways, there
> is
>>> a reality to this.
>>I'm not one of "you guys". I have used Macs and PCs for years. Have
>>built and/or repaired PCs and Apple machines for years.
>>
>>They do not need to use "cheaper" parts to make the prices cheaper.
>>If Apple is going to cut corners like this then their hardware should
>>should be no more than a Dell or E-machine. The fact that they used a un
>
>>tested but cheaper chip instead of the proven to be compatible firewire
>
>>chip set is very lame. Apple have consistently used good quality
>>components over the years the same way some a high-end custom PC maker
>>or a DIY person that wanted to good quality and reliable machine would
>>do. Any of these users main concerns are reliability and compatibility.
>>
>>>
>>> I'm sure RME will get drivers to work with the new chip, it's just a
>>> matter
>>> of time.
>>>
>>
>>Why should RME, MOTU, Presonus, TC, Focusrite, various hard drive
>>makers, etc have to fix it? You would think the company that sells the
>>broken product would fix it? Maybe they can fix it with an OS or
>>firmware update so that hardware developers won't have to develop an
>>specific driver for a malfunctioning hardware that has a limited life
>>span on the market anyways?
>>
>>Chris
>>
>>
>>
>>> Chris Ludwig <chrisl@adkproaudio.com> wrote:
>>>> Nothing more PC like than trying to cut corners on you product than
>>>> using cheaper components. Are Apple going the way of DEll? Let hope
>>>> not.
>>>>
>>>>
>>>> http://www.rme-audio.de/forum/viewtopic.php?id=1475
>>>>
>>>> http://discussions.apple.com/search.jspa?objID=c1&search =Go&q=Agere
>>>>
>>>>
>>>>
>>>> Chris
>>>>
>>>>
>>>> --
>>>> Chris Ludwig
>>>>
>>>> ADK Pro Audio
>>>> (859) 635-5762
>>>> www.adkproaudio.com
>>>> chrisl@adkproaudio.com
>>>
>>
>>--
>>Chris Ludwig
>>
>>ADK Pro Audio
>>(859) 635-5762
>>www.adkproaudio.com
|
|
|
|
Goto Forum:
Current Time: Tue May 05 19:05:05 PDT 2026
Total time taken to generate the page: 0.04856 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
