Feature Request - RDImport specific cut audio replacement

[alexolivan]

While perfectly doable in GUI (Edit Audio -> Save as new external file on the ext. editor -> Import/Export -> select the previous created file, you're done), the matter comes as I've been unable to automate that to some extent (like some other systems do).

Knowing Cart and Cut from filename (very clever!), group also very easy to get from a SQL select on the cart table (I expected needing to struggle with joins... but a grup name field is there, nice! ), the idea is to script a copy of the audio file, open audacity against it, and upon exporting the file, trigger an automatic rdimport.

The problem is that (I could be wrong! correct me otherwise!) at that point, rdimport seems to be designed to import a NEW material, caring therefore about its associated metadata, etc... while it seems unable to import into an existing material (where metadata could eventually be irrelevant)

My idea is that you could have a --cut=XXX option where you could target an specific cut, and possibly something like --no-metadata , so the metadata present in DDBB is preserved, and just the audio is imported (Much like you do in GUI with Import/export)

Regards.

[druidlabs]

Depending on how deep you want to get, you might take a look at RDacity, a project to provide a workflow between Rivendell and Audacity. I know nothing else about it, but the project is on github here: https://github.com/RadioFreeAsia/RDacity. Note that the last update was 4+ years ago, so there may be some issues that were causing problems with the integration. Mike

…

On Thu, May 20, 2021 at 4:13 AM Alejandro Olivan Alvarez < ***@***.***> wrote: While perfectly doable in GUI (Edit Audio -> Save as new external file on the ext. editor -> Import/Export -> select the previous created file, you're done), the matter comes as I've been unable to automate that to some extent (like some other systems do). Knowing Cart and Cut from filename (very clever!), group also very easy to get from a SQL select on the cart table (I expected needing to struggle with joins... but a grup name field is there, nice! ), the idea is to script a copy of the audio file, open audacity against it, and upon exporting the file, trigger an automatic rdimport. The problem is that (I could be wrong! correct me otherwise!) at that point, rdimport seems to be designed to import a NEW material, caring therefore about its associated metadata, etc... while it seems unable to import into an existing material (where metadata could eventually be irrelevant) My idea is that you could have a --cut=XXX option where you could target an specific cut, and possibly something like --no-metadata , so the metadata present in DDBB is preserved, and just the audio is imported (Much like you do in GUI with Import/export) Regards. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#666>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACBX74KGVMFJYTVVC5P7M6DTOTVEBANCNFSM45GYM6TQ> .

[alexolivan]

Hi!
I tried that way... and I opened an issue there... but in the end, it looked to me as if that was used back in time whit Rivendell 2.x and was for some reason discontinued (maybe I'm wrong and Rivendell users do use it!) ... The RDAcity project/idea sounds absolutely amazing to me.

Long Histoy short: I managed to build, but failed in the linking ... reaaaaaally close! The preblem was I had not rivendell package installed on the building machine, I bet this could be overcome, but as you point out, my fear was that that project being quite older than the current version of Rivendell maybe it has become incompatible, and it all is wasting time.

If someone has experience on it With Rivendell 3.X (or even 4.X) please share it!

Thank you very much for your advice! best regards!