Thank you Vegas Team!

adimatis wrote on 8/4/2020, 3:13 PM

First and foremost, I apologize if there was a thread already on this, feel free to merge them if so.

I just wanted to say a thank you to the Vegas team for the release of Vegas 18!

@VEGASDerek , @VEGASPascal , @GaryRebholz etc

Most of the threads about the new version, as expected, will describe various problems which are inevitable for a first release. We all would like to see as many improvements as possible and I think we all need to make a conscious decision to refrain from jumping too quickly into expressing frustrations already.

It might be a time for that too! :) But later.

For now, I think we all should appreciate the new release and the efforts that were put in for it.

I watched Gary's presentation on Monday and I read a lot of posts here on the forum, I am very excited to test v18 myself. I hope it will allow me to test it properly, I hope some of the bad show-stopper (for me) issues are gone. I think we all just need to allow this to be a time of celebrating and give the frustrations a little bit of a break.

Even if all will not be perfect and I will end up not using Vegas that much - if that will prove to be impossible, due to my own particular system maybe - I still want to appreciate the new release and the team efforts.

So, here it is, THANK YOU and looking forward for what's coming!

Keep at it!!

Adi

Comments

supergafudo wrote on 8/4/2020, 4:06 PM

there are some people clearly boycoting the launch, but instead of understand this, moderators close the thread when someone, me in this case, expose the situation.

People calling "bugs" situations when you paste 30 instances of videos and deleted then one by one, but hey, only when the timeline is still playing, a totally normal usage :-)))) ah, I forget, you also need to use two different specific codecs, to reproduce the terrible bug that makes vegas unusable and will make all of us go to Resolve. Is hilarious.

there is something really strange in this forum members and in all of this situation, everyone that have been reading the forum for a while knows it.

but if the moderators would like to prefer closing the threads and allowing this situacion continue is their problem, I am not going to defend people that act this way against the users that try to defend the software and the evident boicot is suffering, against their own programers, and their company, but they prefer to allow all of this people bashing his own software and silence the ones that really understand this is not normal.

You are being demoralized, the software is amazing, I am using it in a computer from 2007 with no problem, so please, exhibit a bit of respect for yourself and do not allow this people boicot your work.

All this people that post this "bugs" could start to put their files in the cloud and gives other permision to download to see all of this terrible things and problems they are having. I will tell you that 99% is just bullshit.

vkmast wrote on 8/4/2020, 4:19 PM

@supergafudo the thread was closed as it was going offtopic due to several personal attacks violating the Community rules, esp. #1:

supergafudo wrote on 8/4/2020, 4:30 PM

@supergafudo the thread was closed as it was going offtopic due to several personal attacks violating the Community rules, esp. #1:

I understand sir, but this guys are deliberately bashing your work continuosly during a lot of months and with the new release of 18 they have downloaded the demo and of course, instead of checking the new features, the sounforge thing etc.. etc.. they have, surprise, find "bugs" few minutes lates than the demo is released. This is just not normal.

I will not post more, but just want to make this clear, there are people that are acting in a very strange ways in this forum, so when someone read the forum and think about to use the software could understand this.

Steve_Rhoden wrote on 8/4/2020, 6:17 PM

adimatis, Well said!.... Very pleased with what i am seeing in Vegas Pro 18 and very proud of the team.... It's not perfect, still a few issues, but so much has been improved along with some good additional features.... Hoping many of your past issues will be resolved.

lenard-p wrote on 8/4/2020, 8:13 PM

 

I will not post more, but just want to make this clear, there are people that are acting in a very strange ways in this forum, so when someone read the forum and think about to use the software could understand this.

There's no conspiracy against Magix by other NLE makers or cartel's of ex users trying to ruin the company. You said you have a 2007? era computer, ofcourse you don't have the problems normal people do. For you, you basically are still running sony vegas as at it's core that's what it still is, you don't have the hardware to take advantage of speed improvements introduced over the years that also make it unstable for some

So an appreciation thread. Well done guys!

joseph-desaavedra wrote on 8/4/2020, 8:28 PM

yeah well gonna roll the dice and pick up 18, I got 2020 hardware bugs be damned. Just hope it don't crash for the same reasons 17 does. Onward.

 CPU Name
