We need to have "Thumbnail URL" for the migrated assets in the analyze report.

[dhanil94]

We are successfully migrated the assets from media services using the tool, and after i have checked the report and it shows the DASH and HLS URL for the assets but here i need one more URL from the same output storage account of these DASH and HLS urls which is its thumbnail url. Is there any possible way to add new column in the report for thumbnail URL.
Similarly i have one more issue after the migration few assets are not migrated those are "non_ism", but i can see that not all non_ism files have this issue.

This is the report and i need one more column in the report for thumbnail url

[pohhsu]

@dhanil94, thanks for reporting the issues.

1. unfortunately for thumbnail url generation, we don't have any way to find information about the thumbnail (both name, or existance) on an asset. it seems existing api doesn't support this scenario as it is not in any of the server manifests / data. So it would be difficult for us to add this feature in a reliable manner. That said, if you know the thumbnail name, then you can compose the url by using the outputHlsURl and substitute .m3u8 to your thumbnail name.

2. for your other issue, I'm not sure I 100% understand what you are saying so in case I misinterpret it, please let me know. For this issue, I think your screen shot shows that we are reporting hls/dash url for non_ism content (with /.m3u8 or /.mpd) which is incorrect. We've submitted a PR to fix this issue.

146d726

so you can git pull and try again to see if it addresses your issue.

[dhanil94]

For the second issue, some assets were not migrated to the new storage account but in the report, it was showing as "completed".

I have checked the assets in the new storage account and have not been able to find the assets.

[pohhsu]

@dhanil94,

you mentioned 'new storage account' so I'm wondering whether the follow scenario happened: you tried to migrate the same asset to two different output storage account?

I can't tell from your screenshot whether this happened or not so I wanted to clarify this with you.

The reason I ask is that the migration tool will mark the input asset that it migrated already with 'complete' and if you tried to run the tool a second time to a different storage location, it will skip the asset (note that your migrated contents should be in the 1st storage account already). In case this is what's happening to you, you get around this by doing one of the two things

1. you can add try to force migrate a single asset by adding '--skip-migrated False' in the asset command, you can see command line usage if you do 'AMSMigrate.exe assets -h'

2. you can try to reset the state of all input asset to 'Not Migrated' by using 'AMSMigrate.exe reset', you can see the command line usage if you do 'AMSMigrate.exe -h', after that you can do a full migration of all assets again.

Also, I wanted to clarify that you didn't set '--copy-nonstreamable' to False in asset command, right? That would prevent copying of the non_ism assets as well.

please let me know if this helps, if not, we'll need more information for you, like the command line, output logs to see what happened.