Facebook Stories are are different from the Facebook posts you usually see on your timeline - they're short photo and video collections from Facebook users that can be viewed an unlimited amount of times and disappear after 24 hours
The story format, originated and made famous by Snapchat, was added as a feature on Facebook in 2017. Today, one billion stories are shared on social media across Facebook, Messenger, Instagram, and WhatsApp every single day.
Hi I am using Vegas Pro 12 to create time-lapse video which I would like to post on Facebook story. I recorded the video in landscape mode. After editing everything and rendering, the video becomes portrait and squished when I try to upload it to Facebook story. I want to post it as landscape. If I try to upload the raw unedited video directly from my phone, it uploads as a landscape video. Can anyone help me with this issue. I feel like I need to play with render setting to fix this problem. Thanks in advance!
If the file plays correctly on your pc it would appear to be a Facebook problem. But to be certain post media info on your file so we can check there's nothing wrong with it. Instructions here -how-to-post-mediainfo-and-vegas-pro-file-properties--104561/
Here is what I mean by squished. Sorry I don't know the correct term haha. First picture is how I see it on my phone. Second picture is when I try to upload it on Facebook. If I try to upload unedited video from my phone then it uploads fine in landscape.
Transferred it to my phone through a cable & uploaded to FB Stories, the size difference made no difference, it was still squished, . I like squished ?but I'd say it was more stretched than squished ?
Nothing to do with render settings and most likely nothing you can do about it except attempt a different way of posting the video.
Facebook & Instagram are platforms that are notorious for doing random switches on video formats. I haven't been in the game for a while, but I suggest looking up the ideal resolution. If the most upto date search yields that what you're doing is correct, then it's most definitely a bug related to the phone app (which is also typical of facebook)
@Mohammed_Anis Really the video should be rendered in a portrait mode then I'm sure it will be fine, but I want to know why unedited phone clips load as they are with no stretching but the OP's Vegas edited 1280x720 ones get stretched,
@Former user Seems like a bug with FB then. My original renders were in 1920x1080 and they did not work for me so I tried 1280x720 and it made no difference. Can you please share your render settings with me just so I know I am not doing anything stupid. I started an automotive repair shop and was planning to upload a bunch of time-lapse videos of my repairs on my FB page for marketing purposes but its all good if FB has a bug. I really appreciate your help as well as others who are trying to help me. Thanks!! ?
@zenoo This was the last setting i used, the third picture above this comment, 1280 x 720 in Vegas, it's either a preset or was just one of the presets that at some point i changed the Frame size, I don't normally fiddle with the other settings, I hope you work it out
So I rendered it again in MainConcept AVC/AAC like @EricLNZ mentioned and used @Former user render settings which were pretty much the same as what I had. The video was still stretched/squished I when uploaded it from my personal profile. But when I uploaded it from my business page it was in landscape. Its strange but it ended up working out for me. Thank you guys for all your help! I really appreciate it.?
On the desktop when I watch a video posted to Facebook Days/Stories using Safari, I can right click the video and press "Copy video address" and I will get the real URL. But in Chrome, it gives me a blob URL.
"Inspect element" doesn't reveal the video's real URL, so how do I get it in Chrome, both with and without a plugin? Can it be done in Edge? Internet Explorer? If you suggest a plugin, it must be able to give me the video URL as opposed to just downloading the video.
The two files are loaded in chunks (streamed). The URL used to load the chunk of MP4 file specifies the bytestart and byteend as parameters to tell the server which section of the video or audio file is being loaded.
I found out this info by opening the developer tools in the chrome browser, and looking at the Network Tab while a video file was playing. put the text MP4 into the filter function, so only urls matching the text MP4 are displayed.
To get the complete video file and complete audio file, you would need to get the URLs for both MP4 files. Once you have 2 unique MP4 file URLs, alter the bytestart parameter to 0 and the byteend parameter to something really large like 9999999 (im not sure what the max byte size you can use is, but you could experiment with it, if you are not getting the complete file, try making the byteend number larger.
Update Having said all that, on the mobile version of the website, facebook does serve complete video/audio files, so if you get the URL for the Story from the desktop site, e.g change it to the mobile website version by replacing "www" with "m"i.e
Then load the Story, if you look at the network tab this time, and filter the urls for mp4, you should see a url for a single combined video and audio file, that you can copy and paste into your browser, then once its loaded you should be able to save the file. Or alternatively simply inspect the HTML code of the page, and look for the
One day, a rotational product manager, Bowen Pan, joined Facebook and said he wanted to work on enabling commerce within Facebook groups. He had previously worked on TradeMe in New Zealand and saw what Facebook could do. Vijaye Raji, our engineering lead, immediately pulled a couple of engineers from our team, and we started testing a product we called Groups Commerce.
We debated for some time and finally decided that having a tab in the largest app in the world was preferable to having a separate app. The ability to work within the Facebook ecosystem, where millions of people were already trading in communities, made this decision a no-brainer. Though we expected to launch a separate app once Marketplace became successful, you will likely notice that it never happened in the years since, because the experience was better integrated into Facebook itself.
Some items were more suited to Groups, such as marbles, which were mostly bought and sold by enthusiasts within their own communities. However, many sellers wanted to drive maximum discovery to move items, especially larger ones, like furniture, cars, and electronics. As we tested cross-posting, we were able to assess the quality and diversity of the inventory that would show up in the new Marketplace Tab well before launch. Typically, we turned on cross-posting within Groups for two months before we rolled out Marketplace in that area.
The launch of Marketplace happened on October 4, 2016. This was the New York Times headline heralding the rollout of a product we had been working on for a year and a half, a product I had dreamt of for seven years:
People use Facebook widely and frequently, often multiple times a day. Adding a local and shipped commerce solution only extended the value of the app and the things that could be done with it. The fact that you can have the app open already and see when something new comes up for sale is part of the serendipitous discovery aspect of Marketplace.
Being integrated with Facebook Messenger makes communication fast and easy. It allows you to pin your location and have someone come to you, or easily send a deposit to someone. This has greatly streamlined the buying and selling process.
I am a member of a Buy Nothing group, and I also regularly buy and sell on Marketplace. I bought an entire bedroom set from someone moving down the street, who turned out to be a friend of a friend. I bought my kids two digital cameras from a student I had met at Stanford just the year before. This idea of people-powered commerce, buying from your neighbors, and reducing waste was part of the ethos of the product from the start.
From the start, we noticed that some of the most popular items on Marketplace were cars and rentals, which surprised us. We did not realize that there was such demand for these big-ticket items online. We started working on structuring posts so that people could easily list places for rent and cars for sale. This enabled us to double down on these new verticals, which helped us become key players in those markets.
While the product started primarily for mobile, we realized that to be competitive, we needed to add a desktop version. This was important for larger purchases and would make listing easier for high-volume sellers.
The desktop version was launched about a year and a half after the initial mobile launch in October 2016. We noticed that participation on desktop was significantly higher in high-consideration categories, such as furniture, rentals, and motor vehicles, where people liked to comparison-shop in different tabs.
In addition to the desktop version, some countries primarily relied on Facebook Lite, so we also had to adapt our product to ensure that it worked for those users. As we launched on new platforms like desktop, Facebook Lite, and mobile web, we saw an increase in engagement and transactions.
We saw different problems arise in different countries, which complicated things. In one country, the issue of selling diplomas (i.e. printed certifications) appeared. This is less of an issue in other countries, so we had to decide what to do with the policy. We had to find a way to keep that particular country safe, such as detecting violations and allowing reporting of these local issues, without adding substantial hurdles in other countries where this was not a problem.
59fb9ae87f