search

mipops / dvrescue

Archivist-made software that supports data migration from DV tapes into digital files suitable for long-term preservation. Snapshot daily builds are at https://mediaarea.net/download/snapshots/binary/dvrescue/.
BSD 3-Clause "New" or "Revised" License
93 stars 20 forks source link

dvrescue GUI - ending multiple capture bug #819

Open libbyhopfauf opened 8 months ago

libbyhopfauf commented 8 months ago

I just did some testing with version 2023-11-11. Capture works great with a single deck. But when I start a capture on a second deck, it'll start recording for about 5 seconds and then quit capturing on both decks. The GUI then swaps the placement of the two decks:

https://github.com/mipops/dvrescue/assets/13877631/8b36a7d4-30da-4248-a454-d6c06241f338

Another observation observation regarding multiple decks is when you first open the DVRescue GUI, the response time for connecting/disconnecting devices is very fast, but once the GUI has been open for awhile capturing with a single deck, if you connect a second device, the response time is really slow and half the time, the second deck won't show up unless you close the GUI and reopen it. In general, decks being detected seems really in consistent. Sometimes when I open the GUI with a device connected, it will either take forever to detect the deck or I have to close and reopen multiple times for even a single deck to be detected.

libbyhopfauf commented 8 months ago

Will test this more tomorrow and send reports if it still seems to be an issue with the new release.

libbyhopfauf commented 7 months ago

This seems to be happening inconsistently with the latest build (sometimes it will end the capture early, sometimes it won't). Will continue testing on various computers to see if it is isolated to M1/M2 models.

ElderOrb commented 2 months ago

@libbyhopfauf still an issue? if yes, @JeromeMartinez will it be possible to add periodic re-reading simulator's txt file with a list of devices - it would allow me to manipulate it with a script and investigate further connect/disconnect behaviour