AMD Ryzen Threadripper 1950X 16-Core Processor
Threading
1 CPU - 16 Core - 32 Threads
Frequency
3466.73 MHz (34.75 * 99.76 MHz) - Uncore: 1596.2 MHz
Multiplier
Current: 34.75
Architecture
Threadripper / Stepping: ZP-B1 / Technology: 14 nm
CPUID / Ext.
F.1.1 / 17.1
IA Extensions
MMX(+), SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, SSE4A, x86-64, AMD-V, AES, AVX, AVX2, FMA3, SHA
Caches
L1D : 32 KB / L2 : 512 KB / L3 : 8192 KB
Caches Assoc.
L1D : 8-way / L2 : 8-way / L3 : 16-way
Microcode
Rev. 0x8001137
TDP / Vcore
180 Watts / 1.212 Volts
Temperature
63.5 °C / 146 °F
Type
Retail
Cores Frequencies
#00: 3466.73 MHz #01: 3491.67 MHz #02: 3466.73 MHz #03: 3466.73 MHz
#04: 3491.67 MHz #05: 3491.67 MHz #06: 3466.73 MHz #07: 3466.73 MHz
#08: 3491.67 MHz #09: 3441.79 MHz #10: 3491.67 MHz #11: 3466.73 MHz
#12: 3466.73 MHz #13: 3491.67 MHz #14: 3466.73 MHz #15: 3466.73 MHz
Motherboard
Model
Gigabyte X399 AORUS XTREME-CF
Socket
Socket SP3r2 (4094)
North Bridge
AMD Ryzen SOC rev 00
South Bridge
AMD X399 rev 51
BIOS
American Megatrends Inc. F5i (05/08/2019)
AMD AGESA
SummitPI-SP3r2-1.1.0.2
Memory (RAM)
Total Size
32768 MB
Type
Quad Channel (256 bit) DDR4-SDRAM
Frequency
1596.2 MHz (DDR4-3192) - Ratio 1:16
Timings
16-18-18-38-56-1 (tCAS-tRC-tRP-tRAS-tCS-tCR)
Slot #1 Module
G.Skill 8192 MB (DDR4-2137) - XMP 2.0 - P/N: F4-3200C16-8GTZR
Slot #2 Module
G.Skill 8192 MB (DDR4-2137) - XMP 2.0 - P/N: F4-3200C16-8GTZR
Slot #3 Module
G.Skill 8192 MB (DDR4-2137) - XMP 2.0 - P/N: F4-3200C16-8GTZR
Slot #4 Module
G.Skill 8192 MB (DDR4-2137) - XMP 2.0 - P/N: F4-3200C16-8GTZR
Graphic Card (GPU)
GPU Type
NVIDIA GeForce RTX 2080 Ti (TU102-300) @ 300 MHz
GPU Brand
EVGA Corp.
GPU Specs
TU102-300 / Process: 12nm / Transistors: 18600M / Die Size: 754 mm² / TDP: 260W
GPU Units
Shader Units: 4352 / Texture Units (TMU): 272 / Render Units (ROP): 88
GPU VRAM
11264 MB GDDR6 352 bit @ 405 MHz (Samsung)
GPU APIs
DirectX 12.0 (12_1) / OpenGL 4.5 / OpenCL 1.2 / Vulkan 1.0
Storage (HDD/SSD)
Model #1 Name
Seagate ST8000VN0022-2EL112 (FW: SC61)
Model #1 Capacity
7452.0 GiB (~8010 GB)
Model #1 Type
Fixed - Bus: SATA (11)
Model #2 Name
Samsung SSD 970 PRO 512GB
Model #2 Capacity
476.9 GiB (~510 GB)
Model #2 Type
Fixed, SSD - Bus: NVMe (17)
Model #3 Name
Samsung SSD 960 PRO 1TB
Model #3 Capacity
953.9 GiB (~1020 GB)
Model #3 Type
Fixed, SSD - Bus: NVMe (17)
Model #4 Name
Samsung SSD 970 PRO 512GB
Model #4 Capacity
476.9 GiB (~510 GB)
Model #4 Type
Fixed, SSD - Bus: NVMe (17)
Model #5 Name
Samsung SSD 970 PRO 512GB
Model #5 Capacity
476.9 GiB (~510 GB)
Model #5 Type
Fixed, SSD - Bus: NVMe (17)
Display
Screen #1
Dell Computer DELL P4317Q (DELD084)
Screen #1 Spec
42.5 inches (108 cm) / 3840 x 2160 pixels @ 23-80 Hz
Miscellaneous
Windows Version
Microsoft Windows 10 (10.0) Professional 64-bit
Windows Subver.
Build 18362
CPU-Z Version
1.90.0 (64 bit)

