"No valid source or titles found" - GoPro Hero 4 file error

HandBrake for Windows support
Forum rules
An Activity Log is required for support requests. Please read How-to get an activity log? for details on how and why this should be provided.
Post Reply
DaHorse
Posts: 3
Joined: Sat Nov 14, 2020 6:14 am

"No valid source or titles found" - GoPro Hero 4 file error

Post by DaHorse »

I have a couple of videos on my GoPro that are corrupt

I am a noob when it comes to Handbrake, so please be gentle ;)
I have a couple of videos that went corrupt on my GoPro Hero 4, one is about 225mb and other 927mb, none of the (free) repair tools I have tried using is able to open the files. I tried VLC (to convert), Freemake Video Converter, and now Handbrake - issue is pretty much the same all the time, files just don't get opened in each case. I have realised by now that this should be recoverable by reading the web, but I need to realise what is wrong with files to find solution, so here I am, asking You for assistance.

HandBrake version 1.3.3 (2020061300)

Operating system and version Win 8

HandBrake Activity Log ***required*** (see How-to get an activity log)

Code: Select all

HandBrake 1.3.3 (2020061300)
OS: Microsoft Windows NT 6.3.9600.0
CPU: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz
Ram: 8084 MB, 
GPU Information:
  NVIDIA GeForce GT 820M - 23.21.13.8871
  Intel(R) HD Graphics Family - 10.18.14.4578
Screen: 1920x1080
Temp Dir: C:\Users\DaHorse\AppData\Local\Temp\
Install Dir: C:\Program Files\HandBrake
Data Dir: C:\Users\DaHorse\AppData\Roaming\HandBrake

-------------------------------------------

[07:19:01] Compile-time hardening features are enabled
Cannot load nvEncodeAPI64.dll
[07:23:17] hb_init: starting libhb thread

 # Starting Scan ...

[07:23:17] CPU: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz
[07:23:17]  - Intel microarchitecture Haswell
[07:23:17]  - logical processor count: 4
[07:23:17] Intel Quick Sync Video support: yes
[07:23:17]  - Intel Media SDK hardware: API 1.17 (minimum: 1.3)
[07:23:17]  - H.264 encoder: yes
[07:23:17]     - preferred implementation: hardware (any) via D3D11
[07:23:17]     - capabilities (hardware):  breftype icq+la+i+downs vsinfo opt1 opt2+mbbrc+extbrc+trellis+ib_adapt+nmpslice
[07:23:17]  - H.265 encoder: no
[07:23:17] hb_scan: path=H:\DCIM\100GOPRO\GOPR7817.MP4, title_index=0
udfread ERROR: ECMA 167 Volume Recognition failed
src/libbluray/disc/disc.c:323: failed opening UDF image H:\DCIM\100GOPRO\GOPR7817.MP4
src/libbluray/disc/disc.c:424: error opening file BDMV\index.bdmv
src/libbluray/disc/disc.c:424: error opening file BDMV\BACKUP\index.bdmv
src/libbluray/bluray.c:2585: nav_get_title_list(H:\DCIM\100GOPRO\GOPR7817.MP4\) failed
[07:23:17] bd: not a bd - trying as a stream/file instead
libdvdnav: Using dvdnav version 6.0.1
libdvdread: Encrypted DVD support unavailable.
libdvdread:DVDOpenFileUDF:UDFFindFile /VIDEO_TS/VIDEO_TS.IFO failed
libdvdread:DVDOpenFileUDF:UDFFindFile /VIDEO_TS/VIDEO_TS.BUP failed
libdvdread: Can't open file VIDEO_TS.IFO.
libdvdnav: vm: failed to read VIDEO_TS.IFO
[07:23:17] dvd: not a dvd - trying as a stream/file instead
[mov,mp4,m4a,3gp,3g2,mj2 @ 000000a1ca14d2c0] moov atom not found
[07:23:17] hb_stream_open: open H:\DCIM\100GOPRO\GOPR7817.MP4 failed
[07:23:17] scan: unrecognized file type
[07:23:17] libhb: scan thread found 0 valid title(s)

 # Processing Scan Information ...


 # Scan Finished ...


[07:32:17] hb_init: starting libhb thread

 # Starting Scan ...

[07:32:17] CPU: Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz
[07:32:17]  - Intel microarchitecture Haswell
[07:32:17]  - logical processor count: 4
[07:32:17] Intel Quick Sync Video support: yes
[07:32:17]  - Intel Media SDK hardware: API 1.17 (minimum: 1.3)
[07:32:17]  - H.264 encoder: yes
[07:32:17]     - preferred implementation: hardware (any) via D3D11
[07:32:17]     - capabilities (hardware):  breftype icq+la+i+downs vsinfo opt1 opt2+mbbrc+extbrc+trellis+ib_adapt+nmpslice
[07:32:17]  - H.265 encoder: no
[07:32:17] hb_scan: path=H:\DCIM\100GOPRO\GOPR7837.MP4, title_index=0
udfread ERROR: ECMA 167 Volume Recognition failed
src/libbluray/disc/disc.c:323: failed opening UDF image H:\DCIM\100GOPRO\GOPR7837.MP4
src/libbluray/disc/disc.c:424: error opening file BDMV\index.bdmv
src/libbluray/disc/disc.c:424: error opening file BDMV\BACKUP\index.bdmv
src/libbluray/bluray.c:2585: nav_get_title_list(H:\DCIM\100GOPRO\GOPR7837.MP4\) failed
[07:32:17] bd: not a bd - trying as a stream/file instead
libdvdnav: Using dvdnav version 6.0.1
libdvdread: Encrypted DVD support unavailable.
libdvdread:DVDOpenFileUDF:UDFFindFile /VIDEO_TS/VIDEO_TS.IFO failed
libdvdread:DVDOpenFileUDF:UDFFindFile /VIDEO_TS/VIDEO_TS.BUP failed
libdvdread: Can't open file VIDEO_TS.IFO.
libdvdnav: vm: failed to read VIDEO_TS.IFO
[07:32:17] dvd: not a dvd - trying as a stream/file instead
[mov,mp4,m4a,3gp,3g2,mj2 @ 000000a1ca185380] moov atom not found
[07:32:17] hb_stream_open: open H:\DCIM\100GOPRO\GOPR7837.MP4 failed
[07:32:17] scan: unrecognized file type
[07:32:17] libhb: scan thread found 0 valid title(s)

 # Processing Scan Information ...


 # Scan Finished ...



DaHorse
Posts: 3
Joined: Sat Nov 14, 2020 6:14 am

Re: "No valid source or titles found" - GoPro Hero 4 file error

Post by DaHorse »

A quick update - I have learned that looking into hex code can tell if the file is recoverable - the smaller one is nothing but 00's, but the larger one has actual values in it, so I hope there is something to be done here... :roll:
DaHorse
Posts: 3
Joined: Sat Nov 14, 2020 6:14 am

Re: "No valid source or titles found" - GoPro Hero 4 file error

Post by DaHorse »

Sorry, I can't seem to be able to find editing of older posts...

As I am an impatient [Censored], I kept looking for solution to my original issue, and I have succeeded:

https://www.youtube.com/watch?v=ISJC8ppXP4A

It isn't the simplest thing I have ever done, but I have the video restored :D :D :D

I would still like to know if there is a way to get results with Handbrake, as I am getting more and more into video editing and it is more than likely that I will be in this predicament again... If I have learned anything by now - it is that the more ways to fix files you know, the more chances you have for positive outcome ;)
Post Reply