Quote:
Originally Posted by northlander
1. bad news i tried playing different songs on hoster 3319 there are still songs that will not play, " track path is missing".
2. What I had to do to get them to play which they do play on 3316 and microstudio is import this file which in my docoments file / my music/ mtu/ songs/ kma.
3. This file is a kma file which i convert over to a bin file by songverter after i do this i import into hoster do a song database and .song will play . so there still seems to be a be a small problem.
|
1. Please post what type of KMA file this is. I'm assuming HDZIP, but we need to know for sure.
1.A. How did you add these songs to the Hoster playlist? Are they KMA files in the Songs database and you used BookID or Brand or Search? Or are the some other format (.zip, MP3+G, .bin, etc.) that you added with the MP3G or CDG, or Audio buttons?
2. I don't understand. Did you do #3 first, and then re-import as indicated in step 2?
3. I don't understand what you are doing here, or maybe why you are doing it. If this is now a .BIN file, and you use the Import Hard Drive Files screen to "import" it as a KMA file, it is already indexed in the Songs Database during the import operation. Why are you rebuilding this database?
Please don't take it wrong as I'm not trying to be argumentative. I'm trying to get the missing details so we can re-create the problem. Without that, we can't say there is or isn't a problem.
QUESTION: Did you try more than one song? If not, please do and report back here 1) what type files (HDZIP, CDCDG, etc.) you are importing, 2) what screen you are using (Import CD Tracks or Import Hard Drive Files), 3) what is the FULL error message you see when it doesn't play?
Can you zip up this "bad file" and post it as an attachment so we can diagnose with it? If you can't add it as an attachment, please email to "sales at mtu dot com", with "Northlander bad file" for the Subject. If we can create the problem, we can solve it.
FYI: We replaced the unzipper code we used in 3.316 and prior with new code that can handle MAX Compression files, which was a very serious problem... now solved. Thus, there is a valid reason (significant code change) why something that works with 3.316, which was very forgiving of bad ZIP files, that won't work with 3.318/3.319. We need the file to find out what we need to work on in the unzipper code.