Update capture.md #922
Update capture.md #922
Conversation
This update includes reorganizing the capture instructions to include a section for CLI vs. GUI. The CLI instructions were also broken down to include a section explaining how to build a CLI string, examples of frequently used capture commands and a list of the full commands (the last of which still needs to be updated and examples need to be added).
docs/_sections/capture.md
Outdated
|
|
||
| 7.) Type the files name. Add a space. Example: ```filename.dv``` | ||
|
|
||
| 8.) Type ```-m``` to note you want to merge the multiple capture attempts for problematic frames (dvrescue will automatically rewind and try to capture the frame again when it encouters a problematic frame). |
There was a problem hiding this comment.
this -m also needs an output - in this case, so the total would be -m -
docs/_sections/capture.md
Outdated
|
|
||
| 2.) You can either type ```dvrescue``` at the start of the command or include the path to the version of dvrescue you want to use. Example: ```/usr/local/bin/dvrescue``` | ||
|
|
||
| 4.) If you only have one device connected, dvrescue will automatically select it (device 0). If you have more than one device connected, add the device number ```device://1``` (for the corresponding deck you want to use for capture). Example (using the deck listed in step 1): ```dvrescue device://0``` |
There was a problem hiding this comment.
hmmm, don't you have the full guid in your result such as
$ dvrescue --list_devices
90:a1838cb4:00000000: UltraStudio 4K Mini [DeckLink]
There was a problem hiding this comment.
Whoops, looks like that was an old example. Will update. So people need to add full number if they have more than one device plugged in right?
There was a problem hiding this comment.
@dericed See latest additions to the pull request for changes :)
I translated the information that was in a Google Doc for the GUI capture documentation to markdown. The formatting could use some adjustments to make it look better, but that's not something I know how to do.
I cleaned up the formatting to make it all consistent and make the organizational hierarchy clearer.
|
@dericed I made all of your suggested changes and made sure all of the latest updates are in there. But them me know if you catch anything else I should change before merging this in :) |
This is a draft to update the packaging documentation,
I was using the wrong formatting to create hyperlinks in the documentation. This is now corrected.
|
@dericed can this be merged? |
updated draft of CLI commands (some not working)
|
@dericed So, I'm hitting a little bit of a brick wall trying to make the CLI documentation accurate. Across the board, with only one deck connected, if I do not specify the device, the capture command will not run. Also, it seemed like if I rand the first command that did work that it was rewinding/recapturing/merging even though I hadn't specified a rewind-count. These commands work:Capture from a specific device: Capture from a specific device and show a preview window: These commands do not:Capture from a specific device using rewind, recapture and merge (3 attempts): Capture from a specific device using rewind, recapture and merge (3 attempts), show a preview window (with only one deck connected): Basic capture (with only one deck connected): Basic capture (with only one deck connected), using rewind and recapture, plus playback view: I also tried this command and the terminal just hangs and doesn't interact with the deck. Here is the Terminal output (the numbers never change from 0, ffplay never opens, and the deck doesn't start playing): |
Update packaging.md
@dericed this is ready to be merged! I updated the images to reflect how the GUI looks and what information is present for capture in the latest build.
I retested all of the CLI commands using a DSR-45 and dvrescue CLI version 2024-08-24 and updated this documentation to reflect that. All CLI commands and examples in this documentation have been updated to reflect their current usage. Ready to merge!
|
@dericed this is ready to be merged! I updated the images to reflect how the GUI looks and what information is present for capture in the latest build. I also tested and updated all of the CLI commands and examples. Everything works and is good to go! |
This update includes reorganizing the capture instructions to include a section for CLI vs. GUI. The CLI instructions were also broken down to include a section explaining how to build a CLI string, examples of frequently used capture commands and a list of the full commands (the last of which still needs to be updated and examples need to be added).