Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Dave T]

Are you planning on adding any new fields in V9?  Specifically, I'd really like to be able to add a couple of new views that I had in Siren, which MJ doesn't currently support.  I'd like to be able to view albums by date ripped (to locate music based on when I got it), by play count (to find music I haven't played much, or to see what I have played a lot), and by date last played.

It would also be nice if these fields were stored directly in the MP3 files, so that if I rescanned the database I wouldn't lose the info.

I'm sure there are some other fields that would be useful, that I'm not thinking of right now...

Ok, here's another one: file type (also supported in Siren).

Please??

- Dave

[Matt]

play count, date last played, file type

These are already in version 8.

Version 9 has flexible fielding so you can create anything you like and use them in lists, view schemes, searches, etc.

The default fields for version 9 aren't set yet, but I guess it doesn't matter that much since you can do whatever you want with MJ 9...

Take care.

-Matt

[Dave T]

Sorry, Matt - you lost me.  I'm new to MJ, and I guess I don't know how fields work.  I'm talking about fields that I can create views on.  I don't see those fields as those available for creating a view.  Actually, I don't see play count or date last played under file properties, either.  Am I missing something?  I am on V8...

And, I'm talking about having the fields auto-populate, upon rip/play, etc.  So, are you saying date ripped would auto-populate, but is an optional field?  It doesn't help me if I have to fill in the fields myself - I'm lazy!  Actually, rip date wouldn't be available for stuff I've already ripped, either.  How about just using the date on the file itself?

- Dave

[Matt]

Sorry, I guess those fields are "hidden" in MJ 8. (so you can't use them in views)  That's not the case in MJ 9.

And all fields are stored in your files. (version 8 and 9)  Of course, you need to leave ID3v2 tags enabled for mp3's to support flexible fielding.

Date created and date last modified are both in the MJ 9 database.  Import data may be added as well.  Any other dates you add would have to be entered by hand.

Hope that clears things up and thanks for your help.

-Matt

[Nila]

Pretty please add imported date.
There's no harm in it, and you could even leave it invisible if you wanted but I know me and several other users would LOVE to have it.

No harm in having it

Also, any possibility of a checksum field that MJ automatically keeps a CRC of all mp3's in and that it can use to verify the integrity of the database??

Also, what would be nice is if each mp3/song could be given a unique reference number so that no matter where it was moved to how, what name it was given etc, it could be recognised (on your machine) and reassociated with it's appropriate database info etc.

[Polonio]

And all fields are stored in your files. (version 8 and 9) Of course, you need to leave ID3v2 tags enabled for mp3's to support flexible fielding.

Is this true talking about WMA?

Why did I lose some fileds (artist albumn, for instance) rescaning directories?

Regards,

Polonio

PS: Fortunately, I had a Media Libarary backup...

[JimH]

Polonio,
You may want to synchronize your tags and your filenames.  Check file properties/tools and the two options for this.  Experiment on a few before doing many.

[Galley]

Being able to sort by "date created" would be helpful for finding songs that haven't been backed up to CD-R.

[Michel]

Will V9 support full* ogg tag editing ?

*V8 supports limited ogg tag editing.

[Michel]

Will V9 support full* ogg tag editing ?

For example, to be able to set several identical tag such as many ARTIST tag for the same track.

[Galley]

Even better, I can create a "backed up" custom field, and then enter "yes" when this songs have been backed up on CD-R.

[Michel]

Even better, I can create a "backed up" custom field, and then enter "yes" when this songs have been backed up on CD-R.

It is possible to do it in V8. I am talking about to create many identical tag such as [ARTIST]=elba ramalho
                     [ARTIST]=zé ramalho

for the same track (ogg tagging allows it)

[Mirko]

About custom fields:

They can't be used it view schemes as I think they are not used during filtering. E.g. I used the standardfield "Genre" for "Pictures". And a custom field "Sub-Genre" for "Vacation", "Flowers" and so on. The I created a viewscheme "Genre/Sub-Genre". The treeview is perfect, but the files displayed are not filtered by sub-genre.
If I use the comment-field instead or the sub-genre-field, MJ filters just fine.

Thanks,
Mirko

[Michel]

E.g. I used the standardfield "Genre" for "Pictures". And a custom field "Sub-Genre"

That is the problem: "standard fields" don't exist, it exists only "mp3/id3 standard fields". But there are others audio formats  which have others "standard fields" or even no standard fields at all (ogg for example).

Please, stop thinking only from a mp3/id3 point of view.

[Raistlin2k]

A really nice field to see in v9 would be the "NAME OF STORAGE".

I scanned all my CDs containing MP3s (over 70) into MJ, lovely tools keeps the info about the disc (and requires me to enter it on playback, perfect!) but it gets not shown in the list on the right.

So I changed "Custom1" to "CD", but I have to change Properties of all MP3s after import to MJ, that's not very hard to do, but, HeY, it would be really cool, if tool could show the name of the MP3-CD, eg "MP3-CD 1L"

Another question, has your jump to v9 something to do with release of WMP9:)?

Raist

[Mirko]

That is the problem: "standard fields" don't exist, it exists only "mp3/id3 standard fields". But there are others audio formats which have others "standard fields" or even no standard fields at all (ogg for example).

Please, stop thinking only from a mp3/id3 point of view.

The problem is: Even if these are not standard fields, they supposed to work in views, aren't they? To my knowledge, only the fields existing in previous version of MJ are able to filter correctly in the views. The new ones, e.g. the ones I created manually, don't. And I don't think this is on purpose and even if it is, it should not be :-)