Clips randomly flipping in viewer during playback

Hitfilm Express 13.

Viewer randomly displays clips right way up or upside down as timeline moves along, they can flip and change as they are being played, they do not necessarily stay in one orientation. 

Previously in a previous version of Hitfilm, this particular film file included files from my phone that needed to be manually flipped by rotating -100 in order for them to show up the right way. After an upgrade to v13 they no longer required that manual override. But now it is happening to any of the three types of file I have DSLR .mov, Drone .mp4 and Phone .mp4 (the first two did not require an override), this is only in the viewer and not in a final rendered file. So it seems as though there is a flag set that is confusing the viewer as to the orientation?

Can this be fixed via a reinstall?

Thank you.

Comments

  • @escher303 unfortunately MOV and MP4 don't tell us much about the actual contents of the file. Can you provide a MediaInfo for these files, since they are simply a container for other video/audio formats.

  • I have reinstalled and for now it has stopped doing it. Can I leave this open to see if it recurs while I test? I will report back either way and can either close this thread or provide mediainfo files. Thank you.

  • It's started again, happened after I dragged the timeline slider backwards and forwards across some clips. All the clips were behaving fine for an hour after reinstalling, now it's reappeared, it's happening randomly to any clip. 

    Here is mediainfo for an example clip (Canon DSLR .mov file, have never had a problem with these anywhere else).

    NB. It is completely intermittent, going back trying to recreate and it is now not doing it, seems interface related, not the files.

    General
    Complete name : G:\Photo Master Library 24-7-2019\All\2019-08-12\MVI_4659.MOV
    Format : MPEG-4
    Format profile : QuickTime
    Codec ID : qt 2007.09 (qt /CAEP)
    File size : 1.08 GiB
    Duration : 3 min 31 s
    Overall bit rate : 43.9 Mb/s
    Encoded date : UTC 2019-08-12 18:39:24
    Tagged date : UTC 2019-08-12 18:39:24

    Video
    ID : 1
    Format : AVC
    Format/Info : Advanced Video Codec
    Format profile : Baseline@L5
    Format settings : 1 Ref Frames
    Format settings, CABAC : No
    Format settings, Reference frames : 1 frame
    Format settings, GOP : M=1, N=12
    Codec ID : avc1
    Codec ID/Info : Advanced Video Coding
    Duration : 3 min 31 s
    Bit rate : 43.8 Mb/s
    Width : 1 920 pixels
    Height : 1 080 pixels
    Original height : 1 088 pixels
    Display aspect ratio : 16:9
    Frame rate mode : Constant
    Frame rate : 25.000 FPS
    Color space : YUV
    Chroma subsampling : 4:2:0
    Bit depth : 8 bits
    Scan type : Progressive
    Bits/(Pixel*Frame) : 0.846
    Stream size : 1.08 GiB (100%)
    Language : English
    Encoded date : UTC 2019-08-12 18:39:24
    Tagged date : UTC 2019-08-12 18:39:24
    Color range : Full
    Color primaries : BT.709
    Transfer characteristics : BT.709
    Matrix coefficients : BT.601
    Codec configuration box : avcC

  • edited November 27

    Bit more info, have possibly managed to recreate:-

    Happened again as timeline bar was dragged backwards over from the Canon DSLR file Mov (above) to a phone .mp4 file which is a file that had to be manually rotated in a previous version of Hitfilm but does not in in v13. I.e. when this phone file was imported in v12 and before it was upside down. In v13 it imports the right way up. This hitfilm project was worked on in v12 and upgraded to v13. So it seems to be something where the viewer is fine when working on files that never had a rotation problem but when quickly moving from one to the other in the editor timeline, the viewer loses it's ability to set the orientation correctly on any file.

    NB. When leaving Hitfilm and doing something else for a while, the clips display properly when returning to the application.

     

    Phone file mediainfo

    General
    Complete name : F:\Lightroom Backup 2018\Imported on 24 January 2019\VID_20190124_144109.mp4
    Format : MPEG-4
    Format profile : Base Media / Version 2
    Codec ID : mp42 (isom/mp42)
    File size : 36.1 MiB
    Duration : 24 s 435 ms
    Overall bit rate : 12.4 Mb/s
    Encoded date : UTC 2019-01-24 14:41:36
    Tagged date : UTC 2019-01-24 14:41:36
    com.android.version : 8.1.0

    Video
    ID : 1
    Format : AVC
    Format/Info : Advanced Video Codec
    Format profile : High@L4
    Format settings : CABAC / 1 Ref Frames
    Format settings, CABAC : Yes
    Format settings, Reference frames : 1 frame
    Format settings, GOP : M=1, N=30
    Codec ID : avc1
    Codec ID/Info : Advanced Video Coding
    Duration : 24 s 384 ms
    Bit rate : 12.1 Mb/s
    Width : 1 920 pixels
    Height : 1 080 pixels
    Display aspect ratio : 16:9
    Rotation : 180°
    Frame rate mode : Variable
    Frame rate : 23.540 FPS
    Minimum frame rate : 14.881 FPS
    Maximum frame rate : 30.354 FPS
    Standard : NTSC
    Color space : YUV
    Chroma subsampling : 4:2:0
    Bit depth : 8 bits
    Scan type : Progressive
    Bits/(Pixel*Frame) : 0.248
    Stream size : 35.2 MiB (97%)
    Title : VideoHandle
    Language : English
    Encoded date : UTC 2019-01-24 14:41:36
    Tagged date : UTC 2019-01-24 14:41:36
    Color range : Full
    Color primaries : BT.601 NTSC
    Transfer characteristics : BT.601
    Matrix coefficients : BT.601
    mdhd_Duration : 24384
    Codec configuration box : avcC

    Audio
    ID : 2
    Format : AAC LC
    Format/Info : Advanced Audio Codec Low Complexity
    Codec ID : mp4a-40-2
    Duration : 24 s 435 ms
    Duration_FirstFrame : 8 ms
    Bit rate mode : Constant
    Bit rate : 320 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 : 954 KiB (3%)
    Title : SoundHandle
    Language : English
    Encoded date : UTC 2019-01-24 14:41:36
    Tagged date : UTC 2019-01-24 14:41:36

     

  • I believe this is something we are aware of and are working on fixing. Hopefully it will be fixed in a future version.

  • Thanks for the update

Sign In or Register to comment.