I've been running 2.1.1 mainly so I could use the 68. It hasn't corrupted anything and runs fairly well. I'd really like to be on a version that works with mp4 like it supposed to. Who's going to go first?

Tonight will be a full trial by fire of 2.3.3+ME 1.7.2.. my fingers are crossed.

i will try it but want to create 2 more backups first.
the other thing is i have to rescan EVERY file before playing out. last time i did that my HD failed.

i know there are plenty of people running 2.3.3 just fine.
this is basically a tip for the community that is happy with 192 but might try the update.

Keep us updated!! IM still on 1.9.2 and ME 1.7.2 lol but it would be interesting to finally get samples and effects :)

for anyone updating i have one big question. this will determine whether i upgrade or not.

is there a lag when loading a video?

in the previous version i would have to wait before manipulating the track or i'd get a blank waveform. waiting 1-3 seconds for a track to fully load is not conducive to how i mix at times.

Sure hope you guys can find something out on this. I would really like to upgrade to a newer version but there is NO WAY I am leaving 1.9.2 Its so stable and runs flawless for me. Why cant Serato just make a version like 1.9.2 where you do not have to scan all your old videos and make a version as good and stable as 1.9.2 There is no way I am going to rescan all my thousands of videos just because some new version wants to. I know we are suppose to move forward but I will be staying where I am for a long time to come unless Serato can get this figured out. I know a ton of other video djs who have tried to upgrade and I see them post that they went back to 1.9.2 after a disaster. You would think Serato would take note of this and realize 1.9.2 was perfect. Why not just add the effects with it and make a version like that. Stop this new rescan for the new version bullcrap. I am with tomatoslice. When I tried I new version a while back it seems like it takes a while to load a new video and it wants to scan it every time. So I just gave up and sticking with 1.9.2

I have had pretty good luck with 2.2 and have not rescanned my videos.

I wish I knew what version it was that if you use itunes for crates and don't initially tag them in itunes and use the files in ssl the tags get messed up in both.
waveforms don't stick, any tagging updates in ssl or itunes does not stay and there isn't a metadata file in ssl that the "data" is being written to.

i upgraded on my pc to see.. i'm getting tons or corrupts... back down i go....

Flawless and my files load fine iv got 0 corrupt files in this version, if you guys are its prob because they are corrupt. But if you do get corrupt files start a help thread and upload them the more corrupt files serato get the more they can improve on stuff. This is by far the best version since 1.9.2 and yes you have to reanalyze the lot but hell they have made big changes to fix problems thats a big bonus. But at the end of the day no one is making you upgrade if 1.9.2 works 100% fine for you why change it?

in 2.3.3? the version just released?

All I can say is my re-scanned set of 90's videos (in 2.3.3) for last night ran flawlessly during the 5 hour set.

This is sort of how it's acting for me, the tags write on eject which makes the next track act weird for a second. It slows what I want to do to a real halt. No corrupt files though.

Thing is, I'm using Serato SL for 6 years so I can pinpoint issues and act accordingly, I'm new on Video-SL and still working out which version acts which way.

sooo EVERY video will do that? rewrite the tags?
if i load a track twice in a row each time it ejects the tags will rewrite?

I noticed the same odd movement during analyzing. Outside of looking different than previous versions I haven't noticed a problem from it.

i hate the rewriting of tags....i believe that if you run all of your videos (as in hooking up your box) once, it won't do it again...or am I wrong?

I am thinking about hooking up my serato box, putting it in auto play and trying out 2.3.3 (after I back it up of course)...

seems a bit ridiculous to rewrite a tag every time a load/unload is happening especially when you have made no changes to the file.

if that is the case, i will not be updating.

don't quote me...but I have been reading all the 2.3.3 threads, it looks like 2.3.3 is the best update in a while, they also seemed to have made it smaller file size wise and somehow carry a smaller load on the computer...sounds all good...I use 1.9.2 for certain gigs, but for mobile I bought an sl2 and I hate using 2.2.2, it makes me nervous, I had a track stop playing midway thru and disappear and then I got the beachball of death....first time it had happened in 2 years and then i restarted it, only to have the next track I play start to have a disappearing wave form, but it ended up working the rest of the night...

I also should mention that it's rearranged and deleted some cue points, very weird. I had set some cue points on a little video mix I was building, and then went to 2.3.3, my cue point 2 had become cuepoint 1 in some instances and in others cues had completely disappeared.

