u/Thercon_Jair

Hello dear EX30 owners!

Were on vacation in Sweden and we rented an EX30 because I wanted to experience an EV for a bit to inform future buying decisions.

The first issue I had was only 11kW charging even at 22kW chargers. Our car is not an Ultra spec, so only 11kV.

Our second issue is that whenever we charge we have to start the process twice because the car side charging port doesn't lock. On some chargers there's a base fee, which is incured every time we have to do that.

What we do:

1. Connect type 2 cable to charging station

2. Connect type 2 cable to car's charging port

3. Fiddle with whatever app is necessary for the charger

4. Start the charging process in the app

The charger changes to a blue light which indicates charging, but the car isn't charging when checking the indicator or the dash. It's waiting to start charging. The charging port on the car isn't locked. We have to stop charging in the app, reconnect everything, start charging again. The car's port locks and it starts charging.

We've done this now 5 times, it has never worked on the first go.

What are we doing wrong?

[Solved] It appears to have been a bug, a second export with the same settings as before lead to the expected results.

Hey everyone! I've run into a snag!

I filmed footage from an event with Canon Eos R6 Mark1 cameras in Clog3 BT.2020 and started the project in Vegas Pro 2026 since I've been using Vegas 17 and 18 in the past but they can't handle the never formats. After further examination of what's excluded from the perpetual version and not wanting to get locked into another subcription, I got Davici Resolve instead. Vegas also seemed to have trouble with the Dlog footage from the DJI Osmo Action5 Pro I used where it sometimes hung itself up completely.

The base timeline for the main camera is done and since an XML project export doesn't transfer all work I wanted to render the video for further use as the base track and edit in Davinci Resolve.

I did an export into Prores 422 and it looked fine, i.e. raised blacks. Started editing in Resolve and at some point I noticed that I missed a very short sliver of the track where I left the Canon LUT in.

So I went back into Vegas to remove the LUT and when wanting to re-export I noticed in the Render options that on the Project tab the "Color range (YCbCr output)" was set to "Limited (default)". So I went to check the project settings and noticed that the pixel format was set to 8bit (full). And from my knowledge, for BT.2020, color range should be full.

I went into the Project settings and changed them to conform to my footage, Pixel format 32-bit floating point (full range) with ACES 1.3 and ACES color space default (ACES2065-1). The preview footage then didn't seem to exhibit raised blacks anymore, which raised an eyebrow but I decided to render it out anyways, with Color range on the project tab set to full.

The footage came out without raised blacks and in Resolve it looked the same.

I am now a bit confused, because I expecte the Prores export to come out correctly now, with the correct bit depth and color range. Any obvious glaring errors (aside from starting in Vegas first and complicating the whole thing)?

Update:

I've just reopened the project in Vegas with the same project settings (32-bit floating point) and the preview now again has raised blacks as I would expect. I'm now rendering it out with full color range.

I now remember something I found strange: I worked on the project in Resolve when I noticed the left in LUT, saved and closed. Then opened the Vegas project to remove the LUT and I noticed the sound playback continue playing after stopping the preview, which it did not do before. It does that however in Resolve and it seemed normal there, thought it might be a difference in how the engines behind the programs work. Is it possible there was some bug with Resolve not relinquishing all resources? The suspense whether the export will look fine this time is mounting...