Next VIRB Edit

@RuiTerrinha
I love all your ideas and I wish we could do all of them! Sadly, we have so many things lined up I don't think we'll be able to get to most of them. That said, at least some of your suggestions are possible without developer support.

2) Adding Audio
Would it be possible to cut the audio? Some times when we import audio files, they contain some silence in the beginning or at the end of the song, or we just plain and simple just want a small portion of a full song, allowing some "cutting" would be super cool.

I've felt like this was a really important feature for a video editor to have for a long time, but I have not succeeded in convincing anyone else of this :( I'll keep trying.

4) shutdown your computer, because saving energy matters

Earlier in this thread, I mentioned it is possible to run an export from the command line. This means you can make exporting a step in a batch file, which should also support shutting the computer down. Follow my guide from earlier in the thread, create a text file in the same folder as VirbEdit with the following lines:

VirbExport.exe "C:\Users\<your username>\AppData\Local\Temp\Garmin\Virb\export_settings.xml" #Make sure you substitute the appropriate thing for <your username>
shutdown -s

rename the file to "ExportThenShutdown.bat" and double click it and you are good to go. I don't win double or triple points with this solution though :(
(Thanks to https://stackoverflow.com/questions/162304/how-do-i-shutdown-restart-logoff-windows-via-a-bat-file for advice on shutting down from the command line)

3) Export All the things!

Other people have requested this as well, and it turns out it is possible already, with some caveats. See https://forums.garmin.com/showthread.php?374824-Bulk-Video-Processing for my description on how to do batch exports. I'll admit it is a little clunky. Since MediaFoundation.tests.exe is not an "official" part of the app I have a little more freedom to do what I want with it. Maybe I'll sneak some changes in there to make it a little easier to batch export under the guise of better automated testing :D

5) Video name while exporting

7) Videos optimization on import

These two aren't heavy duty features, I'll break out my politician hat today and see if I can convince the right people to do these.

8) GPU rendering support
I been reading about this and it's just not easy to understand IF virb edit uses GPU for rendering, if any of the encoders uses GPU and if so, witch one.

Unfortunately, it is not easy to tell you if and when the GPU will get used. Spoiler alert: we've done a big export performance push in this version of VirbEdit, so the GPU gets used a lot more than it used to. Many of the technologies we use now default to using the GPU and fall back CPU if that doesn't work. We have custom code that similarly has software fall backs depending on hardware support and your operating system. So there isn't a way to definitively tell the user what technologies will be used when because it kind of depends on your machine. With decoders, in general: Dxva uses your GPU, ffmpeg uses the CPU and MediaFoundation uses whatever Microsoft, in its infinite wisdom, decides it should use. In 4.2.3, none of our encoders use the GPU. In VirbEdit Next, they all do, sometimes.

I've felt like this was a really important feature for a video editor to have for a long time, but I have not succeeded in convincing anyone else of this :( I'll keep trying.

Cutting the audio file would be awesome, as well as the ability to fade added music at the end of a clip :D

@Purdington Thank you.

@RuiTerrinha
I love all your ideas and I wish we could do all of them! Sadly, we have so many things lined up I don't think we'll be able to get to most of them. That said, at least some of your suggestions are possible without developer support.



I've felt like this was a really important feature for a video editor to have for a long time, but I have not succeeded in convincing anyone else of this :( I'll keep trying.


Earlier in this thread, I mentioned it is possible to run an export from the command line. This means you can make exporting a step in a batch file, which should also support shutting the computer down. Follow my guide from earlier in the thread, create a text file in the same folder as VirbEdit with the following lines:

VirbExport.exe "C:\Users\<your username>\AppData\Local\Temp\Garmin\Virb\export_settings.xml" #Make sure you substitute the appropriate thing for <your username>
shutdown -s

rename the file to "ExportThenShutdown.bat" and double click it and you are good to go. I don't win double or triple points with this solution though :(
(Thanks to https://stackoverflow.com/questions/162304/how-do-i-shutdown-restart-logoff-windows-via-a-bat-file for advice on shutting down from the command line)


Other people have requested this as well, and it turns out it is possible already, with some caveats. See https://forums.garmin.com/showthread.php?374824-Bulk-Video-Processing for my description on how to do batch exports. I'll admit it is a little clunky. Since MediaFoundation.tests.exe is not an "official" part of the app I have a little more freedom to do what I want with it. Maybe I'll sneak some changes in there to make it a little easier to batch export under the guise of better automated testing :D




These two aren't heavy duty features, I'll break out my politician hat today and see if I can convince the right people to do these.


Unfortunately, it is not easy to tell you if and when the GPU will get used. Spoiler alert: we've done a big export performance push in this version of VirbEdit, so the GPU gets used a lot more than it used to. Many of the technologies we use now default to using the GPU and fall back CPU if that doesn't work. We have custom code that similarly has software fall backs depending on hardware support and your operating system. So there isn't a way to definitively tell the user what technologies will be used when because it kind of depends on your machine. With decoders, in general: Dxva uses your GPU, ffmpeg uses the CPU and MediaFoundation uses whatever Microsoft, in its infinite wisdom, decides it should use. In 4.2.3, none of our encoders use the GPU. In VirbEdit Next, they all do, sometimes.

Something I definitely would like to see in the future:

• Cut videos
  

Sounds simple and maybe it really is... The most, if not every, recording starts too early and stops too late. Often with the annoying sound of the recording leaver.
These are parts, which I want to remove permanently.Without rendering, without creating a new video and without the space on my harddisk.

It would be great to pre-edit the recordings and leave them ready to use for later editing.

I would like to see editing profiles saved in a user accessable place - so that when updating the various VIRB Edit updates the user doesn't lose a profile they have spent time perfecting for their own videos.