Sur d’autres sites (11535)

• Unable to identify syntax required to rename files in MacOS Terminal [closed]

  18 juin 2024, par Ben C

  This is a head scratcher.

  


  I need to move these three oddly-named files from an external 2.5" SSD to my desktop. The file names were intended to have variables replaced by date info, however, clearly it didn't work. So I'm left with these filenames that MacOS seems to want to interpret rather than treat as a string. I wish it was as easy as tossing in single quotes or escaping chars, but so far, that hasn't worked.

  


  Files: Test01-$(internal:date_y)-$(internal:date_m)-$(internal:date_d)-.mp4 Test01-$(internal:date_y)-$(internal:date_m)-$(internal:date_d)-0001.mp4 Test01-$(internal:date_y)-$(internal:date_m)-$(internal:date_d)-0002.mp4

  


  I'm on MacOS. In the Finder, the files are not visible. But they are not hidden files.

  


  In Terminal, however, when I navigate to "/Volumes/TestDrive", then run a quick "ls", I can see all three files no problem. Including permissions, size, owners, full filename, etc.

  


  However, when I attempt to move the files to my desktop, and rename in the process (even if I don't rename), Terminal tells me that "No such file or folder can be found" or something very close to that.

  


  I've tried using mv and cp commands to put the filename in single quotes so the filename is read literally. Yet, I'm still given feedback that the file cannot be transferred because it cannot be found or doesn't exist.

  


  mv 'Test01-$(internal:date_y)-$(internal:date_m)-$(internal:date_d)-.mp4' ~/Desktop/Test01-01.mp4' 'cp 'Test01-$(internal:date_y)-$(internal:date_m)-$(internal:date_d)-.mp4' ~/Desktop/Test01-01.mp4

  


  When I try to escape special characters instead of quotes, I am also told the file doesn't exist. But clearly it does when I list out the contents of the drive. And there's only 3x .mp4 files, two hiddne files .fseventsd and some spotlight file.

  


  mv Test01-\$\(internal\:date_y\)-\$\(internal\:date_m\)-\$\(internal\:date_d\)-.mp4 ~/Desktop/Test01-01.mp4

  


  I've tried copying by inode. No luck. I've tried pulling the videos into ffmpeg (CLI based media mgmt tool) to see if I can get some info on the files, and same thing, ffmpeg (or ffprobe) both will tell me the file doesn't exist...even though I can list the files and see that it does.

  


  I hope I'm missing something obvious, but but it seems all the obvious approaches are not yet working for me.

  


  So my question is, what do I need to do to make these files "exist" so that I can rename them and back them up ? Happy to go down any rabbit hole.

  


  Thanks in advance !

  


• Mac Terminal (Bash) batch program to get multimedia file info using ffmpeg

  7 décembre 2013, par julesverne

  I have a Mac computer. Usually all my batch programming is done on my PC. So I tried to create what I assumed would be a simple equivalent using a Mac shell. Obviously as you all know that was foolish of me to think that. After 2 days of scowering the web I found the closest thing I could to what I was looking for. But no, this doesn't work either.

  All I'd like to do is throw a multimedia file onto the script, and have the terminal give me the ffmpeg info output. In my searching I did find this "$@" which as far as I can tell is the windows bat equivalent of %*. Meaning you can throw files on the script and the script refers to those files as variables which can be processed. So I believe what I want to do is possible.

  Again the code at the bottom is just to look through the current directory of all .mov files and run ffmpeg. It doesn't work. But.. if no one can help me figure out the actual thing I'd like to do then I'd settle with something like below that does actually work.

  #!/bin/bash
  
  FFMPEG=/Applications/ffmpeg
  
  FIND=/usr/bin/find
  
  FILES=$(${FIND} . -type f  -iname "*.mov")
  
  if [ "$FILES" == "" ]
  
  then
  
  echo "There are no *.mov file in $(pwd) directory"
  
  exit 1
  
  fi
  
  
  
  for f in *.mov
  
  do
  
  
  
  $FFMPEG -i "$f"
  
  
  
  done

  If someone can please help me figure this out I'd really appreciate it. Thank you in advance ! Jules

  I just found this solution from the "similar questions" sidebar, which is similar to the script above, so again, not completely what I wanted but.. didn't matter, didn't work for me. How to batch convert mp4 files to ogg with ffmpeg using a bash command or Ruby

• Recording audio with FFMPEG works in terminal but not through exec() of PHP

  8 août 2013, par lucasalmeida92

  I use this command to RECORD audio and video from my webcam in terminal and it works !

  ffmpeg -f video4linux2 -r 25 -sameq -s 640x480 -i /dev/video0 -f alsa -i plughw:0,0 -ar 22050 -ab 128k -y webcam.flv

  But when I do it through PHP, like this :

  echo shell_exec('ffmpeg -f video4linux2 -r 25 -sameq -s 640x480 -i /dev/video0 -f alsa -i plughw:0,0 -ar 22050 -ab 128k -y webcam.flv 2>&1 &') ;

  I receive that log :

  ffmpeg version 0.8.6-4:0.8.6-0ubuntu0.12.04.1, Copyright (c) 2000-2013 the Libav developers built on Apr 2 2013 17:02:36 with gcc 4.6.3 * THIS PROGRAM IS DEPRECATED * This program is only provided for compatibility and will be removed in a future release. Please use avconv instead. [video4linux2 @ 0x23579a0] Estimating duration from bitrate, this may be inaccurate Input #0, video4linux2, from '/dev/video0' : Duration : N/A, start : 4868.729067, bitrate : 122880 kb/s Stream #0.0 : Video : rawvideo, yuyv422, 640x480, 122880 kb/s, 25 tbr, 1000k tbn, 25 tbc Home directory /var/www not ours.

  ALSA lib pcm_hw.c:1401 :(_snd_pcm_hw_open) Invalid value for card [alsa @ 0x23589e0] cannot open audio device plughw:0,0 (No such file or directory) plughw:0,0 : Input/output error

  Before I got that Mic device problem I was having problem with the Webcam device's permissions, then i did :

      sudo chmod -R 777 /dev/video0

  And the video capture was ready to be used ! But now I got this Mic device problem !

  I think it can be about permissions too, but I dont know linux very well and have no idea how to fix that !

  Thanks !

  ---

  I just found the solution ! =x

  sudo chmod -R 666 /dev/snd/*