@Brian-Obvilion 

Here are two YUV422 files imported into VPX14

MP4 422 created with Handbrake,

MOV 422 created with Vegas.

Both of these work perfectly well.

I think you need to share your Handbrake settings as there's too many options for me to try all of them.

@browj2 will be able to help with importing the individual jpgs into VPX.

@Brian-Obvilion

Hi

. . . . In a nutshell, I need a high quality video format I can create from all these jpg images encoded in yuv442p preserving the original image data as much as possible - that video pro x16 can actually import correctly.  . . . .

After importing in to VPX 16, what is the intended final usage of the video exported ?

John EB
Forum Moderator

@Brian-Obvilion

Hi

. . . . In a nutshell, I need a high quality video format I can create from all these jpg images encoded in yuv442p preserving the original image data as much as possible - that video pro x16 can actually import correctly.  . . . .

After importing in to VPX 16, what is the intended final usage of the video exported ?

John EB
Forum Moderator

After cleaning up through the neat video plug in, I want to have all the individual timelapse videos as one "program" that plays them all.

I have some new information to add here and some disappointment which I hope is just me doing something wrong.

After much trial and error I did find an a set of command options that would render a video that VPX would "accept".

For anyone looking for help, here it is:

ffmpeg -r 8 -f concat -safe 0 -i filelist.txt -c:v libx265 -preset medium -pix_fmt yuv422p10le -r 8 -b:v 80M -aspect 4:3 -x265-params "colorprim=bt709:transfer=bt709:colormatrix=bt709:range=full:qp=6" output_HEVC_GOPRO_1.mp4

That filelist.txt file contains a list of all the JPGs in the directory. If you use linux, you can use the pattern/glob option and not bother with it. It outputs 8fps (-r 8) video.

However, I did encounter a couple of problems, the 1st of which I believe is a bug. The video is in 4:3 @ 8 fps. The "movie" parameters are set to custom. With the matching resolution and fps.

When I attempt to import it into VPX, it warns me, that the movie and file being imported don't match.... it's said the source is in 16:9. Clearly it's not. Error message shown below.

If I chose to adjust or not to adjust, VPX smashes down the video vertically making it look horrible.

Mediainfo reported the aspect ratio at 4:3

I added the -aspect 4:3 to command and that seemed to stop VPX from complaining and smashing the video file.

Victory right? Wrong.

I don't know what VPX is doing on import but there is a PROFOUND loss of detail/resolution and color depth. Both in the program preview (I don't have reduce resolution etc turn on) and in the rendered/exported file... no matter what format I chose. The color/detail is permanently lost when pulled in VPX it seems.

The difference between playing the video file in say VLC and what VPX previews/renders is night and day.

I suspect VPX is importing in my beautiful video file, running through it's lossy, yuv 4:2:0 codec then that is then being re-rendered out. I don't even have the option of 4:2:2 for HVEC/MPEG4 for export format.

I also tried changing the program device options import/processing/export to use CPU instead of my GPU. It made no difference.

Below is a screen shot of the error and the mediainfo of the input/output.

Any suggestions for improving import/export quality would be appreciated.

######################

###########################################

### VPX Garbage.
General
Complete name                            : C:\2024-10-21 - 02.MP4
Format                                   : MPEG-4
Format profile                           : Base Media
Codec ID                                 : iso4 (iso4/hvc1)
File size                                : 9.70 MiB
Duration                                 : 5 s 0 ms
Overall bit rate                         : 16.3 Mb/s
Frame rate                               : 25.000 FPS
Encoded date                             : 2024-10-21 21:44:18 UTC
Tagged date                              : 2024-10-21 21:44:18 UTC

Video
ID                                       : 1
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format profile                           : Main 10@L6@High
Codec ID                                 : hvc1
Codec ID/Info                            : High Efficiency Video Coding
Duration                                 : 5 s 0 ms
Bit rate                                 : 16.1 Mb/s
Width                                    : 5 568 pixels
Height                                   : 4 176 pixels
Display aspect ratio                     : 4:3
Frame rate mode                          : Constant
Frame rate                               : 25.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 10 bits
Bits/(Pixel*Frame)                       : 0.028
Stream size                              : 9.59 MiB (99%)
Language                                 : English
Encoded date                             : 2024-10-21 21:44:18 UTC
Tagged date                              : 2024-10-21 21:44:18 UTC
Codec configuration box                  : hvcC

