Kommentare

BruceUSA schrieb am 31.01.2015 um 20:01 Uhr
I tried and am having problem. see the screen shot.

[IMG=http://www.overclockers.com/forums/attachment.php?attachmentid=159331&stc=1&d=1422730855]

CPU:  i9 Core Ultra 285K OCed @5.6Ghz  
MBO: MSI Z890 MEG ACE Gaming Wifi 7 10G Super Lan, thunderbolt 4
RAM: 48GB RGB DDR5 8200mhz
GPU: NVidia RTX 5080 16GB Triple fan OCed 3100mhz, Bandwidth 1152 GB/s     
NVMe: 2TB T705 Gen5 OS, 4TB Gen4 storage
MSI PSU 1250W. OS: Windows 11 Pro. Custom built hard tube watercooling

 

                                   

                 

               

 

MikeLV schrieb am 04.02.2015 um 02:35 Uhr
Did anyone have success with the newest version of Handbrake with Marco's tutorial or is it strictly for the previous 0.9.9 version?
OldSmoke schrieb am 04.02.2015 um 02:36 Uhr
I had only issues with 4K footage as reported in another thread; no issue with HD and lower resolutions.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

musicvid10 schrieb am 04.02.2015 um 02:59 Uhr
MPEG-2 encoder in Handbrake sucks. Totally.
musicvid10 schrieb am 04.02.2015 um 04:13 Uhr
Marco,
Could your workflow be adapted for DVD -> MakeMKV -> Handbrake?

pilsburypie schrieb am 04.02.2015 um 13:50 Uhr
What a pity that Mpeg in mp4 container doesn't work. For me the regular mp4 method is only of use if I wanted to really lower bit rates for internet. I had difficulty telling quality apart when I render mp4 in Vegas at very high bitrates. The ultimate winner would be that mpeg 2 conversion to DVD.

pilsburypie schrieb am 04.02.2015 um 15:39 Uhr
UPDATE: I'm on Handbrake 0.9.9 version and the mpg option is available on the video tab. I simply select the 720 width (PAL widescreen resolution) 25 fps and hey presto it renders out without error. DVDA however does insist on re-rendering even though I changed the file extension from .mp4 to .mpg

Now immediately I notice something. My 1080 -> SD renders from Vegas mpeg2 all have what I can only describe as artifacts around moving objects, a bit like noise. The Handbrake render does not. This is a big improvement but still to my HD spoiled eyes, both SD versions, Vegas and Handbrake look soft.

I shall fiddle some more, but so far, looks promising.
MikeLV schrieb am 04.02.2015 um 16:50 Uhr
OldSmoke, thanks, I'll go ahead and download the latest version and see how I make out...
Marco. schrieb am 04.02.2015 um 18:13 Uhr
In theory certainly there are several choices how you could modify the given scripts, cmd and macro functions to work with different tools. For example I have another version only meant for lanczos scaling from Vegas to Vegas.
It always depends on how the used applications (like HandBrake) work and in which ways you could control them. But I don't know how MakeMKV works.
Laurence schrieb am 04.02.2015 um 18:33 Uhr
> This is a big improvement but still to my HD spoiled eyes, both SD versions, Vegas and Handbrake look soft.

Try adding a little sharpening before any downrezzing. I use the simple Sony sharpening filter that comes with Vegas. The default setting of 50% is a good place to start.
MikeLV schrieb am 05.02.2015 um 00:32 Uhr
I just went through the setup process following all the directions on this page: http://www.vegasvideo.de/vegas-2-handbrake-en for Vegas 12. It looked like everything was working. However, after the step where handbrake scans the video, nothing happened. handbrake's status message on the bottom left just says Ready and there's no MP4 file in the designated folder. What could have gone wrong? I should also mention that the only change I made was removing the line about progressive video since my source is interlaced. Rereading this thread, it seems mine is the same problem that dingus reported.. I'm using the latest production version of Handbrake.

Edit: I'm not entirely too bright, I was trying to figure out how the script told handbrake which preset to use, then I realized that it stops on purpose so you can select settings, or a preset to use, then just click start (for anyone else who runs into this)
musicvid10 schrieb am 05.02.2015 um 01:56 Uhr
Well the MakeMKV frontend is wonderful.
Grazie schrieb am 26.02.2015 um 18:57 Uhr
Just got this:

Microsoft.JScript.Vsa.JSVsaException: UnknownError (0x801330FF): System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at JScript 0.Global Code() in Sony.Vegas://Script/__ScriptText__:line 9
at Sony.Vegas._Startup.Startup()
at Microsoft.JScript.Vsa.BaseVsaEngine.Run()


Using HB 0.10.0.6534

Any ideas?

Grazie


Grazie

PC 10 64-bit 64gb * Intel Core i9 10900X s2066 * EVGA RTX 3080 XC3 Ultra 10GB - Studio Driver 551.23 * 4x16G CorsVengLPX DDR4 2666C16 * Asus TUF X299 MK 2


Cameras: Canon XF300 + PowerShot SX60HS Bridge

john_dennis schrieb am 26.02.2015 um 20:00 Uhr
Try 9.9.something.

10 may not be fixed yet.
OldSmoke schrieb am 26.02.2015 um 20:45 Uhr
Yup, I also went back to 9.9xx.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Grazie schrieb am 26.02.2015 um 21:43 Uhr
Nope. Same error.

I went back down to HB 9.4 . Still getting error. Now have HB 0.9.9.5530

Tested that:-

1] Frameserver Works