2.3.3 does not ever write tags for me its mega im soooo happy with it its unreal, quote i do not use dj fx but yes there is an issue with them. All there is left to fix is the quicktime crash nik39 has the indepth of that and he is working with glenn from serato to try find a fix.

When ur tags keep writing on eject it normaly means ur database file is corrupt.

In that case does that mean that we have to delete our database file and start fresh? Or can the database file be fixed somehow?

Why and how did the database file became corrupted should be high priority on serato fix list imo

Erm im not 100% you can just rename it, then when u open ssl it will build a new one least then u can test it this is the issue. Then u can always delete it and use ur original database. Its prob best for anyone having issues to open a help thread and go from there.

I use 2.3.3 Last night 4 hour Set i was pissed videos lagging all night mainly in Left deck
i am delete refomat and then Back too 1.9.2

what computer and operating systems are you guys using with 2.3.3

Mainly in left deck?
Sounds like more than ssl.
I would highly encourage you start a help ticket.

Well i already went back to 1.9.2 and all is fine i think ever since 2.0 it has been getting a little jerky Maybe different code writers now well bring back the old guys please then update

Here is an idea. Why not just bring back 1.9.2 with some of the new stuff without having to deal with all this crap in the versions after 1.9.2 Its perfect and that why most of us still keep it after all this time. Do not understand why you guys just don't go back to the way it was designed and runs. I do not want all my files rescanned. There is absolutely no need for this. Maybe stop this from happening in the future updates and just get back to the reason why 1.9.2 runs so perfect. :-)

Are all you guys using 1.9.2 only using vsl or are you using vsl with mix emergency? I've only used mix emergency with 2.1 or 2.2 and haven't had any problems.

i use 2.0 with ME And I don't have any issue as all.. I have 2.3 loaded on the same MBP and I won't use it cause get dropouts

and I STILL wait!

:)

It's gotta be something with the display/update coding side of things. The data path has plenty of headroom for audio and mpeg-4 video streams. I noticed a little jerkiness but nothing that messed up the mixing.

I've never had smooth waveforms....

I haven't had any corrupt mp4s since I upgraded to 2.3.3. I gained back about 200 gigs of free space on my drive after I batch 'save as' all the corrupt mp4s that I had using mpegstreamclip. Had to go back and re-tag them all too which was a pain. I think Serato did good by this new version.

The only problems that I've had playing out seem to come from VSL and not SSL. No disappearing waveforms of drop outs. Just VSL likes to crash sometimes for no reason so hopefully the next version of VSL is better.

I've been doing this lately and like you said it's a pain to tag it all but worth it in the end.
Still have a ton to do, not corrupt files, but ones where no metadata stays stored in the file.
waveforms and bpm rebuild everytime you go to play the file.

i hate that. i still have 100s of ovb and xml files. yes, even from smash.

we're all in the same situation i guess then.

I'm not talking about those.

i have files from certain editors that if you don't tag them first in itunes before loading into ssl then the metadata somehow gets fucked and you can't edit the taggin itunes or SSL, you tag in ssl and it looks like it sticks, but when you go to play that track a week later the waveforms are gone.

See below
www.djpuma.com

The cues are there but now waves, they show up on the fly, but never finish while playing the song.

damn spelling.

damn, never had that odd tag problem...that i know of.

oooh wait, yes i have....but only recently and oddly i only recently started using itunes.
it only occurred on 1-2 videos.

from what i recall they fill slow, even with auto-fill on. it kind of worried me.

^yes exactly
and when you tag them in ssl, they don't stick and when you go to itunes the bpm doesn't show up after being written in SSL, but the kicker is, there are no ovb xml files for those mp4's.

like they just get written into some false metadata storage bucket that no one can see.

someone should make a program that can tag the tags from your xml files and put that into your newly saved mp4 (out of mpegstreamclip)

That's not so difficult...!

Anyway, SL constantly needs to rebuild the overviews while loading the track to the decks.

Also.. could someone please have a look at this SL stress tester script? I can make SL 2.3.3 constantly crash on my machine.

serato.com < click

I've had less problems just using iTunes to tag everything, that seems to be the one consistent thing through all of the updates/upgrades. I just keep a virgin set with just my iTunes tags, copy them over and let SSL scan them and if all comes out ok, keep them on my play drive. My backups will ALWAYS (now) be just the versions fresh from iTunes though.

