Size Limit on Importing MP4s?

I recorded 4 videos on my Android phone then sent them to my iMac. All of them play perfectly on my iMac. The two under 1 GB play fine when imported to SF. However, the two over 1 GB get imported into SF, but only about the first 25% play correctly. The rest of the import has little or no audio, and very sporadic choppy video. Any thoughts? Thanks in advance!

Greg

12replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • There's no size limit in ScreenFlow. Perhaps the computer's resources are taxed. CPU decoding, RAM, hard drive space the files are stored on, are all factors.

    Try creating a new document and importing just one of the large files and see how it plays back.

    Please make sure ScreenFlow and your macOS are up to date (ScreenFlow 7.3.2 or 8.2.2 and macOS 10.13.6 or 10.14.2).

    Reply Like
  • The Activity Monitor doesn't show any stresses on the CPU or memory. The iMac hard drive has plenty of space. I have latest versions of both macOS and ScreenFlow. However, I will try a new document and see how that works. Thank you for your reply.

    Reply Like
  • Trying to import into a new document (after shutting down SF then starting it again) had the same exact result. A process called net.telestream.screenflow8.diba was taking up 98.5% of CPU during the import. So... is there any way to compress the mp4 safely without affecting the quality too much? I can't re-shoot the video. The event is over and done with. Thank you again for your help!

    Reply Like
  • OK... I've just loaded the same MP4 into iMovie and edited it with no problem. Why can't I do that with my $129 program? I've had no problems up to now with ScreenFlow, but am very frustrated at this point.

    Reply Like
  • Greg Kleist said:
    The Activity Monitor doesn't show any stresses on the CPU or memory.

     Decoder challenges aren't necessarily shown by CPU load.

    Greg Kleist said:
    Trying to import into a new document (after shutting down SF then starting it again) had the same exact result. A process called net.telestream.screenflow8.diba was taking up 98.5% of CPU during the import.

     That may be a factor. There may be an issue decoding the file.
    Compare that to one of the easy to decode files.

    Greg Kleist said:
    I've had no problems up to now with ScreenFlow, but am very frustrated at this point.

     Are you using ScreenFlow 8.2.2 specifically?

    Reply Like
  • CraigS Yes. I'm using 8.2.2. But those files still loading/working fine in iMovie.

    Reply Like
  • Greg Kleist Can you link to one of the problem files (can be Dropbox or Google Drive) so I can download and have a look on my system?

    Reply Like
  • CraigS I'd prefer not to post publicly. Any way I can get to just you?

    Thanks,

    Greg

    Reply Like
  • Greg Kleist you can send me the link by forum private message. Click on my profile icon and select Message.

    Reply Like
  • Greg Kleist Thanks for that.
    Tested on my iMac Pro and ScreenFlow 8.2.2. 
    I see the same issue as you. Audio loads to about one minute.
    Tested in our Switch 4.5.2 analysis software and it shows an audio playback issue similar to ScreenFlow.
    Tested in Quicktime Player and there's no issue with the audio.

    GOP structure is one Key Frame (I Frame) every second with 29 P Frames in between. Audio looks to be 128kbps Stereo 48kHz AAC file. This shouldn't be an issue.

    It's possible there's an issue with our decoder.

    Please do fill out the form and include my comments and we'll send you a case number while we work on fixing this. Include the link to the file in the form.

    ScreenFlow Support Form
     

    Reply Like
  • CraigS  Thank you, Craig! I've already shared the problem with Abdul via the support form. Here is what he advised me (if you haven't already heard from him):

    Thank you for sending me the problematic file, I am not sure precisely the issue, but I did have the same problem. 

    I will have to submit this as a "bug", but I was able to re-encode the file and get it to play correctly in ScreenFlow.

    Right-Click on your MP4 and select "Encode Selected File(s)"

    A dialog box should appear and you will want to change the resolution from the default preset (480p) to 720p to match the resolution of the file as it is now.

    This will create a .mov file the should load and play in ScreenFlow.

    This did fix the problem, even though it was not a smooth as just importing the .mp4 file. That process actually produced an .m4v file instead of the .mov Abdul said it would. I certainly don't know the difference (if any) between the two file formats, but the .m4v worked like a champ, so I'm a happy camper!

    Thank you again for your help and support!

    Greg

    Reply Like
  • Greg Kleist .m4v is just a variant of .mp4 usually meant to show it's compatible with Apple devices (which is also compatible with ScreenFlow of course). To do .mov you'd select Apple ProRes which would make a very large file (but very easy to playback).

    We'll working on fixing the compatibility issue of course.

    Reply Like
Like Follow
  • 2 mths agoLast active
  • 12Replies
  • 298Views
  • 2 Following