Audio
ID                                       : 2
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 4 s 949 ms
Bit rate mode                            : Constant
Bit rate                                 : 192 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Frame rate                               : 46.875 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 116 KiB (1%)
Language                                 : English
Encoded date                             : 2024-10-21 21:44:18 UTC
Tagged date                              : 2024-10-21 21:44:18 UTC

####Beautiful. 

General
Complete name                            : C:\output_BE_HEVC_GOPRO_FULL.mp4
Format                                   : MPEG-4
Format profile                           : Base Media
Codec ID                                 : isom (isom/iso2/mp41)
File size                                : 180 MiB
Duration                                 : 9 s 250 ms
Overall bit rate                         : 163 Mb/s
Frame rate                               : 8.000 FPS
Writing application                      : Lavf61.5.101

Video
ID                                       : 1
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format profile                           : Format Range@L6@Main
Codec ID                                 : hev1
Codec ID/Info                            : High Efficiency Video Coding
Duration                                 : 9 s 250 ms
Bit rate                                 : 163 Mb/s
Width                                    : 5 568 pixels
Height                                   : 4 176 pixels
Display aspect ratio                     : 4:3
Frame rate mode                          : Constant
Frame rate                               : 8.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:2
Bit depth                                : 10 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.877
Stream size                              : 180 MiB (100%)
Writing library                          : x265 3.6+36-2cdd69a6d:[Windows][GCC 14.1.0][64 bit] 10bit
Encoding settings                        : cpuid=1111039 / frame-threads=4 / numa-pools=24 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=2 / input-res=5568x4176 / interlace=0 / total-frames=0 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=3 / no-allow-non-conformance / no-repeat-headers / annexb / no-aud / no-eob / no-eos / no-hrd / info / hash=0 / temporal-layers=0 / open-gop / min-keyint=8 / keyint=250 / gop-lookahead=0 / bframes=4 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=20 / lookahead-slices=8 / scenecut=40 / no-hist-scenecut / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=0 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / strong-intra-smoothing / max-merge=3 / limit-refs=1 / no-limit-modes / me=1 / subme=2 / merange=57 / temporal-mvp / no-frame-dup / no-hme / weightp / no-weightb / no-analyze-src-pics / deblock=0:0 / sao / no-sao-non-deblock / rd=3 / selective-sao=4 / early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=cqp / qp=6 / ipratio=1.40 / pbratio=1.30 / aq-mode=0 / aq-strength=0.00 / no-cutree / zone-count=0 / no-strict-cbr / qg-size=64 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=1 / overscan=0 / videoformat=5 / range=1 / colorprim=1 / transfer=1 / colormatrix=1 / chromaloc=0 / display-window=0 / cll=0,0 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / no-hdr10 / no-hdr10-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=0 / analysis-save-reuse-level=0 / analysis-load-reuse-level=0 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=1 / refine-ctu-distortion=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq / no-svt / no-field / qp-adaptation-range=1.00 / scenecut-aware-qp=0conformance-window-offsets / right=0 / bottom=0 / decoder-max-rate=0 / no-vbv-live-multi-pass / no-mcstf / no-sbrc
Color range                              : Full
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
Codec configuration box                  : hvcC

@Brian-Obvilion

Could you put a short file up on Google Drive or another hosting service for us to have a look at?

Re the aspect ratio, if you think Magix is misinterpreting it eg saying it's 16:9 when it's really 4:3, you can manually set it: right-click on the object on the timeline, go to Video and set the ratio from the droplist.

So, choose "Do not adjust" and then set the ratio on the object.

If the file was coded correctly, Magix shouldn't have a problem interpreting it. Just because MediaInfo says something doesn't make it so.

I will work on getting a clip together for you...but yes, I also did exactly that. It made no difference. It made no difference if I said adjust or do not adjust....then if I right click on object properties and forced it to 4:3, it made no difference. It smashed the image vertically and destroyed the detail/dynamic range. Thought it did display in 4:3.

The only way I stopped the vertical smashing was adding the -aspect 4:3 parameter in ffmpeg. I don't know what that did to convince VPX it was 4:3 but the the ratio is the ratio. 5568X4176 is 4:3. VPX should be "mathing out" the ratio from the resolution.

