![]() |
|
Hoster Help Post Hoster questions, tips and suggestions here. |
![]() |
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
Re: v541.05 - Importing to BIN
Do you understand what it means when files get successfully added to the TRACK LIST WINDOW?
It means that you were successful in DEFINING THE FIELD ORDER. Otherwise, Hoster would NOT have allowed Tracks to be added to the TRACK LIST WINDOW. So, how is it that you ask if I have a Blank character in one of the FIELD SEPARATORS? Why not just follow the instructions on how to duplicate the PROBLEM? Oh, and by the way, the LAST FIELD SEPARATOR to the RIGHT MUST REMAIN BLANK in order for the &this to work correctly with the TRACK LIST WINDOW. That is the POINT. The LAST FIELD SEPARATOR MAY BE USER DEFINED when there is NO need to DEFINE it in the newer version of Hoster. Reason for interacting the LAST SEPARATOR BOX: For instance, Cbe8-01-01 - Artist - Title.bin has a PERIOD at the END of the TITLE but BEFORE BIN, as in TITLEdotBIN. So, TECHNICALLY, there IS another character to define so that Hoster would know the END of what you are DEFINING. The OLD versions of HOSTER 3.3xx versions REQUIRED the FINAL Separator Box to have a PERIOD before Hoster would accept that the DEFINE FIELD ORDER was correct. So, now, the Newer versions of Hoster, actually allows a USER to interact with that BOX and, IF YOU DO, when you click APPLY, Hoster shows the Fields and Separators Window in PINK meaning that you still have not been successful in defining the FIELD ORDER. Now, you have to go back to DEFINE FIELD ORDER to see what is wrong, and, of course, the ONLY thing that is possibly not correct is the PERIOD in the Last Box. Now you simply make that BOX Blank, hit APPLY to return to the IMPORT WINDOW and you will see that the Fields & Separators Box is BLACK, meaning success on DEFINING THE FIELD ORDER. Unfortunately with this &this scenario, if a USER has ALREADY interacted with that LAST SEPARATOR box by SELECTING a PERIOD, and, then, subsequently changes that LAST SEPARATOR Box BACK TO A BLANK, Hoster will malfunction when adding the TITLES to the TRACK LIST WINDOW. Last edited by gd123; April 19th, 2017 at 05:00 PM. |
#2
|
|||
|
|||
Re: v541.05 - Importing to BIN
Hoster automatically removes the extension of any file name (e.g. .mpg, .bin, .zip, etc.) before parsing the fields. Therefore, you do not need to include the period in the final separator field.
Any character in a separator field (including a blank character) will be matched in parsing the file name. This is why only the first word of each song title is appearing. Once it finds the blank character, Hoster stops parsing. Making sure that the final separator field is completely empty will solve your issue. An empty separator field will not match anything, and therefore the entire title will be found and used. |
#3
|
|||
|
|||
Re: v541.05 - Importing to BIN
LOL
You, obviously, don\'t have a clue. So, let\'s say I\'m doing a search on TITLE and I type something where Hoster can\'t find what I typed. Hoster comes back and gives a message to that effect. Then, I type correctly but Hoster comes back and ONLY gives the FIRST WORD of each match. Then, I type a problem in this forum to that effect and: Your \"logic\" is to say I should have typed correctly in the FIRST PLACE. Choosing FIELD SEPARATORS is a USER function. If one gets it wrong, ONE \"experiments\" until Hoster says it is CORRECT. Experimenting, by nature, means to SELECT and RE-SELECT if the \"SELECTION\" is WRONG. Not that, by virtue of a WRONG SELECTION, Hoster malfunctions and doesn\'t RETURN the correct information to the LIST TRACK WINDOW. Get it? |
#4
|
||||
|
||||
Re: v541.05 - Importing to BIN
Dave, I think that what gd123 is trying to point out is that it showed as if it was correct before adding the files, Not in Pink with the message (The selected field does not match). I can confirm that entering a blank space in that last field is what causes the truncated field.
The problem here for Dave the programmer as I see it is, up to that point it does match the field order, there might be a case where you want to enter a blank to define a field as I have in the past although not in that last field, so to make that report back as an error would be a problem if you intentionally entered a space. I think although it might report back as correct you just have to accept that it can be tricked, the final result is seen after pressing the add button before importing so you do still know something is wrong before importing.
__________________
Roy. Test Laptop: Windows 10 Home Premium 64bit. Acer Aspire 5738G Intel core 2 Duo T6600 ATI Graphics 500Mb dedicated. 4Gb Memory 500 Gb SSD Drive. K-lite Mega version 1205 Show Backup: Windows 10 Acer Aspire Touch Screen V15, Intel core i5, Iris Graphics 6100 up to 8277mb dynamic video, 16Gb memory, 1 TB hybrid HDD. K-lite Mega pac. Show Computer: Windows 10, Dell Inspiron 15 7000, CPU I7-855OU, Ram 8GB, Graphics UHD620 + Nvidea GeForce 940MX, Hard Drive SSD 256GB + 1GB internal. |
#5
|
|||
|
|||
Re: v541.05 - Importing to BIN
Roy is correct. Just because Hoster can successfully parse the selected file name and fill in the fields (i.e. not pink) does not mean that the parsing is what you ultimately want.
|
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Display Modes | |
|
|