Direct recording to MMC1

[lyndondr]

Is there any way to make all recordings go directly to the MMC with out using the current dir and browsing to the MMC and then going to the record screen. I would like to be able to have the recording screen come up on start up and I know how to do that, and record directly to the memory card.

Thanks

[intifada]

is very very important for me this option!!!! thanks

[TheNewMinistry]

If the Rockbox firmware designates the 128 MB embedded memory as the default destination for recordings, then allowing the user to specify where to record (MMC or embedded) is a good idea.

Let's say, for instance, that you're recording to the 128 MB embedded memory and you run out of free space while recording.

I'd say that's a huge problem.

[screenclene]

  You can do it with the current Rockbox build:

Browse to the directory you want to record into  (eg to <MMC1>), then hit the menu button.
Go to the "Recording" menu
Go to the "Recording Settings" menu
Go to the "Directory" menu
Hit the up/down buttons to change to "Current dir"
Righ click to OK your change.

That's it.  When you record, it goes to <MMC1> if thats what you selected.

screenclene

[lyndondr]

You can do it with the current Rockbox build:

Browse to the directory you want to record into  (eg to <MMC1>), then hit the menu button.
Go to the "Recording" menu
Go to the "Recording Settings" menu
Go to the "Directory" menu
Hit the up/down buttons to change to "Current dir"
Righ click to OK your change.

That's it.  When you record, it goes to <MMC1> if thats what you selected.

screenclene

This is kind of what I'm doing now. I would like to start in the record screen and not have to do any browsing.

[Enzo]

I would like the same!, the only setting possible (for startup recording) is to the /recordings directory...

[amiconn]

Patience....
As I already mentioned elsewhere, a good way to implement an arbitrary recording directory option requires rewriting the settings system to use ascii .cfg files directly. As I'm now majorly annoyed by our current settings system, I'll tackle this problem soon after the 3.0 release.