I'll note that VLC (et al media players) always showed it correctly in 4:3 without detritus effect regardless of that -aspect parameter.

Here's an image where I ran the video I created from ffmpeg from above, through handbrake (using Pro/Max settings, 4:4:4 chroma subsampling), and put that into VPX per the suggestion earlier that perhaps ffmpeg wasn't populating all the info needed. Same results. Utterly destroyed image quality when imported into VPX.

I have no effects at all. Literally just a brand new "UHD" project, changed the movie settings to the custom 4:3 res and fps settings and dropped the video on the track.

On the right/background image, I have the same video opened in VLC player in approximately the same spot. On the left is what VPX shows in the program window (I have no "reduce resolution" etc setting set ). If I were to export it, the output is the same or worse.

This is a screenshot, it's worse live. Sharpness details are gone (look at wall/sky). Dynamic range compressed. It appears VPX renders the input in some intermediate format before it gets rendered out - damage's done at that point; but I don't know.

Frame rate mode                          : Constant
Frame rate                               : 8.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:2
Bit depth                                : 10 bits

@Brian-Obvilion Find whatever setting you can & change it to 8bit, as far as I know JPEGs are 8-bit files & this is a Nightlapse I just created with my GoPro.

@Brian-Obvilion

Hi

IMHO the workflow you are using is not necessary.

Try the following:

1. VPX - program settings set the import image length to 1 frame -
   
   
   
   Set the project settings to the required resolution and frame rate
   
   Import the GoPro image sequence.
    
2. Export to the Magix intermediate format MXV video for further editing.
    
3. Repeat steps 1 - 2 for each time-lapse image sequence.
    
4. Combine the exported time-lapse videos in a new project and apply NeatVideo Denoiser and any other effects as require and export to final video.

Note, NeatVideo Denoiser will significantly slow down the export rate and may take up 10 - 20 times the final video play time.

John EB

@Brian-Obvilion

Hi,

I can be completely wrong, but have you already tried to export your projects as AV1. Go to: File / Film Export / Video as AV1

HTH,
Rob

addition:

@Bol

Hi Rob

Do you mean using AV1 for the intermediate format for more editing, or final export for viewing/streaming?

As an intermediate format for further editing, IMHO it is not a suitable format to use due to the very high compression applied, and the higher CPU/GPU processing requirements.

John EB

@johnebaker

Hi John,

....Do you mean using AV1 for the intermediate format for more editing, or final export for viewing/streaming?...

I mean the final output for viewing and/or streaming.

Best wishes,

Rob

@johnebaker

Hi John,

AV1 (mp4) files are, as far as I can judge, well editable on the timeline of Pro X16. But to be able to export as an AV1 (MP4) file, a very fast video card is a must.

See: rtx-30-series-av1-decoding

I myself still have an NVIDIA Video Card 1660Ti and it is exported as a mixdown, which can take a very long time.

HTH
Rob

Thanks for all the advice here, I really do appreciate it. 

Per the previous comments of some of the suggestions. Here's what I've tried before and since. Sorry for the long message/narrative :-).

On the setting the frame rate to 1 and dropping in the individual frames..... I did try that...in fact, I tried that 1st. It simply didn't work or render anything that would even play correctly. I set the program setting to 1 frame, dropped in the frames, changed the movie settings to 8 fps etc... and it didn't work.. it was a disaster. like it would try try to render a 2 hour movie from a 10 second clip. 

However, given the suggestion here, I did try again... it failed... then I tried it a slightly different way - which kinda worked. 

You create the project, change the program settings. Create a movie, change the movie setting set the res/fps BEFORE YOU DO ANYTHING. Then drop the files in to it. That seems to allow it show correctly in the tool anyways. It would *not* work if I tried to change the movie settings after putting the images in the the movie. 

So I thought I had it beat at point. Nope. The struggle continues. 

First off, I encountered a myriad of weird and bizarre behaviors/bugs (I am a software dev by trade, BTW). I couldn't possibly document them all here as it would be a tome but it was stuff like... if you drop all the images into movie, then delete them from the track. Then simply tried to add them back in by multi-select them from the project folder - it just wouldn't do anything....most of the time. Sometimes you would take those images, drop them on a single track and it would randomly spray them across the tracks above and below. And sometimes it wouldn't maintain the order - even though they are sequentially numbers and sorted in the correct order. I found I had to take "small" chunks of 20 or so images at a time to force it to stay in order on the track. 

