Recherche avancée

Sur d’autres sites (11531)

• Oddly-named file "not found" when trying to move/copy via MacOS Terminal [closed]

  15 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 !

  


• Revert "avcodec/nvenc : fix b-frame DTS behavior with fractional framerates"

  14 juin 2023, par Timo Rothenpieler

  Revert "avcodec/nvenc : fix b-frame DTS behavior with fractional framerates"
  This reverts commit 9a245bdf5d7860b8bc5e5c21a105a075925b719a.
  This commit basically broke all samples with fractional framerates,
  
  rather than fixing them.
  
  I at this point do not understand the original issue anymore, and I'm
  
  not sure how this slipped my initial testing.
  
  All my test samples must have happened to have a simple timebase.
  The actual dts values pretty much always are just a simple chain of
  
  1,2,3,4,5,... Or maybe slightly bigger steps. Each increase by one means
  
  an advance in time by one unit of the timebase.
  
  So a fractional framerate/timebase is already not an issue.
  So with this patch applied, the calculation might end up substracting
  
  huge values (1001 is a common one) from the dts, which would be an
  
  offset of that many frames, not of that many fractions of a second.
  
  This broke at least muxing into mp4, if the sample happened to have a
  
  fractional framerate.
  I do not thing the original issue this patch tried to fix existed in the
  
  first place, so it can be reverted without further consequences.
  

  • [DH] libavcodec/nvenc.c

• ffmpeg wont "gracefully" terminate using q or kill -2

  24 mai 2023, par Jeff Thompson

  I am trying to run a bash command on Ubuntu to pull video from a stream and make an .mp4 with it. Here is the command I am using.

  


  ffmpeg -rtsp_transport tcp -i 'rtsp://username:password!@ipaddress/?inst=1' -c copy -f segment -segment_time 180 -reset_timestamps 1 ipaddress_day_3_2_%d.mp4

  


  It connects and begins copying the stream fine, the issue comes with trying to stop the process. It states press [q] to stop, which does not work. I have also tried kill -2 pid and kill -15 pid. Where pid is the process id. However kill -9 pid works and ctrl+c works. The issue with killing it this way is it corrupts the .mp4 rendering it useless. This is the error I get when using ctrl+c or kill -9.

  


  av_interleaved_write_frame(): Immediate exit requested   [segment @ 0x56337ec42980] Failure occurred when ending segment 'ipaddress_day_3_2_0.mp4' Error writing trailer of ipaddress_day_3_2_0%d.mp4: Immediate exit requested

  


  One thing to note is pressing [q] did work once, when I first started working on this but has not since.

  


  Thank You.

  


  I have tried kill -2 pid, kill -15 pid and [q], which I expected to "gracefully" terminate it.
kill -9 pid and ctrl+c will forcefully terminate it but corrupt the file.