Hello, Tried to discover this video: http://s3.amazonaws.com/decoded_video/11829468990469319149.avi

and it says: “no video link found”. The video is there. What should I do to get this to work?

Thanks

I suggest you to request http://heywatch.com/download instead of discover. Discover has been done for youtube and others. Here, the link is direct so no need to find the hidden URL.

Thanks, for your reply. Now I have another problem.

I have created an api to automatically get the answer when the upload is complete. The server sends me the “video_id”. Now I create a job and I want to encode this video with a format. Now I get this error:

[job_id] => 57904 [error_code] => 105 (Wrong parameters for format or something like this)

Now I have the job id but I don’t know what video_id to update. How could I get also the video_id?

Also when I get the response for a encoded video I get only: encoded_video_id, filename and link

What video_id should I update in database? or how should I do this? to update the status of my video_id to encoded.

105 error means that the video settings you put in your format are wrong. Tell me what is the name of the format and maybe I can help. I just updated the ping after encode request, so you get the video_id and the job_id.

Thanks for your reply and the update, I tried with the video from the first post and the codec is Mobile 3GP. (Error while encoding the video Untitled in Mobile 3GP format: Wrong settings for video – maybe incorrect parameters such as bit_rate, rate, width or height) – the error from the site or 105 error sent to me.

I just tested to encode your video in 3GP and it works. Did you create the format?

No, the format from general formats… tested more that 1 time…

Here is the link: http://static.heywatch.com/videos/CkD46at5hw/Untitled.3gp

Now the Mobile 3GP is really a problem. We created a api that works with all the formats tried but at Mobile 3GP always send this message: “Wrong settings for video”. Please test your api like we do, not on your site. We created a site that uses this api and we cannot tell clients to enter my account and encode here. The response from your server is: (POST)[2007-07-13 (08:27:42)] Array ( [job_id] => 58924 (different for every video) [error_code] => 105 )

hi bruno, i’m working with adrian on this project. to show you what problem we’re encountering, i’ve recorded the screen and uploaded the video to screencast. please get back to us on fixing this problem.

regards

screencast video

Hi Dave,

Ok I got it. I check the point with Bruno and come back to you later tomorrow. It will be fixed!

Regards.

thanks Eric!

Dave,

We checked with Bruno the different possibilities. Actually, after testing Hey!Watch and following your screencast, it’s not logical at all you can encode manually directly on Hey!Watch and not with the APIbecause it’s the same format “Mobile 3GP”. So it can only come from the process.

For the moment, it seems not to come from us. So, could you please check your code to be sure. Then, we’ll go deeper. Maybe you should have a look to your POST request. But be sure we will solve this together to make TrailerEncoder a success ;)

Regards.

We have logs to every step:

—1. Upload to heywatch with: “&key=xxxxx&url=http://s3.amazonaws.com/decoded_video/11842416335307433640.avi &upload_id=11846539166017563234&title=FamiliaChitChit_owner_17072007073156_22”

—2. Response got from heywatch (POST): [upload_id] => 11846539166017563234 [key] => xxxxxxx [download_id] => 56573 [video_id] => 118152 All ok until now.

—3. Send to heywatch for encoding with selected format (here mobile 3gp): “&s3_directive=s3://xxxx:yyyy@encoded_video/&key=zzzzz&ping_url_if_error=http://trailerencoder.com/hey.php?error=118152 &format_id=13&keep_video_size=0&video_id=118152”

—4. Our server gets the following Post: “( [job_id] => 59140 [error_code] => 105 ) and Get with video_id: Array ( [error] => 118152 )”

Please tell us waht are we doing wrong? We make exactly the same for the other formats and it works.

hey eric, any news on this? it’s kind of holding up our launch… what do you suggest as next steps to identifying and fixing the bug?

kind regards,

Dave

Hi Dave,

Bruno will be back to you later this evening (french time). It will be solved, be sure of that.

Best.

Dave,

I think the issue may come from that part of your code: &keep_video_size=0

Could you retry without this? If it still doesn’t work, we will explore other paths.

Best.

Hello, It seems that “keep_video_size” was the problem for this format… It’s our code of course but in your api at the job says:

“keep_video_size : if “true”, will not resize the video (ignore width and height values of the selected format) “

It doesn’t say anything about an exception for mobile 3gp format. So I used it… Maybe you should add something like this to the documentation…

Anyway I’m glad the problem is solved. Thanks for the help.

You are right Adrian, we have to clarify this line because it’s confusing.

But we are much more glad too to see your problem fixed. Good luck in your project. Plan to release soon?

hey eric, we’re signing up a couple of key clients in the next week or two, and will be doing a big pr push then. we’ll keep you posted. are there many apps out there using the api yet?