[FFmpeg-user] Can I convert from .ram to .mp4?

[David]

Thanks for the courtesy of replying, Rodney!

Turns out I'd not noticed that I was still in the bin directory when I 
invoked first invoked ffmpeg.exe.  When I copied the executable into the 
folder where only the 317.ram was, ffmpeg worked as it ought to.

I'd not known about the user forum's proscription against pasting 
screenshots, so that won't happen again.

I think I did, in a later post, paste the TEXT from the PowerShell 
window into a message to the user forum.

Again, thanks for your kindness in replying!

Regards,
Dave

On 6/19/2020 8:48 AM, Rodney Baker wrote:
> On Thursday, 18 June 2020 2:56:24 ACST David wrote:
>> I've watched the video and invoked a simple command:
>>
>> ffmpeg -i 317.ram 317.mp4
>> which the Windows PowerShell said I had to change to
>> .\ffmpeg -i 317.ram 317.mp4
>> which I did.
>>
>> I have the ffmpeg.exe file in the same folder as the 317.ram, so do you
>> think that should work?  I'll paste here the PowerShell window showing
>> "Permission denied"
>>
>>
>>
>> Any comments or assistance would be appreciated!
>>
>> Regards,
>> Dave
> Dave,
>
> As others have suggested, you've not really provided enough information to
> properly diagnose this, but I'm also pretty sure this is a Windows problem,
> and one that I've seen recently with other video editing software.
>
> Are you using a recent build of Windows 10? If so, you're possibly running
> into an issue with Windows "Protected Folders", where "suspicious"
> applications (i.e. basically ones not written or signed by Microsoft) are
> denied write permissions to folders containing user data. This is presumably
> to guard against ransomware encrypting users' files.
>
> Search for Protected Folders in Settings - you should be able to find recently
> blocked programs and add ffmpeg to the list of permitted applications. I only
> know this because my son recently had this same issue with video editing
> software on his laptop.
>
> Next time you need to ask for help, though, please follow the pointers given
> by others and include the command line you're using along with full, uncut
> console output from ffmpeg (copied as text, not a screenshot).
>