I’m using the Project section in Visual Sequencer very much for importing and export .csv files. Something that I’ve discovered is that when I’m importing very large .csv files with almost 1000 steps the SEQ program seems to halt for almost 2 minutes! It seems like SEQ works alot in the background to accommodate all data in the .csv file.
To Laurent: Is it possible to make a simple progress indicator when importing csv files?
Of course, this is not really necessary but would be very useful when importing extremely large files. If I don’t remember wrong SEQ is capable of handling 255 sequences with 255 steps in each seq.! (eh… maybe this was the limit for the EEPROM in the GP sequencers?) Anyway 255*255 = 65025 steps! How long time would an importing of a csv file with 65000 steps take?
Hello zenta,
Seq can handle 999,998,000,001 steps (999,999 Sequences X 999,999 Steps)…so it will take 3,805 years to fill the database on your computer…um ending fall 5,813 AD
the good news is my computer is 25 times faster so it will take only 152 years here. ha !
seriously, i have looked at the code and it’s crystal clear code, i can’t improve it as long as i’m using the same database engine.
importing 3000 steps takes less than 15 seconds here P4HT @ 3.06Ghz so i was not aware of this issue, sorry.
i’m working on SEQ right now, i’m adding a progress indicator for import feature 8) …what about export ?
the 255 sequences X 255 steps limitation concerns the GP firmware and the onboard twin sequencers / EEPROM storage…
i was able to improve the speed, the import algorithm was working on a filtered Database (Sloooooowwow),
making it unfiltered during the import process then filtering it again at the end of process makes it faster…hahaha crystal clear code
Hi Laurent!
I tried the SEQ ver 1.16. And importing 984 steps didn’t take more than 6 sec! Excellent! The bar was also useful, but since it didn’t take so long it was almost not necessary
Sorry, I must have missed your post’s here. The export has always worked fine. Anyway you seemed to have it all fixed now! Ok, so there is “no limits” about the amount of steps and seq’s, great! But seriously I think 255*255 almost would be enough too
maybe this was the limit for the EEPROM in the GP sequencers?) Anyway 255*255 = 65025 steps! How long time would an importing of a csv file with 65000 steps take? 
The export has always worked fine. Anyway you seemed to have it all fixed now! Ok, so there is “no limits” about the amount of steps and seq’s, great! But seriously I think 255*255 almost would be enough too 