Serato Video General Discussion
Finally did a comparison of Vsl to Vdj
Talk about Serato Video and Video-SL.
Finally did a comparison of Vsl to Vdj
jonnie_Spinns
1:40 AM - 18 March, 2009
We (the program director at the club i work at and i) finally did a side by side comparison of Vsl and Vdj. We noticed that the video quality between vob and mp4, the vob is obviously better. We also noticed that with the vob file the audio was much fuller and concluded that to run vsl we would have to run the rig much louder than we do (head room on the system is no issue) normally with the water sacks (humans) in the room.
we found the mp4's to be very granny (lines in the video we very noticeable as we run 19 tv in high def, and 5 projo's in component)
The question we have is, why did serato choose to go with mp4 support vs. vob when there is a less than 10% difference in the file size, when the quality of the video is much better as well as the audio quality is higher?
we are posting this question to gain some feedback as we are reluctant to switch over our current (and primary) video program to vsl due to these quality differences.
we found the mp4's to be very granny (lines in the video we very noticeable as we run 19 tv in high def, and 5 projo's in component)
The question we have is, why did serato choose to go with mp4 support vs. vob when there is a less than 10% difference in the file size, when the quality of the video is much better as well as the audio quality is higher?
we are posting this question to gain some feedback as we are reluctant to switch over our current (and primary) video program to vsl due to these quality differences.
VJ Justin Allen
2:00 AM - 18 March, 2009
I am not surprised at your findings. Others will now come on and attack the way you compressed your files so it's not a true test but the fact is, your results are 100% accurate.
One of the issues however is it takes more overhead to run an MPEG2 file than a files that has more (and different) compression. There may also be licensing fees involved (not sure about that with Serato)
I think it's a mistake, but I am in the minority.
One of the issues however is it takes more overhead to run an MPEG2 file than a files that has more (and different) compression. There may also be licensing fees involved (not sure about that with Serato)
I think it's a mistake, but I am in the minority.
DJ-Phat-AL
2:00 AM - 18 March, 2009
I used VDJ for over 4 years. When Serato's VSL was release I bought it and did similar comparisons. It took a several months to finally do a complete switch over to VSL. I did a quality comparison as well. Yes VOB files do look better... BUT... if encoded right... MP4 video files look just as good.
Here are 2 main reasons surrounding the MP4 in my opinion why I did the switch:
1) smaller files. can fit several thousand on an 500gb external drive.
2) VSL supports tagging of MP4 and VDJ doesn't!! I was a beta tester and VIP member of VDJ and ALWAYS gave constructive input surrounding improvements. I suggested this added feature over a year ago and they kept dismissing me saying it wasn't important. Well now I can put any fields I want using an MP3 Tagging program like Tag&Rename and have it appear in VSL as soon as you load it into a crate. Important things like BPM will be up and ready. You don't HAVE to scan each file to get that info. If you are particular about tagging like I am then you could appreciate the ability to add info like album, genre, comments, version, etc.. and being able to edit them in batches using Tag&Rename.
Other reasons for switching where because of reliability factor. Simple plug-n-play using a MacBook Pro laptop. I had several config problems with VDJ when using my PC laptop. When VDJ is used with a custom built desktop PC it works GREAT! .. but how portable is that when you do like me and work several spots and tend to travel a bit.
there is lounge here in Vegas that Andrew B works at called V-Bar. In the DJ booth they have a Mac Pro built into the DJ booth. You just bring your external and hook it up and that's it. Solid!
Reason I mention that is if you guys have this a residency somewhere and have a computer permanent install in the booth then get a MacPro. I almost guarantee that most good pro DJ's would be using Serato instead of VDJ.
If you did a poll... you would find that there are several EX-VDJ users here who waited for Serato to release a solid version of the video plug-in. I being one of them. Only reason I was using VDJ was for ability to do video.
Now with Serato having the release of ver. 1.1. .. you would be able to use the SL-1 soundcard and ANY midi device/DJ mixer to run video. That was one thing I did like about VDJ... but that just eliminated that argument now didn't it.
Here are 2 main reasons surrounding the MP4 in my opinion why I did the switch:
1) smaller files. can fit several thousand on an 500gb external drive.
2) VSL supports tagging of MP4 and VDJ doesn't!! I was a beta tester and VIP member of VDJ and ALWAYS gave constructive input surrounding improvements. I suggested this added feature over a year ago and they kept dismissing me saying it wasn't important. Well now I can put any fields I want using an MP3 Tagging program like Tag&Rename and have it appear in VSL as soon as you load it into a crate. Important things like BPM will be up and ready. You don't HAVE to scan each file to get that info. If you are particular about tagging like I am then you could appreciate the ability to add info like album, genre, comments, version, etc.. and being able to edit them in batches using Tag&Rename.
Other reasons for switching where because of reliability factor. Simple plug-n-play using a MacBook Pro laptop. I had several config problems with VDJ when using my PC laptop. When VDJ is used with a custom built desktop PC it works GREAT! .. but how portable is that when you do like me and work several spots and tend to travel a bit.
there is lounge here in Vegas that Andrew B works at called V-Bar. In the DJ booth they have a Mac Pro built into the DJ booth. You just bring your external and hook it up and that's it. Solid!
Reason I mention that is if you guys have this a residency somewhere and have a computer permanent install in the booth then get a MacPro. I almost guarantee that most good pro DJ's would be using Serato instead of VDJ.
If you did a poll... you would find that there are several EX-VDJ users here who waited for Serato to release a solid version of the video plug-in. I being one of them. Only reason I was using VDJ was for ability to do video.
Now with Serato having the release of ver. 1.1. .. you would be able to use the SL-1 soundcard and ANY midi device/DJ mixer to run video. That was one thing I did like about VDJ... but that just eliminated that argument now didn't it.
a-swift
4:25 AM - 18 March, 2009
One of the issues however is it takes more overhead to run an MPEG2 file than a files that has more (and different) compression. There may also be licensing fees involved (not sure about that with Serato)
I think it's a mistake, but I am in the minority.
i think you got this one backwards. it takes a fraction of the computing resources to decode MPEG2 than it does to decode an H.264 mp4 of equal size.
I think I have a 700Mhz Pentium that can decode MPEG2.
Quote:
I am not surprised at your findings. Others will now come on and attack the way you compressed your files so it's not a true test but the fact is, your results are 100% accurate.One of the issues however is it takes more overhead to run an MPEG2 file than a files that has more (and different) compression. There may also be licensing fees involved (not sure about that with Serato)
I think it's a mistake, but I am in the minority.
i think you got this one backwards. it takes a fraction of the computing resources to decode MPEG2 than it does to decode an H.264 mp4 of equal size.
I think I have a 700Mhz Pentium that can decode MPEG2.
djnak
5:21 AM - 18 March, 2009
we found the mp4's to be very granny (lines in the video we very noticeable as we run 19 tv in high def, and 5 projo's in component)
were the mp4 ripped from the same vobs what settings did you use to encode them?
Can hardly say it was a true side by side comparison. I personally notice very little if any quality diffrence between a vob and the mp4 that I ripped from that same vob
And yes I do own vdj tried it for a while and if this is the spinns I think it was I even had high hopes for seeing as it was being used at your spot(in the mall right?) but I could not for the life of me get the timecode to work flawlessly (almost on the powerhouse desktop but still to this day I wouldnt trust it to do a five hour straight set of video) and I was being cheap cause I already had the sl1
Then I went with vsl route(not the cheap way compared to vdj)
Left the store went home installed vsl and blam no issues no little lags after a while of using it my cpu stay in a normal range It runs...Flawlessly and I like I said I really dont notice much diffrence from vob or mp4s that have been encoded properly
Quote:
we found the mp4's to be very granny (lines in the video we very noticeable as we run 19 tv in high def, and 5 projo's in component)
were the mp4 ripped from the same vobs what settings did you use to encode them?
Can hardly say it was a true side by side comparison. I personally notice very little if any quality diffrence between a vob and the mp4 that I ripped from that same vob
And yes I do own vdj tried it for a while and if this is the spinns I think it was I even had high hopes for seeing as it was being used at your spot(in the mall right?) but I could not for the life of me get the timecode to work flawlessly (almost on the powerhouse desktop but still to this day I wouldnt trust it to do a five hour straight set of video) and I was being cheap cause I already had the sl1
Then I went with vsl route(not the cheap way compared to vdj)
Left the store went home installed vsl and blam no issues no little lags after a while of using it my cpu stay in a normal range It runs...Flawlessly and I like I said I really dont notice much diffrence from vob or mp4s that have been encoded properly
nik39
7:39 AM - 18 March, 2009
1st. of all mp4 is a container format. The audio and video inside an mp4 can be encoded in various formats. (Let's assume you are using h264 and aac.)
2nd. per se, vob/MPEG2 is not better or worse than mp4 when it comes to quality.
3rd. obviously it all depends very much on the source material as well as the encoding parameters you go with. Depending on that your mileage will vary.
If done right the difference between MPEG2 and an transcoded mp4 file (done right!) should be almost not noticable (if at all). If you're MPEG's are at 29.97 fps (and they were originally at 24fps, so called pulled-up videos) you will experience "interlacing" artifacts on this material. You can get rid of these artifacts and improve the video quality a lot if you IVTC your videos. If you compare some of the encodes from the smashvidz-video service for example compared to the same MPEG2-videos from normal DVD's, you should see that mp4's can look a lot better.
Were you playing your mp4's in VSL or in VDJ?
A tip:
1. If you want to compare VSL vs. VDJ you have to use the same videos (same files) in both programs
2. If you want to compare mp4 vs. MPEG2/vob you have to use the same program when playing different videos (they should be encoded using the same source and preferrably using "similar" settings).
You can't do a comparison if you are changing the app and the files in the same round.
I think it's a mistake, but I am in the minority.
Yes, it is a mistake, and you have been told several times. This is wrong.
MPEG2-decoding produces less CPU load than h.264/divx/xvid (commonly used with mp4).
Quote:
We noticed that the video quality between vob and mp4, the vob is obviously better. We also noticed that with the vob file the audio was much fuller and concluded that to run vsl we would have to run the rig much louder than we do (head room on the system is no issue) normally with the water sacks (humans) in the room.1st. of all mp4 is a container format. The audio and video inside an mp4 can be encoded in various formats. (Let's assume you are using h264 and aac.)
2nd. per se, vob/MPEG2 is not better or worse than mp4 when it comes to quality.
3rd. obviously it all depends very much on the source material as well as the encoding parameters you go with. Depending on that your mileage will vary.
If done right the difference between MPEG2 and an transcoded mp4 file (done right!) should be almost not noticable (if at all). If you're MPEG's are at 29.97 fps (and they were originally at 24fps, so called pulled-up videos) you will experience "interlacing" artifacts on this material. You can get rid of these artifacts and improve the video quality a lot if you IVTC your videos. If you compare some of the encodes from the smashvidz-video service for example compared to the same MPEG2-videos from normal DVD's, you should see that mp4's can look a lot better.
Quote:
we found the mp4's to be very granny (lines in the video we very noticeable as we run 19 tv in high def, and 5 projo's in component)Were you playing your mp4's in VSL or in VDJ?
A tip:
1. If you want to compare VSL vs. VDJ you have to use the same videos (same files) in both programs
2. If you want to compare mp4 vs. MPEG2/vob you have to use the same program when playing different videos (they should be encoded using the same source and preferrably using "similar" settings).
You can't do a comparison if you are changing the app and the files in the same round.
Quote:
One of the issues however is it takes more overhead to run an MPEG2 file than a files that has more (and different) compression. There may also be licensing fees involved (not sure about that with Serato)I think it's a mistake, but I am in the minority.
Yes, it is a mistake, and you have been told several times. This is wrong.
MPEG2-decoding produces less CPU load than h.264/divx/xvid (commonly used with mp4).
VJ Justin Allen
10:48 AM - 18 March, 2009
MPEG2-decoding produces less CPU load than h.264/divx/xvid (commonly used with mp4).
Absolutely wrong guys. It ALL has to do with your graphics card that you have and the system that you run. NONE of the Apple systems have an MPEG2 decoder chip in their graphic cards, but there are H.264 accelerators in them. SOME PC's have an MPEG2 chip on-board, and they also have H.264 accelerators as well.
Apple is also working on 100% hardware assistance with h.264 encoding/decoding. Currently Apple using 100% software decoding for their MPEG2 decoding.
If you have a system that is showing MPEG2 load being less than H.264 then you have a decoder chip that you are using. And then, of course, your CPU shows less work because the MPEG2 chip is doing all of the work.
Quote:
MPEG2-decoding produces less CPU load than h.264/divx/xvid (commonly used with mp4).
Absolutely wrong guys. It ALL has to do with your graphics card that you have and the system that you run. NONE of the Apple systems have an MPEG2 decoder chip in their graphic cards, but there are H.264 accelerators in them. SOME PC's have an MPEG2 chip on-board, and they also have H.264 accelerators as well.
Apple is also working on 100% hardware assistance with h.264 encoding/decoding. Currently Apple using 100% software decoding for their MPEG2 decoding.
If you have a system that is showing MPEG2 load being less than H.264 then you have a decoder chip that you are using. And then, of course, your CPU shows less work because the MPEG2 chip is doing all of the work.
nik39
10:52 AM - 18 March, 2009
*sigh* You do have no clue. At first reading your ridiculously wrong statements was funny, since they were so off. But now, this is getting boring.
Quote:
If you have a system that is showing MPEG2 load being less than H.264 then you have a decoder chip that you are using. And then, of course, your CPU shows less work because the MPEG2 chip is doing all of the work.*sigh* You do have no clue. At first reading your ridiculously wrong statements was funny, since they were so off. But now, this is getting boring.
DJ-Phat-AL
11:21 AM - 18 March, 2009
Justin is wrong on the MPEG2 decoding.
nik is right.
google it.
nik is right.
google it.
VJ Justin Allen
11:39 AM - 18 March, 2009
Phat-Al please do not get caught up in Nik's pathetic attempts to understand video Read this article
www.pbs.org
www.pbs.org
nik39
11:41 AM - 18 March, 2009
I expect Phat-Al to be able to educate himself, he doesn't need me to tell him what's correct and what's false.
VJ Justin Allen
11:44 AM - 18 March, 2009
Oh and here is a link to the Apple MPEG-2 tech specs page. Notice how it says that PC can use a hardware component but nothing for the mac side.
www.apple.com
www.apple.com
nik39
11:56 AM - 18 March, 2009
www.pbs.org
The author is wrong about two things:
As a-swift has posted... you don't need a fast computer to playback DVD's.
No, not at all, Mr Robert Cringely. I read that master piece of tech-talk before... VJ Austin posted it before you did :) To be fair, Mr Cringely, I have to say, that your article is not that bad at all, but it is just that some people do not understand what you are talking about.
www.apple.com
I'll leave that to someone else to comment. Since you officially ignore understanding the most simple tech talk, I don't think that it will help us or lead us anywhere if I explain it to you. You bore me.
Quote:
Phat-Al please do not get caught up in Nik's pathetic attempts to understand video Read this articlewww.pbs.org
The author is wrong about two things:
Quote:
Maybe you have wondered, as I have, why it takes a pretty robust notebook computer to play DVD videosAs a-swift has posted... you don't need a fast computer to playback DVD's.
Quote:
Remember, you read it here first.No, not at all, Mr Robert Cringely. I read that master piece of tech-talk before... VJ Austin posted it before you did :) To be fair, Mr Cringely, I have to say, that your article is not that bad at all, but it is just that some people do not understand what you are talking about.
Quote:
Oh and here is a link to the Apple MPEG-2 tech specs page. Notice how it says that PC can use a hardware component but nothing for the mac side.www.apple.com
I'll leave that to someone else to comment. Since you officially ignore understanding the most simple tech talk, I don't think that it will help us or lead us anywhere if I explain it to you. You bore me.
VJ Justin Allen
12:12 PM - 18 March, 2009
Wow Nik, you don't think anyone but you is right...now I understand everything.
nik39
12:14 PM - 18 March, 2009
Sorry, but there is no hope.
Quote:
I'll leave that to someone else to comment.Quote:
You bore me.
VJ Justin Allen
12:41 PM - 18 March, 2009
lmaorofl now you are making up quotes. At least I have my entertainment for the day, thanks.
nik39
12:46 PM - 18 March, 2009
You should open your eyes. That helps, esp. when you are reading. :)
DJ-Phat-AL
3:10 PM - 18 March, 2009
am I gonna have separate you two?
... thread jacking with these fights and bickering back and forth...
... thread jacking with these fights and bickering back and forth...
Millz
3:29 PM - 18 March, 2009
Id gladly pay apple $3500+ on March 6th for a MBP today :@. (Arrival Mar 27th)...while Im in Miami. blah
When I used VDJ, the videos did look better, regardless of what any of you say :P
When I used VDJ, the videos did look better, regardless of what any of you say :P
D-Twizzle
3:31 PM - 18 March, 2009
i have to agree that h.264 decoding is more cpu intensive than mpeg2 decoding. this makes obvious sense to me.
a-swift
3:39 PM - 18 March, 2009
vi Justin Allen is wrong. No question about it. He has no clue on this stuff. H.264 is a better looking codec than MPEG2 at the same bitrate. Hell, it's pretty close to being better at half the bitrate. Encode some original source material to both and see for yourself.
He is absolutely wrong also about MPEG2 using more CPU to decode than H.264. That one alone shows how clueless Justin is. I'll post a clip demonstrating this and wait for Justin's response.
Justin, if you are clueless on these things, you shouldn't pretend that you know what you are talking about. nik39, like him or hate him, is a lot more knowledgable on the technical details of video formats,.. A lot more than most people on this forum.
He is absolutely wrong also about MPEG2 using more CPU to decode than H.264. That one alone shows how clueless Justin is. I'll post a clip demonstrating this and wait for Justin's response.
Justin, if you are clueless on these things, you shouldn't pretend that you know what you are talking about. nik39, like him or hate him, is a lot more knowledgable on the technical details of video formats,.. A lot more than most people on this forum.
VJ Justin Allen
4:16 PM - 18 March, 2009
A-swift just because you are friends with Nik, do not make yourself out to be the idiot here. Not only do I stand behind what I say BUT have provided external links to others who say the same thing.
I expect Nik to be an idiot, but I do not expect the same from you.
AND on the issue of MPEG2 vs H.264, I agree 100% that you can get better looking images from H.264 than from MPEG2 IF YOU START WITH THE UNCOMPRESSED IMAGE FIRST.
What you and these other idiots do not see is that you are NOT starting with that, you are starting with an already compressed MPEG2 image and then compressing it some more.
You cannot argue that you end up with a better picture from that process, it is flat out impossible.
I expect Nik to be an idiot, but I do not expect the same from you.
AND on the issue of MPEG2 vs H.264, I agree 100% that you can get better looking images from H.264 than from MPEG2 IF YOU START WITH THE UNCOMPRESSED IMAGE FIRST.
What you and these other idiots do not see is that you are NOT starting with that, you are starting with an already compressed MPEG2 image and then compressing it some more.
You cannot argue that you end up with a better picture from that process, it is flat out impossible.
VJ Justin Allen
4:17 PM - 18 March, 2009
I know that you and Nik want to be the "big boys" around here, but this is not the way to go about it.
a-swift
4:29 PM - 18 March, 2009
Ok, justin posts something that is correct. You can't re-encode an already compressed MPEG2 and expect it to look as good as the mpeg2. It's impossible. This is correct
You are incorrect that nik39 and I are friends. If I think he's wrong on something, I point it out and he does the same to me.
No, I do not know everything but what I know for certain is MPEG2 uses less CPU to decode than h.264.
You are incorrect that nik39 and I are friends. If I think he's wrong on something, I point it out and he does the same to me.
No, I do not know everything but what I know for certain is MPEG2 uses less CPU to decode than h.264.
nik39
4:34 PM - 18 March, 2009
It's not about standing behind your words, it's that you are wrong. External links... So you posted ONE link, which does not even explicitly say that MPEG2 uses more ressources than h264.
No. This is not about re-encoding.
Quote:
Not only do I stand behind what I say BUT have provided external links to others who say the same thing.It's not about standing behind your words, it's that you are wrong. External links... So you posted ONE link, which does not even explicitly say that MPEG2 uses more ressources than h264.
Quote:
What you and these other idiots do not see is that you are NOT starting with that, you are starting with an already compressed MPEG2 image and then compressing it some more.No. This is not about re-encoding.
a-swift
4:34 PM - 18 March, 2009
I could really care less about being a "big boy" around here. But I can't stand to see someone post something incorrect and state it as fact. If you interpret that as me trying to elevate my status then, so be it. Honestly though, I could care less. People respect my opinions because of past contributions. Period.
Quote:
I know that you and Nik want to be the "big boys" around here, but this is not the way to go about it.I could really care less about being a "big boy" around here. But I can't stand to see someone post something incorrect and state it as fact. If you interpret that as me trying to elevate my status then, so be it. Honestly though, I could care less. People respect my opinions because of past contributions. Period.
VJ Justin Allen
4:58 PM - 18 March, 2009
Here is what you guys are talking about I think. I did some more research and looked at much smaller bitrates that the typical DJ may use on their computer.
Decoding a H.264 video takes much more work than with MPEG-2. Yes, I am changing my stance, but not the facts. Using highly encoded movies this is absolutely true. Usually dedicated H.264 decoding hardware is required in standalone BD and HDDVD players, as a generic processor just isn't enough to handle the work load, just like with MPEG2. This is understandable as we have to make a tradeoff between file size/bitrate and the amount of work a CPU needs to do to reproduce the video, and H.264 produces very small files.
Basically in a laptop however the MPEG2 playback has been handled from a dedicated chip. Today (and for the last 2 years) Apple has used the CPU for H.264. Now, Apple is moving to a dedicated chip for H.264 in order to offload that processor intensive workload from the CPU.
Here is the bottom line. At the relativelly small file sizes that we, as VJ's, use and knowing that we are not getting any material form the source and just using already compressed MPEG2 footage, it is almost a wash on the Apple. PC's have more graphic cards available to them for MPEG2 decoding, so in essence H.264 DOES TAKE MORE CPU to decode it because there are no hardware decoders on board. When storing less data through compression, the CPU must do work to fill in the blanks before sending the video out to a display. We also see a much lower CPU utilization with MPEG-2 because it doesn't compress the video as much as H.264.
But once again, this gets washed out because of the transcoding and the low bitrate, and then the addition on MPEG chips on graphic cards.
In this part of the thread both of us were right, and both of us were wrong.
Decoding a H.264 video takes much more work than with MPEG-2. Yes, I am changing my stance, but not the facts. Using highly encoded movies this is absolutely true. Usually dedicated H.264 decoding hardware is required in standalone BD and HDDVD players, as a generic processor just isn't enough to handle the work load, just like with MPEG2. This is understandable as we have to make a tradeoff between file size/bitrate and the amount of work a CPU needs to do to reproduce the video, and H.264 produces very small files.
Basically in a laptop however the MPEG2 playback has been handled from a dedicated chip. Today (and for the last 2 years) Apple has used the CPU for H.264. Now, Apple is moving to a dedicated chip for H.264 in order to offload that processor intensive workload from the CPU.
Here is the bottom line. At the relativelly small file sizes that we, as VJ's, use and knowing that we are not getting any material form the source and just using already compressed MPEG2 footage, it is almost a wash on the Apple. PC's have more graphic cards available to them for MPEG2 decoding, so in essence H.264 DOES TAKE MORE CPU to decode it because there are no hardware decoders on board. When storing less data through compression, the CPU must do work to fill in the blanks before sending the video out to a display. We also see a much lower CPU utilization with MPEG-2 because it doesn't compress the video as much as H.264.
But once again, this gets washed out because of the transcoding and the low bitrate, and then the addition on MPEG chips on graphic cards.
In this part of the thread both of us were right, and both of us were wrong.
nik39
5:52 PM - 18 March, 2009
Thank god, and I thought all hope is lost.
So what?
lol, and hope is lost again.
Nope. You changed your opinion and are partly right now.
Quote:
Decoding a H.264 video takes much more work than with MPEG-2. Yes, I am changing my stanceThank god, and I thought all hope is lost.
Quote:
Basically in a laptop however the MPEG2 playback has been handled from a dedicated chip. Today (and for the last 2 years) Apple has used the CPU for H.264. Now, Apple is moving to a dedicated chip for H.264 in order to offload that processor intensive workload from the CPU.So what?
Quote:
When storing less data through compression, the CPU must do work to fill in the blanks before sending the video out to a display.lol, and hope is lost again.
Quote:
But once again, this gets washed out because of the transcoding and the low bitrate, and then the addition on MPEG chips on graphic cards. [blabla] In this part of the thread both of us were right, and both of us were wrong.Nope. You changed your opinion and are partly right now.
VJ Justin Allen
6:12 PM - 18 March, 2009
I'm puzzled now Nik...what do you think the CPU doing if not filling in the blanks? Perhaps I should have called them "slices" which is what H.264 uses instead of I, B and P pictures. This is the reason that it is more CPU intensive.
Funkytownstopsix
6:44 PM - 18 March, 2009
Im a rookie whos right so I don't have to search for the answer..Sup EYE357 may the Cowboys beat the Giants ASS....
nik39
7:42 PM - 18 March, 2009
No.
Quote:
I'm puzzled now Nik...what do you think the CPU doing if not filling in the blanks? Perhaps I should have called them "slices" which is what H.264 uses instead of I, B and P pictures. This is the reason that it is more CPU intensive.No.
VJ Justin Allen
8:08 PM - 18 March, 2009
No what? No, that's not the reason H.264 is more intensive?
If not, please tell me why?
If not, please tell me why?
Millz
9:06 PM - 18 March, 2009
Kaskade - Step 1 2 (Jack Millz WMC 09 Edit) :) listen to happy music, let it take u to a happy place...."yall just getup and dance...yeaaaaaaaaaaaahhhhh" -Afrika Bambaataa
nik39
9:17 PM - 18 March, 2009
Yes.
No. Explaining it to you is a waste of time, and I was really patient but I already wasted enough time.
Quote:
No what? No, that's not the reason H.264 is more intensive?Yes.
Quote:
If not, please tell me why?No. Explaining it to you is a waste of time, and I was really patient but I already wasted enough time.
VJ Justin Allen
9:27 PM - 18 March, 2009
Nik, since you still do not know what you are talking about, please visit the wiki link I have supplied. It will tell you all about WHY H.264 uses slices to fill in the missing data so that you have an entire picture.
Of course you may not understand it. still.
en.wikipedia.org
Of course you may not understand it. still.
en.wikipedia.org
ChrisD
9:34 PM - 18 March, 2009
VJ Justin Allen,
Once again you're resorting to personal insults in your comments. They're not welcome here.
Consider yourself warned.
Once again you're resorting to personal insults in your comments. They're not welcome here.
Consider yourself warned.
nik39
9:46 PM - 18 March, 2009
That's not what you said.
You said:
What you wrote makes no sense at all.
I didn't know that h264 was breaking down the picture into slices which can have different types of prediction, but that is not the issue here.
Quote:
Nik, since you still do not know what you are talking about, please visit the wiki link I have supplied. It will tell you all about WHY H.264 uses slices to fill in the missing data so that you have an entire picture.That's not what you said.
You said:
Quote:
H.264 DOES TAKE MORE CPU to decode it because there are no hardware decoders on board. When storing less data through compression, the CPU must do work to fill in the blanks before sending the video out to a display.What you wrote makes no sense at all.
I didn't know that h264 was breaking down the picture into slices which can have different types of prediction, but that is not the issue here.
eye357
9:51 PM - 18 March, 2009
ChrisD any relation to ChuckD from P.E. lol. that was too easy sorry
nik39
9:57 PM - 18 March, 2009
Just to clarify, VJ Justin Allen, in the other thread you were explaining why you were taking stabs at me. Different case. In this thread HERE you have called a-swift and "others" idiots. I can't remember a-swift ever going into personal attacks, (neither in this thread, nor in any other).
Quote:
Please see my previous answer to you ChrisJust to clarify, VJ Justin Allen, in the other thread you were explaining why you were taking stabs at me. Different case. In this thread HERE you have called a-swift and "others" idiots. I can't remember a-swift ever going into personal attacks, (neither in this thread, nor in any other).
a-swift
10:02 PM - 18 March, 2009
i kinda chuckled at being called an idiot by vj justin allen. seriously. then i considered posting a real explanation to why H.264 or any other video encoding scheme, uses more CPU than say, another video encoding scheme.
then i though, ... why. so i didn't.
H.264 and it's cousins have been around a lot longer than it has been popular. H.264 and similar schemes have looked a lot better to human eyes than a lot of other "standard" encoding methods, for a long time. only within the last 2-3 years has it really become viable mainstream. i wonder why that is? (actually, i don't)
then i though, ... why. so i didn't.
H.264 and it's cousins have been around a lot longer than it has been popular. H.264 and similar schemes have looked a lot better to human eyes than a lot of other "standard" encoding methods, for a long time. only within the last 2-3 years has it really become viable mainstream. i wonder why that is? (actually, i don't)
DJ-Phat-AL
3:01 AM - 19 March, 2009
+1
man this thread went way off topic....
no mention of the comparisons between VDJ & VSL... since the first few posts
that's what happens though
Quote:
Off topic....I (Heart) dance music.+1
man this thread went way off topic....
no mention of the comparisons between VDJ & VSL... since the first few posts
that's what happens though
DJ-Phat-AL
3:02 AM - 19 March, 2009
u da man!!!
Quote:
People respect my opinions because of past contributions. Period.u da man!!!
Joshua Carl
7:56 PM - 19 March, 2009
and for the first few minutes of reading I was actually picking up some knowledge...
I think.
its too bad this thread went a-rye.
I have 2 systems at my gig. my laptop and the desktop.
for shitz n giggles I ran the same exact file (put a copy in both hds)
cue's them up, and got them running in sync.
then it was a matter of flicking the switch that controls which input goes to the TVs
so, while flicking back an forth I have to echo what we already know.
Vdj seems to run a smoother better looking video.
(if i remember it was a rip from my own dvd @ 3500kbs h264 )
am I gonna swap back to vdj... hellllll no.
but it gets under my skin that, that is still an issue...we all demand quality.
Like phat-al mentioned im one of those who waited in the wings for SSL to deliver
that death blow we now call 1.1 to make the permanant swap over...
now more than ever I scrutinize everyvideo I play and the biggest thing I dont see
on vdj is the ocasional black flashing horizontal line...and the vids in VDJ seem more fluid
I think.
its too bad this thread went a-rye.
I have 2 systems at my gig. my laptop and the desktop.
for shitz n giggles I ran the same exact file (put a copy in both hds)
cue's them up, and got them running in sync.
then it was a matter of flicking the switch that controls which input goes to the TVs
so, while flicking back an forth I have to echo what we already know.
Vdj seems to run a smoother better looking video.
(if i remember it was a rip from my own dvd @ 3500kbs h264 )
am I gonna swap back to vdj... hellllll no.
but it gets under my skin that, that is still an issue...we all demand quality.
Like phat-al mentioned im one of those who waited in the wings for SSL to deliver
that death blow we now call 1.1 to make the permanant swap over...
now more than ever I scrutinize everyvideo I play and the biggest thing I dont see
on vdj is the ocasional black flashing horizontal line...and the vids in VDJ seem more fluid
jonnie_Spinns
1:13 AM - 20 March, 2009
I think.
its too bad this thread went a-rye.
I have 2 systems at my gig. my laptop and the desktop.
for shitz n giggles I ran the same exact file (put a copy in both hds)
cue's them up, and got them running in sync.
then it was a matter of flicking the switch that controls which input goes to the TVs
so, while flicking back an forth I have to echo what we already know.
Vdj seems to run a smoother better looking video.
(if i remember it was a rip from my own dvd @ 3500kbs h264 )
am I gonna swap back to vdj... hellllll no.
but it gets under my skin that, that is still an issue...we all demand quality.
Like phat-al mentioned im one of those who waited in the wings for SSL to deliver
that death blow we now call 1.1 to make the permanant swap over...
now more than ever I scrutinize everyvideo I play and the biggest thing I dont see
on vdj is the ocasional black flashing horizontal line...and the vids in VDJ seem more fluid
The horizontal lines are one thing that is holding us back as well as the fluidity of vdj. we have come to the conclusion that we will be in the future using vsl, and in the mean time gonna use vsl on a minimal basis after everyone has gotten drunk so the likely hood of someone noticing drops.
Quote:
and for the first few minutes of reading I was actually picking up some knowledge...I think.
its too bad this thread went a-rye.
I have 2 systems at my gig. my laptop and the desktop.
for shitz n giggles I ran the same exact file (put a copy in both hds)
cue's them up, and got them running in sync.
then it was a matter of flicking the switch that controls which input goes to the TVs
so, while flicking back an forth I have to echo what we already know.
Vdj seems to run a smoother better looking video.
(if i remember it was a rip from my own dvd @ 3500kbs h264 )
am I gonna swap back to vdj... hellllll no.
but it gets under my skin that, that is still an issue...we all demand quality.
Like phat-al mentioned im one of those who waited in the wings for SSL to deliver
that death blow we now call 1.1 to make the permanant swap over...
now more than ever I scrutinize everyvideo I play and the biggest thing I dont see
on vdj is the ocasional black flashing horizontal line...and the vids in VDJ seem more fluid
The horizontal lines are one thing that is holding us back as well as the fluidity of vdj. we have come to the conclusion that we will be in the future using vsl, and in the mean time gonna use vsl on a minimal basis after everyone has gotten drunk so the likely hood of someone noticing drops.
Charlie Five
7:59 PM - 20 March, 2009
Those lines are most likely because the videos are interlaced. Did you de-interlace when you went the the encoding process?
Funkytownstopsix
8:07 PM - 20 March, 2009
Question do you have to de-interlace if the video looks like it doesn't need it.
Charlie Five
8:16 PM - 20 March, 2009
If you are playing an interlaced file with the settings in V-SL anything lower the the highest quality they will show.
Quote:
Those lines are most likely because the videos are interlaced. Did you de-interlace when you went the the encoding process?If you are playing an interlaced file with the settings in V-SL anything lower the the highest quality they will show.
Joshua Carl
8:38 PM - 20 March, 2009
its not "those" lines... i should have been more clear.
Ill try to get an image, but its so hard
Ill try to get an image, but its so hard
nik39
8:39 PM - 20 March, 2009
I may sound like a broken record.... When using DVD's at a framerate of 29.97 (anything which has been pulled up... PO for example) deinterlacing is not the proper way to fix it, since this will unnecessary cause a reduction of the vertical resolution. IVTC is the proper way of doing it.
Joshua Carl
8:49 PM - 20 March, 2009
nik
can you explain that more, or give reference to how hat works
(im still kinda green on the video side)
Quote:
I may sound like a broken record.... When using DVD's at a framerate of 29.97 (anything which has been pulled up... PO for example) deinterlacing is not the proper way to fix it, since this will unnecessary cause a reduction of the vertical resolution. IVTC is the proper way of doing it.nik
can you explain that more, or give reference to how hat works
(im still kinda green on the video side)
nik39
8:57 PM - 20 March, 2009
Sure, this should help you:
en.wikipedia.org
www.100fps.com < with more pics and examples. It shows when you should NOT deinterlace.
Read the paragraphs which go like:
VJ Austin Allen should also esp have a look at *this* part.. "Resizing height without deinterlacing first"
www.100fps.com
en.wikipedia.org
www.100fps.com < with more pics and examples. It shows when you should NOT deinterlace.
Read the paragraphs which go like:
Quote:
Because this is an artificial step you can undo it without really deinterlacing it but simply by undoing it, which is called "Inverse Telecine" (=IVTC) or "Reverse Telecine" (30fps->24fps). So inversed telecine would consist of merging fields back to frames and deleting artificially inserted frames if there are any. In my example with Crusty the Clown from the series "The Simpsons" you can simply delete Frame2 as it wasn't meant to be by the cartoonists anyway.VJ Austin Allen should also esp have a look at *this* part.. "Resizing height without deinterlacing first"
www.100fps.com
a-swift
11:01 PM - 20 March, 2009
nik39, let me get this straight. you're actually fixing all your video files that are pulled down?
you can't be serious with this right?
maybe i should fix all mine too. compressor does reverse telecine by the way.
you can't be serious with this right?
maybe i should fix all mine too. compressor does reverse telecine by the way.
nik39
11:03 PM - 20 March, 2009
Why not? I am not doing this manually.
I know you like these magic words: My scripts do it ;)
I know you like these magic words: My scripts do it ;)
a-swift
11:06 PM - 20 March, 2009
i don't think anyone else is fixing their videos. i know i'm not. even on my edits where i should be fixing them, i'm not. i never have.
are your scripts smart enough to know when the content doesn't need to be ivtc?
Quote:
Plus... I can't stand the interlacing/combing artifacts.. :-/i don't think anyone else is fixing their videos. i know i'm not. even on my edits where i should be fixing them, i'm not. i never have.
are your scripts smart enough to know when the content doesn't need to be ivtc?
nik39
11:08 PM - 20 March, 2009
If I am ripping from DVD then the files will be tagged in such a way that the scripts know they need to be ivtc'ed.
Correct me if I am wrong, but for example *all* PO DVD's are pulled up, right?
Quote:
are your scripts smart enough to know when the content doesn't need to be ivtc?If I am ripping from DVD then the files will be tagged in such a way that the scripts know they need to be ivtc'ed.
Correct me if I am wrong, but for example *all* PO DVD's are pulled up, right?
nik39
11:09 PM - 20 March, 2009
Yeah, you should really do it.
You already know all the pros.. better quality, better compressibility. (Different lines from different frames in one frame do not compress well)
Quote:
even on my edits where i should be fixing them, i'm not.Yeah, you should really do it.
You already know all the pros.. better quality, better compressibility. (Different lines from different frames in one frame do not compress well)
Rebelguy
11:09 PM - 20 March, 2009
i don't think anyone else is fixing their videos. i know i'm not. even on my edits where i should be fixing them, i'm not. i never have.
are your scripts smart enough to know when the content doesn't need to be ivtc?
Smashvidz is using this method.
Quote:
Quote:
Plus... I can't stand the interlacing/combing artifacts.. :-/i don't think anyone else is fixing their videos. i know i'm not. even on my edits where i should be fixing them, i'm not. i never have.
are your scripts smart enough to know when the content doesn't need to be ivtc?
Smashvidz is using this method.
a-swift
11:16 PM - 20 March, 2009
If I am ripping from DVD then the files will be tagged in such a way that the scripts know they need to be ivtc'ed.
Correct me if I am wrong, but for example *all* PO DVD's are pulled up, right?
hmm. i'm confused. if the video was shot in 29.97 and goes to DVD at 29.97, why would it need to be pulled up? granted, i do understand most are produced at 24fps but most does not equal all, unless there is something i don't know about.
Quote:
Quote:
are your scripts smart enough to know when the content doesn't need to be ivtc?If I am ripping from DVD then the files will be tagged in such a way that the scripts know they need to be ivtc'ed.
Correct me if I am wrong, but for example *all* PO DVD's are pulled up, right?
hmm. i'm confused. if the video was shot in 29.97 and goes to DVD at 29.97, why would it need to be pulled up? granted, i do understand most are produced at 24fps but most does not equal all, unless there is something i don't know about.
nik39
11:20 PM - 20 March, 2009
You are right. But as you said, *most* are shot at 24fps.
However some of the filters are quite advanced, they find out with very high probability whether the video needs to be pulled down or not.
Of course with no automatic method you will ever reach 100%, but you can get close.
However some of the filters are quite advanced, they find out with very high probability whether the video needs to be pulled down or not.
Of course with no automatic method you will ever reach 100%, but you can get close.
a-swift
11:28 PM - 20 March, 2009
However some of the filters are quite advanced, they find out with very high probability whether the video needs to be pulled down or not.
Of course with no automatic method you will ever reach 100%, but you can get close.
you can get 100% accuracy manually.
Quote:
You are right. But as you said, *most* are shot at 24fps.However some of the filters are quite advanced, they find out with very high probability whether the video needs to be pulled down or not.
Of course with no automatic method you will ever reach 100%, but you can get close.
you can get 100% accuracy manually.
VJ Justin Allen
11:31 PM - 20 March, 2009
VJ Austin Allen should also esp have a look at *this* part.. "Resizing height without deinterlacing first"
www.100fps.com
You just cannot help yourself with the continuing cheap shots can you. Well I've told them I will stop but it seems you just cannot.
I'm not surprised.
Quote:
VJ Austin Allen should also esp have a look at *this* part.. "Resizing height without deinterlacing first"
www.100fps.com
You just cannot help yourself with the continuing cheap shots can you. Well I've told them I will stop but it seems you just cannot.
I'm not surprised.
nik39
11:54 PM - 20 March, 2009
Probably. But I have no problem if 0.1% of my videos get ivtc'ed when they shouldn't, rather than 99.9% having combing artifacts.
I'm not surprised.
No cheap shot. It is an objective hint.
"Resizing height without deinterlacing first" is a no go. And you end up with www.100fps.com < that, and the videos on your website. There is nothing to debate about this. This is a fact.
Quote:
you can get 100% accuracy manually.Probably. But I have no problem if 0.1% of my videos get ivtc'ed when they shouldn't, rather than 99.9% having combing artifacts.
Quote:
You just cannot help yourself with the continuing cheap shots can you. Well I've told them I will stop but it seems you just cannot.I'm not surprised.
No cheap shot. It is an objective hint.
"Resizing height without deinterlacing first" is a no go. And you end up with www.100fps.com < that, and the videos on your website. There is nothing to debate about this. This is a fact.
nik39
11:56 PM - 20 March, 2009
Numbers may not be accurate ;)
Quote:
Probably. But I have no problem if 0.1% of my videos get ivtc'ed when they shouldn't, rather than 99.9% having combing artifacts.Numbers may not be accurate ;)
a-swift
12:11 AM - 21 March, 2009
i still can't get over the fact that you are fixing all these videos.
phuckit. i'm doing my whole library. i'm writing my own script to do it. i'm re-doing all my swift edits also.
can't have germany 1-uping me.
phuckit. i'm doing my whole library. i'm writing my own script to do it. i'm re-doing all my swift edits also.
can't have germany 1-uping me.
To participate in this forum discussion please log in to your Serato account.