Advanced Report 6.4 - Updated 24/06/2014
-
- Posts: 1
- Joined: Wed Jun 28, 2006 3:56 pm
Ummm, not really. Maybe you have an artist with a special character as the first digit? Maybe foreign characters?
Download my scripts at my own MediaMonkey fansite.
All the code for my website and scripts is safely backed up immediately and for free using Dropbox.
All the code for my website and scripts is safely backed up immediately and for free using Dropbox.
Same exact error here. #5 Line 477 Col 4.
My first script and I've been looking thinking that I somehow installed it incorrectly - though that would be hard!
Is this definitely an error in an Artist name? If so, I can just scan through them all and see what I find.
I do have one with asian characters, but I am not selecting that track. (This does run omly on selected tracks, correct?)
Thanks.
My first script and I've been looking thinking that I somehow installed it incorrectly - though that would be hard!
Is this definitely an error in an Artist name? If so, I can just scan through them all and see what I find.
I do have one with asian characters, but I am not selecting that track. (This does run omly on selected tracks, correct?)
Thanks.
J-Mac
Oh well...
I went through and either removed all suspect titles, or edited them. This time the script ran all the way through. Yay!
Then when it asked, "Display now?" I clicked on OK and got yet another error message:
Error #-2147023741 - File: "C:\Program Files\MediaMonkey\Scripts\AdvancedReport.vbs", Line: 713, Column: 6
Any thoughts here?
Thanks.[/img]
I went through and either removed all suspect titles, or edited them. This time the script ran all the way through. Yay!
Then when it asked, "Display now?" I clicked on OK and got yet another error message:
Error #-2147023741 - File: "C:\Program Files\MediaMonkey\Scripts\AdvancedReport.vbs", Line: 713, Column: 6
Any thoughts here?
Thanks.[/img]
J-Mac
Line 477 is where the first character of each artist is written to the html file. If there are characters that VBScript can't handle it errors. The next version will be able to handle this better.
Line 713 is just a Run command to open the file. What path did you select? Could you check your MediaMonkey.ini file, the [AdvancedReport] section, and tell the value of the key "Path"?
Line 713 is just a Run command to open the file. What path did you select? Could you check your MediaMonkey.ini file, the [AdvancedReport] section, and tell the value of the key "Path"?
Download my scripts at my own MediaMonkey fansite.
All the code for my website and scripts is safely backed up immediately and for free using Dropbox.
All the code for my website and scripts is safely backed up immediately and for free using Dropbox.
This will be because the track name has non-ascii characters in it. Hopefully the next version will be able to handle Unicode characters, but until then you could replace line 672...... with ...
Code: Select all
fout.WriteLine "<li>"&gettrack(iter2.Item)&"</li>"
Code: Select all
fout.WriteLine "<li>"&SDB.toAscii(gettrack(iter2.Item))&"</li>"
Download my scripts at my own MediaMonkey fansite.
All the code for my website and scripts is safely backed up immediately and for free using Dropbox.
All the code for my website and scripts is safely backed up immediately and for free using Dropbox.
New version (3.8.) is now available from my website. It has many improvements, including...
- Added unicode character support
- Moved all styles and colours to Scripts\report.css
- Added option to group all non-alpha characters
- Added option to only include album artists
- Added option to ignore prefixes when ordering
As always, your feedback is greatly appreciated.
- Added unicode character support
- Moved all styles and colours to Scripts\report.css
- Added option to group all non-alpha characters
- Added option to only include album artists
- Added option to ignore prefixes when ordering
As always, your feedback is greatly appreciated.
Download my scripts at my own MediaMonkey fansite.
All the code for my website and scripts is safely backed up immediately and for free using Dropbox.
All the code for my website and scripts is safely backed up immediately and for free using Dropbox.
-
- Posts: 22
- Joined: Mon Oct 03, 2005 6:58 am
error in 3.8 ?
Hi,
I just upgraded your excellent script from v3.4 to 3.8.
It works fine to create reports but when I click the Edit CSS button I get the error as displayed below.
Is there something wierd my end or....?

I just upgraded your excellent script from v3.4 to 3.8.
It works fine to create reports but when I click the Edit CSS button I get the error as displayed below.
Is there something wierd my end or....?