adimatis wrote on 8/5/2020, 3:02 AM

That's the spirit!

@supergafudo :) Look, I do get you. Really. But equally, not all problems are the same, so please allow for an honest and legit issues to exist and be expressed.

I suspect actually, as I said it before, that many frustrations are raised simply because people here love Vegas and want maybe too much of it.... Like a proper pizza - you eat more and more, beyond what would be reasonable. What about that for an analogy? ;) No conspiracy, no boycott.

To keep this straight, from what I got so far, I think the new Motion Tracking is a very welcome improvement. Also the new anti-flicker and denoise plugin, if they are effective, have not tried it yet.

I wish the UI was revisited too, but for now I'll settle for what it is.

I will try v18 more in depth of course, hopefully sooner than later.

But yeah, it is appreciated.

And thanks @Steve_Rhoden

 

fr0sty wrote on 8/5/2020, 3:25 AM

There actually are some changes to the UI... the effects and transitions panels got an overhaul (same as what is in the new VMS), and there's other minor tweaks like being able to export your settings, and VEGAS remembering where the play head was located when you re-open a project (which is a feature one user on here was VERY vocal about... to the point of it causing problems).

We're off to a good start. It isn't perfect, I have managed to make it crash twice since release, but the vast majority of the time, it runs fast it runs smooth, and it runs stable. Rendering times are as much as twice as fast, projects load as much as 1/3 faster (even complex ones)... the work the team did to improve the video playback engine and VEGAS' code in general is really starting to show. If we're already this well off on the initial release, I can't wait to see where we end up after a few updates. I also know of some REALLY cool features (some that some users on here have been requesting for a long time, saying that it makes VEGAS not "pro" compared to other NLEs) that are coming with these updates, that didn't make it into the launch release.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Radeon VII

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Paul-Fierlinger wrote on 8/5/2020, 7:02 AM

I got a wonderful surprise coming with 18. I use "Render to new track" very frequently and to carry the change back to its source I have to play the new track from the timeline but would get an error warning that it can't be done without deleting the current sound clip. When I called this a bug on the forum someone explained to me that it's not a bug but by design etc. so I had to settle for an awkward workaround. I've had this problem since Vegas 6 I believe but 18 has it fixed! I have a feeling that I am the only user with this workflow and am delighted that someone fixed it for me alone (really?). I surmise that it has been fixed to work as expected for both sides; those who don't consider it a bug and the one who does. What joy!!!

VEGASPascal wrote on 8/5/2020, 8:53 AM

I got a wonderful surprise coming with 18. I use "Render to new track" very frequently and to carry the change back to its source I have to play the new track from the timeline but would get an error warning that it can't be done without deleting the current sound clip. When I called this a bug on the forum someone explained to me that it's not a bug but by design etc. so I had to settle for an awkward workaround. I've had this problem since Vegas 6 I believe but 18 has it fixed! I have a feeling that I am the only user with this workflow and am delighted that someone fixed it for me alone (really?). I surmise that it has been fixed to work as expected for both sides; those who don't consider it a bug and the one who does. What joy!!!

🤔😅

 

aboammar wrote on 8/5/2020, 7:52 PM

@adimatis "To keep this straight, from what I got so far, I think the new Motion Tracking is a very welcome improvement." I did not notice any change in the Motion Tracking! What is new exactly?

HP Z1 AIO Workstation G3

OS: Windows 10 Pro 64bit

Display: 23.6" UHD 4K

CPU: Xeon E3-1270 v5  quad-core @ 3.60GHz, 8MB cache, up to 4GHz with Intel Turbo Boost Technology

GPU: nVidia Quadro M2000M 4GB

