Support and General Use > Recording

Recording Menu Overhaul in Preparation for MikeS's Massive Recording Patch.

<< < (2/3) > >>

pabouk:
I agree with Llorean. I think that the configuration should be kept simple.

You can simply switch the settings suggested by Davide-NYC by selecting a configuration file which is a more general approach.

I would "just" like to see extended support for configuration files:

* Easier possibility to create a configuration file with just some parameters.
Now you have to open the file in an editor and erase the unwanted lines. The easier approach could be accomplished by
a) creating a "differential" configuration file:
1. Mark a reference configuration.
2. Make changes of the configuration.
3. Save just the changes since marking the reference configuration.
b) editing an existing configuration file:
1. Open a configuration file.
2. Make changes of the configuration.
3. Save just the changes since opening the file and the unchanged parameters from the original file.
EDIT: c) optionally editing an existing configuration file using a configuration editor plug-in.
a) and b) could possibly be also implemented using a plug-in.

* Sort the configuration files into sub-directories (i.e. recording, sound settings etc.)

* Make the configuration files accessible from the specific menus like Recording, Sound Settings etc. as "presets". EDIT: Like it is done for equalizer presets and the WPS selection already.

* Cache (some of) the configuration files into the RAM so they can be switched more quickly.

Optionally for different approaches:
* Add actions to the configuration files. For example: entering a specific screen (recording, radio etc.), starting some action (record, playback...) EDIT: The actions would be performed when loading the configuration file.

EDIT:
* Later there could be a timer (already partially implemented by Mmmm) which would load such a configuration file with an action. For example: play a certain radio preset and start recording.

Davide-NYC:

--- Quote from: PaulJam on October 25, 2006, 03:44:43 AM ---
--- Quote ---The problem is: how to visualize this to the user.
--- End quote ---
A solution that comes to my mind would be to show a splash with the current encoder settings when changing the source.
Something like "Int. Mic.: Mp3 / 128kbps / 44.1kHz"

--- End quote ---

There is genius here.

OK what about the following:

The statusbar must change to the "recording statusbar" immediately upon entering either the WRS or the Recording Settings Menu. That way Type, Bitrate, Samplerate and Channels are already displayed. Currently the Statusbar changes only once the WRS has been entered and even then if you make changes from the Recording Settings Menu they don't always reflect in the statusbar immediately.

That leaves only Source.

Using Lloreans and MikeS's method (this is how Mike's patch is setup already) How about adding   a line at the top of the screen showing the current config. This line should change immediately upon any setting change.

We could combine this with Source dependent (inherited) settings.

| MIC-IN -->  MP3 / 160kbps / 22.05kHz / Mono |

Source
Format
Bitrate
Frequency
...

So if the user changes the source the encoder settings will change to whatever was last selected for that source! As long as it's clearly displayed across the top line it should be clear to the user what is happening.

Example: switching from MIC to LINE would give (for example)

| LINE-IN -->  WAV /  -----  / 44.1kHz / Stereo |

Source
Format
Bitrate
Frequency
...

This maybe satisfies the most? Discuss!

Davide-NYC:
We *could* also nest the menu's like so:

| source -->     type / BR / SR / channels |

Source
Format
Other

which if "expanded" would (currently) become:

| source -->     type / BR / SR / channels |

Source
    Microphone
     Line-In
     SPDIF
     FM Radio
Format
     Type/Encoder
     Bit Rate
     Sample Rate
     Channels
Other
     File Split Options
     Prerecord Time
     Create New Files Immediately
     Directory
     Show Recording Screen on Startup
     Clipping Light
     Automatic Gain Control
     AGC clip time

In every screen the "current recording config" would be displayed on the first line.

The idea here is that most people (even me) almost never "fiddle" with the stuff in the OTHER folder. I figure out what the options do, set them, and forget them.

My usage may be different from other peoples, but I think that if the settings could be source dependent it would be great. Including AGC. (!) (?)

Hmm. I guess inherited AGC settings aren't necessary since you can see and change them on the fly from the WRS.

Discusss!!!!!

Maybe AGC should have it's own root menu?

djdafreund:
I can't seem to find this answer using search, but here goes. Is it possible to have anyone that has compiled a build for the H10 with recording AND/OR tuner function patched for use? I realise it's not 'enabled/supported' but i am a debugger for various programs and am currantly bored, and just want to mess with something new, and would LOVE to try it out.
  I promise i won't ask for any support other then just to mess around with things. I just don't want to mess around with patching one myself, as i did read how to do it, but don't want to put linux on my system to do this. And i'm not aware of any other methods using xp to do this. The other truth is i'm slightly lazy when it comes to compiling programs, to be more honest.

 Could anyone possibly help me out here? Please? Thanks in advance.

Davide-NYC:
What the hell does this have to do with the topic / subject of this thread?  >:(


--- Quote from: djdafreund on October 28, 2006, 09:28:53 PM ---I can't seem to find this answer using search, but here goes. Is it possible to have anyone that has compiled a build for the H10 with recording AND/OR tuner function patched for use? I realise it's not 'enabled/supported' but i am a debugger for various programs and am currantly bored, and just want to mess with something new, and would LOVE to try it out.
  I promise i won't ask for any support other then just to mess around with things. I just don't want to mess around with patching one myself, as i did read how to do it, but don't want to put linux on my system to do this. And i'm not aware of any other methods using xp to do this. The other truth is i'm slightly lazy when it comes to compiling programs, to be more honest.

 Could anyone possibly help me out here? Please? Thanks in advance.

--- End quote ---

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version