Its not that I want them in Lightroom necessarily. I want all my pictures and videos and files in the cloud and then want to be able to access them from the 1 spot in the appropriate program like Google Drive does.
I switched from Google Drive to Adobe because I wanted a proper photo editor and a proper video editor but now it's seeming like the Creative Cloud is much more limited then I thought.
Okay, so let me restate the problem and propose a solution:
- Problem: you uploaded video content to Creative Cloud using Lightroom, which keeps media in a special partition of your CC space, and Rush cannot access media stored in that LR partition.
- since you're not committed to uploading your video to Creative Cloud via Lightroom, you could move that content from the LR partition to the main CCFiles location. I think this would entail re-uploading manually (which will be easiest from a desktop system), then deleting the assets from your LR catalog. Of course, if your only copy of the videos is in the LR cloud, then you'll first have to download it. Apart from the time it would take you to move the content, it doesn't sound like this would cost you anything functionally because you're not using the videos in Lightroom.
Photographs are more problematic. If you intend to use photos from LR library in your Rush projects, then about the best workflow I can think of is to export the photos from LR either directly to your phone or tablet or to the main CCFiles area. While that might be marginally viable if you will be using a small number of photos in Rush, it would be painful and limiting if you planned to include lots of photos in your Rush projects.
FWIW, I'm sure that the Lightroom crew had good reason to keep media in a sequestered partition. My guess is that one reason is that everything in the main CCFiles area automatically downloads to every desktop system that's logged into a given CC account, and LR wanted to avoid that and keep the content in the cloud. A downside is that additional work was required on the Rush side to provide access to that partition, and we just didn't have time to get that done for 1.0.