2] HB Works.

But not the One-Click

Ugh . . .

G

Grazie

PC 10 64-bit 64gb * Intel Core i9 10900X s2066 * EVGA RTX 3080 XC3 Ultra 10GB - Studio Driver 551.23 * 4x16G CorsVengLPX DDR4 2666C16 * Asus TUF X299 MK 2


Cameras: Canon XF300 + PowerShot SX60HS Bridge

johnmeyer schrieb am 26.02.2015 um 22:48 Uhr
Why does everyone keep upgrading their software?? "If it ain't broke, don't fix it" is not just a clever saying, but is something everyone here should live by, if they value their time and want to get things finished before their deadline passes.

Most software upgrades, especially once you get past the first few releases, provide very small incremental improvements, but usually also often break things that used to work.

My recommendation:

1. Turn off ALL automatic updates.

2. Only update software when there is a feature that will actually make a HUGE improvement in your life, and let you get something done faster or better.

3. When you are going to upgrade, at the very least create a system restore point, and better yet, do a complete backup of your boot drive.

I just looked at my Program Files folder, and almost all the the "modified" dates are several years old. Everything works just fine.

As for this specific problem, I use MeGUI instead of Handbrake, but it is similar in some ways. When I first installed it 4-5 years ago, I didn't realize it was constantly updating itself (they don't make the automatic update obvious), and suddenly one day, nothing worked. I was able to restore the original installation using a backup, and I haven't updated since.

I just spent more time typing this than I've spent solving update problems in the past five years.


Grazie schrieb am 27.02.2015 um 09:51 Uhr

JM: Why does everyone keep upgrading their software??

Er, wanting "better"? And, not speaking for everybody, when I do, I do it when there is an option to back-track - apparently not here with HB for me - and reinstall an earlier working copy. Could this could be a clue? Maybe I need to uninstall all the components of the One-Click and restart in the order as described by Marco. Maybe I can't - for me - just reinstall an earlier version of HB and have the LINKAGES to be available, again.

No Auto Updates here. Each update done manually and have been for at least 3 years now.

Restore did nothing to improve matters. I went back to a point prior a date that I can prove this one-clicked did work.

FYI, how would I know the benefits unless I trailed it? - But that's me and not you.

Thank you for your typing-time and your wish to assist.

Grazie

Grazie

PC 10 64-bit 64gb * Intel Core i9 10900X s2066 * EVGA RTX 3080 XC3 Ultra 10GB - Studio Driver 551.23 * 4x16G CorsVengLPX DDR4 2666C16 * Asus TUF X299 MK 2


Cameras: Canon XF300 + PowerShot SX60HS Bridge

ushere schrieb am 27.02.2015 um 10:00 Uhr
i've never liked the cutting edge, you bleed too easily...

however, once a few have bled one gets a clearer idea of what's going on. thanks grazie ;-)

i firmly believe in keeping everything up to date, but ONLY after i'm sure i'm not going to get any nasty surprises....
Grazie schrieb am 27.02.2015 um 10:15 Uhr
Leslie: but ONLY after i'm sure i'm not going to get any nasty surprises....Same reply - how'd yer know!

Grazie

Grazie

PC 10 64-bit 64gb * Intel Core i9 10900X s2066 * EVGA RTX 3080 XC3 Ultra 10GB - Studio Driver 551.23 * 4x16G CorsVengLPX DDR4 2666C16 * Asus TUF X299 MK 2


Cameras: Canon XF300 + PowerShot SX60HS Bridge

Marco. schrieb am 27.02.2015 um 10:57 Uhr
I don't know whether this one relates to your problem but now I have an issue on my own system. It seems like after a Windows update the file mount system doesn't work no more. In this case when using the start script from Vegas, frameserving starts fine but then the process hangs in a cmd loop.
I will take a look at the file mount system though at the moment I have no idea how to fix that.
Grazie schrieb am 27.02.2015 um 11:16 Uhr
Marco, sorry to hear that. Could it be that the M$ Update broke a connection to and from your script? Would a reinstall of your Script make any difference?

G

Grazie

PC 10 64-bit 64gb * Intel Core i9 10900X s2066 * EVGA RTX 3080 XC3 Ultra 10GB - Studio Driver 551.23 * 4x16G CorsVengLPX DDR4 2666C16 * Asus TUF X299 MK 2


Cameras: Canon XF300 + PowerShot SX60HS Bridge

Marco. schrieb am 27.02.2015 um 11:27 Uhr
The Vegas script itself works fine here. Else frameserving wouldn't start.
Don't know what it is.
Grazie schrieb am 27.02.2015 um 14:01 Uhr
Back in biz. This was missing.- Move the folder "frameserver" to the main partition C:\ (this is critical because all the scripts and batch files used in this process refer to this path)
I ALSO reinstall AVISynth too.

Why? - No Eye Deer . . . .

Grazie

Grazie

PC 10 64-bit 64gb * Intel Core i9 10900X s2066 * EVGA RTX 3080 XC3 Ultra 10GB - Studio Driver 551.23 * 4x16G CorsVengLPX DDR4 2666C16 * Asus TUF X299 MK 2


Cameras: Canon XF300 + PowerShot SX60HS Bridge