Help with a strange workflow.

Hi all, and specially hello LibRaw people.

I stumbled upon FRV from a suggestion from someone online while I'm looking at cleaning up and tightening my workflow to see if I can go from taking a year to process images to the shortest time possible.

I looked at FRV for a few minutes, and I misread the end date of the sale, and even when the cost for FRV could seem to be extremely reasonable, given mi economics I decided to "take the plunge". Specially when it seems like a well known product whose initals are P and M could so all I need, and more, I am very very very very far away from being able to afford it :) 

So far I'm very happy with how little I've used FRV. I still learn new things every single time I open the program and it seems I'll keep learning things for a very long while.

So, I come to see if there's any help anybody can offer with some issued with my crazy eff workflow. I don't want to turn any of these things into a request (right now) unless the LibRaw people see value in any of them to the community at wide.

My main problem: 

My main problem is culling and pre-editing. (Well I have problems with editing too, but that's outside the scope here). I'm not a pro. I'm a hobbyst. But my SO is a musician, and I have several musician friends. So a few times a year I'll go to a medium or large show, and take 400 to 800 photos.... and then comes the tortuous process of editing.

As I run out of space for editing and storing stuff (I detest discarding stuff), I've reached the point where I want to cull the photos before copying them over to my drives. First running a pass of culling out the photos that are completely unusable. And then tightening a set/burst, leaving only one or two champion shots from a group.

My trouble here is that I have a Nikon D800 that was a gift from a dear friend. I like to shoot in RAW+JPEG because for reasons I'm looking to do as much SooC as possible (I won't go into that into this message. that is a very long discussion that I can have in a separate thread if someone wants to). My intent is to use the JPG to publish online in as often as I can. And using the RAW only when the look for the final photo doesn't really work, or if I ever want to use a better quality version for a print or a special publish.

I've configured the Nikon to write all RAWs to CF (Faster card for larger files, I have two 64GB that I could switch thorough a shoot), and JPGs to an SD that's 256GB (It's a microSD on an adapter, less stable, I'm troubled but less troubled if I lose the jpg than the raw). Because setting them to duplicate to both cards means much less space for photos. Yeah more security, true, but less space.

But this introduces a problem with FRV.... I can only work in one drive at a time. So only RAW or JPEG... Right now I work on the raw card even if it's a tad slower to browse (FRV is really fast though), because I can switch between internal jpg and raw render in case the picture profile I used really doesn't work/ruin the photo but the raw works well, I don't want to cull that photo. 

My idea is run a fast cull moving all files to _rejected, then a second one tagging specially good images with 1 star as a mark of "work on this first". Maybe also designing a use for color codes later on, and then import everything to LightRoom, to apply labels and tags during the import (I've checked and it seems FRV can't apply tags that LR would recognize. Is this right?).

But this being two drives for raw and jpg makes things harder.

So far, I've created a script, using vbs and the help of ai, which basically asks me the drives for the raw and the jpg versions. The script checks all the folders inside DCIM which have a _rejected folder inside. And for the other drive moves all the corresponding jpg/nef files from the images subfolder to its own _rejected. 

This takes care of "syncing" the culling.

My other plan was to extend the script so that all xmp files in one directory would be copied to the other (if one didn't exist) and renamed to associate with the corresponding jpg/raw, but I planned this to copy stars and colors in metadata. And it seems it's stored in the file's metadata, so I would have to do a second script that does the sync via exiftool, and checkign wether one (and only one) of the paired files had the right fields set and copying them to the other. That's a lot of work.

So what I'm asking here mainly and basically is: Is there any way that already exists. Or that the FRV team is interested and willing to implement, to reject, star and tag raw+jpg image pairs that are hosted on different drives?

Thanks for everything, really, and thanks for FRV.