 | | Re: Memory - Where did it go?
|
|
(...) By "Block" you mean a simple operation like and add or a multiply or turning on a motor or reading a sensor? These 'blocks' ought to be turned into little interpreted byte-code segments - it's hard to imagine how a block could possibly take up (...) (18 years ago, 8-Jul-06, to lugnet.robotics)
|
| |
| | Re: Memory - Where did it go?
|
|
(...) By "block" I mean a NXT-G code block as dropped from a pallet. Yep, you would think that these things would compile down to a single bytecode (or a few bytecode sequences), but they don't. There is an awful lot going on under the hood, and (...) (18 years ago, 8-Jul-06, to lugnet.robotics)
|
| |
| | Re: Memory - Where did it go?
|
|
(...) Everything in NXT-G is a block that you drag and drop onto your program. All blocks in NXT-G are LabView Virtual Instruments (VIs). Some blocks expand into a loop construct. Others expand into a switch construct. They often represent (...) (18 years ago, 10-Jul-06, to lugnet.robotics)
|
| |
| | Re: Memory - Where did it go?
|
|
Wow, what a wealth of information. Thanks for the great detail. I am already using the Wav2Rso program but did not know enough about sound files to understand the convertion options. Which option gives you the smallest converted file? In your other (...) (18 years ago, 10-Jul-06, to lugnet.robotics)
|
| |
| | Re: Memory - Where did it go?
|
|
(...) I'm not certain, but I think the file size will be basically the same for each resample option since the result is an 8k 8 bit mono file. There may be slight differences. The higher quality options (in quality order from top to bottom) may be (...) (18 years ago, 10-Jul-06, to lugnet.robotics)
|
