[teostream]

i downloaded a movie i bought through Vudu and it was downloaded 3 files:
1. 9000.f4m
2. 9000Seg1.f4f
3. f4f_frag_offsets.csv


a) I ran php AdobeHDS.php 9000Seg1.f4f
> Found 0 fragments
b) then I ran php AdobeHDS.php --manifest "file:///<goodPath>/9000.f4m" 9000Seg1.f4f

I get a bunch of errors about the XML file:
Warning: simplexml_load_string(): Entity: line 27: parser error : Opening and ending tag mismatch: META line 11 and head in AdobeHDS.php on line 409

Is it possible to use AdobeHDS to convert local .f4f files?

[KSV]

manifest switch is supposed to work with remote manifest url not locally saved manifest file.
php AdobeHDS.php --manifest "http://some.server.com/manifest.f4m"

if you are trying to join locally saved fragments then use base filename without the trailing counter.

php AdobeHDS.php 9000Seg
or
php AdobeHDS.php --fragments 9000Seg

also f4f extension is optional. go through wiki (https://github.com/K-S-V/Scripts/wiki) once again.

[teostream]

Thanks I had tried without the segment index. Thanks to you i tried without the extension and it worked.

$ php AdobeHDS.php 9000Seg.f4f

KSV Adobe HDS Downloader

Found 0 fragments


Now it works but i get a memory exception. I have only 4GB of RAM on my laptop and the file is 6GB.


$ php AdobeHDS.php 9000Seg

KSV Adobe HDS Downloader

Found 1 fragments

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 6934686386 bytes) in /Scripts/AdobeHDS.php on line 1758

[KSV]

6 GB :eek: a single fragment size can't be that large. this script is intended to process client side fragments which will be hardly of few MB in any case. probably you are trying to process the f4f file generated on server side. simply renaming it to f4v or mp4 may work in that case.

[teostream]

This file is the result of downloaded an HDX version from VUDU.

I had tried to change the extension to .mp4 and it did not work :(

[KSV]

i have checked out vudu.com myself. they are using FlashAccess DRM to protect their content. even trailers are DRM'ed. also method to access individual fragments is quite different (too old or custom) Seg1.f4f/range/97248-13224690 instead of regular Seg1-Fragx. This script can't be of much use in case of encrypted content.