RAM: 32GB DDR4 2133MHz ECC memory

System Drive: 1TB M.2 (2500MB/s)

Working Drive: 1TB M.2 (2500MB/s)

Storage Drive: 3GB SSD (500MB/s)

Video: Vegas Pro 16 Suite / DaVinci Resolve 16 Studio

Audio: PreSonus Studio One Pro 5

Graphics: CorelDraw Technical Suite 2020 / Xara Designer Pro X365

Image Editing: Corel PhotoPaint 2020 / Corel PaintShop Pro X9 Ultimate / PHASEONE Capture One Pro 11

3D Graphics: Maxon Cinema 4D Studio 10

Camera: Sony A7S II / A7 III

Website: www.innoviahouse.com

Vimeo: vimeo.com/innoviahouse

aboammar wrote on 8/5/2020, 8:33 PM

There actually are some changes to the UI... the effects and transitions panels got an overhaul (same as what is in the new VMS), and there's other minor tweaks like being able to export your settings, and VEGAS remembering where the play head was located when you re-open a project (which is a feature one user on here was VERY vocal about... to the point of it causing problems).

We're off to a good start. It isn't perfect, I have managed to make it crash twice since release, but the vast majority of the time, it runs fast it runs smooth, and it runs stable. Rendering times are as much as twice as fast, projects load as much as 1/3 faster (even complex ones)... the work the team did to improve the video playback engine and VEGAS' code in general is really starting to show. If we're already this well off on the initial release, I can't wait to see where we end up after a few updates. I also know of some REALLY cool features (some that some users on here have been requesting for a long time, saying that it makes VEGAS not "pro" compared to other NLEs) that are coming with these updates, that didn't make it into the launch release.

@fr0sty "VEGAS remembering where the play head was located when you re-open a project"

BTW, Vegas Pro 17 also remember the last location of the play head when project is reopened! So am I missing something here?

As for rendering time, I did a test comparison between V17 and V18 for the same project and V18 is a little faster, but far away from twice as fast as you said! V17 finished rendering in 51 seconds and V18 finished it in 45 seconds! Loading projects is a little bit fast in V18 but not by much in my test!

Last changed by aboammar on 8/5/2020, 8:35 PM, changed a total of 1 times.

HP Z1 AIO Workstation G3

OS: Windows 10 Pro 64bit

Display: 23.6" UHD 4K

CPU: Xeon E3-1270 v5  quad-core @ 3.60GHz, 8MB cache, up to 4GHz with Intel Turbo Boost Technology

GPU: nVidia Quadro M2000M 4GB

RAM: 32GB DDR4 2133MHz ECC memory

System Drive: 1TB M.2 (2500MB/s)

Working Drive: 1TB M.2 (2500MB/s)

Storage Drive: 3GB SSD (500MB/s)

Video: Vegas Pro 16 Suite / DaVinci Resolve 16 Studio

Audio: PreSonus Studio One Pro 5

Graphics: CorelDraw Technical Suite 2020 / Xara Designer Pro X365

Image Editing: Corel PhotoPaint 2020 / Corel PaintShop Pro X9 Ultimate / PHASEONE Capture One Pro 11

3D Graphics: Maxon Cinema 4D Studio 10

Camera: Sony A7S II / A7 III

Website: www.innoviahouse.com

Vimeo: vimeo.com/innoviahouse

RogerS wrote on 8/5/2020, 11:14 PM

@adimatis "To keep this straight, from what I got so far, I think the new Motion Tracking is a very welcome improvement." I did not notice any change in the Motion Tracking! What is new exactly?

It's pretty different with how it can be applied to other Fx. See here for a simple tutorial:

For loading and rendering time, you really need to try with a more complex project that taxed VP 17.

adimatis wrote on 8/6/2020, 12:12 AM

@aboammar Unless you are thinking Track Motion, which is of course something else completely and that one has not been changed at all, true.

fr0sty wrote on 8/6/2020, 2:29 AM

There actually are some changes to the UI... the effects and transitions panels got an overhaul (same as what is in the new VMS), and there's other minor tweaks like being able to export your settings, and VEGAS remembering where the play head was located when you re-open a project (which is a feature one user on here was VERY vocal about... to the point of it causing problems).

