yes mp4s tagged or set cue/loops will NOT show up in older versions, They have totaly started again on mp4 tags to fix all the issues from the older versions.

2.3.3. work great on my early 2011 17 MBP. I run video SL (and/or ME (well i really on run ME at shows, VSL is just got home use)). "building overviews, bpm, tag editing or any form of meta data writing." all work great. I run os10.6.8,

I am testing 2.3.3 here at home now. Seems to be ok for now. I have been using 1.9.2 since it came out and have not switched because of how stable it is and because of this rescanning issue. Only thing I notice right now is that all the tracks I renamed in Serato itself in the older versions go back to the old way they was before I renamed them in Serato. Not sure if that makes any sense to you guys. LOL Hard to explain.

just spoke with Anthony.
according to him the tagging is not reverse compatible.
meaning new tags will not show.

looks like Ill be riding 1.9.2 a lil bit longer....

due to the type of tagging done that reverse compatibility will most likely be in all new versions of serato.

also, according to Anthony once the mp4s have been rescanned hey should not be doing a rewrite after a load out unless a tag has been changed.
i asked what would occur if the file were locked to be read only and he said that he was not sure but serato would probably still try to rewrite it.
when i update i will be taking about 20-30 videos locked and doing some testing.

also, now that the break has ended it's crunch time for serato so i won't be calling them too much for awhile.

I bet they are busting there butt to get ready for namm.

Yeah I am very curious to see what happens at NAMM this year. Would love to go too. As far as the re tagging tomatoslice does this mean that an ALL NEW version of Serato or Itch? Or something totally different?

i don't quite follow your question, Kos.
maybe my reply was confusing or i said something wrong though.
i probably misused the word "tag"

what i am saying is in the current version of ssl, 2.3.3, the system for cue points does not work with previous versions. a cue placed in 2.3.3 will not be seen in 1.9.2. that's according to Anthony. i am pretty sure it goes for any previous versions as well, like 2.3.3 tags will not be seen in 2.3.1.
from what i gathered it's due to the fix they created.



does that mean for example, in ssl you see an mp4 that has the artist line blank and if you typed in the artist name previously that in the 2.3.3 the artist name is not showing up anymore? basically, the line you typed is gone?

and btw i have no idea how that previous version non-compatibility issue for cues of mp4 in 2.3.3 would affect itch.

frankly, disappearing cues from 233 to 192 would be the least of my worries, especially since i have had cues vanish since day one of vsl.

lol ya what he said wamp

I have never had any problems with 1.9.2 I guess if you make the commitment to the new version I guess thats it. Think I am going to keep two different hard drives. One for new and one for old version. Sounds like to much work to cue point two different hard drives though. UGH.

My main concern at this point is when 2.4 comes out....if it changes again thats a big problem.

It looks looks like 2.3.3 loads and runs smooth (once files are converted). I like how the cues, overviews etc are now stored in a viewable meta data tag.

At this point if I were just worried about myself I would stick to 2.2.2 and wait. Going to 2.3.3 is a big step and at this point I wouldn't take the chance of the meta data format staying the way it is. But I have to worry about more djs then just myself.

Looks like serato is going with the model once you upgrade to a new version you cant go back. Im kinda happy they are going that route, just my personal opinion. @ dj Kos. I could be wrong but i dont remember having to rename (any uncorrupted files) or re set any cue point when i upgraded though any version. But i do set all my cue point live when i play tracks i very rarely go in advance and set up cue points.

So my conclusion for this thread:

Using 2.3.3 prepped files on earlier versions like 2.2.2 or 1.9.2

2.3.3 prepped files really seem to work fine in earlier versions, although I did the majority of the testing on 2.2.0 and 2.2.2. My main concern was what if someone wanted to roll back after not being satisfied with 2.3.3 & was it even possible ie: file corruptions, tags not being read correctly etc.

After hours and hours of testing the good news is if you don't like 2.3.3 you can go back & feel confident that your files will be fine. You actually can go as far as to bring your converted 2.3.3 files back to the way they were before you even upgraded by deleting a couple tags if your really picky ie:

ANALYSISVERSION, AUTGAIN, BEATGRID, MARKERS, MARKERSV2, OVERVIEW, RELVOL & VIDEOASSOCIATION

If you delete the above tags, you have basically brought your files back to a pre 2.3.3 state, but I don't think having these tags populated will hurt or cause any issues if you roll back anyway IMO.

Just a heads up for people thinking about upgrading, but as always backup before upgrading. Personally I wouldn't use 2.3.3, I'm not a fan of the constant writing of tags even after fully analyzing them. Its really random, even if you don't make any changes to the file :-/

This is because when you edited the file in 1.9.2 that information was written to the xml file. No xml in 2.3.3, so its reading the original tag in that file. To test, open one of the files thats giving you a issue in itunes or any meta data reader. I would bet it will read the same thing that 2.3.3 is reading. Sucks & I feel your pain, but your gonna have to deal with it now or later :-/

The good thing is 2.3.3 does read and respect earlier version cue info and loop info. When you scan the files in 2.3.3 it also converts that info to the new format.



Suppose to, but I did catch 2.3.3 doing it many times even when no changes were done & after a file has been fully scanned and prepped.



Yes it will, I actually came across this during my testing because I had mp3tag open at the same time, so the file was locked (basically read only). 2.3.3 did attempt to write to the file, but it of course couldn't save because that file was open in another application. So I would assume if you change to read only your only making 2.3.3 do more work for nothing because its going to keep trying to write info to that file regardless.

Hope that helps

Thankfully this is not the case, check out my explanation 3 posts up :-)

That should not happen. 2.3.3 should still be able to read the XML files. Esp. since a few containers do not support (extended) metadata.


I can confirm this :-( This has been brought up, but.. kind of ignored :-(

I can't think of any other reasons why that would happen.

Looks like a bug to me. Not the first one.

It's not suppose to write XML files anymore right?

It should *always* read XML files if XML files are present.
It should *always* write to XML if XML files are present.

(regardless of the video container format)

It should write to XML if the container format does not support metadata.

So what we really need is a program that can export the xml file to the mp4 metadata IF it can be written. Then it auto delete the xml file. Then re analyze in ssl 2.3.3 and all should be fine then as in the tags would be in the file.

It can. Not so difficult.

But why?

SL should be able to do this.

Even without XML SL does *not* keep the information. (rebuilding overviews for example).

well just might be best to keep meta data in the file incase you move the files ect.

my files in 2.3.3 keep all there info and waveforms.

so you can confirm this happens?
when i spoke to Anthony at first he sounded unsure but then said that once the files are analyzed they should not rewrite unless a change occurs.

oh wait, nm.
you already confirmed it.

because of that rewriting thing i will NOT be upgrading to ANY new version of ssl until it is fixed.

but im not having this rewriting issue but then i deleted the hole metadata folder installed 2.3.3 then analyzed all my files and sorted tags ect as i needed to. maybe this is why im not having these issues???

nik also confirmed on another above post






yes metadata folder is completely empty.

i would definitely start a thread in the help post on that issue.
maybe Anthony was mistaken or maybe it's not supposed to being doing that and you discovered a bug.
either way it should be fixed.

just because a few amount of people speaking up that we do not like this issue does not mean there are not thousands of other people having the same problem.
we are small group that represent a large community.
just because 1, 2 or 3 people mention a bug does not make it a small one.

As said.. Serato is aware of that issue. I don't think it is necessary to report that bug again. But of course... the more people complain - the quicker they will fix it. Hopefully.