Editing GoPro footage in Vegas 13 using Avisynth

[Rickyasna43]

Hi guys,
I'm usually to convert my gopro file from mp4 to avi format using GoPro Studio in order to use avi file in a Vegas workspace. I've know about Avisynth in the last weeks but i've some trouble to use it. I've follow some guides from Youtube but i'm not able to use Avisynth correctly (the giudes are old and with my Windows 10 laptop don't run). Could someone help me? Is there a guide that explain step by step how to use Avisynth in Sony Vegas with GoPro File? Thanks so much.

[FranceBB]

Assuming that Sony Vegas can read .avs files as Virtual Dub and other video editors can,
all you need to do is:

1) Install Avisynth
2) Create a new a .txt typing the following command into it:

DirectShowSource("goprofile.mp4")


3) Save the .txt and change its extenction to .avs
4) Drag and drop it in sony vegas, as avisynth will make a lossless avi audio video stream that will be read by Sony Vegas.

That's it. ;)

Oh, and welcome to the Avisynth world! :D

[Rickyasna43]

Assuming that Sony Vegas can read .avs files as Virtual Dub and other video editors can,
all you need to do is:

1) Install Avisynth
2) Create a new a .txt typing the following command into it:

DirectShowSource("goprofile.mp4")


3) Save the .txt and change its extenction to .avs
4) Drag and drop it in sony vegas, as avisynth will make a lossless avi audio video stream that will be read by Sony Vegas.

That's it. ;)

Oh, and welcome to the Avisynth world! :D

Thanks for your support.
I've try to do it but don't run anything. When i save the txt file with avs extension (replacing goproflie with the real name file) it appears a video black with some red written. Furthermore, i'm not sure that sony vegas it's able to read avs file.

EDIT: Sony Vegas didn't read avs file. How can i do this operation so?

[johnmeyer]

Hi guys,
I'm usually to convert my gopro file from mp4 to avi format using GoPro Studio in order to use avi file in a Vegas workspace. I've know about Avisynth in the last weeks but i've some trouble to use it. I've follow some guides from Youtube but i'm not able to use Avisynth correctly (the giudes are old and with my Windows 10 laptop don't run). Could someone help me? Is there a guide that explain step by step how to use Avisynth in Sony Vegas with GoPro File? Thanks so much.First of all, as I think you already know, Sony Vegas 13 (and probably 14) has problems reading native GoPro files. There is a fix for that which you can find with Google. It involves copying a DLL file from a previous Vegas version. You can then edit the files directly without first converting them in Studio (although that actually is a pretty good workflow, and I'd recommend you stick with it).

As for Vegas reading AVS files, it cannot read them directly. There is a workaround I discovered years ago, and I published a tutorial:

Render Through AVISynth Scripts Using Sony Vegas As Both Source, and Renderer (https://www.youtube.com/watch?v=wVP8BQSV2Ak)

It involves using VFAPIConv, an old hack that works great under XP 32-bit, but may be an issue under later versions of Windows. Since I still have XP installed, I use that when I need to serve an AVISynth script directly into Vegas, so I haven't explored what modifications would be required for 7,8, & 10, or whether any of this will work under a 64-bit O/S. However, once you've tried it, I think you may find a solution to any issues simply by Googling around a little bit.

[StainlessS]

John Meyer is the Dogs,
Ill fight any man that says he is not. John for king!
Bit pissed.

[johnmeyer]

John Meyer is the Dogs,
Ill fight any man that says he is not. John for king!
Bit pissed.May you stay pissed the rest of your life so I can hear more great things about myself!

[GMJCZP]

A good alternative is AVFS (Avisynth Virtual File System).

[Reel.Deel]

2) Create a new a .txt typing the following command into it:

DirectShowSource("goprofile.mp4")


DirectShowSource is horrible advice. Use LSMASHVideoSource (http://avisynth.nl/index.php/LSMASHSource) or FFVideoSource (http://avisynth.nl/index.php/FFmpegSource) instead. If you have compatible hardware and are willing to spend $15, I highly recommend the very reliable DGDecNV (http://rationalqm.us/dgdecnv/dgdecnv.html).

A good alternative is AVFS (Avisynth Virtual File System).

+1, specially the continued development by Myrsloik which adds high bit-depth support for AviSynth+.

[FranceBB]

@Reel.Deel... true; DirectShowSource it's not frame accurate and I don't actually use it either, but since he just installed Avisynth, I suggested something to open videos straight away. ;)

Oh, for the records, I actually prefer LSMASH over DGIndex and DGAVCIndex.
As to FFMpegSource2, I still prefer it over DGIndex and DGAVC Index 'cause it's able to open .MXF files, while DGIndex crashes. ;)