Also keep in mind, these are small timelapse sequences... like each rendered video is about 10-20 seconds max. 

At any rate, I exported the images into the magix video format .mxv file.. at the highest quality. Cool that worked. Nice big intermediate files... as expected.

Given all the weirdness. I closed and just created a new project. Same process... set the movie settings to my res/fps, put the mxv into the track(s) etc... worked ok.... some glitches. Mind you, I have add NO effects to anything at this point. It plays in VPX program as I would expect it to. 

So time render it out... my video that's like 2 minutes or so long. 

HVEC, I can't set the chroma subsampling to anything other than 4:2:0. My nvidia card most definitely supports 4:4:4. This is with or without the GPU set for the encoding. Regardless, the video is not correct... it skips, has terrible color banding etc..  If I attempt to set the framerate to the framerate of the video of 8fps. It's just ignored and stays at 25. I get a warning on export about it, saying it's set for 25. But I can't change it....so I can only "continue".

So screw it, AV1 it is!  I actually bought the AVCInra Encoder upgrade, something I am regretting as I feel like I'm just throwing good money after bad. 

AV1 encoding - garbage. Under advanced I set the bitrates to ridiculous levels like 180000 kBit/s, coding quality "Best" and hardware encoding to GPU (or not). It's moot because it uses the CPU anyways - as it should (GPU can't encode AV1 I believe).

The kinda good news is I can set the framerate to 8 fps and it "sticks". With those settings, the dialog box estimates a 1GB file output... ok cool, let's see what happens. It chews, maxes out all my cores for 15 minutes or so and spits out something between a 9 and 60 MB file (that is correct, megabyte). Mind you there are 800 JPEG frames, that is about 4GB (total, all clips/movies combined) each of the mxv files are around 500 MB....that gets distilled down into a file less than 50 MB total. As you can imagine the rendered output is poor and is really incomplete... freezes, jumps/skips etc. 

I just don't get it, this is such a stupid little thing that is monumentally frustrating. There's so many bugs/glitches working through the interface.... it's unreal. Might be time to try other tools like davinci, or premier or something. 

@Brian-Obvilion

Hi

Taking a step back and looking at the information of the GoPro images you are working with:-

. . . jpeg format with a resolution of 5568X4176, yuvj 422p ... bt470bg colorspace. 

Unless GoPro has 'customised' the image format, eg put 10 bit images into the jpg file format, it does not support 10 bit as @Gid previously mentioned, the images are standard RGB 8bit 4:2:2. chroma subsampling which should not cause any of the issues you are having.

My time-lapse images are identical format, though different resolution, and cause no issues and do not require putting through Handbrake.

. . . . AV1 encoding - garbage. Under advanced I set the bitrates to ridiculous levels like 180000 kBit/s, coding quality "Best" and hardware encoding to GPU (or not). It's moot because it uses the CPU anyways - as it should (GPU can't encode AV1 I believe) . . . .

180000 kBit/s If this is correct I get an error and the export fails.

What is your computer specification and what are the Program settings, Device options tab, Import, Processing and Export options set to, and are the GPU drivers up to date?

An 11 second long timelapse, 550 still images, exporting to AV1 All Intra 4k UHD (3840*2160), 4:2:2, 50 fps 40Mb/s, took approx 16 minutes, all work being done by the CPU - my system specs are in my signature.

John EB

Thanks again for the response.

Correct on the image format, they are YUV 8bit 4:2:2 in the bt470bg (601?, PAL?) colorspace.

Couple of things of note, I'm in the US thus have it set to NTSC (I noticed PAL in previous posts).

While I do have an NVIDIA 4070 RTX Super video card, I've taken it out of the equation (or I think I have anyways). As I understand it, NVIDIA cards do not support 4:2:2... only 4:2:0 or 4:4:4. I have actually TRIED 4:4:4 with the GPU but it gets ignored anyways (I see my GPU is idle and CPU maxes out). This is probably due to the resolution I have set (GPU not supported). I don't need this 5K-ish output thus I have also tried 4K in 4:3, with not any better results.

https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new

