On Wed, 2011-10-05 at 13:14 -0400, Fred Gleason wrote: > > I get hives just trying to imagine the convolutions that would be > required to make play-while-record work properly on NTFS. It's a > minefield of potential race conditions (and one not very successfully > navigated by some vendors, if the reliability of their products is any > indication).
I know (I think) what would be involved but you would have to pay me a hell of a lot of money to cover the loss of sanity involved in trying to pull it off. Reliably sane cleanup after a unclean shutdown would be "Fun" to implement and debug.... > Ripcd and CURL could both be done on Windows without huge effort. > Caed would be the killer -- not only would there be the NTFS/FAT > showstopper referenced above, but some sort of native Windows sound > support would be needed. Yeech. Don't Ripcd and Curl both touch the audio storage directory contents? It was that aspect that was sounding alarm bells in my head (plus the fact that Ripcd likes to fork, which Windows does horribly badly). As for audio, ASIO is callback based, you surely wouldn't want to be doing windows native audio. The BIG showstopper is the filesystem semantics issue. > Before any of that can happen though, all of RD would need to be > ported to Qt4 Mostly done actually, for all that a whole pile of forward porting is needed. IIRC there were only a few files in /lib that still needed doing in one of my branches, mostly stuff where the old comboboxes and such were depreciated in favour of some hairy MVC stuff. Actually the biggest headache here is probably that Rivendells release policy would require a new major number because of the new library dependency. I figure I could do that forward port and have most of it working in a month if I went for it full time (Unemployed at the moment so that is actually possible). Could you update my CVS creds with a new SSH key if I sent it to you? I may have a look at what it would take to do a QT4 branch from whatever CVS head is. Regards, Dan. _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