[Rickyasna43]

First of all, as I think you already know, Sony Vegas 13 (and probably 14) has problems reading native GoPro files. There is a fix for that which you can find with Google. It involves copying a DLL file from a previous Vegas version. You can then edit the files directly without first converting them in Studio (although that actually is a pretty good workflow, and I'd recommend you stick with it).

As for Vegas reading AVS files, it cannot read them directly. There is a workaround I discovered years ago, and I published a tutorial:

Render Through AVISynth Scripts Using Sony Vegas As Both Source, and Renderer (https://www.youtube.com/watch?v=wVP8BQSV2Ak)

It involves using VFAPIConv, an old hack that works great under XP 32-bit, but may be an issue under later versions of Windows. Since I still have XP installed, I use that when I need to serve an AVISynth script directly into Vegas, so I haven't explored what modifications would be required for 7,8, & 10, or whether any of this will work under a 64-bit O/S. However, once you've tried it, I think you may find a solution to any issues simply by Googling around a little bit.

Hi johnmeyer! First of all, thanks for advise me about the problem of gopro native files on Vegas 13.
I've just see your great video on yt but i'm confirming that vfapiconv don't run with windows 10 (i've tried also XP compatibility but nothing). When i try to add the avs file on it, there's no replay from the program. Can i use an other program in order to convert an avs file into an avi file? Could someone suggest me a software able to do this?

A good alternative is AVFS (Avisynth Virtual File System).

Sorry but after downloading the software, the exe didn't run. Why? Who can explain me how AVFS work?

[johnmeyer]

As I stated in my previous post, I suspected that VFAPIConv might not work in Win 7/8/10 or 64-bit. Because I can still boot to XP when I need to, I haven't had to figure out the workaround. So, all I can do is to suggest you use Google to find the answer. After about thirty seconds of searching, I found a post, in this forum, that might be of help:

VFAPI and Windows 7 Problems (http://forum.doom9.org/showpost.php?p=1454837&postcount=10)

My guess is that if that workaround did in fact work for Win7, it will probably also work for Win10.

[poisondeathray]

The newer avfs versions use commandline, the instructions are in the readme. It's a simple one liner

start avfs myscript.avs


This assumes your script is already valid and working . Vegas won't accept YUV, so you need to use ConvertToRGB24() or 32 with the appropriate matrix and flags to work in vegas


BUT - Why don't you edit the gopro footage natively ? What is your reason for using avisynth ? If your system is a bit slow or old, native files may struggle a bit... but using an avs script will make it even SLOWER because there is additional frameserving overhead (the exception is if you use a GPU based decoding script like DGNVTools).

The usual reason for using avs importing methods into vegas, is if you have other pre processing tasks to do and you don't want additional large intermediate files.

The workflow you had been using - cineform - is a commonly used, because it improves editing responsiveness (the files are less compressed and all I-frame), and is visually lossless at the higher quality settings . But the main "negative" is larger filesizes

[Rickyasna43]

The newer avfs versions use commandline, the instructions are in the readme. It's a simple one liner

start avfs myscript.avs


This assumes your script is already valid and working . Vegas won't accept YUV, so you need to use ConvertToRGB24() or 32 with the appropriate matrix and flags to work in vegas


BUT - Why don't you edit the gopro footage natively ? What is your reason for using avisynth ? If your system is a bit slow or old, native files may struggle a bit... but using an avs script will make it even SLOWER because there is additional frameserving overhead (the exception is if you use a GPU based decoding script like DGNVTools).

The usual reason for using avs importing methods into vegas, is if you have other pre processing tasks to do and you don't want additional large intermediate files.

The workflow you had been using - cineform - is a commonly used, because it improves editing responsiveness (the files are less compressed and all I-frame), and is visually lossless at the higher quality settings . But the main "negative" is larger filesizes

Sorry for my late replay.
Now i'm using a laptop with i7 HQ processor, 8 gb of ram and a dedicated graphic card, so i haven't problem to render video. I would know the best way to manipulate a gopro native file from the conversion, passing to editing and then rendering. The workflow Gopro Studio conversion in avi file is good in this sense so? Could you advise me to set conversion to MEDIUM and not to HIGH level during the conversion process with GoPro Studio (i've read about it on internet but i've not discover why is better set a medium option than high)

As I stated in my previous post, I suspected that VFAPIConv might not work in Win 7/8/10 or 64-bit. Because I can still boot to XP when I need to, I haven't had to figure out the workaround. So, all I can do is to suggest you use Google to find the answer. After about thirty seconds of searching, I found a post, in this forum, that might be of help:

VFAPI and Windows 7 Problems

My guess is that if that workaround did in fact work for Win7, it will probably also work for Win10.

I would check this, but if you say that gopro studio workflow is better than using avisnth, i'll continue to use this method

[johnmeyer]

As already stated in earlier posts, converting to a Cineform AVI intermediate using GoPro Studio is an excellent workflow. You should continue doing that.

The "medium" and "high" settings (and the other settings in that same list) change the quality. You may not notice much difference unless you look closely. The Cineform intermediate codec was designed to produce extremely high quality "intermediate" video files. The term "intermediate" means that they are only used during the editing process, and when you have finished editing your videos, you then create a "delivery" format video using h.264 or some other highly-compressed, but still good-quality format.

You should experiment yourself with the quality settings. Render about twenty seconds of video which contains lots of detail and lots of motion. One of my favorite test clips is a stage-lit closeup of a ballet dancer wearing a sequined dress doing fast fouette turns across the stage. It has horizontal and rotational motion, lots of detail on the dress, and constant motion. I then render using the absolutely worst and the absolute best settings available for that codec. I then put those two on my NLE timeline, one above the other and A/B between them while playing. I set the preview quality in my NLE to the best quality. Sometimes I zoom way in on the result. I then look for mosquito noise, loss of detail, and artifacts on flat surfaces (such as the stage floor). I also A/B several freeze frames.

By using the two extremes, you should be able to quickly atune yourself to the artifacts that any particular video compression technique will add to your video.

Then, now knowing what sort of artifact I am looking for, I then try many of the other quality settings.

With Cineform, I found that I could use settings that are quite a bit below the maximum quality level, and I still couldn't see the difference.

BTW, since intermediate file formats are also designed so that you can render a few more times, and then use the results of that render back in your project (i.e., you will eventually be using 2nd, 3rd, or 4th generation video), you may also want to try making a copy of a copy of a copy for each of the extreme quality levels, and then doing the A/B on those pairs.

[Taurus]

One of my favorite test clips is a stage-lit closeup of a ballet dancer wearing a sequined dress
doing fast fouette turns across the stage.
It has horizontal and rotational motion, lots of detail on the dress, and constant motion.

Hi John,
would you mind sharing this sample?
I've been looking around quite some time for a good source to interpret the behaviour of different encoders.
I know there are a many test samples on the net.
But nothing really satisfied my needs.
Maybe your sample is what I'm looking for.
If you can't share it, I understand...

[johnmeyer]

I can't find the clip at the moment ... I'll post a link if I find it.

[Rickyasna43]

As already stated in earlier posts, converting to a Cineform AVI intermediate using GoPro Studio is an excellent workflow. You should continue doing that.

The "medium" and "high" settings (and the other settings in that same list) change the quality. You may not notice much difference unless you look closely. The Cineform intermediate codec was designed to produce extremely high quality "intermediate" video files. The term "intermediate" means that they are only used during the editing process, and when you have finished editing your videos, you then create a "delivery" format video using h.264 or some other highly-compressed, but still good-quality format.

You should experiment yourself with the quality settings. Render about twenty seconds of video which contains lots of detail and lots of motion. One of my favorite test clips is a stage-lit closeup of a ballet dancer wearing a sequined dress doing fast fouette turns across the stage. It has horizontal and rotational motion, lots of detail on the dress, and constant motion. I then render using the absolutely worst and the absolute best settings available for that codec. I then put those two on my NLE timeline, one above the other and A/B between them while playing. I set the preview quality in my NLE to the best quality. Sometimes I zoom way in on the result. I then look for mosquito noise, loss of detail, and artifacts on flat surfaces (such as the stage floor). I also A/B several freeze frames.

By using the two extremes, you should be able to quickly atune yourself to the artifacts that any particular video compression technique will add to your video.

Then, now knowing what sort of artifact I am looking for, I then try many of the other quality settings.

With Cineform, I found that I could use settings that are quite a bit below the maximum quality level, and I still couldn't see the difference.

BTW, since intermediate file formats are also designed so that you can render a few more times, and then use the results of that render back in your project (i.e., you will eventually be using 2nd, 3rd, or 4th generation video), you may also want to try making a copy of a copy of a copy for each of the extreme quality levels, and then doing the A/B on those pairs.

Amazing replay John, at this point i'll continue to use a gopro studio cineform workflow.
How do you have see, i'm not an expert about videomaking. I'm in trouble with this thing. After the conversion of the gopro native file in avi file using gopro studio, i'm usually putting them in sony vegas setting the project property as the resolution i want for the output mp4 edited file (ex. i set a video in 1920 × 1080 pixel with 60 fps). is it a correct procedure? On the web. i've read about a "CineForm Render Template in Sony Vegas Pro" (i've found it in a videomaker's site, Here the website (http://johnrofrano.com/training/video-tutorials/creating-cineform-templates/)). It is necessary in order to export the final edited file with the best quality? Thanks so much for your support.
Cheers

[johnmeyer]

Project properties should be set to one of these two settings:

1. If you want the fastest timeline performance, then use the "match" feature in the project properties to match the project properties to the video on the timeline.

2. If you plan to render to a frame rate and/or resolution that is different from your source video, and if you want to show exactly what the video will look like when you render it to this new size/rate, then change the project properties to match the output. However, the timeline performance will be significantly more sluggish.

Sony (now Magix) dropped support for Cineform many revisions ago. Therefore I don't know if there are any built-in templates anymore. However, if you have Cineform installed (and you do, because it gets installed when you installed GoPro Studio), you can still find the Cineform codec as an option under AVI. You will have to click on the custom settings to find it, and to set its properties (e.g., High/Medium etc.).

[Rickyasna43]

Project properties should be set to one of these two settings:

1. If you want the fastest timeline performance, then use the "match" feature in the project properties to match the project properties to the video on the timeline.

2. If you plan to render to a frame rate and/or resolution that is different from your source video, and if you want to show exactly what the video will look like when you render it to this new size/rate, then change the project properties to match the output. However, the timeline performance will be significantly more sluggish.

Sony (now Magix) dropped support for Cineform many revisions ago. Therefore I don't know if there are any built-in templates anymore. However, if you have Cineform installed (and you do, because it gets installed when you installed GoPro Studio), you can still find the Cineform codec as an option under AVI. You will have to click on the custom settings to find it, and to set its properties (e.g., High/Medium etc.).

Thanks you for your lessons John.
PS: I've tried to use VFAPI following the guide that you posted but unfortunatly it didn't run. Do you not help me about this problem?
Cheers

[johnmeyer]

There are other posts by me about VFAPI, both here and in VideoHelp. Search those and I think you'll find some answers.

[osgZach]

Why use VFAPI?

Why not use AVFS

http://turtlewar.org/avfs/

It works great for me so far. You can index your file / use whatever input plugin you want. Mount your script, navigate to the folder (C:\Volume\scriptname\ for me) and a signpost AVI file will be there.
I'm on Windows 10 as well, so I imagine it would work on any Windows version in recent memory

[Rickyasna43]

Why use VFAPI?

Why not use AVFS

http://turtlewar.org/avfs/

It works great for me so far. You can index your file / use whatever input plugin you want. Mount your script, navigate to the folder (C:\Volume\scriptname\ for me) and a signpost AVI file will be there.
I'm on Windows 10 as well, so I imagine it would work on any Windows version in recent memory

Hi osgZach and thanks for your replay.
I'm honest, i'm a novice of this world. Could you indicate me step by step how use AVFS like "index your file" or " Mount your script". How AVFS interact with Vegas? Is it need some Framework as DebugMode Framework?
Thanks a lot!

[osgZach]

I can write a small (haha it won't be small) guide for you with pictures and stuff, but it would have to be later, when I have some more time. (possibly tonight after work)


I have to stop and ask though, since it does not appear others have. Why did you buy Sony Vegas? You have made several references to being a novice (and it is apparent), and if true, Vegas is really not the kind of software you want to be starting out with (nor is it cheap. I only own it because I caught the least expensive version on sale).

There are a lot of other, more user/novice friendly editors out there. So I'm wondering how you arrived at this point is all. Vegas is Professional editing software, I use it because I happen to like the level of control and the no-fuss interface (I hate "consumer" GUIs) but I don't even understand 10% of what the program can be used to do.

I would like to know a couple things. Because we may be able to give you a very simple solution here that would suit your needs.

Your GoPro shoots footage in 1920x1080, at 60fps? Do you know if it is variable framerate at all?

Do you -prefer- to spend time converting to an AVI format and then import that into Vegas to work on?

I can give you a much easier solution that doesn't rely on Cinneform and is still virtually lossless. (from what I read earlier in the thread Cinneform isn't exactly lossless either?)

It may be a slow method though. But it should allow you to import the new file directly into Vegas.

I guess the ultimate question here is - what is your objective? Why are you now trying to use Avisynth to import GoPro into Vegas? Are you trying to save time by not having to do the file conversion? Or did someone simply tell you "oh use Avisynth its better" ??

If you don't mind sitting through file conversions, stick with the gopro method if that works for you. If you have concerns about how old Cinneform is, and future support and want a "drop-in" solution, then try the following:


all you need is FFMPEG - you can get the windows binaries from here https://ffmpeg.zeranoe.com/builds/

Select the architecture you need (if you have 32bit windows go with the x32, if you have 64-bit windows go with x64, etc)

For brevities sake, extract ffmpeg.exe from the downloaded file, and place it in the same directory as your gopro file.
Open a command prompt (Run -> cmd.exe ) and navigate to the same place your gopro file is.

then type this in


ffmpeg -i "name_of_gopro_file.mp4" -c:v libx264 -preset ultrafast -qp 1 -c:a copy "Newfile.mp4"


That will give you an MP4 that Sony Vegas should have no trouble importing. It may be slow as dirt on your machine though (I use a 6core/12thread CPU and it still dropped down to around 170FPS)
If its too slow, you can try raising the QP value. I have no experience with 60fps/real-life footage so I don't know how high you can safely raise it before you start losing too much detail. But I would try raising it to 5 or maybe 10 at the most, and you can be the judge. Don't raise it too high, because you still need good data there when you export it from Vegas. If you import in crap, you'll get crap out.


and like I said. If you're determined to use Avisynth and import the gopro file that way I can write you a guide later on tonight hopefully.

[Rickyasna43]

I can write a small (haha it won't be small) guide for you with pictures and stuff, but it would have to be later, when I have some more time. (possibly tonight after work)


I have to stop and ask though, since it does not appear others have. Why did you buy Sony Vegas? You have made several references to being a novice (and it is apparent), and if true, Vegas is really not the kind of software you want to be starting out with (nor is it cheap. I only own it because I caught the least expensive version on sale).

There are a lot of other, more user/novice friendly editors out there. So I'm wondering how you arrived at this point is all. Vegas is Professional editing software, I use it because I happen to like the level of control and the no-fuss interface (I hate "consumer" GUIs) but I don't even understand 10% of what the program can be used to do.

I would like to know a couple things. Because we may be able to give you a very simple solution here that would suit your needs.

Your GoPro shoots footage in 1920x1080, at 60fps? Do you know if it is variable framerate at all?

Do you -prefer- to spend time converting to an AVI format and then import that into Vegas to work on?

I can give you a much easier solution that doesn't rely on Cinneform and is still virtually lossless. (from what I read earlier in the thread Cinneform isn't exactly lossless either?)

It may be a slow method though. But it should allow you to import the new file directly into Vegas.

I guess the ultimate question here is - what is your objective? Why are you now trying to use Avisynth to import GoPro into Vegas? Are you trying to save time by not having to do the file conversion? Or did someone simply tell you "oh use Avisynth its better" ??

If you don't mind sitting through file conversions, stick with the gopro method if that works for you. If you have concerns about how old Cinneform is, and future support and want a "drop-in" solution, then try the following:


all you need is FFMPEG - you can get the windows binaries from here https://ffmpeg.zeranoe.com/builds/

Select the architecture you need (if you have 32bit windows go with the x32, if you have 64-bit windows go with x64, etc)

For brevities sake, extract ffmpeg.exe from the downloaded file, and place it in the same directory as your gopro file.
Open a command prompt (Run -> cmd.exe ) and navigate to the same place your gopro file is.

then type this in


ffmpeg -i "name_of_gopro_file.mp4" -c:v libx264 -preset ultrafast -qp 1 -c:a copy "Newfile.mp4"


That will give you an MP4 that Sony Vegas should have no trouble importing. It may be slow as dirt on your machine though (I use a 6core/12thread CPU and it still dropped down to around 170FPS)
If its too slow, you can try raising the QP value. I have no experience with 60fps/real-life footage so I don't know how high you can safely raise it before you start losing too much detail. But I would try raising it to 5 or maybe 10 at the most, and you can be the judge. Don't raise it too high, because you still need good data there when you export it from Vegas. If you import in crap, you'll get crap out.


and like I said. If you're determined to use Avisynth and import the gopro file that way I can write you a guide later on tonight hopefully.

Thanks you for your great support! As i said before, i'm a novice of this wolrd and i'm determined to learn about these software. I choose to try to change my workflow in order to accelerate the conversion process from mp4 to avi and then after edited the avi file recovert it in a finale mp4. At the same time, i would use other camera in the future (not only gopro) and if it happens, i've no idea how convert file from different camera (and i think different file format) in order to edit the file all togheter in an only workflow. So, i've a lot of trouble! :D

You give me a hope! :D
Cheers

[osgZach]

Most modern cameras will likely give you a file in MP4 or M2TS or some container like that. Hopefully they will also be much less of a hassle to import into Vegas.
Something to keep in mind with regards to saving time. Its quite possible that the whole process of importing the GoPro footage into Vegas with Avisynth may allow you to do your work and then encode the output.
But its also possible that bottlenecks introduced with Avisynth could end up slowing the render process down as well.

You may end up with no real change in the total time it takes, or you may end up with an increase. It really depends on the situation.

I will try to write up a guide for you in the future, I just got home and had a long day so I'm kind of beat. Maybe in the next 1 or 2 days I can write a guide up with pictures and stuff for you to understand. (unless someone else wants to do it)

[Rickyasna43]

Most modern cameras will likely give you a file in MP4 or M2TS or some container like that. Hopefully they will also be much less of a hassle to import into Vegas.
Something to keep in mind with regards to saving time. Its quite possible that the whole process of importing the GoPro footage into Vegas with Avisynth may allow you to do your work and then encode the output.
But its also possible that bottlenecks introduced with Avisynth could end up slowing the render process down as well.

You may end up with no real change in the total time it takes, or you may end up with an increase. It really depends on the situation.

I will try to write up a guide for you in the future, I just got home and had a long day so I'm kind of beat. Maybe in the next 1 or 2 days I can write a guide up with pictures and stuff for you to understand. (unless someone else wants to do it)

Wonderful! Thank you again!

[osgZach]

Hi, I just wanted to let you know, I'm working on the guide in my free time. It's not something I can particularly spend an hour or more dedicated to working on, as I've got a lot of things going on outside of work. But I am writing it, it's going to be in a PDF document format so hopefully it will be useful to everyone when I am finished.

I don't have an ETA, I'm sorry. I was going to write very quick and dirty instructions for you but I figured I better do it this way instead. Again maybe someone else can come up with something quicker, but I'll be working on it as time allows. Maybe done by the weekend? I have a busy Friday and Saturday (its superbowl weekend and I work in retail sales as a merchandiser) but I have Sunday off so hopefully it'll be done by then.

[nhope]

First of all, as I think you already know, Sony Vegas 13 (and probably 14) has problems reading native GoPro files. There is a fix for that which you can find with Google. It involves copying a DLL file from a previous Vegas version. You can then edit the files directly without first converting them in Studio (although that actually is a pretty good workflow, and I'd recommend you stick with it)...

Hi John, The awful GoPro playback issue existed in Vegas Pro 12 and in Vegas Pro 13 up to build 444. It was fixed in VP13 build 453 and it's still OK in VP14 build 211. My 2.7k-59.94p Hero5 footage is playing on the timeline here at full frame rate at "Preview (Full)" preview quality.

The VP11 DLL hack that you refer to is described here (https://www.vegascreativesoftware.info/us/forum/why-does-vegas-choke-on-gopro-1080p60-files--96065/?page=2#ca588312), including a link to download the DLL.

[osgZach]

well.. that's interesting

Ricky have you ever tried importing your footage directly, in the recent past?

[johnmeyer]

Hi John, The awful GoPro playback issue existed in Vegas Pro 12 and in Vegas Pro 13 up to build 444. It was fixed in VP13 build 453 and it's still OK in VP14 build 211. My 2.7k-59.94p Hero5 footage is playing on the timeline here at full frame rate at "Preview (Full)" preview quality.That's good to know. Thanks!

I don't think the OP ever posted what build he was using, just that it was VP13.

I guess I should check if I ever updated to the last version. I got so discouraged with both Vegas and Sony (and even more now with Magix) that I didn't pay much attention to new versions.

[Rickyasna43]

well.. that's interesting

Ricky have you ever tried importing your footage directly, in the recent past?

Yes, but i'm not sure that Sony Vegas read the gopro file at the best quality (also with a full frame preview). Until now, i'm normally converting the native mp4 gopro file and then converting it in a cineform avi file.

I've check just now, i'm using Sony Vegas Pro 13.0 Build 290, so as nhope said, probably i'll have some trouble to manage directly mp4 gopro file on the timeline without loosing quality, it is right?

I've just change the DLL file using that guide (https://www.vegascreativesoftware.info/us/forum/why-does-vegas-choke-on-gopro-1080p60-files--96065/?page=2#ca588312), but honestly, i've not seen any significat difference from before and after change the DLL's file.

Finally, thanks you again osgZach to spend your free time in order to help me with FFMPEG!
Cheers

[nhope]

I've check just now, i'm using Sony Vegas Pro 13.0 Build 290, so as nhope said, probably i'll have some trouble to manage directly mp4 gopro file on the timeline without loosing quality, it is right?
The "quality" will be OK but it will just skip frames during playback.

I've just change the DLL file using that guide (https://www.vegascreativesoftware.info/us/forum/why-does-vegas-choke-on-gopro-1080p60-files--96065/?page=2#ca588312), but honestly, i've not seen any significat difference from before and after change the DLL's file.

Why not update? There are 5 bugfix builds (http://download.sonymediasoftware.com/releasenotes/vegaspro13.0.453_readme_enu.htm) since the one you have. Also there are lots of suggestions for improving playback in this thread (https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-make-my-video-preview-play-smoothly-in-vegas-pro--104624/).

[Rickyasna43]

The "quality" will be OK but it will just skip frames during playback.



Why not update? There are 5 bugfix builds (http://download.sonymediasoftware.com/releasenotes/vegaspro13.0.453_readme_enu.htm) since the one you have. Also there are lots of suggestions for improving playback in this thread (https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-make-my-video-preview-play-smoothly-in-vegas-pro--104624/).
I've see the changelog, I'll update the software as soon as possible

Inviato dal mio Mi-4c utilizzando Tapatalk

[Rickyasna43]

Hi, I just wanted to let you know, I'm working on the guide in my free time. It's not something I can particularly spend an hour or more dedicated to working on, as I've got a lot of things going on outside of work. But I am writing it, it's going to be in a PDF document format so hopefully it will be useful to everyone when I am finished.

I don't have an ETA, I'm sorry. I was going to write very quick and dirty instructions for you but I figured I better do it this way instead. Again maybe someone else can come up with something quicker, but I'll be working on it as time allows. Maybe done by the weekend? I have a busy Friday and Saturday (its superbowl weekend and I work in retail sales as a merchandiser) but I have Sunday off so hopefully it'll be done by then.

Hello osgZach and sorry for the double post.
Have you complete your instructions for me? I won't give you hurry, but i've never receive any information for a long time. Thanks you again for your great support!
Cheers