VideoHelp Forum




+ Reply to Thread
Page 5 of 5
FirstFirst ... 3 4 5
Results 121 to 125 of 125
  1. Member
    Join Date
    Nov 2009
    Location
    United Kingdom
    Search Comp PM
    Originally Posted by Alwyn View Post
    I'd only be using the latest 64bit version if I were you. You've got an old machine, on an old OS, using an outdated version; Sep 2020 is a long time ago.
    I didn’t think the 64 but version would work on the 32Bit OS? Hence looking for the 32Bit version, or am I wrong?

    Anyway I did some more searching and found this thread:

    https://forum.shotcut.org/t/exporting-stuck-at-9/14816/5

    It offers a method of exporting the video using Shocut but running the actual export outside of Shocut, using qmelt.exe and the .xml export file.

    Here's the text:

    I agree with @Hudson555x. You are more than likely running out of memory. Not only is a single process (running .exe) limited to 3 GB RAM on 32-bit, which is very limiting for video editing, your entire system only has 3 GB RAM! Export in Shotcut runs in a background process. This means when export starts the operating system itself is taking some RAM, Shotcut UI is taking a fair amount of RAM to load itself plus your project, then the background export process (qmelt.exe) needs to load the same project and spend RAM. Ways to reduce RAM usage:

    Reboot
    Close all other applications
    Limit your project (Video Mode) resolution
    Export outside of Shotcut:
    start an export
    stop it
    right click export Job and view its XML
    save the XML
    close Shotcut
    run cmd.exe
    cd C:\Program Files (x86)\Shotcut
    qmelt \path\to\save\xml


    Entering the details and path to my .xml file, it appears to have started the export and is approaching the failure point.
    I'll let you know how it goes.
    Last edited by JonnyAlpha; 20th Dec 2023 at 06:00.
    Quote Quote  
  2. Member
    Join Date
    Nov 2009
    Location
    United Kingdom
    Search Comp PM
    Well that failed as well, at around the same spot.

    So, I now have 2 x files that are incomplete. In Windows Explorer they look fine, but I have now found that they won't play. What is also interesting is that both where only about 650MB is that correct for around 55minutes of DV encoded to .mp4?

    I then thought I'd download the latest version of Shocut on my Macbook. I'd have to plug the SSD drive into my Mac using an SSD to USB adaptor which I have, import the video clips from the SSD and export either to my Macbook HDD or to the external SSD. Will exporting to an external SSD drive plugged into USB cause any issues with the export?

    I could also try and install Shocut to my Windows 10 Laptop?
    Quote Quote  
  3. Member
    Join Date
    Nov 2009
    Location
    United Kingdom
    Search Comp PM
    Well I ended up installing Shocut on my MacBook and successfully created an mp4 from mulch first tape.
    Then before I got a chance to do another the old Windows PC died and I had to rebuild it.
    So now it’s running on a 2.5 SATA HDD and Windows 64 Ultimate.
    I then started the process of adding WinDV and captured some more AVI clips.
    Then VirtualDub, this is where I started getting into issues. I downloaded VirtualDub and tried running the 32 Bit which I had added the MSUDenoiser. After applying the filters, when attempting to select Save Video, it is not an available option only Save AVI.
    I then downloaded VirtualDub2 and found that this had the Save Video option where you can select the necessary codecs. The problem is it does not have Huffyuv 2.1 as an codec. I downloaded the codex but not exactly sure where to install it.
    Also MSUDenoiser does not want to load into VirtualDub2 64.
    So what version of VirtualDub should I be using and how do I get Huffyuv 2.1 and the correct YUY2 codec.
    Quote Quote  
  4. Member
    Join Date
    May 2005
    Location
    Australia-PAL Land
    Search Comp PM
    VDub 1.x doesn't have a lot of inbuilt export options. VDub2 has the X264 codec built-in, so you can export to MP4 format. As you've found, some filters (MSU Denoiser being one) is a 32bit filter and will only work in 32-bit Vdub, so drop it into vDub2 32bit and you'll be in business.

    Installing HUFF is a minor horror story. I'll leave that to others to help.
    Last edited by Alwyn; 31st Dec 2023 at 20:15.
    Quote Quote  
  5. If you don't have some specific need to use huffyuv and you want to export lossless I believe virtualdub2 also comes with at least ffv1 as a lossless codec built in as an export option which at least shotcut should be able to import than needing to mess around with the ancient huffyuv installer.
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!