We're off to a good start. It isn't perfect, I have managed to make it crash twice since release, but the vast majority of the time, it runs fast it runs smooth, and it runs stable. Rendering times are as much as twice as fast, projects load as much as 1/3 faster (even complex ones)... the work the team did to improve the video playback engine and VEGAS' code in general is really starting to show. If we're already this well off on the initial release, I can't wait to see where we end up after a few updates. I also know of some REALLY cool features (some that some users on here have been requesting for a long time, saying that it makes VEGAS not "pro" compared to other NLEs) that are coming with these updates, that didn't make it into the launch release.

@fr0sty "VEGAS remembering where the play head was located when you re-open a project"

BTW, Vegas Pro 17 also remember the last location of the play head when project is reopened! So am I missing something here?

As for rendering time, I did a test comparison between V17 and V18 for the same project and V18 is a little faster, but far away from twice as fast as you said! V17 finished rendering in 51 seconds and V18 finished it in 45 seconds! Loading projects is a little bit fast in V18 but not by much in my test!

Here is the test I did, I recorded it on video. This is done in a VERY complex project that took months to finish to my expectations, contains half a terabyte of video from 5 camera angles from 3 different types of cameras shot at 2 different bit depths (8 and 10 bit), and there's hundreds, if not into the thousands, of cuts, coloring effects added to individual clips, etc.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Radeon VII

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

adimatis wrote on 8/6/2020, 2:56 AM

I'd like to add also that the horrible issues with the Stabilizer - which rendered (pun intended) it useless for me - seems to be gone now in v18. Not enough testing, but I hope it is true.

Overall it feels somehow quicker, more responsive. I also believe the GPU does more indeed, for the timeline playback that is.