-
- Posts: 22
- Joined: Mon Oct 03, 2005 6:58 am
suggestions for future versions
1) It would be great to be have a 'to top of document' button after every album listing (actually after every artist listing as well). As it is now, after a few clicks one is deep into the structure and has to use the scroll bar to get to the top and start over to browse to a new artist
2) Perhaps this is implemented already in the Edit CSS function (which I can't access, see previous post), but it would be great to colour code so one can see immediately what kind of info one is watching. Even with my own library I often get a bit confused. And friends often ask me to clarify how to use the index. They get lost after a few clicks it seems. Don't get me wrong, your work is great as it is, but IMHO it would be even better if for instance all artists could be colour coded so one immediately can differentiate artists from albums (which is good if one has never heard of an artist and confuses the band's name with an album or something).
2 bis) Alternatively to the above, perhaps one could generate 3 separate html files: for Artist list, Album list, and Album contents list. That way one could specify different colour backgrounds for each of these files and easily know which view one is currently facing.
3) I would like to be able to create reports for a certain ID3 genre only. I have mainly Jazz, Contemporary pop, and Classical music in my library. And all tracks are given one of these as genre when I tag them. So it would be great to create an index of only the classical music for instance.
4) Perhaps this is too difficult to implement but a framed output would be very nice so I will throw out the suggestion anyway: Scrollable artist list to the left and in the main frame to the right the Album lists which are replaced by the Album contents in the same frame.
Thanks a lot for your work so far!
/p
2) Perhaps this is implemented already in the Edit CSS function (which I can't access, see previous post), but it would be great to colour code so one can see immediately what kind of info one is watching. Even with my own library I often get a bit confused. And friends often ask me to clarify how to use the index. They get lost after a few clicks it seems. Don't get me wrong, your work is great as it is, but IMHO it would be even better if for instance all artists could be colour coded so one immediately can differentiate artists from albums (which is good if one has never heard of an artist and confuses the band's name with an album or something).
2 bis) Alternatively to the above, perhaps one could generate 3 separate html files: for Artist list, Album list, and Album contents list. That way one could specify different colour backgrounds for each of these files and easily know which view one is currently facing.
3) I would like to be able to create reports for a certain ID3 genre only. I have mainly Jazz, Contemporary pop, and Classical music in my library. And all tracks are given one of these as genre when I tag them. So it would be great to create an index of only the classical music for instance.
4) Perhaps this is too difficult to implement but a framed output would be very nice so I will throw out the suggestion anyway: Scrollable artist list to the left and in the main frame to the right the Album lists which are replaced by the Album contents in the same frame.
Thanks a lot for your work so far!
/p
Ooops! The CSS file is not moved into the correct location until you run the script. Therefore you cannot edit the CSS file using this button until you generate the report for the second time! This'll be fixed in the next version.
There are some good ideas there, I'll put them on my todo list!
There are some good ideas there, I'll put them on my todo list!

Download my scripts at my own MediaMonkey fansite.
All the code for my website and scripts is safely backed up immediately and for free using Dropbox.
All the code for my website and scripts is safely backed up immediately and for free using Dropbox.
-
- Posts: 22
- Joined: Mon Oct 03, 2005 6:58 am
Here's another suggestion:
* Possibility to filter the report to only include files of a certain filetype. Would be great when one wants to create a separate list that contains only lossless music in APE or FLAC format.
(Filtering on bitrate would not be as precise and would probably skip some lossless tracks beginning with low bitrates)
* Possibility to filter the report to only include files of a certain filetype. Would be great when one wants to create a separate list that contains only lossless music in APE or FLAC format.
(Filtering on bitrate would not be as precise and would probably skip some lossless tracks beginning with low bitrates)
-
- Posts: 22
- Joined: Mon Oct 03, 2005 6:58 am
Regarding the CSS error:
If the implication of your answer was that I can currently get around this thing by first generating a report and then upon generating another report I could access the Edit CSS function I can report back that this does not work for me anyway.
I open MM and generate a report. That works . I 'enter' Advanced report again and this time when clicking Edit CSS I still get the same error message.
I check in the script directory and the report.css is there.
Could the fault be a different one?
If the implication of your answer was that I can currently get around this thing by first generating a report and then upon generating another report I could access the Edit CSS function I can report back that this does not work for me anyway.
I open MM and generate a report. That works . I 'enter' Advanced report again and this time when clicking Edit CSS I still get the same error message.
I check in the script directory and the report.css is there.
Could the fault be a different one?