Open libbyhopfauf opened 1 year ago
I have been trying to install this GUI too. After installing the current version the capture window was showing just a blank white screen. I then discovered this GitHub issue and installed the 2023-07-15 versions. The capture window now says "NO DV DECK DETECTED". The vrecord GUI detects the deck and can successfully capture, as can iMovie and QT Player. I have run through all the recommended steps at https://mipops.github.io/dvrescue/sections/installation.html
MacBook Air M2, macOS Ventura 13.4.1 Sony DSR-40P with a complex daisy chain to Thunderbolt 3 DV Rescue GUI version: devel Jul 15 2023 dvrescue CLI version: 0.22.10 Interestingly "vrecord -e" GUI deck control is flaky, sometimes works, sometimes not. Can supply other details if asked.
ETA: In Ventura Security Settings I cannot give dvrescue Camera access - there is no "add" button. I did give it full disk access.
I have just installed dvrescue 0.21.11.20231025 This version eventually detects the deck but shows "parsing error" and "NO SIGNAL" notes and does not show pictures from tape. Deck controls work but with a 4sec lag. Two attempted captures resulted in empty dv files. DVRESCUE_SESSIONS_2023-10-28_COMMAND_LOG.log CHINA_TAPE_5_DVRESCUE_TEST_2.dv.capture.log CHINA_TAPE_5_DVRESCUE_TEST_2.dv.dvrescue.xml.txt
Media Info for resulting .dv file:
CHINA_TAPE_5_DVRESCUE_TEST_2.dv
File size: 0.00 Byte
Regarding the parsing error, can you send 'dvrescue -list-devices-json'.
My capture device is a Sony DSR-40P
twelveplusone@Toms-MacBook-Air ~ % dvrescue --list_devices -json
DV
twelveplusone@Toms-MacBook-Air ~ %
Can you remove the space before -json and rerun.
Error: missing value after --list_devices-json.
Is --list_devices_json
Does this help?
avfctl -list_devices
2023-10-29 09:07:01.911 avfctl[55154:2651497] Devices:
2023-10-29 09:07:01.911 avfctl[55154:2651497] [0] DV
sorry, my bad for trying type this on my phone dvresuce --list_devices_json
[0] DV
? And that's a Sony DSR-40P?
@dericed Yes
dvrescue --list_devices_json returns:
Error: missing value after --list_devices_json.
Does this help? avfctl -list_devices 2023-10-29 09:07:01.911 avfctl[55154:2651497] Devices: 2023-10-29 09:07:01.911 avfctl[55154:2651497] [0] DV
Helps a bit, but the dvrescue gui is parsing the json output of dvresuce --list_devices_json
so that helps more.
@tomackroyd can you update to https://old.mediaarea.net/download/snapshots/binary/dvrescue/20231028/ and retry
@dericed Done. Installed from dvrescue_CLI_0.21.11.20231028_Mac.dmg But in Terminal:
~ % dvrescue --version
DVRescue v.0.22.10 (MediaInfoLib v.22.09) by MIPoPS.
Same result. CHINA_TAPE_5_DVRESCUE_TEST_3.dv.dvrescue xml.txt CHINA_TAPE_5_DVRESCUE_TEST_3.dv.capture.log DVRESCUE_SESSIONS_2023-10-29_COMMAND_LOG_1.log
Is --list_devices_json
~ % Is --list_devices_json
zsh: command not found: Is
Is was a verb. Try that option with dvrescue.
~ % dvrescue --list_devices_json
Error: missing value after --list_devices_json.
Interesting that dvrescue_GUI_0.21.11.20231006_Mac.app sees the deck, but instead of the parsing error, identifies it (incorrectly) as "[0] DV-VCR (Sony GV-D1000)" also has a "NO SIGNAL" screen. dvrescue_GUI_0.21.11.20231025_Mac.app still has the parsing error
Hi @tomackroyd, it still seems that you don't have a recent dvrescue cli installed.
for me, I get:
$ dvrescue --version
DVRescue v.0.21.11.20231030 (MediaInfoLib v.23.10) by MIPoPS.
$ dvrescue --list_devices_json
[{"id":"0x800460104f1243e","name":"DV-VCR (Sony HVR-M15U)","type":"DV"}]
Could you run:
which dvrescue ; ls -l $(which dvrescue) ; dvrescue --version
Or perhaps you have multiple dvrescue cli in your path.
twelveplusone@Toms-MacBook-Air ~ % brew upgrade dvrescue
Running `brew update --auto-update`...
==> Auto-updated Homebrew!
Updated 2 taps (homebrew/core and homebrew/cask).
==> New Formulae
daktilo lager modsurfer pmix sigma-cli zug
==> New Casks
deveco-studio metamer music-decoy
You have 8 outdated formulae installed.
Warning: mediaarea/mediaarea/dvrescue 0.22.10 already installed
twelveplusone@Toms-MacBook-Air ~ % which dvrescue ; ls -l $(which dvrescue) ; dvrescue --version
/opt/homebrew/bin/dvrescue
lrwxr-xr-x 1 twelveplusone admin 39 26 Oct 18:46 /opt/homebrew/bin/dvrescue -> ../Cellar/dvrescue/0.22.10/bin/dvrescue
DVRescue v.0.22.10 (MediaInfoLib v.22.09) by MIPoPS.
twelveplusone@Toms-MacBook-Air ~ % dvrescue --version
DVRescue v.0.22.10 (MediaInfoLib v.22.09) by MIPoPS.
twelveplusone@Toms-MacBook-Air ~ %
Thanks for the handholding @dericed here is me poking around finding 2 dvrescues:
twelveplusone@Toms-MacBook-Air ~ % /usr/local/bin/dvrescue --version
DVRescue v.0.21.11.20231028 (MediaInfoLib v.23.10) by MIPoPS.
twelveplusone@Toms-MacBook-Air ~ %
twelveplusone@Toms-MacBook-Air ~ % /opt/homebrew/Cellar/dvrescue/0.22.10/bin/dvrescue --version
DVRescue v.0.22.10 (MediaInfoLib v.22.09) by MIPoPS.
twelveplusone@Toms-MacBook-Air ~ %
yup, so all my earlier advise applies to /usr/local/bin/dvrescue --version
. You could also run brew unlink dvrescue
to kick the old release out of the way.
Thanks for the fix. Not sure how I ended up with two versions - I normally use Homebrew and followed the instructions at https://mipops.github.io/dvrescue/sections/installation.html - but the standalone CLI installers put it in a different place - is this something that will trip up other users?
@tomackroyd Yes, that is an outdated part of the instructions. I will update it now! Thank you for letting us know.
I'm still unsure how to continue using dvrescue without using Homebrew. Could anyone do me an explainer? @dericed I followed your advice and unlinked dvrescue, but of course now I get this when running brew doctor
Warning: You have unlinked kegs in your Cellar.
Leaving kegs unlinked can lead to build-trouble and cause formulae that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
dvrescue
I'm still unsure how to continue using dvrescue without using Homebrew. Could anyone do me an explainer? @dericed I followed your advice and unlinked dvrescue, but of course now I get this when running
brew doctor
Warning: You have unlinked kegs in your Cellar. Leaving kegs unlinked can lead to build-trouble and cause formulae that depend on those kegs to fail to run properly once built. Run `brew link` on these: dvrescue
@tomackroyd would you mind running the following commands to update homebrew:
brew update
brew upgrade
brew cleanup
brew doctor
And then install the 2023-11-11 version of the DVRescue GUI and open it directly from the install window?
I was experiencing similar issues as you were with previous versions, but they now seem to be resolved with the latest version, so am curious to know if it works for you now.
@libbyhopfauf I ran all those commands, downloaded (actually the latest) dvrescue_GUI_0.21.11.20231113_Mac.dmg, and launched it directly from the disk image Finder window.
(I still have the Homebrew-installed dvrescue unlinked.)
twelveplusone@Toms-MacBook-Air ~ % /opt/homebrew/Cellar/dvrescue/0.22.10/bin/dvrescue --version
DVRescue v.0.22.10 (MediaInfoLib v.22.09) by MIPoPS.
twelveplusone@Toms-MacBook-Air ~ % /usr/local/bin/dvrescue --version
DVRescue v.0.21.11.20231106 (MediaInfoLib v.23.10) by MIPoPS.
twelveplusone@Toms-MacBook-Air ~ % dvrescue --list_devices_json
[{"id":"0x800460101ab28fb","name":"DV","type":"DV"}]
dvrescue GUI identifies the deck as DV (DV), transport control works, still "NO SIGNAL"
I attempted a capture, resulting in an empty file test.dv.capture.log test.dv.dvrescue_xml.txt
twelveplusone@Toms-MacBook-Air ~ % dvrescue /Users/twelveplusone/Movies/test.dv
<?xml version="1.0" encoding="UTF-8"?>
<dvrescue xmlns="https://mediaarea.net/dvrescue" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="https://mediaarea.net/dvrescue https://mediaarea.net/dvrescue/dvrescue.xsd" version="1.2.1">
<creator>
<program>dvrescue</program>
<version>0.21.11.20231106</version>
<library version="23.10">MediaInfoLib</library>
</creator>
<media ref="/Users/twelveplusone/Movies/test.dv" error="not DV"/>
</dvrescue>
twelveplusone@Toms-MacBook-Air ~ %
[NB I recently upgraded to Sonoma macOS 14.1.1]
I should add that vrecord is still not working for me, pending me being able to test https://github.com/amiaopensource/vrecord/pull/770 once vrecord is updated.
@tomackroyd would you mind trying the latest builds of vrecord and dvrescue and let us know if you're able to capture now?
Also, the no signal just means that the device is connect successfully to the DVRescue GUI, it just isn't playing/the software isn't receiving any information from the device. Just to double check, is your deck in remote mode? That might be why it's failing to play and the recording is just an empty file.
@libbyhopfauf will do, just may be a day or two. DVRescue does play the tape and captures info, just not picture and sound! See log in previous comment (test.dv.dvrescue_xml.txt) Tom
@libbyhopfauf How do I install the latest vrecord build? Homebrew is saying latest version is 2023-08-07
Have tested with dvrescue_GUI_22.12.20231208_Mac - no change:
DVRescue generates following logs from capture process:
FramePos,abst,abst_r,abst_nc,tc,tc_r,tc_nc,rdt,rdt_r,rdt_nc,rec_start,rec_end,Used,Status,Comments,BlockErrors,BlockErrors_Even,IssueFixed,SourceSpeed,FrameSpeed,InputPos,OutputPos
<?xml version="1.0" encoding="UTF-8"?>
<dvrescue xmlns="https://mediaarea.net/dvrescue" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="https://mediaarea.net/dvrescue https://mediaarea.net/dvrescue/dvrescue.xsd" version="1.2.1">
<creator>
<program>dvrescue</program>
<version>0.21.11.20231025</version>
<library version="23.10">MediaInfoLib</library>
</creator>
<media ref="-" fromCapture="device://0x800460101ab28fb" format="DV">
<frames count="175" pts="00:00:00.000000" end_pts="00:00:07.000000" size="720x576" video_rate="25" chroma_subsampling="4:2:0" aspect_ratio="4/3" audio_rate="48000" channels="2" speed="33">
<frame n="0" pos="0" pts="00:00:00.000000" abst="7847" tc="00:00:26:04" rdt="2001-03-08 17:33:31" seqn="4"/>
<frame n="174" pos="25056000" pts="00:00:06.960000" abst="9935" tc="00:00:33:03" rdt="2001-03-08 17:33:38" seqn="A"/>
</frames>
</media>
</dvrescue>
Other terminal probes:
twelveplusone@Toms-MacBook-Air ~ % /usr/local/bin/dvrescue --version
DVRescue v.0.21.11.20231106 (MediaInfoLib v.23.10) by MIPoPS.
twelveplusone@Toms-MacBook-Air ~ % avfctl -list_devices
2023-12-12 20:41:17.255 avfctl[25594:857950] Devices:
2023-12-12 20:41:17.257 avfctl[25594:857950] [0 - 0x800460101ab28fb] DV
twelveplusone@Toms-MacBook-Air ~ % dvrescue --list_devices_json
[{"id":"0x800460101ab28fb","name":"DV","type":"DV"}]
vrecord still cannot see deck
Tom
@tomackroyd just to double check, is your deck or camcorder in remote mode? Also, have you checked/changed your security policy recently to allow dvrescue to capture? Here are the instructions for changing your permissions so that macOS allows you to record using dvrescue (jump to the "troubleshooting" section). I had to reset mine recently to get dvcapture to work for vrecord.
Having the same issue (No Signal) and would absolutely love to help be a guinea pig to help resolve it.
@900video I just replied to your post in issue #808, but I am wondering if you would mind testing the 2024-01-20 version of the daily build for the dvrescue GUI? I'm also curious if you have changed your security policy in recovery mode to "reduced security" and checked "allow" for the first option under that setting.
After adding the software to the applications folder, open the app directly from the install window by double clicking on the DVRescue icon (this will avoid any issues with the GUI using an older version of the CLI that you might have installed on your computer). Also, please wait about 10 seconds for the image to appear in the GUI playback window when recording. The file will contain all of the information, there is just a slight delay currently for the playback display.
I'm just curious because I was able to capture in the DVRescue GUI using the version above. Test files and logs are located here.
Here are the specs that I am working with:
@900video I just replied to your post in issue #808, but I am wondering if you would mind testing the 2024-01-20 version of the daily build for the dvrescue GUI? I'm also curious if you have changed your security policy in recovery mode to "reduced security" and checked "allow" for the first option under that setting.
After adding the software to the applications folder, open the app directly from the install window by double clicking on the DVRescue icon (this will avoid any issues with the GUI using an older version of the CLI that you might have installed on your computer). Also, please wait about 10 seconds for the image to appear in the GUI playback window when recording. The file will contain all of the information, there is just a slight delay currently for the playback display.
I'm just curious because I was able to capture in the DVRescue GUI using the version above. Test files and logs are located here.
Here are the specs that I am working with:
- computer = Macbook Pro (M2 Max Chip)
- macOS = Sonoma 14.2.1 (23C71)
- device = Sony DSR-45
- dvrescue version = 2024-01-20
- security policy = reduced
- full disk access = granted for dvrescue and Terminal
@tomackroyd would you mind testing the latest version as well and confirming your security policy? Thank you so much for all your tests you've been doing!
Hi Libby. Have tried everything, no dice I'm afraid. Ran: brew update brew upgrade brew cleanup brew doctor
computer = Macbook Air (M2, 2002 = Mac14,2)
macOS = Sonoma 14.2.1 (23C71)
device = Sony DSR-40P
device remote = on
dvrescue version = 2024-01-20
System Integrity Protection disabled (csrutil disable
)
security policy = reduced with "allow user management" etc checked
full disk access = granted for dvrescue and Terminal
screen and system audio recording = granted for dvrescue
Launched from dvrescue_GUI_22.12.20240127_Mac.dmg: /Volumes/dvrescue/dvrescue.app Deck recognised, waited 10secs, transport works, still NO SIGNAL Tried with remote off, still NO SIGNAL
Tom
Edit - here is a screenshot showing QuickTime seeing video:
Freakishly, I captured this screenshot: QuickTime seeing pictures, DVRescue seeing a different frozen picture but displaying DV metadata:
And now, DVrescue seeing moving images at same time as QT, with a delay, cannot replicate, also could not capture using DVrescue.
It seems running DVRescue at same time as QTP sometimes causes a clash, QTP sees a freeze frame while deck is in play mode.
I have discovered you can add dvrescue to Camera permissions in recent macOS with the new System Settings layouts. While there are no + or - buttons in that pane, if you drag the app onto it, it will appear in the list. Having said that, dvrescue has Camera, Full Disk and Screen Recording permissions, but still NO SIGNAL, even after several restarts and permission resets, and waiting 10 seconds, and with remote on. Occasionally the transport controls stop working and this can only be fixed with a restart. I thinks it's advisable not to run DVRescue concurrently with QuickTime Player New Movie Recording!
@tomackroyd Thank you so much for all this! I will update the documentation to reflect the drag and drop of dvrescue into the camera permissions.
That makes sense that running dvrescue and QT at the same time would cause a crash from both programs trying to communicate with the deck. I know this sounds like a silly question, but QT hasn't been running every time that you attempt to use the DVRescue GUI, right? Just wanted to check because it looks like you have the same set-up that I do, so I'm not sure why it's not working.
One other question: the tape that you're trying to run isn't HDV is it? Again, just want to rule out any other possibilities!
@libbyhopfauf No, I never have QTP running concurrently, and these are standard def PAL miniDV tapes. (Also, please try and replicate the Camera permissions thing, I might have blinked!) - Tom
@tomackroyd okay, I didn't think so (and I really appreciated the visual comparison), just wanted to double-check! And also glad we can rule out HDV.
I wasn't able to replicate the Camera permissions drag/drop (I think because it's already in there so I can toggle the slider on and off and if I toggle it off and then drag the app in, the switch goes back to on, so that's cool). I added it to the documentation in case some other users are able to. It's great to know there's another option!
I'm so sorry to ask again, but you would mind trying the latest daily build and let me know if there's any change?
@tomackroyd @900video would you both mind downloading the latest release of DVRescue (released yesterday) and see if you can capture from the GUI? I will note that I've found the deck control to still be a little buggy for FF/REW, but capture is consistently working on multiple computers at the MIPoPS office and I'm just curious if the release fixes the issues that you two were having. Thank you so much!
@libbyhopfauf Running from the disk image at that link, dvrescue_GUI_24.01_Mac.dmg, DVRescue sees pictures from deck.
Have replaced above screen recording - hopefully this will demo some of the issues I have. Note when DVRescue transport controls are working, sometimes the video display shows a freeze frame when deck is playing. After playing with the controls some more, DVRescue "resets" and scans for decks. This results in moving pictures again. "FRAME TIME REC TIME" metadata display works when in playback, but when attempting a capture, display shows moving pictures but no FRAME TIME REC TIME metadata. Results in empty files. Also this happens regardless of whether deck is in remote. https://www.dropbox.com/scl/fi/j8j0shvjnjrz49pamlb7x/DVRESCUE_TESTS_2024-02-03.mov?rlkey=1f729xkngnk8kvusregbi56aw&dl=0
Hi @tomackroyd, I found this last dropbox link helpful and glad to see that your machine got past the No Signal image. Can you retest with the latest daily build at https://old.mediaarea.net/download/snapshots/binary/dvrescue-gui/ and let me know if the playback controls still become non-responsive after the first use of 'stop'.
Once you install the dvrescue daily build in your Applications folder, I suggest to run it via Terminal with /Applications/dvrescue.app/Contents/MacOS/dvrescue --log
then use the GUI to replicate the issue and then you can grab the log via cat ~/Library/Containers/net.MediaArea.dvrescue.mac-gui/Data/dvrescue-gui_logs/dvrescue-gui.log
I installed from dvrescue_GUI_22.12.20240425 and am back to "NO DV DECK DETECTED" Same result following "RESET" within the GUI Same result following brew upgrade etc Privacy and Security settings checked. QuickTime Player sees deck and signal. Same result following several restarts.
twelveplusone@Toms-MacBook-Air ~ % /Applications/dvrescue.app/Contents/Helpers/dvrescue --version\
DVRescue v.22.12.20240425 (MediaInfoLib v.24.04) by MIPoPS.
twelveplusone@Toms-MacBook-Air ~ % /Applications/dvrescue.app/Contents/Helpers/dvrescue --list_devices_json
[{"id":"0x800460101ab28fb","name":"DV","type":"DV"}]
twelveplusone@Toms-MacBook-Air ~ % dvrescue --version
DVRescue v.24.04 (MediaInfoLib v.24.03) by MIPoPS.
twelveplusone@Toms-MacBook-Air ~ % dvrescue --list_devices_json
[{"id":"0x800460101ab28fb","name":"DV","type":"DV"}]
Log here: https://gist.github.com/tomackroyd/cadf2b9aef8d63d222afbd78aa188d8b "execvp: Operation not permitted" error as before. Lines 375 to 381 are interesting?
[2024:04:27 12:32:10 +12:00] [debug] [thread 19211] launching process: "/Applications/dvrescue.app/Contents/Helpers/dvrescue" , arguments: ("-list_devices_json")
[2024:04:27 12:32:10 +12:00] [debug] [thread 19211] in a separate thread...
[2024:04:27 12:32:10 +12:00] [debug] [thread 19211] starting thread...
[2024:04:27 12:32:10 +12:00] [debug] [thread 19379] starting process from thread: QThread(0x6000016dc150)
[2024:04:27 12:32:10 +12:00] [debug] [thread 19379] process: 0x600002fc8ec0 state changed: QProcess::NotRunning => QProcess::Starting
[2024:04:27 12:32:10 +12:00] [debug] [thread 19379] process: 0x600002fc8ec0 state changed: QProcess::Starting => QProcess::NotRunning
[2024:04:27 12:32:10 +12:00] [debug] [thread 19379] error changed QThread(0x6000016dc150) : "incorrectly typed command"
[2024:04:27 12:32:10 +12:00] [debug] [thread 19379] QProcess::finished: 0 QProcess::NormalExit thread: QThread(0x6000016dc150)
[2024:04:27 12:32:10 +12:00] [debug] [thread 19211] emitting processFinished: 0 QProcess::NormalExit thread: QThread(0x6000016cc510)
[2024:04:27 12:32:10 +12:00] [debug] [thread 19211] [qml] queryDecks: got from dvrescue:
[2024:04:27 12:32:10 +12:00] [debug] [thread 19211] error occurred at thread QThread(0x6000016cc510) : "execvp: Operation not permitted"
With the latest build of dvrescue, the GUI is not capturing or successfully remote controlling decks. I've tested this on a Sony DSR-25 and a DSR-1500A and both are recognized as connected, but neither seem to be communicating with dvrescue (will not play, FF, REW, etc via the deck control buttons).
Rolling back to 2023-07-15 worked for playing and capturing, but would still not use deck control to FF or REW.