I was wondering if there's any way to take care of this.
Here's my avisynth script:
FFVideosource("F:\Suzumiya\Suzumiya Haruhi no shoushitsu (BD-rip 1920x1080 H.264 AAC 2ch+5.1ch).mp4")
Converting a file in VDM; projected time 12 - 14 hours?
-
Jessie-kun
- Joined: Fri Sep 04, 2009 2:28 pm
Converting a file in VDM; projected time 12 - 14 hours?
Okay, so I have a rather large movie file that I'm wanting to edit with. I am converting and saving the movie into parts, and am currently doing a thirty minute segment. This alone, however, has a projected time going up and down between twelve and fourteen hours.
I was wondering if there's any way to take care of this.
Here's my avisynth script:
I was wondering if there's any way to take care of this.
Here's my avisynth script:
-
BasharOfTheAges
- Just zis guy, you know?
- Joined: Tue Sep 14, 2004 11:32 pm
- Status: Breathing
- Location: Merrimack, NH
Re: Converting a file in VDM; projected time 12 - 14 hours?
1) What codec are you using to save the video? With what settings?
2) What are your system specs?
It's not unheard of for large format frames to take a lot longer... usually you have to be filtering them for that to happen though. Even doing minimal filtering after resizing down to 720p, the entire discs of Paprika and GitS:Innocense took me something like 35 hours a piece to render out on an AMD Phenom II x4 Black (3.14GHz).
2) What are your system specs?
It's not unheard of for large format frames to take a lot longer... usually you have to be filtering them for that to happen though. Even doing minimal filtering after resizing down to 720p, the entire discs of Paprika and GitS:Innocense took me something like 35 hours a piece to render out on an AMD Phenom II x4 Black (3.14GHz).
Anime Boston Fan Creations Coordinator (2019-2023)
Anime Boston Fan Creations Staff (2016-2018)
Another Anime Convention AMV Contest Coordinator 2008-2016
| | |
Anime Boston Fan Creations Staff (2016-2018)
Another Anime Convention AMV Contest Coordinator 2008-2016
| | |
-
Mister Hatt
- Joined: Tue Dec 25, 2007 8:26 am
- Status: better than you
- Contact:
Re: Converting a file in VDM; projected time 12 - 14 hours?
Seriously? The Eureka seveN movie is even bigger than those and it only took me 21 hours on a slower CPU than yours, with more filtering. Except that most filters are optimised for Intel CPU's now.
The first thing you have to realise is that 1080p is BIG. Just because 1920/720 and 1080/480 aren't that big ratio changes doesn't mean the number of pixels involved doesn't jump dramatically. The pixelcount is a multiple of the two, so realistically, your filter has to process 6x the number of pixels of a DVD, making it take 6x the time at LEAST. Then you have to remember that at the higher res, the motion vectors are much longer, so temporal filtering will also take considerably more time. This however isn't a problem for you, as you are just loading directly, but if your encoder is not lossless, or if it is but isn't intra-coded, it will also be processing these longer motion vectors. I do think the time is excessive, but that really depends on your PC specs and encoder settings. Post them if you want a better idea of why it is being 'slow'.
The first thing you have to realise is that 1080p is BIG. Just because 1920/720 and 1080/480 aren't that big ratio changes doesn't mean the number of pixels involved doesn't jump dramatically. The pixelcount is a multiple of the two, so realistically, your filter has to process 6x the number of pixels of a DVD, making it take 6x the time at LEAST. Then you have to remember that at the higher res, the motion vectors are much longer, so temporal filtering will also take considerably more time. This however isn't a problem for you, as you are just loading directly, but if your encoder is not lossless, or if it is but isn't intra-coded, it will also be processing these longer motion vectors. I do think the time is excessive, but that really depends on your PC specs and encoder settings. Post them if you want a better idea of why it is being 'slow'.