OK, lets see if I can answer all these. I appreciate your wonderful way of asking for help.
Quote:
Originally Posted by tkelley3
Hello MTU  . I am having a problem importing songs within Hoster 3.303. Hoster is not importing the graphics correctly (I think it's an import speed issue) and so they don't come out "clean". I have over 10,000 songs and I HAD imported them into hoster 3.2xx and they were perfect (graphics display and music). I mean really perfect. No spots or ticks or globs or anything. (Well, yes every once in awhile there would be a small spot but that was RARE.)
|
If you are using a Plextor drive (712, 716 are the better current ones), you should make sure the Hoster Tools menu > CD/DVD Drives Default
"Use Software Decode" is clicked OFF. Then, it will use the superior error correction that the Plextor drive provides in hardware. If you are using ANY OTHER Brand drive, you
WILL get "snowflakes" with Chartbuster discs. Their mastering process (not so much the media we don't think) creates 3 or more errors per sector, which is darn near impossible to repair on the fly in real time on even 3GHz processors... and the software code doesn't exist to fix them.
Quote:
Originally Posted by tkelley3
Hoster 3.303 did import all the disks but the quality of the import is very suspect. There is no disk speed control that I see and so Hoster just imported at its top speed. Well, Chartbusters (just to mention one company) uses cheaper disks and they need to be imported at a slower speed (this is a good idea with all KJ disks as the interleave and wobble is minimized at slower speeds).
|
We are working on Hoster 3.310 that SHOULD (no promises) restore the ability to control the read speed. Yes, it DID used to be a selectable option in the past. 3.310 will be out... when we release it. Watch the
http://www.mtu.com or
http://www.mtu.com/support/news.htm pages for the announcement.
Quote:
Originally Posted by tkelley3
Many of the newly imported tracks (not just the last one) had so many spots that the song became unrecognizable as it played. This is a very disappointing update of Hoster in this ONE respect. I love the program and I did love the way it input the music and graphics. This really does need to be fixed.
|
Yep, Chartbusters is incredibly bad. I suspect they are intentionally doing this to PREVENT importing them into a computer. Call and complain to them. They either will clean up their act, or no one will be using their discs and songs withint many months.
There is no excuse for a professional producer to do this poor a mastering/production job.... IMHO.
Quote:
Originally Posted by tkelley3
 What did I do? Well since I had already upgraded, I copied ALL 10,000 songs into Microstudio and imported them into Hoster and that cleaned up the problems. Of course Microstudio has an option to slow down the import process to fix wobble among other things. (Not all companies are using 48 or 52 speed disks…duh.) Please fix Hoster so that we can import disks (poor manufactures copies) at a slower speed if we want to.
|
Argh... 10,000!!!

We are working on it now...

You clearly are now the import expert... and have the patience of Job!
Quote:
Originally Posted by tkelley3
 While I am at it, I noticed that you must now insert the disk into the burner (mine is a Plextor PS-708UF and my other one is a Plextor PS-716UF) before you click on import. Very annoying as BEFORE the disk would slide in if the door was open and you clicked on import. Please fix that also and put it back the way it was. Remember, I absolutely LOVE Hoster and would not think of EVER doing a KJ show without it ever again. I know you have lots of programming experience and have been in this business for many years. I am guessing this just got lost in the shuffle of the new updates.
|
Hummm. From subsequent posts (now above mine), it appears you are referring to importing tracks from a Singer's disc using the CDG button. I'll note this to be reviewed. We did have a problem as DDouglas indicated, and this might have been part of the fix. Our new 3.310 may overcome the "bug" that required fixing. We'll look at it. Thanks for asking.
