So....I finished my first sequence in 4.0.18 and thought I would try playing with the export feature. I went to the Export tab and tried both options...and nothing happens. Are they live yet? I went to see if I could find the what's not working yet post/list but couldn't find it.
So....am I just getting ahead of myself or am I missing something....?
Thanks
SC
Just remember that this is still beta software and not an officially released version.
jnealand wrote:Just remember that this is still beta software and not an officially released version.
Oh...I understand and wasn't being critical....just trying to verify. When you aren't sure of which features are live yet you don't know if it's you or a not completed development piece.....
I have no problem waiting on known issues as I can work around or put them off until later and just move on to other things while the development is being finalized.... But being unsure if it's something I'm not seeing/doing or something not finalized then the only way I know to verify which is to ask.....if that makes sense...
I'm just peddlin along as fast as I can.....trying to keep up with the 'gang'.... 🙂
two ways to export:
1) If you want to just export a model (say your megatree) to LOR,Vixen,HLS , etc. Right click on the model that is in the SEQUENCER tab. Choose export model
2) If you want to export every model you have, we have changed this in XL 4. First save your sequence and then go to CONVERT and convert your fseq into lms, lcb, vix or whatever files works for your sequencer.
smeighan wrote:two ways to export:1) If you want to just export a model (say your megatree) to LOR,Vixen,HLS , etc. Right click on the model that is in the SEQUENCER tab. Choose export model
2) If you want to export every model you have, we have changed this in XL 4. First save your sequence and then go to CONVERT and convert your fseq into lms, lcb, vix or whatever files works for your sequencer.
Thanks Joe.....I had no clue....I was just trying the tab up top.....
Just tried it....with mixed results. When I exported all models (not the wholehouse model)it worked perfectly. When I exported the wholehouse model alone some channels didn't export over to the HLSNC file....the channels play in XL preview and you can clearly see them working but in the exported WHM there is a series of channels that have no data in them....35 channels exactly.....which is not divisible by 3 so it doesn't appear to be a pixel problem per se.....
The fact that it plays fine in XL preview is what is confusing me.....and if all the other models didn't work when exported I could also see a common issue....but I'm scratching my head on this.....
Any ideas are welcomed.....
UPDATE: My bad it was 35 pixels which happens to be the exact number in my string around the door...and is next to the string that is out.....and they are the first 35 pixels in the next universe......
but, as I stated it works fine until I export the WHM......curious....mighty curious....
PROBLEM SOLVED: I went back and checked all my model channel # assignments. Several of my models were scrambled. Most of the ones affected were set to channel 1 as the first channel....instead of the correct sequential method. Not sure how that happened unless I did it when playing around with and adjusting my WHM.....which very is possible even though I didn't manually change them maybe manipulating things reset them without my knowing....
SC
smeighan wrote:two ways to export:1) If you want to just export a model (say your megatree) to LOR,Vixen,HLS , etc. Right click on the model that is in the SEQUENCER tab. Choose export model
2) If you want to export every model you have, we have changed this in XL 4. First save your sequence and then go to CONVERT and convert your fseq into lms, lcb, vix or whatever files works for your sequencer.
Still crashes when I right click to Export; generates a bug report also
Yeah....I when I hit "save as" it crashes but it seems to export the HLSNC file nevertheless....so I don't know if that file is the source of my missing 35 pixels....or if it's something else..... I'm still poking around looking for something I didn't assign properly.....
Open an issue on the crash on github issue tracker
Sent from my iPhone using Tapatalk
smeighan wrote:Open an issue on the crash on github issue trackerSent from my iPhone using Tapatalk
already did that couple days ago
smeighan wrote:Open an issue on the crash on github issue tracker
I submitted that and another....thanks Sean

