Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: does rip&encode in ram and could be 100% portable? (Read 1163 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

does rip&encode in ram and could be 100% portable?

Hi
I have used cuetools  2.2.6 , i have updated only flac encoder FLAC v1.4.3 Release bundle
It's amazing fast , and I really like it

can I ask few question ?

1) does it rip and save the wav in ram and encode in flac or other encoders always in ram or does it save the wav files in c: temp folder and after encode in flac or mp3.. ?
in case , if does cuetools /cueripper store in a temp folder could be added in the whish list

2) could be release a 100% stealth portable version ?
just because after some rips I have noticed it does store in the %appdata% files and folders
it would be really great ,so we can use on an usb pen and use on others laptops or computers without leaving files
could be added in the wishlist ? have a full portable so powerfull
even reading this tutorial to make it portable , it does save always folder and files in host machine %appdata%

3) i have selected cover art  pretty huge 2000 pixel but it does download only 300px cover art , may i know why?

thanks

Re: does rip&encode in ram and could be 100% portable?

Reply #1 –
libFLAC v1.4.3 is already built-in. Unless you're referring to an External Encoder. All users must supply the .exe (and dependencies) to use the flac.exe encoder.

1. No temporary .wav file. Ripped/decoded audio is fed directly into the encoder. Metadata is written last after all audio files are written.

2. If you remove/rename the user_profiles_enabled file (from the CUETools directory) before you run CUETools/CUERipper for the first time, no folders are created in %appdata%. Anytime you run CUETools/CUERipper with the user_profiles_enabled file present the appropriate folders are created in %appdata%. If you then decide to switch to portable mode, the user can delete the folders from %appdata% (they will not be deleted by CUETools/CUERipper) and are only re-created if you run CUETools/CUERipper again with the user_profiles_enabled file present.

3. There is  a setting in CUETools to limit the cover art size (pixels). There is no size limit setting in CUERipper if you have Album art size set to Large.
korth

Re: does rip&encode in ram and could be 100% portable?

Reply #2 –
Quote from: korth on
libFLAC v1.4.3 is already built-in. Unless you're referring to an External Encoder. All users must supply the .exe (and dependencies) to use the flac.exe encoder.

1. No temporary .wav file. Ripped/decoded audio is fed directly into the encoder. Metadata is written last after all audio files are written.

2. If you remove/rename the user_profiles_enabled file (from the CUETools directory) before you run CUETools/CUERipper for the first time, no folders are created in %appdata%. Anytime you run CUETools/CUERipper with the user_profiles_enabled file present the appropriate folders are created in %appdata%. If you then decide to switch to portable mode, the user can delete the folders from %appdata% (they will not be deleted by CUETools/CUERipper) and are only re-created if you run CUETools/CUERipper again with the user_profiles_enabled file present.

3. There is  a setting in CUETools to limit the cover art size (pixels). There is no size limit setting in CUERipper if you have Album art size set to Large.
Hi Korth
2) i have remove and even renamed user_profiles_enabled ,but cuetools does keep writing on the %appdata%
don't know why..

4) in CUETools i have added external codec , like lame.exe ,flac.exe qaac.exe and refalac64.exe about these encoder are not present in CUERipper.exe
can i know why?
since if i want to rip a cd , i have to use CUERipper.exe

thanks Korth

Re: does rip&encode in ram and could be 100% portable?

Reply #3 –
2. I assume you're referring to
Code: [Select]
%appdata%\CUE Tools\
and
Code: [Select]
%appdata%\CUERipper\
I cannot duplicate. The folders do not exist in %appdata% on my system. I currently have 87 beta and release versions of CUETools (in portable mode) on my system. That doesn't mean it isn't happening on your system. It just means I don't know how to duplicate it on mine.

4. CUETools and CUERipper use different settings files located in separate folders. They need to be configured separately.
There are built-in ALAC & libmp3LAME encoders too. You don't have to use them.
For flac.exe, qaac.exe, and lame.exe in CUERipper you just need select the preset and click the gear icon to configure the path to the .exe or other options.


For refalac, you can add a new encoder to the \CUERipper\settings.txt file in the encoders section. CUERipper should not be open.
Code: [Select]
=    {
=      "$type": "CUETools.Codecs.CommandLine.EncoderSettings, CUETools.Codecs",
=      "Name": "refalac.exe",
=      "Extension": "m4a",
=      "Lossless": true,
=      "Path": "refalac.exe",
=      "Parameters": "- -o %O"
=    }
Then open CUERipper to configure path via the gear icon (or simply copy refalac.exe to the CUETools program folder).
korth

Re: does rip&encode in ram and could be 100% portable?

Reply #4 –
I forgot to show adding a comma after the current last encoder
Code: [Select]
=    {
=      "$type": "CUETools.Codecs.CommandLine.EncoderSettings, CUETools.Codecs",
=      "Name": "qaac.exe (tvbr)",
=      "Extension": "m4a",
=      "SupportedModes": "10 20 30 40 50 60 70 80 90 100 110 127",
=      "EncoderMode": "80",
=      "Path": "qaac.exe",
=      "Parameters": "-s -V %M -q 2 - -o %O"
=    }
=  ],

Add comma after last } before adding new encoder
Code: [Select]
=    {
=      "$type": "CUETools.Codecs.CommandLine.EncoderSettings, CUETools.Codecs",
=      "Name": "qaac.exe (tvbr)",
=      "Extension": "m4a",
=      "SupportedModes": "10 20 30 40 50 60 70 80 90 100 110 127",
=      "EncoderMode": "80",
=      "Path": "qaac.exe",
=      "Parameters": "-s -V %M -q 2 - -o %O"
=    },
=    {
=      "$type": "CUETools.Codecs.CommandLine.EncoderSettings, CUETools.Codecs",
=      "Name": "refalac.exe",
=      "Extension": "m4a",
=      "Lossless": true,
=      "Path": "refalac.exe",
=      "Parameters": "- -o %O"
=    }
=  ],
korth