My "Master Program" consists of 4 tracks of mxv videos that total about 3 GB of video data. The rendered AV1 if about 8MB (yes MB). I do get a rendered playable file... though it's playing "faster" than it should. in VPX it's a 40 sec clip, rendered it's 11 sec. Almost certainly due to the 25fps and it "ignoring" my setting. The quality is also quite poor compared to what I see in VPX.

On the movie settings I have tried setting the colorspace to 601, bt470bg etc... seems every time I come back to the settings it randomly changes back to 709 (or I'm doing something somewhere to flip it back). Regardless, none of those changes made any difference anyways. Also noteworthy, I don't seem to have bt470bg option in the export options only bt470M (NTSC eq?; not sure if that is the same).

I've attached screen shots of what I believe are the relevant settings I used to render a video who's MediaInfo is below. (I did crank down the bit rates).

I'm starting to believe the problem is circling around the fps. My individual movie settings are 7fps.... the master movie is 7fps, I export at 7fps, thus the output should be 7fps? I noticed yours is much higher. Or perhaps my program vid/aud settings are wrong?

#####MEDIAINFO

Format                                   : MPEG-4
Format profile                           : Base Media
Codec ID                                 : isom (isom/av01/iso2/mp41)
File size                                : 7.09 MiB
Duration                                 : 11 s 560 ms
Overall bit rate                         : 5 146 kb/s
Frame rate                               : 25.000 FPS
Encoded date                             : 2024-10-23 14:14:47 UTC
Tagged date                              : 2024-10-23 14:14:47 UTC

Video
ID                                       : 1
Format                                   : AV1
Format/Info                              : AOMedia Video 1
Format profile                           : Professional
Codec ID                                 : av01
Duration                                 : 11 s 560 ms
Bit rate                                 : 5 144 kb/s
Width                                    : 5 568 pixels
Height                                   : 4 176 pixels
Display aspect ratio                     : 4:3
Frame rate mode                          : Constant
Frame rate                               : 25.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:2
Bit depth                                : 8 bits
Bits/(Pixel*Frame)                       : 0.009
Stream size                              : 7.09 MiB (100%)
Language                                 : English
Encoded date                             : 2024-10-23 14:14:47 UTC
Tagged date                              : 2024-10-23 14:14:47 UTC
Color range                              : Limited
Color primaries                          : BT.601 NTSC
Transfer characteristics                 : BT.601
Matrix coefficients                      : BT.601
Codec configuration box                  : av1C
 

@Brian-Obvilion

Hi

. . . . I'm starting to believe the problem is circling around the fps. My individual movie settings are 7fps.... the master movie is 7fps, I export at 7fps, thus the output should be 7fps? I noticed yours is much higher. Or perhaps my program vid/aud settings are wrong? . . . .

This will certainly contribute to poor playback, at 7 fps the video will be 'jerky' to say the least.

MXV 7fps

MXV 50fps

I cannot replicate the video speed up on playback.

Looking at your project and video export settings, there are several things I would change:
 

• MXV exports from the still image sequences export at 29.97 or 59.94 fps, otherwise they are going to playback jerkily as seen above.
   
• Project setting framerate
  
  Set to 29.97 or 59.94 fps before importing the MXV files. When importing the MXV files, if you get the message to adjust the project settings, click Do not adjust
   
• Export settings:
  
  Bitrate mode leave this as Variable (VBR)- Constant (CBR) will rob the encoder of bits where there is high/fine detail in a frame, from the night-lapses images you posted the subtle colours of the night sky should be better with VBR.
   
• Average and Max Bitrate - leave these at the default settings, from the MediaInfo data you posted the encoder is not achieving the Average rate specified.
   
• Frame rate: leave this the same as the project - 29.97 or 59.94 fps
   
• Maximum GOP length - set this to 15 or 30
   
• Audio AAC samplerate - if you intend to add an audio track set the sample rate to 48000 Hz. - this is the standard default for video.

WRT to my higher settings, I am in PAL land and record at 4K UHD HEVC, 50 fps, 10bit, Cine D (HDR) on my DJI Action 3, time lapses are recorded directly to 4K UHD HEVC MP4 video at 29.97 fps 8 bit.

HTH

John EB

OK I'll give that a try... the thing is, I'm using 7fps to "slow" the video down.

@Brian-Obvilion

Hi.

The way to slow down the motion in a time lapse video would be to extend how many frames each image is displayed on the timeline rather than set an uncommon and generally unsupported frame rate for export.

I'm surprised Go-Pro do not have a program that would do that for you similar to DJI's Media Maker. Then process the that video with the neat video plugin once that video is placed on the timeline.

Ray.

I'm surprised Go-Pro do not have a program that would do that for you 

@CubeAce Hi, GoPro might have that feature in GoPro Quick or GoPro Studio but I think they assume you've already set the camera as timelapse video or photo sequence as that has been an option for yrs.

Google -

You can also use the GoPro app to create time-lapse videos in two modes:

Time Lapse Video: The camera automatically stitches the stills into a video file

Time Lapse Photo: The camera saves each still image separately, which gives you more control over the final video 

With respect to the OP he started off wrong, his statement is incorrect - 'Given how long the sequences are, gopro doesn't stitch them together', & now he seems to be making this into very hard work.

'While I do have an NVIDIA 4070 RTX Super video card, I've taken it out of the equation (or I think I have anyways). As I understand it, NVIDIA cards do not support 4:2:2' - this maybe true but my PC has no integrated graphics & handles these files without problems, importing them into VPX watching Taskmanager the GPU is doing all the work. Why the OP has disabled his GPU I've no idea.

He wants a slower video but set the photo interval too long so when set at the period he wishes it stutters, not enough images to make it run smooth. Maybe just learn to use the camera correctly by learning through trial n error, this one being an error.

@Gid

Hi Gid.

He wants a slower video but set the photo interval too long so when set at the period he wishes it stutters, not enough images to make it run smooth. Maybe just learn to use the camera correctly by learning through trial n error, this one being an error.

Totally agree.

Time Lapse is supposed to speed things up, not slow them down. To slow something down you need more frames per second than the frame rate of the intended exported video or you get stuttering. To do that for astro photography I'm not even sure what camera you could use as the exposure times would be too short to provide enough light for even a noisy image with most consumer grade sensors as you would have to push the ISO values to very high levels. You would not be able to distinguish between noise and starlight.

Ray.

@CubeAce Hi, there's a few presets like Star trails & Vehicle lights etc. which can be modified & a little photography knowledge would be needed but this is where the 'trial n error' comes in. In the photo & video mode there's plenty of settings, ISO & Interval. this is just the photo options but video has similar settings, On the GoPro site where i got those pictures from the instructions are fairly clear.

Here in the UK good clear nights can be few n far between but practice with the time interval can be experimented with on the reg Timelapse during the day, it's the same interval settings as the Nightlapse one.

This is a short section of 3.5mins of the sun coming up, I set the interval too short, the battery ran out after a couple of hrs & the sun hardly moves, turned it into a bit of a boring video, Doh!😂🤦‍♂️

Even when I speeded the orig up in Vegas x8 it was a bit crap but like I say - trial n error.

@Brian-Obvilion

Hi

. . . . using 7fps to "slow" the video down . . . .

This can be fixed, within reasonable limits, in the stage where you bring all the exported MXV files together in one project using the Speed effect and turning on Calculate intermediate images.

The question is how slow do you want to go, and do you want smooth playback as in my second example above or is the 'stepped' playback, as seen in my first example above, acceptable ?

The example I gave above is a sequence of 607 images shot with a time-lapse interval of 5 seconds, the interval being set by the speed factor I required, in the example above 10x real time when put together into a video.

As @Gid and @CubeAce have commented/hinted at, night shots require longer exposure time which limits the timelapse interval and can be a bit 'hit & miss' getting the settings right.

John EB

@Gid

Hi Gid.

I've played with time lapse, hyper lapse, and motion lapse and the lower the light, the harder it gets. If the camera can do any of them in raw then the gap available between shots gets larger due to the longer processing times needed over jpg and even in jpeg some cameras can only go to one frame every second during daylight. I would think to have any chance photographing stars at those exposure times you would need a sensor with at least 14 stops available to the sensor at a low ISO setting. Anything above ISO 640 and I personally think you would not be able to definitely reduce noise and expect not to eliminate all but the brightest stars even with a full framed sensor. Tail lights on a highway are a lot brighter than the pinprick of stars and a star trail setting would mean a long exposure is set.

As you have seen in your experiment, smooth rarely happens at all let alone trying to slow such a video down.

Opening motion lapse sequence.

If I remember correctly that motion lapse took 43 minutes.

Ray.