got this problem with my 2.3.1 :(

hmmm...what if i set my videos to be read only?
would that negate the rewrite of tags after load out?

I used 2.3.3 for 6 hours tonight. I had almost zero problems. I say this because there was one time 2 hours into my set when I went to load an audio drop to a crate and serato froze. The video played fine but serato was frozen. It was one of those moments when your butthole puckers and your looking for the headphone to rca adapter for your iPhone. Then after a minute it goes back to normal and you feel all the adrenaline release from your body. That was the only problem. 2.3 with vsl performed (Near) flawlessly.

I am on osx 10.7.2, 8 gig 1333mhz ram, 750 gig 5200rpm hdd, 17 inch MBP. I used an external hdd via usb, sl1, and midi controller (Djm 700).

what's the cpu?

2.3 core I7

I am now trying 2.3.3 at home. Hate to leave 1.9.2 but its got to happen sometime. Lets hope this new version is stable and works. I will keep you guys updated. I am hardcore 1.9.2 believer but I really want into a newer version.

What sucks about this version is I am losing all the rename of track inside of Serato when the new version does the rescan. Why cant we just have an option to not have this happen???

hahahaha rescanning 18000 vids this shit is gonna take forever....It did come up with about 200 corrupt video files on initial load so I rebuilt those and only about 70 came out corrupt.
Lots for obvious reasons(old 8th edits I havent found a replacement video for and are just too obscure I never really cared to try and replace them)<puts head down in shame.....

there are a few that seem abnormal to me like a couple from smash xtenda,which I think might have something to do with me changing tag info within serato[mainly key info and track color] also a couple cc track which are now totally corrupt I think might have a bit to do with poor encoding on the part of that one editor(Not calling anybody out) that seems to put out more edits in a week than humanly possible and is clearly not as qualified as most of the other editors...
gonna try and re d/l / grab a couple off my back up drive and try and figure out how it went corrupt...

...crashed while reanalizing 4463 vids... guess im gonna have to start all over....

*while=after

Do them in batches so at least you know which set of videos crashed.
Someone else did this as well.

u can also just see where it crashed, then start from there. It works from the top down.

Been running 2.3.3 over new years and Xmas it's very stable, although I had two hard freezes due to a very used HDD with bad sectors. Replaced the HDD with another 500GB one.
For a PC-based DJ, I had issues getting high framerates without sacrificing high-quality output... As I learned with this install, I couldn't see changes I made to video/codec settings before because I didn't completely exit Serato each time I tested. Word to the wise.

-------Fresh install of Win7 64-bit, SL 2.3.3 and VSL 1.2.0---------
Format full HDD, Clean install of Windows 7 64-bit
Installed Serato Video SL (12020) and Scratch Live (2.3.3)
Video output very sharp (high setting) both primary and secondary screens
one deck loaded 60fps; one video playing avg 52fps
two decks, one playing avg 43fps, two videos playing avg 14fps

downloaded ffdshow_rev4096_20111129.exe and
Haali_MatroskaSplitter-16-09-2011.zip from free-codecs (haali's website is down...?)
installed ffdshow then haali splitter, in order, using defaults. Rebooted pc.
Launched Serato, with two videos playing (high setting) avg 59fps. Works like a charm.

yes, do them in batches.

the last version of ssl fkt me.
i did all the analyzing at once.
my hd, that was actually a dual hd with raid0, died. i had not backed it up and lost 2 months of work. from what i could tell the doubling of the size of video files filled the hd and crushed it.
i should have done it in batches. would have caught the problems soon enough to stop it.

also, have a backup.

Im actually doing this from a fresh drive so if it messes anything up I will just reformat and start over...

but yes Im gonna be doing it in batches after 2 more crashes......

@ marx how can yo figure out where it left off?

In your _serato_ folder is a file called overviewbuilder.log.

As long as you've been analysing in an organised fashion (i.e A-Z) you can open that with text editor and see which was the last file it analysed before the crash.

The next one in your crate is the one which crashed it.

thank you!!...I shoulda waited I just went by where the track length meta data started missing

I was so happy when I first found out how to do that. ;-)

Not necessarily. It could be one of the last few files esp if your using a multicore computer - I doubt anyone is still using a single core machine ;)

I can make it reproducably crash on my machine :-(

BTW...

Here is a way how you can stress test the QT decoder in SL

serato.com < click

That's true about the multicore thing Nik39 but at least it gets you in the ballpark.

Correct, I go up a couple files prior.

well after all week of trying to get this scanning b.s done...I got 2500 vids left....crash after crash... the new way of tagging files better be worth it!!! All I want to do is tag the key and genre fields properly without the risk of corrupting the video!!

Thanks Marx! Never knew about this either!! Such a saver :D

serato.com

making the switch... and documenting everything ^^^