Video converting, not attaching to node, new nodes automatically getting created, and so on

I believe I have everything set up properly:

1. FFMPEG is working correctly -- when videos are uploaded, they are moved from the original upload directory into a folder specified as that which should contain the original. Thumbnails and .FLV files are being generated in the directory I specified in FFMPEG settings, so everything seems to be functioning as it should.
   
   The settings of my CCK Filefields are as follows:
   • Label: Video Upload, name: field_video_upload, type: file upload, path: video_post_import
   • Label: Converted Video, name: field_converted_video, type: fie upload, path: blank (takes setting from FFMPEG setting since whenever this is populated, the converted video dumps into the user file directory root
   • Label: Converted Thumb, name: field_converted_thumb, type: file upload, path: blank (see above)
2. The original .MOV file is still listed in the Video Upload field as the attached file, and displays in a list within the node. The generated Flash file is not referenced in the node at all. If a [video] tag is used in the node body, the "Video is not available" default .PNG file displays. For the record, I tried this both before running cron, hoping to utilize the automatically converted files, as well as after running cron, with the same result.
3. In the course of exploring different options, I disabled the [video] tag and created a node-video-post.tpl.php file and included the following code:

   <?php
     if ($teaser): /* teaser */
       print flashvideo_get_thumbnail($node);
     else: /* full node */
       print flashvideo_get_video($node, $params);
       print $content;
     endif;
   ?>

   This has been uploaded to my site's theme directory, at the same level as the orignal node.tpl.php file. This file is completely ignored by Drupal. When I added the above code to the default node.tpl.php file, the node behaved as before, displaying "Video not available."

4. I have confirmed that the proper data is being entered into both the FlashVideo and the FFMPEG_data tables of MySql. Here are two entries confirming that everything is working as it should:
   • From ffmpeg_data:
     

     did 	fid 	created 	input_file 	output_file 	status 	data
     15 	144 	1237758012 	sites/default/files/original_video/stardust-test_0.mov 	sites/default/files/converted_video/stardust-test_0_144.flv 	1 	NULL

   • From flashvideo:
     

     fid Ascending 	nid 	oid 	status 	video_index 	width 	height 	play_counter 	flags
     144  	122  	144  	3  	0  	450  	337  	0  	0

   What's curious is that if I examine the files table, I find the following three entries:

   • 144 1 stardust-test_0.mov sites/default/files/original_video/stardust-test_0... video 367555 1 1237758009
   • 149 1 stardust-test_0_144.jpg sites/default/files/converted_video/stardust-test_... jpg 7670 1 1237758012
   • 150 1 stardust-test_0_144.flv sites/default/files/converted_video/stardust-test_... flv-application/octet-stream 271318 1 1237758012

   This tells me that the node references to the file & player flashvars are not being updated at any point, so that the only file associated with the created node is the original uploaded movie, not the converted .FLV file.

5. Following this lead, I constructed a View to pull in all the possible references. Here's the constructed Views query:
   

   SELECT node.nid AS nid,
      node_revisions.body AS node_revisions_body,
      node_revisions.format AS node_revisions_format,
      node.title AS node_title,
      flashvideo.nid AS flashvideo_nid,
      node_data_field_converted_video.field_converted_video_fid AS node_data_field_converted_video_field_converted_video_fid,
      node_data_field_converted_video.field_converted_video_list AS node_data_field_converted_video_field_converted_video_list,
      node_data_field_converted_video.field_converted_video_data AS node_data_field_converted_video_field_converted_video_data,
      node.type AS node_type,
      node.vid AS node_vid
    FROM node node 
    LEFT JOIN node_revisions node_revisions ON node.vid = node_revisions.vid
    LEFT JOIN flashvideo flashvideo ON node.nid = flashvideo.nid
    LEFT JOIN content_type_video_post node_data_field_converted_video ON node.vid = node_data_field_converted_video.vid
    WHERE node.type in ('video_post')
   

   This gave me some optimism. This View preview showed a number of nodes, the first being the ones I would see after created a Video Post type -- that is, the orignal .MOV file being listed and "Video Not Available" displayed. Below these were a number of nodes that had been created by Drupal, categorized as Video Posts, that were created automatically due to what I believe to be the "Convert Videos Immediately" option selected in the Edit FlashVideo Settings - Content Type Settings menu. These generated nodes had the title of the uploaded movie file as the node title, with all other content fields such as Taxonomy and Body empty, although it was still referencing the uploaded .MOV file from the node I created. On the plus side, once I edited this node and added the [video] tag into the body and saved the node, the <embed> tag showed up in the node body, pointing to the Player.swf file, and providing the proper FlashVars so that the desired video was playing!

   Hurray!

6. If I'm rambling at this point, bear with me, for I'm triple-checking everything as I'm writing this, and discovering some new details and possible solutions along the way.
7. If I deselect "Convert Videos Immediately," no nodes are generated, and none of the pertinent data is getting to the original node I create with the original video upload, even after running cron.

It appears at this point that the only way I can get this to work like I want is to select "Convert Videos Immediately," and edit the generated node that's created in the video conversion process. This behavior is unexpected and undocumented, but is a workaround if need be. I would prefer that I only have to deal with the node I originally create, obviously, instead of creating a node, editing the generated node, then deleting the original node. I would also prefer that since the end-users of this site aren't going to be the most tech-savvy folks, I'd like for Drupal to recognize the node-video-post.tpl.php file so that I can disable the [video] tag.

Granted, in the course of writing this request, I did discover the workaround solution, but I can't imagine this is the designed process flow. Any suggestions would be most appreciated and I thank you in advance.