[ddots-l] Problem importing audio on new machine
- From: "Phil Halton" <philhalt@xxxxxxxxxxx>
- To: "ddots-l" <ddots-l@xxxxxxxxxxxxx>
- Date: Thu, 8 Mar 2007 21:52:48 -0500
Hello list,
I just tried importing an MP3 file into sonar on my new laptop with a newly
installed Edirol FA66 firewire interface and got a really screwy result.
Upon browsing to the file I wanted to import, and pressing enter, the
machine immediately locked up and emitted a continuous rapid Stuttering
sound from the internal soundcard. . The machine was hopelessly locked and
I had to Cycle the power switch to get out of it before it blew my internal
soundcard or speakers.
Its not the file(I imported it without problems on my older system). So, I
checked the settings under Global Options > AudioData page. Under import
bit depth, I noticed that the older system has "origional bit depth"
selected and the new machine had "24 bit " selected, so I changed it to
"origional" figuring that was the problem.
Trying again, with the import bit depth setting of "Origional", It happened
again, only it didn't happen instantly as it did the first time--it took
about two seconds for it to go completely Kur floowy.
The only other setting that is different now is the record bit depth, but I
doubt that's the problem(I'm probably wrong these things don't seem to care
what I think). The older machine setting is "16 bit" for record bit depth
and the new machine is "24 bit depth".
I suppose, for the sake of consistancy, I should change that setting to "16
bit" and try again (that way the settings on both machines are identical),
but I'm a little reluctant to hear that grinding sound on a completely
locked up new laptop again.
On the old machine the soundcard is an Echo Indigo cardbus soundcard with
the audio driver bit depth set at 16 bits. on this new machine, the FA66
firewire interface is set at audio driver bit depth of 24. These numbers
correspond to the recording bit depth fields in the audio data pages of the
global options on each machine, although I don't know if thats important or
not in regards this problem.
Any suggestions before I go ahead and do something stupid?
** To leave the list, click on the immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq
Other related posts:
