Importing disrupting my music

[gd123]

Yes, this happens.

For lack of better phrasing, Hoster is and always has been a processor/memory hog.

When I import, I just walk away from the computer until the import process is finished.

I think, in the past, someone mentioned that it would be nice to have a WAV file attached to alert your attention that the Import process was done. The output of the sound card attached to the input of an amplifier would do nicely, when in another room.

But, how to get the WAV file to play, only at the end of ALL Trks Checked for Import, may be impossible. I wouldn't want to hear the WAV file at the end of each trk imported.

[bryant]

A general rule of thumb in all programs that write onto CD's, DVD's, or importing from them is to close down everything else while it is happening.

And like the man said, walk away.

[George]

Originally Posted by gd123

Yes, this happens.

For lack of better phrasing, Hoster is and always has been a processor/memory hog.

Got curious and checked my CPU usage both during play and import.

During play the CPU usage flatlined out at about 2% usage with an occassional brief spike up to about 4%.

During import the average CPU usage ran an average of 60 to 70% CPU usage and an occassional spike upwards to about 90% and and an occassional downward dip to about 40%.

Imported 8 tracks from a S.C.2092 disc. Total import time for 8 tracks 3:30. Projecting that out, a normal 15 track cdg would import in about 6+ minutes. I shut nothing off from running in the background.

My processor is an Intel P-4 running at about 1600ghz.

Suggest you guys look elsewhere for the problems you're having with CPU drain and slow importing, rather than the software.

[admin]

Thank you George!

I was taken back how someone could say Hoster is a memory hog. We used to be, but we did an extensive checkup and rework and, as you say, we're now in the 2% - 4% range.

As to importing from a CDG disc, our error correction in Hoster 3.316 is the best available in the world! PERIOD! To get that level of quality takes extremely heavy computation. I'm surprised its only 60%-70%. But the results are pristine lyrics without random dot coloration errors.

Even importing track 15 on any Chartbuster's disc, which are the most warped in the world and track 15 is the worst on the disc, and we get very few graphic errors. Comparing the same disc/track importing with other software and the resulting imported file is unusable.


Tricerasoft's Swift Elite has been reported by about 10 of their "ex" users to work the CPU so hard that running it will burn the process up... totally destroy the chip. Now THAT's a processor intensive program!

[Beavis]

what version is he running ???

[George]

Not terribly old, 3.301

[George]

O.K.

I installed 3.316 and ran the same tests.
On play with 3.316 the results were the same.

On importing 8 tracks of S.C.2038, the average CPU usage was just about the same with occassional dips lower that with 3.301, and some spikes higher.

The import time was 3:30 minutes longer(7 minutes), but the total track time being imported was 3:42 longer. Considering what ADMIN said regarding improved error checking, still in the ballpark projecting an average cdg import of 15 tracks in 13+ minutes or so.