Except I cannot render... :( https://www.vegascreativesoftware.info/us/forum/vegas-18-rendering-error--122866/

klapkowscy.com wrote on 8/6/2020, 3:05 AM

Unfortunately, from version 9 to version 17, I was and I am happy every time, unfortunately, the 18 version of the lime does not even start for me. I paid for something that I do not have and they do not even regret help in solving the problem

RogerS wrote on 8/6/2020, 3:13 AM

Unfortunately, from version 9 to version 17, I was and I am happy every time, unfortunately, the 18 version of the lime does not even start for me. I paid for something that I do not have and they do not even regret help in solving the problem


18 not starting when you have a bunch of old versions is likely do to an old Fx conflicting with startup. Did you file a support request? You can also search here for how to temporarily move/disable add-ons so Vegas can start.

There is a FAQ on start-up here: https://www.vegascreativesoftware.info/us/forum/faq-vegas-pro-won-t-start-what-can-i-do--104784/

aboammar wrote on 8/6/2020, 5:03 AM

@aboammar Unless you are thinking Track Motion, which is of course something else completely and that one has not been changed at all, true.

You are right, I got confused with Track Motion 😅

Last changed by aboammar on 8/6/2020, 5:04 AM, changed a total of 1 times.

HP Z1 AIO Workstation G3

OS: Windows 10 Pro 64bit

Display: 23.6" UHD 4K

CPU: Xeon E3-1270 v5  quad-core @ 3.60GHz, 8MB cache, up to 4GHz with Intel Turbo Boost Technology

GPU: nVidia Quadro M2000M 4GB

RAM: 32GB DDR4 2133MHz ECC memory

System Drive: 1TB M.2 (2500MB/s)

Working Drive: 1TB M.2 (2500MB/s)

Storage Drive: 3GB SSD (500MB/s)

Video: Vegas Pro 16 Suite / DaVinci Resolve 16 Studio

Audio: PreSonus Studio One Pro 5

Graphics: CorelDraw Technical Suite 2020 / Xara Designer Pro X365

Image Editing: Corel PhotoPaint 2020 / Corel PaintShop Pro X9 Ultimate / PHASEONE Capture One Pro 11

3D Graphics: Maxon Cinema 4D Studio 10

Camera: Sony A7S II / A7 III

Website: www.innoviahouse.com

Vimeo: vimeo.com/innoviahouse

aboammar wrote on 8/6/2020, 5:05 AM

@adimatis "To keep this straight, from what I got so far, I think the new Motion Tracking is a very welcome improvement." I did not notice any change in the Motion Tracking! What is new exactly?

It's pretty different with how it can be applied to other Fx. See here for a simple tutorial:

For loading and rendering time, you really need to try with a more complex project that taxed VP 17.

Thanks for the clarification 👍

HP Z1 AIO Workstation G3

OS: Windows 10 Pro 64bit

Display: 23.6" UHD 4K

CPU: Xeon E3-1270 v5  quad-core @ 3.60GHz, 8MB cache, up to 4GHz with Intel Turbo Boost Technology

GPU: nVidia Quadro M2000M 4GB

RAM: 32GB DDR4 2133MHz ECC memory

System Drive: 1TB M.2 (2500MB/s)

Working Drive: 1TB M.2 (2500MB/s)

Storage Drive: 3GB SSD (500MB/s)

Video: Vegas Pro 16 Suite / DaVinci Resolve 16 Studio

Audio: PreSonus Studio One Pro 5

Graphics: CorelDraw Technical Suite 2020 / Xara Designer Pro X365

Image Editing: Corel PhotoPaint 2020 / Corel PaintShop Pro X9 Ultimate / PHASEONE Capture One Pro 11

3D Graphics: Maxon Cinema 4D Studio 10

Camera: Sony A7S II / A7 III

Website: www.innoviahouse.com

Vimeo: vimeo.com/innoviahouse

aboammar wrote on 8/6/2020, 5:09 AM

There actually are some changes to the UI... the effects and transitions panels got an overhaul (same as what is in the new VMS), and there's other minor tweaks like being able to export your settings, and VEGAS remembering where the play head was located when you re-open a project (which is a feature one user on here was VERY vocal about... to the point of it causing problems).

We're off to a good start. It isn't perfect, I have managed to make it crash twice since release, but the vast majority of the time, it runs fast it runs smooth, and it runs stable. Rendering times are as much as twice as fast, projects load as much as 1/3 faster (even complex ones)... the work the team did to improve the video playback engine and VEGAS' code in general is really starting to show. If we're already this well off on the initial release, I can't wait to see where we end up after a few updates. I also know of some REALLY cool features (some that some users on here have been requesting for a long time, saying that it makes VEGAS not "pro" compared to other NLEs) that are coming with these updates, that didn't make it into the launch release.

@fr0sty "VEGAS remembering where the play head was located when you re-open a project"

BTW, Vegas Pro 17 also remember the last location of the play head when project is reopened! So am I missing something here?

As for rendering time, I did a test comparison between V17 and V18 for the same project and V18 is a little faster, but far away from twice as fast as you said! V17 finished rendering in 51 seconds and V18 finished it in 45 seconds! Loading projects is a little bit fast in V18 but not by much in my test!

Here is the test I did, I recorded it on video. This is done in a VERY complex project that took months to finish to my expectations, contains half a terabyte of video from 5 camera angles from 3 different types of cameras shot at 2 different bit depths (8 and 10 bit), and there's hundreds, if not into the thousands, of cuts, coloring effects added to individual clips, etc.

Thanks.. It seems the improvement difference shows more with complex projects, not small ones!

HP Z1 AIO Workstation G3

OS: Windows 10 Pro 64bit

Display: 23.6" UHD 4K

CPU: Xeon E3-1270 v5  quad-core @ 3.60GHz, 8MB cache, up to 4GHz with Intel Turbo Boost Technology

GPU: nVidia Quadro M2000M 4GB

RAM: 32GB DDR4 2133MHz ECC memory

System Drive: 1TB M.2 (2500MB/s)

Working Drive: 1TB M.2 (2500MB/s)

Storage Drive: 3GB SSD (500MB/s)

Video: Vegas Pro 16 Suite / DaVinci Resolve 16 Studio

Audio: PreSonus Studio One Pro 5

Graphics: CorelDraw Technical Suite 2020 / Xara Designer Pro X365

Image Editing: Corel PhotoPaint 2020 / Corel PaintShop Pro X9 Ultimate / PHASEONE Capture One Pro 11

3D Graphics: Maxon Cinema 4D Studio 10

Camera: Sony A7S II / A7 III

Website: www.innoviahouse.com

Vimeo: vimeo.com/innoviahouse